لطفا منتظر باشید ...
Artifacts
Each Rational Unified Process activity has associated artifacts, either required as an input or generated as an output. Some artifacts are used to direct input to subsequent activities, kept as reference resources on the project, or generated in a format as contractual deliverables.
Models
Modeling is discussed in Chapter 1 . |
| 1. Business use case model | Establishes an abstraction of the organization |
| 2. Business analysis model | Establishes the context of the system |
| 3. Use case model | Establishes the system's functional requirements |
| 4. Analysis model (optional) | Establishes a conceptual design |
| 5. Design model | Establishes the vocabulary of the problem and its solution |
| 6. Data model (optional) | Establishes the representation of data for databases and other repositories |
| 7. Deployment model | Establishes the hardware topology on which the system is executed as well as the systems concurrency and synchronization mechanisms |
| 8. Implementation model | Establishes the parts used to assemble and release the physical system |
Architecture is discussed in Chapter 2 . |
Other Artifacts
The Rational Unified Process's artifacts are categorized as either management artifacts or technical artifacts. The Rational Unified Process's technical artifacts may be divided into four main sets.
| 1. Requirements set | Describes what the system must do |
| 2. Analysis and design set | Describes how the system is to be constructed |
| 3. Test set | Describes the approach by which the system is validated and verified |
| 4. Implementation set | Describes the assembly of developed software components |
| 5. Deployment set | Provides all the data for the deliverable configuration |
Requirements Set
This set groups all information describing what the system must do. This may comprise a use case model, a nonfunctional requirements model, a domain model, an analysis model, and other forms of expression of the user's needs, including but not limited to mock-ups, interface prototypes, regulatory constraints, and so on.
Design Set
This set groups information describing how the system is to be constructed and captures decisions about how the system is to be built, taking into account all the constraints of time, budget, legacy, reuse, quality objectives, and so forth. This may comprise a design model, a test model, and other forms of expression of the system's nature, including but not limited to prototypes and executable architectures.
Test Set
This set groups information about testing the system, including scripts, test cases, defect-tracking metrics, and acceptance criteria.
Implementation Set
This set groups all information about the elements of the software that comprises the system, including but not limited to source code in various programming languages, configuration files, data files, software components, and so on, together with the information describing how to assemble the system.
Deployment Set
This set groups all information about the way the software is actually packaged, shipped, installed, and run on the target environment.
