Generally, we maintain as less document as possible according to our agile methodology when considering project type, client’s request, etc. It enables us to focus more on working software instead of document.
| Document |
Description |
| Software Development Plan |
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 early phase of the project and is maintained throughout the project. |
| Risk Management Plan |
The Risk Management Plan details how to manage the risks associated with a project. It details the risk management tasks that will be carried out, assigned responsibilities, and any additional resources required for the risk management activity. On a smaller scale project, this plan may be embedded within the Software Development Plan. |
| Configuration Management Plan |
The Configuration Management (CM) Plan describes all Configuration and Change Control Management (CCM) activities that are performed during the course of the product or project lifecycle. It details the schedule of activities, the assigned responsibilities, and the required resources, including staff, tools, and computer facilities. |
| Quality Assurance Plan |
The Quality Assurance Plan is an artifact that provides a clear view of how product, artifact, and process quality are to be assured. It contains the Review and Audit Plan, and references a number of other artifacts developed during the Inception phase. It is maintained throughout the project. |
| Iteration Plan |
A time-sequenced set of activities and tasks, with assigned resources, containing task dependencies, for the iteration; a fine-grained plan. |
| Test Plan |
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. |
| Test Evaluation Summary |
The Test Evaluation Summary organizes and presents a summary analysis of the Test Results and key measures of test for review and assessment, typically by key quality stakeholders. In addition, the Test Evaluation Summary may contain a general statement of relative quality and provide recommendations for future test effort. |
| Use Case Model |
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. |
| Supplementary Specification |
The Supplementary Specification artifact capture system requirements that are not readily captured in behavioral requirements artifacts such as use-case specifications. |
| Requirement Management Plan |
Describes the requirements artifacts, requirement types, and their respective requirements attributes, specifying the information to be collected and control mechanisms to be used for measuring, reporting, and controlling changes to the product requirements. |
| Software Architecture Document |
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. |
| Design Model |
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. |
| Review Record |
Created to capture the results of a review activity in which one or more project artifacts are reviewed. |
| Project Specific Guideline |
Project-Specific Guideline provides prescriptive guidance on how to perform a certain activity or a set of activities in the context of the project. The guidelines selected for the project are seen as a part of the development process for this project, also known as the Project-Specific Process.Project Specific Guideline may include Design Guidelines, Programming Guidelines, Test Guidelines, and so forth. |
To learn more about Shinetech's documentation levels, please
download:
