STATE OF MICHIGAN

STRUCTURED WALKTHROUGH (SWT)

PROCESS GUIDE
A Companion to the Systems Engineering
Methodology (SEM) of the State Unified
Information Technology Environment (SUITE)

Michigan Department of Technology,

Management & Budget
www.michigan.gov/SUITE

October 2014
Version 1.3
 Revision History

REVISION HISTORY

Revision Date Section(s) Summary

April 2009 n/a Initial document release.
Updates for consistent formatting, references to correct PMM and
October 2014 All
SEM forms and department name.

October 1014 State of Michigan Structured Walkthrough (SWT) Process Guide Page i
 Preface

PREFACE
The initial development of the Structured Walkthrough Process Guide was published in August 2007, and was
developed as part of a continuing effort to improve the quality, performance, and productivity of State of
Michigan information systems. Development of the Process Guide was governed by the Michigan State Unified
Information Technology Environment (SUITE) initiative. This update incorporates revisions to the templates
associated with the Structured Walkthrough process.

The purpose of SUITE is to standardize methodologies, procedures, training, and tools for project management
and systems development lifecycle management throughout the Department of Technology Management and
Budget (DTMB) in order to implement repeatable processes and conduct development activities according to
Capability Maturity Model Integrated (CMMI) Level 3 requirements. A formal enterprise level support structure
will be created to support, improve and administer all SUITE components, including the System Engineering
Methodology (SEM), the SMG, the Project Management Methodology (PMM) and related enterprise initiatives.
Until that structure is in place, questions regarding this process guide should be sent to the SUITE Core Team at
SUITE@michigan.gov.

October 1014 State of Michigan Structured Walkthrough (SWT) Process Guide Page ii
 Table of Contents

TABLE OF CONTENTS

REVISION HISTORY ............................................................................................................................. i

PREFACE ........................................................................................................................................... ii
TABLE OF CONTENTS ........................................................................................................................ iii
CHAPTER 1.0 - OVERVIEW ................................................................................................................. 1
Purpose ................................................................................................................................................... 1
Organization ............................................................................................................................................ 1
Description .............................................................................................................................................. 1
General Information ............................................................................................................................... 1
Benefits ................................................................................................................................................... 2
Participants ............................................................................................................................................. 2
Defect Tracking Log................................................................................................................................. 2
Meeting Record ...................................................................................................................................... 3
Implementation ...................................................................................................................................... 3
Note ........................................................................................................................................................ 3
CHAPTER 2.0 – RESPONSIBILITIES BEFORE THE WALKTHROUGH ........................................................ 4
Author's Responsibilities ........................................................................................................................ 4
Presenter's Responsibilities .................................................................................................................... 4
Reviewers’ Responsibilities ..................................................................................................................... 5
Moderator and Scribe Responsibilities .................................................................................................. 5
CHAPTER 3.0 – RESPONSIBILITIES DURING THE WALKTHROUGH ........................................................ 6
Moderator’s Responsibilities .................................................................................................................. 6
Presenter's Responsibilities .................................................................................................................... 7
Scribe's Responsibilities .......................................................................................................................... 7
Reviewers’ Responsibilities ..................................................................................................................... 8
CHAPTER 4.0 – RESPOSIBILITIES AFTER THE WALKTHROUGH ............................................................. 9
Scribe's Responsibilities .......................................................................................................................... 9
Reviewers' Responsibilities ..................................................................................................................... 9
Presenter's Responsibilities .................................................................................................................... 9
Author's Responsibilities ...................................................................................................................... 10
Quality Assurance Manager.................................................................................................................. 10
Project Manager ................................................................................................................................... 10
CHAPTER 5.0 – ADDITIONAL ACTIVITIES AFTER THE WALKTHROUGH ............................................... 12
Preparation of Structured Walkthrough Meeting Record ................................................................... 12
Follow-up Walkthrough ........................................................................................................................ 12
CHAPTER 6.0 – STRUCTURED WALKTHROUGH FOR LIFECYCLE STAGES ............................................. 13
What to Review – Introduction ............................................................................................................ 13
Initiation and Planning Stage ................................................................................................................ 13
Requirements Definition Stage............................................................................................................. 13
Functional Design Stage ........................................................................................................................ 13
System Design Stage ............................................................................................................................. 14
Construction Stage ................................................................................................................................ 14
Testing Stage ......................................................................................................................................... 15

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page iii
 Table of Contents

