Software Development Process Proposal

1
Software Development Process Proposal

• Process Improvement Proposal
• Vince Petrielli
• SE470

2
Generalized View of Current Development Process

• Customer involved in use
• Case reviews
• Iteratively developed some
• use cases.

3
Current Development Process Pitfalls

• New technology risk Wasted effort on unused
  alternatives.
• Semi iterative process - Iteration cycles only
  included analysis, design, and small portions of
  implementation.
• On demand Tier integration no formal build and
  integration schedule
• Limited time for prototyping due to poor
  estimations
• No traceability between Requirements and Code
• No continuous verification of quality
• Just-in-time risk identification and last minute
  risk resolution
• Insufficient Hardware requirements
• Resources assigned to concurrent projects which
  jeopardized delivery dates.

4
Process Improvement Objectices

• Improve requirements management and software
  configuration management (ClearQuest/ClearCase
  integration)
• Stakeholder review at each development phase to
  identify risks and risk action plans
• Capture more in-phase defects in requirements and
  design (Improve requirements definition)
• Regression testing at each test phase

5
Proposed process improvement plan

• Implement an XP-Spiral process
• Identify key artifacts - Requirements, Plans,
  Design, Code--in each Iteration
• More defined Requirement phases
• Customer requirements
• System requirements
• Implementation requirements
• Consider all customer objectives and constraints,
  product and process alternatives, risks and
  resolution, stakeholder review, and commitment to
  proceed.
• Continue pair programming within each tier with
  100 resource commitment.
• Deliver small releases delivery for each use
  case

6
Q A