Download Assignment 2-1631-PASS and more Study Guides, Projects, Research Information Technology in PDF only on Docsity!
ASSIGNMENT 02 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Truong Duy Minh Student ID GCD Class GED1102 Assessor name Pham Thanh Son 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: Internal Verifier’s Comments: Signature & Date:
- A. Investigate software to fulfill a business requirement (P5)..................................................................................................................................................................
- I. Identify the stakeholders, their roles and interests in the case study................................................................................................................................................
- Introduction of requirement definition of the project..................................................................................................................................................................
- The relationships between the FRs and NFRs...............................................................................................................................................................................
- Skateholders and their roles in Tune Source project....................................................................................................................................................................
- Present the requirement definition used in the Tune Source Project.........................................................................................................................................
- II. Discuss the technique(s) used to obtain the requirements............................................................................................................................................................
- Describe 3 requirement gathering techniques used in the project: Interviews, Document Analysis, Observation....................................................................
- Technique that I’d taken to obtain the requirements.................................................................................................................................................................
- B. Conduct a software investigation using the proper tools and procedures for software analysis and produce documentation to support customers findings (P6).
- I. Requirements Modelling:................................................................................................................................................................................................................
- II. Apply to Tune Source project..........................................................................................................................................................................................................
- C. Explain how user and software requirements have been addressed (P7)..........................................................................................................................................
- II. Wireframe of TS project..................................................................................................................................................................................................................
- III. Explain the architecture is suitable for the project........................................................................................................................................................................
- IV. Address which technical solution stack could be suitable to implement the project with clear explanations..............................................................................
- V. CONCLUSION..................................................................................................................................................................................................................................
- References..............................................................................................................................................................................................................................................
- Figure 1: requirement definition..............................................................................................................................................................................................................
- Figure 2: Functional requirement.............................................................................................................................................................................................................
- Figure 3: Non-Functional requirements....................................................................................................................................................................................................
- Figure 4: Skateholder..............................................................................................................................................................................................................................
- Figure 5: Major Use case.........................................................................................................................................................................................................................
- Figure 6: Buy Use case............................................................................................................................................................................................................................
- Figure 7: Search Use case.......................................................................................................................................................................................................................
- Figure 8: Register Use case.....................................................................................................................................................................................................................
- Figure 9:ERD of project...........................................................................................................................................................................................................................
- Figure 10: DFD of project........................................................................................................................................................................................................................
- Figure 11: Context diagram of project....................................................................................................................................................................................................
- Figure 12: Main screen...........................................................................................................................................................................................................................
- Figure 13: Featured product...................................................................................................................................................................................................................
- Figure 14: Main screen...........................................................................................................................................................................................................................
- Figure 15: Login screen...........................................................................................................................................................................................................................
- Figure 16: Cart screen.............................................................................................................................................................................................................................
Figure 17: Shipping screen...................................................................................................................................................................................................................... 31 A. Investigate software to fulfill a business requirement (P5)
I. Identify the stakeholders, their roles and interests in the case study
1. Introduction of requirement definition of the project
Product development and process improvement make an effort to satisfy a certain physical or functional demand through a particular design, product, or technique. In formal engineering design procedures like systems engineering, software engineering, or enterprise engineering, it is frequently used. It is a broad concept that can relate to any feature, capability, quality, or attribute of a system that is required (or occasionally desired) in order for a client, business, internal user, or other stakeholders to find it worthwhile and practical.
The functional Requirements of a system should include these following things: Information about the procedures performed on each screen The system must have data processing logic inserted into it, along with descriptions of system outputs like reports. full disclosure of the workflows that the system performs It should expressly state who will be permitted to add, edit, and delete data in the system. The functional document must provide information on how the system will satisfy applicable regulatory and compliance requirements. Advantages of FRs It lets you check to see if the app offers each of the features stated in the functional requirements for this application. You can specify how a system or one of its subsystems functions using a functional requirements document. The functional requirements and requirements analysis collaborate to identify the unfulfilled demands. They assist in defining the desired system behavior and functionality in a clear and concise manner. Finding problems during the functional requirements collection stage is much easier. Support for user behaviors, tasks, or objectives.
2.2. Non-Functional Requirements (NFRs)
Definition Non-functional requirements or NFRs are a set of specifications that describe the system’s operation capabilities and constraints and attempt to improve its functionality. These are basically the requirements that outline how well it will operate including things like speed, security, reliability, data integrity, etc. (htt56)
Figure 3 : Non-Functional requirements Advantages of NFRs: They ensure that all applicable laws and regulations are complied with by the software application. They detail the software’s quality characteristics. They guarantee that the software system is dependable, accessible, effective, and scalable. They support the creation of the security policy for the software system. They guarantee a positive user experience, make it simple to use the program, and keep costs down.
2.3. Difference between FRs and NFRs:
Parameters Functional Requirement Non-Functional Requirement What it is Verb Attributes Requirement It is mandatory It is non-mandatory Capturing type It is captured in use case. It is captured as a quality attribute. End result Product feature Product properties Capturing Easy to capture Hard to capture
Figure 4 : Skateholder Skateholders role and interest/work in Tune Source project SKATEHOLDER ROLE INTEREST/WORK Truong Duy Minh Manager Project managers take the lead in organizing, carrying out, overseeing, and concluding projects. Have a look at the work duties, credentials that apply, compensation that may be expected, and advice on how to get a position for a project manager. Truong Minh An Customers Use Tune Source website to play music or buy the company product. Thien Minh Cuong Sponsor Manage the budget and spending of the project. Hao Duy Cong Head coder Become familiar with Internet technology as it has collaborated with the ISP to keep the site up.
4. Present the requirement definition used in the Tune Source Project
FUNCTIONAL REQUIREMENT DESCRIPTION
Download Allow customers to download the music they want.
Listen Allow consumers to play music online (if have not downloaded) or offline (if have downloaded). Search Allow customers to search for songs by entering song- related keywords such as song title, artist name or album name. Login Enable users to log in to the Tune Source system and use the available accounts to access all other services. Security Enable users to log in to the Tune Source system and use the available accounts to access all other services. Purchase Allow customers to buy song from the website. NON-FUNCTIONAL REQUIREMENT
DESCRIPTION
Security A firewall would be use for database security to prevent unauthorized access. Reliability Technology that is highly reliable functions with the same or similar efficacy after extensive use Capacity Ensure that the system has the capacity to handle high visitor volume; users can customize and save settings according to their preferences.
II. Discuss the technique(s) used to obtain the requirements
1. Describe 3 requirement gathering techniques used in the project: Interviews, Document Analysis, Observation
1.1 Interviews
Description The most common method for gathering requirements is this one. By the use of interviewing methodologies, strong relationships between business analysts and stakeholders should be developed. With this approach, stakeholders are interviewed in order to acquire information. One-on-one interviews are the method that is most frequently used. Advantages:
Understanding other people's actions, tasks, tools, and events is the main purpose of the observation session. The observation plan makes ensuring that everyone involved understands the session's goal, that they concur on the anticipated results, and that the session meets their expectations. The participants must be informed that their performance will not be graded. The observer should keep track of everyone's movements and how long it takes others to finish an activity throughout the session so that they can be imitated. The BA will review the findings and follow up with the participants after the session. It is possible to observe actively or passively. Advantages: The observer will gain a useful understanding of the task. It is simple to identify areas for improvement. Disadvantages: Participants might become agitated. Participants' working methods could change throughout the observation, making it difficult for the observer to get a clear picture.
2. Technique that I’d taken to obtain the requirements
Techniques YES NO Interviews ✔ Document analysis ✔ Observation ✔ An interview is utilized in this Tune Source project to gather needs because it is easier to gather information from a large audience, it requires less time for consumers to respond, and it yields more accurate information than other methods. Team projects can obtain essential knowledge and data using the interviews approach. Also, the team project needs remarkable information if it is to produce a great study report. Furthermore, a well-designed survey or research would be necessary if the project calls for high-quality data. The most well-liked and convenient method for collecting data for research is through interviewing. As a result, a group effort might develop a survey, distribute it to many of people, and then evaluate and review the replies.
B. Conduct a software investigation using the proper tools and procedures for software analysis and produce documentation to support customers findings (P6). I. Requirements Modelling: Definition: Requirements modeling is a technique used in software development projects to collaboratively and collaboratively change requirements and solutions. You may ensure that your team meets the expectations of the stakeholders by using this approach of cross-functional and self-organizing teams. Stages of Requirements Modelling: Scenario-based modelling Data modelling Flow-oriented modelling Class-based modelling Behavioral modelling Types of Requirements Modelling: Entity Relationship (E-R) Model: Unified Modelling Language (UML): II. Apply to Tune Source project II.1. Use case of TS project
Figure 6 : Buy Use case Figure 7 : Search Use case
USE CASE NAME Register use case DESCRIPTION Customer register an account to use the website ACTOR(S) Customer, Admin PRIORITY Must have TRIGGER Customer register an account PRE-CONDITION Customer information must not be duplicated Customer’s device must have wi-fi or internet connection when enroll POST-CONDITION Customer register successful The system recognizes the successful register operation. BASIC FLOW Customer enroll an account The system check for data validation Customer enter information and email System checking for email successful System successfully authenticates the register information and allow the user to login EXCEPTION FLOW The system validates the credentials failed and displays a message. The user chooses to cancel the login. Use Case stops.
USE CASE NAME Search use case DESCRIPTION Customer searching for a song on the website ACTOR(S) Customer, Admin PRIORITY Must have TRIGGER Customer search for a song PRE-CONDITION Customer account must be available. Customer’s device must have wi-fi or internet connection when searching. POST-CONDITION Customer search successful. The system recognizes the successful searching operation. BASIC FLOW Customer found the song they want. System switches to the song that customer search. System show all the information of the song. EXCEPTION FLOW Customer enter wrong keyword or any information about the song. The user chooses to cancel the searching. Use Case stops. II.2. ERD of TS project