Implementation Stage .......................................................................................................................... 16

CHAPTER 7.0 – STRUCTURED WALKTHROUGHS FOR OTHER DOCUMENTS ....................................... 17
Types of Documents ............................................................................................................................. 17
Types of verification ............................................................................................................................. 17

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page iv
 Table of Contents

Page inserted for consistency in section start points.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page v
 Chapter 1.0 - Overview

CHAPTER 1.0 - OVERVIEW

Purpose
This process guide describes the method for conducting a Structured Walkthrough (SWT) during the lifecycle
stages of systems engineering projects, regardless of hardware platform.

Organization
This process guide consists of the following sections:

 Overview
 Responsibilities Before the Walkthrough
 Responsibilities During the Walkthrough
 Responsibilities After the Walkthrough
 Additional Activities After the Walkthrough
 Structured Walkthroughs for Lifecycle Stages
 Structured Walkthroughs for Other Documents

Description
A structured walkthrough is an organized procedure for a group of peers to review and discuss the technical
aspects of software development work products. The major objectives of a structured walkthrough are to find
errors and to improve the quality of the product. Errors typically occur as omissions or contradictions, flaws in
logic, or inconsistencies in the work product style (e.g., poorly stated requirements and inefficient code).

Structured walkthroughs should not be used to discuss solutions for the errors that are found. The basic purpose
of a walkthrough is error detection, not error correction. When the walkthrough is completed, the author of the
work product is responsible for taking the necessary actions to correct the errors. The author may hold private
conversations with reviewers or conduct follow-up meetings to discuss potential solutions.

Structured walkthroughs should be conducted during all stages of the system lifecycle. Walkthroughs can be
conducted in various formats, with various levels of formality, and with different types of participants.

In some cases, it might be useful and expedient to include end users in walkthroughs. Management
representatives do not participate in structured walkthroughs. Regardless of the variations in format and
participants, the basic activity (peer review) and the major objectives (find errors and improve quality) of the
structured walkthroughs remain the same.

General Information
Structured walkthroughs are appropriate for reviewing the technical accuracy and completeness of system
development work products, project management tools, and other types of documents (e.g., technical operating

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 1
 Chapter 1.0 - Overview

procedures). The walkthroughs should be scheduled to review small, meaningful pieces of work. The progress
made in each lifecycle stage should determine the frequency of the walkthroughs.

Benefits
Structured walkthroughs provide the following benefits.

 Save time and money by finding and correcting errors earlier in the lifecycle.
 Provide value-added input from reviewers with different technical backgrounds, experience, and
expertise.
 Validate and improve the related lifecycle work products.
 Keep the project team informed of the development progress.
 Provide professional growth to participants by giving them an opportunity to look at different
development methodologies and approaches.

Participants
Each participant in the structured walkthrough process has a specific role. For a small size project, a person may
fulfill multiple roles.

The author of the work product is responsible for requesting the walkthrough when a meaningful portion of the
product has been developed and is free from casual errors (e.g., spelling errors). The author attends the
walkthrough as an observer and answers reviewer's general questions. The author is not a reviewer.

The presenter usually develops the agenda for the walkthrough and presents the work product being reviewed.
The presenter should be familiar with the work product and be a member of the project team.

The moderator facilitates the walkthrough session, ensures that the walkthrough agenda is followed, and
encourages the participation of all reviewers. The moderator may also be the scribe.

The reviewers evaluate the work product to determine if it is technically accurate. The reviewers also assess
whether the project guidelines or standards are being followed, the project requirements are met, and the
product is properly prepared.

The scribe takes notes during the walkthrough. The scribe records the errors identified and any other technical
comments, suggestions, and unresolved questions. The scribe should not be a reviewer.

Defect Tracking Log

The Defect Tracking Log (SEM-0186) is available to assist the reviewers with recording errors found prior to the
walkthrough session. It is an Excel spreadsheet containing five tabs: Defects, User Acceptance Testing,
Production, Analysis, and Summary. Of particular note are the Analysis and Summary tabs.

