Software Development Life Cycle Assignment
27 Pages9120 Words232 Views
Added on 2021-06-17
Software Development Life Cycle Assignment
Added on 2021-06-17
ShareRelated Documents
ASSIGNMENT 01 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09: Software Development Life CycleSubmission date Date Received 1st submissionRe-submission DateDate Received 2nd submissionStudent Name Nguyễn Việt Hà Student ID GCH200035 Class GCH0903 Assessor name Đỗ Quốc Bình 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 Grading grid P1 P2 P3 P4 M1 M2 D1 D2
❒Summative Feedback: ❒Resubmission Feedback:Grade:Assessor Signature:Date:Internal Verifier’s Comments:Signature & Date:
Table of Contents: I.Introduction....................................................................................................................................................................................................................................... 5 II.The diffểrent systems development lifecycles.......................................................................................................................................................................... 5 1.Iterative and sequential software lifecycle models..................................................................................................................................................................... 5 a.Sequential software lifecycle models............................................................................................................................................................................................ 5 b.Iterative software lifecycle models............................................................................................................................................................................................... 9 c.The best model for the project.................................................................................................................................................................................................... 14 2.Software Risk Management........................................................................................................................................................................................................ 16 a.Risk management explanation and process.............................................................................................................................................................................. 16 b.Applying the concepts at Tune Source...................................................................................................................................................................................... 17 III.The importance of feasibility study.................................................................................................................................................................................... 18 1.The purpose of feasibility study............................................................................................................................................................................................. 18 2.Technical Feasibility................................................................................................................................................................................................................ 19 3.Economic Feasibility................................................................................................................................................................................................................ 20 4.Organizational Feasibility....................................................................................................................................................................................................... 21 5.How technical solutions can be compared............................................................................................................................................................................. 23 6.Evaluate solutions for Tune Source....................................................................................................................................................................................... 25 IV.Conclusion........................................................................................................................................................................................................................ 26
Table of Figures: Figure 1: Waterfall Development (Roth, Dennis and Wixom, 2013) .......................................................................................................................................................... 6 Figure 2: Parallel development (Roth, Dennis and Wixom, 2013) ............................................................................................................................................................. 7 Figure 3: V-model (Roth, Dennis and Wixom, 2013) ................................................................................................................................................................................. 8 Figure 4: Iterative development (Roth, Dennis and Wixom, 2013) .......................................................................................................................................................... 10 Figure 5: System Prototyping (Roth, Dennis and Wixom, 2013) .............................................................................................................................................................. 11 Figure 6: Throwaway Prototyping (Roth, Dennis and Wixom, 2013) ...................................................................................................................................................... 12 Figure 7: Extreme Programming (Roth, Dennis and Wixom, 2013) ......................................................................................................................................................... 13 Figure 8: Criteria for Selecting a Methodology (Roth, Dennis and Wixom, 2013) .................................................................................................................................. 14 Figure 9: Sample Risk Assessment (Roth, Dennis and Wixom, 2013) ..................................................................................................................................................... 17 Figure 10: Feasibility Analysis Assessment Factors (Roth, Dennis and Wixom, 2013) ........................................................................................................................... 19 Figure 11: Simple Cash Flow Projection (Roth, Dennis and Wixom, 2013) ............................................................................................................................................ 21
I.Introduction A software development cycle is required for successful projects, thus this report will explain and assess the four software development processes or software, as well as conduct research and analyze the feasibility stage. and construct Different methodologies for programming progress models are chosen for the project. Furthermore, there are several models for designing huge, extremely efficient applications available today. Finally, the author will examine the responses in order to determine the most appropriate, progressive, and practicable project configurations. II.The diffểrent systems development lifecycles According to Roth, Dennis and Wixom (2013), the system development life cycle is a key process that all system development initiatives follow (SDLC). The SDLC begins with the planning phase, in which the project team determines the system's commercial value, conducts a feasibility study, and develops a project plan. The team establishes an analysis strategy, obtains data, and creates a set of analysis models in the second phase, which is the analysis phase. The team produces the design strategy, physical design, architecture design, interface design, database and file requirements, and program design in the following step, the design phase.The system is constructed, implemented, and maintained in the last step, implementation. 1.Iterative and sequential software lifecycle models a.Sequential software lifecycle models Waterfall Development(Roth, Dennis and Wixom, 2013):In waterfall development, analysts and users move from one phase to the next in a logical order. As the project progresses from phase to phase, the primary deliverables for each phase are often voluminous (sometimes hundreds of pages) and are given to the approval committee and project sponsor for approval. The work completed in one phase is authorized, and the next step begins. As the project proceeds from phase to phase, it flows like a cascade. It is possible to travel backwards through the phases (for example, from design to analysis), but it is extremely difficult. (Imagine swimming upstream in a waterfall like a salmon.)
Figure 1: Waterfall Development(Roth, Dennis and Wixom, 2013)Waterfall development approaches offer the benefit of establishing requirements well before programming begins and restricting needs modifications as the project progresses. The main drawbacks are that the design must be fully stated before programming can begin, that there is a considerable period between the completion of the system proposal in the analysis phase and the delivery of the system, and that testing is virtually an afterthought in the implementation phase. Furthermore, because deliverables are frequently a poor means of communication, critical needs may be lost in the voluminous paperwork.If a key need is overlooked by the project team, costly post-implementation programming may be required. Because so much time has passed between the initial idea and the actual implementation, users may forget the system's initial goal. Furthermore, in today's changing business world, a system that suited the current environmental circumstances during the analysis phase may require significant modification when it is implemented to meet the environment. This rework necessitates returning to the first step and making necessary modifications in each of the succeeding stages one by one. Parallel development
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Assignment on Software Development Life Cyclelg...
|37
|7409
|54
Unit 9: Software Development Life Cycle Doclg...
|26
|7835
|538
Unit 9 : Software Development Life Cyclelg...
|24
|5075
|934
ASSIGNMENT NAME: ASSIGNMENT 1 ASSIGNMENT NAME: ASSIGNMENT 1 ASSIGNMENT NAME: ASSIGNMENT 1 ASSIGNMENT NAME: ASSIGNMENT 1 ASSIGNMENT NAME: ASSIGNMENT 1 ASSIGNMENT NAME: ASSIGNMENT 1 ASSIGNMENT NAME: ASSlg...
|18
|4969
|84
Systems Development Life Cycle Analysis 2022lg...
|12
|1582
|24
Systems Analysis and Design for Adroit Ads Companylg...
|29
|5985
|419