Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Leave blank if none exists

Unknown macro: {div}

This is the text which will be hyperlinked, if a link exists

Software Architecture Review Board sub-community of practice.

SWE or Topic

SWE-058, SWE-111, SWE-143, Topic 7.7, Topic 7.07,

This contains additional information, which will appear after the title, separated by a comma

The objectives of SARB are to manage and/or reduce flight software complexity through better software architecture and help improve mission software reliability and save costs.

More specific directions where to look in the resource for relevant content

Example Reference as it will appear to end user:

  1. Title, Citation


Quotes used in SWEs and Topics

“Software architecture should be evaluated concerning the problem it is trying to solve. That's why a project's problem statement is an essential part of review preparation; it describes the problem to be solved and lists success criteria held by various stakeholders. Software architecture should also be evaluated concerning common concerns within its problem domain e.g., flight software...

“During a review, it's important to keep in mind the distinction between software architecture and software architecture description. A system can have great architecture and a poor description, or vice versa, or any of the other two combinations. In a review, it's important to note where each weakness lies: in architecture or description."