Small Project Development Case : Artifacts


Table of Contents - Introduction - General Tailoring - Project Lifecycle - Inception - Elaboration - Construction - Transition - Artifacts	This section of the development case lists the artifacts that are part of the process, along with guidance on the tools used to create them, comments (which may include tailoring), and whether or not the artifact is a formal deliverable. Formal deliverables are provided to the customer and must be approved by the customer. Other artifacts are project-internal. Topics (on this page) - Requirements - [Analysis & Design](#Analysis & Design) - Implementation - Testing - Deployment - [Configuration & Change Management](#Configuration & Change Management) - [Project Management](#Project Management) - Environment

Table of Contents - Introduction - General Tailoring - Project Lifecycle - Inception - Elaboration - Construction - Transition - Artifacts

This section of the development case lists the artifacts that are part of the process, along with guidance on the tools used to create them, comments (which may include tailoring), and whether or not the artifact is a formal deliverable. Formal deliverables are provided to the customer and must be approved by the customer. Other artifacts are project-internal. Topics (on this page) - Requirements - [Analysis & Design](#Analysis & Design) - Implementation - Testing - Deployment - [Configuration & Change Management](#Configuration & Change Management) - [Project Management](#Project Management) - Environment

Requirements

Workflow

For details on the workflow, see the Requirements Overview.

Artifacts


Artifact	Tools Used	Comments	Formal Deliverable?
Vision	Rational RequisitePro, Microsoft® Word®		Yes
Stakeholder Requests	Rational ClearQuest	Stakeholder requests are logged and managed as Rational ClearQuest Change Requests.	No
Use-Case Model (Actors, Use Cases)	Rational Rose, Rational RequisitePro	Important actors and use cases identified and flows of events will be outlined for only the most critical use cases. Descriptions will be captured as Word documents.	No (however the Use-Case Survey report is deliverable)
Glossary	Rational RequisitePro		Yes
Supplementary Specifications		Captured as part of the Vision document.	Yes
User Interface Prototype			No

Reports

The following reports are generated from the Use-Case Model.


Report	Tools Used	Formal Deliverable?
Use-Case Survey	Rational Soda	Yes

Analysis & Design

Workflow

For details on the workflow, see the Analysis & Design Overview.

Artifacts


Artifact	Tools Used	Comments	Formal Deliverable?
Architectural Proof of Concept, Prototypes		Project risks will be addressed as early as possible using executable architectural prototypes.	No
Design Model (and all constituent artifacts)	Rational Rose	The Design Model is expected to evolve over a series of brainstorming sessions. No separate Analysis Model is created. The Design Model will only be maintained as long as the developers find it useful.	No
Data Model	Rational Rose		No
Software Architecture Document	Rational Soda, Microsoft Word	A description of the architecture will be captured that briefly describes the architecturally significant use cases (use-case view), identification of key mechanisms and design elements (logical view), plus definition of the process view and the deployment view.	Yes

Implementation

Workflow

For details see the Implementation Overview. This project is small enough that no separate subsystem integration is performed (elements are directly integrated into the overall system). High level integration planning is described in the project schedule. Detailed integration planning is done informally and as-needed.

Artifacts


Artifact	Tools Used	Comments	Formal Deliverable?
Implementation Model (and all constituent artifacts, including Implementation Elements and Builds)	<development tools - compiler, debugger, and so on> Rational Rose, Rational Test Manager, Rational Test Factory, Rational Robot, Rational PurifyPlus .	Rational Rose will be used to generate the initial code. Unit Tests will be scripted using Rational Robot and organized into suites using Rational Test Manager. Scripts generated by Rational Test Factory will supplement hand-generated tests. Rational PurifyPlus will be used to help determine if component testing is adequate.	Yes


Artifact	Tools Used	Comments	Formal Deliverable?
Test Plan	Microsoft Word		No
Test Script, Test Data	Rational QualityArchitect, Rational Test Factory, Rational Robot, Rational PurifyPlus,<database tool used by the application>	User Interface (UI) component test scripts and test data are created using Rational Robot and Rational Test Factory. Non-UI components test scripts and test data are created using Rational QualityArchitect.	No
Test Suite, Test Log	Rational Test Manager	Rational Test Manager is used to create Test Suites and execute them to produce Test Logs and reports.	No
Test Ideas List	Microsoft Word	These will primarily be harvested from previous projects.	No
Test Case	Rational Test Manager		No
Test Evaluation Summary	Microsoft Word		No
Test Environment Configuration	Microsoft Word	Documented informally.	No.


Artifact	Tools Used	Comments	Formal Deliverable?
Product (including Deployment Unit and Installation Artifacts)			Yes
End-User Support Material (including Release Notes)		Are built into the online help.	Yes


Artifact	Tools Used	Comments	Formal Deliverable?
Change Request	Rational ClearQuest		No
Project Repository, Workspace	Rational ClearCase LT		No


Artifact	Tools Used	Comments	Formal Deliverable?
Business Case	Microsoft Word	The business case is produced and approved by company management. It is not expected to be maintained.	No
Software Development Plan (including Risk List, and Iteration Plan)	Microsoft Word, Microsoft® Project®	The schedule and resource information will be generated as reports out of Microsoft Project.	No
Review Record	Microsoft Word	This is mandatory and deliverable only for customer reviews.	Yes
Iteration Assessment, Status Assessment	Microsoft Word, email	Status Assessment is be combined with the Iteration Assessment because the iterations are frequent (one or more each month). The Project Manager will meet with each project team member on a weekly basis to determine progress, and help identify and resolve issues. At the end of each iteration, the team will meet to discuss the project status and brainstorm improvements. The intent is to capture lessons learned. This is followed by a review with the Management Reviewer.	No


Artifact	Tools Used	Comments	Formal Deliverable?
Development Case	[HTML editor]	This project Development Case was created by minor tailoring of the RUP Example Development Case For Small Projects.	No
Use-Case Modeling Guidelines	Microsoft Word	This project follows the RUP Example Use-Case Modeling Guidelines without further tailoring.	No
Programming Guidelines	Microsoft Word	The Programming Guidelines for the project already exist. They are a slightly tailored version of the example provided in RUP.	No
Design Guidelines	Microsoft Word	The Design Guidelines for the project already exist (harvested from a similar, previous project).	No
Test Guidelines	Microsoft Word	The Test Guidelines for the project already exist (harvested from a similar, previous project).	No
User Interface Guidelines	Microsoft Word	The User Interface Guidelines for the project already exist (harvested from a similar, previous project).	No

Keyboard shortcuts

Rational Unified Process - Complete Reference