New version page

OSU BA 371 - Systems Analysis & Design

Documents in this Course
Load more
Upgrade to remove ads
Upgrade to remove ads
Unformatted text preview:

Systems Analysis & DesignThe CHAOS Report (1994)The CHAOS Report (1994) FindingsProject Success FactorsSystems Analysis & DesignThe Cost of DefectsProcess DefinedJuggle Juggle JuggleThe Importance of ProcessesCapability Maturity Model Integration (CMMI )A Practical Example of Process ImprovementSlide 12Waterfall ModelWaterfall Model (continued)Software Process Models Waterfall Model (continued)Software Process Models Drawbacks of The Waterfall ModelSlide 17Slide 18Slide 19Slide 20Software Process Models Agile MethodsSlide 22The Big ?The Rise of Computer Science◦Machine Language (1st Gen)◦Assembly Language (2nd Gen)◦Third Generation Languages (FORTRAN, BASIC, Java, C++, etc.)◦CASE (4th Gen)?IT System ComplexitySystems Analysis & DesignThe CHAOS Report (1994)Produced by the Standish Group via surveys, focus groups, and case studieshttp://www.standishgroup.com/sample_research/chaos_1994_1.phpProject Resolution Types◦Success = On-Time, On-Budget, Fully Featured◦Challenged = Over-Time, Over-Budget, Fewer Features◦Impaired = CancelledA lot of interesting findings about Software Development track recordThe CHAOS Report (1994) FindingsProject Success Factors“The three major reasons that a project will succeed are user involvement, executive management support, and a clear statement of requirements. There are other success criteria, but with these three elements in place, the chances of success are much greater. Without them, chance of failure increases dramatically.” – The Chaos Report (1994), Standish GroupProject Success Factors% of Responses1. User Involvement 15.9%2. Executive Management Support13.9%3. Clear Statement of Requirements13.0%4. Proper Planning 9.6%5. Realistic Expectations 8.2%6. Smaller Project Milestones 7.7%7. Competent Staf 7.2%8. Ownership 5.3%9. Clear Vision & Objectives 2.9%10. Hard-Working, Focused Staf 2.4%Other 13.9%p.3: "Systems analysis and design emerged from the need to perform certain activities around, and particularly prior to, the steps involved in developing a computer system using software engineering tools and techniques." Systems Analysis & DesignThe Cost of DefectsSpecification Planning Programming OperationCost of DefectsA process: a series of steps involving activities, constrains, and resources that produce an intended ouput of some kindA process involves a set of tools and techniquesProcess DefinedPhase I Requirements◦All balls must remain in motion◦Only one person at a time can touch a ball (ball must be passed in the air)◦Each person may only touch one ball at a time◦Juggle for 15 seconds without dropping the ballPhase II Requirements◦All phase I requirements apply◦The ball cannot be passed to the person by your sideJuggle Juggle JuggleImpose consistency and structure on a set of activitiesGuide us to understand, control, examine, and improve the activitiesEnable us to capture our experiences and pass them alongThe Importance of ProcessesCapability Maturity Model Integration (CMMI )Carnegie Mellon UniversityA Practical Example of Process ImprovementWaterfall modelV modelPrototyping modelOperational specificationTransformational modelSpiral modelPhased development: increments and iterationsAgile methodsSoftware Development Process Models or Software Development Life Cycle (SDLC)One of the first process development models proposedWorks for well understood problems with minimal or no changes in the requirements Simple and easy to explain to customersIt presents a very high-level view of the development processsequence of process activities Each major phase is marked by milestones and deliverables (artifacts)Waterfall ModelWaterfall Model (continued)This version difers from the book but the idea is the same:There is no iteration in waterfall modelMost software developers apply a great many iterationsSoftware Process ModelsWaterfall Model (continued)Provides no guidance on how to handle changes to requirements/design during development (assumes requirements/design can be frozen)Views software development as manufacturing process rather than as creative processThere is no iterative activities that lead to creating a final productLong wait before a final productLacks Business Process Redesign!Software Process ModelsDrawbacks of The Waterfall ModelShorter cycle timeSystem delivered in pieces◦enables customers to have some functionality while the rest is being developedAllows two systems functioning in parallel◦the production system (release n): currently being used◦the development system (release n+1): the next versionSoftware Process ModelsPhased Development: Increments and IterationsSoftware Process ModelsPhased Development: Increments and Iterations(continued)Incremental development: starts with small functional subsystem and adds functionality with each new releaseIterative development: starts with full system, then changes functionality of each subsystem with each new releaseSoftware Process ModelsPhased Development: Increments and IterationsPhased development is desirable for several reasons◦Training can begin early, even though some functions are missing◦Markets can be created early for functionality that has never before been ofered◦Frequent releases allow developers to fix unanticipated problems globaly and quickly◦The development team can focus on diferent areas of expertise with diferent releasesSoftware Process ModelsPhased Development: Increments and IterationsEmphasis on flexibility in producing software quickly and capablyAgile manifesto http://www.agilemanifesto.org/Value individuals and interactions over process and toolsPrefer to invest time in producing working software rather than in producing comprehensive documentationFocus on customer collaboration rather than contract negotiationConcentrate on responding to change rather than on creating a plan and then following itSoftware Process ModelsAgile MethodsExtreme programming (XP)Crystal: a collection of approaches based on the notion that every project needs a unique set of policies and conventionsScrum: 30-day iterations; multiple self-organizing teams; daily “scrum” coordinationSoftware Process ModelsAgile Methods: Examples of Agile ProcessWhat about process redesign?◦What does it profit the business if all we do is automate the process as is?◦What about


View Full Document
Download Systems Analysis & Design
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Systems Analysis & Design and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Systems Analysis & Design 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?