Tune Source Music Platform Development - Prof. Loan, Assignments of Software Development

The tune source project is a comprehensive music platform development initiative that aims to provide high-quality music experiences for customers. It discusses the use of object-oriented and structured analysis techniques to model the system's functionality, addressing both functional and non-functional requirements. Key aspects include user management, music search and playback, purchase and download options, and administrative capabilities. The project involves various stakeholders, emphasizing the importance of requirements analysis, design, and quality assurance to deliver a reliable and effective music platform.

Typology: Assignments

2021/2022

Uploaded on 10/09/2022

le-tan-nghia
le-tan-nghia 🇻🇳

2 documents

1 / 18

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Page 1
ASSIGNMENT 2 BRIEF
Qualification
BTEC Level 5 HND Diploma in Computing
Unit number
Unit 9: Software Development Life Cycle
Assignment title
Undertake a software development lifecycle
Academic Year
Unit Tutor
Issue date
Submission date
Name and date
Submission Format:
Format:
The submission is in the form of 1 document.
You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3
and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm.
Citation and references must follow the Harvard referencing style.
Word limit: 3000 words (excluding figures and references). Submissions that exceed this
limit will be rejected.
Submission:
You must submit the assignment by the due date and follow the submission method
specified by the Tutor. The submission form is soft copy, which is to be uploaded to the
following URL: http://cms.greenwich.edu.vn.
Note:
Your assignment must be your own work, and not copied by or from another student or
from other sources, such as book etc. If you use ideas, quotes or data (such as diagrams)
from books, journals or other sources, you must reference the sources, using the Harvard
style. Make sure that you know how to reference properly and that you understand the
plagiarism guidelines. Plagiarism is a very serious offence, which will result in a failing
grade.
Unit Learning Outcomes:
LO3 Undertake a software development lifecycle.
LO4 Discuss the suitability of software behavioural design techniques.
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12

Partial preview of the text

Download Tune Source Music Platform Development - Prof. Loan and more Assignments Software Development in PDF only on Docsity!

ASSIGNMENT 2 BRIEF

Qualification BTEC Level 5 HND Diploma in Computing Unit number Unit 9 : Software Development Life Cycle Assignment title Undertake a software development lifecycle Academic Year Unit Tutor

Issue date Submission date Name and date

Submission Format:

Format:

The submission is in the form of 1 document. You must use the Times font with 12pt size , turn on page numbering ; set line spacing to 1. and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation and references must follow the Harvard referencing style. Word limit : 3000 words (excluding figures and references). Submissions that exceed this limit will be rejected.

Submission:

You must submit the assignment by the due date and follow the submission method specified by the Tutor. The submission form is soft copy , which is to be uploaded to the following URL: http://cms.greenwich.edu.vn.

Note:

Your assignment must be your own work, and not copied by or from another student or from other sources, such as book etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference the sources, using the Harvard style. Make sure that you know how to reference properly and that you understand the plagiarism guidelines. Plagiarism is a very serious offence , which will result in a failing grade. Unit Learning Outcomes:

LO3 Undertake a software development lifecycle. LO4 Discuss the suitability of software behavioural design techniques.

Assignment Brief and Guidance:

Tasks

At this stage, you have convinced Tune Source to select your project for development. Complete the following tasks to analyse and design the software. Task 1 – Analysis (1)  (P5.a) Identify the stakeholders, theirs roles and interests in the case study. Review the requirement definition of the project. Clearly indicate which stakeholder(s) provide what requirements. Discuss the relationships between the FRs and NFRs.

 (P5.b) Discuss the technique(s) you would use to obtain the requirements. If needed, you may state suitable additional assumptions about the project in order to justify the technique(s) that you choose.

 (M3) Discuss how you would trace these requirements throughout the project.  Task 2 – Analysis (2) (P6) Analyse the requirements that you identified in Task 1 using a combination of structural and behavioural modelling techniques that you have learnt. Scope : you only need to construct the activity and class diagrams for the use case of one top-level function. The activity diagram needs only cover 2 sub-functions.

 You can choose to use either object oriented analysis and design techniques (use case diagram, class diagram, activity diagram) OR structured analysis and design techniques (DFD, ERD, flowchart).  Do not mix these two sets of techniques. For example, do NOT use ERD with activity diagram!

Task 3 – Design Based on the analysis result, discuss how you would conduct the design phase:  (P7) Discuss how the user and software requirements are addressed in the design phase. [MV]

Learning Outcomes and Assessment Criteria Pass Merit Distinction

LO3 Undertake a software development lifecycle D^3 Critically evaluate how the use of the function design paradigm in the software development lifecycle can improve software quality.

P5 Undertake a software investigation to meet a business need.

P6 Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation.

M3 Analyse how software requirements can be traced throughout the software lifecycle.

M4 Discuss two approaches to improving software quality.

LO4 Discuss the suitability of software behavioural design techniques

D4 Present justifications of how data driven software can improve the reliability and effectiveness of software.

P7 Explain how user and software requirements have been addressed.

M5 Suggest two software behavioural specification methods and illustrate their use with an example. M6 Differentiate between a finite state machine (FSM) and an extended- FSM, providing an application for both.

TABLE OF CONTENT

  • ASSIGNMENT 2...............................................................................................................................................
    • P5. Identify the stakeholders, theirs roles and interests in the case study
      • I. Introduction
      • Requirement II. Task 1-Analysis (1) 1. Identify the stakeholders, theirs roles and interests in the case study. a)
      • Requirement
    • behavioural modelling techniques P6) Analyse the requirements that you identified in Task 1 using a combination of structural and
      • Process modeting
      • Entity relationships diagram
    • P7
  • REFERENCES

