Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
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
Normal Size Small Size show me how
UP
Unified Process
| Question | Answer |
|---|---|
| UP phases | 1) Inception 2) Elaboration 3) Construction 4) Transition |
| UP is | 1) Use-Case Driven 2) Architecture-Centric 3) Iterative and Incremental |
| Inception (launching the project) | 1) Cost/Benefit 2) Time to market 3) System Scope 4) Resolve ambiguities in the requirements 5) Candidate Architecture 6) Mitigate critical risks |
| Inception deliverables | 1) feature list 2) v1 domain model 3) v1 use case model 4) analysis model 5) design model 6) Requirements 7) Candidate Architecture 8) Possible prototype 9) v1 risk and use case ranking list 10) phases plan 11) Business success criteria |
| Elaboration (Architectural baseline) | 1) remaining requirements, 2) functional requirements -> use cases. 3) Architectural foundation 4) project plan 5) Worth of Business case |
| Elaboration deliverables | 1) Complete domain model 2) New version of all the models 3) No architecturally important use case is missing 4) Executable architectural baseline and description 5) Project plan for the constructional and transition phases 6) Complete businenss case |
| Construction (leads to initial operational capability) | 1) starting from an executable architecture baseline and 2) working through a series of iterations and increments, 3) develops a software product ready for initial operation in the user environment. |
| Construction deliverables | 1) Project plan for the transition phase 2) MVP software 3) all artifacts, models 4) maintained and updated architectural description 5) Beta user manual 6) Business case |
| Transition (Completes product release) | This phase focuses on establishing the product in the operational environment. pub fixes, documentation |
| Transition deliverables | 1) The Software 2) Contracts, licenses, waivers and warranties 3) models, architecture description 4) Final user, operator, sysadmin manuals and trailing materials 5) Customer support references |
| User story | 1) User stories are written by users. 2) User stories focuses on details. 3) User stories cannot be guaranteed to be complete. User stories does not define system boundaries. |
| Use cases | 1) Use cases are written by developers. 2) A use case model will describe the complete (sub)system. 3) A use case defines the system boundary. 4) Any use case scenario will bring the system from one consistent state to another. |
| Use case detail levels | 1) Brief use case The use case is merely more than the title of an action 2) Casual use case Typically casual use cases are described in more detail 3) Fully dressed use case Includes all entries from the template |
| Actors | Actors are outside the system. Actor responsibilities are not and should not be covered by the system. Actors are not concrete people or systems, rather abstract roles of these users or systems. |
Created by:
timeakiss
Popular Computers sets