Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.


Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.

Remove ads
Don't know
Know
remaining cards
Save
0:01
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
Retries:
restart all cards




share
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

Architecture based

Contracting, based on architecture

QuestionAnswer
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
Created by: timeakiss