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