Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

ASM2 - 1631 Software Development Life Cycles, Assignments of Information Systems

FPT University (FPTU)Information Systems

1631 Software Development Life Cycles Pass

Typology: Assignments

2022/2023

Uploaded on 03/24/2023

andrew-2709
andrew-2709 🇻🇳

4.8

(20)

33 documents

1 / 31

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Higher Nationals in Computing
Unit 9: Software Development Life Cycle
ASSIGNMENT 2
Assessor name: PHAN MINH TAM
Learner’s name:
ID:
Class:
Subject code: 1631
Assignment due: Assignment submitted:
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f

Partial preview of the text

Download ASM2 - 1631 Software Development Life Cycles and more Assignments Information Systems 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:

ID:

Class:

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 Student ID Class 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: 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: LO 3 Undertake a software development lifecycle. LO 4 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)

  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 – 40 0 words.
  2. 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.
  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)

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

  • P5 Undertake a software investigation to meet a business need.
    • 1 Business need analysis:
      1. Stackeholders and their roles in Tune Source Project:
      1. FRs and NFRs of the Tune Source Project:
      • 3.1. Functional requirement:
      • 3.2. Non-functional requirement:
  • create supporting documentation. P6 Use appropriate software analysis tools/techniques to carry out a software investigation and
    • 1 Software requirements modeling:
      1. Use Case specification:
      1. Process modeling:
      • 3.1. Context Diagram:
      • 3.2. DFD - Level 0:
      1. Data Modeling:
  • P7 Explain how user and software requirements have been addressed.
    • 1 Wireframe design:...................................................................................................................
      • 1.1. site map:...........................................................................................................................
      • 1.2. Home page:
      • 1.3. Register page:
      • 1.4. Login page:
      • 1.5. Order page:.......................................................................................................................
      • 1.6. Search page:
      • 1.7. Detail page:
      • 1.8. Admin panel page:
      1. System architecture design:
      1. Technical solution stack:
    • REFERENCES

P a g e | 2 Name of stakeholder Roles in Tune Source Target Carly Edwards Project Sponsor, Assistant Vice President, Marketing.

  • Feature of Tune Source.
  • The motto of the company. John Margolis Founder - The current problem of the System.
  • Available feature and feature goals. Phil Cooper Founder - Music copyright issues.
  • The quality of each song. Megan Taylor Founder - Budget.
  • Sales from the sale of CDs and the downloading of music through the internet.
3. FRs and NFRs of the Tune Source Project:

3.1. Functional requirement: Customers frequently communicate their requirements to the "Tune Source" project team through functional requirements. The "Tune Source" project team uses functional requirements to stay on track. A functional requirement, in other words, describes how a system function behaves when certain needs are met. Tune Source's requirements and website design must meet the following standards: ● 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. 3.2. Non-functional requirement:

  • “Tune Source” provides a mobile-friendly platform to help customers listen to music easier.

P a g e | 3

  • A simple and good clear and accurate website “Tune Source” that makes it easy for customers to use.
  • “Tune Source” make sure the site works and meets the requirements from simple to difficult to help customers find the songs they are looking for.
  • Each request should be handled in less than ten seconds. The site should load in 3 seconds when there are more than 10,000 concurrent users.
  • The material in the "Tune Source" system must be constantly updated with new hot tunes. The page load, search, and download speeds must all be flawless.
  • Avoid server problems while paying third parties. Keep consumer information safe.
  • Security of customer information, payment, and transaction history.
  • The payment procedure with a third party must be quick after clicking the "Payment" button.
  • The system will capture the user's location information based on cookies and GPS, thereby avoiding the display of songs forbidden in that region/country altogether.
  • Use only words and symbols that are not offensive to anyone on the globe. P6 Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation.
1. Software requirements modeling:

P a g e | 5

2. Use Case specification:

2.1. Use case 1: Use case name: Purchase gift cards ID: UC- 01 Priority: High Actor: Customer Description: Purchase gift cards in Tune Source. Trigger: User wants to buy gift card from system. Type:  External  Temporal Preconditions:

  1. The user's device is already connected to the internet when logging in.
  2. User accounts already created.
  3. User account has been authorized. Normal Course: 1.0 Request to buy gift cards in the Tune Source Project.
  4. The system asks the user to log in.
  5. Login information confirmation system.
  6. The system displays the number of gift cards.
  7. The system displays the types of gift cards that users want.
  8. Users choose the number of gift cards they want.
  9. The system asks the user to reconfirm the number of gift cards.
  10. The system sends a notification about the user's request. Post-Conditions:
  11. Request a gift card stored in the Tune Source system.
  12. User successfully logged into the application.

