ASSIGNMENT 02 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09 Software Development Life Cycle Submission date March 12, 2023 Date Received 1st submission[.]
ASSIGNMENT 02 FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title Unit 09: Software Development Life Cycle Submission date March 12, 2023 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Nguyễn Hữu Thắng Student ID GCH211274 Class GCH1103 Assessor name Đỗ Quốc Bình 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 Thắng Grading grid P5 P6 P7 M3 M4 M5 M6 D3 D4 ❒ Summative Feedback: Grade: Internal Verifier’s Comments: Signature & Date: ❒ Resubmission Feedback: Assessor Signature: Date: Contents Introduction I Task – Analysis 1.1 Identify the stakeholders, their roles and interests in the case study 1.2 Identify FRs and NFRs of Tune Source Project 1.3 Discuss the technique(s) you would use to obtain the requirements .9 Interviews Joint Application Development (JAD) 11 Questionnaires 11 Document Analysis 12 Observation 12 Selecting the Appropriate Techniques 12 II Task – Analysis (2) 13 2.1 Use Case Diagram for the whole system 13 2.2 Use Case specification for Use cases 15 2.3 Context Diagram for the whole system 17 2.4 Data Flow Diagram – Level for the whole system 18 2.5 ERD for the whole system 19 III Design 20 3.1 Discuss how the user and software requirements are addressed in the design phase 20 Mock-up, and Wireframe are used in the project 20 Architecture for the project 25 Technical solution stack for the project 26 Conclusion 28 References 28 Figure 1: Sample Requirements Definition Figure 2: Comparison of Requirements Elicitation Techniques (Dennis, page 129) 12 Figure 3:Use case Diagram 14 Figure 4: Tunes Source Context Diagram (Dennis) 18 Figure 5: ERD for Tunes Source System 19 ASSIGNMENT Introduction Southern California is located to the corporate headquarters of Tune Source Three businesspeople with ties to the music business—John Margolis, Megan Taylor, and Phil Cooper—created Tune Source Initially, John and Phil worked together to launch a series of brick-and-mortar businesses in southern California that catered to customers looking for historic and difficult-to-find jazz, rock, country, and folk recordings A quick invitation to join the partnership came Megan's way thanks to her connections and expertise in classical music Quickly, people began to know that Tune Source was the best site to look for uncommon audio recordings With a growth rate of between 3% and 5% last year, annual revenues were $40 million Customers can browse and buy CDs on the Tune Source website now An established regional Los Angeles Internet Service Provider (ISP) is hosting this website, which was originally created by an Internet consulting firm Tune Source's IT department has gained knowledge with Internet technologies because of its collaboration with the ISP to keep the site up-todate As the project manager for the FPT business I was contracted to present a website development strategy for the music label Tune Source that considers risks, interest rates, and potential weaknesses The specifications state that a website must be adaptable to multiple downloads across the board for all carriers I'll provide solutions using the SDLC methodology to address the issue In addition, I provide evidence and information on the strategy I've suggested for persuading Tune Source to support my initiative I Task – Analysis I.1 Identify the stakeholders, their roles and interests in the case study A stakeholder is a person, group, or business that has the ability to influence (or be affected by) a new system The project champion, system users, and organizational management are often the most crucial stakeholders in the introduction of a new system, while additional stakeholders may also be impacted on occasion A project's sponsor Investor in this project is Carly Edwards, Associate Vice President, Marketing The choice to accept this project and future collaboration will therefore depend on how your specifications for the final product standard The company was founded by Phil Cooper, Megan Taylor, and John Margolis The direction they want for the project's outcome is what they are responsible for providing Marketing Users participate in advertising by using products and providing feedback They play the user experience role first, then the marketing role System requirements include both functional and non-functional requirements, or characteristics the system should possess (How the System Should Be Built) An uncomplicated text statement that solely addresses functional and non-functional demands is referred to as a "requirement definition" sometimes Alternatively said, this is a need (Dennis, 18 Jan 2012) To establish a comprehensive website about music that generates money for the company, several stakeholders, including shareholders, partners, and staff, are involved in the project These were the requirements for this project: Browse the music archive Hear a sample of the music Purchase sheet music Register and log in Other promotions: Clients are the company's customer partner, who also serves as the project's requirements maker and product tester A developer is a person who creates a full program and creates project software based on customer needs Project managers oversee overseeing the personnel, making sure the project stays on track, and reporting project statuses to clients Tester is the person who writes test lists of software before using it in the market I.2 Identify FRs and NFRs of Tune Source Project Functional requirements are "the capabilities of a product or things that the product must for its consumers," according to the International Institute for Business Analysis (IIBA) Its functional requirements, or how the system will function and operate via specified processes, indicate how a system can help a user execute a task in the first place One type of necessities is nonfunctional requirements These conditions are stated as "the quality attributes, design and implementation limits, and external interfaces which a product must have" by the IIBA Although the term "nonfunctional" is not particularly evocative, this need category encompasses essential behavioral characteristics that the system must have, such as performance and usability Figure 1: Sample Requirements Definition Base on the FIGURE table 3-3 page 110 in the book by Alan Dennis (Dennis, January 18, 2012), I define FRs and NFRs of the Tune Source Project Functional Requirements Guest and Customer: The system will allow to search and view the demo of the Song The system will allow to register an account by phone number or popular account types such as Microsoft, Facebook, Gmail, … Project sponsor Carly Edwards, Assistant Vice President, Marketing The system will have a search feature and make recommendations for songs based on each person's flavors The system will enable monthly music download packages The system will allow music downloads with a certain cost Customers will be able to purchase VIP cards through the system The purchase made by the consumer will be documented by the system The system will contain a section to examine overall revenue, weekly spending, and total spending The system will permit editing of personal data John Margolis, Megan Taylor and Phil Cooper, Co-founder Customers will be able to comment on the product in an area of the system Customers will be able to submit requests for admin through a section on the system Admin: The system will use a separate form to manage music products such as adding, editing, deleting, and updating Access to the management system will need to be granted through a different administrator account Non-Functional Requirements Operational The system should work on digital devices, but for client login, mobile phones, TVs A customer management system should be used to manage the system The system should be able to use credit cards or online banking to purchase products Performance A team of three individuals should be assigned to the system who will read comments, keep it updated, and only resolve serious errors once a week or every day A team of four highly specialized individuals should be assigned to the system to update weekly income and development statistics Security To access the management page, each employee needs to have their own account On copied systems, such as the computer given by the company or the registered personal computer, all logins from the management page are required Each employee is only given a single account and is only given access to the designated areas Cultural and Political The employees should be aware about musical genres and have certain musical preferences According to the established laws and regulations, customer information is kept private The community standards outlined by Tune Source must be followed by all posts, music, lyrics, captions, and other speech and copyright components I.3 Discuss the technique(s) you would use to obtain the requirements The analyst should be aware that gaining political support for the project and creating a sense of trust between the project team and the users are significant side effects of the process of determining requirements Who is involved in the process of determining requirements should be carefully chosen by the analyst Interviews The methods for eliciting requirements that are most frequently employed The fundamental steps in the interview are as follows: choosing interviewees, create interview questions, getting ready for the interview, conducted interviews, After the interview, follow-up Selecting interviewers A timetable for interviews that outlines who will be interviewed, why, and where and when the interview will occur is advised The schedule may be an official list that is part of the work plan, or it may be an unofficial list that is used to help determine the times of meetings Based on the analyst's information needs, the people on the interview schedule are selected Designing Interview Questions Interview questions can be divided into three categories: probing, open-ended, and closed-ended With closed-ended questions, analysts can direct the interview and get the data they require These questions, however, neither reveal the cause of the response's oddity nor they produce information that the interrogator did not intend to find out Open-ended questions are those that provide the discussion topic the opportunity to elaborate In many ways, they are similar to essay questions you may see on an exam Open-ended questions are designed to elicit in-depth responses while providing the interviewee greater control over what they choose to disclose The probing question is the next style of query The purpose of this follow-up question is for the interviewer to learn more and get clarification on any ambiguous points in the interviewee's response These will aid the interviewer in providing more thorough, accurate, and detailed information about what is being discussed, and they also serve as a sign that the interviewee is genuinely interested in the topic and questions Preparing for the Interview Good interview preparation helps the interview move in the right direction We will need to compile a list of the questions, subjects, and material that must be covered, then arrange them suitably so that people will not find it difficult to ask and answer questions Areas to focus on, questions the interviewer can answer, and a clear distinction between those areas After that, evaluate the queries to determine their priority and importance Finally, I need to set aside a reasonable amount of time to make sure the candidate has time to pay Conducting the Interview When you the interview, you can start to establish confidence with the interviewee and then collect the essential data Both partners frequently lack complete trust in one another at first Some interviewees will occasionally withhold information As a result, we must exercise good communication, be objective, ask the proper questions, act professionally, and look for reliable, independent information In order to build more trust between the two parties, you should also clarify why you and they are here throughout the interview Post-interview Follow-up The analyst must record the interview in order to document the information and ensure that information is collected after the session There will be a lot of interview notes taken to record valuable information To avoid forgetting crucial information, the information collection process should be finished as quickly as possible after the interview is over Document Analysis The current state of the system is understood through document analysis The organization's formal systems are described in forms, reports, policy manuals, and organizational charts The "actual," unofficial system is different from the official one and highlights what needs to be corrected The creation of new forms or modifications to current forms/reports by users is a sign that the system needs to be modified Observation Monitoring processes is what is meant by observation This is an effective tool for gaining perspective on the system as-is and for confirming the accuracy of data gathered from other sources But, when they know they are being watched, people tend to behave far more cautiously Selecting the Appropriate Techniques Figure 2: Comparison of Requirements Elicitation Techniques (Dennis, page 129) - Several types of information can be gathered during the information collection process using each approach Three key categories may be found in the information-gathering process: the present situation, improvements, and future There will be a way of enhancement or maintenance for each type of information. Regardless of phase or direction, the system does not modify or release the required information - Depth of Information: The phrase "depth of information" refers to how thorough and in-depth the information is that the technique normally generates as well as how successful it is at acquiring not only facts and views but also a knowledge of the reasons behind those facts and opinions - The term "breadth of information" refers to the variety of information and information sources that may be quickly acquired utilizing that method An extensive range of data can be easily gathered from a wide range of data sources using both surveys and document analysis - Integration of Information: One of the most challenging aspects of gathering requirements is integrating information from diverse sources - User Involvement: The degree to which the target users of the new system must devote time and effort to the analysis process is referred to as user involvement - Cost: Whether a technology is implemented depends in large part on its cost Because sometimes the expense is more concerned with development than it is with acquiring requirements The marketing department created the specifications for the Tune Source project, but they weren't very detailed A broader and deeper grasp of the requirements is crucial since it provides development direction Although it is a wise decision, interviewing is expensive and time-consuming I therefore require a thorough, meticulous, and precise plan I will thus select methodologies, Joint Application Development (JAD) and Questionnaires, based on the preceding table II Task – Analysis (2) II.1 Use Case Diagram for the whole system A use case diagram serves as the primary visual representation of the hardware and software specifications for a novel, unfinished software application The majority of use case diagrams are simple The specifics of the use cases are not displayed: The relationships between use cases, players, and systems are only briefly outlined in a few places It does not show the sequence of steps taken to achieve the goals of each use case. Figure 3:Use case Diagram II.2 Use Case specification for Use cases During the analysis and design phase, it is usual to develop the use case specification iteratively The capabilities of the use case and the steps necessary to execute its usual flow are initially only briefly defined As the analysis progresses, the steps are expanded to provide more information The use case also contains the exceptional flows, to sum up Each project is permitted to use a standard use case template for the purpose of creating the use case specification Use Case Name Create an account Actor(s) Summary Description Priority Status Pre-Condition Guest(main) Allowed to register by email or phone number Necessary Medium Level of details Client has an email or phone number Complete the required form The customer's account has been successfully registered Successfully logged into the web with the login account Access Tune Source's website Press register Complete the fields for your name, email or phone number, address Notice that some details are necessary (email) Choose Accept Account Type Consumers should read to make sure they are aware of their rights and the law Press the register icon Display the login page after a successful registration Completely enter all the login details Choose Sign Up Visit the website after successfully logging in 1a Email or phone number already exists 5b Name required 8a Invalid account or password 8c Login failed a The information entered is not valid b Have not filled in required information c Network or connection error during execution Post-Condition Basic Path Alternative Paths Use Case Name Buy music Actor(s) Summary Description Priority Status Pre-Condition Post-Condition Customer (Client) Allows for pre-registered accounts to make payments over the website Basic Path Alternative Paths Must Have High Level of details User has an account Make the payment properly A notification of a successful purchase is given to the customer Clients have unlimited access to the songs they have purchased Consumers select the song they wish to purchase Choose "Buy" The payment screen is shown on the website Complete the payment details (debit or credit card) Confirmation of payment A form to enter the code and transmit it to the phone number is visible on the page. Input the payment code in step The webpage shows that the transaction was successful Verify the transaction was successful 10 Consumers may utilize the music they have purchased 4a Cannot buy 4b Invalid Information 6c A form to enter doesn’t show up 6d A form to enter doesn’t show up 9d Cannot verify 10d Cannot listen to the song a: The country is not allowed to buy that song b: Input Invalid debit or credit card information c: Losing Network and Connection d: System get a problem II.3 Context Diagram for the whole system The system context diagram, also known as a level DFD, is the highest level of a data flow diagram and has just one process that represents the complete system and sets the context and boundaries of the system that needs to be described It identifies the information exchanges between the system and external stakeholders (i.e., actors) Context diagrams are commonly used in requirements papers Since that all project stakeholders are required to read it, it should be written in simple terms that everyone can understand The objective of the system context diagram is to highlight external factors and events that ought to be considered while composing an exhaustive list of system requirements and constraints DFD level (paradigm) Figure 4: Tunes Source Context Diagram (Dennis) II.4 Data Flow Diagram – Level for the whole system Data flow diagrams, commonly known as DFDs, are used to illustrate how data moves within an organization's information system The term "DFD" refers to the processes a system uses to transport data from the input to file storage and report generation Data transportation diagrams come in logical and physical varieties The logical data flow diagram demonstrates how data flows through a system to perform particular business operations The physical data flow diagram displays the application of the rational data flow (Paradigm, DFD) II.5 ERD for the whole system A form of structural diagram used in database architecture is an entity relationship diagram, commonly referred to as an ER diagram, ER model, or ERD Several ERD connectors and symbols are used to visually indicate the primary components of the system scope as well as the connections between these components It is also called as an entity relationship diagram because of this (ERD) Figure 5: ERD for Tunes Source System III Design III.1 Discuss how the user and software requirements are addressed in the design phase Mock-up, and Wireframe are used in the project Prototypes of a website after it has been finished are called mockups or wireframes I made the decision to develop the first website visualizations using wireframes Login First, when customer enter the website, they will be asked to log in with an account If they have an account, they can choose to sign in by entering their account or if they don't have an account they can click register Register They provide pertinent information and accept the terms on the registration page Customers can use their newly created account to log in and access the homepage after registration Homepage Customers can product searches and use other features at home They can click to view the details of a product when they decide to purchase it