Risk Management in the Spiral Software Development Model, Study Guides, Projects, Research of Information Technology

Download Risk Management in the Spiral Software Development Model and more Study Guides, Projects, Research Information Technology in PDF only on Docsity! BTEC FPT INTERNATIONAL COLLEGE INFORMATION TECHNOLOGY ASSIGNMENT 1 UNIT: SOFTWARE DEVELOPMENT LIFE CYCLE STUDENT : NGUYEN THI TUYET NHUNG CLASS : IT16101 STUDENT ID : BDAF200008 SUPERVISOR : NGUYEN HOANG ANH VU DaNang, March 2022 ASSIGNMENT 1 FRONT SHEET Qualification BTEC Level 4 HND Diploma in Business Unit number and title Unit: Software Development Life Cycle Submission date 14/03/2022 Date received (1st sub- mission) Re-submission date Date received (2nd submission) Student name Nguyen Thi Tuyet Nhung Student ID BDAF200008 Class IT16101 Assessor name Nguyen Hoang Anh Vu Student declaration I certify that the assignment submission is entirely my own work and I fully understand the con- sequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature: TUYETNHUNG Grading grid P1 P2 M1 D1 P3 P4 M2 D2 iii Describe how technical solutions can be compared. (P4) ............................ 21 2.1 Definition of technical solution ............................................................... 21 2.2 Technical solution can be compared on the following points ................ 22 2.3 Solution for the Tune Source project ..................................................... 23 Discuss the components of a feasibility report. (M2) .................................... 25 CONCLUSION ........................................................................................................ 26 CRITICAL EVALUATION ....................................................................................... 27 REFERENCES ....................................................................................................... 28 iv LIST OF TABLES AND FIGURES Table 1: Phases of waterfall model ...................................................................................... 4 Table 2: User Acceptance Testing ………………………….………..…….…………………….7 Table 3: Phases of Agile model ………………………….………………………………….……9 Table 4: Phases of Spiral model …………….…………………….……………….……………11 Figure 1: SDLC .................................................................................................................... 2 Figure 2: Waterfall model..................................................................................................... 3 Figure 3: V-model ................................................................................................................ 5 Figure 4: Agile model ........................................................................................................... 8 Figure 5: Spiral model ....................................................................................................... 10 Figure 6: Risk Management Process ................................................................................. 13 Figure 7: Spiral model ....................................................................................................... 15 Figure 8: Risk Management Process ................................................................................. 16 Figure 9: Feasibility study .................................................................................................. 17 Figure 10: Technical Feasibility Study ............................................................................... 18 Figure 11: Economic Feasibility Study ............................................................................... 19 Figure 12: Schedule Feasibility .......................................................................................... 20 Figure 13: Technical solutions ........................................................................................... 21 Figure 14: Performance ..................................................................................................... 22 Figure 15: Efficiency .......................................................................................................... 22 Figure 16: Budget .............................................................................................................. 23 v LIST OF ACRONYM SDLC Software Development Life Cycle UAT User Acceptance Testing Perfomed Student: Nguyen Thi Tuyet Nhung 3 Figure 2. Waterfall model 1.1.2 Characteristics - The software development process is divided into many different stages and each phase will have different tasks and goals. - In this model, there is no overlap. The output of one phase is the input of the next phase. It's like the stage that must be completed before the next one can begin. - Each stage of the waterfall model must be precisely defined. 1.1.3 Phases A waterfall model consists of 6 stages NO PHASES ACTIVITIES PERFORMED 1 Requirement Gathering stage Collect and grasp all the necessary requirements, then discuss and guide to understand the requirements properly. Do test the requirements to see if these requirements are suitable for testing in the next steps. 2 Design stage Based on the requirements, create the design. Discuss and document the hardware/software requirements and then they will document the design. 3 Built stage Based on design create programs or code, then integrate the code again for the next stage. Unit test this piece of code. Perfomed Student: Nguyen Thi Tuyet Nhung 4 4 Test stage Integrate unit tested code and test it to make sure it there is activity. Perform a test of the entire system to see if it is running smoothly. In case of abnormality, report it. Then finalize the test report. 5 Deployment state Ensure that the environment is still working, there are no server opening errors and that the test criteria are met. Then deploy the application in the respective environment. Do an environment test after the application is deployed to make sure the application is free of problems and crashes. 6 Maintenance stage Always make sure the application is still running and running in the respective environment. If the user encounters an error, the problem must be resolved and fixed. The application must always be enhanced to be able to combine many features, update the environment with the latest features. Table 1. Phases of waterfall model 1.1.4 Advantages and Disadvantages Advantages: - Easy to deploy and use. - The process is simple, easy to understand and easy to manage. - Suitable for simple, small-scale projects. - For small projects, the waterfall model will work well and give very good results. - There are many documents that provide information to customers. - Input and output re- quirements are clear, so the work process is easy and quality. Disadvantages: - Do not accept changing requirements, project scope. - Not suitable for projects where requirements change frequently. Perfomed Student: Nguyen Thi Tuyet Nhung 5 - It is very difficult to move back to the previous stage. - Unexpected risk is not easy to handle. - For large and complex projects, the waterfall model is not suitable because of the high risk factor. 1.2 V-model 1.2.1 Definition V-model is one of the most widely used software development processes. It is an extension of the waterfall model. V-model is also known as verification model and validation model. Verification: is a static analysis technique. It executes the test without having to run the code. Confirmation: is a dynamic analysis technique. It performs testing by executing code. Figure 3. V-model 1.2.2 Characteristics - Quite similar to waterfall model, also executes processes sequentially, each stage must be completed before executing the next stage, only difference is that the test is trong mô hìnhexecuted at the same time with each stage. - The test execution in the V model takes place right from the requirement gathering phase. - The verification uses static analysis method, no need to run the code. Perfomed Student: Nguyen Thi Tuyet Nhung 8 active. In the Agile model, the project will be handled in different ways and the method that best suits the requirements. Tasks will be broken down into small time frames to easily deliver specific features for a release. Figure 4. Agile model 1.3.2 Characteristics - Each product will be broken down by the Agile model into several small incremental builds, and these builds will be delivered in iterations. - Each iteration typically lasts from about one to three weeks and includes functions such as planning, requirements analysis, design, coding, unit testing, and acceptance testing. - Each project will be handled and there are different methods to best suit the requirements of that project. - The task is broken down into several small time periods to deliver a specific feature for a release. 1.3.3 Phases NO PHASES ACTIVITIES PERFORMED 1 Requirement Evaluate the project as a whole, then determine the time and resources required for development. Also, assess risk and prioritize functions differently depending on business value. Perfomed Student: Nguyen Thi Tuyet Nhung 9 2 Design Discuss the order in which features are introduced and identify the necessary tools, programming languages, syntax libraries, and underlying frameworks. User interface templates can be created. 3 Development and coding After agreeing on the plan, the product will be distributed in stages. Each phase will be designed to be an improvement over the current version. The first release will likely go through many changes to provide improved functionality and new features. 4 Integration and testing At this stage, the product is already available, so tests must be carried out to check and make sure that the software is fully functional. If a problem or potential error is found, it must be rectified immediately. Then record the consumer feedback. 5 Implementation and deployment The software is fully deployed and available. During this phase, it must be ensured that the system is running smoothly and that if there is a new error, it must be fixed immediately. 6 Review After completing all previous stages of development, re-statis- tical results have been achieved in meeting the requirements. Then, the software development phases of the Agile model will start over, either with a new iteration or move on to the next phase. Table 3. Phases of Agile model 1.3.4 Advantages and Disadvantages Advantages: - Agile model is a logical and practical approach to software development. - Minimum resource requirements. - Promote effective teamwork and cross-training. - Suitable for environments with constantly changing requirements and fixed needs. Perfomed Student: Nguyen Thi Tuyet Nhung 10 - Documentation is easy to use. - Quickly come up with partial working solutions. - There are minimum rules. - Virtually no planning is required. - Easy management, easy handling and high flexibility. Disadvantages: - Not suitable for handling complex environments. - Sustainability, maintainability and scalability are high risk. - Supply management strictly stipulates the scope, functions to be provided, and adjustments to meet deadlines. - Agile relies heavily on customer interaction, if the customer is not clearly defined, it can be misguided. - Documentation is minimal so the reliance on the individual is very high. - Difficulty in transferring technology within the group due to lack of documentation. 1.4 Spiral model 1.4.1 Definition The spiral model is an SDLC model, it is a combination of elements of waterfall model with iterative software development tissue. The Spiral model also shares many similarities with the incremental model. Figure 5. Spiral model Perfomed Student: Nguyen Thi Tuyet Nhung 13 Explain how risk is managed in the Spiral lifecycle model. (P2) 2.1 Definition of Risk Management Process Risk management is a set of systematic, scientific and regularly performed processes to identify, analyze, prevent and find solutions to handle risk factors. and control risks that may arise in the course of operation, in order to avoid causing disadvantages and limitations for enterprises. Risk management helps businesses proactively prevent risks and their development goals will be on the right track. In addition, it also helps to seize many new opportunities to compete in the market. Figure 6. Risk Management Process Example: DaNang Green is a large and famous travel agency in Da Nang city. The risks and risk settlement options are:  Risks due to external impacts: are force majeure risks such as the current situation of the Covid-19 epidemic. Because of the increasing number of disease cases, the Government requested to avoid large gatherings. Therefore, Danang Green implements the plan that each time you gather with the right number of people, customers will be tested for covid and always wear a mask.  Risks from customers: customers do not comply with regulations on epidemics, aviation, violate the law or customers get sick, have accidents, etc. DaNang Green will coordinate and work with company branches at the destination for timely processing. Perfomed Student: Nguyen Thi Tuyet Nhung 14  Risks from employees: employees do not follow the correct process and order to advise customers on regulations, policies and procedures. DaNang Green will have annual training sessions for employees to have more business, legal, legal and other skills.  Airline risk: flight cancellation or delay. In this case, DaNang Green also has contingency plans such as canceling or postponing the tour to minimize the damage committed to the customer. 2.2 Risk management in the Spiral model - The spiral model is a practical approach to developing large-scale and complex software products because software evolves as the process progresses. - The spiral model will use prototyping as a tool to reduce risk and it allows the development of prototypes at any stage in the development process. - The spiral model has four phases, first goal setting and solution finding, risk analysis and resolution, development and testing, and final review.  In the first stage, requirements gathering and analysis, then goal identification and search for different alternatives.  Next, the proposed solutions will be analyzed. Any potential risks are identified and addressed.  Next, implement various features, then the implemented features are verified and tested thoroughly.  Finally, the customer will give a review of the software. Simultaneously identify and manage risks such as cost overruns, and begin planning for the next phase. - When the first phase begins it has the ability to manage potential risks. - Each phase in the spiral model begins with design requirements and goals. It will then end with the client checking the progress of each phase. - In each stage, it is capable of prototyping, each of which is considered a risk management technique. Perfomed Student: Nguyen Thi Tuyet Nhung 15 Figure 7. Spiral model 2.3 Project risk management - Lack of personnel: leading to project fire, unable to complete on schedule. To address this risk, employees will work 4 hours overtime in the evening and pay will be doubled. It is not possible to recruit new personnel, because it will take time to transfer and re-train. - The coding process generates an error: resulting in the product not meeting the customer's requirements. The solution is to meet with customers 1 to 2 times a week to understand and better understand the requirements of customers. - The project's goals and needs are not clearly defined: leading to the project being derailed. In this case, the requirements should be clearly documented. - Project planning and schedule malfunction: resulting in timely completion of the project will not be possible. The way to fix it is that the team leader will monitor and report daily, when there is a problem, it must be reported to the Project Board soon and resolved immediately. Also, provide a backup schedule if the completion date is exceeded. - Project conflicts: to resolve, regular team meetings should be held to review conflicts. When found, immediately resolve the conflict. 2.4 Steps of the Risk Management Process To be able to determine the most accurate risk range, it is necessary to perform 5 steps. The 5 steps to take to determine the scope of risk are: Perfomed Student: Nguyen Thi Tuyet Nhung 18 Feasibility study is an important step, it checks various factors like cost to create and implement the system, suitable time for each step of the system, etc. If these factors are not analyzed and considered, it will affect the organization and development of the project, and the project system will collapse completely. So, to do it right, after analyzing and reviewing the system requirements, the next step is to analyze the software requirements. The project team must meet and communicate with the customer to clearly understand the customer requirements and analysis. It is then possible to identify and generate a report of the difficulty and problem. Once the document is created, the next step in this phase is to perform a comprehensive analysis, including details such as the project plan, schedule, and expected costs for the design and implementation of the system, etc. Feasibility studies help identify potential risks and problems that may arise during project development. Then it will give the possible options and priority options in the research process. Feasibility studies help determine if a project has the right people, financial resources, and technology. Feasibility study helps to assess whether the project as well as its needs, conditions and prospects are successfully implemented and worth the investment. Unfeasible projects, will be hindered by many factors such as lack of funding and unclear feasibility, when the application can lead to additional costs, the implementation cost of the project is exceeded profit. Feasibility studies help confirm market opportunities, narrow down alternatives, document benefits and risks, and provide more information before making a decision. 1.3 Types of feasibility study Technical Feasibility Study: provides a focused approach and assessment of tool resources to see if it is stable. Determine if the technical resources are sufficient to fulfill the software requirements within the budget and time specified. In addition, it also includes an assessment of the system's hardware, software, and other requirements. Figure 10. Technical Feasibility Study Perfomed Student: Nguyen Thi Tuyet Nhung 19 Economic Feasibility Study: helps determine if the requested software can generate financial returns. It includes breakdowns of incidental costs, research costs, and estimated software and hardware costs. Help determine the viability, costs, and advantages of a project. Figure 11. Economic Feasibility Study Management Feasibility Study: organizational structure and project management will be solved based on this feasibility, it is certain that the proposed structure that will be mentioned in the submission is feasible for activities are performed. Operational Feasibility Study: analyze and determine if the levels and needs of the organization can be met to complete the project. It helps to check the plan of a project whether it satisfies all the defined requirements. Financial Feasibility Study: is the ability to raise enough capital needed to implement the project. Some other aspects of this viability that should be considered include creditworthiness, lending capacity, equity, and loan schedule. Schedule feasibility: it is the most important assessment that determines the success of the project. The amount of time required to complete the project should be determined. When all factors have been thoroughly checked, viable programming can help identify risks and problems that the project may face: internal constraints such as technical, technological, financial constraints key and resources; financial constraints, marketing, export, etc. There are also external constraints such as environment, laws and regulations, etc. Perfomed Student: Nguyen Thi Tuyet Nhung 20 Figure 12. Schedule Feasibility Environmental Feasibility Study: it is very important in the implementation of any potential projects. In the early stages, should be considered. All relevant information about the environment will be recorded or reported so that actions can be taken and problems resolved. This feasibility study also includes the possibility of obtaining the necessary project permits and approvals at an appropriate cost. 1.4 Benefits - Analyze and support thorough testing of system requirements. - Identify risks associated with the system and assist in planning risk analysis. - Generate cost and benefit analyzes to help organizations and systems operate efficiently. - Help distinguish the pros and cons of undertaking a project before investing in it. - Helps identify how it works, potential risks, competition, market analysis, and funding needed for growth. - Before a product is produced, it is necessary to carry out feasibility studies, which will help to develop and maintain the system effectively within budget spending. 1.5 Feasibility study for the project The customer requested a music website to increase sales in the store. But the client is concerned about the look of the website and the cost of the project. Feasibility studies explore the current latest technology needs, benefits to customers, and long-term viability. A modern sales website will expand the business and attract more buyers. Perfomed Student: Nguyen Thi Tuyet Nhung 23 2.2.3 Budget Budget is the amount required for the project to maintain and complete. If the budget is too small, it will be difficult to cover costs such as technology, labor and risks in the software. On the contrary, if the budget is fully funded, financial problems will be solved and credibility can be enhanced. Figure 16. Budget 2.3 Solution for the Tune Source project - For technical solution, implement front-end design in html and css languages. Back- end design in Java language, with mySQL database connection or SQL server. - For the organizational solution, the project team needs about 40 members. Team members will be clearly trained about the project to understand the project. The work to be done of the project such as requirements gathering, planning, risk identification and analysis, design, testing, ... will be divided equally among team members. - As for the economic solution, to complete the project will range from about 3500 to 5000 USD, not including the additional costs incurred due to unexpected incidents. The salary of the employees is 3 dollars for an hour of work, if overtime work in the evening, the salary will be doubled. Merchandise sales can range from $4500 to $7000, not to mention possibly earning additional revenue from shipping. In summary, the project is still profitable. In terms of importance, the solutions can be classified as economic, technical and organizational respectively. Because without the cost and capital to pay the necessary sums, the project cannot be carried out. ✸ In the Tune Source project, we went through five stages of completing the feasibility to come up with a plango in the best and most complete direction, including: Perfomed Student: Nguyen Thi Tuyet Nhung 24  Step 1: Preliminary analysis Screening project ideas before investing, to avoid losing a lot of time, effort and money. Therefore, it is necessary to check and conduct preliminary analysis. For a preliminary assessment, four steps are required is Create concept sketches, assess the market space for the project, test the competitive advantage and identify the risks of the project. Preliminary assessment is complete, helping to determine whether to continue with the project's viability. If the risks can all be resolved, then move on to a feasibility study.  Step 2: Outline the project scope At this stage it is necessary to identify and explain issues such as whether the plan is technically, economically and operationally feasible, legal, and feasible within a certain period of time. reasonable time. Once the above issues are identified, the project's principles will be outlined, such as situations and problems to be solved, objectives to be accomplished, etc.  Step 3: Market research At this stage, help identify other market opportunities for the project like new customers, additional uses, etc. Helps to better understand competitors and potential customers' needs. Understand and identify the best way to execute the project, such as time, required staff and management. To conduct market research, implement methods such as surveying and interviewing customers, experts... observing other organizations, listening to social media, etc.  Step 4: Main cost calculation At this stage, it is necessary to determine where the financial resources come from, the costs of the risks when implementing the project, the risks that cause a lot of damage to the project's budget, etc. Estimate financial costs for the project is higher, in case unexpected problems occur.  Step 5: Review the study and present the results The review aggregates everything analyzed and accomplished in the project, and then presents it to the client and stakeholders. If there are some feasibility concerns, the approach and budget should be re-evaluated to better suit the project. Perfomed Student: Nguyen Thi Tuyet Nhung 25 Discuss the components of a feasibility report. (M2) Feasibility Study activities are general in nature and can be applied to all types of projects such as systems and software development or any other project. Basically, the Feasibility Study has six parts as follows: o Project Scope: used for problem identification and resolution. The scope must be precisely defined, and the problem must also be clearly stated, otherwise it may cause confusion among project participants. o Current analysis: used to identify and analyze current performance methods. At this stage, the system will not be too large to detect, except for some minor problems that need to be fixed simply. Analysts will be warned not to stop and fix any problems encountered during this period, instead, they only need to detect problems. Therefore, this stage saves time and costs for later. o Requirements: how requirements are defined depends on the object of the project. o Approach: there are various alternatives and they will be considered with an explanation of why they are the preferred solution chosen. At this stage a thor- ough analysis is needed to take the next step. o Evaluation: analyze and determine the cost of the chosen approach. First, an- alyze the total estimated cost of the project. In addition to the chosen solution, other alternatives also need to be estimated. Then need to estimate the cost of labor and project schedule. Once the total cost of the project has been com- pleted, a full cost report should be prepared. o Review: hold a formal review with all stakeholders to be able to ensure that the previous elements are all incorporated into a Feasibility Study. At this stage, it is necessary to review and demonstrate the thoroughness and accu- racy of the Feasibility Study to be able to make decisions related to the project, whether to accept, reject or request amendments before Make the final deci- sion. If accepted, all parties involved must sign the document expressing their acceptance and commitment to it. Conversely, if denied, the reason for the refusal must be clearly stated, explained and attached to the document.