Download Free Templates Websites Templates












Reviewing Checklist



2        Checklist for Architecture Reviews


Readiness Criteria





2.1       Structure




Does the architecture allow for implementation of all of the requirements?




• Has the architecture been adequately decomposed?




• Have the system functions been appropriately allocated to components?




• Does the architecture provide an adequate base for subsequent design work?




• Is the architecture feasible for implementation?




• Have maintainability issues been adequately addressed?




• Can the program set be integrated and tested in an incremental fashion?








2.2       Correctness




• Does the architecture avoid unnecessary redundancy?




• Have all reliability and performance requirements been      addressed?




• Have all security considerations been addressed?




• Does the architecture consider all existing constraints?




• Are all necessary, and only the necessary, data structures   defined?




• Will the proposed architecture satisfy all specified quality attributes and performance goals?








2.3       Standards and Traceability




Have all architecture standards been followed?




• Can all parts of the architecture be traced back to requirements?




• Are standard, not proprietary, components being used wherever possible?









2.4       Logic




Is there any missing or incomplete logic?




Are all possible states or cases considered?








2.5       Interfaces




Are all interfaces clear and well-defined?




• Is the minimum data passed at each interface?




• Is minimum global system data added or impacted?








2.6       Clarity




Is the architecture, including the data flow, control flow, and interfaces, clearly represented?




• Are multiple representations of the design consistent with each other?




• Are all of the decisions, dependencies, and assumptions for this    design documented?






3.  Checklist for Detailed Design Reviews


Readiness Criteria





3.1       Structure




Is the pseudocode or other representation format consistent in       its level of detail?








3.2       Data




Has all the data been properly defined and initialized?




• Is all defined data used?




• Do the data element names and types conform to the project data dictionary?




• Are defaults used, and are they correct?








3.3       Correctness and Completeness




Is the detailed design a complete and accurate implementation of the high-level design?




• Are the external specifications of each module complete and testable?




• Have all numerical techniques been analyzed for accuracy?




• Has critical timing been analyzed?




• Has the high-level design memory budget been expanded into further detail and updated?




• Are all  functions clearly specified and logically independent?




• Have maintainability issues been adequately addressed?




• Does each module have high internal cohesion?




• Does each module have low external coupling?




• Is the detailed design verifiable?




• Is the logic correct, clear, and complete?




• Have all user interfaces been completely designed?





• Can the termination conditions for loops be realized?




• Can all logic be tested?








3.4 Standards and Traceability




• Have all detailed design standards been followed?




• Does the calling protocol follow project standards?




• Can all parts of the detailed design be traced back to the high-level design and to requirements?







Quality Management System (QMS)