The Analysis tab contains three pivot tables titled Defect Analysis (total), UAT Defect Analysis, and Production
Defect Analysis. These pivot tables collect data from the previous tabs and generate defect summary information
by:

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 2
 Chapter 1.0 - Overview

Initiation and Planning, Requirements, Functional Design, System

SEM Stage
Design, Construction, Testing and Implementation
Environment, Code, Change of Scope, Cosmetic, Data, Design, and
Defect Type
Performance
Priority Low, Medium, High, and Urgent
New, Open/In progress, Rejected/Re-open, Future Release, Fixed,
Status
Closed, and N/A

The Summary tab summarizes the information from the pivot tables on the Analysis tab: Defect Tally Summary,
UAT Tally Summary, and Production Tally Summary. These summaries provide counts of defects by Status type.
While the N/A and Future Release summary counts are displayed, they are not included in the net defect totals.

A copy of the Defect Tracking Log is available electronically on the DTMB SUITE website. The Defect Tracking Log
has been developed for teams that do not have an acceptable method for recording and tracking defects.

Meeting Record
The Structured Walkthrough Meeting Record (SEM-0187) is completed during the formal SWT meeting to
capture SWT information such as attendees and SWT date information. The Meeting Record is finalized after the
meeting and includes the recording of defect summary totals. The Meeting Record is used during each stage of
the software lifecycle will be checked during the Stage Exit process. The Meeting Record is also used by Quality
Assurance to maintain statistical data on structured walkthroughs. The presenter is responsible for the
preparation of the Structured Walkthrough Meeting Record. A copy of the Structured Walkthrough Meeting
Record is available electronically on the DTMB SUITE website.

Implementation
This procedure describes a formal structure for conducting walkthroughs. The formality and structure of the
walkthrough sessions should be tailored to meet the needs of the development team, and the purpose and
scope of the work product.

Note
The Structured Walkthrough procedure is a Maturity Level 3 Key Process Area of the SEI Software Capability
Maturity Model Integration (CMMI) model.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 3
 Chapter 2.0 - Responsibilities Before the Walkthrough

CHAPTER 2.0 – RESPONSIBILITIES BEFORE THE WALKTHROUGH

Author's Responsibilities
Prior to the walkthrough session, the author of the work product must:

Step Activity
Complete a meaningful segment of a work product. Avoid requesting walkthroughs on
1 incomplete segments or on a segment(s) that is too large to be adequately reviewed in
less than 2 hours.
Proofread work product segment and eliminate non-technical errors such as spelling or
2 typographical mistakes. Non-technical errors can distract reviewers from the technical
aspects of the work product.
Notify the presenter that a completed segment of a work product is ready for a
3 structured walkthrough. May also discuss potential reviewers with the presenter.
Prepare any support materials, such as flow charts, to assist reviewers with their
4 understanding of the entire work product and how the segment being reviewed fits into
the entire product.
Provide the work product and all support materials to the presenter for advance
5 distribution to the reviewers.
When the segment to be reviewed is finished, the author should be prepared to work on
6 other segments of the work product (or other project tasks) while waiting for the
walkthrough to occur.

Presenter's Responsibilities
Prior to the walkthrough session, the presenter must:

Step Activity
Determine if the size of the work product segment is appropriate for one walkthrough
session; walkthrough sessions should not exceed 2 hours in length. If more time is
1 necessary, the work product segment should be divided into smaller portions and each
portion reviewed separately.
Select reviewers who are appropriate for the work product, such as systems analysts,
programmers, technical writers, and testers. Reviewers should include people on and off
the project. In some cases, the participation of software users may be considered
2
desirable. If necessary, the presenter can discuss who should participate in the
walkthrough with the manager of the project team.
Select the moderator and the scribe. Determine whether the scribe will be responsible for
3 completing the Structured Walkthrough Meeting Record (SEM-0187) and the Defect
Tracking Log (SEM-0186).
Schedule the meeting date, time, and location. Notify all participants of these
4 arrangements at least two days prior to the walkthrough.
Establish the agenda. Review the agenda and any important issues with the moderator.
5

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 4
 Chapter 2.0 - Responsibilities Before the Walkthrough

