Download Software Development Lifecycle Models and more Assignments Environmental Law in PDF only on Docsity!
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Lifecycles Submission date 24 /11/2022 Date Received 1st submission 24 /11/ Re-submission Date Date Received 2nd submission Student Name MAI HUU NAM Student ID Bs Class PBIT17101 Assessor name TRUONG QUOC KHANH Student declaration I certify that the assignment submission is entirely my work and that I fully understand plagiarism's consequences. I understand that making a false declaration is a form of malpractice. Studentās signature MAI HUU NAM Grading grid P5 P6 P7 P8 M4 M5 D3 D
ļ² Summative Feedback: ļ² Resubmission Feedback: Signature & Date:
Submission Format The submission is in the form of 1 document You are required to make use of headings, paragraphs, subsections, and illustrations as appropriate, and all work must be supported with research and referenced using the Harvard referencing system.
Table of Contents
Introduction We achieved good outcomes by employing the functional design concept when designing the system. We can increase software quality by incorporating the functional design paradigm into the software development lifecycle. I even advise other software development firms and people to utilize this methodology while creating the system. It provides us with several advantages such as resilience and stability, and it generally increases software quality, which is the ultimate objective of every software organization. As a result, to reach the worldwide market, this organization must upgrade the old system and replace it with a new system that offers a variety of services. Describe two iterative and two sequential software lifecycle models(P1) Define: The software development life cycle (SDLC) is a diagram that describes the activities that must be completed at each stage of the software development process. SDLC is a design process that is carried out by a development team inside a software firm. It comprises a detailed plan for developing, maintaining, and replacing specific software. The life cycle outlines an approach for enhancing software quality and the development process as a whole. The software development process is another name for the software development life cycle. Standard business processes used to create software applications throughout the software development life cycle are generally divided into six steps: Planning, analysis, design, implementation, testing, and maintenance. The software development model or software development process defines the phases of software development being built. In this type of model, model improvements can be made quickly with execution in each iteration. The two iterative models that I am about to describe are the prototype model and the agile model.
Picture 1 SDLC MODEl
Picture 2 WATERFALL MODEL Analysis and Gathering of Requirements : All of the system's requirements that must be produced are gathered and then recorded in a specification document. Here, final product specifications are marked and examined. System Design: In this step, the needed specifications acquired in the first phase are examined before creating the system design. Thus, a well-prepared system design aids the developer in defining the hardware and system requirements as well as the overall system's architecture. Implementation: Based on feedback from the system design, the system is created in tiny components that are combined in the following step. Unit testing is the process of functionally testing each produced unit. Integration and testing : Following each unit test, the units created in the preceding step are integrated into the system. The full system System deployment : Following functional and non-functional testing, the product is deployed in the client environment or released to the market as needed. Maintenance: Client environment problems may arise even after the system has been deployed, thus patches are supplied to address these problems. In the maintenance phase, new versions are published to further improve the product. Up to the software's demise, this phase is completed. ADVANTAGE DISADVANTAGE Simple to use and understand The software is ready only after the last stage is over
Management simplicity thanks to its rigidity: every phase has a defined result and process review High risks and uncertainty Development stages go one by one Not the best choice for complex and object-oriented projects Perfect for small or mid-sized projects where requirements are clear and not equivocal Inappropriate for the long-term projects Easy to determine the key points in the development cycle The progress of the stage is hard to measure while it is still in the development Easy to classify and prioritize tasks Integration is done at the very end, which does not give the option of identifying the problem in advance THE V-MODEL The V-model is a type of SDLC model where the process executes sequentially in a V-shape. It is also known as the Verification and Validation model. It is based on the association of a testing phase for each corresponding development stage. delete the development of each step is directly associated with the testing phase. The next phase starts only after the completion of the previous phase i.e. for each development activity, there is a testing activity corresponding to it.
Testing for Acceptance. ADVANTAGE DISADVANTAGE This is a highly disciplined model and Phases are completed one at a time. It is not a go for complex and object-oriented projects. Simple and easy to understand and use. It is not suitable for projects where requirements are not clear and contains a hriskrisa k of changing. This model focuses on verification and validation activities early in the life cycle thereby enhancing the probability of building an error-free and good equal good-quality This model does not support the iteration of phases. It enables project management managers to stress accurately. It does not easily handle concurrent events. The Agile Model The meaning of Agile is swift or versatile." Agile process model" refers to a software development approach based on iterative development. Agile methods break tasks into smaller iterations or parts that do not directly involve long-term planning. The project scope and requirements are laid down at the beginning of the development process. Plans regarding the number of iterations, the duration, and the scope of each iteration are clearly defined in advance.
Picture 4 AGILE MODEL Agile phase: Requirements gathering Design the requirements Construction/ iteration Testing/ Quality assurance Deployment
multiple phases might be misconstrued at any point by different team members. AGILE SOFTWARE DEVELOPMENT METHODS Adaptive software development (ASD) Agile modelling Agile unified process (AUP) Disciplined agile delivery Dynamic systems development method (DSDM) Extreme programming (XP) Feature-driven development (FDD) Lean software development Kanban Rapid application development (RAD) Scrum Scrumban
TWO ITERATIVE
THE SPIRAL MODEL
The spiral model is a hybrid of the iterative and waterfall SDLC methods, with a strong emphasis on risk analysis. The biggest problem with the spiral model is determining when to go on to the next level. The tentative timelines are suggested as a solution to this problem. Even if the preceding step's work isn't finished, the transition to the following stage is carried out as planned. The strategy is provided based on statistical data collected in previous projects as well as the personal developer's expertise. Picture 5 SPRIAL MODEL
Flexibility in Requirements: Change requests in the Requirements at later a phase can be incorporated accurately by using this model. Too much dependability on Risk Analysis: The successful completion of the project is very much dependent on Risk Analysis. Without very highly experienced experts, it is going to be a failure to develop a project using this model. Customer Satisfaction: Customerscustomerse the development of the product at the early phase of the software development and thus, they habituated to the site using it before the depletion of t al product. Difficulty in time management: As the number of phases is unknown at the start of the project, time estimation is very difficult. The DSDM The Dynamic Systems Development technique (DSDM) is an associate degree agile code development approach that provides a framework for building and maintaining systems. The DSDM philosophy is borrowed from a modified version of the sociologist principleā80 % of An application is often delivered in twenty cents of the time itād desire to deliver the entire (100 per cent) application. DSDM is An iterative code method within which every iteration follows the 80% rule that simply enough work is needed for every increment to facilitate movement to the following increment. The remaining detail is often completed later once a lot of business necessities are noted or changes are requested and accommodated.
Picture 6 DSDM MODEL
