Chap 7. Moving to Design
* Analysis -> Design (Evolving)
(analysis ~ Design mutually go)
* Analysis Model Examine(Cross Check)
Functional - Structural (activity diagram ~ class diagram)
Functional - Behavior (activity diagram ~ communication diagram, state machine)
Structural - Behavior (class Diagram ~ communication diagram, state machine)
* Analysis Model -> Design Model !!non-Functional Requirements!!
performance + environment
(maintainable, affordable, effective, efficient)
* Factoring ( Generalization, Aggregation, Abstraction, Refinement )
Partition + Collaboration
* Layer - include System environment
-> Package Diagram ( HCI, PD, PA, DM, F )
* Guidelines for Package Diagram - logical, semantic, name, cohesive
(context, cluster, relation, verify & validate)
* Design Strategy ( Develop, Purchase package, Outsource )
* Develop ( Flexible, specific, skill up, security ) // ( burden, risk )
* Purchase SW ( efficient, reliable ) // ( not flexible )
System Integration - (API)
* Outsource - coordinator, security
* Tool, Skill, package, outsource Company
'Archived(CSE) > 소프트웨어 설계' 카테고리의 다른 글
Chap 12. Construction (0) | 2018.12.08 |
---|---|
Chap 10. User Interface Design (0) | 2018.11.29 |
Chap 11. Physical Architecture layer Design (0) | 2018.11.26 |
Chap 8. Class and Method Design (0) | 2018.11.22 |
Chap 6. Behavioral Modeling (0) | 2018.11.15 |