Download Assignment 1 - Software Development Life Cycle (SDLC) - PASS and more Assignments Computer Science in PDF only on Docsity!
ASSIGNMENT 1 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 0 9: Software Development Life Cycle Submission date 22 /06/2022 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Huynh Minh Huy Student ID GCD Class GCD1001^ Assessor name Tran Trong Minh 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 Huy
Grading grid P1 P2 P3 P4 M1 M2 D1 D
Summative Feedback: Resubmission Feedback:
Grade: Assessor Signature: Date: Lecturer Signature:
- Task 1: SDLC Model.
- I. Sequential Models.
- II. Iterative Models.
- Spiral Model.
- Agile Model.
- Task 2: Explain how risk is managed in the spiral lifecycle model
- I. Identify Risk.
- Definition of Risk in a Project.
- Identifying Risk in Tune Source.
- II. Which is most suitable model for Tune Sources and discuss why?
- Task 3: Explain the purpose of a feasibility report.
- I. Feasibility Report.
- Definition of Feasibility Report.
- The purpose of a Feasibility Report.
- How feasibility is helpful for Undertaking Project.
- II. Feasibility Study.......................................................................................................................................................
- Definition of Feasibility Study.
- The purpose of Feasibility Study for the project.
- Task 4: Describe how technical solution can be compared.
- the project. Discuss whether the project is feasible. I. Discuss how the three feasibility criteria (technical, economic, organizational) are applied to
- Technical Feasibility.
- Economic Feasibility.
- Organizational Feasibility.
- alternative matrix)........................................................................................................................................................... II. Give out at least 02 technical solutions and compare them about feasibility (using the
- Conclusion.
- References
- Figure 1: Waterfall SDLC Model. Table of Figures
- Figure 2: V-shaped SDLC Model.
- Figure 3: Spiral SDLC Model.
- Figure 4: Agile SDLC Model.
- Table 1: Advantages and Disadvantages in Waterfall Model................................................................................. Table of Tables
- Table 2: Advantages and Disadvantages in V Model.
- Table 3: Advantages and Disadvantages in Spiral Model......................................................................................
- Table 4: Advantages and Disadvantages in Agile Model.
- Table 5: Risk Identifying Table
- Table 6: Technical Feasibility
- Table 7: Alternative matrix
Task 1: SDLC Model. I. Sequential Models.
- Waterfall. The Waterfall technique was the first SDLC Model extensively utilized in Software Engineering to assure project success. The entire software development process is separated into phases in "The Waterfall" technique. Typically, the conclusion of one step serves as the input for the following phase in this Waterfall approach. The Waterfall Model's several stages are seen in the figure below. Contextualize to Tune Source Project Requirement Gathering and Analysis: All of the organization's "Tune Source" requirements "In this phase, the system to be built is captured and documented in a requirement specification document." System Design: This phase evaluates the previous phase's requirements specifications and develops the system design. This "Tune Source" system design assists with the specification of hardware and system requirements, as well as the overall system architecture. Figure 1 : Waterfall SDLC Model.
Tasks are simple to organize. Cannot meet changing needs. The process and outcomes are thoroughly documented. Changing the scope of a project during its life cycle might lead to its demise. Integration occurs as a "big-bang" in the end, making it impossible to uncover any technological or commercial bottlenecks or issues early on. Table 1 : Advantages and Disadvantages in Waterfall Model.
- V model. The V-model is an SDLC paradigm in which processes are executed sequentially in a V- shape. It is often referred to as the Verification and Validation model. The V-Model is an extension of the waterfall model that is based on assigning a testing phase to each development step. This means that there is a testing phase for every single phase of the development cycle. This is a very disciplined plan, and the next step begins only once the previous phase is completed. Figure 2 : V-shaped SDLC Model.
V-Model – Verification Phases. The V-Model has numerous Verification steps, each of which is detailed in detail below: Business Requirement Analysis This is the initial stage of the development cycle in which the product needs are understood from the customer's point of view. This phase entails extensive discussion with the consumer to ascertain his expectations and precise requirements. This is a critical operation that must be effectively handled because most clients are unsure about what they require. At this point, acceptance test design is completed since business requirements may be utilized as input for acceptance testing. System Design It is time to design the entire system if you have clear and thorough product requirements. The system design will comprehend and detail the whole hardware and communication architecture for the product being developed. The system test plan is created using the system design. Doing so sooner allows you more time for real test execution later. Architectural Design During this phase, architectural specifications are understood and designed. Typically, more than one technological method is presented, and the ultimate selection is made based on technical and budgetary feasibility. The system design is further subdivided into modules that perform distinct functions. This is also known as High Level Design (HLD). In this level, data flow and communication between internal modules and with the outside world (other systems) are thoroughly known and specified. During this step, integration tests may be built and documented using this knowledge.
System Testing System testing is inextricably linked to the system design process. System tests verify the overall functionality of the system as well as the communication of the system under development with external systems. During this system test, the majority of software and hardware compatibility issues can be discovered. Acceptance Testing Acceptance testing is linked to the business requirement analysis phase and entails testing the product in a user environment. Acceptance testing reveal compatibility concerns with other systems in the user environment. It also detects non-functional faults in the real user environment, such as load and performance flaws. Advantages Disadvantages Phases are performed one at a time in this highly disciplined methodology. Uncertainty and high risk. Works effectively for smaller projects with well- defined needs. Not suitable for complex, object-oriented programs. Simple to grasp and use. Poor model for long-term projects. Because of the model's rigidity, it is simple to manage. Each phase includes its own set of deliverables and a review procedure. Not appropriate for projects with a moderate to high risk of changing needs. It is tough to update a functionality after an application has entered the testing stage. Until late in the life cycle, no functioning software is developed. Table 2 : Advantages and Disadvantages in V Model.
II. Iterative Models.
- Spiral Model. The spiral model blends the notion of repeated development with the waterfall model's methodical, regulated characteristics. This spiral model is a hybrid of the iterative development process model and the sequential linear development model, often known as the waterfall model, with a heavy emphasis on risk analysis. It enables incremental product launches or incremental refining with each iteration around the spiral. The spiral model is divided into four stages. A software project goes through these phases in iterations known as Spirals. Identification This step begins with acquiring the baseline spiral's business needs. This phase is used to identify system requirements, subsystem requirements, and unit requirements in future spirals as the product grows. This phase also includes continual contact between the client and the system analyst to understand the system requirements. The product is launched in the specified market at the conclusion of the spiral. Design The Design process begins with conceptual design in the baseline spiral and progresses to architectural design, logical module design, physical product design, and final design in successive spirals. Construct or Build At each spiral, the Construct phase relates to the construction of the real software product. In the baseline spiral, while the idea is still being thought about and the design is being developed, a POC (Proof of Concept) is created to get user input.
- Agile Model. The Agile SDLC model is a hybrid of iterative and incremental process models, with a focus on process adaptation and customer satisfaction through quick delivery of functional software. Agile methodologies divide a product into small incremental builds. Iterations of these builds are available. According to the Agile model, each project must be handled differently, and current techniques must be customized to best meet the project objectives. Tasks are grouped into time boxes (short time windows) in Agile to provide particular features for a release. The technique is iterative, with each iteration delivering a viable software build. In terms of features, each build is incremental; the final version contains all of the features requested by the client. Here is a graphical illustration of the Agile Model. Advantages Disadvantages Changing needs can be addressed. Management is becoming increasingly difficult. Prototypes can be used extensively. The project's conclusion may not be known for some time. More precise requirements can be captured. Tiny or low-risk initiatives are not suited, and small projects may be costly. Users first notice the system. The procedure is complicated. Development may be broken into smaller portions, and dangerous aspects can be created early, allowing for better risk management. The spiral might carry on indefinitely. A large number of intermediate steps need an abundance of documentation. Table 3 : Advantages and Disadvantages in Spiral Model.
Contextualize to Tune Source Project. Requirement gathering: In this step, I'll outline the requirements. I'll discuss the commercial potential of the firm "Tune Source" as well as the time and work necessary to complete the project. Based on these data, I can analyze the technical and economic feasibility. Design the requirements: Once I've decided on a project, I'll collaborate with stakeholders to define requirements. Using a user flow diagram or a high-level UML diagram, I may describe how new features function and how they will relate to the existing system of the firm "Tune Source." Iteration: After the team has determined the criteria, the work begins. Designers and engineers start working on the company's "Tune Source" project, which aims to produce a usable product. Before being published, the product will go through multiple rounds of development, therefore it will only have basic, primitive capabilities. Testing: During this phase, the Quality Assurance team examines the product's performance and looks for bugs. Figure 4 : Agile SDLC Model.
There's no need to plan ahead of time if you don't want to. It's simple to use. Allows developers to be more creative. Table 4 : Advantages and Disadvantages in Agile Model. Task 2: Explain how risk is managed in the spiral lifecycle model I. Identify Risk.
- Definition of Risk in a Project. Any unanticipated incident that might have a good or negative impact on your project is referred to be a risk. People, procedures, technology, and resources may all be affected by risks. It's critical to understand that threats and worries are not the same thing. Problems are things you know you'll have to deal with and can even predict when they'll occur, such as a team member's scheduled vacation or a substantial rise in product demand throughout the holiday season. Risks are occurrences that can occur at any moment and that you may not be able to forecast, such as a sudden flu outbreak among your employees or the failure of a critical product component.
- Identifying Risk in Tune Source. If they choose the Spiral Model as the model for building the product, these steps will outline the process of discovering hazards in "Tune Source." 1 st: First, we must identify all risks and organize them into various risk categories, which will assist us in determining which hazards belong to which category and what impact they will have on the project. 2 nd: Second, we must establish the risk's likelihood and effect percentage, and then apply the risk factor method to compute the risk factor %; this percentage will be used to decide risk priority in the following step. The probability percentage denotes the chance of the risk occurring during the project, whereas the impact denotes the severity with which the risk will impair the project.
3 rd: The final step is to rank risks based on their risk factor percent; a risk with a risk factor of 0-30% would be regarded low, meaning that the risk would have little or no influence on the project, and will be prioritized as the last problem to be handled. The effect will be greater and will require quick correction, but not in the 30% to 60% range. The danger with a risk factor percentage of greater than 60% will require immediate resolution. Here is the table that being created to identify some of the risk in developing “Tune Source” using Spiral Model. No Risk Probability Impact Risk factor Risk category Risk response plan 1 The project's facilities and equipment are insufficient. 5% 60% 3% Low This is uncommon since each team member is needed to prepare their own development equipment prior to applying for the project. However, if any equipment is destroyed, resulting in a lack of equipment, I propose borrowing equipment from others and temporarily repairing their equipment. 2 The end product's security is inadequate. 70% 90% 63% High Make sure we develop a test strategy that allows us to test the final product's security
maintain the development process as efficient as possible. Table 5 : Risk Identifying Table II. Which is most suitable model for Tune Sources and discuss why? Based on the intricacy and adaptability of new needs in a rapidly changing market. This project appears to be a good fit for the Agile Model. The following are some of the primary reasons: Given the size of the organization and the number of clients that may contact with this product on a daily basis, the project size is rather large. Websites, particularly e-commerce sites, require frequent updates. This project may have various third-party services that must be integrated with every possible function. The utilization of different development platforms may pose numerous issues along the road. Redefining needs may occur often.
Task 3: Explain the purpose of a feasibility report. I. Feasibility Report.
- Definition of Feasibility Report. A feasibility study is a report that assesses the viability of a collection of potential project pathways or solutions. The person who writes a feasibility report assesses the feasibility of several ideas and then recommends the best alternative. They then give the feasibility study and offer their proposal to their company.
- The purpose of a Feasibility Report. The goal of a feasibility study is to assess the viability of various solutions or project pathways and select the best choice. The feasibility report helps readers comprehend the viability of various approaches to a problem or project by breaking them down. Readers can determine whether to follow the study's suggestion for the optimal method based on the evaluation presented in the report. This detailed examination of several ways can assist businesses in making the best judgments possible about projects and difficulties.
- How feasibility is helpful for Undertaking Project. One of the most important steps in the website building process is the creation of a feasibility report. The feasibility report gives everyone on the development team an overview of the viability of many different variables in the project. The team may use the report to identify the project's strengths and shortcomings and then make changes to ensure the project's success. II. Feasibility Study.
- Definition of Feasibility Study. A feasibility study assesses whether or not it is feasible to carry out a certain project. A feasibility study attempts to evaluate a project's strengths and limitations, as well as the possibilities and risks existing in the natural environment, the amount of resources needed, and, ultimately, the likelihood of success.
