Ho Chi Minh City
ASSIGMENT REPORT
SOFTWARE DEVELOPMENT LIFE CYCLE
(Đào Vĩnh Lộc – TCS21019)
Date: (29-Sep-2022)
Version: 1.0
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software Development Life-cycle Assignment 1, Essays (high school) of Computer science
Software Development Life-cycle Assignment 1
Typology: Essays (high school)
2021/2022
1 / 23
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software Development Life-cycle Assignment 1 and more Essays (high school) Computer science in PDF only on Docsity!
Ho Chi Minh City
ASSIGMENT REPORT
SOFTWARE DEVELOPMENT LIFE CYCLE
(Đào Vĩnh Lộc – TCS21019)
Date: (29-Sep-2022)
Version: 1.
ASSIGNMENT FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life Cycle Submission date 03-Oct-2022 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name DAO VINH LOC Student ID TCS Class GCS1002 Assessor name MaiVN 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 DAO VINH LOC Grading grid P1 P 2 P3 M1 M2 D 1
Ho Chi Minh City Assignment Brief (RQF) Higher National Certificate/Diploma in Computing Title 22FA01- 1631 - GCS1002-MAIVN Academic Year 2022 Unit Tutor MaVN Assignment Title Planning a Software Development Lifecycle Issue Date Submission Date 03 - Jul- 2022 IV Name & Date Đào Vĩnh Lộc – TCS2 1019 Submission Format Format: The submission is in the form of 1 document You must use font Calibri size 12, set number of the pages and use multiple line spacing at 1.3. Margins must be: left: 1.25 cm; right: 1 cm; top: 1 cm and bottom: 1 cm. The reference follows Harvard referencing system. Submission Students are compulsory to submit the assignment in due date and in a way requested by the Tutors. The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/ Note: The Assignment must be your own work, and not copied by or from another student or from books etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. Make sure that you know how to reference properly, and that understand the guidelines on plagiarism. If you do not, you definitely get failed. Unit Learning Outcomes LO1 Describe different software development lifecycles LO2 Explain the importance of a feasibility study Assignment Brief Scenario Tune Source is a company headquartered in southern California. Tune Source is the brainchild of three entrepreneurs with ties to the music industry: John Margolis, Megan Taylor, and Phil Cooper. Originally, John and Phil partnered to open a number of brick and
mortar stores in southern California specializing in hard-to-find and classic jazz, rock, country, and folk recordings. Megan soon was invited to join the partnership because of her contacts and knowledge of classical music. Tune Source quickly became known as the place to go to find rare audio recordings. Annual sales last year were $40 million with annual growth at about 3%–5% per year. Tune Source currently has a website that enables customers to search for and purchase CDs. This site was initially developed by an Internet consulting firm and is hosted by a prominent local Internet Service Provider (ISP) in Los Angeles. The IT department at Tune Source has become experienced with Internet technology as it has worked with the ISP to maintain the site. System Request Project Sponsor: Carly Edwards, Assistant Vice President, Marketing Business Need: This project has been initiated to increase sales by creating the capability of selling digital music downloads to customers through kiosks in our stores, and over the Internet using our website. Business Requirements: Using the Web or in-store kiosks, customers will be able to search for and purchase digital music downloads. The specific functionality that the system should have includes the following: Search for music in our digital music archive. Listen to music samples. Purchase individual downloads at a fixed fee per download. Establish a customer subscription account permitting unlimited downloads for a monthly fee. Purchase music download gift cards. Business Value: We expect that Tune Source will increase sales by enabling existing customers to purchase specific digital music tracks and by reaching new customers who are interested in our unique archive of rare and hard-to-find music. We expect to gain a new revenue stream from customer subscriptions to our download services. We expect some increase in cross-selling, as customers who have downloaded a track or two of a CD decide to purchase the entire CD in a store or through our website. We also expect a new revenue stream from the sale of music download gift cards. Conservative estimates of tangible value to the company include the following: $757,500 in sales from individual music downloads
Learning Outcomes and Assessment Criteria Pass Merit Distinction LO1 Describe different software development lifecycles D1 Assess the merits of applying the Waterfall lifecycle model to a large software development project. P1 Describe two iterative and two sequential software lifecycle models. P2 Explain how risk is managed in the Spiral lifecycle model. M1 Describe, with an example, why a particular lifecycle model is selected for a development environment. LO2 Explain the importance of a feasibility study D2 Assess the impact of different feasibility criteria on a software investigation. P3 Explain the purpose of a feasibility report. P4 Describe how technical solutions can be compared. M2 Discuss the components of a feasibility report.
Ho Chi Minh City
- INTRODUCTION.............................................................................................................................................................................. Table of Contents
- LO1 DESCRIBE DIFFERENT SOFTWARE DEVELOPMENT LIFECYCLES
- 2.1. INTRODUCTION
- 2.2. P1 DESCRIBE TWO ITERATIVE AND TWO SEQUENTIAL SOFTWARE LIFECYCLE MODELS
- 2.2.1. Common standards
- 2.2.2. Waterfall Model
- 2.2.3. Spiral Model
- 2.2.4. Agile Model
- 2.3. P2 EXPLAIN HOW RISK IS MANAGED IN THE SPIRAL LIFECYCLE MODEL
- 2.3.1. Recommendation of the Spiral Model
- 2.3.2. Challenges of the spiral model
- 2.4. M1 DESCRIBE, WITH AN EXAMPLE, WHY A PARTICULAR LIFECYCLE MODEL IS SELECTED FOR A DEVELOPMENT ENVIRONMENT
- 2.4.1. Introduction selecting a Software Development Life Cycle (SDLC)
- moderately or least suitable 2.4.2. Discuss the suitability of each of the SDLC models for the project. For each model, specify whether it is most, - 2.5. D1 ASSESS THE MERITS OF APPLYING THE WATERFALL LIFECYCLE MODEL TO A LARGE SOFTWARE DEVELOPMENT PROJECT.............................
- LO2 EXPLAIN THE IMPORTANCE OF A FEASIBILITY STUDY
- 3.1. P3 EXPLAIN THE PURPOSE OF A FEASIBILITY REPORT
- 3.1.1. What is Feasibility Report?
- 3.1.2. Type of Feasibility...........................................................................................................................................................
- 3.1.3. Purpose of Operation Feasibility
- 3.2. P4 DESCRIBE HOW TECHNICAL SOLUTIONS CAN BE COMPARED
- 3.2.1. Discuss whether the project is feasible
- 3.2.2. Alternative technical solutions using the alternative matrix
- 3.3. M2 DISCUSS THE COMPONENTS OF A FEASIBILITY REPORT.
- 3.3.1. What is the feasibility report?
- 3.3.2. What is the current analysis?
- 3.3.3. Defining and reviewing the organizational requirements of the project
- 3.3.4. Evaluating a comprehensive cost analysis for the project
- 3.3.5. Conclusion
- 3.4. D2 ASSESS THE IMPACT OF DIFFERENT FEASIBILITY CRITERIA ON A SOFTWARE INVESTIGATION..................................................................
- REFERENCES
Stage 3. Development and programming After the requirements are approved, the process goes to the next stage – actual development. Programmers start here with the source code writing while keeping in mind previously defined requirements. The system administrators adjust the software environment, front-end programmers develop the user interface of the program and the logic for its interaction with the server. The programming by itself assumes four stages o Algorithm development o Source code writing o Compilation o Testing and debugging Stage 4. Testing The testing phase includes the debugging process. All the code flaws missed during the development are detected here, documented, and passed back to the developers to fix. The SDLC testing process repeats until all the critical issues are removed and software workflow is stable. Stage 5. Deployment When the program is finalized and has no critical issues – it is time to launch it for the end users. After the new program version release, the tech support team joins. This department provides user feedback; consult and support users during the time of exploitation. Moreover, the update of selected components is included in this phase, to make sure, that the software is up-to-date and is invulnerable to a security breach.
2.2.2. Waterfall Model
Waterfall – is a cascade SDLC model, in which development process looks like the flow, moving step by step through the phases of analysis, projecting, realization, testing, implementation, and support. This SDLC model includes gradual execution of every stage completely. This process is strictly documented and predefined with features expected to every phase of this software development life cycle model.
Use cases for the Waterfall SDLC model The requirements are precisely documented. Product definition is stable. The technologies stack is predefined which makes it not dynamic. No ambiguous requirements. The project is short.
2.2.3. Spiral Model
Spiral model – is SDLC model, which combines architecture and prototyping by stages. It is a combination of the Iterative and Waterfall SDLC models with the significant accent on the risk analysis. The main issue of the spiral model – is defining the right moment to make a step into the next stage. The preliminary set time frames are recommended as the solution to this issue. The shift to the next stage is done according to the plan, even if the work on the previous stage isn’t done yet. The plan is introduced basing on the statistics data, received during the previous projects even from the personal developer’s experience.
Use cases for the Agile model The users’ needs change dynamically. Less price for the changes implemented because of the many iterations. Unlike the Waterfall model, it requires only initial planning to start the project
2.3. P2 Explain how risk is managed in the Spiral lifecycle model
Spiral model is one of the most important Software Development Life Cycle models, which provides support for Risk Handling. In its diagrammatic representation, it looks like a spiral with many loops. The exact number of loops of the spiral is unknown and can varyfrom project to project. Each loop of the spiral is called a Phase of the software development process. The exact number of phases needed to develop the product can bevaried by the project manager depending upon the project risks. The Radius of the spiral at any point represents the expenses (cost) of the project so far, andthe angular dimension represents the progress made so far in the current phase. The below diagram shows the different phases of the Spiral Model. Each phase of the Spiral Model is divided into four quadrants as shown in the above figure.The functions of these four quadrants are discussed below.
- Objective determination and identify alternative solutions Requirements are gathered from the customers and the objectives are identified, elaborated, and analyzed at the start of every phase. Then alternative solutions possible forthe phase are proposed in this quadrant.
- Identify and resolve Risks During the second quadrant, all the possible solutions are evaluated to select the best possible solution. Then the risks associated with that solution are identified and the risks are resolved using thebest possible strategy.
- Develop next version of the Product During the third quadrant, theidentified features are developed and verified through testing. At the end of thethird quadrant, the next version of the software is available.
- Review and plan for the next Phase In the fourth quadrant, the Customers evaluate the so far developed version of the software. In the end, planning forthe next phase is started.
2.3.1. Recommendation of the Spiral Model
Risk Handling The projects with many unknown risks that occur as the development proceeds, in that case, Spiral Model is the best development model to follow due to the risk analysis and risk handling at every phase. Good for large projects It is recommended to use the Spiral Model in large andcomplex projects. Flexibility in Requirements Change requests in the Requirements at later phase can be incorporated accurately by using this model. Customer Satisfaction Customer can see the development of the product at the early phase of the software development and thus, they habituated with the system by using it before completion of the total product.
2.3.2. Challenges of the spiral model
Complex The Spiral Model is much more complex than other SDLC models. Expensive Spiral Model is not suitable for small projects as it is expensive. 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. Difficulty in time management As the number of phases is unknown at the startof the project, so time estimation is very difficult.
2.4. M1 Describe, with an example, why a particular lifecycle model is selected for a
development environment
2.4.1. Introduction selecting a Software Development Life Cycle (SDLC)
Selecting a Software Development Life Cycle (SDLC) methodology is a challenging task formany organizations and software engineers. What tends to make it challenging is the fact that few organizations know what are the criteria to use in selecting a methodology to addvalue to the organization. Fewer still understand that a methodology might apply to more than one Life Cycle Model. Before considering a framework for selecting a given SDLC methodology, we need to define the different types and illustrate the advantages and disadvantages of those models (please see the Software Development Life Cycle Models and Methodologies).
spend any money to change the end user’s requirement. In conclusion, Waterfall is not suitable for Tune Source. It is suitable for small projects. Iterative model Iterative model is the same waterfall model that is software requirement clearly definedand know Software development technologies. When business analysis takes the request from tune source. End-user gives current requests and clearly does not know software development technologies. End-user only need to know the product that has the same as they want. It is an incomplete analysis. Users confuse the prototype and the complete system. Developers mis interpret user goals. It is costly to implement the prototypes. Conclusion it is also a suitable for tune source. High cost and time to reach the final product. It needs special skills to evaluate the risks and assumptions. The cost is very expensive. Inconclusion, it is also not a suitable for tune course. Spiral model The spiral model is quite suitable for project because it’s used in the large applications and systems which built-in small phases or segments. This will avoid the end product being requested by the end user but it is not really a suitable for tune source. In response, the Spiral methodology works best for complicated projects with small functionality or strict budgets. It is also suitable for projects with no clear requirements at the early stages, or with requirements that need to be evaluated. Agile Software development Agile software development is suitable for Tune Source because It can be used with any type of project, but it needs more engagement from the customer and to be interactive. Providing teams with a competitive advantage by catching defects and making changes throughout the development process, instead of at the end. It speeds up time spent on evaluations since each evaluation is only on a small part of the whole project. Ensures changes can be made quicker and throughout the development process by having consistent evaluations to assess the product with the expected outcomes requested. It keep seach project transparent by holding regular consistent meetings with customers and systems that allow everyone involved to access project data and progress. It decreases the time required to avail some system features. Conclusion, it’s suitable for project.
2.5. D1 Assess the merits of applying the Waterfall lifecycle model to a large software
development project
- LO2 Explain the importance of a feasibility study
3.1. P3 Explain the purpose of a feasibility report
3.1.1. What is Feasibility Report?
A feasibility report is a testimony that attempts to create some sort of action. Feasibility reports are created to persuade/help the decision-makers to choose between available options. Remember that your option is not the only one, the decision-makers will probably have many to choose from. A feasibility report also determines whether or not the investigated task can be done with the number of resources available OR how many resources will be necessary in order to complete the task. Feasibility may be useful in a lot of different situations such as event planning, finances, or even remodeling your home. Feasibility reports are usually used to sway decision-makers towards one direction or the other. Many times, there is only one course of action but, there needs to be a second course of action.
3.1.2. Type of Feasibility
A feasibility analysis evaluates the project’s potential for success; therefore, perceived objectivity is an essential factor in the credibility of the study for potential investors andlending institutions. There are five types of feasibility study—separate areas that afeasibility study examines, described below. Technical Feasibility This assessment focuses on the technical resources available to the organization. It helps organizations determine whether the technical resources meet capacity and whether the technical team is capable of converting the ideas into working systems. Technical feasibility also involves the evaluation of the hardware, software, and other technical requirements of the proposed system. As an exaggerated example, anorganization wouldn’t want to try to put Star Trek’s transporters in their building—currently, this project is not technically feasible. Economic Feasibility This assessment typically involves a cost/ benefits analysis of the project, helping organizations determine the viability, cost, and benefits associated with a project before financial resources are allocated. It also serves as an independent projectassessment and enhances project credibility—helping decision-makers determine the positive economic benefits to the organization that the proposed project will provide. Legal Feasibility This assessment investigates whether any aspect of the proposed project conflicts with legal requirements like zoning laws, data protection acts or social media laws. Let’s sayan organization wants to construct a new office building in a specific location. Afeasibility study might reveal the organization’s ideal location isn’t zoned for that
Net Present Value PAYBACK ANALYSIS FOR CLIENT-SERVER SYSTEM ALTERNATIVE Cash flowdescription year 0 year 1 year 2 year 3 year 4 year 5 Development cost $ 500,000. $
- $
$
$
$
Discount factors for 20% 1 0.83 0.694 0.586 0.482 0. Operation & Maintenance cost $
$ 20,000. $ 22,000. $ 24,000. $ 28,000. $ 30,000. Time adjusted costs $ 500,000. $ 16,600. $ 15,268. $ 14,064. $ 13,496. $ 12,060. Cumulative time -adjusted costs over $ 500,000. $ 516,600. $ 531,868. $ 545,932. $ 559,428. $ 571,488. Benefits derived from operation of new $
$ 170,000. $ 200,000. $ 250,000. $ 290,000. $ 300,000. Time -adjusted benefits (current of present) $
$ 141,100. $ 138,800. $ 146,500. $ 139,780. $ 120,600. Cumulative time -adjusted benefits over $
$ 141,100. $ 279,900. $ 426,400. $ 566,180. $ 686,780. Cumulative life time- adjusted costs+ $(500,000.
$(375,500.
$(251,968.
$(119,532.
$ 6,752. $ 115,292. Conclusion, Project can accept and proceed.
3.2.2. Alternative technical solutions using the alternative matrix
JavaScript JavaScript is one of the easiest, versatile and effective languages used to extend functionality in websites. JavaScript Development Services helps in on-screen visual effects and processing and calculating data on web pages with ease. The programming language also helps in extended functionality to websites using third party scripts among several other handy features.
.Net o One of the most popular software development frameworks in the market, the .NET Framework props up many of the applications that we know of today. It is used widely by developers due to how prolific it is and how large theeco system has become. The fact that it is open-source is also why we have noticed that it is quite popular, particularly among developers with large projects meant for a slew of different platforms. o The biggest beneficiaries of the .NET Framework are businesses that are in need of a lot of features that are meant to address a number of required services. These services would then extend towards multiple ecosystems that are under the framework’s umbrella. Not everything integrates smoothly, but those that do are easy to work with and do not present too much of a challenge to get used to. Open-source o Open Source is software that has a set of source code that users can easily download, modify, or upgrade to add necessary features to meet their own actual usage needs. Usually these are the source code released completely free, owned by the units, large businesses in the field of technology. Sometimes, open-source code is developed by programmers, providing it with certain differences, uniqueness when compared to the original version. o Source code is software that cannot be seen by most computer users. However,for programmers, it is easy to access the source code, make improvements by adding, removing, or modifying features, inactive parts, etc. on demand. A summary weighted score table