Higher Nationals in Computing

Unit 09: Software Development Life Cycle

ASSIGNMENT 2

Learner’s name: Ninh Xuân Bảo Hưng

ID: GCS200058

Class: GCS0905A

Subject code: 1631

Assessor name: Vo Ngoc Mai

Assignment due: Assignment submit

1
 ASSIGNMENT 1 FRONT SHEET

Qualification TEC Level 5 HND Diploma in Computing

Unit number and title Unit 09: Software Development Life Cycle

Submission date Date Received 1st submission

Date Received 2nd

Re-submission Date
submission

Student Name NINH XUÂN BẢO HƯNG Student ID GCS200058

Class GCS0905A Assessor name Vo Ngoc Mai

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

Grading grid

P5 P6 P7 M3 M4 M5 M6 D3 D4

1
 Summative Feedback:  Resubmission Feedback:

Grade: Assessor Signature: Date:

Signature & Date:

2
 Assignment Brief 02 (RQF)
Higher National Certificate/Diploma in Business

Student Name/ID Number: Nguyen Le Minh Phat/GCS200137

Unit Number and Title: Unit 09: Software Development Life Cycle

Academic Year:

Unit Assessor: Vo Ngoc Mai

Assignment Title: Undertake a software development life cycle

Issue Date: 07/12/2020

Submission Date:

Internal Verifier Name:

Date:

Submission Format:

Format:
● The submission is in the form of 1 document.
● You must use the Times font with 12pt size, turn on page numbering; set line spacing to 1.3 and
margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation and
references must follow the Harvard referencing style.
Submission:
● Students are compulsory to submit the assignment in due date and in a way requested by the
Tutor.
● The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/.
● Remember to convert the word file into PDF file before the submission on CMS.
Note:

3
 ● The individual Assignment must be your own work, and not copied by or from another student.
● If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you
must reference your sources, using the Harvard style.
● Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to comply
this requirement will result in a failed assignment.

Unit Learning Outcomes:

LO3 Undertake a software development lifecycle.

LO4 Discuss the suitability of software behavioural design techniques.

Assignment Brief and Guidance:

Tasks
At this stage, you have convinced Tune Source to select your project for development. Complete the
following tasks to analyse and design the software.
Task 1 – Analysis (1)
1. (P5.a)Identify the stakeholders, their roles and interests in the case study.
Review the requirement definition of the project. Clearly indicate which stakeholder(s) provide what
requirements.
Word limit: 150 – 200.
Identify FRs and NFRs of Tune Source Project.
Discuss the relationships between the FRs and NFRs.
Word limit: 300 – 400 words.
2. (P5.b)Discuss the technique(s) you would use to obtain the requirements.
If needed, you may state suitable additional assumptions about the project in order to justify the
technique(s) that you choose.
Techniques: JAD, Interview, Observation, etc.
Demonstrate how to collect requirements based on chosen technique.
Word limit: 700 – 1000.
3. (M3)Discuss how you would trace these requirements throughout the project by using Requirement
Traceability matrix. You will have to provide real usage of it.
Word limit: 400 – 500 words.
Task 2 – Analysis (2)

4
(P6)Analyze the requirements that you identified in Task 1 using a combination of structural and
behavioral modelling techniques that you have learnt.
Scope: You only need to construct following items for the system. You will have to include:

 Use Case Diagram for the whole system.

 Use Case specification for 2 Use cases.
 Context Diagram for the whole system.
 Data Flow Diagram – Level 0 for the whole system.
 ERD for the whole system.
For each diagram, you will have to explain properly.
Word limit: 1000 – 1200 words.
Task 3 – Design
Based on the analysis result, discuss how you would conduct the design phase:
1. (P7)Discuss how the user and software requirements are addressed in the design phase.
 You will explain how Mock-up, and Wireframe are used in the project. You should include some
of the mockup or wireframe (at least 5) design of the Tune Source project to justify that it matches
users’ requirements.
 You will explain which architecture (client – server, n-tier, microservices, etc.) is suitable for the
project with clear illustrations and why.
 Then you will address which technical solution stack could be suitable to implement the project
with clear explanations.
2. (M5)Discuss how activity diagram and pseudocode are used to specify the software behaviour.
3. (M6)Discuss how UML state machine can be used to specify the software behaviour. Differentiate
between FSM and extended FSM using the case study.
4. (D4)Discuss how the data-driven approach improves the reliability and effectiveness of software.
Word limit: 800 – 1500.
Task 4 – Software quality management
1. (M4.a)Discuss two software quality attributes that are applicable to the project.
2. (M4.b)Discuss two quality assurance techniques that can help improve the software quality in the
project.
3. (D3)Discuss how the design techniques and approaches that you have used can help improve the
software quality.
Word limit: 400 – 1500.

Learning Outcomes and Assessment Criteria (Assignment 02):

5
Learning
Pass Merit Distinction
Outcome

P5 Undertake a software
investigation to meet a M3 Analyse how software D3 Critically evaluate
business need. requirements can be traced how the use of the
LO3 Undertake a throughout the software
P6 Use appropriate function design
software lifecycle.
software analysis paradigm in the
development
tools/techniques to carry M4 Discuss two software development
lifecycle
out a software approaches to improving lifecycle can improve
investigation and create software quality. software quality.
supporting documentation.

M5 Suggest two software

behavioural specification D4 Present
LO4 Discuss the methods and illustrate justifications of how
suitability of P7 Explain how user and their use with an example. data driven software
software software requirements M6 Differentiate between can improve the
behavioural have been addressed. a finite state machine reliability and
design techniques (FSM) and an extended- effectiveness of
FSM, providing an software.
application for both.

6
 Table of Contents
P5a. Identify the stakeholders,theirs roles and interests in the case study and review the
requirement definition of the project. ....................................................................................................... 8
1. Intro purpose of this section............................................................................................................... 8
2. Introduction of requirement definition, FR, NFR and more details .............................................. 8
3. Present the discussion about relationships between the FRs and NFRs ...................................... 11
4 List out stakeholders who can provide requirements, their roles and their interests in Tune
Source project........................................................................................................................................ 12
5. Apply FR and NFR for tune source ................................................................................................ 13
P5b. Discuss the technique to obtain the requirements. ........................................................................ 14
1. Intro purpose of this section............................................................................................................. 14
2.Intro 5 requirement gathering techniques ....................................................................................... 14
3. Apply to tune source ......................................................................................................................... 21
4.Interview note for Tune Source ........................................................................................................ 21
P6 Analysis the requirements that I identified in task 1........................................................................ 22
1.Intro purpose of this section.............................................................................................................. 22
2.Introduce about requirement modelling .......................................................................................... 23
3.Apply requirement modelling to Tune Source ................................................................................ 24
P7. Discuss how the user and software requirement are addressed in the design phase. ................... 30
1.Intro purpose of this section.............................................................................................................. 30
2.Intro detail of use case diagram ........................................................................................................ 30
3.Apply to Tune Source ........................................................................................................................ 31

7
P5a. Identify the stakeholders,theirs roles and interests in the case study and review the
requirement definition of the project.
1. Intro purpose of this section
- 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.

2. Introduction of requirement definition, FR, NFR and more details

a. Functional Requirement
- A Functional Requirement (FR) is a description of the service that the software must offer. It
describes a software system or its component. A function is nothing but inputs to the software
system, its behavior, and outputs. It can be a calculation, data manipulation, business process,
user interaction, or any other specific functionality which defines what function a system is
likely to perform. Functional Requirements in Software Engineering are also called Functional
Specification.
- In software engineering and systems engineering, a Functional Requirement can range from the
high-level abstract statement of the sender’s necessity to detailed mathematical functional
requirement specifications. Functional software requirements help you to capture the intended
behaviour of the system.
- Functional Requirements of a system should include the following things:
+ Details of operations conducted in every screen
+ Data handling logic should be entered into the system
+ It should have descriptions of system reports or other outputs
+ Complete information about the workflows performed by the system
+ It should clearly define who will be allowed to create/modify/delete the data in the system
+ How the system will fulfill applicable regulatory and compliance needs should be captured in
the functional document

