UNITENIANS

Module 4 : Software Engineering

Basically Chapter 4 explains design creates the representation or model of the software. Different than the analysis model , design model provides details such as software architecture , data structures , interfaces and components that are necessary to implement the system. Thus it is important because model design can assessed for quality and improvement before code , test and more users gets involved.

Apart from that , a good characterictis of a design must be :-

• implementation of all the expilcit requirements contained in the analysis model and it must accomodate all the implicit requirements desired by the customer
• must be readable , understandable guide for those who generate code and for those who test and subsequently support the software
• must provide a complete picture of the software , addressing the data , functional and behavioral domains from an implementation perspective

• should not suffer from 'tunnel vision'
• should be traceable to the analysis model
• should not reinvent the wheel
• should minimize the intellectual distance between software and problem
• should exhibit uniformly and integration
• should be structure to accomodate changes
• should be structure to degrade gently
• design is not a coding ,coding is not design
• design should be assessed for quality as it is being created
• should be reviewed to minimize conceptual (semantic) errors

1. Abstraction that is divided into Procedural abstraction and Data abstractions
2. Architecture that basically describe the overall structure of the software
3. Patterns
4. Separations of concerns , its a rule of thumb to define how modules should be separated
5. Modularity , to divide into components
6. Information hiding
7. Functional Independence
8. Refinement
9. Aspects
10. Refactoring
11. OO Design concepts
12. Design classes

This post was written by: UNITENIAN AUTHORS