1 (TCO 1) Explain the Unitifed Process (UP). (Points : 11) 2. (TCO 1) What is me
ID: 3851345 • Letter: 1
Question
1 (TCO 1) Explain the Unitifed Process (UP). (Points : 11)
2. (TCO 1) What is meant by saying that UP is an iterative and incremental process? (Points : 11)
3. (TCO 4) Describe sequence diagrams. Include in your discussion how to read them. What does a curved message call line do? There is an ATHLETE class and a COACH class. A coach wants to get an athlete's statistics using a method named Get_Athlete_Statistics. Explain which class this method belongs in and how the message line would be drawn in a sequence diagram. (Points : 11)
4. (TCO 2) Explain the difference between normal flows and alternate or subflows that is documented in a use case. What technique is used to link the logic in those two areas with each other? Give an example. (Points : 11)
5. (TCO 3) Define a structural model. Why should a systems analyst create one? What is class cohesion? Give an example of class cohesion. In your example, discuss attributes and operations. (Points : 11)
6. (TCO 3) Define the following terms: class, attribute, and operation. Give examples of each in a class. (Points : 11)
7. (TCO 5) How does a communication diagram differ from a sequence diagram? Why would an analyst choose to draw a communication diagram? If object Z sends a message to object T, where does the method being executed reside? (Points : 11)
8. (TCO 6) Describe the generalization/specialization class relationship and how this relationship relates to the concept of inheritance. (Points : 11)
. 9. (TCO 7) Explain what is the goal of the Implementation phase of the SDLC. (Points : 11)
10. (TCO 8) Some objects are suitable for a state machine diagraming while others are not. Give an explanation and example of an object that would be a poor candidate to diagram in an object state diagram. Justify your answers. (Points : 11)
Explanation / Answer
1)Unitifed Process (UP):
Unified process (UP) is an architecture-centric, use-case driven, iterative and incremental development process that leverages unified modeling language and is compliant with the system process engineering metamodel. Unified process can be applied to different software systems with different levels of technical and managerial complexity across various domains and organizational cultures.
->Unified process is a refinement of rational unified process. It is an extensible framework that can be customized for specific projects.
This process divides the development process into four phases:
Inception:
The primary goal of the Inception phase is to establish the case for the viability of the proposed system.
The tasks that a project team performs during Inception include the following:
Defining the scope of the system (that is, what's in and what's out)
Outlining a candidate architecture, which is made up of initial versions of six different models
Identifying critical risks and determining when and how the project will address them
Starting to make the business case that the project is worth doing, based on initial estimates of cost, effort, schedule, and product quality.
Elaboration:
The primary goal of the Elaboration phase is to establish the ability to build the new system given the financial constraints, schedule constraints, and other kinds of constraints that the development project faces.
The tasks that a project team performs during Elaboration include the following:
Capturing a healthy majority of the remaining functional requirements
Expanding the candidate architecture into a full architectural baseline, which is an internal release of the system focused on describing the architecture
Addressing significant risks on an ongoing basis
Finalizing the business case for the project and preparing a project plan that contains sufficient detail to guide the next phase of the project (Construction)
Construction:
The primary goal of the Construction phase is to build a system capable of operating successfully in beta customer environments.
During Construction, the project team performs tasks that involve building the system iteratively and incrementally (see "Iterations and Increments" later in this chapter), making sure that the viability of the system is always evident in executable form.
The major milestone associated with the Construction phase is called Initial Operational Capability. The project has reached this milestone if a set of beta customers has a more or less fully operational system in their hands.
Transition:
The primary goal of the Transition phase is to roll out the fully functional system to customers.
During Transition, the project team focuses on correcting defects and modifying the system to correct previously unidentified problems.
The major milestone associated with the Transition phase is called Product Release.
UP has the following major characteristics:
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.