Tune Source Project: SDLC, Stakeholder and Requirement Analysis Report

This report provides a detailed analysis of the System Development Life Cycle (SDLC) applied to the Tune Source project, a hypothetical initiative in the music industry. It begins with an introduction to SDLC and its importance in managing information system development. The report identifies and categorizes stakeholders, including internal (business analysts, project managers, programmers) and external stakeholders (Tune Source owners, sponsors, customers, and users), highlighting their roles and interests. It then defines the functional and non-functional requirements of the Tune Source project, such as online music searching, purchasing, and subscription services, alongside considerations for data privacy and download speed. The report explores the JAD (Joint Application Development) methodology as a technique for requirement elicitation, outlining its phases and benefits in improving collaboration and reducing development time. Finally, the report examines how these elements contribute to the successful development and implementation of the Tune Source project.

INTRODUCTION
When developing an information system, there should be a strategy in place to manage and control the
project from start to finish to meet the projected goals and objectives. We need a project management tool to
make the analysis, design, and other development activities easier to handle. A set of guidelines or a
structure for coordinating the project's work flow the framework in place One that outlines all tasks required
to build, launch, and manage an information system is required. System. Analysis, design, programming,
testing, and evaluation should all be included in the framework. We'll keep the system running until we're
ready to launch and implement it. System is the name of the framework Life Cycle of Development
(SDLC).
Although SDLC necessitates many different activities or processes, there are a few fundamental processes
that must be followed to build and develop the project's result, the system. The following are the main steps
in creating a new system:
➢ Determine the issues or requirements and receive permission to proceed.
➢ Plan and monitor the project in terms of what to do, how to accomplish it, and who will execute it.
➢ Identify and comprehend the specifics of the issues or requirements ➢ Create the system components
that will fix the issues.
➢ Complete system tests and deploy the solution after building, testing, and integrating system
components
P5. Undertake software investigation to meet a business need
I. Requirement Definition
1. Stakeholder
Stakeholders are individuals who have a vested interest in the project's success. They are not directly
involved in the production of a product, but they may contribute to the development process in a
variety of ways.
Through a constant inspection and adaption process, an agile project evolves as it advances.
Stakeholders must actively participate in the development process for this method to be successful.
Rather to merely developing plans and ensuring that they are implemented, they must shape a project
and the output it produces as research progresses.
For an agile project, having a highly engaged project group is critical. A flexible ecosystem of
projects is formed by the production team and other stakeholders. They are those who have an impact
on the project or are affected by it.
There are some of examples:
➢ Investors: They are the company's original and most important owners because they invested
in it and expect a reasonable return on their investment.

➢ Creditors: Creditors are the banks or significant corporations that lend money to the
corporation. Among the creditors could be retail buyers who bought the company's
bankruptcy filings and lending instruments.
➢ Employees: Employees are the company's most vital partners. They are the ones in charge of
making choices and running the business. They devote the time, effort, and expertise
necessary to run the businesses for which they are paid.
➢ Customers: The customer is an important related party to the company since he or she does
business with it. Businesses are prone to spotting possibilities and analyzing product demand.
They design and manufacture items that clients require and that address their difficulties on a
regular basis.
2. Identify stakeholders for Tune Source project
According to the Tune Source scenario, it has a relationship with the music industry: John Margolis,
Megan Taylor, and Phil Cooper. John and Phil collaborated to open several brick-and-mortar shops
in southern Hard-to-find and classical music, rock, country, and folk albums from California. Tune
root is now collaborating with an internet consultancy firm (ISP). Carly Edwards, Assistant Vice
President, Marketing, is the project's sponsor. Management: To complete the prototype, my
organization is currently collaborating with Tune Source. I'm the project manager for ABC. Users
who stream music from the Tune Source website and those who use shop kiosks are all considered
device users.
2.1. Internal Stakeholders
Internal Stakeholders are organizations, entities, or groups with an interest in the operation of the
corporation. Regardless of the organization's interests, you will have an impact on and be affected by
the entity's success or failure. The Internal Stakeholders' second term is Primary Stakeholders.
Business Analysists
The business analyst is the link between the project's customers and the technical team of software
developers. The project's business analyst met with the project's customers, analyzed the program,
developed specifications, reported, explained the project to the technical team, and collaborated with
them throughout the development process.
A business analysists job description typically includes:
• Creating a complete business analysis, describing issues, opportunities, and solutions for a business
• Budgeting and forecasting
• Planning and monitoring
• Financial modeling
• Variance Analysis
• Pricing
• Reporting

• Defining business requirements and reporting them back to stakeholders
The business analyst will do the following tasks during the SDLC:
• Assistance with business cases
• Conduct high-level feasibility studies
• Gather requirements
• Create and/or analyze test cases for schools
• Managing change requests
• Monitoring requirements during implementation
• Project scope management
• Approval, integration, and deployment are all steps in the process.
System Analysis
Create an internet music system using the following components:
• Connects to an internet music distribution system.
• System performance and data models
• User interface and process models
• The user's experience
Project Manager
To assure quality, timing, and budget compliance, oversee the full Tune Source software
development project.
Programmer
As a team directly execute software such as code config functions and database
2.2. External Stakeholders
External stakeholders are individuals who are not part of the management team but are influenced by
the company's work in some way. The market atmosphere is determined by outside parties.
Secondary Stakeholders is another name for them. They are the ones who consume the financial data
of the company to learn about its efficiency, profitability, and liquidity. External stakeholders in the
Tune Source software development project include:

Tune Source’s Owner
Tune Source is based in Southern California. Tune Source was founded by John Margolis, Megan
Taylor, and Phil Cooper, all of whom are involved in the music industry. The network chief is the
person in charge of overseeing all operations. They oversee all system work, employee actions, and
other system-related operations. They oversee installing and maintaining the workstations. All
customer, employee, product, and service records must be accessed through a secure login system.
Sponsor
The sponsor for Tune Source Project is Carly Edwards
Users
Audience: As the whole public. This episode is completely indistinguishable from the others. The
intended customer group for the product is referred to as the target audience. This episode is a spin-
off from the initial large-audience program, and it features small groups:
Customer is the person who will purchase the product.
Knowing about the product and persuading others to buy it KOL (Key Opinion Leader) Someone
who knows about a product but has not yet acted.
Customer: Customers are the most important stakeholders who use network services. They'll require
a separate login screen to choose among Tune Source's offerings. They require a demonstration of
the most recent items and services that Tuning Source is implementing. They must also challenge
and provide input on any issues that arise.
User = Customer: The buyer, often known as the User, is the one who pays for the product. There are
two types of customers:
Trade Customers Use the Product Final Customer = End User = Consumer Resale Products (Trade)
End Users: A consumer is also known as a product user or an end user. Users of tangible items are
referred to as consumers. End user: for users of intangible products
3. Requirement
As you can see (Dennis, 2014) A need is a single documented physical or functional necessity that a
design, product, or process is intended to meet. In engineering design, it's usually used in an
appropriate sense, such as in systems engineering, software engineering, or enterprise engineering.
It's a broad term that can refer to any required (or sometimes desirable) function, attribute, capability,
trait, or quality of a system for it to have value and utility for a customer, business, internal user, or
other stakeholders. A requirement specification or requirement "spec" (often imprecisely referred to
as "the" spec/specs, but there are literally different types of specifications) refers to a specific, highly
objective/clear (and often quantitative) requirement (or sometimes, set of requirements) that must be
satisfied by a cloth, design, product, or service.

4. The requirement definition of the project
We'll work with stakeholders to create the specs and incorporate some of the project's core roles.
Let's begin by creating an account, then looking for and listening to music. Submitting a purchase
order. Customers can also access invoices and modify orders directly on the invoice. before making a
purchase. You can either buy the song or subscribe for a monthly fee and get unlimited downloads
fee. At any point throughout the update, the consumer might choose to restart it. Information on
Customers' identities would be kept hidden.
5. Functional for Tune Source o Customers can use the internet or retail kiosks to look for and purchase
digital music downloads. The optical media library can be used to search for music. o Play the song
you've selected. o Individual downloads can be purchased for a set price per copy. o Create a
consumer registration account with limitless downloads and subscription fees. o Downloadable tunes
and gifts are available for purchase.
o Music options will be personalized to the customer based on previous purchases on
subsequent visits to the website.
o Customers may be notified about special CD discounts available at the daily Tune Source
web site or in a Tune Source shop based on their preferences.
6. Nonfunction for Tune Source
➢ Why If a customer's music transfer fails, the consumer has the option of restarting it or being
diverted to a backup. connection to download
➢ All customer information will be kept private.
➢ The download speed will be tracked and kept at a fair (not too slow) pace.
➢ All payment information will be kept confidential.
➢ A digital music archive would be created to make music searching easier.
II. Requirement elicitation techniques
1. JAD (Joint Application Development)
1.1. Definition
JAD (Joint Application Development) is a way of involving the client or end user in the design
and development of an application through a series of collaborative workshops known as JAD
sessions. JAD is a software development methodology that improves stakeholder collaboration
during software development cycles. For domains of dynamic software development, its life
cycle has been embraced. While developing a new information system for any organization or
enterprise, it collects business and system needs.

1.2. Phases of JAD Model
Since you have become familiar with the JAD concept, it is time to know about its phases and
how the model’s design and development approach work:
• Defining Specific Objectives: The facilitator, in collaboration with stakeholders, defines all of
the goals as well as a list of things, which are then provided to other developers and participants
to comprehend as well as a review. The extent of the proposed system, as well as its potential, are
all included in this purpose. Result required technological specifications, and so on.
• Session preparation: The facilitator is exclusively responsible for this preparation, which
includes gathering all required information. Data is gathered in advance and forwarded to other
members. Work has been done to improve understanding been carried out to learn more about the
device's requirements and to obtain all the necessary information about the implementation.
• Session Conduct: The facilitator oversees identifying the issues that need to be resolved for
the system to be error-free. The facilitator will take part in this discussion but will have no choice
in what material is shared.
• Documentation: After the product has been established, reports and written papers are
delivered to the meeting so that it may be acknowledged by stakeholders and customers.
1.3. Benefits of using JAD Model
The following are some of the advantages of employing the JAD Model:
• Improved delivery time: The JAD model reduces the time it takes to produce a product. Some
classical models are more efficient
• Cost-cutting: Effective interaction with company executives and stakeholders. Specifications
and facts will make it easier to implement the program, resulting in lower costs will be required
during the installation period.
• A better comprehension: Because all the criteria are examined by company managers, there is
a better understanding. Careful selection of engineers and team leaders who can effectively
communicate with one another effectively aids in gaining a better understanding of product
development.
• Improved Quality: Because all of the project's key decision-makers and stakeholders are
involved in its creation, there is a lower risk of error, resulting in a higher and more reliable
product.
1.4. When to use JAD? Project Types
• New systems
• Enhancements to existing systems
• System conversions

• Purchase of a system Project Characteristics
However, not every project is a good fit for JAD. At least some of the following features are
present in a suitable project:
• Involves many users with responsibilities that extend beyond standard department or division
lines.
• Is a first-time project for the organization • Has a troublesome project history or relationship
between the systems and user organizations • Is deemed vital to the organization's future
success
• Involves willing users
• Is a first-time project for the organization
While the attributes listed above characterize a solid JAD candidate project, not all of them
should be present in your initial JAD projects. It is possible to take on more complex projects as the
development team and the customer become more familiar with the JAD approach. 1.5. Step to step
use JAD Planning
• Choose an executive sponsor.
• Determine why the system is required.
• Assign team members to the definition phase.
• Establish the session's parameters.
Preparation
• Arrange for design sessions.
• Provide participants in the design session with orientation and training.
• Gather the necessary materials, as well as the room and software aids.
• Create your own agenda for the design session.
• Hold a kickoff meeting.
Design Sessions
• Examine the scope, objectives, and definition paper for the project.
• Define the requirements for data, processes, and systems.
• Locate the system's interfaces.
• Create a working prototype.
• Keep track of decisions, issues, assumptions, and terminology definitions.
• Assign someone to deal with all problems.
Finalization
• Finish all the design documentation.
• Approve the design documents by signing them.
• Give an executive sponsor a presentation.

• Show off the prototype.
• Obtain the consent of the executive sponsor before proceeding.
• Assess the JAD procedure.
2. Interview
As you can see (Dennis, 2016) The interview is the most common approach for eliciting
prerequisites. All things considered; it is natural to ask someone if you need to know something.
When all is said and done, interviews are conducted one on one (one questioner and one
interviewee), however due to time constraints, a few people may be interviewed at the same time.
The meeting procedure is divided into five steps: selecting interviewees, planning inquiry questions,
preparing for the meeting, leading the meeting, and post-meeting development. The interviews are
separated into two categories:
➢ A private interview is one in which the interviewer prepares questions ahead of time and tries
to elicit responses from stakeholders
➢ An open-ended interview is one in which the interviewer does not need to plan any questions
ahead of time and the questions are completely random during the interview.
Advantages
• Rich data collection
• Gather information for survey design or other usage activities
• Getting a holistic view Disadvantages
• Collect data from large samples or multiple people
• Collecting data very quickly is not feasible
3. Observation
As you can see (Dennis, 2014) Observation, or the act of watching forms being executed, could be a
useful tool for incorporating new information into the existing structure. Instead of tuning in to
others' depictions of a situation in interviews or JAD sessions, perception allows the investigator to
see the reality of the situation. Several inquiries have revealed that many supervisors are completely
unaware of how they operate and how they allocate their time. Perception may be a useful tool for
verifying the validity of data gathered from other sources, such as interviews and surveys.
This technique is often used along with other required techniques such as interviewing and document
analysis.
Advantages
• Prerequisite’s tech tool that is extremely authentic • The primary purpose of observations is
to confirm
• and check requests.

Disadvantages
• Because of the travel prices, it was very expensive.
• Analyzing can take some time.
P6. Use appropriate software analysis tools/techniques to carry out a software investigation and create
supporting documentation
1. DFD
1.1. Definition
Data flow diagrams are graphical representations of data flow within a business information
system. DFD is a framework for transporting data from input to file storage and providing reports
that outlines the procedures required.
Data flow diagrams can be divided into logical and physical categories. The logical data flow
diagram depicts how data flows through a system to achieve a certain business goal. The data
flow diagram depicts the realization of the conceptual data flow.
Below DFD symbols:
Notation:
• There should be at least one input and one output for each procedure.
• There should be at least one data flow in and out for each data store.
• The data saved in a system must go through a process.
• In a DFD, every process or data store must be linked to another process or data store.
Levels DFD
DFDs (data flow diagrams) can be used in software engineering to illustrate systems at various
degrees of abstraction. DFDs at higher levels are divided into lower layers, allowing more

information and functional elements to be hacked. In DFD, levels are numbered 0, 1, 2, or higher. In
this data flow diagram, there are primarily three levels: 0-level DFD, 1-level DFD, and 2-level DFD.
It's meant to be an abstraction perspective, with the system depicted as a single process with external
entities. It depicts the complete system as a single bubble with incoming/outgoing arrows indicating
input and output data.
The context diagram is split into numerous bubbles/processes in 1-level DFD. At this level, we
highlight the system's major functions and break down the 0-level DFD's high-level process into
subprocesses.

2-level DFD goes one step deeper into parts of 1-level DFD. It can be used to plan or record the
specific/necessary detail about the system’s functioning.
2. DFD level 0 Tune Source Project
The following are some of the primary features of Tune Source software:
• Look for music
• Download music and pay a fee
• Get new training music updates
The development team has identified the source of engagement with clients as online search and
purchase, as well as music suggestion, according to a survey by Tune Source's marketing team. The
team used this information to create DFD level 0 to display software.
Evaluate
The context diagram was the starting point for the software development team. Non-functional
requirements and non-functional requirements from clients are read and analyzed. The team then
discovered three of the most common consumer interaction strategies. Search for music, download it
for a price, and receive fresh training music updates. DFD was produced by the team and includes
data for both internal and external entities.
Below is DFD level 0 of Tune Source online music system:

