Download Assignment 2 - Software Development Life Cycle (1631) and more Study Guides, Projects, Research 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 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Phan Nhat Linh Student ID GCD Class GCD0905 Assessor name Phyo Min Tun 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 Linh 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:
Table of Contents
I/ Undertake a software investigation to meet a business need (P5)
1. Identify the stakeholders, their roles and interests in the case study.
1.1 Review the requirement definition of the project. The goal is to create a website for Tune Source in order to sell music to customers. The use of this website will eventually replace traditional stores. Furthermore, according to Tune Source's economic analysis, product sales via the internet channel are the principal source of revenue. As a result, creating a website is essential for expanding the business and producing revenue. The website is now being built on a PC-based platform with a basic application, but Tune Source will be utilized in the future. The Progressive Web App (PWA). Because of this technology, users may use the website as an application on their phone without having to install anything. According to Tune Source's circumstance, functional needs and website design must match the following standards. ➢ Allows people to sign up for an account. ➢ Allow users to log in using their personal account. ➢ Customers can obtain a membership to listen to and download digital music as well as a gift card. ➢ The Tune Source website also sells CDs online. ➢ Music news, events, and singers ➢ Ranking the most popular songs on a regular basis. 1.2 Stakeholder Role in the Tune Source project A stakeholder's primary job is to contribute their knowledge and insight to the Tune Source project in order to aid a firm in accomplishing its strategic objectives. They may be able to provide materials and resources as well. Their support is important to a project's success; if they are unhappy with the results, the Tune Source project is usually considered a failure, even if all objectives were met. The project manager is responsible for keeping stakeholders pleased by proactively managing their needs: through direct and timely interactions, as
well as an understanding of their expectations and timescale for the Tune Source project. This sort of leadership instills trust and confidence in project stakeholders while also confirming their buy-in or good participation. Figure 1 : Stakeholder Role ➢ Customer: As a customer of "Tune Source's" musical production. They will be involved in the project planning process from start to completion. They will be in responsibility of explaining the project's needs and functionality, as well as ensuring that the requirements they lay forth are met efficiently at the project's completion. It is also the customer's responsibility to define his or her requirements during "Tune Source" contacts with customers. collaboration. ➢ Users: These are the people who will interact with the music-selling website as part of the "Tune Source" project. They will be the ones who search for discs or download songs they like, listen to music they like, and pay when they want to buy anything or download a song they like. To achieve client satisfaction, "Tune Source" should ensure that their platform is user-friendly (UX/UI).
➢ Users can create an account on the system. ➢ Users can access the system using their own accounts. ➢ Customers may use the system to register in order to listen to and download digital music and gift cards. ➢ Customers may buy CDs online using the method. ➢ The system broadcasts music and singer-related news and events. ➢ The method ranks the most popular songs throughout time. ➢ Customers may search for music using the technology. ➢ Customers can use the system to register and pay online. Information-oriented ➢ The system will display to customers the information that has been successfully registered for an account. ➢ The system will display to the client the invoice data once the CD has been purchased. 1.5 The Tune Source Project’s Non-Functional Requirements Non-functional requirements, rather than specific activities, include criteria for evaluating a system's performance. To put it another way, a non-functional necessity would dictate how a "Tune Source" digital music website system would work and what limits it would have. Non-functional criteria, when properly conceived and implemented, make the "Tune Source" system easier to use and improve performance. Nonfunctional requirements have an influence on the user experience since they affect the system's general behavior, features, and characteristics. As a result, Non-Functional Requirements focus on user expectations, which are product attributes. Here are some examples of non-functional needs that "Tune Source" can meet. Operation: Provide a mobile-friendly platform to make it easier for clients to listen to music. Performance ➢ The system's material must be constantly updated with new hot tunes. ➢ Page load, search, and download speeds must be perfect.
➢ Update new UI features on a regular basis to keep clients from becoming bored. Security Avoid server problems while making payments to third parties. Keep consumer information secure. Cultural and political prerequisites: No specific cultural or political requirements are anticipated. 1.6 The relationships between the FRS and NFRs. Figure 2 : The relationships between the FRS and NFRs FRs: In software engineering, a functional requirement describes a system or its component. Its actions and outputs. A computation, data manipulation, business procedure, user interaction, or any other function that decides what a system is likely to perform can be considered. defines the tasks that the software must do A function is made up of three parts: inputs, outputs, and parameters. Functional
When a person initially registers for a software system, he or she receives a verification email. Each request should be handled in under 10 seconds. When there are over 10,000 concurrent users, the site should load in 3 seconds.
2. The techniques that Tune Source would use to obtain the requirements
The analysis phase consists of the acts of gathering and assessing requirements. Following that, the criteria are classified as functional or non-functional. Processes, information, and relationships are examples of functional needs. These are the qualities that the client would want to see in the system, and they explain how the system interacts with its surroundings. A system's functional requirements usually define what it is expected to do. Non-functional demands are characteristics that do not meet operational or technological requirements. Non-functional qualities include encryption, security, storage, environment, disaster recovery, and business continuity, to name a few. "Tune Source" has provided three methods for correctly gathering requirements and selecting the appropriate technique: JAD (Joint Application Development), Interview, and Observation are all ways that might be used to guarantee that "Tune Source" is not making false claims.
2.1 Observation Technique Figure 3 : Observational Technique Professional observation and instruction, as well as working settings, are frequently used by developers to use and assess data. This approach is used to identify needs, growth opportunities, or a business method, to construct and assess the efficacy of a proposal, and to recommend and present the highest quality choices for producing a design. Furthermore, this approach is frequently used in conjunction with other techniques to validate the accuracy of the data being gathered. There are two methods to observation techniques that are fundamental: Active Method: When monitoring the way of working on an item, the investigator will question any concerns regarding data about the challenges required to construct the software project. Although this strategy disrupts the task or observer item's working flow, designers may quickly understand why hidden activities and procedures are included in a workflow. Passive Method: The approach by which the participants discreetly observe and retrieve is the manner they observe and obtain data on the work process of the observant's item. The benefit of this strategy is that it allows designers to examine how the piece of nature truly
Individual surveys, concentrated community gatherings, telephone and courier surveys are just a few of the interview techniques accessible today. Each strategy will have its own set of pros and limitations. ➢ Personal interviews: Personal interviews are a form of interviewing and interviewing people to meet and discuss personally. If the responder does not understand a question, the interviewer can modify it or explain it. This approach is more adaptable than others. Direct interviews are likely to yield more data from the client-replying questionnaire, since the interviewer may observe to gather additional information about the interviewer through observation (environmental work, attitude, behaviour, costumes). The capacity to interview, communicate, or negotiate will be put into practice, and the quality and amount of information acquired will be determined. ➢ Group Interview: In the focus group research approach, the interviewer will meet with a group of 5 to 10 people in a comfortable environment, which helps interviewees and interviewed people feel safe. Closer and closer to the ceiling. During the interview, the interviewer will prepare open-ended questions to allow clients to openly explore the difficulties mentioned. The interviewer might ask successive questions to acquire a better grasp of the client's stance on a topic. The goal of collective interview methods is to generate thoughts and concepts that may be examined and refined using surveys and data acquired. This strategy is also utilized to learn more about consumer behavior. However, the approach of direct interaction has significant cost drawbacks; the interviewer has a long history of guiding and offering various topics during the debate. ➢ Phone interviews and mail interviews: A phone interview is a form of topic analysis. With the assistance of modern equipment, the viability of this procedure is improved. Responses with high capability can be gathered. The benefit of telephone interviews is that they are quick and straightforward to conduct, regardless of location. The disadvantage of this method is that it is not ideal for sophisticated conversations with nature; changing object behavior is not noticed. 2.3 The joint Application Development (JAD) Approach JAD (Joint Application Development) is a software development process in which the customer and/or end-users are involved in the design and development of the system. This paradigm was presented by IBM's Dr. Chuck Morris and Dr. Tony Crawford in the late 1970s, and it was produced and put out by them. When compared to other core SDLC methodologies, the Joint Application Development strategy results in a faster evolution of system development and more client acceptability. JAD model phases used in the Tune Source project:
➢ Define Specific Tune Source Project Objectives: In conjunction with stakeholders, the facilitator produces all of the objectives and a list of items, which is then delivered to other developers and participants to grasp and review. This goal includes the width of this suggested system, its probable conclusion, technological needs, and so on. ➢ Session Preparation: The facilitator is solely responsible for this preparation, which includes gathering all essential information and disseminating it ahead of time to other participants. Research is carried out to have a deeper grasp of Tune Source's system requirements and to acquire all of the necessary information for development. ➢ Session Conduct: The facilitator is responsible for identifying and resolving any issues that need to be addressed in order for the system Tune Source to be error-free. The facilitator will participate in the conversation but will not be able to make any choices regarding the topic. ➢ Documentation: After Tune Source's product has been developed, the records and published papers are presented in a meeting so that stakeholders and consumers may accept it. The advantages of utilizing the JAD approach in the Tune Source project: ➢ Improved Delivery Time: When producing a product for Tune Source, the JAD process takes less time and is more efficient than other traditional models. ➢ Cost Savings: Tune Source will require less labor to create if the requirements and facts are well discussed with business executives and stakeholders. As a consequence, the overall development cost will be reduced. ➢ Better Understanding: Because the Tune Source system's whole need is analyzed by business executives, followed by a thorough selection of developers and team members who can professionally connect with one another, product development is often simpler to grasp. ➢ Improved Quality: Because all of the important decision-makers and stakeholders in the Tune Source project are involved in its development, there is less chance of error, and therefore the product quality improves and becomes more accurate.
Figure 5 : Use Case Diagram for the whole system
Customers will be divided into two groups: those who are using the system for the first time (new customers) and those who have been using it for a long time (long-term customers). New customers can only register, see playlists, search, and listen to a few tracks. Users with a registered account may log in with their account, search for songs, listen to music, download tracks on demand, download vouchers, and buy CDs. The final function will be that of the system administrator, who will be the general administrator of the system and will personally oversee its operation. They will be involved in the evaluation of material for upload to the system, as well as the management of client information and transaction data.
2. Use Case specification for 2 Use cases
Use Case specification 1 Use case name Create New User Account Actor(s) Customer(primary), Tune Source Company Summary Description Allows customers to make account registration on the platform of "Tune Source" Priority Must-Have Status Medium Level of details Pre-Condition User must register as “Customer” Post-Condition(s) ➢ If all goes well, a "Customer" account is created. ➢ The user-created is granted the appropriate rights. ➢ A four-digit customer number and a default password are issued to the user. ➢ If a failure occurs, the Customer receives an error message. Basic Path ➢ The customer clicks the new member registration button on the homepage of "Tune Source's" digital music website. ➢ Customers provide the necessary information in the default fields. ➢ After entering their information, customers must click the registration button.
