Capstone Project Wiki

User Tools

Site Tools

Trace:
project-wiki:artifacts:requirements_artifacts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
project-wiki:artifacts:requirements_artifacts [2023/08/16 12:40]
mlhicks 		project-wiki:artifacts:requirements_artifacts [2023/08/31 16:02] (current)
mlhicks
Line 4: Line 4:
 The requirements define the expected and actual performance of the product according to both the market and the development team. Expect the requirements to //evolve// as new information is obtained during the product development process. Each stage report submitted by the team must included **updated requirements**. While there are variety of ways for expressing and tracking requirements used by industry, for Capstone the requirements are captured in system and subsystem requirements matrices or the Software Requirements Specification (SRS).  The requirements define the expected and actual performance of the product according to both the market and the development team. Expect the requirements to //evolve// as new information is obtained during the product development process. Each stage report submitted by the team must included **updated requirements**. While there are variety of ways for expressing and tracking requirements used by industry, for Capstone the requirements are captured in system and subsystem requirements matrices or the Software Requirements Specification (SRS). 
  
-See [[..:tools:software_projects|software projects]] for additional guidance when completing requirements for software projects.+See [[..software_projects:home|software projects]] for additional guidance when completing requirements for software projects.
  
 ====Content==== ====Content====
Line 29: Line 29:
  
   * Requirements Matrix: The most succinct summary of the product performance is the requirements matrix. In the opportunity development stage, there is only a single requirements matrix. In later stages, additional requirements matrices for subsystems and components can be created.  The complete set of requirements matrices should be included in the requirements section.  See the Requirements Matrix section of the Product Development Reference for more information on the requirements matrix. A template for the requirements matrix is also available on Learning Suite.  A template file and examples are available on Box. The requirements matrices may be hard to read if printed on standard letter-size paper.  It may be desirable to print the performance matrices on B-size (11 by 17 inch) paper.   * Requirements Matrix: The most succinct summary of the product performance is the requirements matrix. In the opportunity development stage, there is only a single requirements matrix. In later stages, additional requirements matrices for subsystems and components can be created.  The complete set of requirements matrices should be included in the requirements section.  See the Requirements Matrix section of the Product Development Reference for more information on the requirements matrix. A template for the requirements matrix is also available on Learning Suite.  A template file and examples are available on Box. The requirements matrices may be hard to read if printed on standard letter-size paper.  It may be desirable to print the performance matrices on B-size (11 by 17 inch) paper.
-  * Software Requirement Specification:  For [[..tools:software projects]], or software components of mechanical projects, it may be preferable to use a software requirements specification (SRS) instead of a requirements matrix.  For more information on the SRS go to [[..tools:Software Projects]]. +  * Software Requirement Specification:  For [[..software_projects:home|software projects]], or software components of mechanical projects, it may be preferable to use a software requirements specification (SRS) instead of a requirements matrix.  For more information on the SRS go to [[..software_projects:home]]. 
   * Performance Graphs: In many cases, the measured or predicted performance is best represented by a graph rather than by a single number.  In such cases, relevant graphs should be part of the requirements artifacts.  Methods used to obtain the graphs should be part of the test artifacts, and should be cross-referenced here.   * Performance Graphs: In many cases, the measured or predicted performance is best represented by a graph rather than by a single number.  In such cases, relevant graphs should be part of the requirements artifacts.  Methods used to obtain the graphs should be part of the test artifacts, and should be cross-referenced here.
  
  
  
project-wiki/artifacts/requirements_artifacts.1692211231.txt.gz ยท Last modified: 2023/08/16 12:40 by mlhicks

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: Copyright Brigham Young University, all rights reserved
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki