Assignment 2 - Software Development Life Cycle (SDLC) - PASS, Assignments of Computer Science

Download Assignment 2 - Software Development Life Cycle (SDLC) - PASS and more Assignments Computer Science in PDF only on Docsity! ASSIGNMENT 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 09: Software Development Life Cycle Submission date 11/07/2022 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Huynh Minh Huy Student ID GCD210173 Class GCD1001 Assessor name Tran Trong Minh 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 Huy Grading grid P5 P6 P7 M3 M4 M5 M6 D3 D4  Summative Feedback:  Resubmission Feedback: Grade: Assessor Signature: Date: Lecturer Signature: 2. Mockup. .............................................................................................................................................................. 25 References ............................................................................................................................................................................... 30 Table of Figures Figure 1: Stakeholder. ........................................................................................................................................................... 6 Figure 2: Data Flow Diagram. .......................................................................................................................................... 17 Figure 3: Entity Relationship Diagram. ........................................................................................................................ 18 Figure 4: Flow Chart. ........................................................................................................................................................... 19 Figure 5: Log-in Page. .......................................................................................................................................................... 21 Figure 6: Register Page. ...................................................................................................................................................... 22 Figure 7: Landing Page. ...................................................................................................................................................... 23 Figure 8: Home Page. ........................................................................................................................................................... 24 Figure 9: Log-in page. .......................................................................................................................................................... 25 Figure 10: Register Page. ................................................................................................................................................... 26 Figure 11: Landing Page..................................................................................................................................................... 26 Figure 12: Home Page. ........................................................................................................................................................ 27 Figure 13: Home Page In Mobile Interface. ................................................................................................................ 28 Figure 14: Landing Page in Mobile Interface. ............................................................................................................ 29 Introduction. The previous assignment explored several software development lifecycles and emphasized the significance of a feasibility analysis for the Tune Source project. Furthermore, analyzing the applicability of software behavioral design methodologies by describing how user and software criteria have been met. Task 1 – Requirement. I. Identify the stakeholders, their roles and interests in the case study. 1. What is stakeholder? A stakeholder is any individual, group, or party who has an interest in an organization and the effects of its actions. Employees, consumers, shareholders, suppliers, communities, and governments are all examples of stakeholders. Diverse stakeholders have different interests, and firms frequently confront trade-offs while attempting to please everyone. Figure 1: Stakeholder. 2. Types of stakeholder. a. Customers.  Stake: Product/service quality and value Many would contend that companies are there to serve their clients. Customers are stakeholders in a company because they are affected by the value and quality of the goods and services offered. For instance, when boarding a flight, a passenger practically places their life in the hands of the airline. b. Employees.  Stake: Employment income and safety Because they receive benefits and an income to maintain themselves, employees have a direct financial interest in the business (both monetary and non-monetary). The nature of the firm will determine whether employees' interests in health and safety exist (for example, in the industries of transportation, mining, oil and gas, construction, etc.). c. Investor.  Stake: Financial returns Shareholders and debtholders are both types of investors. Shareholders invest capital in the business with the expectation of earning a certain rate of return on that investment. Shareholder value is a topic that many investors are interested in. All other capital providers, such as lenders and potential acquirers, are included in this category. All shareholders are inherently stakeholders, but not all stakeholders are shareholders. 4. Stakeholder role with interest in Tune Source Project. Stakeholder Roles Interest Huynh Minh Huy Project Manager Project managers take the lead in project planning, execution, monitoring, control, and closure. Here is an overview of the project manager role, responsibilities, required credentials, projected wages, and job-search advice. Users Customers Customers are those who utilize Tune Source services to listen to music and buy it, which boosts the company's revenue. John Margolis, Megan Taylor, Phil Cooper Co-Founders of Tune Source Co-Founders will be able to offer ideas, develop the project, and handle budgeting and spending management. The IT department at Tune Source Management, maintenance, and monitoring of the website As it has worked with the ISP to manage the site, get knowledge with Internet technologies. Carly Edwards, Assistant Vice President, Marketing Project Sponsor The project sponsor will be accountable for the entire success of the project, including the selection of the project manager and team, the development of success criteria, and the project's successful conclusion. 5. Stakeholder Requirements. Stakeholders Requirements Provided Huynh Minh Huy Carry out the project and assist the team in developing software to meet the specifications. Users Customers will be able to find and buy digital music downloads. John Margolis, Megan Taylor, Phil Cooper Co-Founders must bring the system to market as quickly as feasible. The IT department at Tune Source Increase sales by enabling consumers to purchase non-copyrighted music downloads via kiosks in their stores and via the internet via their website. Carly Edwards, Assistant Vice President, Marketing Management and maintenance. 6. Identify FRs and NFRs of Tune Source Project. a. Definition of Functional Requirements. A Functional Requirement (FR) describes the service that the program must provide. It refers to a software system or a component of one. A function is nothing more than the software system's inputs, behavior, and outputs. It might be a computation, data manipulation, business process, user interaction, or any other specialized activity that defines the function of a system. In software engineering, functional requirements are also known as functional specifications. Functional Requirements Description Example Download Allow clients to download their purchased songs. Customers may download and listen to their favorite songs without needing to connect to the internet. You may also make an album to put it in. Listen Allow customers to listen to music online without downloading simply connecting to the Internet. Customers may listen to the music by just clicking on it. When the song ends, the music will switch to a new one. Search Allow users to search for songs by using song-related terms like song title, artist name, album name, or a phrase in the song. When a customer submits a song title or lyric, the system displays the name of the song. Register Allows new users to create a new account in order to access the Tune Source service. Customers can access their registered account and download the copyrighted music from Tune Source. Login to website Allow customers and administrators to log in to the Tune Source system and utilize accessible accounts to access all other services. When logged in, the consumer gets access to all system functions and can purchase gift cards. Purchase gift card/song Customers may purchase gift cards and song downloads. Customers may purchase songs to delight themselves and gift cards to friends, such as trail 1 weeks to trail service. Manage account/information Customers' account information may be managed and modified by the administrator. Customers' information, such as name, address, bill, date of birth, and so on, can be changed by the administrator.  Survey/Questionnaire. The phrase "questionnaire" refers to the series of questions you are asking an individual. A survey is the process of gathering, analyzing, and interpreting data from a large number of people. It seeks to learn more about a group of individuals.  Benefits: - It takes less time for participants to answer. - When compared to interviews, you can obtain more accurate information.  Drawbacks: - Based on the replies made by participants, follow-up surveys may be necessary. - Some questions may be unclear to all participants. - Open-ended questions necessitate deeper investigation. - The surveys may not be completed by all stakeholders.  Mind Mapping. Acquiring project requirements requires not just gathering information, but also capturing, structuring, and organizing it. Mind mapping might be a very efficient way of capturing a brainstorming session.  Benefits: - A wealth of important information. - It works in the same way as your mind operates in a hierarchy, pushing you to be analytical in order to find gaps and trends. - The structure allows you to go on to the next stage (information sorting) before the requirement gathering is finished, saving you time and effort.  Drawbacks: - Manual mind mapping (with a pen and paper) is inefficient and unorganized. - It can be tough to translate ideas and intentions into action without the right tools. 2. Conclusion. In this Tune Source project, a survey/questionnaire is used to collect needs since it is simple to collect data from a broad audience, takes less time for users to reply, and provides more reliable information than other strategies.  Assumption about the project justifying the techniques that you have chosen. The Questionnaires approach enables team projects to get critical information and data. Furthermore, if the team project is to create an excellent research report, the project must have exceptional facts. Furthermore, if the project requires high-quality data, a well-designed questionnaire or research would be required. Questionnaire procedures are the most popular and easiest way to gather data in research. As a result, a team project may create a survey, disseminate it to a large number of individuals, and then analyze and assess the responses.  Steps in the development of Survey/Questionnaire. The following Technique was used to obtain requirements: Step 1: Determine the important information we must know. Step 2: Who will get the Survey? Step 3: How will the data be collected (by mail, email, or phone)? Step 4: What questions will be asked? Step 5: Check that the questions only disclose potential respondents and, if necessary, change them. Step 6: Make the questionnaire accessible to the general audience. Step 7: Locate the solution. Step 8: Perform a test. Step 9: Put the results into action. Task 2 – Analyze the requirements. I. Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation. 1. Data Flow Diagram (DFD). The Data Flow Diagram (DFD) is a system paradigm that aligns data and progress. It demonstrates how information is transferred from one operation or function in the system to another. The data flow diagram in Tune Source should assist developers in identifying external influences or determining the scope of the project. Figure 2: Data Flow Diagram. Task 3 – Design. I. Explain how user and software requirements have been addressed in the design.  Requirements and functions for design. User can listen to the music when they find the song by clicking on the song.  So we need.  Landing Page.  Home Page.  Register Page.  Log-In Page. 1. Wireframe. Wireframes are the design's base upon which everything else is built. They are black and white images that rely primarily on grey boxes and text to portray what a product will appear like. They are low quality and quick to construct, and are frequently used in brainstorming sessions. Creation may be done using paper and pencil, a whiteboard, or in a product management platform – and it does not have to be done by a UX designer. Product managers may step in to assist with brainstorming. Wireframes should be utilized to gain agreement on a concept's essential functionality. The exclusion of aesthetic components like as colors and logos is deliberate, as critiques should focus on whether or not the suggested layout or organization will benefit users rather than on visual aspects.  Wireframe of Tune Source Web. Figure 5: Log-in Page. UNIVERSITY w Ab ‘BTEC Sign Up for a free account Create Password What should we call you? Figure 6: Register Page.  2. Mockup. Mockups take wireframes to the next level by incorporating design components like color schemes, fonts, icons, and navigation elements. Typically, more than one prototype is generated, presenting decision-makers with a variety of choices to consider. Actual content is frequently added in renderings to make them more indicative of the final result. To produce mockups, more work and talent are necessary. A UX designer will construct and show the possibilities using digital software. A more extensive visual assessment is recommended when the prototypes are given to stakeholders. The realistic depictions make it straightforward to determine what makes sense about the designs from the consumers' point of view. Comparing mockups assists the team in reaching an agreement on a design direction. Because mockups are static, any modifications or requests can be easily included.  Laptop, Computer Interface. Figure 9: Log-in page. ‘BTEC Sign up for a free account. Figure 10: Register Page. Tune Source to WORKOUT Dein nd ad te aad Figure 11: Landing Page. 127.001 Bret ga ry WORKOU e 7 ‘iy? Doral ror) Dede Be ad Sem Coe ey ered