Download ASM 1 1631 software development life cycle and more Lecture notes Software Development in PDF only on Docsity!
Assignment Brief 01 (RQF)
Higher National Certificate/Diploma in Business
Student Name/ID Number: Ly Nguyen Unit Number and Title: Unit 09: Software Development Life Cycle Academic Year: 2022 Unit Assessor: Assignment Title: Plan a software development life cycle Issue Date: 07/12/ Submission Date: Internal Verifier Name: Date: Submission Format: Format: ● The submission is in the form of 1 document. ● You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3 and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation and references must follow the Harvard referencing style. Submission: ● Students are compulsory to submit the assignment in due date and in a way requested by the Tutor. ● The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/. ● Remember to convert the word file into PDF file before the submission on
CMS.
Note: ● The individual Assignment must be your own work, and not copied by or from another student. ● 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 understand and follow the guidelines to avoid plagiarism. Failure to comply this requirement will result in a failed assignment. Unit Learning Outcomes: LO1 Describe different software development lifecycles. LO2 Explain the importance of a feasibility study. Assignment Brief and Guidance: Assignment scenario Tune Source is a company headquartered in southern California. Tune Source is the brainchild of three entrepreneurs with ties to the music industry: John Margolis, Megan Taylor, and Phil Cooper. Originally, John and Phil partnered to open a number of brick-and-mortar stores in southern California specialising 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.
● Because customers have a number of music download options available to them elsewhere, we need to bring this system to the market as soon as possible. Tasks Complete the following tasks: Task 1 – SDLC model You are a project manager of a company named ABC. Your company has been hired by Tune Source to carry out a project that helps them develop a software for the requirements specified in the system request. As the first step, you need to:
- Describe the following SDLC models: waterfall, v-model, prototyping, scrum and spiral. Choose one that you think suitable for the project and explain why. ● 350 - 500 words for each model. ● Explanation: 400 – 600 words. Discuss the suitability of each of the SDLC models for the project. For each model, specify whether it is most, moderately or least suitable. ● Word limit: 800 - 1000 words. Discuss the merits of applying the waterfall model to a large software development project. ● Word limit: 800 – 1200 words.
- Identify some risks and discuss an approach to manage them. You will have the present what is Risk Management process with clear illustrations and explanations. Then you will create a Risk Management Matrix to assess and manage risks of Tune Source project. ● Word limit: 600 – 1000 words. Task 2 – Feasibility study
- Discuss the purpose of conducting a feasibility study for the project.
● Word limit: 400 – 600 words.
- Discuss how the three feasibility criteria (technical, economic, organizational) are applied to the project. Discuss whether the project is feasible. Discuss alternative technical solutions using the alternative matrix. ● Word limit: 1200 – 1500 words.
- Explain the components of a feasibility report. Discussion economic feasibility study on Tune Source project (NPV, Cashflow, Break-Even Point) ● Word limit 350 – 500 words. Discussion organizational feasibility study on Tune Source project ● Word limit 350 – 500 words.
- Assess the impact of each feasibility criterion on a software investigation. Discussion and represent as feasibility alternatives matrix for Tune Source project ● Word limit: 500 – 700 words.
ASSIGNMENT 01 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Ly Nguyen Student ID GCS Class GCS1003A Assessor name Vo Ngoc Mai Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature
Grading grid P1 P2 P3 P4 M1 M2 D1 D
❒ Summative Feedback: ❒ Resubmission Feedback:
Grade: Assessor Signature: Date:
Table of Contents
- P1 - Describe two iterative and two sequential software lifecycle models...................
- Waterfall Model.....................................................................................................
- Prototyping Model.................................................................................................
- Agile Model............................................................................................................
- Spiral Model...........................................................................................................
- Conclusion..............................................................................................................
- P2 - Explain how risk is managed in the Spiral lifecycle model.....................................
- Introduction...........................................................................................................
- Risk management in the software projects...........................................................
- Risk Management Process.....................................................................................
- List out common risks of a software project..........................................................
- Some risks that the Tune Source project may face...............................................
- P3 - Explain the purpose of a feasibility report.............................................................
- Feasibility report....................................................................................................
- The purpose of feasibility.......................................................................................
- Discuss the purpose of conducting a feasibility study...........................................
- Basic Feasibility Report Template..........................................................................
- P4 - Describe how technical solutions can be compared..............................................
- Discuss how the three feasibility criteria...............................................................
- Discuss alternative technical solutions using the alternative matrix....................
- Conclusion..............................................................................................................
- References......................................................................................................................
- Figure 1: Waterfall Model.............................................................................................. Table of Figure
- Figure 2: Prototype Model.............................................................................................
- Figure 3: Agile Model.....................................................................................................
- Figure 4: Props and Cons of Agile Model (Verma, 2015)...............................................
- Figure 5: Spiral Model....................................................................................................
System Design − The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture. Implementation − With inputs from the system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing. Integration and Testing − All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures. Deployment of system − Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market. Maintenance − There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment. Waterfall Model - Advantages The advantages of waterfall development are that it allows for departmentalization and control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process model phases one by one. Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order. Some of the major advantages of the Waterfall Model are as follows − Simple and easy to understand and use
Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review process. Phases are processed and completed one at a time. Works well for smaller projects where requirements are very well understood. Clearly defined stages. Wells understood milestones. Easy to arrange tasks. Process and results are well documented. Waterfall Model - Disadvantages The disadvantage of waterfall development is that it does not allow much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-documented or thought upon in the concept stage. The major disadvantages of the Waterfall Model are as follows − No working software is produced until late during the life cycle. High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. Not suitable for the projects where requirements are at a moderate to high risk of changing. So, risk and uncertainty is high with this process model. It is difficult to measure progress within stages. Cannot accommodate changing requirements. Adjusting scope during the life cycle can end a project. Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological or business bottleneck or challenges early.
Prototyping Model
The Prototyping Model is a methodology that is treated as a model for software development where a prototype - which is a premature approximated sample of the final product, is constructed and then tested. After that rework is done on that unfinished product as per requirement in anticipation of building a suitable prototype that is, at last, attain after the entire software is developed and then it is delivered to the customer. It is a useful model for those whose project requirement is not fully known or there is a constant update required based on customer satisfaction. It can be considered as a trial-and-error method which takes place involving the developers as well as the users. (W3school, 2022)
Feasibility study In the next phase, the BA, HR, Architecture and Finance team leaders will sit together and talk about the cost of the product, what resources will be needed, what technology is used to develop the product and how much will be needed. time. for product completion and delivery. Create prototypes Once the feasibility study is completed, we will move on to the next phase where we will create a Prototype (prototype or mock) based on the data collected from the client and the web developer will design the Prototype. Here, we have the following Prototypes:
- Static prototype In Static Prototype we keep the entire Prototype of requirements in one word document with all instructions, screenshots and description on how to build the software, what the finished product will look like and how will it work, etc..
- Dynamic prototype The dynamic prototype is parallel to the browser, but here we can't give any details, only the functionality is there without data entry. It's like a dummy page made out of html with tags and links to different pages with expressive features of the product. Prototype testing After we build the Prototype, the BA checks the Prototype and does a round of Prototype testing. Customer review and approval Once Prototype testing is done, it will be delivered to the customer for their review and approval. If the customer is not satisfied with the given sample, we will change the test sample based on the customer's instructions and feedback. This process will continue until the customer approves and is satisfied with the Prototype. It takes a bit of time because we have to redo the changes in Prototype.
Design Once the approved Prototype is received, we will begin high-level and low- level design of the final product and review all the proposals the customer makes at the time of final prototyping. Coding Once the design phase has been successfully completed, we move on to our coding phase where the developer involved starts developing the product based on their programming knowledge. Testing After compiling the development phase, it is handed over to the test engineer. And the test engineer checks the application functionality and all inputs and outputs. Installation and maintenance Once our final product is developed and tested to the final Prototype, it goes into production. And the product will be serviced over time to minimize any disruptions, helping to avoid significant breakdowns. Advantages of Prototype Model
- Active involvement : In this model, the users are involved actively in the development phase and, thus, it is easier to develop the model according to their preferences.
- Easy detection of missing functionality: The missing functionality in the prototype model is easily detectable.
- Quick feedback : Since the customer has direct interaction with the prototype model, their feedback is much faster. These feedbacks are essential since they are taken into consideration while creating the final system.
- Customer satisfaction : The prototype model provides more significant customer satisfaction. The customer can feel the product and make actual contact with it from a very early stage and can also understand the needs of the product much better.
- Flexibility : The prototype model is flexible. It can be easily changed and modified according to the preferences and needs of the customer or the developer. Furthermore, the developer can reuse the prototype for future use in more complicated projects.
Figure 3 : Agile Model Phases of Agile Model: Requirements gathering: In this phase, you must define the requirements. Explain business opportunities and plan the time and effort needed to build the project. Based on this information, you can evaluate technical and economic feasibility. Design the requirements: When you have identified the project, work with stakeholders to define requirements. Use the user flow diagram or the high- level UML diagram to show the work of new features and show how it will apply to your existing system. Construction/ iteration: When the team defines the requirements, the work begins. Designers and developers start working on their project, which aims to deploy a working product. The product will undergo various stages of improvement, so it includes simple, minimal functionality. Testing: In this phase, the Quality Assurance team examines the product's performance and looks for the bug.
Deployment: In this phase, the team issues a product for the user's work environment. Feedback: After releasing the product, the last step is feedback. In this, the team receives feedback about the product and works through the feedback. Agile Testing Methods:
1. Scrum SCRUM is an agile development process focused primarily on ways to manage tasks in team-based development conditions. There are three roles in it, and their responsibilities are: - Scrum Master: The scrum can set up the master team, arrange the meeting and remove obstacles for the process - Product owner: The product owner makes the product backlog, prioritizes the delay and is responsible for the distribution of functionality on each repetition. - Scrum Team: The team manages its work and organizes the work to complete the sprint or cycle. 2. Crystal: There are three concepts of this method- Chartering: Multi activities are involved in this phase such as making a development team, performing feasibility analysis, developing plans, etc. Cyclic delivery: under this, two more cycles consist, these are: - Team updates the release plan. - Integrated product delivers to the users. Wrap up: According to the user environment, this phase performs deployment, post-deployment. 3. Dynamic Software Development Method (DSDM): DSDM is a rapid application development strategy for software development and gives an agile project distribution structure. The essential features of DSDM are that users must be actively connected, and teams have been given the right to make decisions. The DSDM project contains seven stages: - Pre-project - Feasibility Study - Business Study - Functional Model Iteration
