1. Team #TBD Member1, Member2, Member3, Member4 [Alphabetical]
Code Inspection
Units and Subsystems
[10 to 12 Diagram Content Slides Please! – Move Less Critical Slides to Backup Section]
11/12/2018
 Embry Riddle Prescott

2. Inspection Outline – One Page
Requirements Summary
Requirements Validation Methods - E.g. Walk-through, Acceptance Test
Requirements Metrics (See P. 475 OOSE)
Unambiguity, Completeness, Correctness, Consistency
Acceptance Test Plan Traced to Requirements
Design Overview
Block Diagram
Models of Importance to Units and Subsystems [OO, SA/SD]
# Modules, Lines of Code, Cohesion [6=weak, 0=strong] and Coupling Levels by Module [6=tight, 0=loose] – see Functional and Message/No coupling is “0,0” – perfect low value
Code Unit CSU Reviews
Unit Test Cases and Results [Coverage, Profiles, Negative]
Inspection Questions (Review Source as Requested)
I&T Subsystem CSCI Reviews
CSCI Test Cases and Results [Performance, Soak, Stress, Negative, Regression % PASS/FAIL]
Inspection Questions (Review Interfaces as Requested)
Final Bug, Release Notes, and CMVC Report
Bug Status (# Open, # Closed), Statistics (Total Bugs over Time), Commit Profile
Release Notes (Issues unresolved that impact end users)
 Embry Riddle Prescott

3. Capability Requirements - #1
Metrics
 Embry Riddle Prescott

4. System/Functional Requirements - #2
System Requirement #1
System Requirement #2
Metrics
 Embry Riddle Prescott

5. Performance Requirements - #3
Metrics
 Embry Riddle Prescott

6. Acceptance Test to Requirements - #4
Requirement – Test
Table or List
 Embry Riddle Prescott

7. System Block Diagram – Design #1
Any Useful Information about System
Keep it Simple – One Page View of Everything
Users, IT, Software, External Systems and Hardware
Software System Service, Task, Process, etc.
Hardware or Other System External Entity
I/O label
I/O label
I/O label
End Users
I/O label
Cloud Service
System Administration
 Embry Riddle Prescott

8. UML OO Models – That Apply
Class, Component, Package, Deployment, State Machine for Units
OIM and Activity for I&T
Use Case for Test Cases and Drivers
Use Case for Acceptance Testing
 Embry Riddle Prescott

9. Key SA/SD Models – Design Overview #2
CFD/DFD - Transformation/Even-Driven
ER/EER - Information Model
State Machine – Behavioral
Flow-Charts – Detailed Procedural
CFD/DFD
ER/EER
SM/EFSM
Flowchart
 Sam Siewert

10. CSU #1 – Owner Identified
Unit Test Cases and Results [Coverage, Profiles, Negative]
Inspection Questions (Review Source as Requested)
 Embry Riddle Prescott

11. CSU #N – Owner Identified
Unit Test Cases and Results [Coverage, Profiles, Negative]
Inspection Questions (Review Source as Requested)
 Embry Riddle Prescott

12. CSCI #1 – Owner Identified
CSCI Test Cases and Results [Performance, Soak, Stress, Negative, Regression % PASS/FAIL]
Inspection Questions (Review Interfaces as Requested)
 Embry Riddle Prescott

13. CSCI #N – Owner Identified
CSCI Test Cases and Results [Performance, Soak, Stress, Negative, Regression % PASS/FAIL]
Inspection Questions (Review Interfaces and Code as Requested)
 Embry Riddle Prescott

14.  Embry Riddle Prescott 14
System Test Readiness
Final Bug Report
Bug Status (# Open, # Closed) – Count and Summary Page
Statistics (Total Bugs over Time) – Chart with Coverage Metrics Overlay
CMVC Report
Commit Profile over Time by Owner
Current Tagged Revision Candidate for System Test
Final Release Notes
List of unresolved issues that impact end users
Limitations for use
Key Constraints (expected and unexpected)
 Embry Riddle Prescott

15. Summary Thank Audience Encourage Submission of Deficiency Sheets
Open to Q&A for 10 Minutes
 Sam Siewert

16. Move Slides Not Making MUST PRESENT Status to HERE for Q&A
Backup Slides
Move Slides Not Making MUST PRESENT Status to HERE for Q&A
 Embry Riddle Prescott