6 Provide reviewers with copies of all materials to be reviewed at least 2 days prior to the
walkthrough.

Reviewers’ Responsibilities
Prior to the walkthrough session, the reviewers must:

Step Activity
Carefully review the materials provided by the presenter. Make a note about the amount
1 of time spent reviewing the material. Give this information to the scribe at the beginning
of the walkthrough session.
Identify technical errors. Insert comments and questions directly on the review materials
2 for easy reference during the walkthrough discussion.
Note directly on the review materials any non-technical errors found during the review,
3 such as spelling or typographical mistakes. While these errors are not discussed during
the walkthrough, they should be provided to the author at the conclusion of the
walkthrough.
Notify the presenter immediately if the reviewer will not be able to complete the review
4 in time for the walkthrough session. An unprepared reviewer will hinder the walkthrough
process. If enough time is available, the presenter can select a new reviewer.
Review the procedures for the structured walkthrough process. Each reviewer should be
5 familiar with the procedures prior to participating in a walkthrough session.

Moderator and Scribe Responsibilities

Prior to the walkthrough session the moderator and the scribe must:

Step Activity
1 Review the materials provided by the presenter to become familiar with the contents.

2 Review the agenda and discuss any questions with the presenter.
Note directly on the review materials any non-technical errors found during the review,
such as spelling or typographical mistakes. While these errors are not discussed during
3 the walkthrough, they should be provided to the author at the conclusion of the
walkthrough.
Review the procedures (ground-rules) for the structured walkthrough process. Clarify
4 specific roles and responsibilities with the presenter. The moderator and scribe should be
familiar with the procedures prior to participating in a walkthrough session.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 5
 Chapter 3.0 - Responsibilities During the Walkthrough

CHAPTER 3.0 – RESPONSIBILITIES DURING THE WALKTHROUGH

Moderator’s Responsibilities
During the walkthrough the moderator is responsible for the following activities:

Step Activity
Call the walkthrough session to order. It is important to start the session at the scheduled
1 time.
Ask participants to introduce themselves and state their current responsibility/job
2 assignment.

3 Briefly review the procedures and agenda for the walkthrough session.
Facilitate the walkthrough session. Every attempt should be made to adhere to the
agenda and the established meeting procedures.

Encourage active participation of all reviewers. Limit discussion to the identification of

errors. The discussion of solutions is not part of the walkthrough process. Limit the
4 author's participation to observation and answering questions.

If the session exceeds 2 hours, the moderator should stop the session at a logical
breaking point and schedule another session to continue the discussion. When
walkthrough sessions exceed 2 hours, the productivity and attention span of the
reviewers will be adversely affected.
At the conclusion of the session, ask the reviewers to make a decision about the status of
the work product as follows:

A = Accept product(s) as presented

B = Acceptable with Revisions – no further walkthrough needed
C = Revise and schedule another walkthrough
5
A majority opinion decides the action. If a majority opinion or consensus cannot be
reached, the presenter will make the decision.

If another walkthrough is necessary, the entire structured walkthrough process should be

repeated.
Adjourn the walkthrough session at the scheduled time. If the agenda has not been
6 completed, schedule a follow-up session.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 6
 Chapter 3.0 - Responsibilities During the Walkthrough

Presenter's Responsibilities
During the walkthrough the presenter is responsible for the following activities:

Step Activity
1 Provide a brief overview of the work product.
2 If necessary, review outstanding issues from previous walkthrough(s).
Present the product to be reviewed. Answer reviewers' questions. The presenter can ask
3
the author for assistance in answering questions.
At the conclusion of the meeting, if the reviewers cannot reach consensus about the
status of the work product, the presenter is responsible for making that decision.

The status will be one of the following:

4
A = Accept product(s) as presented
B = Acceptable with Revisions – no further walkthrough needed
C = Revise and schedule another walkthrough

Scribe's Responsibilities
During the walkthrough the scribe is responsible for the following activities:

