‹#›
U.S. Department of Transportation
Research and Innovative Technology Administration
Triscallion_Black
From ConOps to Req/Arch
System Architecture
Document
System Requirements Specification
Concept of Operations
Document
•User Needs, Expectations, Constraints
•High Level System Description
•Operational Scenarios
•What – functional requirements, interface definitions
•How Well - performance
•Under What Conditions – environmental, non-functional
•Framework
•Address Stakeholder Concerns
•High-Level System Definition
Not everything is done in the first step (which is where we are); once the concepts for the overall system are captured and agreed upon we can proceed into Requirements and Architecture.  Some of your questions may not be answerable until we get to either the SyRS or Architecture discussions.

System Architecture is sometimes called High Level Design;