This is the last step between modeling our problems and coding our solutions.
Each of the elements in our requirements model helps provide us with necessary information that can be used to solve our problem.
While the book has the models and design being two separate steps, in many cases you will find that they are combined in real life and people automatically start building the design from the models and the differences between the two are blurred into one real step before the actual coding process.
As design iterations occur, the design is refined to provide a more detailed view of the project until it is ready for actual coding.
- The design should implement all of the explicit requirements contained in the requirements model, and it must accommodate all of the implicit requirements desired by stakeholders.
- The design should be a readable, understandable guide for those who generate code and for those who test and subsequently support the software.
- The design should provide a complete picture of the software, addressing the data, functional, and behavioral domains from an implementation perspective.
Design with the Concept of Software Engineering in Mind was originally found on Access 2 Learn
