Lecture "Software Design Reviews" in Object Oriented Software Engineering course at Beaconhouse National University Lahore for Spring 2017 Semester by Hafiz Ammar Siddiqui

1. Software Design
Reviews
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

2. Software Design Reviews
■ [IEEE] A formal meeting at which a system's preliminary or detailed design is
presented to the user, customer, or other interested parties for comment and
approval
■ Systematic, comprehensive, and well-documented inspection of design
– Check whether the specified design requirements are acceptable
– Examine whether the design meets all the specified requirements
– Identify the problems in the design process
■ Include all artifacts produced as a deliverableof a software
– Design
– Source Code
– Documentation
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

3. Informal Reviews
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

4. Informal Reviews
■ Conducted as needed throughout the development life cycle
■ Lead by the author / developer / designer as one to one discussion with peers
■ Goal is to improvethe qualityof an artifact
■ Not documented or reported
■ Walk through is a method of conducting an informal review
– Author presents the artifact to peers
– Author walks through the artifact
– All peers participate equally in review process
– Peers point out suggestions or defects
– Outcome is not noted or usually hand written
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

5. Formal Technical Reviews
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

6. Formal Technical Reviews
■ Properly planned usually at the end of every development life cycle phase
■ Lead by the manager as a meeting with team
■ Goal is to verify and validatean artifact
■ Very well documented and reported
■ Inspection is a method of conducting a formal review
– Team manager presents the artifact to team
– Team reviews the artifact
– Each team member is assigned a fixed role in review process
– Team members point out suggestions or defects
– Outcome is in the form of a detailed report
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

7. Reference
■ Using UML: Software Engineering with Objects and Components by Perdita Stevens,
Rob Pooley, Addison-Wesley, 2006
FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY