Risk Management in Spiral Lifecycle Model for Tune Source Project - Prof. Pham, Study notes of Engineering

Download Risk Management in Spiral Lifecycle Model for Tune Source Project - Prof. Pham and more Study notes Engineering in PDF only on Docsity!

ASSIGNMENT 1 BRIEF

Qualification BTEC Level 5 HND Diploma in Computing Unit number Unit 9: Software Development Life Cycle Assignment title Planning a Software Development Lifecycle Academic Year (^) 2021 - 2022 Unit Tutor Ngọc Mai Issue date 22 - 08 - 2021 Submission date IV name and date Hoài Nam Submission Format: Format: The submission is in the form of 1 document You must use font Calibri size 12, set number of the pages and use multiple line spacing at 1.3. Margins must be: left: 1.25 cm; right: 1 cm; top: 1 cm and bottom: 1 cm. The reference follows Harvard referencing system. Submission Students are compulsory to submit the assignment in due date and in a way requested by the Tutors. The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/ Note: The Assignment must be your own work, and not copied by or from another student or from books etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. Make sure that you know how to reference properly, and that understand the guidelines on plagiarism. If you do not, you definitely get failed Unit Learning Outcomes:

Table of Contents

Unit 09: SOFTWARE DEVELOPMENT LIFE CYCLES ............................................................................................ 1 INTRODUCTION OF SOFTWARE DEVELOPMENT LIFE CYCLES .......................................................................... 1 P1 Describe two iterative and two sequential software lifecycle models. ....................................................... 2

1. Original Waterfall Model ................................................................................................................... 2 1.1. What is the waterfall model? ..................................................................................................... 2 1.2. How is waterfall description? ..................................................................................................... 2 1.3. Advantages and Disadvantages of waterfall mode ...................................................................... 3
2. Prototyping Mode ............................................................................................................................. 4 1. What is the prototyping mode? ..................................................................................................... 4 2. How is it description? .................................................................................................................... 4 3. Advantages and disadvantages of prototyping mode ...................................................................... 5
3. Spiral model ...................................................................................................................................... 6 3.1. What is spiral model? ................................................................................................................. 6 3.2. How is it description? ................................................................................................................. 7 3.3. Advantages and disadvantages of prototyping mode .................................................................. 7
4. Agile Software Development ............................................................................................................. 7 **4.1. What is Agile Software Development? ....................................................................................... 7 4.1. What are the benefits of Agile? .................................................................................................. 8
5. Which method is best for tune source and why? ................................................................................ 9 P2 Explain how risk is managed in the Spiral lifecycle model. ......................................................................... 9**
6. Introduction of Risk ........................................................................................................................... 9
7. Inportance of risk management ....................................................................................................... 10 3. Risk management Process ............................................................................................................... 11 4. Identify some risks in Tune Source project ....................................................................................... 11 5. Discuss an approach to manage them .............................................................................................. 11 M1 Describe, with an example, why a particular lifecycle model is selected for a development environment. .................................................................................................................................................................. 12

