1. System Vision Document:
A System Vision document views the <Application Name> system from the stakeholder perspective. The purpose of this document is to define and agree upon the specific solution required to capture <Project Name> data and process.
2.Use Case Survey:
A Use Case Model Survey views the <Application Name> system functionality from the end users perspective. The purpose of this document is to define and agree upon the specific use cases (“functionality”) required to capture <Project Name> data within the <Application Name>.
3. Supplementary Specification:
A Supplementary Specification views the <Application Name> system from the non-functional perspective and captures requirements not covered in either the Software Requirements Specification (SRS) or individual Use Case Specificationsdocuments. The purpose of this document is to define and agree upon the specific solution required to capture <Project Name> data and process.
4. Steel Thread:
Steel Thread is Architecturally Significant Use Cases, Narrow but critical Use Cases that based on Risk, Centrality, Critical Functions of the System from the Customers Point of View.
5.RIO log:
R is risk, things that may happen; I is issue, things that already happened; O is opportunity, things that can make project better.
The purpose of the Risk, Issue and Opportunity (RIO) Management Plan is to document the process of tracking and managing Risks, Issues, and Opportunities. In particular, this document addresses the fundamental terminology, requirements, and functional procedures that are necessary for proper execution of the Risk, Issue, & Opportunity Management processes.
This RIO Management Plan documents the selected RIO management strategies, defines roles and responsibilities, establishes standard approaches including templates and describes the implementation of Risk, Issue, and Opportunity management at
6.SAD:
SAD stands for system architecture document.
This document provides a guideline for developing a System Architecture Document (SAD). It provides guidelines for developing the SAD and addresses how to incorporate activities related to developing the SAD iteratively into project schedule.