btec level 5 hnd diploma in computing unit 09 software development life cycle

The Joint Application Development JAD process in the Tune Source project...172.2.. Identify the stakeholders, their roles and interests in the case study.The Tuna Source project was star

ASSIGNMENT 02 FRONT SHEET

❒Summative Feedback: ❒Resubmission Feedback:

Internal Verifier’s Comments:

Signature & Date:

Table of Contents

Chapter 1: Undertake a software development lifecycle (LO3) 6

A Undertake a software investigation to meet a business need (P5) 6

1 Identify the stakeholders, their roles and interests in the case study 6

1.1 Stakeholders with roles and interests in the project 7

1.2 Stakeholders with their requirements 9

1.3 Identify FRs and NFRs of the Tune Source Project 9

1.3.1 Functional requirements 10

1.3.2 Nonfunctional requirements 11

1.4 Discuss the relationships between the FRs and NFRs 14

2 Discuss the technique(s) you would use to obtain the requirements 17

2.1 The Joint Application Development (JAD) process in the Tune Source project 17

2.2 The Interview Technique in the Tune Source project 19

2.3 Observation in the Tune Source project 20

B Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation (P6) 21

1 Overall system uses case diagram 21

2 Use case specification for 2 Use cases 23

3 Context Diagram for the whole system 25

4 Data Flow Diagram – Level 0 for the whole system 26

5 Entity Relationship Diagram (ERD) for the whole system 27

Chapter 2: Discuss the suitability of software behavioral design techniques (LO4) 29

C Explain how user and software requirements have been addressed (P7) 29

1 Wireframe and Mockup 29

2 Which architecture is suitable for the project? 31

3 Which technical solution stack could be suitable to implement the project? 32

References 35

Figure 1: Stakeholders 7

Figure 2: Relationships between the FRs and NFRs 14

Figure 3: JAD process phases 18

Figure 4: Use case diagram 22

Figure 5: Buy Use case 23

Figure 6: Search Use case 24

Figure 7: Register Use case 25

Figure 8: Context diagram 28

Figure 9: Data flow diagram-level 0 30

Figure 10: ERD of the system 31

Figure 11: Main screen 33

Figure 12: Featured product 34

Figure 13: Main screen 35

Figure 14: Login screen 36

Figure 15: Cart screen 37

Figure 16: Mock-up of Tune Source Web 39

Figure 17: Microservice architecture 40

Figure 18: MERN stack 41

Chapter 1: Undertake a software development lifecycle (LO3)

A Undertake a software investigation to meet a business need (P5)

1 Identify the stakeholders, their roles and interests in the case study

The Tuna Source project was started with the intention of developing a system that enables the business to sell CDs online or through kiosks in its stores rather than through traditional merchants By enabling current customers to purchase specific digital music tracks and by luring new consumers interested in its distinctive collection of rare and hard-to-find music, this technology willassist the business in growing its income Additionally, if buyers opt to purchase the complete CD in a store or online after downloading one or two tracks, the company anticipates an increase in cross- selling

Due to the organization's goals listed above, the Tune Source project must adhere to the following standards:

• The system allows customers to register an account

• The system allows customers to log in to the system by an account

• The system allows customers to buy and download digital music songs that are rare and hard to find in the system

• The system allows customers to get subscriptions to the company’s download services

• The system allows customers to buy several tracks of a CD, then customers can continue to buy entire tracks of a CD

• The system allows customers to purchase music download gift cards

1.1 Stakeholders with roles and interests in the project

Stakeholders are people who have an interest in the project's outcomes and will provide the company with their opinions and suggestions in order to aid it in achieving its strategic objectives Typically, stakeholders will provide money, people, and relevant documentation to help the project succeed The following are some of the stakeholders in the Tuna Source project:

Figure 1: Stakeholders

• Customer: In order to assist define the functionality of the system, customers in the Tuna Source project are responsible for submitting their requirements and demands Additionally, they must offer input throughout the testing process to guarantee that the system runs properly in a real context or to raise user standards in cases where the system's capabilities are restricted.

back afterwards The owner, creditor, and shareholder will thus often be the investor

testers, technical managers, and designers are typically members of a development team As a result, project criteriaincluding the system's UX/UI, functionalities, and performance must be addressed by the development team

• Government: To protect the interests of stakeholders, the government will enact regulations that the project must abideby

• The third partner: will help with the project by offering methods, equipment, and software for creating the system, such as

a payment system

Before implementing a system, a paper containing the requirements must be created that outlines the functions and workings of the software It also outlines the characteristics the product must possess in order to meet the demands of all stakeholders

customer, business analyst Look through the system's digital music archives.

download

and download tracks using an account

• The system will let users sign in using an account.

• The system will let users subscribe for monthly fees that allow for limitless downloading

• The technology will let consumers look up the CDs they wish to purchase

• The device will let users hear music samples

• The technology will let consumers purchase and download individual CD songs or complete CDs

• The system would enable users to buy gift cards for music downloads

• The system will provide the user the option of selecting alternative payment methods

Information-oriented requirements:

1.3.2 Nonfunctional requirements

