Docsity Assignment 2 Software Development Life Cycle SDLC Pass

Assignment 2 - Software
Development Life Cycle (SDLC) -

PASS
Computer Science
FPT University (FPTU)
30 pag.
Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Downloaded by: nguyet-minh-17 (phongnguyenk604@gmail.com)
ASSIGNMENT 2 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing
Unit number and title Unit 09: Software Development Life Cycle
Submission date 11/07/2022 Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Huynh Minh Huy Student ID GCD210173
Class GCD1001 Assessor name Tran Trong Minh
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 Huy

Grading grid
P5 P6 P7 M3 M4 M5 M6 D3 D4

 Summative Feedback:  Resubmission Feedback:
Grade: Assessor Signature: Date:

Lecturer Signature:

Acknowledgement
First and foremost, I want to thank the curators at the University of Greenwich for making
these courses available to students. I would like to thank all of the writers and researchers
who worked on this data. I would also want to thank teacher Tran Trong Minh for his
excellent and professional lectures and tutorials. Finally, I would like to thank our
university's lecturers and responsible personnel for offering an excellent learning
atmosphere.

Table of Contents
Introduction. ............................................................................................................................................................................. 6
Task 1 – Requirement. .......................................................................................................................................................... 6
I. Identify the stakeholders, their roles and interests in the case study. ................................................. 6
1. What is stakeholder? ....................................................................................................................................... 6
2. Types of stakeholder. ...................................................................................................................................... 7
3. Roles of Stakeholders. ..................................................................................................................................... 9
4. Stakeholder role with interest in Tune Source Project. ................................................................... 10
5. Stakeholder Requirements. ........................................................................................................................ 11
6. Identify FRs and NFRs of Tune Source Project. ................................................................................... 11
7. Discuss the relationships between the FRs and NFRs. ..................................................................... 13
II. Discuss the technique(s) you would use to obtain the requirements. ............................................... 14
1. Some approach/technique (es) suitable for the project. ................................................................ 14
2. Conclusion. ........................................................................................................................................................ 16
Task 2 – Analyze the requirements. .............................................................................................................................. 17
I. Use appropriate software analysis tools/techniques to carry out a software investigation and
create supporting documentation. ............................................................................................................................ 17
1. Data Flow Diagram (DFD). .......................................................................................................................... 17
2. Entity Relationship Diagram. ..................................................................................................................... 18
3. Flow Chart. ........................................................................................................................................................ 19
Task 3 – Design. .....................................................................................................................................................................

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/ 20
I. Explain how user and software requirements have been addressed in the design. ..................... 20
1. Wireframe. ......................................................................................................................................................... 20
2. Mockup. .............................................................................................................................................................. 25
References ............................................................................................................................................................................... 30
Table of Figures
Figure 1: Stakeholder. ........................................................................................................................................................... 6
Figure 2: Data Flow Diagram. .......................................................................................................................................... 17
Figure 3: Entity Relationship Diagram. ........................................................................................................................ 18
Figure 4: Flow Chart. ........................................................................................................................................................... 19
Figure 5: Log-in Page. .......................................................................................................................................................... 21
Figure 6: Register Page. ...................................................................................................................................................... 22
Figure 7: Landing Page. ...................................................................................................................................................... 23
Figure 8: Home Page............................................................................................................................................................ 24
Figure 9: Log-in page. .......................................................................................................................................................... 25
Figure 10: Register Page. ................................................................................................................................................... 26
Figure 11: Landing Page..................................................................................................................................................... 26
Figure 12: Home Page. ........................................................................................................................................................ 27
Figure 13: Home Page In Mobile Interface. ................................................................................................................ 28
Figure 14: Landing Page in Mobile Interface. ............................................................................................................ 29

Introduction.
The previous assignment explored several software development lifecycles and emphasized
the significance of a feasibility analysis for the Tune Source project. Furthermore, analyzing
the applicability of software behavioral design methodologies by describing how user and
software criteria have been met.
Task 1 – Requirement.
I. Identify the stakeholders, their roles and interests in the case study.
1. What is stakeholder?
A stakeholder is any individual, group, or party who has an interest in an
organization and the effects of its actions. Employees, consumers, shareholders,
suppliers, communities, and governments are all examples of stakeholders. Diverse
stakeholders have different interests, and firms frequently confront trade-offs while
attempting to please everyone.

Figure 1: Stakeholder.
2. Types of stakeholder.
a. Customers.
 Stake: Product/service quality and value
Many would contend that companies are there to serve their clients.
Customers are stakeholders in a company because they are affected by the
value and quality of the goods and services offered. For instance, when
boarding a flight, a passenger practically places their life in the hands of the
airline.
b. Employees.
 Stake: Employment income and safety
Because they receive benefits and an income to maintain themselves,
employees have a direct financial interest in the business (both monetary and
non-monetary). The nature of the firm will determine whether employees'
interests in health and safety exist (for example, in the industries of
transportation, mining, oil and gas, construction, etc.).
c. Investor.
 Stake: Financial returns
Shareholders and debtholders are both types of investors. Shareholders
invest capital in the business with the expectation of earning a certain rate of
return on that investment. Shareholder value is a topic that many investors
are interested in. All other capital providers, such as lenders and potential
acquirers, are included in this category. All shareholders are inherently
stakeholders, but not all stakeholders are shareholders.

d. Suppliers and Vendors.
 Stake: Revenues and safety
Suppliers and vendors sell goods and/or services to businesses that rely on
them for revenue and ongoing income. Suppliers' health and safety are at risk
in many industries because they may be directly involved in the company's
operations.
e. Communities.
 Stake: Health, safety, economic development
Communities play an important role in the success of large businesses that
locate in them. They are influenced by a variety of factors, such as job creation,
economic development, health, and safety. When a large corporation enters
or exits a small community, it has an immediate and significant impact on
local employment, income, and spending. Some industries may have a
negative impact on health because they alter the environment.
f. Governments.
 Stake: Taxes and GDP
Governments are also important stakeholders in businesses because they
collect taxes from the company (corporate income taxes), as well as from all
of the people it employs (payroll taxes), and from other expenses the
company incurs (sales taxes). Governments benefit from the overall Gross
Domestic Product (GDP) contribution of businesses.

3. Roles of Stakeholders.
 Direct the Management: Stakeholders can serve on the board of directors and so
contribute to decision-making. They can oversee certain departments like as
service, human resources, or research and development to ensure success.
 They Bring in Money: Stakeholders are the company's largest investors, and they
can withdraw or deposit funds at any moment. Their judgment will be influenced
by the company's financial success. As a result, they may put pressure on
management for financial reports and, if required, modify methods. Some
stakeholders may even raise or decrease their investment in order to affect the
market share price and so make the conditions more beneficial to them.
 Help in Decision Making: The board of directors includes major interests. As a
result, they make choices alongside the other board members. They also have the
ability to sway judgments. They also introduce new ideas and threaten
management to obey them. The stakeholders also have complete authority to
designate top management. As a result, they are present in all significant decision-
making sectors. They also make judgments on acquisitions and liquidations.
 Corporate Conscience: Large stakeholders are the company's primary
stakeholders, and they have overseen all of the company's important actions. They
have the power to compel the corporation to follow human rights and
environmental regulations. They also monitor outsourcing activities and may vote
against any business action that jeopardizes the company's long-term goals.
 Other Responsibilities: Apart from the four core jobs listed above, they also
perform various minor roles in the firm. They can spot fresh opportunities for
market penetration and revenue growth. They can contribute additional
marketing ideas. They also draw additional investors to the firm like honeybees.
TheyDocument
might be
shared a member of a selection committee or a corporate representative.
on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/
Furthermore, they have the authority to make all key social and environmental
choices.
4. Stakeholder role with interest in Tune Source Project.
Stakeholder Roles Interest

Huynh Minh Huy Project Manager Project managers take the lead in project
planning, execution, monitoring, control,
and closure. Here is an overview of the
project manager role, responsibilities,
required credentials, projected wages,
and job-search advice.
Users Customers Customers are those who utilize Tune
Source services to listen to music and buy
it, which boosts the company's revenue.
John Margolis, Megan Co-Founders of Tune Co-Founders will be able to offer ideas,
Taylor, Phil Cooper Source develop the project, and handle budgeting
and spending management.
The IT department at Management, As it has worked with the ISP to manage
Tune Source maintenance, and the site, get knowledge with Internet
monitoring of the technologies.
website
Carly Edwards, Project Sponsor The project sponsor will be accountable
Assistant Vice for the entire success of the project,
President, Marketing including the selection of the project
manager and team, the development of
success criteria, and the project's
successful conclusion.

5. Stakeholder Requirements.
Stakeholders Requirements Provided

Huynh Minh Huy Carry out the project and assist the team in
developing software to meet the specifications.
Users Customers will be able to find and buy digital
music downloads.
John Margolis, Megan Taylor, Phil Cooper Co-Founders must bring the system to market
as quickly as feasible.
The IT department at Tune Source Increase sales by enabling consumers to
purchase non-copyrighted music downloads via
kiosks in their stores and via the internet via
their website.
Carly Edwards, Assistant Vice President, Management and maintenance.
Marketing
6. Identify FRs and NFRs of Tune Source Project.

a. Definition of Functional Requirements.
A Functional Requirement (FR) describes the service that the program must
provide. It refers to a software system or a component of one. A function is
nothing more than the software system's inputs, behavior, and outputs. It
might be a computation, data manipulation, business process, user interaction,
or any other specialized activity that defines the function of a system. In
software engineering, functional requirements are also known as functional
specifications.

Functional Requirements Description Example
Download Allow clients to download their Customers may download and listen to their
purchased songs. favorite songs without needing to connect to
the internet. You may also make an album to
put it in.
Listen Allow customers to listen to music Customers may listen to the music by just
online without downloading clicking on it. When the song ends, the music
simply connecting to the Internet. will switch to a new one.
Search Allow users to search for songs by When a customer submits a song title or lyric,
using song-related terms like song the system displays the name of the song.
title, artist name, album name, or a
phrase in the song.
Register Allows new users to create a new Customers can access their registered account
account in order to access the and download the copyrighted music from
Tune Source service. Tune Source.
Login to website Allow customers and When logged in, the consumer gets access to all
administrators to log in to the system functions and can purchase gift cards.
Tune Source system and utilize
accessible accounts to access all
other services.
Purchase gift card/song Customers may purchase gift Customers may purchase songs to delight
cards and song downloads. themselves and gift cards to friends, such as
trail 1 weeks to trail service.
Manage Customers' account information Customers' information, such as name, address,
account/information may be managed and modified by bill, date of birth, and so on, can be changed by
the administrator. the administrator.
b. Definition of Non-Functional Requirements.
Non-Functional Requirement (NFR) describes a software system's quality
attribute. They evaluate the software system based on its responsiveness,
usability, security, portability, and other non-functional characteristics that
are crucial to its success. "How quickly does the website load?" is an example
of a nonfunctional requirement. Non-functional requirements that are not met
can lead to systems that do not meet the demands of the users.
Non-Functional Requirements Description
A firewall should be installed on a user's
Security
database to prevent unwanted access.
The system performs well in a number of
settings. Users may access the website using a
Compatibility
variety of devices, including phones, tablets,
and laptop computers.
Ensure that the system's capacity is sufficient to
support when a large number of people come at
Capacity
the same time, and that users may alter and
store settings based on their preferences.
Highly dependable technology continues to
Reliability perform with the same or similar efficacy after
extended use.
7. Discuss the relationships between the FRs and NFRs.
The functional and non-functional requirements create the groundwork for the
successDocument
of shared
a software development project. Functional requirements specified
on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/
certain characteristics to encourage software development. Non-functional
requirements are tied directly to software features.
Non-functional requirements are product criteria from the user's perspective that
outline how a project should be implemented to create an end-user experience. The
software development process is greatly accelerated when the needed product
features are identified and requirements for each of those features are established.
If the functional or nonfunctional needs are not specified, the project will suffer
severely.
II. Discuss the technique(s) you would use to obtain the requirements.
1. Some approach/technique (es) suitable for the project.
 Joint Application Development (JAD).
JAD (Joint Application Development) is a way of including the client or
end user in the design and development of an application through a
series of collaborative workshops known as JAD sessions.
 Benefits:
- JAD enables you to solve problems more quickly and develop
better, error-free software.
- The company's and clients' combined participation reduces all
hazards.
- JAD saves project development costs and time.
- System quality is improved by well-defined criteria.
- Progress is accelerated as a result of close communication.
- JAD motivates the team to work quicker and to produce on
schedule.
 Drawbacks:
- Diverse viewpoints on the team make it challenging to align
goals and keep focus.
- JAD may need a large time investment depending on the scale
of the project.
 Survey/Questionnaire.
The phrase "questionnaire" refers to the series of questions you are
asking an individual. A survey is the process of gathering, analyzing, and
interpreting data from a large number of people. It seeks to learn more
about a group of individuals.
 Benefits:
- It takes less time for participants to answer.
- When compared to interviews, you can obtain more accurate
information.
 Drawbacks:
- Based on the replies made by participants, follow-up surveys
may be necessary.
- Some questions may be unclear to all participants.
- Open-ended questions necessitate deeper investigation.
- The surveys may not be completed by all stakeholders.
 Mind Mapping.
Acquiring project requirements requires not just gathering information,
but also capturing, structuring, and organizing it. Mind mapping might be
a very efficient way of capturing a brainstorming session.
 Benefits:
- A wealth of important information.
- It works in the same way as your mind operates in a hierarchy,
pushing you to be analytical in order to find gaps and trends.
- The structure allows you to go on to the next stage
(information sorting) before the requirement gathering is
finished, saving you time and effort.
 Drawbacks:
- Manual mind mapping (with a pen and paper) is inefficient
and unorganized.
- It can be tough to translate ideas and intentions into action
without the right tools.
2. Conclusion.
In this Tune Source project, a survey/questionnaire is used to collect needs since it
is simple to collect data from a broad audience, takes less time for users to reply,
and provides more reliable information than other strategies.
 Assumption about the project justifying the techniques that you have
chosen.
The Questionnaires approach enables team projects to get critical information
and data. Furthermore, if the team project is to create an excellent research
report, the project must have exceptional facts. Furthermore, if the project
requires high-quality data, a well-designed questionnaire or research would
be required. Questionnaire procedures are the most popular and easiest way
to gather data in research. As a result, a team project may create a survey,
disseminate it to a large number of individuals, and then analyze and assess
the responses.
 Steps in the development of Survey/Questionnaire.
The following Technique was used to obtain requirements:
Step 1: Determine the important information we must know.
Step 2: Who will get the Survey?
Step 3: How will the data be collected (by mail, email, or phone)?
Step 4: What questions
Downloaded will be
by: nguyet-minh-17 asked?
(phongnguyenk604@gmail.com)
Step 5: Check that the questions only disclose potential respondents and, if
necessary, change them.
Step 6: Make the questionnaire accessible to the general audience.
Step 7: Locate the solution.
Step 8: Perform a test.
Step 9: Put the results into action.
Task 2 – Analyze the requirements.

I. Use appropriate software analysis tools/techniques to carry out a software investigation and
create supporting documentation.
1. Data Flow Diagram (DFD).
The Data Flow Diagram (DFD) is a system paradigm that aligns data and progress.
It demonstrates how information is transferred from one operation or function in
the system to another.
The data flow diagram in Tune Source should assist developers in identifying
external influences or determining the scope of the project.

Figure 2: Data Flow Diagram.
2. Entity Relationship Diagram.
An Entity-Relationship (ER) Diagram is a type of flowchart that depicts how
"entities" in a system interact with one another, such as people, objects, or concepts.
To construct or debug relational databases, ERD are most widely used in software
engineering, business information systems, education, and research. They use a
fixed set of symbols such as rectangles, diamonds, ovals, and connecting lines to
depict the interconnectedness of things, connections, and their attributes. They are
often referred to as ERDs or ER Models. They mirror the verbal structure, with
things serving as nouns and connections serving as verbs.
Figure 3: Entity Relationship Diagram.

3. Flow Chart.
A flowchart depicts the individual phases of a process in sequential order. It is a

general-purpose tool that may be used to define a range of processes, such as a
manufacturing process, an administration or service process, or a project plan. It is
a standard process analysis tool and one of the seven fundamental quality tools.

Figure 4: Flow Chart

Task 3 – Design.
I. Explain how user and software requirements have been addressed in the design.
 Requirements and functions for design.
User can listen to the music when they find the song by clicking on the song.
 So we need.
 Landing Page.
 Home Page.
 Register Page.
 Log-In Page.
1. Wireframe.
Wireframes are the design's base upon which everything else is built. They are black
and white images that rely primarily on grey boxes and text to portray what a
product will appear like. They are low quality and quick to construct, and are
frequently used in brainstorming sessions. Creation may be done using paper and
pencil, a whiteboard, or in a product management platform – and it does not have
to be done by a UX designer. Product managers may step in to assist with
brainstorming. Wireframes should be utilized to gain agreement on a concept's
essential functionality. The exclusion of aesthetic components like as colors and
logos is deliberate, as critiques should focus on whether or not the suggested layout
or organization will benefit users rather than on visual aspects.

 Wireframe of Tune Source Web.
Figure 5: Log-in Page.

Figure 6: Register Page.

Figure 7: Landing Page.

Figure 8: Home Page.

2. Mockup.
Mockups take wireframes to the next level by incorporating design components like
color schemes, fonts, icons, and navigation elements. Typically, more than one
prototype is generated, presenting decision-makers with a variety of choices to
consider. Actual content is frequently added in renderings to make them more
indicative of the final result. To produce mockups, more work and talent are
necessary. A UX designer will construct and show the possibilities using digital
software.
A more extensive visual assessment is recommended when the prototypes are given
to stakeholders. The realistic depictions make it straightforward to determine what
makes sense about the designs from the consumers' point of view. Comparing
mockups assists the team in reaching an agreement on a design direction. Because
mockups are static, any modifications or requests can be easily included.
 Laptop, Computer Interface.

Figure 9: Log-in page.

Figure 10: Register Page.

Figure 11: Landing Page.

Figure 12: Home Page.

 Mobile Interface.
Figure 13: Home Page In Mobile Interface.

Figure 14: Landing Page in Mobile Interface.

References
Aha, n.d. What is the difference: Wireframe vs. Mockup vs. Prototype?. [Online]
Available at: https://www.aha.io/roadmapping/guide/product-management/wireframe-mockup-
prototype
[Accessed 09 07 2022].
Landau, P., 2022. What Is a Stakeholder? Definitions, Types & Examples. [Online]
Available at: https://www.projectmanager.com/blog/what-is-a-stakeholder
[Accessed 09 07 2022].
Martin, M., 2022. What is a Functional Requirement in Software Engineering? Specification, Types,
Examples. [Online]
Available at: https://www.guru99.com/functional-requirement-specification-example.html
[Accessed 09 07 2022].
Martin, M., 2022. What is Non-Functional Requirement in Software Engineering? Types and Examples.
[Online]
Available at: https://www.guru99.com/non-functional-requirement-type-example.html
[Accessed 09 07 2022].

Powered by TCPDF (www.tcpdf.org)

Docsity Assignment 2 Software Development Life Cycle SDLC Pass

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Docsity Assignment 2 Software Development Life Cycle SDLC Pass

Uploaded by

Copyright:

Available Formats

Assignment 2 - Software

Development Life Cycle (SDLC) -

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Qualification BTEC Level 5 HND Diploma in Computing

Submission date 11/07/2022 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name Huynh Minh Huy Student ID GCD210173

Class GCD1001 Assessor name Tran Trong Minh

Student’s signature Huy

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Grade: Assessor Signature: Date:

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Task 1 – Requirement. .......................................................................................................................................................... 6

1. What is stakeholder? ....................................................................................................................................... 6

2. Types of stakeholder. ...................................................................................................................................... 7

3. Roles of Stakeholders. ..................................................................................................................................... 9

4. Stakeholder role with interest in Tune Source Project. ................................................................... 10

5. Stakeholder Requirements. ........................................................................................................................ 11

6. Identify FRs and NFRs of Tune Source Project. ................................................................................... 11

7. Discuss the relationships between the FRs and NFRs. ..................................................................... 13

1. Some approach/technique (es) suitable for the project. ................................................................ 14

Task 2 – Analyze the requirements. .............................................................................................................................. 17

1. Data Flow Diagram (DFD). .......................................................................................................................... 17

2. Entity Relationship Diagram. ..................................................................................................................... 18

3. Flow Chart. ........................................................................................................................................................ 19

Task 3 – Design. .....................................................................................................................................................................

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Stakeholder Roles Interest

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Stakeholders Requirements Provided

6. Identify FRs and NFRs of Tune Source Project.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

7. Discuss the relationships between the FRs and NFRs.

Task 2 – Analyze the requirements.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Figure 3: Entity Relationship Diagram.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

A flowchart depicts the individual phases of a process in sequential order. It is a

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Figure 4: Flow Chart

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Figure 5: Log-in Page.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Figure 9: Log-in page.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Figure 11: Landing Page.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Figure 13: Home Page In Mobile Interface.

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Document shared on https://www.docsity.com/en/assignment-2-software-development-life-cycle-sdlc-pass/8832155/

Powered by TCPDF (www.tcpdf.org)

You might also like