A. Advantages of Functional Requirement

Here, are the pros/advantages of creating a typical functional requirement document-

Helps you to check whether the application is providing all the functionalities that were
mentioned in the functional requirement of that application

8
A functional requirement document helps you to define the functionality of a system or one of its
subsystems.
Functional requirements along with requirement analysis help identify missing requirements.
They help clearly define the expected system service and behavior.
Errors caught in the Functional requirement gathering stage are the cheapest to fix.
Support user goals, tasks, or activities for easy project management
Functional requirement can be expressed in Use Case form or user story as they exhibit
externally visible functional behavior.

B. Types of Functional Requirements

- Here are the most common functional requirement types:
+ Transaction Handling
+ Business Rules
+ Certification Requirements
+ Reporting Requirements
+ Administrative functions
+ Authorization levels
+ Audit Tracking
+ External Interfaces
+ Historical Data management
+ Legal and Regulatory Requirements

b. Non-Functional Requirement
- Non-Functional Requirement (NFR) specifies the quality attribute of a software system. They
judge the software system based on Responsiveness, Usability, Security, Portability and other
non-functional standards that are critical to the success of the software system. Example of
nonfunctional requirement, “how fast does the website load?” Failing to meet non-functional
requirements can result in systems that fail to satisfy user needs.
- Non Functional requirements in Software Engineering allows you to impose constraints or
restrictions on the design of the system across the various agile backlogs. Example, the site
should load in 3 seconds when the number of simultaneous users are > 10000. Description of
non-functional requirements is just as critical as a functional requirement.
9
A. Types of Non-functional Requirement
- Below are the main types of non functional requirements:
+ Usability requirement
+ Serviceability requirement
+ Manageability requirement
+ Recoverability requirement
+ Security requirement
+ Data Integrity requirement
+ Capacity requirement
+ Availability requirement
+ Scalability requirement
+ Interoperability requirement
+ Reliability requirement
+ Maintainability requirement
+ Regulatory requirement
+ Environmental requirement

B. Advantages of Non-Functional Requirement

- Benefits/pros of Non-functional testing are:
+ The nonfunctional requirements ensure the software system follow legal and compliance rules.
+ They ensure the reliability, availability, and performance of the software system
+ They ensure good user experience and ease of operating the software.
+ They help in formulating security policy of the software system.

C. Disadvantages of Non-functional requirement

- Cons/drawbacks of Non-function requirement are:
+ None functional requirement may affect the various high-level software subsystem

10
+ They require special consideration during the software architecture/high-level design phase
which increases costs.
+ Their implementation does not usually map to the specific software sub-system,
+ It is tough to modify non-functional once you pass the architecture phase.

3. Present the discussion about relationships between the FRs and NFRs
- Functional Requirements: These are the requirements that the end user specifically demands as
basic facilities that the system should offer. All these functionalities need to be necessarily
incorporated into the system as a part of the contract. These are represented or stated in the form
of input to be given to the system, the operation performed and the output expected. They are
basically the requirements stated by the user which one can see directly in the final product,
unlike the non-functional requirements.
- Non-functional requirements: These are basically the quality constraints that the system must
satisfy according to the project contract. The priority or extent to which these factors are
implemented varies from one project to other. They are also called non-behavioral requirements.
-They basically deal with issues like:
+ Portability
+ Security
+ Maintainability
+ Reliability
+ Scalability
+ Performance
+ Reusability
+ Flexibility

- Following are the differences between Functional and Non Functional Requirements :

