SR NWT 002419 : ISSUE 1

1 INTRODUCTION
1.1 Scope of Software Architecture Review
1.2 A Gray Box Approach
1.3 Benefits
1.4 Organization and Audience
2 METHODOLOGY OF SOFTWARE ARCHITECTURE REVIEW
2.1 Stages of Software Architecture Review
2.1.1 Product-Oriented Software Quality Criteria
2.1.2 Checklists
2.1.3 Analysis
2.1.4 Feedback
2.2 Capability Evolution
2.3 Fault Management
2.4 Robustness Improvement
3 CHECKLIST FOR CAPABILITY EVOLUTION
3.1 System Architecture Evoluability
3.2 Software Manageability
3.3 Data Independence
3.4 Interoperability of Releases
4 CHECKLIST FOR FAULT MANAGEMENT
4.1 Fault Prevention
4.2 Fault Detection
4.3 Fault Resolution
5 CHECKLIST FOR ROBUSTNESS IMPROVEMENT
5.1 Failure Mode Characterization and Handling
5.2 Detection of Failures and Overload Conditions
5.3 Recovery from Failures and Overload Conditions
5.4 Containment of Failures and Overload Conditions
5.5 Reporting of Failures and Overload Conditions
6 ACRONYMS
References
LIST OF FIGURES
Figure 1 General Scope of Software Architecture Review
Figure 2 Stages of Software Architecture Review

Presents the Software Architecture Review (SAR) methodology and introduces the SAR checklists. SAR is a product-oriented software system analysis. The checklists are used to collect the software architecture information of a telecommunications system. These checklists include three areas: capability evolution, fault management and robustness improvement. The users of this document will be Bellcore software analysts, BCCs and suppliers' software quality assurance staff and suppliers' software architects and designers.