Download Assignment 1 - Software Development Life Cycle (1631) and more Study Guides, Projects, Research Information Technology in PDF only on Docsity!
ASSIGNMENT 01 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 0 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Phan Nhat Linh Student ID GCD Class GCD0905 Assessor name Phyo Min Tun 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 Linh Grading grid P 1 P 2 P 3 P4 M 1 M 2 D1 D 2
❒ Summative Feedback: ❒ Resubmission Feedback:
Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date:
Table of Contents
I/ SDLC MODEL ( P1 – P2 – M1 – D1 )
1. What is the Systems Development Life Cycle (SDLC)
Figure 1 : Definition of Systems Development Life Cycle (SDLC) The systems development life cycle (SDLC) is a project management conceptual model that defines the processes involved in an information system development project, from early feasibility studies to application maintenance. SDLC is applicable to both technical and non-technical systems. In most situations, a system is an IT technology that includes both hardware and software. SDLC is often attended by project and program managers, as well as system and software engineers, development teams, and end users. Every hardware or software system must go through a development process, which may be thought of as a multi-step iterative process. The SDLC provides a formal structure and framework for defining the phases and steps required in system development.
Synchronous Data Link Control and software development life cycle are frequently abbreviated as SDLC. The software development life cycle is quite similar to the systems development life cycle, except it is only focused on the software development life cycle.
2. SDLC models (P1)
Figure 2 : SDLC models
2.1 Sequential life cycle model
In this paradigm, the developer must adhere to certain rules, regulations, and set orders in order to complete the project.
➢ Process that is extremely tight and stringent ➢ Cannot go on to the next phase until the prior one is done, which normally extends the schedule. ➢ Methodology is not highly adaptable or cost-effective. When to use the waterfall model: ➢ The application definition is consistent. ➢ The criteria are clearly recognized, explicit, and comprehended. ➢ There should be no ambiguity in the requirements. ➢ The project is much smaller. b. V Shaped model The waterfall model is modified in the V shape. It stresses product verification and validation. All deliverables may be tested, and progress is measured using milestones. Testing occurs along with the development process. Advantages: ➢ Simple and straightforward. ➢ Testing tasks like as planning and developing tests take place prior to coding. This saves a significant amount of time. As a result, the waterfall approach has a better likelihood of success. ➢ Defects are discovered at an early stage with proactive defect tracking. ➢ Prevents the flow of flaws downward. ➢ It works effectively for small projects with simple needs. Disadvantages: ➢ The least flexible and most unyielding. ➢ Because software is built during the implementation phase, no early prototypes are generated. ➢ If any modifications occur in the middle of the project, the test papers and requirement documents must be updated. When to use the V-model:
➢ When the project is modest to medium in size and has well-defined needs. ➢ In the event of a complex project, we employ the v-model.
2.2 Iterative Model
Iterative models are a type of software development lifecycle that focuses on a simple, initial implementation that gradually increases in complexity and feature set until the final system is complete. Improvements in this sort of model may be seen fast as they are implemented during each cycle. Prototype and agile models are the two iterative approaches that I will discuss. Figure 4 : Iterative Model a. Prototype model Prototype model: During the requirement phase, a prototype is created and reviewed by end users. Developers modify the prototype based on customer input to meet the needs of the users. While this approach efficiently finalizes requirements, its usage in a production context may result in quality difficulties, causing the rectification process to continue indefinitely. Advantages:
b. Spiral model Spiral model: Combines waterfall and prototype models. It extends the waterfall approach with 4th generation programming languages, fast application development prototyping, and risk analysis. A preliminary system design is generated once the system requirements have been designed. A first prototype is created and tested. A second prototype is built based on the examination of test findings. Following prototypes are built to assure client satisfaction. The system is built on the final prototype. The completed system has been examined and tested. Though this strategy significantly decreases risk, it may not fulfill the budget and is implemented differently for each application. Advantages: ➢ Software is produced early in the software life cycle. ➢ Risk handling is one of important advantages of the Spiral model, it is best development model to follow due to the risk analysis and risk handling at every phase. ➢ Flexibility in requirements. In this model, we can easily change requirements at later phases and can be incorporated accurately. Also, additional Functionality can be added at a later date. ➢ It is good for large and complex projects. ➢ It is good for customer satisfaction. We can involve customers in the development of products at early phase of the software development. Also, software is produced early in the software life cycle. ➢ Strong approval and documentation control. ➢ It is suitable for high risk projects, where business needs may be unstable. A highly customized product can be developed using this. Disadvantages: ➢ It is not ideal for modest projects due to its high cost. ➢ It is significantly more sophisticated than other SDLC models. The procedure is complicated. ➢ Too reliant on risk analysis and necessitates highly specialized knowledge. ➢ Time management is difficult. Because the number of stages is unknown at the outset of the project, estimating time is challenging. ➢ The spiral might carry on indefinitely.
➢ The project's conclusion may not be known for some time. ➢ It is not appropriate for low-risk projects. ➢ Objective, verifiable milestones may be difficult to establish. A large number of intermediate phases necessitate an abundance of documentation. When to use Spiral model: ➢ When working on a long-term project, the spiral model comes in handy. ➢ When a person is unsure about their expectations ➢ When a new product line is introduced ➢ If the project is critical, ➢ For initiatives with a medium to high chance of failure c. Scrum model Scrum is a project management framework. It adheres to the agile approach and specifies roles, procedures, tools, and processes to ensure that an efficient and successful project is delivered on schedule via iterative development cycles. According to one survey, about 70% of software teams utilize scrum or a scrum hybrid. This technique is mostly used where there is a significant demand for rapid growth and substantial stakeholder participation. The Scrum technique continuously analyzes software development while the project is being built. The Scrum Software Development Methodology places a strong emphasis on accountability, cooperation, and iterative progress toward a well-defined business goal. Advantages: ➢ Transparent approach encourages developers to complete their responsibilities on time. ➢ Defined deadlines at each stage keep developers motivated and empowered. ➢ Feedback at each stage of the project guarantees that a high-quality project is completed.
3.2 The suitable SDLC modal for this project
Figure 5 : Spiral model
- I believe that'spiral model' is the best solution for this project for the following reasons: The Spiral model draws its lead from the Iterative model and its repetition; the project travels through four phases (planning, risk analysis, engineering, and assessment) again and over in a "spiral" until finished, allowing for several rounds of modification. Spiral models are commonly utilized for huge projects. It allows development teams to create a highly personalised product while also incorporating consumer feedback early in the process. Risk management is another advantage of this SDLC strategy. Each iteration begins by anticipating possible hazards and determining how to effectively prevent or manage them. Example:
One of the most intriguing aspects of the SDLC Spiral model is that it was utilized by Microsoft to create early versions of Windows. The approach was also used to create the Gantt chart software. As a result, it comes as no surprise that Spiral Model is used for large, high- risk initiatives that are also aimed at a large audience. Another business that use the Spiral model is game development. As previously stated, the approach enables meticulous and rapid prototyping. Because the gaming business relies significantly on early game versions, Spiral becomes a viable choice. With the strategy, game development businesses may quickly receive feedback from their clients and create a playable that can expand into equally fun games.
4. Discuss the merits of applying the waterfall model to a large software
development project. (D1)
Figure 6 : Waterfall model
which version of the requirements, high maintenance effort, specialized competence focus and lack of confidence in people, and localization issues due to communication barriers.
5. Identify some risks and discuss an approach to manage them (P2)
5.1 What is Risk Management process
Risk management is the process of discovering, analyzing, and controlling hazards to an organization's capital and revenues. These risks arise from a range of sources, including financial uncertainty, legal obligations, technical challenges, strategic management failures, accidents, and natural disasters. A good risk management program assists a company in considering the complete spectrum of risks it confronts. Risk management also investigates the link between risks and the cascading effect they may have on an organization's strategic goals.
Figure 7 : Risk Management process Because of its emphasis on predicting and understanding risk throughout a company, this holistic approach to risk management is also referred to as enterprise risk management. Enterprise risk management (ERM) highlights the necessity of managing positive risk in addition to focusing on internal and external threats. Positive risks are opportunities that, if not accepted, can either improve corporate value or harm a firm. Indeed, the goal of any risk management program is not to remove all risk, but rather to protect and create value to the organization by making prudent risk decisions.
