Cycoda: RUP Glossary

RUP Glossary
	Artifact	Role

	Stakeholder Requests	System Analyst	The Stakeholder Requests contains any type of requests a stakeholder (customer, end user, marketing person, and so on) might have on the system to be developed. It may also contain references to any type of external sources to which the system must comply.
	Vision	System Analyst	The Vision defines the stakeholders view of the product to be developed, specified in terms of the stakeholders key needs and features. Containing an outline of the envisioned core requirements, it provides the contractual basis for the more detailed technical requirements.
	Business Case	Project Manager	The Business Case provides the necessary information from a business standpoint to determine whether or not this project is worth investing in. For a commercial software product, the Business Case should include a set of assumptions about the project and the order of magnitude return on investment (ROI) if those assumptions are true. For example, the ROI will be a magnitude of five if completed in one year, two if completed in two years, and a negative number after that. These assumptions are checked again at the end of the Elaboration phase, when the scope and plan are defined with more accuracy.
	Risk List	Project Manager	A sorted list of known and open risks to the project, sorted in decreasing order of importance and associated with specific mitigation or contingency actions.
	Glossary	System Analyst	The Glossary defines important terms used by the project.
	Software Requirements Specification		The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system. When using use-case modeling, this artifact consists of a package containing use cases of the use-case model and applicable Supplementary Specifications.
	Supplementary Specifications	System Analyst	The Supplementary Specifications capture the system requirements that are not readily captured in the use cases of the use-case model. Such requirements include: Legal and regulatory requirements, and application standards Quality attributes of the system to be built, including usability, reliability, performance, and supportability requirements Other requirements such as operating systems and environments, compatibility requirements, and design constraints
	Use-Case Model	System Analyst	The use-case model is a model of the system's intended functions and its environment, and serves as a contract between the customer and the developers. The use-case model is used as an essential input to activities in analysis, design, and test.
	Software Development Plan	Project Manager	The Software Development Plan is a comprehensive, composite artifact that gathers all information required to manage the project. It encloses a number of artifacts developed during the Inception phase and is maintained throughout the project.
	Analysis Model	System Analyst	An object model describing the realization of use cases, and which serves as an abstraction of the Artifact: Design Model. The Analysis Model contains the results of use case analysis, instances of the Artifact: Analysis Class. The Analysis Model is an optional artifact.
	Design Model	Software Architect	The design model is an object model describing the realization of use cases, and serves as an abstraction of the implementation model and its source code. The design model is used as essential input to activities in implementation and test.
	Implementation Model	Software Architect	The implementation model is a collection of components, and the implementation subsystems that contain them. Components include both deliverable components, such as executables, and components from which the deliverables are produced, such as source code files.
	Software Architecture Document	Software Architect	The Software Architecture Document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system.
	Test Plan	Test Manager	The definition of the goals and objectives of testing within the scope of the iteration (or project), the items being targeted, the approach to be taken, the resources required and the deliverables to be produced.
	Deployment Plan	Deployment Manager	The Deployment Plan describes the set of tasks necessary to install and test the developed product such that it can be effectively transitioned to the user community.