Docsity
Log inSign up
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search Store documents

The best documents sold by students who completed their studies

Search through all study resources
Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

University Rankings

Discover the best universities in your country according to Docsity users

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

From our blog

Exams and Study
Go to the blog

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

Danang College of Technology (DCT)Information Technology

An in-depth analysis of the Spiral software development model, focusing on its risk management process. The Spiral model is an iterative SDLC (Software Development Life Cycle) approach that combines elements of the waterfall model with risk analysis. how risk is identified, managed, and resolved throughout the four phases of the Spiral model: goal setting and solution finding, risk analysis and resolution, development and testing, and final review. It also discusses the benefits of using the Spiral model for managing risks in software projects.

Typology: Study Guides, Projects, Research

2019/2020

Uploaded on 10/02/2022

nguyen-thi-tuyet-nhung
nguyen-thi-tuyet-nhung 🇻🇳

4

(3)

21 documents

1 / 35

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
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
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23

Partial preview of the text

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 : IT

STUDENT ID : BDAF

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/ Date received (1st sub- mission) Re-submission date Date received (2nd submission) Student name Nguyen Thi Tuyet Nhung Student ID BDAF 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 D

ii

TABLE OF CONTENT

Contents TABLE OF CONTENT .............................................................................................. ii LIST OF TABLES AND FIGURES .......................................................................... iv LIST OF ACRONYM ................................................................................................. v INTRODUCTION ...................................................................................................... 1 CHAPTER 1. DESCRIBE DIFFERENT SOFTWARE DEVELOPMENT LIFECYCLES. (LO1) ........................................................................................................... 2 Describe two iterative and two sequential software lifecycle models. (P1) ..... 2 1.1 Waterfall model ....................................................................................... 2 1.2 V-model................................................................................................... 5 1.3 Agile model ............................................................................................. 7 1.4 Spiral model .......................................................................................... 10 1.5 Choose one that you think suitable for the project and explain why? .... 12 Explain how risk is managed in the Spiral lifecycle model. (P2) ................... 13 2.1 Definition of Risk Management Process ............................................... 13 2.2 Risk management in the Spiral model .................................................. 14 2.3 Project risk management ...................................................................... 15 2.4 Steps of the Risk Management Process ............................................... 15 CHAPTER 2. EXPLAIN THE IMPORTANCE OF A FEASIBILITY STUDY. (LO2) .. 17 Explain the purpose of a feasibility report. (P3) ............................................ 17 1.1 Definition of feasibility report ................................................................. 17 1.2 Purpose of feasibility study ................................................................... 17 1.3 Types of feasibility study ....................................................................... 18 1.4 Benefits ................................................................................................. 20 1.5 Feasibility study for the project.............................................................. 20

iii

v

LIST OF ACRONYM

SDLC Software Development Life Cycle UAT User Acceptance Testing

Perfomed Student: Nguyen Thi Tuyet Nhung 1

INTRODUCTION

First of all, I would like to thank my family for their enthusiastic encouragement and invaluable support for me to complete this assignment. Next, I would like to thank my subject teachers for guiding me, helping me achieve good academic results, and thanking all my friends for exchanging and supporting me. Software Development Life Cycle is an essential knowledge for those of you who intend to become a professional software testing engineer in the future. SDLC has many benefits such as measuring system growth and costs, enhanced monitoring of complex and important projects, providing a lot of documentation, when delivering software ensures accuracy and correctness. deadlines, etc. To learn more about SDLC, see the report below, which includes the following sections:  Chapter 1: Describe different software development lifecycles.  Chapter 2: Explain the importance of a feasibility study.

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 6

  • The validation uses dynamic analysis method, must execute the code.
  • Development and quality assurance activities are carried out concurrently.
  • Verification and validation activities go hand in hand. 1.2.3 Phases PHASES ACTIVITIES PERFORMED Design Phases Requirement Analysis Gather requirements, details, and software specifications from the customer's wishes. System Design Design the complete system, hardware setup and communication for product development. Architectural Design The design of the system will be broken down into modules that undertake various functions. Internal and external modules (other systems) have clear data transmission and communication. Module Design The system will be divided into many small modules, the detailed design of the modules will be specified. Testing Phases Unit Testing This phase is done to eliminate bugs at the code or unit level. Integration Testing Once unit testing is completed, Integration Testing will be executed immediately. Modules will be integrated and the system will be tested. System Testing Test the complete application with functionalities, interdependencies and communication. Test all functional and non-functional requirements of the developed application.

Perfomed Student: Nguyen Thi Tuyet Nhung 7 User Acceptance Testing (UAT) UAT is performed in a user environment similar to a production environment. This phase is intended to verify that the delivered system meets all user requirements, and is therefore ready for real-life use. Table 2. Phases of V-model 1.2.4 Advantages and Disadvantages Advantages:

  • Highly disciplined, stages are completed at once.
  • Organizational management and development.
  • Works well for small to medium sized projects with clear requirements.
  • There are specific activities and plans for the testing process.
  • The implementation checks from the first stage, so the ambiguity is defined right from the start.
  • Easy to manage as each stage has clear goals.
  • Simple, easy to use.
  • Try to spot bugs in the first place. Disadvantages:
  • Little flexibility, but still rigidity.
  • Not suitable for large, complex projects and unclear requirements.
  • High risk and uncertainty.
  • Repeating stages is not supported.
  • It's not easy to handle concurrent events. 1.3 Agile model 1.3.1 Definition The Agile model is a combination of a cyclically iterative process, increasing the focus on process adaptability and customer satisfaction by rapidly delivering software products

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 12

  • Suitable for large and important projects.
  • Control and approval of documents are strictly implemented.
  • Customers can give feedback about the product. Disadvantages:
  • Risk analysis in each stage is time consuming and expensive.
  • Not suitable for simple and small-scale projects.
  • Time and cost are limitless.
  • Ask for more documentation.
  • If there is a risk, it will not meet schedule or budget.
  • In this model, the success depends on the risk analysis stage. 1.5 Choose one that you think suitable for the project and explain why? I will choose the Spiral model for the project. The reason is:
  • Focus on analysis and risk orientation for software projects.
  • This model helps to reduce many risks, as prototyping and evaluation are done continuously.
  • This model supports the response and implementation of customer change requests.
  • Customers can give feedback and reviews in each stage of the Spiral model, so guest satisfaction is higher.
  • Spiral model is suitable for complex and large-scale projects. And suitable for projects with constantly changing requirements from customers.
  • In addition, it is also suitable for projects such as frequent release requirements, unclear requirements, complex and large software requirements, etc.

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.