11
4 List out stakeholders who can provide requirements, their roles and their interests in
Tune Source project
Name Position Interest
John Margolis Project Sponsor, President open a number of brick and
mortar stores in southern
California specialising in
hard-to-find and classic jazz,
rock, country, and folk
recordings
Megan Taylor Project Sponsor, President contacts and knowledge of
classical music
Phil Cooper Project Sponsor, President open a number of brick and
mortar stores in southern
California specialising in
hard-to-find and classic jazz,
rock, country, and folk
recordings

12
 Ninh Xuan Bao Hung project management Fulfill all requests from
customers like 1. Search for
music in our digital music
archive. 2. Listen to music
samples. 3. Purchase
individual downloads at a
fixed fee per download. 4.
Establish a customer
subscription account
permitting unlimited
downloads for a monthly fee.
5. Purchase music download
gift cards.
Carly Edwards Project Sponsor This project has been initiated
to increase sales by creating
the capability of selling
digital music downloads to
customers through kiosks in
our stores, and over the
Internet using our website.

5. Apply FR and NFR for tune source

Person Interviewed Interviewer Requirement Explaining its needs
John Annie Ninh Xuan Bao Hung Search for music in We created the search
our digital music feature. Users only need to
archive enter the name of their
favorite song
Elizabeth Ninh Xuan Bao Hung Listen to music We will let the user listen to
samples. a part of the song first. If you
like it, you can buy it
Christopher Ninh Xuan Bao Hung Purchase individual We will show customers the
downloads at a fixed price of the product so that
fee per download. they can know and buy it
Daniel Ninh Xuan Bao Hung Establish a customer We create an account so
subscription account users can log in and
permitting unlimited download any music they
downloads for a like for a fixed price every
monthly fee month
Kevin Ninh Xuan Bao Hung Purchase music We will create gift cards for
download gift cards. customers to give to relatives
or friends to share the music

Person Interviewed Interviewer Requirement Explaining its needs

13
Beru Ninh Xuan Bao Hung The system should be We want to create a system
able to work on any that can be accessed by any
Web Browser browser
Nata Ninh Xuan Bao Hung The system can be we work 24/7 so that people
used 24 hours a day in other countries can buy
tune source products at any
time.
Cris Ninh Xuan Bao Hung The system supports We optimize the number of
300 people at the people logging in at the same
same time time so that there is no delay
Bi Ninh Xuan Bao Hung System updates status Quick information update
parameters within 3 system so customers can buy
minutes and view history quickly
Ken Ninh Xuan Bao Hung The system only uses We create a system that
dollars for makes it more convenient for
transactions foreign countries and users

P5b. Discuss the technique to obtain the requirements.

1. Intro purpose of this section
Techniques describe how tasks are performed under specific circumstances. A task may have
none or one or more related techniques. A technique should be related to at least one task.
2.Intro 5 requirement gathering techniques
a. Interview
- An interview is a conversation with stakeholders to elicit or validate needs and requirements.
An interview may include one or more stakeholders. The interview may also involve a question
and answer session used to discover other potential stakeholders and any discrepancies between
needs; the high-level requirements derived from those needs; and the resulting detailed
requirements. Interviews facilitate obtaining approval from stakeholders on their needs,
requirements, and any changes to them.
- Advantages :
+ Generally easy, because it can be done with minimal preparation.
+ Interviews of individuals and small groups require less planning and scheduling effort than
large workshops.
+ Interviews of individuals and small groups require less stakeholder commitment than large
workshops.
+ Interviews provide an opportunity to explore or clarify topics in more detail.
- Disadvantages :

14
+ The questions used in the interview may reflect the interviewer’s preconceived ideas, which
can influence the responses.
+ For projects with a large number of stakeholders the interviews technique can be time-
consuming and inefficient.
+ Conflicts and inconsistencies between stakeholder information need to be resolved in
additional interviews.
+ This technique does not allow different stakeholders to hear and elaborate upon the
information being relayed.
- Formal Interview Process Steps :
Step 1. Identify stakeholders to be interviewed
Step 2. Obtain a general understanding of the customers business
Step 3. Develop interview questions using open-ended questions
Step 4. Set meeting time and location for the interview
Step 5. Provide a set of questions to interviewees prior to the interview (if they will need to
prepare for the interview)
Step 6. Use one or more Recorders to accurately preserve results of the interview
Step 7. Provide results to interviewees for confirmation of content

