BDT9e_CH17_Student_PPT_accessible lu6.pdf

Business Analysis Building Software to Support an Agile Organisation (Learning Unit 6 – Chapter 17  CHAPTER SEVENTEEN: OVERVIEW The Systems Development Life Cycle. Software Development Methodology: Waterfall. Agile Software Development Methodologies. © McGraw Hill...

Business Analysis Building Software to Support an Agile Organisation (Learning Unit 6 – Chapter 17  CHAPTER SEVENTEEN: OVERVIEW The Systems Development Life Cycle. Software Development Methodology: Waterfall. Agile Software Development Methodologies. © McGraw Hill 2  LEARNING OUTCOMES 1. Describe the seven phases of the systems development life cycle. 2. Summarize the different software development methodologies. © McGraw Hill 3  THE SYSTEMS DEVELOPMENT LIFE CYCLE 1 Software that is built correctly can transform as the organization and its business transforms. Software that effectively meets employee needs will help an organization become more productive and enhance decision making. Software that does not meet employee needs may have a damaging effect on productivity and can even cause a business to fail. © McGraw Hill 4  THE SYSTEMS DEVELOPMENT LIFE CYCLE 2 As organizations’ reliance on software grows, so do the business-related consequences of software successes and failures including: Increase or decrease revenue. Repair or damage to brand reputation. Prevent or incur liabilities. Increase or decrease productivity. © McGraw Hill 5  THE SYSTEMS DEVELOPMENT LIFE CYCLE 3 Systems development life cycle (SDLC) – The overall process for developing information systems from planning and analysis through implementation and maintenance. Access the text alternative for slide images. © McGraw Hill 6  THE SYSTEMS DEVELOPMENT LIFE CYCLE 4 1. Planning phase – Establishes a high-level plan of the intended project and determines project goals. Organizations must carefully plan the activities (and determine why they are necessary) to be successful. Brainstorming ideas by encouraging participants to offer as many ideas as possible 2. Analysis phase – Involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system. © McGraw Hill 7  THE SYSTEMS DEVELOPMENT LIFE CYCLE 5 3. Design phase – Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation. 4. Development phase – Involves taking all of the detailed design documents from the design phase and transforming them into the actual system. During development the team defines the programming language it will use to build the system © McGraw Hill 8  THE SYSTEMS DEVELOPMENT LIFE CYCLE 6 5. Testing phase – Involves bringing all the project pieces together into a special testing environment to eliminate errors and bugs and verify that the system meets all of the business requirements defined in the analysis phase. © McGraw Hill 9  THE SYSTEMS DEVELOPMENT LIFE CYCLE 7 Access the text alternative for slide images. © McGraw Hill 10  THE SYSTEMS DEVELOPMENT LIFE CYCLE 6 5. Implementation phase – Involves placing the system into production so users can begin to perform actual business operations with it. In this phase a detailed user documentation is created that highlights how to use the system and how to troubleshoot issues or problem. © McGraw Hill 11  THE SYSTEMS DEVELOPMENT LIFE CYCLE 8 Access the text alternative for slide images. © McGraw Hill 12  THE SYSTEMS DEVELOPMENT LIFE CYCLE 9 7. Maintenance phase – Involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet its business goals. © McGraw Hill 13  SOFTWARE DEVELOPMENT METHODOLOGIES There are a number of different software development methodologies including: Waterfall. Agile. Rapid application development (RAD). Extreme programming. Rational unified process (RUP). Scrum. © McGraw Hill 14  WATERFALL METHODOLOGY Waterfall methodology – A sequence of phases in which the output of each phase becomes the input for the next. Access the text alternative for slide images. © McGraw Hill 15  AGILE METHODOLOGY Agile methodology – Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements. Agile is what sounds like: fast and efficient, with lower costs and fewer features. Iterative development – Consists of a series of tiny projects. © McGraw Hill 16  RAPID APPLICATION DEVELOPMENT METHODOLOGY (RAD) The primary forms of agile methodologies include the following: Rapid application development methodology– Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process. Prototype – A smaller-scale representation or working model of the users’ requirements or a proposed design for an information system. The prototype is an essential part of the analysis phase when using a RAD methodology. 17 © McGraw Hill  TBP309 Extreme Programming Methodology ◼ Extreme programming (XP) methodology – breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete User feedback User feedback User feedback User feedback  RATIONAL UNIFIED PROCESS (RUP) METHODOLOGY Rational Unified Process (RUP) – Provides a framework for breaking down the development of software into four gates: Gate One: Inception. Gate Two: Elaboration. Gate Three: Construction. Gate Four: Transition. © McGraw Hill 19  SCRUM METHODOLOGY SCRUM – Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal. Under this methodology, each day ends or begins with a stand-up meeting to monitor and control the development effort. © McGraw Hill 20  TBP250 Software Problems Are Business Problems ◼ Primary reasons for project failure include: ◼ Unclear or missing business requirements ◼ Skipping SDLC phases ◼ Failure to manage project scope ◼ Failure to manage project plan ◼ Changing technology 17-21  TBP250 Software Problems Are Business Problems ◼ Find errors early: the later in the SDLC an error is found - the more expensive it is to fix 17-22  LEARNING OUTCOME REVIEW Now that you have finished the chapter please review the learning outcomes in your text. © McGraw Hill 23  Because learning changes everything. ® www.mheducation.com Copyright 2022 © McGraw Hill LLC. All rights reserved. No reproduction or distribution without the prior written consent of McGraw Hill LLC.