Download ASM1 Development Life Cycle and more Assignments Computer Programming in PDF only on Docsity!
ASSIGNMENT 01 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09: Software Development Life Cycle Submission date 4/27 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Nguyen Van Long Student ID GCH Class GCH0907 Assessor name 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 Long Grading grid P1 P2 P3 P4 M1 M2 D1 D
❒ Summative Feedback: ❒ Resubmission Feedback:
Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date:
Introduction The Tune Source Corporation is headquartered in California. Three music industry professionals, John Margolis, Megan Taylor, and Phil Cooper came up with the concept for Tune Source. Initially, John and Phil worked together to open several physical stores in southern California, focusing on hard-to-find and classical jazz, rock, country, and folk recordings. Tune Source now has a website where anyone may look for and buy CDs. As a result, in order to increase revenue from music products, this company needs modernize its existing system and replace it with a new system that provides a wider range of services. Due to the fact that purchasers from various countries will be purchasing items in a variety of currencies Task 1.SDLC model A. SDLC (Software Development Life Cycle) SDLC (software development life cycle) is a planning, development, and maintenance process for information and industrial systems. The Waterfall model, which consists of five phases that must be completed in order to deliver a software solution, and the Spiral model, which is considered as a process that goes through a number of iterations, are two SDLC models accessible. Finally, any combination of iterative design or iterative technique and incremental construction model is known as the incremental model for software development. The seven steps of the process include planning, requirements, analysis, implementation, deployment, testing, and assessment. Many academics have looked at SDLC, and several models have been proposed, each with its own set of strengths and weaknesses. The waterfall, spiral, incremental, rational unified process (RUP), rapid application development (RAD), agile software development, and rapid prototyping are all successful SDLC approaches. Furthermore, all of the proposed SDLC models share the same core properties. They are all made up of a sequence of phases or procedures that system developers and designers must follow and complete in order to build systems and deliver the commodities that are required. In the following section, I will discuss the waterfall model. (Anon, 2015)
Figure 1 SDLC (Software Development Life Cycle) The most well-known and oldest SDLC model is the Waterfall Model. This paradigm is commonly used by the government as well as a number of significant organizations. The sequential steps are a distinguishing feature of this paradigm. It moves through the processes of requirements analysis, design, coding, testing, and maintenance. Furthermore, it ensures that design flaws are recognized before a product is developed. This methodology is effective for projects where quality control is a top priority due to its intensive documentation and preparation. Because the phases in this model do not overlap, the waterfall model begins and ends with one stage before going on to the next. A quick overview of the waterfall process is provided in the phases below:
- Requirement: A requirement is a description of the system behavior that must be developed. In most cases, the information provided by clients is accurate. As a result, the software specifications and features agreement between the clients and the developers are established. In a nutshell, requirements are gathered, evaluated, and appropriate documentation is then prepared to aid in the development process.
- High-level design: The data collected in the previous phase is reviewed, and an implementation strategy is established. It's a software project's planning and problem-solving phase. Among the topics covered are algorithm design, software architecture design, database conceptual schema, logical diagram design, and data structure description.
- Coding: During this phase, all requirements will be transported to the production environment.
ready for installation and maintenance, the team will add functionality for additional requirements in ever-increasing "spirals." Each iteration prior to the production version is referred to as a prototype in this model. The phases of the Spiral model are briefly described in the steps below:
- Planning: This phase entails gaining a thorough understanding of the system requirements through ongoing contact between customers and system analysts.
- Risk Analysis: In this step, a procedure is followed to identify risks and potential alternatives. At the conclusion of this phase, a prototype is created.
- Development/Engineering: During this phase, the software is created and tested.
- Evaluation Phase: This allows the customer to assess the project's output before moving on to the following spiral or round.
Figure 3 Spira Model Agile development is built on the concept of incremental and iterative development, in which different phases of a development life cycle are examined repeatedly. It converges on solutions iteratively by using consumer feedback to enhance the software. The development life cycle is broken into smaller portions, called "increments" or "iterations," in agile development, rather than a single huge process model as in conventional SDLC. Each of these increments touches on each of the traditional phases of development. The four primary agile factors, according to the Agile Manifesto, are as follows:
Figure 4 Agile Model The V-model (Validation and Verification Model) is a variant of the Waterfall approach. Unlike the Waterfall approach, this one does not follow a linear axis; instead, after the coding phase is completed, the phases reverse direction. The V-Model is built on the idea of assigning a testing period to each development stage. This means that each phase of the development cycle has a testing phase that is directly linked to it. This is a very rigorous model, and the following step begins only once the previous one has been completed. This developmental process is well-balanced, relying on previous steps' verification before moving on. Before moving on, every phase's product must be reviewed and approved. In the V-model, the developer and tester work in tandem. The V-model prepares System test cases based on the requirements, while the HLD (High-Level Document) model prepares HLD (High-Level Document) test cases based on the requirements. The Integration Test cases are prepared based on the LLD (Low-Level document), and the Integration Test cases are prepared based on the LLD (Low-Level document). The coding is then completed. After the code is finished, unit,
integration, and system testing are performed in order. The V-model establishes a link between each development stage and the testing stage. (Balaji,
Figure 5 V-Model Prototyping, a software development approach that involves the creation and evaluation of functioning system models, is increasingly being used to assist quickly and precisely establish system requirements and functional capabilities. Although prototyping can be a useful part of the SDLe, it can also cause a number of issues. Prototyping, which has long been a popular design technique for difficult engineering projects, has recently gained traction as a viable alternative to standard software development approaches. Before the final system is established, prototypes, or working models of the system, are created. Prototyping allows users to interact with a system early in the development process by displaying its features before it is fully developed. This allows users to better understand and define what they want from the new system. It also makes it easier for system designers to test their designs fast. Prototyping is an ongoing, iterative process in which system needs and specifications are refined and modified as users and
which is caused by the requirement to complete one location before moving on to the next. Because the criteria are clearly stated and expressed, it is unlikely that they will change rapidly in the future, and the project is relatively short, the waterfall model may be a viable choice. The core principle of Agile is to prioritize the needs of the customer. This method implies a user-centered approach, eliminates many of the difficulties associated with earlier engineering, and makes software responsive to consumer feedback. The project manager splits the entire project into a series of phases called “sprints,” each of which results in a functioning software product. The user input that each product receives aids the developers in revising the initial strategy. As a result, if the project’s success depends on the ability to fulfill the needs of clients who have regularly changing needs or if the project requires inventiveness, this software development life cycle will be a good fit on a constant basis. As a result, the Waterfall model will be the best fit for this project. C. Identify some risks and discuss an approach to manage them. A risk is essentially a potential issue. It's an activity or circumstance that could have an impact on a software development project's success. Risk is the possibility of suffering a loss, and the total risk exposure to a project will take into account both the probability and amount of the potential loss. Crisis management and guesswork are seldom successful. The major predictive technique for capturing the probability of an unplanned or undesired event occurring during a software development project is to identify and gather risks. Terminations, discontinuities, scheduling delays, cost overruns, and resource overruns are all examples of these. Containing and minimizing hazards are two aspects of risk management. To begin, you must first identify and strategize. Then, when a risk arises, be ready to respond, drawing on the entire team's expertise and knowledge to minimize the project's impact. The following are some of the tasks that risk management entails:
- Determine the risks as well as the variables that contribute to them.
- Every hazard should be classified and ranked.
- Make a strategy to link each risk to a mitigation approach. Keep an eye out for risk factors during the process.
- If a threat arises, take the necessary precautions.
- Communicate the status of hazards at all times during the project. Some risk in the software project
No Risk Possibility Cause Consequence Risk response 1 Slow progress 35% Due to irrational task assignments or unforeseen circumstances such as epidemics, error codes, a lack of people, or equipment malfunctions A punishment or a compensation contract may be imposed if the consumer is discredited. Assign responsibilities to each person that are appropriate for them, do frequent inspections or replace any defective equipment, and adhere to rigorous time management. 2 Code issue 10% A range of other reasons and issues with code can occur as a result of rushed labor, low- quality code, bugs, logical flaws, and a variety of other causes and issues with code. During the code fix, the project will be delayed and will not be completed on time. Regularly testing code, addressing bugs as they arise, and logically resolving them 3 Material, intellectual property, and equipment theft are all examples of theft. 5% Employees stealing products or stealing intellectual property are both examples of intellectual property theft. The project's intellectual property rights were revoked, and it is no longer viable for commercialization. Check to see that all physical security measures are in place. Insurance for information security. Notify the proper authorities, such as the police and the Project Board, and begin an internal inquiry.
- Familiar with Technology The structure can be built using the Visual Studio environment. On the Windows platform, this platform is very familiar and simple to use, making it easier for developers to deploy the software. - The project sizes This is a low-capital venture with a strong yearly growth rate of 18 to 21% (previous year's annual revenue was $4-5 million). As a result, the project will be completed and put on the market as soon as possible. - Compatibility with other system Because the framework is designed in current popular source code (C# and Java), it is extremely interoperable with various systems.
- Economic feasibility Non-Using New System 2022 2023 2024 2025 Total Development Cost Management Cost -20000$ -22000$ -24000$ -66000$ Total Cost -20000$ -22000$ -24000$ -66000$ Search, Sell CDs 160000$ 170000$ 190000$ 520000$ Customer Subscription Music Download Music Download Gift Card Total benefit 160000$ 170000$ 190000$ 520000$ Total take 4540000$ Using New System 2022 2023 2024 2025 Total Development Cost -118000$ -118000$ Management Cost -75000$ -82500$ -90750$ -248250$ Total Cost -118000$ -75000$ -82500$ -90750$ -366250$ Search, Sell CDs 210000$ 240000$ 270000$ 720000$
Customer Subscription 2500000$ 3000000$ 3700000$ 9200000$ Music Download 450000$ 510000$ 590000$ 1550000$ Music Download Gift Card 180000$ 210000$ 230000$ 620000$ Total benefit 3340000$ 3960000$ 4790000$ 24150000$ Total take 23430000$
- Organizational feasibility Tune Source will soon become a well-known and widely used product as a result of its increasing earnings and success. CEOs and administrators may keep a careful eye on software ownership at first. Tune Source will be the first music portal because it contains capabilities that other apps don't have (download, find music...). The product's popularity can be due to its ease of use and features, such as the opportunity to listen to rare music and unique tracks exclusively available on Tune Source. II. Discuss whether the project is feasible Here are three Tune Source solutions. The first option is to use Visual Studio tools to assist with C# software development. The second option is to use the Visual Studio Code tool to assist with JavaScript program development. The Apache Netbeans IDE is the third option, which uses the Java language and development tool. - Using C# This is a programming language designed to be simple yet current. It offers a large number of libraries that may be used to create excellent front-end and back-end applications. - Using JavaScript JavaScript is a straightforward programming language. This is a language that can improve the aesthetics and flexibility of a website or app. At the same time, it gives connectivity to tens of thousands of users simultaneously.
References (Anon, 2015: , (Anon, 2015), (Leau, 2012: , (Leau, 2012), (Balaji, 2012: , (Balaji, 2012), (Weinberg, 1991: , (Weinberg, 1991), (TEAM, 2021: , (TEAM, 2021),
