Textbook Notes (368,317)
Canada (161,798)
Commerce (1,695)
Chapter 10

Commerce 2KA3 - Chapter 10 Summary

16 Pages
Unlock Document


Chapter 10Systems DevelopmentIntroductionSoftware that effectively meets employee needs will help an organization become more productive and enhance decision makingDeveloping SoftwareAlmost every large organization in the world relies on software either to drive its business operations or to make its products workAsorganizations reliance on software grows so do the businessrelated consequences of software successes and failuresUnderstanding the basics of software development methodologies will help organizations avoid potential software development pitfalls and ensure that software development efforts are successfulSoftware Development MethodologiesToday systems are so large and complex that teams of architects analysts developers testers and users must work together to create the millions of lines of customwritten code that drive enterprisesWaterfall MethodologyWaterfall methodology a sequential activitybased process in which each phase in the systems development life cycle is performed sequentially from planning through implementation and maintenanceOne of the oldest and has been around more than 30 yearsSuccess rate is 1 in 10 On primary reason for such a low success rate is that the waterfall methodology does not sufficiently consider the level of uncertainty in new projects and the creativity required to complete software development projects in several aspectsAs peoples understanding of the business problems evolve so must the softwareRapid Application Development Methodology RADRapid application development also called rapid prototyping methodology emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development processPrototype a smallerscale representation or working model of the users requirements or a proposed design for an information systemExtreme Programming MethodologyExtreme programming XP methodology breaks a project into tiny phases and developers cannot continue on to the next phase until the first phase is completeThe primary difference between the waterfall and XP methodologies is that XP divides its phases into iterations with user feedbackXP is a significant departure from traditional software development methodologies and many organizations in different industries have developed successful software using itThe XP methodology promotes quickly being able to respond to changing requirements and technologyAgile MethodologyAgile methodology a form of XP aims for customer satisfaction through early and continuous delivery of useful software componentsAgile is similar to XP but with less focus on team coding and more on limiting project scopeSlash the Budget Small budgets force developers and users to focus on the essentials They also make it easier to kill a failing projectIf It doesnt work kill it Bring all key stakeholders together at the beginning of a project and as it progresses bring them together again to evaluate the softwareoEliminate any software that is not meeting business expectationsKeep Requirements to a Minimum Start each project with what the software must absolutely do Do not start with a list of everything the software should do
More Less

Related notes for COMMERCE 2KA3

Log In


Join OneClass

Access over 10 million pages of study
documents for 1.3 million courses.

Sign up

Join to view


By registering, I agree to the Terms and Privacy Policies
Already have an account?
Just a few more details

So we can recommend you notes for your school.

Reset Password

Please enter below the email address you registered with and we will send you a link to reset your password.

Add your courses

Get notes from the top students in your class.