1.2 – Software Architect and Design Roles in Industry
Software design looks at the lower-level aspects of a system.
Software architecture looks at the higher-level aspects of a system.
Software design is the process of turning the wishes and requirements of a customer into working code that is stable and maintainable in the long run.
Software architecture is primarily begins with understanding what is the business problem that the client needs to solve. Software architecture is the study of boxes and lines because the first description of what it is your are trying to do is simply a lot of boxes with things inside them and lines expressing relationships.
Why is it important?
- It is important because if you get it wrong, your project will fail.
What are key challenges in software design and architecture?
- It is the tendency to have to trade off between speed and quality.
Software Design Principles
- Simplicity
- To avoid Unnecessary Complexity
Required Skills to Be a Software Architect
- Has to be a Technical guru.
- Need to be able to communicate with people at the level that they want to be communicated with.
- Project planning, and oraganizational skills.
- Need to be able to get people to tell you what their requirements are.
Advices to a Newbie Software Architect
- Try to read the foundational literature in the field, and read a lot of code and a lot of code. That is how you become a software architect.
- Meet as many as humanly possible, and get some ideas at the same time share your own perspective.
- Try to learn from mistakes.
'공부 > Object-Oriented Design' 카테고리의 다른 글
1.6 – Record, Organize, and Refine Components (0) | 2021.09.18 |
---|---|
1.5 – Competing Qualities and Trade-offs (0) | 2021.09.17 |
1.4 – Software Requirements, Conceptual and Technical Designs (0) | 2021.09.17 |
1.3 – Object-Oriented Modeling (0) | 2021.09.17 |
1-1 Welcome to Software Design and Architecture (0) | 2021.09.15 |
댓글