USC
C
S E
University of Southern California
Center for Software Engineering
PWP Demonstration
System Descriptions to the "Elevator Test"
© 2003 USC Center for Software Engineering
533576739 – 1 of 24
v 0.4 04/02/00
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Goals of Presentation
You should get a working overview of the Personal Writing
Process applied to the description of a system that passes
the "elevator test"
 Exposure to process and forms for PWP
© 2016 USC Center for Software Engineering
533576739 – 2 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
The "Elevator Test"
The “elevator test” is described in Geoffrey Moore’s Crossing
the Chasm (Harper Collins, 1991, p.161). This would enable
you to explain to an executive while riding up or down an
elevator why the system should be built. It should address
the following points:
 For <target customer>
 Who <statement of the need or opportunity>
 The <product name> is a <product category>
 That <statement of key benefit-that is, compelling reason to buy>
 Unlike <primary competitive alternative>
 Our product <statement of primary differentiation>
© 2016 USC Center for Software Engineering
533576739 – 3 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
The "Elevator Test"
An example for a corporate order-entry system:
“Our sales people need a faster, more integrated
order entry system to increase sales. Our proposed
Web Order system would give us an e-commerce
order entry system similar to Amazon.com’s that will
fit the special needs of ordering mountain bicycles
and their aftermarket components. Unlike the
template-based system our main competitor bought,
ours would be faster, more user friendly, and better
integrated with our order fulfillment system.”
© 2016 USC Center for Software Engineering
533576739 – 4 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Super Hello World
Generates a time-stamped "Hello World" message to
sent to at least the following devices/outputs.
 A Printer
 An the monitor
 An HTML page?
 An email to a user whose email address is entered via the
keyboard?
The objective of this "elevator test" system description
is to get approval from an executive to use one person
day's effort to generate, test and package the program.
© 2016 USC Center for Software Engineering
533576739 – 5 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Outline
Elevator Test and System
PWP Process and Artifacts
Apply PWP to "Super Hello World" System Description
© 2016 USC Center for Software Engineering
533576739 – 6 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Process Flow
PPMP0 Process Flow
Requirements
Planning
Plan
Design
AKA Outline
Write
Results
Scripts
Logs
Check
Test
Plan
Summary
Time
Defects
Postmortem
Project and Process Data
Summary Report
Finished Product
© 2016 USC Center for Software Engineering
533576739 – 7 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0s' Project Plan Summary
© 2016 USC Center for Software Engineering
533576739 – 8 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWPs' Time Recording Log
© 2016 USC Center for Software Engineering
533576739 – 9 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWPs' Defect Recording Log
© 2016 USC Center for Software Engineering
533576739 – 10 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0s' Process Decomposition
PWP0s' Process
Decomposition
Requirements
Planning
Development
Outline
Write
Check
Test
Postmortem
Finished Product
Project and Process Data
Summary Report
© 2016 USC Center for Software Engineering
533576739 – 11 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Process Script
 Purpose
To Guide you in developing module-level spreadsheets
 Problem description
Inputs
Required  PWP0 Project Plan Summary form
 Time and Defect Recording Logs
 Defect Type Standard
 Stop watch (optional)
1. Planning
2. Development
3. PM







Produce [or obtain] a requirements statement.
Estimate the writing time.
Enter the plan data [estimate] in the Project Plan Summary form.
Complete the Time Recording Log.
Outline the document.
Write the document; No AutoCorrect; Hide errors while typing.
Spell and grammar check the document: fix and log all defects found; record
readability statistics
 Proof read the document, fix and log all defects found; record final
readability statistics
 Complete the Time Recording Log.
Complete the Project Plan Summary form with actual time, defect, and size data
 A thoroughly tested spreadsheet
Exit
Condition  Completed Project Plan Summary with estimated & actual data
 Completed Defect and Time Recordings Logs
© 2016 USC Center for Software Engineering
533576739 – 12 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Planning Process Script
 Purpose



Document 

Rqts


Estimate
Entry
Condition
1.
2.
To guide the PSSP & PSP planning process
Resources
Exit
Condition
Problem description
PWP0 Project Plan Summary form
Time Recording Log
Produce or obtain a requirements statement for the document
Ensure the requirements statement is clear and unambiguous.
Resolve any questions.
Make your best estimate of the time required to develop this
document.
 Documented requirements statement
 Project Plan Summary with estimated document development
time data
 Completed Time Recording Log
© 2016 USC Center for Software Engineering
533576739 – 13 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Development Process Script
 Purpose
