Download Assignment 1. Unit: Software Development Life Cycle and more Exercises Technology in PDF only on Docsity!
ASSIGNMENT 1 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit^ 9:^ Software^ Development Life^ Cycle Submission date 27/2/2023^ Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Dao Mai Xuan Di Student ID BC Class IT05101^ Assessor name Tran^ Van^ Nhuom 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 P1 P2 P3 P4 M1 M2 D1 D
Table of Contents
Describe with an example, why a particular lifecycle model is selected for a development environment (M1)
Table of contents table
Table 1: Advantages and disadvantages of each option ............................................................................................. 19 Table 2:. Presented as a matrix of possible alternatives............................................................................................. 30
INTRODUCTION
The use of common business procedures in the creation of software applications is known as the software development lifecycle. Plan, Request, Design, Build, Document,Test, Implement, Maintenance are the general six to eight steps. Depending on the size of the project, some project managers may combine, divide, or skip steps. These are the fundamental elements that are advised for all software development initiatives. SDLC is a method for monitoring and enhancing development. It makes it possible to thoroughly analyze every stage of the process. By doing this, businesses will be able to maximize efficiency at every turn. Software and developers must now meet increased demands as processing power rises. Businesses must cut costs, deploy software more quickly, and meet or exceed consumer expectations. By detecting inefficiencies and increased costs and resolving them for smooth operation, SDLC aids in the achievement of these objectives.
Figure 1: Spiral Model 1.2. Scrum model: a. Definition: Scrum is an Agile methodology (flexible software development) based on platform and growth. Scrum is designed to support the development, delivery, and improvement of complex products. With Scrum, the product is built in an iterative sequence of processes, known as a sprint. Thereby, you can continuously improve the product, technique, team and work environment. That way, you can provide value to your customers throughout the development process. b. Advantage: Scrum can help teams complete project deliverables quickly and efficiently. Scrum can help teams complete project deliverables quickly and efficiently. Scrum ensures efficient use of time and money. Large projects broken down into manageable sprints Developments are coded and tested during sprint evaluation.
Works well for fast growing projects. Teams get clear vision through scrum meetings Scrum, agile, takes feedback from customers and stakeholders. Short sprints allow for a lot easier feedback-based changes. The individual effort of each team member is visible in the daily scrum meetings. c. Disadvantage: Nothing is perfect and the Scrum method is no exception. In some cases, Scrum combined with other project management techniques can help address some of the following disadvantages: Scrum often leads to scope escalation, due to the lack of a defined end date. Chances of project failure are very high if individuals are not committed or cooperative. Adopting the Scrum framework in large teams is challenging. The framework can only succeed with experienced team members. Daily meetings sometimes frustrate team members. If any team member leaves in the middle of the project, it can have a huge negative impact on the project. Quality is hard to come by until the team undergoes aggressive testing.
c. Disadvantage: In the case of large software projects, it is difficult to assess the effort required at the early stages of the software development life cycle. Agile development focuses more on code and generates less documentation. Agile development relies heavily on customer input. If the client is vague in his vision of the end result, there is a high chance that the project will go astray. Face-to-face communication is more difficult in large organizations. Only senior programmers have the ability to make the necessary decisions during development. As a result, new programmers have difficulty adapting to the environment. Figure 3: Agile Model
2. Sequential model Definition: The Sequential Model API is the simplest and is the recommended API, especially as a beginner..
It is called “sequential” because it involves defining a Sequential class and adding each layer to the model in a linear way, from input to output. 2.1. Waterfall model: a. Definition: Waterfall modeling is an early stage in the SDLC process. In fact, it was the first model widely used in the software industry. b. Advantage: Simple and easy to understand and easy to use. Easy to manage due to the rigor of the model. Each stage has specific products and a review process. Stages are processed and completed at a time. Works well for smaller projects where the requirements are very well understood. The stages are clearly defined. Milestones are well understood. Easy to organize work. Process and results are fully documented. c. Disadvantage: No working software is produced until the end of the life cycle. The amount of risk and uncertainty is high. Not a good pattern for complex and object-oriented projects. Poor model for long and ongoing projects. Not suitable for projects where requirements have a moderate to high risk of change. So risk and uncertainty are high with this process model. It is difficult to measure progress in stages. The change request could not be met. Adjusting scope in the lifecycle can end a project.
The software is developed in the implementation phase so no early prototypes of the software have been released. If any changes occur during the development phase, the test documentation along with the requirements document must be updated again. Figure 5: V Model Describe how technical solutions can be compared (P4)
1. Solutions: In project management, three important feasibility criteria include technical, economic and organizational. These three criteria need to be strictly applied to ensure that the project is implemented effectively and achieves its objectives. 1.1. Technical Criteria: Technical criteria related to the ability to implement and complete the project with modern technologies and techniques. To ensure this criterion, we need to perform the following steps:
Assess the ability to deploy new technology and techniques. Analyze project technical requirements and ensure that they are consistent with existing technologies and techniques. Ensure that project components work well together and can integrate with other systems. Ensure that the project meets performance and quality requirements. 1.2. Economic criteria: Economic criteria relate to the financial elements of the project. To ensure this criterion, we need to perform the following steps: Assess project costs and income potential. Identify the financial resources needed to implement the project and ensure that they are available. Evaluation of the project's expected profit. Ensure that project costs and profits are effectively managed. 1.3. Organization criteria Organizational criteria relate to the ability to organize and manage projects effectively. To ensure this criterion, we need to perform the following steps: Define roles and responsibilities of project members. Ensure that necessary information and resources are effectively shared and managed. Identify the steps needed to manage risks and respond to problems.
2. Advantages and disadvantages of each option: Advantages Disadvantages Technical criteria (^) Provide a common standard by which to judge the quality of a product or service. Helps ensure product or service uniformity. Helps increase reliability and accuracy in measurement and inspection methods. Ensure that the product or service meets customer and consumer requirements. Helps increase synchronization between products or services of the same type. Not all specifications are appropriate for every product or service. Technical specifications may not guarantee the aesthetics or inventiveness of a product or service. It can take time and cost to define and implement technical criteria. Technical criteria can limit innovation and creativity in producing products or providing services.
Organization criteria (^) Focus on organizational structure: Organizational criteria focus on evaluating the structure, processes and procedures of an organization. This assessment can help enhance an organization's efficiency and performance, thereby helping to improve its success. Measuring Sustainability: Organizational Criteria also measure the sustainability of an organization by assessing its activities in terms of the environment, society and economy. This helps to ensure that the organization is making a positive contribution to society and the environment. Improve organizational management: Organizational criteria can also help an organization improve its management by providing important information about enhancing the fit between organizational structure, processes and procedures. From there, it helps to increase management efficiency and reduce chaos in the organization. Failure to measure individual capacity: Organizational criteria do not measure the individual capacity of members of the organization. Factors such as skills, knowledge and personality of individuals in the organization are not assessed in this criterion. Failure to measure cultural harmony: Organizational criteria do not measure cultural harmony among members of the organization. An organization's culture can affect its success, but not all factors in the culture can be measured. Difficult to measure: Organizational criteria can be difficult to measure and evaluate for some Table 1: Advantages and disadvantages of each option Explain how risk is managed in the Spiral lifecycle model (P2)
1. What is a Spiral lifecycle model? The spiral model is a practical approach to developing large-scale software products because the software evolves as the process progresses. In addition, developers and customers better understand and react to risks at each level of development.The model uses prototyping as a risk reduction mechanism and allows prototypes to be developed at any stage of the development process. It maintains a systematic approach, much like the Life Cycle - Model, but combines it into an iterative framework that is more
reflective of the real world. If used correctly, this model will reduce risks before they become an issue. As technical risks are considered at all stages.
2. Risk Handling in Spiral Model. An effective risk management process is an important component of a successful information technology security program. The risk management process should not be seen primarily as a technical function performed by information technology professionals who operate and manage information technology systems, but rather as a function. essential management of the organization. The primary objective of the organization's risk management process should be to protect the organization and its ability to achieve its objectives. 2.1. Risk assessment: Risk assessment is the first process in the risk management approach. Use a risk assessment to determine the extent of the potential threat and its impact on the organization. Consequences are the degree of impact that the potential risk event can have on the achievement of business objectives.. The level 5 rating scale in the risk survey includes: 25-Almost certainly, 20-likely, 15- probably, 10 - unlikely, 5-rare. 2.2. Calculate inherent risk: Inherent risk determines the level of risk arising from a risk event before any action is taken to manage it. Inherent Risk = Consequence X Probability The inherent risk rating will be expressed on a 4 - level rating scale: Extreme Risk, High Risk, Moderate Risk, Low Risk. 2.3. Risk assessment report: There are different types of risk assessment reports. Detail - Risk Report: detailed reports of risks at different stages based on factors of cost, schedule, resources and human resources. Scope - Risk statement: The scope statement or mission statement can be assessed for risk at the beginning of the project. Cost Assessment Risk Reporting: Costs or funds are always at risk in a project. It must be maintained and controlled with as little deviation as possible from the predicted values. 2.4. Risk Report Assessment Schedule: Time is a luxury that a project cannot buy. It is imperative that the time schedule is met with as little delay as possible. Time delays can affect the progress of a project and put it at risk. Such risks are recorded in the schedule assessment risk report. Technical Assessment Risk Report: Risks related to resources, human resources and departments fall into this category. Risks arising from quality limitations and those resulting from poor design and planning errors also fall into this group. 2.5. Keys to a successful risk management program: Commitment of senior management. Full support and participation of the technology team.
