Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

The architecture of the RUP > Artifacts - Pg. 487

Artifacts Artifacts can take various shapes or forms, such as: A model, such as the use-case model or the design model. These contain model elements (sub-artifacts) such as design classes, use cases, and design subsystems. Databases or other types of tabular information repositories such as spreadsheets. Source code and executables. Various types of documents, for example, a specification document, such as the requirements specification, or a plan document, such as the software development plan. Roles A role defines the behavior and responsibilities of an individual, or a set of individuals working together as a team, within the context of a software engineering organization. Note that roles are not individuals; instead, roles describe responsibilities. An individual will typically take on several roles at one time and frequently will change roles over the duration of the project. Activities An activity is work performed by a role. It is usually defined as a series of steps that involve creating or updating one or more artifacts. Some examples of activities are: Find actors and use cases: An activity performed by the system analyst role to identify high-level functional requirements in terms of actors and use cases. Describe distribution: An activity performed by the software architect role to describe software distribution across multiple processors. Workflow and workflow details A process should describe which activities are performed together and the order in which activities are performed. A workflow is a sequence that shows how work is ordered. Appendix C. Rational Unified Process (RUP) overview 487