The UP describes work activities, such as writing a use case, within disciplines a set of activities (and related artifacts) in one subject area, such as the activities within requirements analysis. In the UP, an artifactis the general term for any work product: code, Web graphics, database schema, text documents, diagrams, models, and so on.
There are several disciplines in the UP; this book focuses on some artifacts in the following three:
A longer list of UP disciplines is shown in Figure.
In the UP, Implementation means programming and building the system, not deploying it. The Environmentdiscipline refers to establishing the tools and customizing the process for the project that is, setting up the tool and process environment.
What is the Relationship Between the Disciplines and Phases?
As illustrated in Figure, during one iteration work goes on in most or all disciplines. However, the relative effort across these disciplines changes over time. Early iterations naturally tend to apply greater relative emphasis to requirements and design, and later ones less so, as the requirements and core design stabilize through a process of feedback and adaptation.
Relating this to the UP phases (inception, elaboration, ...), Figure illustrates the changing relative effort with respect to the phases; please note these are suggestive, not literal. In elaboration, for example, the iterations tend to have a relatively high level of requirements and design work, although definitely some implementation as well. During construction, the emphasis is heavier on implementation and lighter on requirements analysis.
Disciplines and phases
How is the Book Structure Influenced by UP Phases and Disciplines?
With respect to the phases and disciplines, what is the focus of the case studies?
The earlier chapters introduce activities in inception; later chapters explore several iterations in elaboration. The following list and Figure describe the organization with respect to the UP phases.
Book organization is related to the UP phases and iterations
UML Related Interview Questions
|Adv Java Interview Questions||Java collections framework Interview Questions|
|Design Patterns Interview Questions||Rational robot Interview Questions|
|Web semantic Interview Questions||Spring MVC Framework Interview Questions|
|Advanced C++ Interview Questions||Advanced jQuery Interview Questions|
|XML DOM Interview Questions||Object Oriented Analysis and Design Interview Questions|
Object-oriented Analysis And Design
Iterative, Evolutionary, And Agile
Inception Is Not The Requirements Phase
Iteration 1 Basics
System 'sequence Diagrams
Requirements To Design-iteratively
Logical Architecture And Uml Package Diagrams
On To Object Design
Uml Interaction Diagrams
Uml Class Diagrams
Grasp: Designing Objects With Responsibilities
Object Design Examples With Grasp
Designing For Visibility
Mapping Designs To Code
Test - Driven Development And Refactoring
Uml Tools And Uml As Blueprint
Iteration 2 - More Patterns
Quick Analysis Update
Grasp: More Objects With Responsibilities
Applying Gof Design Patterns
Iteration 3 Intermediate Topics
Uml Activity Diagrams And Modeling
Uml State Machine Diagrams And Modeling
Relating Use Cases
Domain Model Refinement
More Ssds And Contracts
Logical Architecture Refinement
More Object Design With Gof Patterns
Designing A Persistence Framework With Patterns
Uml Deployment And Component Diagrams
Documenting Architecture: Uml & The N+1 View Model
More On Iterative Development And Agile Project Management
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.