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 0 9: 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 GCD 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 D
Summative Feedback: Resubmission Feedback:
Grade: Assessor Signature: Date: Lecturer Signature:
Table of Contents
- Introduction.
- Task 1 – Requirement.
- I. Identify the stakeholders, their roles and interests in the case study.
- What is stakeholder?
- Types of stakeholder.
- Roles of Stakeholders.
- Stakeholder role with interest in Tune Source Project.
- Stakeholder Requirements.
- Identify FRs and NFRs of Tune Source Project.
- Discuss the relationships between the FRs and NFRs.
- II. Discuss the technique(s) you would use to obtain the requirements.
- Some approach/technique (es) suitable for the project.
- Conclusion.
- Task 2 – Analyze the requirements.
- create supporting documentation. I. Use appropriate software analysis tools/techniques to carry out a software investigation and
- Data Flow Diagram (DFD).
- Entity Relationship Diagram.
- Flow Chart.
- Task 3 – Design.
- I. Explain how user and software requirements have been addressed in the design.
- Mockup.
- References
- Figure 1: Stakeholder. Table of Figures
- Figure 2: Data Flow Diagram.
- Figure 3: Entity Relationship Diagram.
- Figure 4: Flow Chart.
- Figure 5: Log-in Page.
- Figure 6: Register Page.
- Figure 7: Landing Page.
- Figure 8: Home Page............................................................................................................................................................
- Figure 9: Log-in page.
- Figure 10: Register Page.
- Figure 11: Landing Page.....................................................................................................................................................
- Figure 12: Home Page.
- Figure 13: Home Page In Mobile Interface.
- Figure 14: Landing Page in Mobile Interface.
- 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.
d. Suppliers and Vendors. Stake: Revenues and safety Suppliers and vendors sell goods and/or services to businesses that rely on them for revenue and ongoing income. Suppliers' health and safety are at risk in many industries because they may be directly involved in the company's operations. e. Communities. Stake: Health, safety, economic development Communities play an important role in the success of large businesses that locate in them. They are influenced by a variety of factors, such as job creation, economic development, health, and safety. When a large corporation enters or exits a small community, it has an immediate and significant impact on local employment, income, and spending. Some industries may have a negative impact on health because they alter the environment. f. Governments. Stake: Taxes and GDP Governments are also important stakeholders in businesses because they collect taxes from the company (corporate income taxes), as well as from all of the people it employs (payroll taxes), and from other expenses the company incurs (sales taxes). Governments benefit from the overall Gross Domestic Product (GDP) contribution of businesses.
- 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.
- 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.
- 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.
b. Definition of Non-Functional Requirements. Non-Functional Requirement (NFR) describes a software system's quality attribute. They evaluate the software system based on its responsiveness, usability, security, portability, and other non-functional characteristics that are crucial to its success. "How quickly does the website load?" is an example of a nonfunctional requirement. Non-functional requirements that are not met can lead to systems that do not meet the demands of the users. Non-Functional Requirements Description Security A firewall should be installed on a user's database to prevent unwanted access. Compatibility The system performs well in a number of settings. Users may access the website using a variety of devices, including phones, tablets, and laptop computers. Capacity Ensure that the system's capacity is sufficient to support when a large number of people come at the same time, and that users may alter and store settings based on their preferences. Reliability Highly dependable technology continues to perform with the same or similar efficacy after extended use.
- Discuss the relationships between the FRs and NFRs. The functional and non-functional requirements create the groundwork for the success of a software development project. Functional requirements specified certain characteristics to encourage software development. Non-functional requirements are tied directly to software features.
Non-functional requirements are product criteria from the user's perspective that outline how a project should be implemented to create an end-user experience. The software development process is greatly accelerated when the needed product features are identified and requirements for each of those features are established. If the functional or nonfunctional needs are not specified, the project will suffer severely. II. Discuss the technique(s) you would use to obtain the requirements.
- Some approach/technique (es) suitable for the project. Joint Application Development (JAD). JAD (Joint Application Development) is a way of including the client or end user in the design and development of an application through a series of collaborative workshops known as JAD sessions. Benefits: - JAD enables you to solve problems more quickly and develop better, error-free software. - The company's and clients' combined participation reduces all hazards. - JAD saves project development costs and time. - System quality is improved by well-defined criteria. - Progress is accelerated as a result of close communication. - JAD motivates the team to work quicker and to produce on schedule. Drawbacks: - Diverse viewpoints on the team make it challenging to align goals and keep focus. - JAD may need a large time investment depending on the scale of the project.
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.
- 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.
- 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.
- Flow Chart. A flowchart depicts the individual phases of a process in sequential order. It is a general-purpose tool that may be used to define a range of processes, such as a manufacturing process, an administration or service process, or a project plan. It is a standard process analysis tool and one of the seven fundamental quality tools. Figure 4 : Flow Chart
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.
- 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.