1. Introduction selecting a Software Development Life Cycle ( SDLC) .................................................... 12 2. Discuss the suitability of each of the SDLC models for the project. For each model, specify whether it is most, moderately or least suitable. ......................................................................................................... 13 2.1. Waterfal model ........................................................................................................................ 13 2.2. Protyping model ...................................................................................................................... 14 2.3. Spiral model ............................................................................................................................ 14 2.4. Agile Software development .................................................................................................... 14 D1 Assess the merits of applying the Waterfall lifecycle model to a large software development project. ..... 15
2. Introduction of waterfall life cycle model ......................................................................................... 15 2. Evaluation The Merits to apply the Waterfall model In large Project ................................................. 15 **2.1. The Waterfall Model In Large Project........................................................................................ 15 2.2. Case Study Design .................................................................................................................... 16 2.3. Threats to Validit ..................................................................................................................... 16
3. Conclusion ...................................................................................................................................... 16 P3 Explain the purpose of a feasibility report. ............................................................................................. 17**
4. What is a feasibility report? ............................................................................................................. 17 2. Purpose of each element in a Basic Feasibility Report....................................................................... 17 2.1. Introduction of Basic Feasibility Report .................................................................................... 17 2.2. Purpose of four elements ......................................................................................................... 17 P4 Describe how technical solutions can be compared. ............................................................................... 19
5. Introduction of a feasibility study .................................................................................................... 19 2. Technical Feasibility ........................................................................................................................ 19 2.1. What is Technical Feasibility? .................................................................................................. 19 2.2. Can we build it? ...................................................................................................................... 19
6. Economic Feasibility ........................................................................................................................ 20 3.1. What is Economic Feasibility? .................................................................................................. 20 3.2. Should we build it? .................................................................................................................. 20
7. Organizational Feasibility ................................................................................................................ 21 4.1. What is Organization Feasibility? ............................................................................................. 21 4.2. If we build it, will they come? .................................................................................................. 21

REFERENCES ............................................................................................................................................... 40

List of Figures

Figure 1 Software Development Life Cycles ............................................................................................................. 1 Figure 2 Original Waterfall Model ............................................................................................................................ 2 Figure 3 Prototyping Mode ....................................................................................................................................... 4 Figure 4 Spiral Model ................................................................................................................................................ 6 Figure 5 Agile Software Development ...................................................................................................................... 8 Figure 7 Key Customer Phase I ............................................................................................................................... 33 Figure 8 Key Customer Phase II .............................................................................................................................. 35

John and Phil partnered to open a number of brick and mortar stores in southern California specializing in hard-to-find and classic jazz, rock, country, and folk recordings. Megan soon was invited to join the partnership because of her contacts and knowledge of classical music. Tune Source quickly became known as the place to go to find rare audio recordings. Annual sales last year were $40 million with annual growth at about 3%–5% per year. Tune Source currently has a website that enables customers to search for and purchase CDs. This site was initially developed by an Internet consulting firm and is hosted by a prominent local Internet Service Provider (ISP) in Los Angeles. The IT department at Tune Source has become experienced with Internet technology as it has worked with the ISP to maintain the site.

System Request

Project Sponsor : Carly Edwards, Assistant Vice President, Marketing Business Need : This project has been initiated to increase sales by creating the capability of selling digital music downloads to customers through kiosks in our stores, and over the Internet using our website. Business Requirements : Using the Web or in-store kiosks, customers will be able to search for and purchase digital music downloads. The specific functionality that the system should have includes the following:

• Search for music in our digital music archive.
• Listen to music samples.
• Purchase individual downloads at a fixed fee per download.
• Establish a customer subscription account permitting unlimited downloads for a monthly fee. Purchase music download gift cards. Business Value : We expect that Tune Source will increase sales by enabling existing customers to purchase specific digital music tracks and by reaching new customers who are interested in our unique archive of rare and hard-to-find music. We expect to gain a new revenue stream from customer subscriptions to our download services. We expect some increase in cross-selling, as customers who have downloaded a track or two of a CD decide to purchase the entire CD in a store or through our website. We also expect a new revenue stream from the sale of music download gift cards. Conservative estimates of tangible value to the company include the following:
• $757,500 in sales from individual music downloads
• $950,000 in sales from customer subscriptions
• $205,000 in additional in-store or website CD sales
• $153,000 in sales from music download gift cards Special Issues or Constraints:
• The marketing department views this as a strategic system. The ability to offer digital music downloads is critical in order to remain competitive in our market niche. Our music archive of rare and hard-to-find music is an asset that is currently underutilized.

