O. vs. BP. vs. WP. - SYS.3 System Architectural Design ()
O. vs. BP. vs. WP. - SYS.3 System Architectural Design
SYS.3.BP3 Define interfaces of system elements SYS.3.O.3 The interfaces of each system element are defined
SYS.3.BP2 Allocate system requirements SYS.3.O.2 The system requirements are allocated to the elements of the system
SYS.3.BP5 Evaluate alternative system architectures SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system
SYS.3.BP4 Describe dynamic behavior SYS.3.O.4 The dynamic behavior of the system elements is defined
SYS.3.BP1 Develop system architectural design SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system
SYS.3.BP6 Establish bidirectional traceability SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design
SYS.3.BP7 Ensure consistency SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system
SYS.3.BP7 Ensure consistency SYS.3.O.2 The system requirements are allocated to the elements of the system
SYS.3.BP7 Ensure consistency SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design
SYS.3.BP7 Ensure consistency SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties
SYS.3.BP8 Communicate agreed system architectural design SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties
04-06 System architectural design SYS.3.O.1 A system architectural design is defined that identifies the elements ofthe system
04-06 System architectural design SYS.3.O.2 The system requirements are allocated to the elements of the system
04-06 System architectural design SYS.3.O.3 The interfaces of each system element are defined
04-06 System architectural design SYS.3.O.4 The dynamic behavior of the system elements is defined
04-06 System architectural design SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design
13-04 Communication Record SYS.3.O.6 The system architectural design is agreed and communicated to allaffected parties
13-19 Review Record SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design
13-22 Traceability record SYS.3.O.5 Consistency and bidirectional traceability are established between system requirements and system architectural design
17-08 Interface requirements specification SYS.3.O.3 The interfaces of each system element are defined