As previously stated, Tune Source's marketing team conducted a poll and created a description of the
customer-Tune Source relationship:
3. ERD
The Entity Relationship Diagram, often known as the ERD, ER Diagram, or ER model, is a sort of
database architecture structure diagram. The key entities within the system scope, as well as the
interrelationships among these entities, are visualized using different symbols and connectors in an
ERD. That is why we need ERD for Tune Source Software developers to grasp how to upgrade,
debug, and maintain their software.

The database for Tune Source can be obtained here. The following tables are included: Gift Code,
Customer, Order, Order Detail, Object, Type, and Admin. The Gift Code table is used to keep track
of the gift codes sent out to customers. Customer records are kept in a table called the customer table.
The order table contains information about customer orders. The order detail table keeps track of
customer information. A product table is used to keep track of song information. Create a table
category to contain information about the album type.
4. Flowchart
4.1. Search in web

Explanation: For Tune Source web search function. When customers come to the website, they will
type the keyword to search in the search box to start searching for the song. The system will filter
songs according to 3 criteria: name, singers, and type song. When the customer has selected the filter
criteria, the search results appear. If it matches the song the customer is searching for, the function
ends. But if not, customers will start with typing a new keyword to continue searching
4.2. Purchase

Explanation: Customers search for a suitable tune, their wanted, using the Tune Source Web's
Purchase function. They will then proceed to purchase the song to download it. If the customer does
not have an account, the system will prompt them to create one, after which they must complete the
relevant registration requirements before moving on to the next step. If the customer already has an
account, the payment method will be used. The system will then return the payment information to
the consumer and ask them to confirm whether they want to accept the payment. If the consumer
agrees, the system will begin downloading; otherwise, the system will display an error message and
redirect the user to the payment page.
5. Analysis function of Tune Source
There are some functions that Tune Source need have and should improve in the future:
Download music, listening to music, searching music, Registration, Login, download gift card,
Subscriptions, Buy CD.
6. Tool/Techniques to carry out a software investigation
6.1. Use case

7. Supporting documentation
Software documentation is written text or an illustration that comes with or is integrated in the source
code of a computer program. It either describes how it works or how to utilize it, and it might mean
different things to different people depending on their positions. Support documentation will be
based on Tune Source and will include requirements, architecture/design.

Technique, End user and marketing.

Requirement of Tune Source project:
Tune Source Company Content
Business value $650,000 in deals with individual music download
$850,000 in deals from client memberships
$105,000 in extra in-store or site CD deals
$123,000 in deals with music download gift
vouchers
Business requirement In our advanced music file, look for music.
Pay attention to music exams.
Purchase individual downloads at a fixed price per
download.
Create a client membership account that allows you
to download as much as you like for a monthly fee.
Purchase music download gift cards.
Project’s cost Approximately 30% of total value: $600,000.
P7. Explain how user and software requirements have been addressed.
1. Wireframe
A wireframe website, also known as a schematic page or computer diagram, is a visual
representation of a website's architecture. Wireframes are used to organize elements so that they can
better serve a given goal. The aim is usually revealed through a corporate goal or an inventive idea.
The wireframe depicts the website's page layout or arrangement of content, including interface
components and navigation systems, as well as how they interact.
Because the major focus is on functionality, activities, and material priorities, the wireframe usually
lacks typographic design, color, or graphics. In other words, it is concerned with what a screen
accomplishes rather than how it seems. Wireframes can be handwritten or drawn on a whiteboard, or
they can be created with a variety of free or paid tools. Wireframes are often created by market
analysts, customer interface designers, developers, graphic designers, and others with experience in
interaction design, information architecture, and consumer analysis.
Wireframe on focus:
• The number of functionalities offered
• The relative importance of the information and functions
• The rules for presenting specific types of data
• The impact of various circumstances on the display
Wireframe of Tune Source Web

2. Mockup
A mockup, also known as a mock-up, is a scale or full-size model of a concept or product used
in manufacturing and construction for training, presentation, concept review, promotion, and other
purposes. Because it comprises at least some of a system's functionality and allows for design testing,
a mockup is considered a prototype. [1] Mock-ups are mostly used by designers to solicit feedback
from users. Mock-ups handle the concept represented in a famous one-liner engineering: You can fix
it now with an eraser on the drafting board, or you can fix it later the construction site with a
sledgehammer.
Mockup for Tune Source