Learning Outcomes and Assessment Criteria Pass Merit Distinction LO1 Describe different software development lifecycles D1 Assess the merits of applying the P1 Describe two iterative and two sequential software lifecycle models. P2 Explain how risk is managed in the Spiral lifecycle model. M1 Describe, with an example, why a particular lifecycle model is selected for a development environment. Waterfall lifecycle model to a large software development project. LO2 Explain the importance of a feasibility study D2 Assess the impact of different P3 Explain the purpose of a feasibility report. P4 Describe how technical solutions can be compared. M2 Discuss the components of a feasibility report. feasibility criteria on a software investigation.

LO1 Describe different software development lifecycles

P1 Describe two iterative and two sequential software lifecycle models.

• Iterative models:- Spiral:Spiral Model is a combination of a waterfall model and iterative model. Each phasein spiral model begins with a design goal and ends with the client reviewing the progress. Software development life cycle (SDLC) is a series of phases that provide a common understanding of the software building process. How the software will be realized and developed from the business understanding and requirements elicitation phase to convert these business ideas and requirements into functions and features until its usage and operation to achieve the business needs. The good software engineer should have enough knowledge on how to choose the SDLC model based on the project context and the business requirements. Therefore, it may be required to choose the right SDLC model according to the specific concerns and requirements of the project to ensure its success. I wrote another article on how to choose the right SDLC, you can follow this link for more information. Moreover, to learn more about Software Testing life cycles and SDLC phases you follow the links highlighted here. In this article, we will explore the different types of SDLC models and the advantages and disadvantages of each one and when to use them. You can think of SDLC models as tools that you can use to better deliver your software project. Therefore, knowing and understanding each model and when to use it, the advantages and disadvantages of each one are important to know which one is suitable for the project context.

Projects which not focus on changing the requirements, for example, projects initiated from a request for proposals (RFPs), the customer has a very clear documented requirements V-Shaped Model Description It is an extension of the waterfall model, Instead of moving down in a linear way, the process steps are bent upwards after the implementation and coding phase, to form the typical V shape. The major difference between the V-shaped model and waterfall model is the early test planning in the Vshaped model. Each phase of Spiral Model is divided into four quadrants as shown in the above figure. The functions of these four quadrants are discussed below-

1. Objectives determination and identify alternative solutions : Requirements are gathered from the customers and the objectives are identified, elaborated and analyzed at the start of

every phase. Then alternative solutions possible for the phase are proposed in this quadrant.

2. Identify and resolve Risks : During the second quadrant all the possible solutions are evaluated to select the best possible solution. Then the risks associated with that solution is identified and the risks are resolved using the best possible strategy. At the end of this quadrant, Prototype is built for the best possible solution.
3. Develop next version of the Product : During the third quadrant, the identified features are developed and verified through testing. At the end of the third quadrant, the next version of the software is available.
4. Review and plan for the next Phase: In the fourth quadrant, the Customers evaluate the so far developed version of the software. In the end, planning for the next phase is started. A risk is any adverse situation that might affect the successful completion of a software project. The most important feature of the spiral model is handling these unknown risks after the project has started. Such risk resolutions are easier done by developing a prototype. The spiral model supports coping up with risks by providing the scope to build a prototype at every phase of the software development. Prototyping Model also support risk handling, but the risks must be identified completely before the start of the development work of the project. But in real life project risk may occur after the development work starts, in that case, we cannot use Prototyping Model. In each phase of the Spiral Model, the features of the product dated and analyzed and the risks at that point of time are identified and are resolved through prototyping. Thus, this model is much more flexible compared to other SDLC models. The Spiral model is called as a Meta Model because it subsumes all the other SDLC models. For example, a single loop spiral actually represents the Iterative Waterfall Model. The spiral model incorporates the stepwise approach of the Classical Waterfall Model. The spiral model uses the approach of Prototyping Model by building a prototype at the start of each phase as a risk handling technique. Also, the spiral model can be considered as supporting the evolutionary model – the iterations along the spiral can be considered as evolutionary levels through which the complete system is built. Advantages of Spiral Model : Below are some of the advantages of the Spiral Model.

