Download 1631 assignment 2 2023 and more Schemes and Mind Maps Network Design in PDF only on Docsity!
ASSIGNMENT 2 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Tran Van Khoi Student ID BH Class IT0501 Assessor name Nguyen Thai Cuong 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 P5 P6 P7 M3 M4 M5 M6 D3 D
❒ Summative Feedback: ❒ Resubmission Feedback: Grade: Assessor Signature: Date:
II. Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation.
A. Introduction Hello teacher. My name is Tran Van Khoi, currently studying in class IT0501 of BTEC British College. Today I will present ASM 2. In the content of ASM 2 I present the following main points:
- Identify the stakeholders, their roles and interests in the case study.(P5)
- Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation. (P6)
- Explain how user and software requirements have been addressed. (P7) B.Content TASK 1 – ANALYSIS (1) I. Identify the stakeholders, their roles and interests in the case study.(P5)
1. Requirement difinition of the project 1.1. Identify the stakeholders, roles, and interests in the case studey a. Definition - Project requirements are conditions or tasks that must be completed to ensure the success or completion of the project. They provide a clear picture of the work that needs to be done. They're meant to align the project's resources with the objectives of the organization. The benefits of effectively gathering project requirements include cost reduction, higher project success rates, more effective change management, and improved communication among stakeholders. b. Categories Project requirements can be categorized into three main categories: business, solution, and stakeholder requirements.
Business requirements are the high-level needs of the business. They address what's required and why the project is happening. Getting back to our house example, a business requirement might include, 'build an eco-friendly house with high-efficiency solar panels that will reduce carbon emissions and reduce environmental impact.' This is the starting point of the project and provides guidance for the other types of requirements. It's imperative that these requirements are communicated clearly and early on. Solution requirements , which include both functional and non-functional requirements, are the specific features and characteristics of the product or service that meet all requirements, both business and stakeholder. Functional requirements describe something that a product or service is required to do. Non-functional requirements describe how a system is supposed to function. A functional requirement for your solar panel is to 'convert light into electricity,' while the non-functional requirement is to 'produce this electricity at an efficiency rate of 20%.' A stakeholder is anyone who has an interest in the product or service that's being produced or provided. They may be internal stakeholders (employees) or external stakeholders (customers, regulators, or suppliers). Every individual stakeholder has specific needs or requirements that they want to be fulfilled. Each of these needs must be balanced during the course of the project. Often times, stakeholders have competing needs, which can impact the schedule, budget, and scope of the project if not managed effectively. Suppose, as the owner of the house, you decide that you want repurposed composite wood for the exterior of your house. However, after your builder has placed the order, you discover that your Home Owners Association only allows for stucco and brick exteriors. This change will have a knock-on effect in terms of pricing, materials and design and will ultimately slow down the project. When a stakeholder happens to be your customer, you need to ensure that you're eliciting their exact requirements in order to deliver on your product or service. If the right questions are not asked using the right method, you will not meet customer needs and, in the end, the project will have failed. c. Requirement Gathering Methods There are several different ways to collect requirements that vary depending on the type and complexity of the project. There are advantages and drawbacks to each method. It's best to use a combination of these techniques and avoid taking shortcuts when it comes to collecting project requirements. The success of the project is directly related to how well requirements are communicated, documented, and carried out. A best practice is to ensure that you're including as many stakeholders as possible.
Figure 1 : project
b. Types of stakeholders in project management There are two main types of stakeholders in project management, internal and external. Internal stakeholders These stakeholders are coming from within the house!!! Internal stakeholders are people or groups within the business, such as team members, managers, executives, and so on. External stakeholders External stakeholders are — as you can probably guess — people or groups outside the business. This includes customers, users, suppliers, and investors. c. Examples of stakeholders in a project The stakeholders in each particular project will vary depending on the type of project and industry, but here are a few examples of the types of stakeholders in project management you might need to consider: Project manager Team members Managers Resource managers Executives Senior management Company owners Investors
Other Responsibilities : Apart from the above four major roles they also have some other roles to play in the company. They can identify new areas for market penetration and increased sales. They can bring in more marketing ideas. They also attract other investors like honeybees in the company. They can be a part of a selection board or a representative for the company. Moreover, they can take all the major social and environmental decisions.
2. Identify FRs and NTRs of the Tune Source Project 2.1. Functional Requirements a. What is a Functional Requirement? A Functional Requirement (FR) is a description of the service that the software must offer. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs. It can be a calculation, data manipulation, business process, user interaction, or any other specific functionality which defines what function a system is likely to perform. Functional Requirements in Software Engineering are also called Functional Specification.
Figure 2 : Functional Requirement b. What should be included in the Functional Requirements Document?
- Functional Requirements of a system should include the following things: Details of operations conducted in every screen Data handling logic should be entered into the system
Administrative functions Authorization levels Audit Tracking External Interfaces Historical Data management Legal and Regulatory Requirements e. Example of Functional Requirements Below are the popular functional requirements examples: The software automatically validates customers against the ABC Contact Management System The Sales system should allow users to record customers sales The background color for all windows in the application will be blue and have a hexadecimal RGB color value of 0x0000FF. Only Managerial level employees have the right to view revenue data. The software system should be integrated with banking API The software system should pass Section 508 accessibility requirement. 2.2 Non-Functional Requements a. What is Non-Functional Requirement? Non-Functional Requirement (NFR) specifies the quality attribute of a software system. They judge the software system based on Responsiveness, Usability, Security, Portability and other non-functional standards that are critical to the success of the software
system. Example of nonfunctional requirement, “how fast does the website load?” Failing to meet non-functional requirements can result in systems that fail to satisfy user needs. Figure 3 : Non Functional b. Types of Non-functional Requirement Below are the main types of non functional requirements: Usability requirement
A website should be capable enough to handle 20 million users with affecting its performance The software should be portable. So moving from one OS to other OS does not create any problem. Privacy of information, the export of restricted technologies, intellectual property rights, etc. should be audited. d. Advantages of Non-Functional Requirement Benefits/pros of Non-functional testing are: The nonfunctional requirements ensure the software system follow legal and compliance rules. They ensure the reliability, availability, and performance of the software system They ensure good user experience and ease of operating the software. They help in formulating security policy of the software system. e. Disadvantages of Non-functional requirement Cons/drawbacks of Non-function requirement are: None functional requirement may affect the various high-level software subsystem They require special consideration during the software architecture/high-level design phase which increases costs. Their implementation does not usually map to the specific software sub-system, It is tough to modify non-functional once you pass the architecture phase.
3. Discuss the relationships between the FRs and NFRs These requirements should be fulfilled in order to define a system or component in terms of functional requirements. The user defines the functional requirement, which is necessary and states "What should the software system do?" Functional requirements are specified at the component level and documented in use cases, which aid in the verification of software functionalities and the testing of features such as system, end-to-end, and API, among others. Normally, defining the requirements for a job is pretty simple.
Utilizing non-functional needs won't always be necessary to satisfy the aforementioned requirements. Non-functional requirements answer the question, "How should the software system meet the functional requirements?" and establish the quality attribute of the software system. Technical professionals like architects, software engineers, etc. are required to specify non-functional requirements, although they are not required. It is thought of as a quality trait that can be applied to the complete system and aids in evaluating non- functionalities including performance, usability, security, and other... The definition of non-functional requirements is frequently more challenging.
4. The technical requirements The requirements gathering and requirements evaluation subphases make up the analysis phase. Software requirements must be gathered for software development projects. Utilize strategies to carry out precise actions to satisfy unique, well-articulated, considerate, direct, and precise criteria. The requirements must be documented, followed by a review, revision, and improvement process by the partners. Here are a few typical methods:
