https://www.docsity.

com/en/software-development-life-cycle-
assignment-2/7605281/
LO3 Undertake a software development lifecycle.
After we have explored and clarified the definitions and
information about the Tune Source project.
Now, we will conduct surveys, research on the business and the
main sponsors of the Tune Source
project, and will raise and clarify the issues of the Tune Source
project.

P5 Undertake a software investigation to meet a business need.

Requirement Specification
Interview and Survey

1. What is an interview?
An interview is defined as a purposeful conversation.
Commonly used interviews are: portraying a
character's character or providing information about the area
where the interviewee is knowledgeable
about the subject or is responsible for answering.
2. Necessary skills in the interview.
• Research carefully partners: Before having an interview,
we need to research partners and
prepare questions that are connected to their capabilities and
knowledge. In addition, we should address questions to our
partners in advance so that they can research the topics for the
most successful interview.
• Good organization skills: This is one of the essential skills
for all jobs. Employers will have
a better view of someone who can handle all the jobs. If an
interview is not well prepared, it
is very easy for unforeseen risks to occur.
• Prepare questions carefully: Before important interviews,
we should carefully prepare
questions, make sure that your partners are experts or who have
knowledge of the field.
• Working in Group: This is a very important skill for an
interview. After all the preparations
are completed, we must make sure that the work is clearly
assigned. Members must support
each other to work, avoiding conflicts that shouldn't exist when
the interview takes place.
• Control situations: In the interview that takes place, there
will certainly be unimportant risk
situations, make sure you have a sufficiently strong knowledge,
skills to deal with and deal
with those situations.

P6 Use appropriate software analysis tools/techniques to carry

out a software
investigation and create supporting documentation.
We will have a tool that is used to investigate requirements that
help create a holistic view of how the
application will work and meet business needs.
1. Identify some countenances of the Tune Source project.
• Stakeholders: include individuals and groups related to the
Tune Source project or have project
related impacts such as:
✓ Team leaders, project managers and developers who need
to meet all customer needs and
improve and upgrade to help users have the best look and
experience.
✓ Sponsors of the project: In addition to Carly Edwards - one
of the individuals contributing
to the cost support of the Tune Source project, there are also
others are also investors and
shareholders give money to implement the project.
✓ Company leaders include John Margolis, Megan Taylor and
Phil Cooper who have strong
passion, relevant knowledge about the music industry and have
extensive relationships with
many companies. Entertainment other music recording will help
increase the opportunity to
collect and select rare music, while increasing the number of
users more.
✓ Users: are those who will have access to the system's rare
music archive. They will also have
the right to raise their own views to evaluate the quality of the
end-stage application and
provide suggestions for developers to improve their products.
• Cost: is the amount of money that needs to be maintained
and used for items in a Tune Source
project.
✓ Costs for applying new technologies to the application,
updating the system.
✓ Costs for the development team.
✓ Costs for running ads.
✓ Cost of gift card programs, promotions and discounts.
✓ Costs for the construction of kiosks and system
maintenance.

✓ Cost of infrastructure maintenance for the application, for

servers, for the system.
✓ Costs for repairs.
• Security issues.
✓ Message, code via phone number and email.
✓ Security question.
✓ Payment verification.
✓ Strange access detected.
✓ Two-factor authentication.
✓ Prevent an attacker from accessing data without permission.
✓ Prevent, protect any network attacks such as Dos or DDos
from outside.
✓ Cost of infrastructure maintenance for the application, for
servers, for the system.
✓ Costs for repairs.
• Security issues.
✓ Message, code via phone number and email.
✓ Security question.
✓ Payment verification.
✓ Strange access detected.
✓ Two-factor authentication.
✓ Prevent an attacker from accessing data without permission.
✓ Prevent, protect any network attacks such as Dos or DDos
from outside.
✓ Cost of infrastructure maintenance for the application, for
servers, for the system.
✓ Costs for repairs.
• Security issues.
✓ Message, code via phone number and email.
✓ Security question.
✓ Payment verification.
✓ Strange access detected.
✓ Two-factor authentication.
✓ Prevent an attacker from accessing data without permission.
✓ Prevent, protect any network attacks such as Dos or DDos
from outside.
✓ Cost of infrastructure maintenance for the application, for
servers, for the system. ✓ Costs for repairs. • Security issues. ✓
Message, code via phone number and email. ✓ Security
question. ✓ Payment verification. ✓ Strange access detected. ✓
Two-factor authentication. ✓ Prevent an attacker from
accessing data without permission. ✓ Prevent, protect any
network attacks such as Dos or DDos from outside.

Problems with the old system:

✓ Like other cases, when the technology is too old to make the
system slow, slow, updating and replacing outdated equipment
and tools is a must. 2. Requesting an investigation use Case
Diagram. The following is a picture of the shift diagram that was
used in the system, including the steps to authenticate login,
access to music store, listen to music, pay, user profile and
some other functions: From the table above we can
understand that, if users want to listen to the fullest of
copyrighted and highest quality songs, users will have to
register so that they will not be interrupted when enjoying
music. However, they will have to pay a very small amount to
maintain listening to music, downloading music monthly. At the
same time, if you register to use, they will enjoy the VIP
privileges of VIP members.

The above chart has been applied to two types of users:

registered users and unregistered users. Registered users will
have the right to listen and download the full version of the
music, while those who have not registered, they will also have
the right to listen to the music for 10 seconds to make their
final decision about. download music, subscribe to the right to
use the full features and enjoy all the incentives. Figure 4 -
Requirements investigation flow chart.
above chart has been applied to two types of users: registered
users and unregistered users. Registered users will have the
right to listen and download the full version of the music, while
those who have not registered, they will also have the right to
listen to the music for 10 seconds to make their final decision
about. download music, subscribe to the right to use the full
features and enjoy all the incentives. Figure 4 - Requirements
investigation flow chart.

M3 Analyze how software requirements can be traced

throughout the software lifecycle.
1. Software requirements in the Tune Source project. After
researching the Tune Source project scenario, we learned
that the Tune Source company project will include the
following software requirements:
✓ Software for corporate projects.
✓ The company's project software is suitable for all
customers.
✓ Customers will have the right to create a free account
and submit a card, will have the right to download music
and listen to rare songs downloaded. Above are the very
important software requirements that must be included interview
in
the Tune Source project and the company needs to
research and supplement to meet all customer
requirements.
2. Traceability. How traceability occurs will always be
monitored if it is within the project's traceability area. It
will bring a favorable factor that it will give development
directions and will always follow the project that can be
interview
 tracked back to previous tasks and stages. In Tune Source,
we have considered all aspects to monitor such as:
Authorization, quality, user control and full
implementation to ensure that all requirements are met
and not dropped. Any miss is the agent affecting the
project. We can look at the traceability matrix, from which
there can be a clear check to follow and provide
appropriate back and forward solutions. Require
description End User Administration Manager Enable
profile function Add, update, listen, display Add, delete,
update, display
3. Display reviews sent Feedbacks receive Feedbacks receive
Feedbacks Sign up for an account Payment, VIP services
Give Feedback to Security Give Feedback to Security
Security review Retrieve password, pay card money, ... IT
services Send Feedbacks to security team User interface UI
Simple Easy management Comprehensive report Table 3 -
Traceability matrix required. The table above is a sample
table for creating traceable matrices for three categories:
end users, administrators and managers. Each person will
have different functions, the above table will give us an
overview of customer requirements and see if the quality
of the application has met all the requirements. 3. The
baseline. A baseline was created that aims to establish
project points at a specific time including tasks and tasks.
At that point of the process it will determine the
completion of the task. With this matrix, we can schedule
 the Tune Source project schedule and follow it for
development. Depending on the different aspects, the
baseline will be different: ➢ Scope: depending on the size
of the project, how much money the stakeholders will
support. For example, Carly Edwards is the Assistant Vice
President, and the main sponsor of the Tune Source
project. We will have to rely on the schedule using the
amount of money he will invest and be able to invite him
to an interview and give a questionnaire to conduct a
survey that will provide additional details about the
investment. , then we will analyze the requirements
for scoping schedule and set specific points. ➢ Time:
for the key factor: we will need to determine the
estimated time span and calculate how long the project
will last.

This page cannot be seen from the preview

Don't miss anything!

This page cannot be seen from the preview

Don't miss anything!
17 | P a g e Assignment 2 – SDLC – Nguyen Duc Dung Types
of Version Control: ✓ CVS: is the standard here, and is used just
about everywhere. ✓ SVN: is the version control system that
has the widest adoption. ✓ GIT: is a newer, and faster emerging
star. ✓ Mercurial: is a very fast and efficient application. ✓
Bazaar: is distributed version control system. Figure 7 - Types
of VSC Figure 6 - Version Control sample
17 | P a g e Assignment 2 – SDLC – Nguyen Duc Dung Types
of Version Control: ✓ CVS: is the standard here, and is used just
about everywhere. ✓ SVN: is the version control system that
has the widest adoption. ✓ GIT: is a newer, and faster emerging
star. ✓ Mercurial: is a very fast and efficient application. ✓
Bazaar: is distributed version control system. Figure 7 - Types
of VSC Figure 6 - Version Control sample
This page cannot be seen from the preview
Don't miss anything!

M3 Analyze how software requirements can be traced

throughout the software lifecycle.
1. Software requirements in the Tune Source project. After
researching the Tune Source project scenario, we learned that
the Tune Source company project will include the following
software requirements: ✓ Software for corporate projects. ✓
The company's project software is suitable for all customers. ✓
Customers will have the right to create a free account and
submit a card, will have the right to download music and listen
to rare songs downloaded.
Above are the very important software requirements that must
be included in the Tune Source project and the company needs
to research and supplement to meet all customer
requirements.
2. Traceability. How traceability occurs will always be
monitored if it is within the project's traceability area. It will
bring a favorable factor that it will give development directions
and will always follow the project that can be tracked back to
previous tasks and stages. In Tune Source, we have considered
all aspects to monitor such as: Authorization, quality, user
control and full implementation to ensure that all requirements
are met and not dropped. Any miss is the agent affecting the
project. We can look at the traceability matrix, from which
there can be a clear check to follow and provide appropriate
back and forward solutions.
The table above is a sample table for creating traceable matrices
for three categories: end users,
administrators and managers. Each person will have different
functions, the above table will give
us an overview of customer requirements and see if the quality
of the application has met all the
requirements.
3. The baseline.
A baseline was created that aims to establish project points at a
specific time including tasks
and tasks. At that point of the process it will determine the
completion of the task. With this matrix,
we can schedule the Tune Source project schedule and follow it
for development.
Depending on the different aspects, the baseline will be
different:
➢ Scope: depending on the size of the project, how much
money the stakeholders will
support. For example, Carly Edwards is the Assistant Vice
President, and the main
sponsor of the Tune Source project. We will have to rely on the
schedule using the
amount of money he will invest and be able to invite him to an
interview and give a
questionnaire to conduct a survey that will provide
additional details about the
investment. , then we will analyze the requirements for
scoping schedule and set
specific points.
➢ Time: for the key factor: we will need to determine
the estimated time span and
calculate how long the project will last.