• Risk Handling: The projects with many unknown risks that occur as the development proceeds, in that case, Spiral Model is the best development model to follow due to the risk analysis and risk handling at every phase.
• Good for large projects: It is recommended to use the Spiral Model in large and complex projects. Advantages Disadvantages

P2 Explain how risk is managed in the Spiral lifecycle model.

The Spiral model is called as a Meta Model because it subsumes all the other SDLC models. For example, a single loop spiral actually represents the Iterative Waterfall Model. The spiral model incorporates the stepwise approach of the Classical Waterfall Model. The spiral model uses the approach of Prototyping Model by building a prototype at the start of each phase as a risk handling technique. Also, the spiral model can be considered as supporting the evolutionary model – the iterations along the spiral can be considered as evolutionary levels through which the complete system is built. Advantages of Spiral Model : Below are some of the advantages of the Spiral Model.

• Risk Handling: The projects with many unknown risks that occur as the development proceeds, in that case, Spiral Model is the best development model to follow due to the risk analysis and risk handling at every phase.
• Good for large projects: It is recommended to use the Spiral Model in large and complex projects.

final Effective risk management must be totally integrated into the System Development Life Cycle. Risk management can be performed in support of each system development life cycle phase. Phase 1—Initiation

• Identified risks are used to support the development of the system requirements, including security requirements, and a security concept. Phase 2—Development or Acquisition
• The risks identified during this phase can be used to support the security analyses of the IT system that may lead to architecture and design tradeoffs during system development of operations (strategy) decision Phase 3— The risk management process supports the assessment of the system implementation against its requirements and within its modeled operational environment. Decisions regarding risks identified must be made prior to system operation Phase 4—Operation or Maintenance
• Risk management activities are performed for periodic system reauthorization (or reaccreditations) or whenever major changes are made to an IT system in its operational, production environment (e.g., new system interfaces) Phase 5—Disposal
• Risk management activities are performed for system components that will be disposed of or replaced to ensure that the hardware and software are properly disposed of, that residual data is appropriately handled, and that system migration is conducted in a secure and systematic manner 3. Risk management Process - Risk management process involves: ▪ Identify Organizational Risks: By surveys, interviews, and solicitation of input across divisions and departments of Probability - The likelihood of risk getting realized. ▪ Inherent Risk - The nature of the risk event. ▪ Mitigation Control Effectiveness - The effectiveness of mitigation plans. 4. Identify some risks in Tune Source project

• We all understand that there are risks in the world. All of us as investors are aware that risks also exist in our portfolios. To put it simply, risk is the likelihood of loss. When we think of losses as an investor, we often think of the primary value of what we own diminish, but this type of risk (known as market risk) is only is one of the many types of risks that investors should consider alongside different types of risk management.
• Other types of risks that are important to any investor's consideration include, but are not limited to: + Longevity Risk + Inflation Risk + Sequence of Returns Risk + Interest Rate Risk + Liquidity Risk 5. Discuss an approach to manage them
• Because no two projects are exactly alike, the risk management approach and plan should be tailored to the scope and complexity of individual projects. Other considerations include the roles, responsibilities, and size of the project team, the risk management processes required or recommended by the government organization, and the risk management tools available to the project.
• Risk occurs across the spectrum of government and its various enterprises, systems- ofsystems, and individual systems. At the system level, the risk focus typically centers on development. Risk exists in operations, requirements, design, development, integration, testing, training, fielding, etc. For systems-of-systems, the dependency risks rise to the top. Working consistency across the system-of-systems, synchronizing capability development and fielding, considering whether to interface, interoperate, or integrate, and the risks associated with these paths all come to the forefront in the system-of- systems environment. At the enterprise level, governance and complexity risks become more prominent. Governance risk of different guidance across the enterprise for the benefit of the enterprise will trickle down into the system-of-systems and individual