Step Activity
1 Record the beginning time for the walkthrough session.
2 Record the attendance of each participant.
3 Record the amount of time each reviewer spent reviewing the work product.
Record the technical errors identified by the reviewers. Record all significant comments
4
and suggestions made by the reviewers and presenter.
5 Record suggested action items and other follow-up activities.
6 Record the end time for the walkthrough session.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 7
 Chapter 3.0 - Responsibilities During the Walkthrough

Reviewers’ Responsibilities
During the walkthrough each reviewer is responsible for the following activities:

Step Activity
1 Provide the scribe with the time spent reviewing the work product.
Provide the appropriate introduction information (e.g., name and current job
2
responsibilities).
Describe technical errors found during review of the work product. Be an active
3
participant.
4 Ask questions as needed to clarify information about the work product.
5 Make constructive suggestions and comments about the work product.
Participate in the decision about the status of the work product:

A = Accept product(s) as presented

B = Acceptable with Revisions – no further walkthrough needed
6
C = Revise and schedule another walkthrough

If consensus cannot be reached by the reviewers, the presenter is responsible for making
the decision.
Inform the author about any non-technical errors found during the review by providing a
7 marked up copy of the review package.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 8
 Section 4.0 - Responsibilities After the Walkthrough

CHAPTER 4.0 – RESPOSIBILITIES AFTER THE WALKTHROUGH

Scribe's Responsibilities
The scribe is responsible for the following activities after the walkthrough:

Step Activity
Prepare the meeting record for the walkthrough session. Include any action items
1 identified by the reviewers and the person/team responsible for completing each action
item.
2 Circulate the meeting record to the participants for their review and comments.
Update the meeting record as needed. Distribute the revised meeting record to the
3 author. Copies of the meeting record should be distributed to the other participants only
if an additional walkthrough is required.

Reviewers' Responsibilities
The reviewers are responsible for the following activities after the walkthrough:

Step Activity
Review the Review the Structured Walkthrough Meeting Record (SEM-0187) and the
1
additions to the Defect Tracking Log (SEM-0186) for accuracy and completeness.
Indicate changes that are needed to add or clarify information in the meeting record.
2
Submit any changes to the scribe. If necessary, discuss discrepancies with the presenter.
If requested by the author of the work product, provide additional explanation of
3
walkthrough comments.

Presenter's Responsibilities
The presenter is responsible for the following activities after the walkthrough:

Step Activity
Review the Review the Structured Walkthrough Meeting Record (SEM-0187) and the
1
additions to the Defect Tracking Log (SEM-0186) for accuracy and completeness.
Indicate changes to the meeting record and return to scribe. If necessary, discuss
2
discrepancies with the reviewers.
Initiate follow-up activities recommended by the reviewers. Verify that all action items
3
have been assigned to the appropriate person/team.
Finalize the Structured Walkthrough Meeting Record. Include the following information:

4  Description of the work product reviewed.

 Description of findings. In addition to findings, include significant problems that
would cause schedule slippage or project cost increase.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 9
 Section 4.0 - Responsibilities After the Walkthrough

 Date, time, and duration of the walkthrough.

 List of attendees.
 Status decision (i.e., accept as is, revise--no further walkthrough, or revise and
schedule another walkthrough) and any other follow-up activities.
Distribute copies of the Structured Walkthrough Meeting Record and the updated Defect
5 Tracking Log to the appropriate management personnel including the Project Manager
and the Quality Assurance Team Manager.
Track progress made on open action items. As action items are closed, indicate closed
6
status on the meeting record.
7 If necessary, schedule a follow-up walkthrough when the revised work product is ready.

Author's Responsibilities
The author is responsible for the following activities after the walkthrough:

Step Activity
1 Make all necessary changes to the work product.
Use the Defect Tracking Log as a checklist to make sure all errors are corrected,
2
reviewer's comments have been addressed, and open issues are investigated.
Check with the presenter and reviewers, as needed, to obtain additional information or
3
clarifications.
Conduct follow-up meetings with subject matter experts, as needed, to complete work
4
product.
5 Prepare work product and participate in follow-up walkthrough, if required.

Quality Assurance Manager

The Quality Assurance Manager is responsible for the following activities after the walkthrough:

