Download Assignment 1 1631 (P) and more Assignments Information Technology in PDF only on Docsity!
ASSIGNMENT 0 2 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 0 9: Software Development Life Cycle Submission date 17 - 6 - 2023 Date Received 1st submission 17 - 6 - 2023 Re-submission Date Date Received 2nd submission Student Name Nguyễn Văn Quang Student ID GCH Class GCH1107 Assessor name Nguyễn Thế Lâm Tùng 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. Undertake a software investigation to meet a business need (P5)
- I. Introduction purpose of this section
- II. Review the requirement definition of the project Clearly indicate which stakeholder(s) provide what requirements
- III. Identify Functional Requirements (FRs) and Non Functional Requirements (NFRs) - 3.1 Functional Requirements - 3.2 Non functional Requirements
- IV. Discuss the relationships between the FRs and NFRs
- V. Identify the stakeholders, their roles and interests in the case study
- VI. Discuss the technique(s) you would use to obtain the requirements.
- V. The Interview Technique in the Tune Source project
- VII. Discuss how you would trace these requirements throughout the project by using Requirement Traceability matrix.
- B. Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation (P6)
- I. Use Case Diagram for the whole system
- II. Use Case specification for 2 Use cases
- III. Context Diagram for the whole system
- IV. Data Flow Diagram – Level 0 for the whole system
- V. ERD for the whole system
- VI. Pseudocode for one module of the program
- C. Explain how user and software requirements have been addressed(P7)
- I. Mock-up and wireframe
- II. Explain which architecture (client – server, n-tier, microservices) is suitable for the project with clear illustrations
- III. Explanation why the chosen three-tiered is suitable for this project
- IV. Address which technical solution stack could be suitable to implement the project with clear explanations
- D. References
- Figure 1: Functional Requirements (FRs)
- Figure 2:Non functional Requirements
- Figure 3:FRs vs NFRs
- Figure 4:Use Case Diagram for the whole system
- Figure 5:Context Diagram for the whole system.......................................................................................................................................................................................
- Figure 6:Data Flow Diagram – Level 0 for the whole system
- Figure 7: Data Flow Diagram login
- Figure 8: : Data Flow Diagram search and listen music
- Figure 9: Data Flow Diagram search and download music
- Figure 10:ERD for the whole system
- Figure 11:The main menu, customer can sign up, login............................................................................................................................................................................
- Figure 12: Login form
- Figure 13:Register form
- Figure 14: Main page.................................................................................................................................................................................................................................
- Figure 15:Information of music.................................................................................................................................................................................................................
Establish a customer subscription account permitting unlimited downloads for a monthly fee. Purchase music download gift cards. Stakeholders: John Margolis, Megan Taylor, and Phil Cooper (Entrepreneurs): They would benefit from the increased sales and revenue generated through the sale of digital music downloads. They are likely proponents of all the mentioned requirements as they aim to expand their business and leverage their music archive. Carly Edwards (Assistant Vice President, Marketing): Carly is the project sponsor and represents the marketing department. She views the implementation of digital music downloads as a strategic system to increase sales and revenue. Carly would likely support all the mentioned requirements to achieve the desired business objectives. Existing Customers: The ability to search, listen, and purchase digital music downloads would cater to the requests of the loyal customers. They would benefit from the convenience of accessing rare and hard-to-find music through the Tune Source platform. These customers are likely proponents of the requirements mentioned.
III. Identify Functional Requirements (FRs) and Non Functional Requirements (NFRs) 3.1 Functional Requirements Figure 1 : Functional Requirements (FRs) The service that the software must provide is described in a functional requirement (FR). A software system or one of its components is described. The software system's inputs, actions, and outputs are all together referred to as a function. It may be a calculation, data manipulation, business procedure, user interaction, or any other particular functionality that identifies the likely use of a system. Functional Specification is another name for functional requirements in software engineering. (Martin, 2023). Functional Requirements (FRs) for project
3.2 Non functional Requirements Figure 2 :Non functional Requirements Non-Functional Requirement (NFR) describes a software system's quality aspect. They assess the software system according to non-functional criteria such as responsiveness, usability, security, portability, and other criteria that are essential to the software system's success. The nonfunctional requirement "how quickly does the website load?" is an example. Systems that don't satisfy user needs can result from not meeting non-functional requirements (Martin, 2023b). Non-Functional Requirements (NFRs): Performance: The system should be capable of handling a high volume of concurrent users without significant performance degradation. Response times for search queries, sample playback, and purchase transactions should be fast and efficient. Usability: The user interface of the website and in-store kiosks should be user-friendly, intuitive, and visually appealing. Users should be able to navigate the system easily, locate desired music, and complete transactions with minimal effort.
Security: The system should implement robust security measures to protect customer information, payment details, and digital content from unauthorized access or breaches. It should incorporate encryption protocols, secure authentication mechanisms, and compliance with industry security standards. Reliability: The system should be highly reliable, with minimal downtime or service disruptions. It should be able to recover from failures or errors quickly and ensure the continuity of essential functions. Compatibility: The system should be compatible with various devices and platforms, including desktops, laptops, smartphones, and tablets. It should support different operating systems and web browsers to provide seamless access and functionality to a wide range of users. Scalability: The system should be designed to scale effectively to accommodate increasing user demand and growing digital music archives. It should be able to handle a larger number of users, concurrent transactions, and a larger collection of music files without compromising performance. Integration: The system should integrate smoothly with existing systems such as inventory management, customer databases, and payment gateways. It should facilitate the exchange of data and ensure accurate tracking of purchases, subscriptions, and customer information. Accessibility: The system should adhere to accessibility standards and guidelines, ensuring that users with disabilities can access and use the service effectively. It should provide support for assistive technologies and offer alternative means of interaction for users with visual or motor impairments. Legal and Copyright Compliance: The system should comply with copyright laws and licensing agreements when offering digital music downloads. It should ensure that the music content is legally obtained and distributed to customers, preventing any infringement of intellectual property rights. Maintenance and Support: The system should be designed for easy maintenance, with modular components and clear documentation. Technical support should be available to address any user inquiries, resolve.
Performance (NFR) and Search for music in the digital music archive (FR): The performance of the system, such as response time and search result retrieval, directly affects the user experience in searching for music. The system should be optimized to deliver fast and accurate search results, meeting users' expectations and providing a satisfactory performance. Usability (NFR) and Listen to music samples (FR): The usability of the system, including the ease of use and intuitive interface, plays a crucial role in enabling users to listen to music samples. The system should provide a seamless and user-friendly experience for users to preview music samples effortlessly, facilitating their decision-making process. Security (NFR) and Purchase individual downloads at a fixed fee per download (FR): Security measures need to be implemented to protect customers' payment details and digital content during the purchase process. The system should incorporate secure payment gateways, encryption protocols, and authentication mechanisms to ensure secure transactions and prevent unauthorized access. Reliability (NFR) and Establish a customer subscription account permitting unlimited downloads for a monthly fee (FR): The system's reliability is vital for managing customer subscription accounts effectively. Users should have uninterrupted access to their subscription benefits, and the system should ensure the availability and reliability of the subscription service, minimizing downtime and disruptions. Compatibility (NFR) and Purchase music download gift cards (FR): The system should be compatible with different devices and platforms to enable the purchase and redemption of music download gift cards seamlessly. Compatibility ensures that users can access and utilize the gift card feature across various devices, enhancing user convenience and satisfaction. Scalability (NFR) and Search for music in the digital music archive (FR): As the digital music archive grows, the system should be scalable to handle the increasing volume of music tracks and accommodate a larger user base. Scalability ensures that the search functionality remains efficient and responsive, even with a vast and expanding collection of music.
V. Identify the stakeholders, their roles and interests in the case study Stakeholder Role Interests Requirements John Margolis Founder/Owner Expanding business, increasing sales
- Ability to offer digital music downloads Megan Taylor Founder/Owner Expanding business, increasing sales
- Ability to offer digital music downloads Phil cooper Founder/Owner Expanding business, increasing sales
- Ability to offer digital music downloads Carly Edwards Project Sponsor/ Assistant VP, Marking boosting sales, keeping clients, and remaining competitive
- Ability to offer digital music downloads IT Department IT Department Smooth system setup and website maintenance
- Including the ability to download songs digitally Existing Customers Current customers loyalty, accessibility to rare music - Search the digital music library for music
- Play some music samples.
- Buy individual downloads at a set price
- Create an unlimited downloads customer membership account.
- Buy gift cards for music downloads New customers Potential customers Access to rate music, convenience, unique offerings
- Find songs by searching the digital music archive
- Hear music samples
- Buy individual files for a set price
IT department: The IT department is responsible for maintaining the website and working with the internet service provider. They possess expertise in internet technology and their interests lie in utilizing their skills and experience. Their requirements involve integrating the digital music download functionality into the website and ensuring the smooth operation of the system. The requirement definition for the Tune Source (TS) project, based on the provided table, includes the following: Search for music in our digital music archive: Customers, both existing and new, should be able to search for music within the digital music archive of Tune Source. Listen to music samples: Customers, both existing and new, should have the capability to listen to samples of music tracks before making a purchase. Purchase individual downloads at a fixed fee per download: Customers, both existing and new, should be able to purchase individual music downloads at a predetermined fixed fee for each download. Establish a customer subscription account permitting unlimited downloads for a monthly fee: Customers, both existing and new, should have the option to create a customer subscription account that allows them to download music tracks without any limits, in exchange for a monthly fee. Purchase music download gift cards: Customers, both existing and new, should have the ability to purchase gift cards specifically for music downloads. These requirements aim to enhance the customer experience, provide flexibility in purchasing options, and tap into new revenue streams for Tune Source. Existing and new customers: Both existing and new customers have interests in being able to search for music, listen to music samples, purchase individual downloads at fixed fees, establish customer subscription accounts for unlimited downloads, and buy music download gift cards. These requirements cater to their desire for convenience, access to rare music, and easy purchasing options.
VI. Discuss the technique(s) you would use to obtain the requirements. A survey is the initial stage of the system development process, which gathers requirements. The two types of requirements that must be met are functional requirements and non-functional requirements. The user typically specifies the functional requirements, which are evident in the finished product. The tasks that a system must accomplish are typically outlined in the functional requirements. In terms of non-functional requirements, they are essentially the criteria of quality outlined in the project contract that the system must meet. They center mostly on realism, effectiveness, security, and adaptability. 6.1 The Joint Application Development (JAD) process in the Tune Source project Through a series of interactive workshops called JAD sessions, the client or end user is involved in the design and development of an application using the JAD process. JAD was created by IBM employees Chuck Morris and Tony Crawford in the late 1970s, and it was first taught through workshops in
- Because the client is involved at every stage of the development process, the JAD technique is said to result in quicker development timelines and higher client satisfaction than the more conventional practice. In contrast, the traditional method of systems development entails the developer researching the needs of the system and creating an application with client input coming from a series of interviews (Contributor, 2017). The JAD process is a collaborative approach that involves key stakeholders and subject matter experts in requirement elicitation and analysis. It promotes active participation, fosters communication, and ensures that the requirements are well-understood and agreed upon by all involved parties. Here's how the JAD process can be utilized in the Tune Source project: Identify the JAD participants: Carly Edwards (Project Sponsor) John Margolis, Megan Taylor, and Phil Cooper (Company Entrepreneurs) Representatives from the marketing department, IT department, and customer service Schedule and facilitate JAD sessions: Plan and schedule multiple JAD sessions with the identified participants. Define the objectives and agenda for each session, focusing on specific aspects of the system requirements. Prepare necessary materials, such as the system request, business requirements, and any existing documentation or prototypes. Conduct JAD sessions: Facilitate the sessions, ensuring active participation from all attendees. Discuss and analyze the business needs and requirements outlined in the system request.
Decide on the interview's date, time, and location. Provide the interviewers with the list of prepared questions in case they need extra time to do their study. Take notes and record the interview using a variety of recording methods. 6.3 Observation in the Tune Source project Data may be gathered by observation by keeping an eye on behavior and events, or by noting physical qualities in their natural context. People are more inclined to act impulsively if they are unaware that they are being watched, which is a benefit of covert observation. Instead of just interacting with customers and stakeholders, the Tuna Source project should employ the observation approach to better understand them by seeing their actions and behaviors. The Tune Source analyst can benefit from user observations that show the user's real engagements with the system. The analyst may consider how the user's surroundings and interactions with the system affect them if the goal is to improve a task. Monitoring users can help informing decisions in situations when stakeholders struggle to properly express their roles and expectations. Observational categories in the Tune Source project: Both passive observation and active observation are forms of observation that may be used to gather information for the Tune Source project.
- Active observation: It's possible that users and other stakeholders won't perform as they would under direct observation, hiding their true selves from us instead. However, if the analyst participates in the process in some way, it may result in successful progress management. - Passive Observations: Passive observers would remain out of the way, obstruct the action, and refrain from becoming involved. The analyst will only observe and record rather than interrogate the development team or end users. Finding out what clients really want might be useful. VII. Discuss how you would trace these requirements throughout the project by using Requirement Traceability matrix. Requirement ID Business Requirement Functional Requirement Design Artifact Test Case ID(s0 Implementation Status R1 Search for music in our digital music archive Provide a search functionality for digital music archive UI design TC1 Implemented R2 Listen to music samples Enable music sample playback UI design TC2 Implemented
R3 Purchase individual downloads at a fixed fee Implement a payment system for individual downloads UI design, backend TC3 Implemented R4 Establish customer subscription account Create user accounts for customer subscriptions Backend design TC4 Implemented R5 Purchase music Enable purchase of music download gift cards UI design, backend TC5 Implemented In the above matrix, each requirement is assigned a unique requirement ID for easy reference. The business requirements from the scenario are linked to their corresponding functional requirements, design artifacts, test case IDs, and implementation status. For example, Requirement R1 states the business need to search for music in the digital music archive. The corresponding functional requirement is to provide a search functionality for the archive. This requirement is reflected in the UI design artifact, and its implementation status indicates that it has been implemented. Test case TC1 is associated with this requirement to validate the search functionality. Similarly, the other requirements are traced through the project lifecycle. This traceability matrix helps in ensuring that all the requirements are accounted for during the design, development, and testing phases. It also aids in tracking the implementation status of each requirement. By utilizing the requirement traceability matrix, project stakeholders can easily track the progress of requirements and ensure that they are fulfilled. It also facilitates effective communication and collaboration between the business, development, and testing teams, leading to a successful project delivery. B. Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation (P6)
