Introduction to the Unified Process

Multiple Choice

1. The process model or methodology we are teaching in this class is called____.
   1. Unified Process
   2. Waterfall
   3. Rational Unified Process
   4. Agile Delopment Process
   5. Extreme Programming
2. Which one of the following is NOT a characteristics of UML
   1. Is graphical
   2. Allow software engineers to communicate quickly and accurately
   3. Is a modeling technique
   4. Was established by the Object Management Group
   5. Is used to represent deliverables of the structured development paradigm
3. UML stands for
   1. Universal Metadata Language
   2. Universal Modeling Language
   3. Unified Micro Language
   4. Unified Modeling Language
4. Which of the following is most true about UML.
   1. UML uses Use Cases sometimes but not always
   2. UML is use case centric
   3. Use cases are only used if there is a misunderstanding in requirements
   4. Use cases are only used as support to the data dictionary.
5. Which of the following are the workflows of the unified process
   1. Initiation, Elaboration, Analysis, Design, Implementation, Testing
   2. Requirements, Analysis, Design, Implementation
   3. Inception, Analysis, Implementation
   4. Requirements, Analysis, Construction, Implementation
6. Which of the following are the phases of the unified process
   1. Inception, Analysis, Construction, Implementation
   2. Initiation, Elaboration, Construction, Implementation
   3. Inception, Elaboration, Construction, Transition
   4. Initiation, Analysis Construction, Transition
7. Initial business model, project plan, and initial vision are deliverables of what PHASE of the unified process:
   1. Planning
   2. Inception
   3. Initiation
   4. Elaboration
   5. Requirements
   6. Analysis
   7. Design
   8. Construction
   9. Implementation
   10. Transition
8. The completed domain model (use cases, classes), completed business model, and project plan are deliverables of what PHASE of the unified process:
   1. Planning
   2. Inception
   3. Initiation
   4. Elaboration
   5. Requirements
   6. Analysis
   7. Design
   8. Construction
   9. Implementation
   10. Transition
9. Working software, user manuals, and acceptance testing documentation are deliverables of what PHASE of the unified process:
   1. Planning
   2. Inception
   3. Initiation
   4. Elaboration
   5. Requirements
   6. Analysis
   7. Design
   8. Construction
   9. Implementation
   10. Transition
10. Scope Definition, stakeholder identification, risk analysis, and team building are done during what unified process workflow.
    1. Planning
    2. Inception
    3. Initiation
    4. Elaboration
    5. Requirements
    6. Analysis
    7. Design
    8. Construction
    9. Implementation
    10. Transition
11. Listing candidate requirements , domain modeling, defining functional requirements, and use case modeling are done in which unified process workflow.
    1. Planning
    2. Inception
    3. Initiation
    4. Elaboration
    5. Requirements
    6. Analysis
    7. Design
    8. Construction
    9. Implementation
    10. Transition
12. Creating Packages, creating design classes, defining method signatures, creation of interaction diagrams are all done in what unified process workflow.
    1. Planning
    2. Inception
    3. Initiation
    4. Elaboration
    5. Requirements
    6. Analysis
    7. Design
    8. Construction
    9. Implementation
    10. Transition