To guide the development of small spreadsheets
 Requirements statement  Time and Defect Recording Logs
Entry
condition  Project Plan Summary with estimated writing time
 Defect Type Standard
 Review the requirements and produce a design in the form of an
1. Outline
annotated outline to meet them.
 Record in the DRL any requirements found.
 Record time in Time Recording Log.
 Implement the design: automatic calculation off & formula mode.
2. Write
 Record in the DRL any requirements or design defects found.
 Record time in Time Recording Log.
 Spell and grammar check the document until error free
3. Check
 Fix all defects found. ● Record readability statistics
 Record defects in Defect Recording Log.
 Record time in Time Recording Log.
© 2016 USC Center for Software Engineering
533576739 – 14 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Development Process Script (cont.)
 Print-out and proof-read the document  Fix all defects found.
 Record defects in Defect Recording Log.
 Re-check the document (spelling and grammar); record
readability statistics
 Record time in Time Recording Log.
 Thoroughly tested document
Exit
condition  Completed Defect Recording Log
 Completed Time Recording Log
4. Test
© 2016 USC Center for Software Engineering
533576739 – 15 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Postmortem Process Script

1.
2.
3.
To guide the PPMP & PSP postmortem process
 Problem description and requirements statement
Entry
 Project Plan Summary with planned document size and
Condition
development time
 Completed Defect Recording Log  Completed Time
Recording Log
 A tested and and acceptable document
 Determine from the DRL the number of defects injected in
Defects
each phase.
Injected
 Enter this number under Defects Injected—Actual on the PPS.
 Determine from the Defect Recording Log the number of
Defects
defects removed in each PWP0 phase.
Removed  Enter this number under Defects Removed—Actual on the
Project Plan Summary.
 Review the completed Time Recording Log.
Time
 Enter the total time spent in each PWP phase under Actual on
the Project Plan Summary form.
 A fully tested document
Exit
 Completed Project Plan Summary form
Condition  Completed Defect and Time Recording Logs
Purpose
© 2016 USC Center for Software Engineering
533576739 – 16 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Watts' Process Elements
Software & Project Management Process Elements
 Defined scripts to guide in performing the tasks
 A set of
 forms
 templates
 instructions
for
 planning
 tracking
 recording
 An improvement procedure, with process
improvement proposal (PIP) forms and facilities
© 2016 USC Center for Software Engineering
533576739 – 17 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Outline
Elevator Test and System
PWP Process and Artifacts
Apply PWP to "Super Hello World" System Description

Step hints

Audience=?

What steps to drop

Persuasive or discriptive sentences

Re-arrange outline points
© 2016 USC Center for Software Engineering
533576739 – 18 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWPs' Process Time Recording Log
Student
Instructor
Date
Spreadsheet #
Date Start Stop Interruption Delta Phase Comments
Time
Time
© 2016 USC Center for Software Engineering
533576739 – 19 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Project Plan Summary
Student
Spreadsheet
Instructor
Date
Spreadsheet #
Language
Time in Phase (min.) Plan
Planning
Outline
Write
Check
Test
Postmortem
Total
© 2016 USC Center for Software Engineering
Actual
533576739 – 20 of 24
To Date To Date %
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Requirements Statement
<students provide>
© 2016 USC Center for Software Engineering
533576739 – 21 of 24
v1.0 - 03/07/16
USC
C
University of Southern California
S E
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWPs' Defect Recording Log
10 Spelling 20 Typographic 30 Punctuation 40 Diction
60 Sentence 70 Reasonable 80 Effective
90 Larger
sense
sentences
sentences
elements
Student
Instructor
Date
Number
50 Grammar
100 Intended
audience
Date
Spreadsheet #
Type
Inject
Remove
Fix Time
Fix Defect
Type
Inject
Remove
Fix Time
Fix Defect
Description:
Date
Number
Description:
© 2016 USC Center for Software Engineering
533576739 – 22 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
PWP0 Project Plan Summary (cont.)
Defects Injected
Planning
Outline
Write
Check
Test
Total Development
Actual
To Date
To Date %
Defects Removed
Planning
Outline
Write
Check
Test
Total Development
After Development
Actual
To Date
To Date %
© 2016 USC Center for Software Engineering
533576739 – 23 of 24
v1.0 - 03/07/16
USC
C
S E
University of Southern California
PWP Demonstration – System Descriptions to the "Elevator Test"
Center for Software Engineering
Next Session
© 2016 USC Center for Software Engineering
533576739 – 24 of 24
v1.0 - 03/07/16