Need help with : software development process model
module_02_assessment__assingment.docx
module_2f_slides.pdf
Unformatted Attachment Preview
For this week’s assignment, please read the following scenario and respond to the
questions below. You should submit your responses in a Microsoft Word or PDF
document by clicking the “Module 02 Assessment” link above, and then uploading your
document to the Blackboard site.
Scenario:
The Investment Services business area at Financial Global Inc. is preparing a proposal for a new
contract to develop a new internet banking program. The internet banking program must support
four releases to be built 10 months apart beginning 12 months after contract award. The
customer requires the product to be fully tested and installed three months before the official
releases. The banking program has been estimated to require 40,000 lines of code (8,000 for
basic functionality, 8,000 for build 0 unique functionality, 10,000 for build 1 unique
functionality, 8,000 for build 2 unique functionality, and 6,000 for build 3 unique
functionality). Your organization has not previously developed in this domain so you are using
10 lines of code per day as a very conservative productivity estimate.
What software development process model do you suggest? Defend your suggestion.
Choosing a Software Process
Model
Engineering for Professionals
Comparing Process Models
Category
Characteris.cs
Code & Fix
•
•
Code used for analysis/problem solving
Small amount of code
•
•
One developer
Thrown away after results obtained
Waterfall
•
•
•
•
Requirements well defined
Predictable development
Known environment
Experienced development team
•
•
•
•
Enhancing/upgrading existing system
No technological risks
Reasonable budget/schedule
Interfaces established/unchanging
Evolutionary (or Incremental
Build) Model
•
•
•
•
Most requirements well defined
Budget/schedule constraints
Some technology risks
Integration with other systems/
subsystems
•
•
•
•
Some evolving requirements
Interfaces not well defined
New system, never done before
COTS and/or reusable software not
available
Spiral Model
•
•
Very large software system
Long schedule (5 to 10 years)
•
•
Many risk areas
Emphasis on system reliability
•
Requirements can be satisfied by COTS
products
Numerous functional capabilities in
commercial
•
•
•
Government furnished components
Intended to be inexpensive solution
Often assumed “simple” solution
Requirements unstable
Unpredictable development
Unknown environment
Minimal planning
•
•
•
•
Anticipate Requirements Volatility
People-oriented
Highly Collaborative
Focus on Construction
COTS Integration
Agile Development
Engineering for Professionals
•
•
•
•
•
General Capabilities
Lifecycle Model Capability
Code and Fix
Waterfall
Evolutionary
Spiral
COTS
Agile
Integration Development
Works with ambiguous requirements
Poor
Poor
Fair to
Excellent
Excellent
Excellent
Excellent
Works with ambiguous architecture
Poor
Poor
Poor
Excellent
Poor to
Excellent
Excellent
Produces highly reliable system
Poor
Excellent
Fair to
Excellent
Excellent
Poor to
Excellent
Poor to
Excellent
Produces system with large growth potential Poor
Excellent
Excellent
Excellent
N/A
Fair
Manages risks
Poor
Poor
Fair
Excellent
N/A
Fair
Can be constrained to a predefined
schedule
Poor
Fair
Fair
Fair
Excellent
Poor
Minimal management and technical
oversight needed to use the model
Excellent
Poor
Fair
Fair
Excellent
Fair
Allows for midcourse corrections
Poor to
Excellent
Poor
Fair to
Excellent
Fair
Poor
Excellent
Provides customer with progress visibility
Fair
Poor
Excellent
Excellent
N/A
Excellent
Provides management with progress
visibility
Poor
Fair
Excellent
Excellent
N/A
Excellent
Requires little manager or developer
sophistication
Excellent
Fair
Fair
Poor
Fair
Fair
Works with ambiguous requirements
Poor
Poor
Fair to
Excellent
Excellent
Excellent
Excellent
Engineering for Professionals
…
Purchase answer to see full
attachment
Recent Comments