Download Software Development Life Cycle - Assignment 1 - Pass and more Assignments Software Development in PDF only on Docsity!
ASSIGNMENT 01 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 0 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Do Trong Thinh Student ID GCD Class GCD1102 Assessor name Pham Thanh Son 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 P 1 P 2 P 3 P4 M 1 M 2 D1 D 2
Summative Feedback: Resubmission Feedback:
Grade: Assessor Signature: Date: Lecturer Signature:
- A. INTRODUCTION
- B. SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) MODEL
- I. Some popular SDLC model
- Water fall model
- Agile model
- V-model
- Prototyping model
- Spiral model
- II. SDLC model suitable for Tune Source
- Model suitable for project
- Discuss the suitable of each of the SDLC models for the project
- C. IDENTIFY SOME RISKS AND DISCUSS AN APPROACH TO MANAGE THEM
- D. FEASIBILITY STUDY
- I. Discuss the purpose of conducting a feasibility study for the project
- project. Discuss whether the project is feasible II. Discuss how the three feasibility criteria (technical, economic, organizational) are applied to the
- Technical feasibility
- Economic Feasibility
- Organizational feasibility
- III. Discuss alternative technical solutions using the alternative matrix...........................................
- IV. The components of a feasibility report
- Explain a feasibility report
- Discuss economic feasibility study on Tune Source project (NPV, Cashflow, Break-Even Point)
- Discuss whether the project is feasible or not
- V. Describe how technical solutions can be compared
- REFERENCE:
- Figure 1: Waterfall model Table of figure
- Figure 2: Agile model
- Figure 3: V-model
- Figure 4: Protopying model
- Figure 5: Spiral model
- Figure 6: Discuss the suitablility of the model
- Figure 7: NPV
- Figure 8: Break-even point.......................................................................................................................
A. INTRODUCTION Product excellence and customer satisfaction with the system are always top considerations for companies and enterprises. A system must pass through a number of precise and demanding stages in order to be able to build one that satisfies all requirements for entering the market. All of these phases make up the idea of the software development life cycle. In this study, models representing different phases of the software development life cycle will be examined, and the model that most closely matches the viewpoint of the Tune Source firm will be selected. The paper will also look at risks and how to approach and handle them. The last piece will cover the value of a feasibility study in any system and how it fits into the Tune Source project. B. SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) MODEL The Software Development Life Cycle is a method used by software organizations to manage software projects (SDLC). It includes a manual detailing how to develop, improve, alter, or maintain certain software (Balaji and Murugaiyan, 2012). The procedure, which enables all project participants—old and young, within and outside the company— to manage the work synchronously according to their roles throughout the whole business process, or at least at the project level, is one of the main components in the success of software manufacturers.
I. Some popular SDLC model
- Water fall model The Waterfall Approach was the first commonly used SDLC Model in software engineering to assure project success. The entire software development process is split into several phases using "The Waterfall" technique. Typically, the results of one step in this waterfall model serve as the input for the subsequent phases in turn.
Figure 2 : Agile model An agile model's system size enlarges with time as a result of the synthesis of several loops. Between iterations, agile aims to swiftly react to shifting customer demands. Using agile, system development is divided into smaller builds. There will be sufficient planning, requirements analysis, design, implementation, and testing phases in each of these iterations, which normally run 2-4 weeks. They actually don't change all that much from the waterfall method, but after each iteration, users test them and assess any adjustments; if required, features are added before moving on to the next iteration to satisfy user demands. After three to four repetitions, the procedure will be refined, user-friendly, and error-free. Agile is a technique that has several advantages, such as a practical strategy for software development and the capacity to gather user feedback, which guarantees that all user demands are always satisfied in the best way. The work will be finished more rapidly because of the short deadline and the requirement for comprehensive developer training. Agile can demonstrate the effectiveness of the product because users will begin utilizing it immediately following the demo. The resource is not very good because of how slowly it increases. Needs for user customization are complemented by those for environment adaptation. Agile gives developers independence and is easy to maintain. However, there are also significant drawbacks, such as the great pressure to deliver the system and software fast and to verify that all necessary components have been developed in full (Balaji and Murugaiyan, 2012). A system with inadequate users runs the risk of having the model fail or move in the wrong direction since it is useless without user engagement.
- V-model The waterfall method of system or software development is streamlined by the V model. Figure 1 shows how the V model outperforms the waterfall approach by placing a greater emphasis on verification and validation. In order for the activities on the right to verify or check the outcomes of the activities on the left, the bottom half of the waterfall model is bent upward in the shape of a V. More specifically, the right side of the V symbolizes the associated synthesis activities that integrate (and test) various components into a system that satisfies the users' needs. The left side of the V depicts the analysis activities that break the users' demands into smaller, more manageable pieces. The V-model is used in collaboration between the developer and tester. Integration test cases are produced based on the LLD and the HLD (High level document), whereas system test cases are developed based on the requirements (Low-level document). The code is done after that. When the code is finished, unit, integration, and system testing are performed in that order. Each step of development and the testing phase are connected by the V-model. The tester in the V-model will be involved in the requirements process itself, which has all the advantages of the waterfall approach but also allows for requirements to change at any point. The V-worst model has the drawback of being extremely stiff and inflexible. If modifications are made while the project is still in progress, the requirements and test documentation must be updated. It is inappropriate for short-term efforts since stage-by-stage reviews are required. The functional requirements, high level design, low level design, unit testing, system testing, and integration testing that were developed during the requirement phase may all be modified in our case study if the customer updates any of the needs. The V-Model is typically used by larger firms since it demands more resources.
This process model allows clients to see the product early in its life cycle since the system is partially built before or during the analysis step. The initial parts of the process include client interviews and the construction of a high-level paper model that is incomplete. This paper serves as the basis for creating the first prototype, which only offers the most fundamental features requested by the client. The prototype is further improved to address the issues once the customer has identified them. The approach is carried out repeatedly until the user declares the functional model to be adequate and accepts the prototype. Advantages: Early in the life cycle, the clients get to witness the incomplete product. This guarantees higher levels of client comfort and pleasure. Given the potential for improvement, new requirements are easily accomodated. It is easy to spot missing functionality. Errors may be discovered much more quickly, saving time and money while also raising the caliber of the software. The prototype can be used by the developer once more in the future for more difficult jobs. Disadvantages: costly in terms of both time and money. There may be too much variability in the requirements each time the client assesses the prototype. inadequate recordkeeping as a result of continuously shifting consumer needs. Implementing every change that a customer demands is quite difficult for developers. It is hard to predict how many changes would need to be made before the consumer eventually accepted the prototype. After witnessing an early prototype, some customers want delivery of the full product straight soon. Developers that rush to create prototypes could come up with less-than-ideal solutions.
- Spiral model Figure 5 : Spiral model One of the most crucial models for the Software Development Life Cycle that aids in risk management is the spiral model. On a diagram, it seems to be a spiral with several loops. The spiral's precise number of loops changes from project to project and is unknown. A stage in the software development process is represented by each spiral loop. The project manager may alter the precise number of phases required to generate the product depending on the risks of the project. Project managers are crucial to the spiral model of product development because they may dynamically determine the number of stages. The spiral's angular dimension denotes how far along the current phase is, while the spiral's radius denotes the project's overall costs at any given point. Plaining Stage: The development of needs occurs during the planning stage. The baseline spiral is used to gather attribute needs at this phase. As the item increases, this stage of the continuous spirals develops system demands, element information, and unit-level inputs. Additionally, throughout this phase, regular client and consultant interaction is established in an effort to familiarize yourself with the project's components. The operation is completed, and the code is then released into the particular market.
Environment is balance. The technology used is dynamic or stable. There are resources and training available. The requirements do not change on the a regular basis. The project is short.
- Discuss the suitable of each of the SDLC models for the project Factors Uncl ear User Requ irem ent Unfa milia r Tech nolo gy Comp lex Syste m Relia ble Syste m Shor t Time Sche dule Strong Project Manag ement Cost limita tion Visibilit y of Stakeh olders Skills limita tion Docume ntation Compon ent reusabili ty Water fall Poor Poor Good Good Poor Exelient Poor Good Good Excelien t Excelien t Scrum (Agile) Excel ient Poor Poor Good Exce lient Excelie nt Exceli ent Excelie nt Poor Poor Poor V- model Goo d Goo d Good Good Exce lient Excelie nt Exceli ent Good Good Excelien t Excelien t Protot yping Goo d Exce lient Exceli ent Poor Goo d Excelie nt Poor Excelie nt Poor Good Poor Spiral Excel ient Exce lient Exceli ent Exceli ent Poor Excelie nt Poor Excelie nt Poor Good Poor Figure 6 : Discuss the suitablility of the model C. IDENTIFY SOME RISKS AND DISCUSS AN APPROACH TO MANAGE THEM No Risk Possible Cause Consequense Solution 1 Outdated technology 40% Employees lack the training or are too slow to pick up new technology Cannot develop practical features to draw customers and compete with other brands Always keep current with the most recent technologies 2 Lack of personal 10% Employees are regisned or fired Project finished on schedule Prepare extra personnel and direct them to work together. 3 Lack of budget 15% Impact of COVID- 19 on sources of income lacking the resources to develop Utilize dated technology that nevertheless works really well to cut expenses
4 Slow progress 20% Unfair division of labor reputational damage to the business Bind tasks for simple management and shared perspectives. Risk management process with clear illustrations and explanations Risk Management process A project's risk management process is a logical series of steps that decision makers take to maintain the project's execution within defined bounds. In order to address risks in favor of the project, decision- makers must recognize, assess, and act upon them during the course of each project. To do this, they must make use of their organizational framework and administrative procedures. It is believed that key variables that might influence a project's success include the project's complexity and the organizations' maturity. Why is Risk assessment important Risk assessments are vital because they are a key part of a management strategy for occupational health and safety. They have to: Create awareness of hazard and risk. Identify who may be at risk (employees, cleaners, visitors, contractors, the public, etc.) Determine whether a control program is required for a particular hazard. Prevent injuries or illnesses, especially when done at the design or planning stage. Prioritize hazards and control measures. What is the purpose of risk analysis? By putting management strategies into place, risks may either be removed when necessary or have their level of risk reduced. This is the aim of the risk assessment process. By doing this, you've improved the safety and wellness of the workplace. Steps of the Risk Management Process D. FEASIBILITY STUDY
I. Discuss the purpose of conducting a feasibility study for the project
A feasibility study is a document that assesses the viability of a group of suggested project options or solutions. When writing a feasibility report, the author assesses the viability of many solutions before making a suggestion for the best one. Following that, they give their advice to the firm and provide the feasibility report.
III. Discuss alternative technical solutions using the alternative matrix
Technical feasibility Website development technology is fairly sophisticated at the moment, with various modern technologies including C#, Java, PHP, and JavaScript. The technologies listed above make it easy and practical to develop a website with useful features to meet the needs of the Tune Source company. The technical aspects are therefore perfectly feasible. Economic Feasibility With a growth rate of between 3% and 5%, yearly revenues were $40 million last year. As a result, this business has a highly steady and expanding consumer base. This idea is entirely possible from an economic perspective. Organizational feasibility By choosing the right people for the tasks and giving each department a commander with the right responsibilities, powers, and functions, the organization can achieve its stated objectives. This is a workable practicality.
IV. The components of a feasibility report
- Explain a feasibility report Defination A feasibility study determines if a proposed plan or project is feasible. A feasibility study evaluates the viability of a project or commercial venture to see whether it has a good chance of success. The purpose of the study is to find any problems and concerns that could arise while working on the project. The components of a feasibility report Executive summary: Describe the project, product, service, plan, or business in detail in a narrative. Technological considerations: What will it require, inquire. Have you got it? Can you get it if not? What is the price? Existing marketplace: Analyze the regional and global markets for the proposed product, service, business, or plan. Marketing strategy: Describe it in detail. Required staffing: What kind of human resources are required for this project? An organizational chart should be created. Schedule and timeline: Include key intermediate milestones when estimating the project's end date.
Project financials. Findings and recommendations: Divide technology, marketing, organization, and finances into smaller groups.
- Discuss economic feasibility study on Tune Source project (NPV, Cashflow, Break-Even Point) Figure 7 : NPV Net Present Value (NPV) In our earlier discussion of inflation, we looked back at the past, but in this case, we must look forward. We previously observed that an increase in the inflation rate causes an increase in the pricing of goods and services. In this case, however, we must do the reverse, or deflate or discount (as the finance community likes to call it) future cash flows by a particular rate, r. The future cash flow is divided by (1+r) increased by the year to achieve this. However, we do not utilize the inflation rate in this instance. The Weighted Average Cost of Capital, or WACC, is what it is all about. Cashflow Financial feasibility is described as "a property that can generate enough revenue to pay its own debt to fund the project and to deliver a cash return to the developer and its investors." Knowing if a project is financially feasible can help assess the potential Return of Capital and Return on Capital. Return on Capital is the payback to equity partners, whereas Return on Capital is the distribution of earnings. Discounted cash flows are utilized in the third stage of income property development to assess a project's financial sustainability and attractiveness to potential investors. Break-Even Point
With a growth rate of between 3% and 5%, yearly revenues were $40 million last year. As a result, this business has a highly steady and expanding consumer base. This idea is entirely possible from an economic perspective. Organizational feasibility The company may accomplish its stated goals by assigning each department's commander the proper responsibility, authority, and duties, as well as by selecting the best personnel for the job. This is a plausible scenario.
V. Describe how technical solutions can be compared
Evaluation Criteria Relative Importa nce Alternati ve 1: using C# Scor e (
- 5) Wei gh ted scor e Alternati ve 2: using JavaScri pt Scor e ( - 5) Wei gh ted scor e Alternati ve 2: using PHP Scor e ( - 5) Weight ed Score Technical issues: Front-end and backend support 10 Only backend 5 50 Both fronted and 7 70 Only backend 5 50 backend 7 70 Only backend
Capable of running on Windows Server 10 Current system uses Window 60 server 5 50 Current system fully supports 5 50 Current system fully support Js
Multimedi a libraries 10 Microsof t support 6 60 Easy to find source code in library 5 50 Easy to find open source library
Econimic issues: The license is less than $5 2000 10 Visual studio + .NET framwor k cost $ 4 40 Free for commer cial use 5 50 Free for commer cia I use
A server costs less than S 1000 per year 10 Reuse current server 5 50 Reuse server 3 30 Reuse server
Organizatio nal issues: Capable of hiring a senior developer 10 Very high salary 3 30 No easy to find 5 150 Easy to find