Step Activity
Prepare a summary of the information contained in the Structured Walkthrough Meeting
1
Record (SEM-0187) and the Defect Tracking Log (SEM-0186).
Distribute the summary to the Project Manager. The data presented in the report is
2
included in periodic management reports.

Project Manager
The Project Manager is responsible for the following activities after the walkthrough.

Step Activity
1 Review the Structured Walkthrough Meeting Record (SEM-0187) and the Defect Tracking

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 10
 Section 4.0 - Responsibilities After the Walkthrough

Log (SEM-0186).
File the Structured Walkthrough Meeting Record in the project management
2
notebook/files.
Follow up on any action items that remain open. A formal plan may need to be
3
developed for action items that cannot be resolved during the current lifecycle stage.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 11
 Section 5.0 - Additional Activities After the Walkthrough

CHAPTER 5.0 – ADDITIONAL ACTIVITIES AFTER THE WALKTHROUGH

Preparation of Structured Walkthrough Meeting Record
The presenter is responsible for the preparation of the Structured Walkthrough Meeting Record (SEM-0187). The
presenter may ask the scribe to prepare the report. If the scribe prepares the report, the presenter reviews the
report before it is distributed. A copy of the Structured Walkthrough Meeting Record is available at the end of
this process guide and is available electronically on the DTMB SUITE website.

The Meeting Record is distributed to the appropriate project personnel including:

 Project Manager
 Quality Assurance Manager

The Meeting Record and Defect Tracking Log is used by Quality Assurance to maintain statistical data on
structured walkthroughs.

The Structured Walkthrough Meeting Records generated during each stage of the software lifecycle will be
checked during the Stage Exit process. The purpose of the Stage Exit Process Guide check is to verify that
structured walkthroughs were conducted during each lifecycle stage, that the walkthrough action items were
documented, and that the action items have been properly resolved and closed.

Follow-up Walkthrough
If a follow-up walkthrough is required, the procedures used in the original walkthrough should be repeated. Use
the meeting record and defect tracking log from the previous walkthrough as a checklist to confirm that the
previously identified errors and issues were resolved.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 12
 Chapter 6.0 - Structured Walkthrough for Lifecycle Stages

CHAPTER 6.0 – STRUCTURED WALKTHROUGH FOR LIFECYCLE STAGES

What to Review – Introduction
Structured walkthroughs are generally used to review software products or systems under development at
various lifecycle stages. This section describes the work products that should be reviewed at each stage of the
lifecycle. The work products correspond to the deliverables described in the State of Michigan Systems
Engineering Methodology (SEM).

Initiation and Planning Stage

The Initiation and Planning Stage defines the work to be accomplished for a development or maintenance task
and estimates the resources that will be required. During the Initiation and Planning Stage, a structured
walkthrough should be conducted for each deliverable.
Purpose Additional Participants
Review the stage deliverables, such as the The developer and at least one systems
following: analyst, preferably outside the project.

 Project Plan If the project involves sensitive data, include

 Security Plan the Security Liaison from the Office of
 Maintenance Plan, if needed Enterprise Security
 Software Configuration
Management Plan

Requirements Definition Stage

The Requirements Definition Stage determines the scope and requirements for a development project. During
the Requirements Definition Stage, structured walkthroughs are used primarily to identify problems,
inaccuracies, ambiguities, and omissions in the Requirements Specifications.

Purpose Additional Participants

Review the following stage deliverables: One or more of the project designers and at
least one systems analyst.
 Requirements Specification
Document If the project involves sensitive data, include
 Requirements Traceability Matrix the Security Liaison from the Office of
(initial) Enterprise Security.
 Security Plan

Functional Design Stage

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 13
 Chapter 6.0 - Structured Walkthrough for Lifecycle Stages

The Functional Design Stage selects the design elements that determine how the software product will be
constructed to meet the functional requirements. During the Functional Design Stage, the structured
walkthroughs are used to identify flaws, weaknesses, errors, and omissions in the architecture of the design.

Purpose Additional Participants

