ASSIGNMENT 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life Cycle Submission date 04/20/2023 Date Received 1stsubmission Re-submission Date Date Received 2ndsubmission Student Name Nguyen Dang Hoang Khang Student ID BC00007 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 unde making a false declaration is a form of malpractice. Student’s signature Khang Grading grid P5 P6 P7 M3 M4 M5 M6 D1 D2 1 Summative Feedback: ResubmissionFeedback: Grade: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date: 2 Table of contents INTRODUCTION. 7 UNDERTAKE A SOFTWARE INVESTIGATION TO MEET A BUSINESS NEED (P5).
Identify the stakeholders, their roles and interests in the case study. Distinguish functional and non-functional requirements. The relationship between functional and non-functional requirements. Discuss the technique(s) you would use to obtain the requirements.
14 USE APPROPRIATE SOFTWARE ANALYSIS TOOLS/TECHNIQUES TO CARRY OUT A SOFTWARE INVESTIGATION AND CREATE SUPPORTING DOCUMENTATION (P6). Use case diagram. Identify actors and use cases for each actor. Draw a use case diagram.
Use case description. Data Flow Diagram. Draw a Data Flow Diagram. Entity Relation Diagram.
Relationships between entities. 26 EXPLAIN HOW USER AND SOFTWARE REQUIREMENTS HAVE BEEN ADDRESSED (P7). Website interface design. Address which solution stack could be suitable to implement the project.
41 Discuss how you would trace these requirements throughout the project (M3). 43 Discuss two approaches to improving software quality (M4). Discuss two software quality attributes that are applicable to the project. Discuss two quality assurance techniques that can help improve the software quality in the project.
45 Suggest two software behavioural specification methods and illustrate their use with an example (M5). 46 Differentiate between a finite state machine (FSM) and an extended-FSM, providing an application for both. 50 4 List of Figures Figure 1: Usecase level 1. 16 Figure 2: Book Management.
17 Figure 3: Category Management. 17 Figure 4: Orders Management. 17 Figure 5: Customer Management. 18 Figure 6: Customer Account.
18 Figure 7: Employee Account. 18 Figure 8: Order detail Management. 20 Figure 12: Data Flow Diagram level 0. 23 Figure 13: Context Diagram.
28 Figure 16: Create Account. 30 Figure 20: Login Admin. 30 Figure 21: Add book and list of book. 33 Figure 25: Edit Profile.
34 Figure 26 : Your Profile. 35 Figure 28 :Login Admin. 35 Figure 29 : Home Admin. 36 Figure 30 : Add Book.
36 Figure 31 : List Book. 37 Figure 32 : Add Employee. 37 Figure 33: List Book. 38 Figure 34 : Add Customer.
38 Figure 35 : List Customer. 39 Figure 36 : List Order. 39 Figure 37 : Order detail. 40 Figure 38 :List Feedback.
40 Figure 39: LAMP stack. 42 5 List of Table Table 1: Functional and Non Functional Requirements. 14 Table 3: Actors and use cases for each actor. 16 Table 4: Function table of use case.
21 Table 5: Function Login. 21 Table 6: Function Login. 22 Table 7: Function Register. 22 Table 8: Function Register.
22 Table 9: Function Logout. 23 Table 10: Function Logout. 23 Table 11: Entity Description. 26 6 INTRODUCTION In this report, I will teach the knowledge collected by technology, including 5 technologies: interviews, questionnaires, JAD, Document analysis and observation.
Among them, I give definitions and related factors. I can use it too The application of interview technology has paved the way for project development. I also created The system designed charts, such as: application diagram, activity diagram, data flowchart and entity Relational card. I created a relationship database that contains all information from the physical relationship diagram.
The data required by the system. In addition, I also created a report for the website function, including The main functions of the system. The software of the system reaction is below. 7 UNDERTAKE A SOFTWARE INVESTIGATION TO MEET A BUSINESS NEED (P5) I.
Identify the stakeholders, their roles and interests in the case study A stakeholder is any individual, group or party that has an interest in an organization and the results of its actions. for example in the tune source system here the stakeholders are customers, employees administrators, project investors, government, and the community. The stakeholders: Phill Lewis, Kevin Hart and Ariana Grande Administrator Administrator stakeholders are the owners of an organization. They provide capital or equity to the project and have a say in how things run.
There can be multiple owners and each administrator will have equity in the project. Project Sponsor: David Beckham Project Sponsor can include owners but they can also be outside vendors who typically have a right to accurate and timely information such as regular financial statements. Sponsor may also have the right to approve or reject major decisions like mergers and acquisitions. System User The System User represents the end-users who will use the system or product being developed in the project.
Their role is to provide input on functional requirements, user experience (UX), and usability considerations. Their interests may include having a system or product that meets their needs, is user-friendly, and provides a positive experience. Customers Customers are the entities or individuals who will use or benefit from the project outcome. Their role is to provide input on requirements, provide feedback during project execution, and accept the final deliverables.
Their interests may include receiving a high-quality product or service that meets their needs, is delivered on time, and is within budget. It's important to note that stakeholders' roles and interests may evolve throughout the project lifecycle, and effective stakeholder management is crucial for project success. Understanding the roles and interests of stakeholders helps in identifying and managing their expectations, addressing their concerns, and ensuring their active participation and support throughout the project. Definition 8 Represents a need that an Information System should fulfill.
Conditions can be functional( what the software or element should do, a functionality),non-functional( how the system will do, that is, constraints or rates) and environmental( assessed constraints similar as legal restrictions or norms). This bracket can be seen from the stoner point of view( accessible for stakeholders) or from the system point of view( on a specialized and more detailed position). Distinguish functional and non-functional requirements Requirements analysis is very critical process that enables the success of a system or software project to be assessed. Requirements are generally split into two types: Functional and Non-functional requirements.
Functional Conditions These are the conditions that the end stoner specifically demands as introductory installations that the system should offer. All these functionalities need to be inescapably incorporated into the system as a part of the contract. These are represented or stated in the form of input to be given to the system, the operation performed and the affair anticipated. They're principally the conditions stated by the stoner which one can see directly in the final product, unlike the non-functional conditions.
Non-functional conditions These are principally the quality constraints that the system must satisfy according to the design contract. The precedence or extent to which these factors are enforced varies from one design to other. They're also called non-behavioral conditions. They basically deal with issues like: Portability Security Maintainability Reliability Scalability Performance Reusability Flexibility Following are the differences between Functional and Non Functional Requirements Functional Requirements Non Functional Requirements A functional requirement defines a system or its A non-functional requirement defines the component.
quality attribute of a software system. It specifies “What should the software system It places constraints on “How should the do?” software system fulfill the functional requirements?” 9 Functional requirement is specified by User. Non-functional requirement is specified by technical peoples e. Architect, Technical leaders and software developers.
It is mandatory. It is not mandatory. It is captured in use case. It is captured as a quality attribute.
Defined at a component level. Applied to a system as a whole. Helps you verify the functionality of the Helps you to verify the performance of the software. Functional Testing like System, Integration, End Non-Functional Testing like Performance, to End, API testing, etc are done.
Stress, Usability, Security testing, etc are done. Usually easy to define. Usually more difficult to define. Example Example 1) Authentication of user whenever he/she logs 1) Emails should be sent with a latency of no into the system.
greater than 12 hours from such an activity. 2) System shutdown in case of a cyber attack. 2) The processing of each request should be 3) A Verification email is sent to user whenever done within 10 seconds he/she registers for the first time on some 3) The site should load in 3 seconds when the software system. number of simultaneous users are > 10000 Table 1: Functional and Non Functional Requirements 3.
The relationship between functional and non-functional requirements Functional Conditions and non-functional conditions are both important in the development of a successful software system. Functional conditions define the specific features and functionality that the software system must give to meet the stoner's requirements. Non-functional conditions, on the other hand, describe the performance, usability, security, and other quality characteristics that the system must parade. Functional conditions concentrate on what the software system should do, while non- functional conditions concentrate on how it should do it.
In other words, functional conditions are concerned with the" what" of the system, while non-functional conditions are concerned with the" how." The relationship between functional and non-functional conditions is that they're both necessary in order to produce a successful software system. The functional conditions define what the system is supposed to do, while the non-functional conditions define how well it should do it. For illustration, a functional demand might be that a system must allow druggies to produce and save documents, while anon-functional demand might be that the system must be suitable to handle a large number of druggies contemporaneously without decelerating down. while functional conditions are necessary to describe the functionality of the system,non-functional conditions are necessary to insure that the system meets the necessary quality norms and performs effectively under different conditions.
Both types of conditions are important and should be considered in the development of any software system. Discuss the technique(s) you would use to obtain the requirements Justification for the technique(s): Decades of resource-related project planning issues decades ago, although it was rarely used in this issue. The reason is a simple and fast technology that will create a new timetable when using the timetable, as long as the original timetable -usually shorter. These results prompted us to summarize this technology to further study it.
In this article, the differences and general forms of reasoning technology are proposed, which can obtain a survey of the relationship between the timetable. The results obtained show that the proposed summary is worth it. Several computer tests were performed to determine the impact of general concepts on algorithm efficiency. We use collective requirements, observation, and questionnaire/survey.
Observational Method: The term Observational research is used to refer to a number of different types of non- experimental research in which behavior is systematically observed and recorded. Naturalistic Observation: Natural observation is a method of observation, including observing human behavior in the field of customers and investors. For example, observe customers and behaviors using the melody source. Your research will invalidate the research.
Therefore, the observation value of camouflage may be low, so it may have a higher value because people do not know that their behavior is observed and recorded. However, we now know that people are often accustomed to observing. Over time, they start to act naturally in front of researchers.
