0% found this document useful (0 votes)
18 views36 pages

Chapter 2 Developing An Analysis Plan

Uploaded by

kelwa3366
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views36 pages

Chapter 2 Developing An Analysis Plan

Uploaded by

kelwa3366
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 36

DEVELOPING AN

ANALYSIS PLAN
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and
Design
Slide 1 Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.
CREATING THE PROJECT
PLAN
Project management phases consist of
- initiation
- planning
- execution
- control, and
- enclosure.

POWERPOINT PRESENTATION FOR DENNIS, WIXOM & TEGARDEM SYSTEMS ANALYSIS


Slide 2
AND DESIGN
COPYRIGHT 2001 © JOHN WILEY & SONS, INC. ALL RIGHTS RESERVED.
THE SDLC PROCESS

PowerPoint
Presentation for
Dennis, Wixom &
Tegardem
Systems Analysis and
Design SLIDE 3
Copyright 2001 ©
PROJECT
METHODOLOGY
OPTIONS
A methodology is a formalized approach to
implementing the SDLC.

- Waterfall Development
- Parallel Development
- V-model (variation of the WaterfallDevelopment)
- Rapid Application Development (RAD)
- Iterative Development
- System prototyping
- Agile Development
POWERPOINT PRESENTATION FOR DENNIS, WIXOM & TEGARDEM SYSTEMS ANALYSIS
Slide 4
AND DESIGN
COPYRIGHT 2001 © JOHN WILEY & SONS, INC. ALL RIGHTS RESERVED.
WATERFALL DEVELOPMENT

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-5
PARALLEL DEVELOPMENT

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-6
V-MODEL

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-7
RAPID APPLICATION DEVELOPMENT:
ITERATIVE DEVELOPMENT

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-8
RAP
RAFID APPLICATION DEVELOPMENT: SYSTEM
PROTOTYPING

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-9
(CONT’D)
Throwaway prototyping

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-10
AGILE DEVELOPMENT
A group of programming-centric methodologies that focus on streamlining
the SDLC.
Includes face-to-face communication
Extreme programming – emphasizes customer satisfaction and
teamwork.

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-11
EXTREME PROGRAMMING

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-12
CRITERIA FOR SELECTING A
METHODOLOGY

POWERPOINT PRESENTATION FOR


DENNIS, WIXOM & ROTH SYSTEMS
ANALYSIS AND DESIGN, 4TH EDITION
COPYRIGHT 2011© JOHN WILEY &
2 - 13
SONS, INC. ALL RIGHTS RESERVED..
(CONT’D)
Important factors to consider in selecting the development
methodology
- Clarity of User Requirements
- Familiarity with Technology
- System Complexity
- System Reliability
- Short Time Schedules
- Schedule Visibility

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-14
ESTIMATING THE
PROJECT TIME FRAME
1. Estimating Project Time Using Industry Standards

2. Function point approach (Appendix 2A)


© COPYRIGHT 2011 JOHN WILEY & SONS,
INC. 2-15
FUNCTION POINT APPROACH –
APPENDIX 2A
Estimate project size
 Use function points
 Calculate TUFP
 Calculate APC
 Calculate TAFP
 Use lines of code (see figure 2A-3, p. 93)
Estimate effort required (in person-months)
 1.4 * thousands of lines of code

Estimate time required (in months)


 3 * person-months1/3
© COPYRIGHT 2011 JOHN WILEY & SONS, 2-16
INC.
DEVELOPING THE WORK
PLAN
Identify Tasks

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-17
WORK BREAKDOWN
STRUCTURE

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-18
(CONT’D)

The project work plan

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-19
GANTT CHART
GANTT charts display the tasks in a project as a
box or line showing the calendar duration of the
task on the horizontal axis (the horizontal length of
the task box is proportional to the task duration).
Tasks are normally arranged in date order on the
vertical axis. The time relation of all tasks to each
other (for example, tasks carried out
simultaneously) is therefore clearly apparent in a
GANTT chart.
The project status can be easily determined at
intermediate dates in the project, and progress of
individual tasks can be shown by filling in the task
boxes. Slide 20
GANTT CHART
GANTT CHART EXAMPLE

Slide 22
EXAMPLE 2

Slide 23
SOLUTION

Slide 24
PERT CHART
Program Evaluation Review Technique (PERT) charts show
each task in a project as a node. Dependencies between tasks
(e.g. where one task requires another one to be completed
before it can start) are clearly shown by interconnections
between the task nodes.
PERT charts also show timing information for each task. PERT
charts are similar to the critical path method (CPM) which
identifies the longest path through the project, and therefore
the minimum time for the project to be completed. In the
example below, the critical path is shown by the red arrows.

PERT charts try to make a realistic estimate by considering


three scenarios and then generating an Expected Time as a
weighted average:

Slide 25
PERT CHART EXAMPLE

Slide 26
PERT EXAMPLE

Slide 27
SOLUTION

Critical path: A-B-C-E-F-G

Slide 28
Slide 29
CRITICAL PATH

Slide 30
EXAMPLE
Task Duration Dependent

Task 1 4 days -

Task 2 6 days -

Task 3 5 days -

Task 4 3 days 1

Task 5 6 days 2

Task 6 4 days 3

Task 7 2 days 4&5

Task 8 5 days 6&7


Slide 31
SOLUTION

Slide 32
STAFFING THE PROJECT
Staffing Plan

- Staffing levels will change over a


project’s lifetime
- Adding staff may add more overhead
than additional labor
- Using teams of 8-10 reporting in a
hierarchical structure can reduce
complexity
© COPYRIGHT 2011 JOHN WILEY & SONS,
INC. 2-33
(CONT’D)
Reporting structure

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-34
(CONT’D)
The staffing plan describes the kinds of people working on the project
The project charter describes the project’s objectives and rules
A functional lead manages a group of analysts
A technical lead oversees progress of programmers and technical staff
members

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-35
HANDLING CONFLICT
Clearly define plans for the project.
Recognize project importance to organization.
Project charter listing norms and ground rules.
Develop schedule commitments ahead of time.
Forecast other priorities and their possible impact on the project.

© COPYRIGHT 2011 JOHN WILEY & SONS,


INC. 2-36

You might also like