Higher Nationals in Computing
Unit 9: Software Development Life Cycle
ASSIGNMENT 1
Assessor name: PHAN MINH TAM
Learner’s name: Nguyễn ThànhThông
ID: GCS210147
Class: GCS1005A
Subject code: 1631
Assignment due: Assignment submitted:
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software Development Life Cycle (SDLC) for Tune Source Project, Assignments of Software Development
An overview of the software development life cycle (sdlc) and its various models, including the waterfall, v-model, scrum, and spiral models. It discusses the suitability of each sdlc model for the tune source project, which aims to develop a software system for selling digital music downloads through web and in-store kiosks. The document also covers risk management processes, feasibility studies (economic and organizational), and requirement elicitation techniques. It serves as a comprehensive guide for the project manager to plan and execute the tune source software development project effectively.
Typology: Assignments
2022/2023
1 / 30
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software Development Life Cycle (SDLC) for Tune Source Project and more Assignments Software Development in PDF only on Docsity!
Higher Nationals in Computing
Unit 9: Software Development Life Cycle
ASSIGNMENT 1
Assessor name: PHAN MINH TAM
Learner’s name: Nguyễn Thành Thông
ID: GCS
Class: GCS1005A
Subject code: 1631
Assignment due: Assignment submitted:
ASSIGNMENT 1 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Nguyễn Thành Thông Student ID GCS Class GCS1005A Assessor name Phan Minh Tam 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
Assignment Brief 01 (RQF)
Higher National Certificate/Diploma in Business
Student Name/ID Number: Unit Number and Title: Unit 09: Software Development Life Cycle Academic Year: 2021 – 2022 Unit Assessor: TamPM Assignment Title: Plan a software development life cycle Issue Date: 10/Jan/ 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. 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
● 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.
Learning Outcomes and Assessment Criteria (Assignment 01): Learning Outcome Pass Merit Distinction LO1 Describe different software development lifecycles 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. D1 Assess the merits of applying the Waterfall lifecycle model to a large software development project. LO2 Explain the importance of a feasibility study P3 Explain the purpose of a feasibility report. P4 Describe how technical solutions can be compared. M2 Discuss the components of a feasibility report. D2 Assess the impact of different feasibility criteria on a software investigation.
- Unit 9: Software Development Life Cycle ASSIGNMENT
- Assignment Brief 01 (RQF)
- Higher National Certificate/Diploma in Business
- ASSIGNMENT 1 ANSWERS
- P1 Describe two iterative and two sequential software lifecycle models.
- Introduction to SDLC
- 1.1 Definition of SDLC
- 1.2 Purpose of SDLC
- Two sequential software lifecycle models
- 2.1 Waterfall model
- 2.2 V model
- Two iterative software lifecycle models
- 3.1 Scrum
- 3.2 Spiral model
- The model is used in the Tune Source project
- P2 Explain how risk is managed in the Spiral lifecycle model.
- Risk management
- Risk management process
- Risk management matrix in Tune Source project
- 7: Risk assessment matrix ( https://bigpicture.one/project-risk-assessment-examples/)
- How to manage risks in the Spiral lifecycle model
- P3 Explain the purpose of a feasibility report.
- What is a feasibilty study
- The purpose of a feasibility report
- Feasibility study on Tune Source project
- P4 Describe how technical solutions can be compared.
- What is requirements
- Types of requirement
- How to determine requirements
- Requirements elicitation techniques
- 4.1 Interviews
- 4.2 Joint Application Development (JAD)
- 4.3 Questionnaires
- 4.4 Document Analysis
- 4.5 Observation
- Comparison of requirements elicitation techniques
- REFERENCES
- Figure 1: SDLC........................................................................................................................................... Tables of Figure
- Figure 2: Waterfall Model
- Figure 3: V-model
- Figure 4: Srcum
- Figure 5: Spiral model
- Figure 6 : Five Steps of Risk Management Process
- Figure 7 : Feasibility Study
- Figure 8 : Requirements
- Figure 9 : Functional requirements
- Figure 10 : Non - functional requirements
P a g e | 1
ASSIGNMENT 1 ANSWERS
P1 Describe two iterative and two sequential software lifecycle models.
1. Introduction to SDLC
1.1 Definition of SDLC
The Software Development Life Cycle, also known as SDLC, is a method for creating software that is of the greatest quality and least expensive in the shortest amount of time. The well-organized phases of the SDLC allow an organization swiftly develop high-quality software that is well-tested and prepared for usage in production. The SDLC involves six phases as explained in the introduction: Planning (Planning) Requirement analysis Software design such as architectural design Implementation Testing (Testing) Maintenance Figure 1: SDLC
P a g e | 3 Figure 2: Waterfall Model Explain: Requirement analysis stage: The client will provide specific requirements for the software system being developed during this phase. Design Stage: Plan a programming language, such as Java, PHP or .net. For example, a database like Oracle, MySQL, etc. Or more high-level technical information relevant to the project. Implementation: The built stage comes after the design stage and consists only of coding the program. Test Stage: You test the program to make sure it was created in accordance with the client's requirements. Deployment Stage: The product tested and deployed the application in the respective environment. Maintenance Stage: Your system is ready to use. In the future, you can require change the code as per customer request. 2.1.2 Advantages ‒ Adapts well to flexible groups. ‒ Suitable for smaller projects with well-defined criteria. ‒ Before each stage is complete, we should conduct a quality assurance test. ‒ Any software modifications are made during the development phase.
P a g e | 4 2.1.3 Disadvantages ‒ Only during this stage can the error be corrected. ‒ Unsuitable for complex projects with constantly changing requirements. ‒ Documentation consumes a significant amount of time. Therefore, there is a chance that bugs will be discovered after the development stage, and fixing them is quite expensive. 2.1.4 When to use ‒ Clear and fixed requirements may not change. ‒ There are no ambiguous requirements (no confusion). ‒ It is good to use this model when the technology is well understood. ‒ Short project and low cast. ‒ Zero or minimal risk.
2.2 V model
2.2.1 Definition The V-model is an SDLC model where execution of processes happens in a sequential manner in a V- shape. It is also known as Verification and Validation model. Figure 3: V-model
P a g e | 6 Figure 4: Srcum Explain: Product backlog: It is a list of items that must be completed in order to develop a product, and it may contain everything from technology research to fixing bugs to different product functionality. Sprint planning: Sprint is a development phase that has a duration of 1-4 weeks. To prepare for each Sprint the team needs to meet to determine what functionality (story) will develop during this phase (sprint backlog), expected output (Goal, Release result), Estimate (who does what) and discuss solutions. All are recorded in minutes to have a basis for implementation and review later. Sprint backlog: Is is a list of items the team agrees to complete in the Sprint following the Sprint review. Daily Scrum meetings: It is a 24-hour stand-up meeting where each team member talks about their goals and any issues that arise. Sprint review meetings: At the end of each Sprint, the team presents the work they have completed at the review meeting. Sprint retrospective meetings: At the end of each Sprint, the team reflects on how well they work together and discusses any changes that need to be made in the next Sprint. 3.1.2 Advantages ‒ A transparent system encourages developers to complete their tasks and deliver them on time. ‒ Defined deadlines at each stage keep developers motivated and empowered at all times. ‒ Feedback^ at^ each^ stage^ of^ the^ project^ guarantees^ that^ a^ high-quality^ result^ is^ produced^ in^ the^ end. 3.1.3 Disadvantages ‒ Difficulty planning, structuring and managing projects without defined goals and vision. ‒ Frequent changes in the project cause delays in the project's handover schedule. ‒ More resources are used and stakeholders engage in minute-by-minute detailed revisions and debates 3.1.4 When to use
- When requirements are not clearly defined.
P a g e | 7
- When the probablity of changes during the development is high.
- When there is a need to test the solution.
- When the team has self-management skills.
3.2 Spiral model
3.2.1 Definition The Spiral Paradigm is a software development process model that is risk-driven. It is a hybrid of the waterfall and iterative models. Figure 5: Spiral model Explain: Planning: Collect and analyze project requirements from customers ( estimating cost, shedule-master, (identifying necessary resources and work environment, Bussiness Requirement Specifications and System Requirement specifications ). Risk Analysis: Potential risks and offer alternative solutions. Engineering: The devs conduct the code, the testers conduct the testing and deploying the software on the customer's web. Evaluation: The customer will evaluate the work, the product and ensure that the product meets all the requirements set forth previously. 3.2.2 Advantages
- High amount of risk analysis. Thus risk avoidance is enhanced.
P a g e | 9 P2 Explain how risk is managed in the Spiral lifecycle model.
1. Risk management A risk management is the process of identifying, analyzing, measuring, and evaluating risk. The complexity of the project and the maturity of the organization are considered as key factors that can affect the success of the project. 2. Risk management process All the five steps Risk management process: Step 1: Risk Identification Step 2: Risk Assessment and Analysis Step 3: Risk Evaluation and Prioritization Step 4: Risk Response and Treatment Step 5: Risk Control Figure 6 : Five Steps of Risk Management Process
P a g e | 10
3. Risk management matrix in Tune Source project A project risk matrix, commonly referred to as a probability and severity risk matrix, is a table-like graphical tool for risk analysis (matrix). Most risk matrices are square, although some are rectangular or round. You may quickly assess project risks and the seriousness of their repercussions using a risk matrix (impact). Based on two overlapping elements, you utilize it to assign ratings for each risk: The likelihood (or likelihood) of a risk to occur (x-axis). The impact (or severity) if a risk occurs (y-axis). Impact Likehood Very unlikely to happen Unlikely to happen Possibly could happen Likely to happen Very likely to happen Catastrophic consequences Significant consequences Server crash Moderate consequences Customer data stolen Personnel conflict The system does not meet the needs of customers Low consequences late for the deadline Data is not secure Negligible consequences Not enough manpower Untrained and inexperienced human resources stolen data Table 1: Risk assessment matrix This might be a problem for projects that use Tune Source. The chance of danger is categorized using five percentage ranges: