SOFTWARE

DEVELOPMENT
LIFE CYCLE
Presenter: Nguyen Anh Khoa

Student: University of Greenwich

Content

1. Introduction
2. Identify the stakeholders, their roles and interests in the case
study
3. Analyse the requirements.
4. Discuss how the user and software requirements are
addressed in the design phase.
5. Conclusion
OUTLINE OF THE
ANALYSIS 1

Stakeholders - Roles -Interests

Functional and Non-functional
requirements
Technique to obtain therequirements
 Owner
John Margolis, Project
Megan
Taylor, and Phil Sponsor
Cooper. Carly Edwards,

Assistant Vice
Project President, and
Marketing
Manager

Anh Khoa Analyst

Team
Developer Requirement

Stakeholder Team
Developers,
analyst, business
analyst, infrastructure
analyst, and system analyst.
Designers, and
Testers
 Functional Requirements
- A functional requirement in software engineering
determines a device or component. It defines the
functions that must be performed by a program.
Nothing but inputs, their actions, and outputs are a
function. It can be a calculation, data manipulation,
businessmethod, user interaction, or some other
particular feature that determines what is likely to
Functional and Non- perform a system's purpose.

functional - Requirements for usable applications allow you to

Requirements capture the system's expected actions. This conduct

may be represented in the form of functions,
facilities or tasks or which system must be executed.
 Non-Functional Requirements

- The quality attribute of a software system is specified by a non-functional requirement.

They reflect a collection of criteria that are used to judge a system's basic activity. How
quick, for example, does the website load?

- To ensure the usability and efficacy of the entire software framework, a non-functional
requirement is vital. Failure to meet non-functional specifications will lead to systems
that do not meet the needs of users.

- Non-functional specifications allow you to enforce system design restrictions or

limitations through the various agile backlogs. Example, if the number of simultaneous
users is > 10000, the site should be loaded within 3 seconds. It is just as important as a
functional requirement to definenon-functional requirements.
 TECHNIQUE CHOSEN
FOR OBTAIN REQUIREMENT

Documentation Technique

Document analysis helps reviewing the existing system's documentation (user

manuals and instructions.)

-> Helpful particularly for any changeover risk mitigation and the PM can glean important
information that pushes the boundary of establishing new requirements or validating existing
ones.

-> Helpful to have multiple people review the documents and hold a meeting afterwards to
compile Tune Source’s insights to make sure nothing gets missed
Use Case Diagram

USER ADMIN
Context Diagram
Data Flow Diagram - Level 0
Entity Relationship Diagram
Wireframe Index of Tune Source
Wireframe Index of Tune Source
Thank you for
listening