1631 - Software Development Life Cycles -Assignment 2 (Pass), Summaries of Software Development

Download 1631 - Software Development Life Cycles -Assignment 2 (Pass) and more Summaries Software Development in PDF only on Docsity!

Higher Nationals in Computing

Unit 9: Software Development Life Cycle

ASSIGNMENT 2

Assessor name: PHAN MINH TAM

Learner’s name: Nguyễn Bảo Khang

ID: GCS

Class: GCS1005C

Subject code: 1631

Assignment due: Assignment submitted:

❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Assignment Brief 02 (RQF)

Higher National Certificate/Diploma in Business

Student Name/ID Number: Unit Number and Title: Unit 09: Software Development Life Cycle Academic Year: 2021 – 2022 Unit Assessor: TamPM Assignment Title: Undertake a software development life cycle Issue Date: 10/Jan/ Submission Date: Internal Verifier Name: 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. Submission: ● Students are compulsory to submit the assignment in due date and in a way requested by the Tutor. ● The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/. ● Remember to convert the word file into PDF file before the submission on CMS.

3. Discuss how you would trace these requirements throughout the project by using Requirement Traceability matrix. You will have to provide real usage of it. Word limit: 400 – 500 words. Task 2 – Analysis (2) Analyze the requirements that you identified in Task 1 using a combination of structural and behavioral modelling techniques that you have learnt. Scope: You only need to construct following items for the system. You will have to include:  Use Case Diagram for the whole system.  Use Case specification for 2 Use cases.  Context Diagram for the whole system.  Data Flow Diagram – Level 0 for the whole system.  ERD for the whole system. For each diagram, you will have to explain properly. Word limit: 1000 – 1200 words. Task 3 – Design Based on the analysis result, discuss how you would conduct the design phase:
4. Discuss how the user and software requirements are addressed in the design phase.  You will explain how Mock-up, and Wireframe are used in the project. You should include some of the mockup or wireframe (at least 5) design of the Tune Source project to justify that it matches users’ requirements.  You will explain which architecture (client – server, n-tier, microservices, etc.) is suitable for the project with clear illustrations and why.  Then you will address which technical solution stack could be suitable to implement the project with clear explanations.
5. Discuss how activity diagram and pseudocode are used to specify the software behaviour.
6. Discuss how UML state machine can be used to specify the software behaviour. Differentiate between FSM and extended FSM using the case study.
7. Discuss how the data-driven approach improves the reliability and effectiveness of software. Word limit: 800 – 1500. Task 4 – Software quality management
8. Discuss two software quality attributes that are applicable to the project.
9. Discuss two quality assurance techniques that can help improve the software quality in the project.
10. Discuss how the design techniques and approaches that you have used can help improve the software

quality. Word limit: 400 – 1500.

Table of Contents

ASSIGNMENT 2 ANSWERS

P5. Undertake a software investigation to meet a business need

1. Business need analysis

 Business Need: This project has been initiated to increase sales by creating the capability of selling

digital music downloads to customers through kiosks in our stores, and over the Internet using our

website.

 Business Value: We expect that Tune Source will increase sales by enabling existing customers to

purchase specific digital music tracks and by reaching new customers who are interested in our

unique archive of rare and hard-to-find music. We expect to gain a new revenue stream from

customer subscriptions to our download services. We expect some increase in cross-selling, as

customers who have downloaded a track or two of a CD decide to purchase the entire CD in a

store or through our website. We also expect a new revenue stream from the sale of music

download gift cards.

 Analysis: Tune source system need increase sales to help the system reach users easily.

Furthermore, the system need gain a new revenue stream from customers to improve systems -

making improve systems.

2. Stakeholders and their roles in Tune Source Project

2.1. Stakeholders in Tune Source Project

John Margolis, Megan Taylor, and Phil Cooper, Originally, John and Phil

Project Sponsor: Carly Edwards, Assistant Vice President, Marketing.

2.2. Stakeholders roles in Tune Source Project

 Carly Edwards : These are individuals involved in developing the Tune Source platform. They will

be interested in having a clear understanding of the functional and non-functional requirements

of the system, and in ensuring that the project is delivered on time and within budget.

 Assistant Vice President: These are government agencies or bodies that oversee the music

industry and may have a regulatory role in the Tune Source Project. They will be interested in

ensuring that the platform operates within legal and regulatory frameworks.

P a g e | 1

 Marketing: These are companies or organizations that are partnering with Tune Source for

marketing, advertising or distribution. They will be interested in ensuring the platform is attractive

to potential customers and is well-integrated into their own systems.

3. FRs and NFRs of Tune Source Project

3.1. Non-Functional Requirements

The systems can be include all available:

 Tune Source Project can run on handheld devices and it can work on any Web browser.

 This system downloads new status parameters within 5 minutes of a change.

 Tune Source Project can be safe ground from viruses, worm,…

 Customer information can be protected by Data Protection.

3.2. Functional Requirements

● Search for music in our digital music archive.

● Listen to music samples.

● Purchase individual downloads at a fixed fee per download.

● Establish a customer subscription account permitting unlimited downloads for a monthly fee.

● Purchase music download gift cards.

P a g e | 2

Preconditions:

The user must create a "Customer" account on the "Tune Source" system..

Normal Courses:

Firstly, customers must to login or register to the system.

After that, they have to choose search music box and write the name of music which they interested

Postconditions:

Customers can listen music they want to hear

Exceptions:

 The customer lacks or does not have access to an email account.

 The customer gave inaccurate information.

 The customer fails to acknowledge receipt of the email confirming successful registration.

 No email confirmation message was received.

2.2. Use case 2: Register

Use case name: Register ID: UC-02 Priority: High

Actor: Customers

Description: Tune Source currently has a website that enables customers to search for and purchase

CDs.

Trigger: Customers login into website, if they do not have account, they must to register one

Type: R External £ Temporal

Preconditions:

The user must create a "Customer" account on the "Tune Source" system.

Normal Courses:

After customers have accessed to the website, they must to write their name and password exactly. If

they do not have account in Tune Website, they must to create an account include their information if

they want to access into the website

Postconditions:

Customers can have an account to access to website

Exceptions:

P a g e | 4

 The customer lacks or does not have access to an email account.

 The customer gave inaccurate information.

 The customer fails to acknowledge receipt of the email confirming successful registration.

 No email confirmation message was received.

2.3. Use case 3: Purchase Music

Use case name: Purchase music ID: UC-03 Priority: High

Actor: Customers

Description: Tune Source currently has a website that enables customers to search for and purchase

CDs.

Trigger: Customers purchase music in website

Type: R External £ Temporal

Preconditions:

The user must create a "Customer" account on the "Tune Source" system.

Customers must have a bank account to make purchases.

Normal Courses:

 After successfully logging in as "Customer," the "Customer" account enables the purchase of

various CDs as well as payment via banking.

 Tune Source will enlist the help of a third party to record transaction data between the user and

the "Tune Source" payment mechanism.

Postconditions:

Customers can purchase music they want

Exceptions:

 The customer lacks or does not have access to an email account.

 The customer gave inaccurate information.

 The customer fails to acknowledge receipt of the email confirming successful registration.

 No email confirmation message was received.

2.4. Use case 4: Download music

P a g e | 5

Figure 3 : Context diagram

3.2. DFD - Level 0

Figure 4 : DFD - Level 0

4. Data Modelling (Entity Relationship Diagram - ERD)

P a g e | 7

Figure 5 : Entity Relationship Diagram - ERD P7. Explain how user and software requirements have been addressed

1. Wirefram design

1.1. Site map

P a g e | 8