A group of business analysts must establish nonfunctional requirements in order for the system to perform properly and to prevent potentially harmful problems when it is deployed in the real world Determining the system's non-functional needs during the design anddevelopment phases is crucial

Operational requirements:

• The system is compatible with a wide range of gadgets, including laptops, cellphones, and tablets

• To create the bill, the system may export data into an Excel file

• The system has the ability to examine and add data to the database

Performance requirements:

Cultural and Political requirements:

• The users' data must be strictly protected and according to the nation's data privacy regulation

Security requirements:

• Authentication will be needed of all users logging in from the outside

• For information security, data will be encrypted when it is sent from the user's computer to the system

• Before being stored in the system, all submitted files will be scanned for viruses

Figure 4: Use case diagram

Figure 5: Buy Use case

Figure 6: Search Use case

Figure 7: Register Use case

2 Use case specification for 2 Use cases

• Use case for the register use case

Input informationSave

The user chooses to cancel the login Use Case stops

• Use case for search use case

Customer's device must have a wi-fi or internet connection when searching

The system switches to the song that the customer searches for

The system displays all the information of the song

The user chooses to cancel the searching Use Case stops

3 Context Diagram for the whole system

I'll draw a context diagram to better explain the system to stakeholders The data flow of the system for purchasing songs

to and from external entities is shown in the context diagram, which depicts the whole business process as just oneprocess

Figure 8: Context diagram

4 Data Flow Diagram – Level 0 for the whole system

Figure 9: Data flow diagram-level 0

5 Entity Relationship Diagram (ERD) for the whole system

An Entity-Relationship (ER) Diagram is a type of flowchart that demonstrates the connections among "entities" such as individuals, things, or concepts inside a system To construct or repair relational databases, ER Diagrams are most often used in the disciplines

of software engineering, business information systems, education, and research They use a predetermined set of symbols to describe the interconnectedness of entities, connections, and their properties and are also known as ERDs or ER Models

Rectangles, diamonds, ovals, and connecting lines are some of these symbols They reflect the grammatical structure by having verbs for links and nouns for entities

Figure 10: ERD of the system

Chapter 2: Discuss the suitability of software behavioral design techniques (LO4)

C Explain how user and software requirements have been addressed (P7)

1 Wireframe and Mockup

• Wireframe

A wireframe is a two-dimensional representation of a page's user interface that focuses on the placement and hierarchy of material, the features that are offered, and the desired behavior For these reasons, style, color, or images are often absent from wireframes Additionally, wireframes aid in defining connections across the various website layouts

Wireframes of Tune Source Web

Figure 11: Main screen

Figure 12: Featured product

Figure 13: Main screen

Figure 14: Login screen

Figure 15: Cart screen

Mock-up of Tune Source Web

Figure 16: Mock-up of Tune Source Web

2 Which architecture is suitable for the project?

It's crucial to select the system's architectural design before you begin construction We understand that the Tune Source project involves building and deploying each component independently because the system is rather large and complicated Therefore, we will decide to build the system using a microservices design

Microservice architecture, sometimes referred to as "microservices," is a unique method of developing software systems that seeks

to focus on developing single-function modules with well-defined interfaces and behaviors The entire system may be affected if the system with the other architectures changes Microservices with a feature that is as modular as possible will be the answer to this problem In its simplest form, they contribute to the development of an application as a collection of little services, each of which operates in its own process and is independently deployable

Figure 17: Microservice architecture

Since the Tune Source project is large, using the microservice design would allow us to complete it faster than using a monolitharchitecture by breaking it up into smaller services and distributing them among several firm developers.

3 Which technical solution stack could be suitable to implement the project?

The team constructing the CD selling system must first decide which architecture is appropriate for the system before analyzing thedemands of stakeholders and choosing the best technological solution stack The project development team for the Regulated Source project made the decision to use the MERN stack to construct the system after carefully considering the necessary system features The rationale for their selection of the MERN stack is provided below

Figure 18: MERN stack

A group of technologies known as the MERN stack make it possible to construct applications more quickly Most

JavaScript-only app development uses the MERN stack This is true since all four of the technological stack's based MongoDB, ExpressJS, ReactJS, and NodeJS—are present These four powerful technologies each provide a

elements—JS-comprehensive working environment for developers and are crucial to the development of web applications

MERN stack can benefit the Tune Source project in the following ways:

• No context switching: JavaScript is used exclusively throughout the whole program to write client-side and server-side code, eliminating the requirement for context switching and resulting in web programs that work well

• Model-View-Controller (MVC) model: The MERN stack's Model-View- Controller architecture is a crucial benefit since itmakes it simple for developers to build the system

• Flexibility: The MERN tech stack offers the benefit of allowing the tech stack's components to be open source, so there won't be any licensing issues Due to the prominence of the tech stack, we have several options for constructing the CS selling system

• Code Maintenance: The team development can easily maintain the system's code and address bugs using the MERN stack development, making it a cost-effective choice Powerful testing tools are also included

• Take use of MongoDB: MongoDB provides high speed and data volume scalability It provides solid stability as well as sufficient flexibility for team development across several data centers