Higher Nationals in Computing
Unit 9: Software Development Life Cycle
ASSIGNMENT 2
Assessor name: PHAN MINH TAM
Learner’s name: NGUYEN CHI BAO
ID: GCS200235
Class: GC0903A
Subject code: 1631
Assignment due: Assignment submitted:
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
SDLC full assignment 2, Study Guides, Projects, Research of Software Engineering
SDLC ass 2 of Greenwich the assignment include my project and wire, please change the wireframe so the report can be differences.
Typology: Study Guides, Projects, Research
2021/2022
1 / 30
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download SDLC full assignment 2 and more Study Guides, Projects, Research Software Engineering 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: NGUYEN CHI BAO
ID: GCS
Class: GC0903A
Subject code: 1631
Assignment due: Assignment submitted:
ASSIGNMENT 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name NGUYEN CHI BAO^ Student ID GCS Class GC0903A^ Assessor name Phan Minh Tam 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 Grading grid P5 P6 P7 M3 M4 M5 M6 D3 D
Assignment Brief 02 (RQF)
Higher National Certificate/Diploma in Business
Student Name/ID Number: NGUYEN CHI BAO/GCS 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. Note: ● The individual Assignment must be your own work, and not copied by or from another student.
● If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. ● Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to comply this requirement will result in a failed assignment. 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)
- Identify the stakeholders, their roles and interests in the case study. Review the requirement definition of the project. Clearly indicate which stakeholder(s) provide what requirements. Word limit: 150 – 200. Identify FRs and NFRs of Tune Source Project. Discuss the relationships between the FRs and NFRs. Word limit: 300 – 400 words.
- 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. Techniques: JAD, Interview, Observation, etc. Demonstrate how to collect requirements based on chosen technique. Word limit: 700 – 1000.
- 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)
Learning Outcomes and Assessment Criteria (Assignment 02): Learning Outcome Pass Merit Distinction LO3 Undertake a software development lifecycle 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. D3 Critically evaluate how the use of the function design paradigm in the software development lifecycle can improve software quality. LO4 Discuss the suitability of software behavioural design techniques 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. D4 Present justifications of how data driven software can improve the reliability and effectiveness of software.
Table of Contents
- Unit 9: Software Development Life Cycle ASSIGNMENT Table of Contents
- Assignment Brief 02 (RQF)
- Higher National Certificate/Diploma in Business
- P5 Undertake a software investigation to meet a business need.
- System requirements of the Tune Source project:
- Stakeholder of Tune Source Projects:
- 3.Identify and Discuss about FRs and NFRs of Tune Source Project:
- 3.1 Functional of Tune Source Project:
- 3.2 List of functional requirements for the Tune Source project:
- 3.3 Nonfunctional of Tune Source Project:
- 3.4 List of Non-functional requirements for the Tune Source project:
- 3.5 Relationships between the FRs and NFRs:
- 4.Discuss the technique(s) you would use to obtain the requirements.
- supporting documentation. P6. Use appropriate software analysis tools/techniques to carry out a software investigation and create
- Analysis the Tune Source Project
- 1.1 Use case Diagram:
- 1.2 Use Case specification for 2 Use cases:......................................................................................................
- 1.3 Context Diagram for the whole system:
- 1.4 Data Flow Diagram – Level 0 for the whole system:
- 1.5 ERD for the whole system:
- P7 Explain how user and software requirements have been addressed:
- 1.Design of Tune Source Project. - 1.1 Wireframe of Tune Source Project: - 1.2 Tune Source Architecture: - 1.3 Technical solution stack could be suitable to implement to the Tune Source project
P a g e | 2
- Stakeholder of Tune Source Projects: Name Position Roles Interest Carly Edwards, Assistant Vice President, John Margolis, Megan Taylor, and Phil Cooper Project Sponsor founders and investment of projects 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. Nguyen Chi Bao Project Manager Manage and optimize projects together with the team Get Paid!! Interest of working with Music Record. Successfully created the Tune Source project. User Customer Using Tune Source at a music digitals platform Listen to music with lots of music genre.
- Identify and Discuss about FRs and NFRs of Tune Source Project: 3.1 Functional of Tune Source Project: First, we must focus on the most basic requirements of the given project to ensure that all requirements and functionality of the system are best guaranteed so we will apply testing methods to the system with Tune Source Project and identify the functional of the project to achieve the completely requirements of the users. The basic system behavior is defined by functional requirements. They are essentially what the system does or does not do in response to inputs and can be understood of in terms of how the system responds to inputs. Calculations, data input, and business processes are frequently included in functional requirements, which specify if/then behavior. The features that allow the system to perform as planned are known as functional requirements. To put it another way, if the system's functional criteria aren't met, it won't work. Product features are referred to as functional requirements, and they are focused on the needs of the user: 3.2 List of functional requirements for the Tune Source project:
- Searching for music
- Listen to music.
- Purchase individual downloads at a fixed fee per download.
- Establish a customer subscription account.
- Purchase music download and gift cards. 3.3 Nonfunctional of Tune Source Project: The limits or requirements imposed on the system are known as non-functional requirements. They define the software's quality attribute. Scalability, maintainability, performance, portability, security,
P a g e | 3 and dependability are all examples of non-functional requirements. Non-Functional Requirements address critical software quality issues. If NFRs are not adequately addressed, the following outcomes may occur: •Users, clients, and developers are dissatisfied with the product. •Software that is inconsistent.
- Fixing the program that was prepared without considering NFRs resulted in a time and cost overrun. **3.4 List of Non-functional requirements for the Tune Source project:
- Physical Requirements:** You'll need a computer, tablet, or phone with a mouse and keyboard for input and a sound system for listening to use the system. 2) Availability Requirement: The program must be always available to any user with an internet connection. On a smartphone or tablet, tablet, or computer, an internet access or offline functionality is required. 3) Physical Requirements: You'll need a computer, tablet, or phone with a keyboard and mouse for input and an audio system for listening to use the system. 4) Requirement for Availability: Any user with an internet connection or offline functionality on a smartphone or tablet, tablet, or computer must be able to always access the app. 5) Security Requirement: A log-in system with a passwords protects the user's profile is required by the program. When the password is stored in the database, it is encrypted rather than saved in plain text. The system will shut down when have issue and SQL injected. 6) Data Requirement: The database design must be able to handle a high bunch of tracks and users without failing. To avoid any unpredicted application downtime, a strong database backup and restore plan should be prepared. 7) Accessibility Requirement: Responses to information viewing must appear on the screen in less than 3 seconds. 9000 users at a time and 12550 requests per minute should be possible using Quick Access. 3.5 Relationships between the FRs and NFRs: NFRs describe the entire event of using a business or software system, whereas FRs are solely concerned with a particular set of features. They're generally offered as unspoken requirements.
- User narratives, use cases, and function points can all be used to collect FRs. NFRs are frequently discovered. throughout the item Usability, often known as user experience (UX), is a term used to describe is a product- or software criteria, for illustration, which should be addressed even in product updates, upgrades, and additions. NFRs are observed across a product's/various app's components, including the front-end, backend, and databases. NFRs are commonly characterized as part of software Qa (SQA) process, which is valid.
- In conclusion, the FRs describe "How" while the NFRs clarify "What." Both are critical from the perspective of the end customer, and they should work together.
P a g e | **5 P6. Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation.
- Analysis the Tune Source Project 1 .1 Use case Diagram:** Figure 2. Use Case Diagram
P a g e | 6 Explanation of Use Case Diagram:
USER: .Customer (extends arrow >>> Normal Customer, Premium Customer) System: +Staff +Admin User Requirement:
- Listen to music sample
- Search for music in our digital music archive.
- Purchase individual downloads at a fixed fee per download.
- Purchase music download gift cards.
- register account
Admin
- customer manage
- Establish a customer subscription account permitting unlimited downloads for a monthly fee.
- Music manage ( include arrow >>> add music, update music, pop ups music gerne)
P a g e | 8 Use Case Name: Register for Account ID Use Case: RFA Priority: Must Have Actor(s): Users Description: As a user’s they want to access the website and listen to music Trigger: Users want to Sign in the Tune Source website. Pre-Condition(s):
- The users account have already created.
- User’s devices must connect to the internet for access the Tune Source website. •The users account have not create yet Normal Course 1.User access the Tune Source website. 2.User can choose between Sign Up or Sign In. 3.User Sign Up the Tune Source website.
- User Sign in the Tune Source website. 5.The system will be recording and verified user account.
- The system records the successful login operation in the datastore. Alternative Course(s): 2a. Users can choose to sign in with Facebook or Google account. 2a1. The system will pop ups the Google or Facebook sign in tabs. 3a. Users type in their Facebook account or Google. 4a. Facebook and Google successful verified and allow user to access Tune Source website Post-Condition(s): •System recording the users account are verified and allow user to access
- The system records the successful login operation in the datastore. Exceptions: 4c. The system validates the login failed and displays a message. 4c1.The user chooses to cancel the login. Use Case stops. 4c2. User chooses password reset command Use Case continues Use Case UC1- 3 4c3. User chooses the account lock command Use case continue UC1- 4
P a g e | 9 1 .3 Context Diagram for the whole system: Figure 3. Context Diagram 1 .4 Data Flow Diagram – Level 0 for the whole system: Figure 4.DFD Level 0 for the whole system
P a g e | 11 Relationship Explain:
- User can by many gifts cards
- One users can choose optional about the Package deals they want to download music with monthly fee +One users can create many playlists and in play list got many songs. +Many songs can have many artists and many difference Music Genre. +Many songs can be in one playlist. P7 Explain how user and software requirements have been addressed: 1 .Design of Tune Source Project. 1.1 Wireframe of Tune Source Project: Figure 6. Tune Source Front Page
P a g e | 12 Figure 7. Sign Up Tune Source