Software Design Reviews

FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

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 andapproval

■ 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 deliverable of a software– Design– Source Code– Documentation

FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

Informal Reviews

FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

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 improve the quality of 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

Formal Technical Reviews

FROM: HAFIZ AMMAR SIDDIQUI – COURSE: OBJECT ORIENTED SOFTWARE ENGINEERING – INSTITUTE: BEACONHOUSE NATIONAL UNIVERSITY

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 validate an 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

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