Requirements Requirements DocumentDocument

Work Breakdown StructureWork Breakdown Structure

ScheduleScheduleDate Tooic Assignment

1-Oct-08 work breakdown/features breakdown

8-Oct-08 agile methods requirements doc

15-Oct-08 acceptance criteria feature breakdown

22-Oct-08 testing - unit, tdd, design review

29-Oct-08 Student Presentations Student Presentations

5-Nov-08 Student Presentations Student Presentations

12-Nov-08 Student Presentations Student Presentations

19-Nov-08 DemosDemos Demos

26-Nov-08 Thanksgiving Break Thanksgiving Break

3-Dec-08 Code reviewCode review code review

10-Dec-08 last day of instruction

Requirements DocumentRequirements Document DDJ – “Quick-kill Project DDJ – “Quick-kill Project

Management”Management” Problem StatementProblem Statement

Project backgroundProject background StakeholdersStakeholders End-usersEnd-users

Vision and ScopeVision and Scope Vision statementVision statement List of featuresList of features List of features that will NOT be List of features that will NOT be

developeddeveloped

Problem StatementProblem Statement Project backgroundProject background

summary of the problem that the project solves. summary of the problem that the project solves. a brief history of the problem a brief history of the problem an explanation of how the organization justified an explanation of how the organization justified

the decision to build software to address itthe decision to build software to address it why the problem existswhy the problem exists the organization's history with this problemthe organization's history with this problem any previous projects that were undertaken to any previous projects that were undertaken to

try to address ittry to address it the way that the decision to begin this project the way that the decision to begin this project

was reachedwas reached

Problem StatementProblem Statement

Stakeholders – list of stakeholdersStakeholders – list of stakeholders Individuals within the client Individuals within the client

organization that have a vested interest organization that have a vested interest in the outcomein the outcome

Name, title or roleName, title or role UsersUsers

Name, title or roleName, title or role OR “the end users are individuals with OR “the end users are individuals with

an interest in…”an interest in…”

Vision and ScopeVision and Scope

Vision statementVision statement A description of the goal of the softwareA description of the goal of the software How does it fulfill the needs of the How does it fulfill the needs of the

client or users?client or users?

Vision and ScopeVision and Scope

List of featuresList of features List of features or functionality that List of features or functionality that

will NOT be developedwill NOT be developed concise list of exactly what will and concise list of exactly what will and

won't be built won't be built

WBSWBS

What is it?What is it? Why do we need it?Why do we need it? Are we going to get graded on this?Are we going to get graded on this?

What is it?What is it?

In software development, this is a In software development, this is a “feature breakdown structure”.“feature breakdown structure”.

Feature-by-feature catalog and Feature-by-feature catalog and descriptiondescription

A comprehensive classification of A comprehensive classification of project scope, not an exhaustive list project scope, not an exhaustive list of workof work

Why do we need it?Why do we need it?

To document agreement with clientTo document agreement with client To provide a define the scope of the To provide a define the scope of the

project clearly for the team and the project clearly for the team and the clientclient

Aids in planningAids in planning EstimationEstimation Assigning responsibilityAssigning responsibility

It is considered poor practice to develop a It is considered poor practice to develop a schedule without first designing a WBSschedule without first designing a WBS

Are we going to be graded Are we going to be graded on this?on this?

YesYes The way you are graded is pass/fail The way you are graded is pass/fail

on this section. If you turn in on this section. If you turn in documents without this they will be documents without this they will be returned to you for revision.returned to you for revision.

WBSWBS(wikipedia)(wikipedia)

100% Rule100% Rule Planned outcomes, not planned Planned outcomes, not planned

actionsactions Mutually exclusive elementsMutually exclusive elements

100% Rule100% Rule

Represents all of the work defined Represents all of the work defined by projectby project

Includes all deliverablesIncludes all deliverables Applies to all levels of the hierarchyApplies to all levels of the hierarchy

Planned outcome, not Planned outcome, not planned actionsplanned actions

(Unless an action is a deliverable)(Unless an action is a deliverable)

Mutually Exclusive Mutually Exclusive ElementsElements

When breaking down the tasks, it is When breaking down the tasks, it is important that nothing appears on important that nothing appears on the WPS more than oncethe WPS more than once

WBSWBS

User interfaceUser interface Business logicBusiness logic DatabaseDatabase

WBSWBS User interfaceUser interface

User Log-in pageUser Log-in page Account summary pageAccount summary page Pay billsPay bills

Business logicBusiness logic Combine database table data for summaryCombine database table data for summary Generate data for presentationGenerate data for presentation

DatabaseDatabase Table designTable design Query designQuery design

WBSWBSNumberingNumbering

1.0 User interface1.0 User interface 1.1 User Log-in page1.1 User Log-in page 1.2 Account summary page1.2 Account summary page 1.3 Pay bills1.3 Pay bills

2.0 Business logic2.0 Business logic 2.1 Combine database table data for summary2.1 Combine database table data for summary 2.2 Generate data for presentation2.2 Generate data for presentation 2.3 Record transactions2.3 Record transactions 2.4 User verification2.4 User verification

3.0 Database3.0 Database 3.1 Table design3.1 Table design 3.2 Query design3.2 Query design

GranularityGranularity

How far do you continue this How far do you continue this process?process? Too fine = MicromanagementToo fine = Micromanagement Too course = too difficult to manageToo course = too difficult to manage

Can’t estimate time to completionCan’t estimate time to completion Can’t keep track of how complete it isCan’t keep track of how complete it is Can’t turn in interim results because they Can’t turn in interim results because they

are not definedare not defined

GranularityGranularity

If a task is not a direct deliverable If a task is not a direct deliverable then it is too finethen it is too fine

A task should:A task should: Be definable as an OUTCOMEBe definable as an OUTCOME Have a duration no more than a weekHave a duration no more than a week

GranularityGranularity

Progressive elaborationProgressive elaboration Allows details to be progressivelyAllows details to be progressively

A word on durationA word on duration

A task may only take 10 hours to A task may only take 10 hours to completecomplete

Theoretically, that can be done by Theoretically, that can be done by the end of the weekthe end of the week

If the person assigned this task is If the person assigned this task is out of town, sick or gets hit by a bus out of town, sick or gets hit by a bus you have a problemyou have a problem

EstimatingEstimating

If you can not estimate time to If you can not estimate time to completion, break the task down completion, break the task down furtherfurther

If you can not AGREE on the time to If you can not AGREE on the time to completion, list the assumptions of completion, list the assumptions of those in disagreementthose in disagreement

ScheduleSchedule

Each OUTCOME must be listedEach OUTCOME must be listed A date of completion must A date of completion must

accompany each outcomeaccompany each outcome Responsibility for each outcome Responsibility for each outcome

must be assignedmust be assigned All expected outcomes must be listedAll expected outcomes must be listed