- Informal Interview Process Steps :

Step 1. Identify stakeholders to be interviewed
Step 2. Obtain a general understanding of the customers business
Step 3. Develop interview questions (for interviewer’s use only) to make sure certain questions
are answered during the session
Step 4. Set up a casual meeting or telephone conversation time for the interview.
Step 5. Takes handwritten notes during the interview; avoid using electronic data capture.
Step 6. Provide results to interviewee for confirmation of content

b. Joint Application Development

- Joint Application Development is a process in which business information is gathered for the
development of new information technology systems or to improve user involvement or develop
and improve quality in systems.

15
- In this technique IT, specialists and business users collaborate in discussion, project
management and learning groups, talking about the new information system. With the
participation of both parties it is possible to develop and solve the requirements of the new
software system in an easier way. The meetings can be hours, days or weeks, depending on the
intensity of the workshops.
- Advantages of Joint Application Development
+ Allows collaboration between various professions to resolve conflicts
+ Avoids traditional interviews per person and thus saves time
+ Improves the system as the business users involved help to identify what is really needed based
on their needs. Thus achieving the product for the end customer
+ JAD proposes brainstorming sessions to get people to interact and think for the project
+ The joint collaboration between the company and the clients reduces all risks
+ It uses CASE tools in JAD workshops which improve the productivity of the session and
provides system analysts with discussed and ready-to-use models
- Disadvantages of Joint Application Development
+ Different opinions can make it difficult to organise objectives.
+ Depending on the size of the project the time in JAD sessions can have a more significant
commitment and take time from the people involved.

-Steps in Joint Application Development (JAD)

There are a number of steps to achieve Joint Application Development. The steps are mentioned
below:
Step 1: identify the objectives and constraints of the project
Step 2: identify the critical success factors
Step 3: define project deliverables
Step 4: define the schedule of workshop activities
Step 5: select participants
Step 6: prepare the workshop in advance
Step 7: organise the workshop activities and exercises
Step 8: prepare, inform and educate the participants

16
c. Questionnaires
- Questionnaires are web-based surveys that contain a series of questions asked with the intent of
gathering information from the respondents. In some cases, these are used to deliver information
to the employees and potential customers.
- In business marketing, online questionnaires play an important role. It helps in bringing about
significant improvements in the business processes. It can be used to get information about an
organization’s target audience and collect customer feedback about a particular product/service
- Advantages of Questionnaires
+ Help Understand Customer
+ Cost-Effective
+ Targeted Surveys
+ Fast Results
+ Scalable
+ Market Research
+ Smart Analysis
+ Simple to Administer
+ Uniform Format
+ Give Follow-Up Opportunities
+ Evergreen
+ Anonymous

- Disadvantages of Questionnaires
+ Incorrect Feedback
+ Reluctance Towards Sensitive Topics
+ Ignorance of Questions
+ Neglects Emotions
+ Different Interpretations
+ Survey Fatigue
+ Lack of Accessibility

17
+ Superficial Responses
+ Inaccuracy in Analyzing Open-Ended Questions
+ Use of Complicated Language
+ Survey May Appear Impersonal
+ Getting Too Personal

-Steps in Questionnaires
Step 1: Identify your research aims and the goal of your questionnaire
Step 2: Define your target respondents
Step 3: Develop questions
Step 4: Choose your question type
Step 5: Design question sequence and overall layout
Step 6: Run a pilot.

d. Document analysis
- Document analysis is a technique for collecting data from historical data that is recorded,
stored, managed and versioned in the form of documents.In the context of companies, historical
data refers to information that was created and documented in earlier projects and developments.
Document analysis – which is sometimes referred to as source analysis – includes not only
electronically stored documents, but also printed information that is not available on the intranet
or Internet.
- The broader the concept of document analysis, the more sources of information can be
identified:text files, spreadsheets, sketches, graphics, drawings, plans and also films or photos.

- Advantages
+ Document analysis helps you focus on the questions you might ask in interviews and also
helps you understand what to look out for with participant observation.
+ It is particularly useful when you want to drill down and focus on a particular case study, be it
a particular patient, school pupil, village, sub-sector or workshop.
+ It is relatively cost-effective and rapid where data is readily available (e.g. via the internet).

18
+ Documents offer specific and stable data, which is unaffected by the presence of researchers
(with participant observation by contrast, project participants may behave differently when they
know they are being observed).
- Disadvantages
+ Documents may not be complete or written in an objective fashion so you will have to adopt a
critical stance and not assume that the information contained within them is precise or unbiased.
+ The number of documents involved can lead to information overload. Which parts of which
document are most relevant to your question? Which is largely about the progress of your project
and the factors that have helped or hindered that progress?
+ Documents may need to be anonymised and scrutinised against other documents. Is the one
document that you end up using most representative or is it stating something very different to all
the other documents? If so, why is this? Is the source or research design or the purpose of the
document different?
+ Note that artifact analysis can be an alternative or complement to document analysis. It
involves interpreting different artifacts such as tools, sculptures, weapons or even pieces of
equipment. For ways of analysing such artifacts, see for example the National Archives website.

-Steps in Document analysis

Step 1. List your resources
Step 2. Decide how to organize the information
Step 3. Make copies for notes
Step 4. Ensure authenticity
Step 5. Check for biases
Step 6. Ask questions
Step 7. Evaluate the document

e. Observation
- The method of observation is qualitative. It is used to collect information by observing the
subjects in a natural environment and then analyzing the information. Observation is based on
behavioral patterns, psychological character, attitude and beliefs of the subject, etc.
- The observation method consists of watching, listening, touching, and recording the behavior,
attitude, and characteristics of objects or phenomena or living beings. By using this method, the

19
researchers try to understand and comprehend the behavior and psychological character of the
said subject.
- Advantages of the Observation Method
+ Directness: The main advantage of observation is its directness. We can collect data at the time
they occur. The observer does not have to ask people about their behavior and reports from
others.
+ Natural environment: Whereas other data collection techniques introduce artificiality into the
research environment, data collected in an observation study describe the observed phenomena
as they occur in their natural settings.

+ Longitudinal analysis : Since the observation is possible to be conducted in a natural setting,

the observer can conduct his or her study over a much longer period than with either the survey
or experiment.
+ Non-verbal behavior : Observation is decidedly superior to survey research, experimentation,
or document study for collecting data on non-verbal behavior. Some studies focus on individuals
who are unable to give verbal reports or to articulate themselves meaningfully.

- Disadvantages of the Observation Method

+ Lack of control: Despite the advantage as achieved from the natural environment, the
observation study, however, has little control over extraneous variables that may affect the data.
+ Difficulties in quantification : Measurement in observational studies generally takes the form
of observer’s un-quantified perceptions rather than the quantitative measures often used in the
survey and experimental studies.
+ Smallness in sample size
+ Because observational studies are generally conducted in-depth, with data that are often
subjective and difficult to quantify, the sample size is usually kept at a minimum.
+ No opportunity to learn past: In an observational study, there is no way to know the past. It is
also difficult to gather information on such topics as intentions, opinions, attitudes, or
preferences.

- Steps in observational
Step 1. Decide upon the goals of the study;

20
Step 2. Decide upon the group for subjects to be observed;
Step 3. Gain entry to the group;
Step 4. Gain rapport with the subjects being studied;
Step 5. Conduct the study by observing and recording field notes over weeks, months or even
years;
Step 6. Deal with crises that occur, such as confrontations with subjects who think you are some
sort of spy;
Step 7. Exit from the observational
Step 8. Analyze the data;
Step 9. Write a report presenting the findings.

3. Apply to tune source

- I choose Interview for tune source. Because the interview helps uncover the potential of and
any differences in needs, the high-level requirements stem from those needs, and the resulting
detailed requirements. Interview facilitates getting approval of their request and request if there
are any changes.

4.Interview note for Tune Source

Interview notes Approved by : John Margolis, Megan Taylor, and Phil Cooper
Person Interviewd : John Margolis, Megan Taylor, and Phil Cooper

Interviewer : Ninh Xuân Bảo Hưng

Purpose of Interview:

 Determine information requirements for future system

Summary of Interview:

 Search for music in our digital music archive.

 Listen to music samples.
 Purchase individual downloads at a fixed fee per download.

21
  Establish a customer subscription account permitting unlimited downloads for a monthly
fee.
 Purchase music download gift cards

Detailed Notes : See attached transcript

Interview notes Approved by : Carly Edwards, project sponsor

Person Interviewd : Carly Edwards, project sponsor

Interviewer : Ninh Xuân Bảo Hưng

Purpose of Interview:

 Calculate the full amount for the whole project

Summary of Interview:

Home funding requests must complete the project as soon as possible. If the project is
completed, I will receive $757,500 in revenue from personal music downloads, $950,000
in revenue from customer subscriptions, $205,000 for additional CD sales in store or
website and $153,000 in music download gift card revenue

Detailed Notes : See attached transcript

P6 Analysis the requirements that I identified in task 1

1.Intro purpose of this section
- The purpose of this section is to introduce the requirements model, and to apply it to the tune
source

22
2.Introduce about requirement modelling
- Requirements modeling is the process used in software development projects where requirements
and solutions constantly evolve through collaborative efforts and teamwork. By using this method
of cross-functional and self-organizing teams, you can ensure that your team meets the exact needs
of the stakeholders.

Requirements modeling comprises several stages:

- Scenario-based modeling

- Data modeling

- Flow-oriented modeling

- Class-based modeling

- Behavioral modeling

Intro Scenario-based modeling

- Scenario modeling examines a range of potential futures, instead of attempting to predict just one
future. While you don’t have structured data on future performance, like you do with the past, you
can use inputs and scenarios to see possible trends that you may encounter in the next few years
or decades

Intro data modeling

- Data modeling is the process of creating a visual representation of either a whole information
system or parts of it to communicate connections between data points and structures. The goal is
to illustrate the types of data used and stored within the system, the relationships among these data
types, the ways the data can be grouped and organized and its formats and attributes.

Intro Flow-oriented modeling

- The flow oriented modelling depicts how data objects are transformed at they move through the
system. It has Derived from structured analysis, flow models use the data flow diagram, a
modeling documentation that represent how input is transformed into output as data objects
move through the system. Each software function that transforms data (i.e collection of raw

23
facts) is described by a process specification. In addition to data flow, this modelling element
also represent control flow.

Intro class-base modeling

- Class-based modeling is a stage of requirements modeling. In the context of software

engineering, requirements modeling examines the requirements a proposed software application
or system must meet in order to be successful. Typically, requirements modeling begins with
scenario-based modeling, which develops a use case that will help with the next stages, like data
and class-based modeling. Class-based modeling takes the use case and extracts from it the classes,
attributes, and operations the application will use. Like all modeling stages, the end result of class-
based modeling is most often a diagram or series of diagrams, most frequently created using UML,
or rather, Unified Modeling Language.

Intro behavioral modeling

- Behavior Modeling, a component of Social Learning Theory, is the act of guiding the employees
how to do something by showing them the standard modeled behavior. This process is of the
premise that people tend to inevitably learn things they see in a hands-on way.

3.Apply requirement modelling to Tune Source

In this project I use object oriented analysis and design techniques (1 class diagram, 2 activity
diagrams, 2 sequence diagrams, 1 pseudocode) to design .

24
a. Class Diagram of Tune Source

25
b. Activity diagrams of search

26
c. Activity diagrams of try muscic

27
d. Sequence diagrams of search

28
e. Sequence diagrams of try music

f. pseudocode of try music

29
P7. Discuss how the user and software requirement are addressed in the design phase.
1.Intro purpose of this section
- In this part 7 . I will introduce the detail of the use case digram and apply them to Tune Source

2.Intro detail of use case diagram

- Use-case diagrams illustrate and define the context and requirements of either an entire system
or the important parts of the system. You can model a complex system with a single use-case
diagram, or create many use-case diagrams to model the components of the system. You would
typically develop use-case diagrams in the early phases of a project and refer to them throughout
the development process.

- Use-case diagrams are helpful in the following situations:

+ Before starting a project, you can create use-case diagrams to model a business so that all
participants in the project share an understanding of the workers, customers, and activities of the
business.

+ While gathering requirements, you can create use-case diagrams to capture the system
requirements and to present to others what the system should do.

+ During the analysis and design phases, you can use the use cases and actors from your use-case
diagrams to identify the classes that the system requires.

+ During the testing phase, you can use use-case diagrams to identify tests for the system.

- The following topics describe model elements in use-case diagrams:

Use cases

- A use case describes a function that a system performs to achieve the user’s goal. A use case
must yield an observable result that is of value to the user of the system.

Actors

- An actor represents a role of a user that interacts with the system that you are modeling. The user
can be a human user, an organization, a machine, or another external system.

Subsystems

30
- In UML models, subsystems are a type of stereotyped component that represent independent,
behavioral units in a system. Subsystems are used in class, component, and use-case diagrams to
represent large-scale components in the system that you are modeling.

Relationships in use-case diagrams

- In UML, a relationship is a connection between model elements. A UML relationship is a type

of model element that adds semantics to a model by defining the structure and behavior between
the model elements.

3.Apply to Tune Source

Apply major usce case to Tune Source

Apply elaborating use case to Tune Source

31
a. Search for music in our digital music archive.

b. Listen to music samples.

32
c. Purchase music download gift cards

33
d. Purchase individual downloads at a fixed fee per download.

34
 REFERENT
ibm.com (2020). Data Modeling [Online] Availiable at :https://www.ibm.com/cloud/learn/data-
modeling
synario.com(2022). Scenario Modeling. [Online] Availiable at : https://www.synario.com/scenario-
modeling-what-you-need-to-know/
celms.ap.gov.in(2022). Flow-Oriented Modelling . [Online] Availiable at
:https://ccelms.ap.gov.in/adminassets/docs/30112020110536-SE_3.5.6.2.5_text_.pdf

study.com (2022). Class-Based Data Modeling: Definition & Application. [Online] Availiable at
:https://study.com/academy/lesson/class-based-data-modeling-definition-
application.html#:~:text=Class%2Dbased%20modeling%20takes%20the,or%20rather%2C%20
Unified%20Modeling%20Language.
mbaskool.com (2022). Behavior Modeling Meaning, Process & Example. [Online] Availiable at
:https://www.mbaskool.com/business-concepts/human-resources-hr-terms/15104-behavior-
modeling.html
indeed.com (2022). 9 Nonfunctional Requirements Examples. [Online] Availiable at
:https://www.indeed.com/career-advice/career-development/non-functional-requirements-
examples
guru99.com(2022) . Functional Vs. Non Functional Requirements: Differences .[Online] Availiable at
:https://www.guru99.com/functional-vs-non-functional-requirements.html

opentextbc.ca(2022). 5. Stakeholder Management. [Online] Availiable at :

https://opentextbc.ca/projectmanagement/chapter/chapter-5-project-stakeholders-project-
management/
tutorialspoint.com(2022). Requirement Gathering Techniques. [Online] Availiable at
:https://www.tutorialspoint.com/business_analysis/business_analysis_requirement_gathering_tec
hniques.htm

35