Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Outline for assignment 1_Professional Practice, Assignments of Computer Science

Outline for assignment 1_Professional Practice

Typology: Assignments

2021/2022

Uploaded on 06/13/2023

trung-nguyen-42
trung-nguyen-42 🇻🇳

6 documents

1 / 20

Toggle sidebar

Related documents


Partial preview of the text

Download Outline for assignment 1_Professional Practice and more Assignments Computer Science in PDF only on Docsity! ASSIGNMENT 01 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09: Software Development Life Cycle Submission date May 19, 2023 Date Received 1st submission May 19, 2023 Re-submission Date June 5, 2023 Date Received 2nd submission June 5, 2023 Student Name Phan Trung Nguyen Student ID GCH200685 Class GCH1106 Assessor name Nguyen The Lam Tung 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 Nguyen Grading grid P1 P2 P3 P4 M1 M2 D1 D2 ❒ Summative Feedback: ❒ Resubmission Feedback: Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date: Introduction 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 specializing in hard-to-find and classic jazz, rock, country, and folk recordings. 1 SDLC model 1.1 What is SDLC model? A framework that describes the many phases of software development is known as the SDLC (Software Development Life Cycle) model. Phases including planning, analysis, design, implementation, testing, and maintenance are frequently included. In order to assure quality, effectiveness, and consistency across the software development process, the SDLC model was created. There are several SDLC models, including the Waterfall model, Agile model, V-model, Scrum and Spiral model, each having distinct advantages and disadvantages. Figure 1 SDLC 1.2 Waterfall model One notable software development methodology is The Waterfall model that follows a structured approach consisting of several distinct phases: requirements gathering, design, implementation, testing, deployment and maintenance. This model has proven efficient due to its clear standards but can also be rigid when implementing any change across stages. model is an organized method of developing software that makes sure each stage of the process is finished before going on to the next. By doing so, mistakes are reduced and the end result is guaranteed to satisfy the stakeholders' needs. Figure 3V-model - In the V-model, each phase of the development process has a corresponding testing phase. The testing phases are designed to verify that the work done in the previous phase was done correctly and meets the requirements.  Requirements gathering -> Requirements verification.  Design -> Design verification  Implementation -> Unit testing  Integration -> Integration testing  System testing -> Acceptance testing  Maintenance -> Regression testing 1.4 Prototyping The prototyping is a software development model that involves creating a working prototype of the software before developing the final product. This prototype is used to get feedback from consumers and stakeholders, which is then utilized to develop and refine the finished product. The Prototyping Model is useful for projects where requirements are not well defined or are likely to change, as it allows flexibility and iteration throughout the development process. However, it can also cost more time and money than other models, as multiple prototypes may need to be created and tested before the final product is developed. Figure 4 Prototyping model 1.5 Scrum model The Scrum model is an Agile software development framework that emphasizes collaboration, flexibility, and iterative development. It involves a team-based approach to project management, with a focus on delivering working software in short iterations or sprints. The Scrum model includes several key roles, including the Product Owner, Scrum Master, and Development Team, as well as several ceremonies, such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The Scrum model is useful for projects where the requirements are likely to change or are not well-defined, as it allows for flexibility and adaptation throughout the development process. (Lutkevich, n.d.) 1.7 The model that suitable for the project By the information had given, the project has the income about 2 million USD, so this Is a large-scale project. The waterfall is an old model and is used for small project, it would be very risky to use waterfall model on this project. V-model also does not meet the requirements of this project, this model doesn't include risk analysis activities, making it difficult to control risks and increasing the likelihood that projects would fail. The Spiral Model is a useful methodology for software development projects that are complex, have changing requirements, or have a high level of risk. It allows for iterative development and testing, continuous feedback and adaptation, and prioritization of critical features and functionality. So Spiral model will be the best choice for this project 2 Explain how risk is managed in the Spiral lifecycle model 2.1 What is risk management The process of detecting, evaluating, and prioritizing risks as well as creating mitigation or avoidance plans is known as risk management. It entails assessing potential risks and how they can affect a project or an organization, as well as creating measures to reduce or eliminate such risks. In order to accomplish projects on schedule, within budget, and with little disruption or negative impact, risk management is a crucial component of project management. (Tucci, n.d.) 2.2 Some risk Tune Source may face No. Risk possibility Cause Consequence Solution 1 Code issues High Code issues can be caused by a variety of factors, including syntax errors, logic errors, and runtime errors Take more time to complete the project Figure out and fix the code ASAP 2 Lack of personnel low Employees are resigned, fired or are not qualified Take more time to complete the project Prepare more employees than needed, choose those who meet the requirements 3 Budget risk low the requested amount exceeds the budget amount will have to spend an extra amount and re-plan Take advantage of available items to reduce costs
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved