ASM1-SDLC-NguyenVanHieu (3) (1)

BTEC FPT INTERNATIONAL COLLEGE INFORMATION TECHNOLOGY FINAL REPORT OF ASSIGNMENT UNIT: SOFTWARE DEVELOPMENT LIFECYCLES STUDENT CLASS STUDENT ID SUPERVISOR : : : : Nguyen Van Hieu BDAF-2005-1 BDAF190023 NGUYEN HOANG ANH VU DANANG, March 2021 SOFTWARE DEVELOPMENT LIFECYCLES Qualification BTEC Levels and Higher Nationals in Computing Unit number and title Unit 9: Software Development Lifecycles Assignment due Assignment mitted sub- Learner’s name Assessor name Learner declaration: I certify that the work submitted for this assignment is my own and research sources are fully acknowledged Learner signature Date Grading grid P Assignment title M D Assignment 1: Planning a Software Development Lifecycle NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES Learning Outcomes and Assessment Criteria Pass Merit Distinction LO1 Describe different software development lifecycles P1 Describe two iterative M1 Describe, with an exam- and two sequential soft- ple, why a particular lifecycle ware lifecycle models model is selected for a development environment P2 Explain how risk is D1 Assess the merits of applying the Waterfall lifecycle model to a large software development project managed in the Spiral lifecycle model LO2 Explain the importance of a feasibility study P3 Explain the purpose of M2 Discuss the components a feasibility report of a feasibility report D2 Assess the impact of different feasibility criteria on a software investigation P4 Describe how technical solutions can be compared NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES Summative feedback: Assessor’s signature Assignment title Date Assignment 2: Undertake a Software Development Lifecycle NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES Learning Outcomes and Assessment Criteria Pass Merit Distinction LO3 Undertake a software development lifecycle P5 Undertake a software M3 Analyse how software investigation to meet a requirements can be business need traced throughout the software lifecycle P6 Use appropriate software analysis tools/techniques to carry out a software M4 Discuss two D3 Critically evaluate how the use of the function design paradigm in the software development lifecycle can improve software quality approaches to improving software quality investigation and create supporting documentation LO4 Discuss the suitability of software behavioural D4 Present justifications design techniques of how data driven P7 Explain how user and M5 Suggest two software software requirements behavioural specification have been addressed methods and illustrate their use with an example M6 Differentiate between a finite state machine (FSM) and an extendedFSM, providing an application for both NAME: Nguyen Van Hieu BDAF190023 software can improve the reliability and effectiveness of software SOFTWARE DEVELOPMENT LIFECYCLES Summative feedback: Assessor’s signature NAME: Nguyen Van Hieu BDAF190023 Date SOFTWARE DEVELOPMENT LIFECYCLES PREFACE/ ACKNOWLEDGEMENT I sincerely thank NGUYEN HOANG ANH VU who wholeheartedly guided me through the course of learning and imparting knowledge about the subject so that I could apply and complete this exercise However, in the process of doing the lesson, due to limited professional knowledge, I still lack knowledge, evaluation, and presentation about the work I hope to receive the attention and suggestions of the teachers and teachers of the subject to make my work more complete and complete Sincerely thank! Da Nang, December 2021 Performed Student Nguyen Van Hieu NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES Learners declaration The content of this thesis is made by me under the direct guidance of lecturers NGUYEN HOANG ANH VU I certify that the work submitted for this assignment is my own and research sources are fully acknowledged Any unauthorized copying, copyright infringement, or fraud, I will take full responsibility Date: November, 2021 Student signature: Nguyen Van Hieu NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES Contents SOFTWARE INTRODUCTION CHAPTER 1: PLANNING A SOFTWARE DEVELOPMENT LIFECYCLE 10 1.1 Software lifecycle models (P1) 10 1.1.1 Waterfall model 10 1.1.2 Interative model 13 1.1.3 The spiral model 17 1.1.4 V model 20 (P4) 1.2 The risk in spiral lifecycle model (P2) 25 1.3 Feasibility report (P3) 28 1.4 DESCRIBING HOW TECHNICAL SOLUTIONS CAN BE COMPARED 30 1.4.1 How to apply the three feasibility criteria in the project 30 1.4.2 The feasibility of the project 33 1.4.3 Alternative technical solutions 34 CONCLUSION 36 REFERENCES 37 NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES SOFTWARE INTRODUCTION Commodity management is a must in any business The management of goods takes a lot of time, causing a lot of costs With the development of information technology, businesses are gradually applying technology to management to improve the efficiency of their jobs The requirement for inventory management software is inventory management, so you can know how much inventory is in stock In addition, in the daily activities of the business often arise transactions with customers, suppliers so the software needs to have inventory entry features out of stock And make reports on the situation of import and export, the amount of unsold goods to send to management in order to give timely and right solutions to build a growing business NAME: Nguyen Van Hieu BDAF190023 SOFTWARE DEVELOPMENT LIFECYCLES • Technology is not dynamic and is well understood by the project team • There are no ambiguous or undefined requirements • The project is short V-Model - Pros and Cons The advantage of the V-Model method is that it is very easy to understand and apply The simplicity of this model also makes it easier to manage The disadvantage is that the model is not flexible to changes and just in case there is a requirement change, which is very common in today’s dynamic world, it becomes very expensive to make the change The advantages of the V-Model method are as follows − • This is a highly-disciplined model and Phases are completed one at a time • Works well for smaller projects where requirements are very well understood • Simple and easy to understand and use • Easy to manage due to the rigidity of the model Each phase has specific deliverables and a review process The disadvantages of the V-Model method are as follows − • High risk and uncertainty • Not a good model for complex and object-oriented projects • Poor model for long and ongoing projects • Not suitable for the projects where requirements are at a moderate to high risk of changing • Once an application is in the testing stage, it is difficult to go back and change a functionality • No working software is produced until late during the life cycle 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 The V-Model is an extension of the waterfall model and is based on the association of a testing phase for each corresponding development stage NAME: Nguyen Van Hieu BDAF190023 23 SOFTWARE DEVELOPMENT LIFECYCLES • Case in used  Requirements are well defined, clearly documented and fixed  Product definition is stable  Technology is not dynamic and is well understood by the project team  There are no ambiguous or undefined requirements  The project is short • Advantages of V model  This is a highly-disciplined model and Phases are completed one at a time  Works well for smaller projects where requirements are very well understood  Simple and easy to understand and use  Easy to manage due to the rigidity of the model Each phase has specific deliverables and a review process • Disadvantages of V model  High risk and uncertainty  Not a good model for complex and object-oriented projects  Poor model for long and ongoing projects  Not suitable for the projects where requirements are at a moderate to high risk of changing  Once an application is in the testing stage, it is difficult to go back and change a functionality  No working software is produced until late during the life cycle NAME: Nguyen Van Hieu BDAF190023 24