89%(9)8 out of 9 people found this document helpful
This preview shows page 27 - 28 out of 28 pages.
AACSB: Reflective Thinking SkillsBaltzan - Chapter 17 #50Learning Outcome: 17.3Level: HardTaxonomy: Application and Analysis51. Define the relationship between the systems development life cycle and software development methodologies. All software development methodologies use the systems development life cycle, however, the way that they use it differs. For example, all projects must have planning and testing phases, however one project might use the waterfall approach and have the planning occur at the beginning of the project and the testing occur at the end. Another project might use the XP method and have small planning and testing phases occurring all the time.AACSB: Reflective Thinking SkillsBaltzan - Chapter 17 #51Learning Outcome: 17.1Level: HardTaxonomy: Application and Analysis27
52. Compare the waterfall methodology and the agile methodology. The waterfall methodology is a sequential, activity-based process in which each phase in the SDLC is performed sequentially from planning through implementation and maintenance. The agile methodology is a form of XP, aims for customer satisfaction through early and continuous delivery of useful software components. These are two opposite ends of the spectrum in terms of systems development methodologies. The primary difference between the waterfall and XP methodologies is that XP divides its phases into iterations with user feedback.AACSB: Reflective Thinking SkillsBaltzan - Chapter 17 #52Learning Outcome: 17.3Level: HardTaxonomy: Application and Analysis53. Explain why software problems are business problems. Only 28 percent of projects are developed within budget and delivered on time and as promised, says a report from the Standish Group, a Massachusetts-based consultancy. The primary reasons for project failure are: Unclear or missing business requirements, skipping SDLC phases, failure to manage project scope, failure to manage project plan, and changing technology.AACSB: Reflective Thinking SkillsBaltzan - Chapter 17 #53Learning Outcome: 17.6Level: HardTaxonomy: Application and Analysis
You've reached the end of your free preview.
Want to read all 28 pages?
Revenue, Systems Development Life Cycle, Rapid application development