click below
click below
Normal Size Small Size show me how
Architecture based
Contracting, based on architecture
Question | Answer |
---|---|
Domain Model | – Must have attributes – Must have correct cardinalities – Must include all relevant concepts – Does normally NOT include methods – Remember glossary – Relations are without direction – Roles are typically left out |
Contracting party activities | – Do inception and the first iteration(s) in elaboration – Create Use Case model – Create the architectural model |
Contracted party activities | – Do the rest – Wil lwork under the constrains of the requirements and architecture defined by the contracting party |
Architectural contracts focus on | focus on the solution domain – Make the overall decisions about the structure of the application – High level design of the system – Focus both on functional and non-functional requirements – UML component, deployment, and package diagrams |
Contracting party artifacts | Requirements 1) Vision 2) Use Case Model 3) Supplementary Specifications 4) Glossary 5) Requirement Management Plan 6) Domain Model (optional) Analysis 7) Analysis Model 8) Architecture model 9) Design model&testplan |
Contracted party artifacts | Analysis 1) Data Model 2) Deployment Model 3) Implementation Model 4) Integration Build Plan Test 5) Test Suite 6) Test Results 7) Test Case |
FURPS | – Functionality-Featureset,Security – Usability-Humanfactors,Aesthetics,Consistency,Documentation – Reliability-Frequency/severityoffailure,Predictability – Performance-Speed,Responsetime – Supportability- Testability,Extensibility,Maintainability |
The tree basic principles | – Low coupling – High cohesion – Protected variation, Architectural patterns |