Project Management in the Software Development Environment CIS490.

Project ManagementProject Management in the

Software Development EnvironmentSoftware Development Environment

CIS490CIS490

Project Management

Managing Resources

SDLCAnd

Its deliverables

Software Economics

TeamManagement

Managing Risk and change

ManagementSkills

Project management frameworkProject management framework

Function Point EstimationStep One

Complexity

Description Low Medium High Total

Inputs __x 3 __x 4 __x 6 ____

Outputs __x 4 __x 5 __x 7 ____

Queries __x 3 __x 4 __x 6 ____

Files __x 7 __x 10 __x 15 ____

Program __x 5 __x 7 __x 10 ____Interfaces

TOTAL UNADJUSTED FUNCTION POINTS ____

Function Points EstimationStep Two

Scale of 1 to 5

Data Communications _____Heavy Use Configuration _____Transaction Rate _____End-User efficiency _____Complex Processing _____Installation Ease _____Multiple sites _____Performance _____Distributed functions _____On-line data entry _____On-line update _____Reusability _____Operational Ease _____Extensibility _____

Project Complexity (PC) _____

Function Point Estimation -- Step 3

Processing Complexity (PC): ________(From Step 2)

Adjusted Processing Complexity (PCA) = 0.65 + (0.001 * ____ )

Total Adjusted Function Points: _____ * ____ = (TUFP -- From Step 1)

Function Points EstimationStep Three

Adjusted Project Complexity

= .065 + (0.01 * Project Complexity)

Total Adjusted Function Points

=

Adjusted Project Complexity * TUFP

Converting Function Points to Lines of Code

Source: Capers Jones, Software Productivity Research

Language LOC/Function Code Point

CCOBOLJAVAC++Turbo PascalVisual BasicPowerBuilderHTMLPackages (e.g., Access, Excel)

130110 55 50 50 30 15 1510-40

Estimating Effort

• Function of size and production rate

• COCOMO model

COCOMO Estimation Calculation

Effort = 1.4 * thousands-of-(in Person- lines-of-codeMonths)

Example:

If LOC = 2000 Then...Effort = (1.4 * 2000) = 28

Person Months

Estimating Schedule Time

• Rule of thumb for estimation

Schedule Time (months)

=

3.0 * person-months1/3

A Workplan ExampleWork Plan Information Example

Name of task Perform economic feasibilityStart date ` Jan 05, 2001Completion date Jan 19, 2001Person assigned Mary Smith, sponsorDeliverable(s) Cost-benefit analysisCompletion status OpenPriority HighResources needed SpreadsheetEstimated time 16 hoursActual time 14.5 hours

Top Down Task Identification

PhasesPhases with

high level steps

Work Plan Deliverables Estimated Actual Assignedhours hours To

****

A Gantt Chart

A PERT Chart

PERT Chart Showing Activities and Sequence

Acrobat Document

PERT Chart for the SPTS Project

Viewing Project Information as a PERT Chart in Microsoft for Windows

Boehm’s top ten risk items• Personnel shortfalls• Unrealistic schedules and budgets• Developing the wrong functions• Developing the wrong user interfaces• Gold-plating• Continuing stream of requirements changes• Shortfalls in externally-performed tasks• Shortfalls in externally-furnished components• Real-time performance shortfalls• Straining computer science capabilities

Risk management requirements

• Risk impact: the loss associated with the event

• Risk probability: the likelihood that the event will occur

• Risk control: the degree to which we can change the outcome

Risk exposure = (risk probability) x (risk impact)

Three strategies for risk reduction

• avoiding the risk: change requirements for performance or functionality

• transferring the risk: transfer to other system, or buy insurance

• assuming the risk: accept and control it

risk leverage = difference in risk exposure divided by cost of reducing the risk