Review the Functional Design Document, At least one systems analyst and one or
Logical Model, Data Dictionary, more of the project designers/programmers.
Requirements Traceability Matrix and
Security Plan for errors in the following If the project involves or sensitive data,
design areas: include the Security Liaison from the Office
of Enterprise Security.
 Hardware
 Software
 Logical design
 Communications
 System interfaces
 Backup and recovery
 Security
 User interface
 Reports

System Design Stage

The System Design Stage uses the concepts and the system architecture to describe the system components in
detail. During the System Design Stage, structured walkthroughs are used to review detailed specifications, and
plans that address testing and implementation issues.

Purpose Additional Participants

Review the stage deliverables: At least one systems analyst and one or
more of the project designers /
 Physical Model programmers.
 Program Specifications
 System Design Document If the project involves sensitive data, include
 Conversion Plan the Security Liaison from the Office of
 Test Plan (initial) Enterprise Security.
 Test Reports (initial)
 Data Dictionary (revised)
 Requirements Traceability Matrix
(revised)
 Software Configuration
Management Plan
 Security Plan
Construction Stage

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 14
 Chapter 6.0 - Structured Walkthrough for Lifecycle Stages

The Construction Stage involves the construction of the product or solution and the testing that is an integral
part of the construction process. During this stage, walkthroughs are conducted on deliverables such as
programs, test plans, test cases, and the operating documentation.

Purpose Additional Participants

Reviews programs and/or solution Technical personnel with appropriate
components at the completion of a logical expertise and at least two additional
unit of work. Reviews should verify reviewers. The entire programming team
adherence to the following: might attend the walkthrough, depending on
the approach.
 System design
 Program Specifications If the project involves sensitive data, include
 Software Configuration the Security Liaison from the Office of
Management Plan Enterprise Security.

Other deliverables to be reviewed:

 Installation Plan (initial)

 Requirements Traceability Matrix
(revised)
 Test Plan (final)
 Transition Plan
 Operating Documents
 Training Plan (initial)
 Security Plan

Testing Stage
The Testing Stage is the transition from individual software components to an integrated software product.
During the Testing Stage, structured walkthroughs are used to review the integrated product, check the accuracy
of the operating documents that will be provided to the user(s) and programmer(s), and the acceptance
activities.

Purpose Additional Participants

Review the following stage work products: Participants include personnel with
appropriate technical expertise and a
 Integration and System Test technical writer.
Results/Reports
 Programmers Reference Manual If the project involves telecommunications,
 Requirements Traceability Matrix include a representative from the
(final) appropriate functional area.
 Installation Plan (final)
 Training Plan (final) If the project involves sensitive data, include
the Security Liaison from the Office of
Enterprise Security.

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 15
 Chapter 6.0 - Structured Walkthrough for Lifecycle Stages

Implementation Stage
The Implementation Stage is the transition from a product or solution in development to a product or system in
full production status. During the Installation Stage, structured walkthroughs are used to check the Acceptance
Test Report and inspect the plans for activities performed in preparation for full-scale production.

Purpose Additional Participants

Review the following stage deliverables: Participants include personnel with
appropriate technical expertise.
 Installation Test Materials
 User Training Materials If the project involves telecommunications,
 Maintenance Plan (final) include a representative from the
 Transition Plan (final) appropriate functional area.
 Conversion Plan (final)
 Security Plan (final) If the project involves sensitive data, include
 Project Plan (final) the Security Liaison from the Office of
 Post Implementation Evaluation Enterprise Security.
Report (PIER)

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 16
 Section 7.0 - Structured Walkthroughs for Other Documents

CHAPTER 7.0 – STRUCTURED WALKTHROUGHS FOR OTHER DOCUMENTS

Types of Documents
Structured walkthroughs are appropriate for reviewing other types of documents, such as the following:

 Departmental and contractual publications

 Long-range plans
 Administrative and technical operating procedures
 Technical reports
 Presentations

Types of verification

When reviewing other types of documents, structured walkthroughs are used to verify the technical and
editorial accuracy and appropriateness of the content and format

Purpose Participants
Reviews for accuracy including the following: Technical experts, technical writer, and
graphics expert.
 Consistency
 Completeness
 Conformance to standards and
guidelines
 Style
 Grammar and spelling

October 2014 State of Michigan Structured Walkthrough (SWT) Process Guide Page 17