P a g e | 6

  1. User can add products to the cart.
  2. Gift card already paid. Exceptions:
  3. The system sends the message "Gift card has expired".
  4. The system says the account doesn't exist.
  5. Failed transaction notification system.
  6. Normal Course Restart System.
  7. The system asks if the user wants to get another gift card or quit. 2. 2. Use case 2 : Use case name: Register ID: UC- 02 Priority: High Actor: Customer Description: As a user, I want to register the app to use the service. Trigger: The user wants to register an account in the application. Type:  External  Temporal Preconditions:
  8. User accepts the terms of service.
  9. User's device is already connected to the Internet when logging in. Normal Course: 1.1 Tune Source project registration requirements.
  10. System requires the user to enter an id and password.
  11. User confirms the information.
  12. Customer data is updated by the system.
  13. User selects the type of account to register.
  14. The system asks the user to re-confirm the account.
  15. The system sends a notification about the user's request. Post-Conditions:

P a g e | 8 the email address specified during login.

  1. Customers go to the homepage of the digital "Source Tune" music site to make sure that their account login is success. Post-Conditions:
  2. If all goes well, the "Customer" account will be logged in.
  3. The created user is granted the appropriate permissions.
  4. Four-digit customer code and default password granted to the user.
  5. If an error occurs, the Customer will receive an error message. Exceptions:
  6. Customers lost or cannot access their email accounts.
  7. The customer provides incorrect information.
  8. The customer did not confirm that he received the successful login confirmation email.
  9. Did not receive a confirmation email. 2. 4. Use case 4 : Use case name: Purchase individual download ID: UC- 04 Priority: High Actor: Customer Description: Allows any "Tune Source" user to create an account buy songs on the website. Trigger: User wants to buy songs from system Type:  External  Temporal Preconditions:
  10. The user must create a "Customer" account on the "Tune Source" system.
  11. Customers must have a bank account to make purchases. Normal Course: 1.3. Customers look for songs they want to buy.

P a g e | 9

  1. The consumer will evaluate the quality of the song based on the a number of customers, reviews, and price.
  2. The customer will select the checkout page for the song they desire to purchase.
  3. Customers will be asked to supply some basic information in order to complete their transactions.
  4. From "Tune Source," the consumer selects an online payment option.
  5. The customer confirms that the information is valid and that the the form is completed by clicking the button.
  6. To make a payment, the customer taps the payment button.
  7. The bank issues and validates an OTP to the consumer.
  8. The customer double-checks the invoice after a successful transaction. Post-Conditions:
  9. After successfully logging in as "Customer", the "Customer" account allows the purchase of different songs as well as bank payments.
  10. Tune Source will enlist the help of a third party for recording transaction data between the user and the "Regulatory Source" payment mechanism. Exceptions:
  11. Customers who do not have a Tune Source account or have lost their login information.
  12. Customers do not have a bank account or lose their passwords.
  13. The customer's bank account does not have enough funds to pay for the order.
  14. "Tune Source" does not accept customer payment methods.
  15. There has been no feedback on the bank's OPT code-sending mechanism.

P a g e | 11 Figure 3: DFD Level 0 A data-flow diagram (DFD) shows the direction of data flow within a system or process (typically an information system). Along with the process itself, it also shows the inputs and outputs for each entity. There are no loops, control flows, or decision rules in a data-flow diagram. You can represent specific operations based on data using a flowchart. The connection between the system and the consumer for Tune Source's digital music system is shown in the Data Flow Diagram - Level 0 below.

4. Data Modeling:

P a g e | 12 Figure 4 : ERD

  • The customer will have a one-to-many relationship with the order because there may be one or several bills for the customer.
  • Customers will have a one-to-many relationship with gift cards since users can order one or more gift cards.
  • The CD will have a one-to-many relationship with order details because the CD can be purchased by one or more people.
  • Category will have a one-to-many relationship with the CD because each genre can have one or more songs. P7 Explain how user and software requirements have been addressed.