Systems Development Life Cycle (SDLC)PowerPoint PresentationStructured Project SDLCSDLC Waterfall ModelSlide 5Spiral Model and PrototypingRequirements ElicitationSlide 8Slide 9SOFTWARE PROBLEMS ARE BUSINESS PROBLEMSBalancing The Triple Constraints in ProjectsThe Mythical Man-MonthSlide 13Team ProductivityAdding More PeopleDesign: Cohesion and CouplingStubs and DriversGeneral Systems Theory: Abstract ThinkingTestingTypes of TestsRegression and Regression TestReasons for Project FailuresSlide 23Successful Principles for Software DevelopmentThe EndThe Ten Essentials of RUPUnified Process StructureSlide 28Slide 29Slide 30Slide 31Slide 32SDLC - 1Systems Development Life Cycle(SDLC)Minder Chen, Ph.D. Professor of MISMartin V. Smith School of Business and EconomicsCSU Channel [email protected] - 2Life Cycle Stages: Planning Analysis Design Implementation What Problems/OpportunitiesRequirementsSoft/People SkillsHowSolutionsSpecificationsTechnical SkillsVisibility: Deliverables/DocumentationMethodology*:•Process (Life Cycle)•Techniques (Modeling)Data ProcessUIPrototypingCodingProgrammingImplementationUI: User Interface*A system development methodology is a framework that is used to structure, plan, and control the process of developing an information system.Use modeling techniquesSDLC - 3Structured Project SDLC Planning/ PreliminaryStudyAnalysisDesignImplementationTesting , Integration, & InstallationOperation & Maintenance•Users Participation•Documentation•Modeling Techniques•CASE/IDE Tools*•Quality AssuranceApproved ProjectProposalRefined project scopeCost/Benefit AnalysisApprovedRe-developmentProject ProposalRequirementsDesignSpecificationsImplemented SystemIntegrated & Tested System*CASE: Computer-Aided Software Engineering IDE: Integrated Development EnvironmentSDLC - 4SDLC Waterfall Model •Programming•Testing•Training•InstallationRequirementsAS-IS vs. TO-BELogical and physical Design specificationIdentify & prioritize IS development projectsBug fix and UpgradesIT Service Management (ITIL standard)SDLC - 5Deliverables/Documentations of SDLC Stages/Phases5SDLC - 6Spiral Model and Prototyping http://en.wikipedia.org/wiki/Spiral_modelhttp://www.reliablesoftware.com/weblog/uploaded_images/spiral-712085.bmp 6SDLC - 7Requirements ElicitationSDLC - 8Managing User InterviewsSDLC - 9Stakeholder PerspectivesSDLC - 10SOFTWARE PROBLEMS ARE BUSINESS PROBLEMS•Find errors early: the later in the SDLC an error is found - the more expensive it is to fixSDLC - 11Balancing The Triple Constraints in ProjectsSDLC - 12The Mythical Man-Monthhttp://www.cs.drexel.edu/~yfcai/CS451/RequiredReadings/MythicalManMonth.pdfSDLC - 13The Mythical Man-MonthSDLC - 14Team ProductivitySDLC - 15Adding More People•Brook's Law: •Adding developers to a late project will make it later.SDLC - 16Design: Cohesion and Coupling•Divide and Conquer for effective teamwork•Software Design Criteria•Modularization: Simple, stable, and clearly defined interface for each module, no need to understand the internal structure or design of the module to use it.•Good design is a system that has low coupling between modules and high cohesion within modulesSDLC - 17Stubs and DriversDriverModule 1 Module 2Module MStub Module 2•Stubs Stubs are non-functional components that provide the class, property, or method definition used by the other component. Stubs are a kind of outline of the code you will create later. •To test two components that need to work together through a third component that has not been written yet, you create a driver. Drivers Drivers are simply test components that make sure two or more components work together. Later in the project, testing performed by the driver can be performed by the actual component. The most common build problem occurs when one component tries to use another component that has not yet been written. This occurs with modular design because the components are often created out of sequence.SDLC - 18General Systems Theory: Abstract ThinkingSource: http://cimru.nuigalway.ie/david/pdf/SE/Slides/Theory.PDFSDLC - 19Source: Developing Web Applications with Microsoft Visual Basic .NET and Microsoft Visual C# .NETTesting•Test plan objectives –Is thoroughly tested–Meets requirements–Does not contain defects•Test plan covers–Tools–Who–Schedule–Test result analysis–What is being tested? •Test cases•Automated testing –Reproducible –MeasurableSDLC - 20Test type ObjectivesUnit testEach independent piece of code works correctlyIntegration testAll units work together without errorsRegression testNewly added features do not introduce errors to other features that are already working Load test (also called stress test)The product continues to work under extreme usagePlatform testThe product works on all of the target hardware and software platformsTypes of TestsSDLC - 21Regression and Regression Test•Regression testing is the process of validating modified parts of the software and ensuring that no new errors are introduced into previously tested code. •Unit and integration tests form the basis of regression testing. As each test is written and passed, it gets checked into the test library for a regularly scheduled testing run. If a new component or a change to an existing component breaks one of the existing unit or integration tests, the error is called a regression.the error is called a regression.SDLC - 22Reasons for Project FailuresPrimary reasons for project failure include•Unclear or missing business requirements•Skipping SDLC phases•Failure to manage project scope–Scope creep – occurs when the scope increases–Feature creep – occurs when extra features are added•Failure to manage project plan•Changing technologySDLC - 23SDLC - 24Successful Principles for Software DevelopmentPrimary principles for successful agile software development include:•Slash the budget•If it doesn’t work, kill it•Keep requirements to a minimum •Test and deliver frequently•Assign non-IT executives to software projectsSDLC - 25The EndSDLC - 26The Ten Essentials of RUPThe Ten Essentials of RUP1. Develop a Vision 2. Manage to the Plan 3. Identify and Mitigate Risks 4. Assign and Track Issues 5. Examine the Business Case 6. Design a Component Architecture 7. Incrementally Build and Test the Product 8. Verify and Evaluate Results 9. Manage and Control Changes 10. Provide User Support Source: