This is part 1 of the following series:

  1. Originating requirements (this document)
  2. Use cases
  3. Product requirements specification
  4. Physical architecture and interfaces

The document catches all of the wish lists from all stackholders. To contribute more contents, review and link each item to the "internal" system model.

How to use this document

The document is created as a catch-all for capturing and sorting through all of the supplied desires. Typically included are stakeholder requirements, user needs, and a myriad of other inputs.

System engineering V-model. Originating requirements captures the high-level requirements from all stakeholders. Those will be internalized in the System-level requirements.

The first step is to import all of the input content into the requirement tracking database. Many word processing tools have a utility that can help with this step. Once the originating requirements have been captured within the database, the requirements trace begins. Originating requirements can trace to use cases, system requirements, and interfaces. These items were selected to capture the behavior (use cases), constraints and performance (system requirements), and interfaces (interfaces) which are typically contained in input documentation. Each originating requirement is systematically considered, and then traced to relevant item(s).

Some originating requirements are not traced to anything or are traced to an item that doesn't exactly match – this is part of the requirement analysis process that determines which stakeholder requirements take precedence, and which will not be included in the current project. During this process, the lower level items do not need to be fully defined – that will occur in the next phase – in some cases a placeholder for further definition is sufficient.

After the trace is complete, the Originating Requirements Trace document is output. This document shows the originating requirement, and each item it has been traced to. All of the redundant, contradictory, and impossible originating requirements are output along with those that are logically traced. This creates the discussion when, for example, stakeholders see an originating requirement for a red product traced to a system requirement for a blue product.

Trace all system requirements and specifications back to the orignating requirements.

Once the trace has been agreed to, the originating requirements are set aside, and the focus is solely on the system requirements. In certain industries, such as medical, the originating requirements will need to be updated to ensure that they are coherent and traceable.

org-1: Charging

A user should be able to quickly charge the device with a cell phone charger.