3 The IT department Website operations Get a salary from the company 4 Customer Carry out shopping activities, bring in the number of subscribers, the number of download, the number of people using the site is large, increase revenue and grow the company. Give feedback to develop the website.

Get good music back, a great experience when visiting the site.

Requirement  Project manager (Co-founder): As a project manager, I want the system to fully meet the company's requirements, without any errors so that the user experience is improved. As a project manager, I want the system to be completed within 3 months so that it can be released to the market this fall.

Sponsor: As a sponsor, I want to be advertised, introduced on Tune Source website so that many people know me. As a sponsor, I want the site to have good, quality music that increases the number of users and revenue.

IT department: As an IT department, I want to have an admin login account so that I can login and manage the Tune Source website. As an IT department, I want CRUD function so that I can view, add, update, delete tunes. As an IT department, I want the system to give an error when it encounters any error so that the system runs smoothly. As an IT department, I want functions like search, filter so that I can find music more easily.

As an IT department, I want statistical functions so that I can see metrics like revenue, number of subscribers.

  • Customer: As a customer, I want registration and login functionality so that I can buy tracks. As a customer, I want my account to be secure so that my information is not exposed. As a customer, I want the system to have an easy-to-use interface so that shopping is easier. As a customer, I want good quality website compared to that fast access speed. As a customer, I want to see a list of tracks so that I can choose the music I want. As a customer, I want the search function so that I can select tracks faster. As a customer, I want the listening function so that I know the quality of that track. As a customer, I want download function so that I can download selected track. As a customer, I want the gift card buying function so that I can get the best deals from it. As a customer, I want the review function so that to send my experiences and develop the website. As a customer, I want 2 separate functions i.e. fixed and unlimited downloads so that's convenient for downloading music or saving money. b ) The relationships between the FRs and NFRs. FRs: A functional requirement defines a system or its component in software engineering. It specifies the tasks the program must complete. A function is made up of three parts: inputs, behavior, and outputs. It can be a calculation, data manipulation, business process, user interaction, or any other function that determines what a system is likely to do. Functional software requirements assist you in capturing the system's intended behavior. This behavior can be represented in terms of functions, services, or tasks that a system must accomplish. NFRs: A software system's quality characteristic is defined by a non-functional need. They are a set of criteria used to judge and evaluate a system's specific operation. A non-functional requirement is required to ensure the overall software system's usability and effectiveness. Non-functional requirements that are not met can lead to systems that do not meet user needs. Non-functional Requirements allow you to place constraints or limitations on the system's architecture across several agile backlogs. When there are more than 10000 simultaneous users, the site should load in 3 seconds. Non-functional requirements must be described just as carefully as functional requirements. Relationship: FRs and NFRs requirements lay the foundation for a software development project's

Interview method: The interview is the most typical method for gathering requirements. The interview process has five fundamental steps: selecting interviewees, designing interview questions, preparing for the interview, conducting the interview, post interview follow-up. The interviewer asks stakeholders questions to acquire information in this method. Face-to-face interviews are the most popular technique. In a structured interview, the interviewer asks a list of predetermined questions. When the interviewer does not follow a set framework or asks specified questions, it is called an unstructured interview. Suitable method: The best method for this Tune source project is Interview because it will be planned in advance with a detailed, purposeful question system, in addition, the answer is not limited to yes or no but rather an open answer. Users of Tune Source website are not only internal but mainly music enjoyment customers, a workshop of JAD method will not be able to get all the requirements of users. In addition, the cost of the Interview method is also quite low compared to opening JAD workshops. Type of Question Examples Closed-Ended questions What statistical functions do you want the website to have? What technology do you want the website to be secured with Opened-ended questions What do you think about the look and feel of the current website? What are the problems you usually have when downloading music on a website? What special functions do you want the website to have? How much money do you usually spend on enjoying music? Probing questions What is your favorite website, why do you like it? Does the site have a music download function with a promotional price?

P6) Analyse the requirements that you identified in Task 1 using a combination of structural

and behavioural modelling techniques

Customer can login, register, search, listen to music, they can also select and add to favorites. You can then purchase music or gift card. Admin can login and perform action such as view, add, edit, delete tracks and view statistical data. In addition, the bank also authenticates the customer’s bank account

Process modeting Use case name Search for music ID BM- Desciption Search for certain song Actor User, admin Trigger User or admin use website to search

Actor Admin Pre-condition 1. The song exists on Tune Source server

  1. Admin account must be used for this action Normal Course 1. Search the song admin want to delete
  2. Delete the song
  3. Save action Post-Condition The song got delete successfully

Use case name Music manager (Edit Song) ID: ES- Description Admin can edit the song and its information Actor Admin Pre-condition 1. Admin account must be for this function

  1. The song is available to edit Normal Course 1. Admin locate the song they want to edit
  2. Edit the song’s information
  3. Save the action Post-Condition The information of the song is edited

Use case name User’s information manager ID: UM- Description Admin and User can both manager the user information Actor User, Admin Pre-condition Admin account is logged in / This user account is logged in Normal Course 1. User/Admin logged in the account need to edit

  1. Find the option to manager this account information
  2. Edit the information
  3. Save the action Post-Condition Account’s information is edited

Entity relationships diagram

Entity Description Admin The manager of whole system Customer The user of the system Song Thing being listen/bought by customer Purchase The detail of what the customer have bought CD Information of the song being bought by customer

DFD DFD of the whole system