Objectives:

Chapter 2: 1. Explain software requirements

Software and the role
Requirement of systemanalyst.
Analysis & 2.Describe requirement
engineering process.
Specification
3.Apply the concepts of structured
analysis.
HTTPS://WWW.TUTORIALSPOINT.COM/SOFTWARE_ENGINEERING/SOFTWARE_REQUIREMENTS.HTM
  The software requirements are description of features and
functionalities of the target system.
 Requirements convey the expectations of users from the
Introduction software product.
 The requirements can be known or unknown, expected or
unexpected from client’s point of view.
3.1 Software System Analyst:
 System analyst in an IT organization is a person, who
analyzes the requirements of proposed system and
ensures that requirements are documented properly &
correctly.
 Role of an analyst starts during Software Analysis Phase
of SDLC.
 It is the responsibility of analyst to make sure that the
developed software meets the requirements of the
client.
https://www.tutorialspoint.com/software_engineering/software_requirements.htm
  Analyzing and understanding requirements of
developing software/Project
Responsibilities  Understanding how the Software/Project will
of contribute in the organization objectives
System  Identify sources of requirement
 Validation of requirement
Analysts :  Develop and implement requirement management
plan
 Documentation of business, technical, process and
product requirements
 Coordination with clients to prioritize requirements
and remove ambiguity
 Finalizing acceptance criteria with client andother
stakeholders
  The process to gather the software
requirements from client, analyze and
3.2 document them is known as requirement
engineering.
Requirement  The goal of requirement engineering is to
Engineering: develop and maintain ‘System
Requirements Specification document
3.2.1 Requirement Engineering Process :
 Four step process, which includes:
1. Feasibility Study
2. Requirement Gathering
3. Software Requirement Specification
4. Software Requirement Validation
 • When the client approaches the
organization for getting the desired
product to be developed, he comes
3.2.1.1
up with rough idea about what all
Feasibility
functions the software must
Study:
perform and which all features are
expected from the software.
• From the above information, the
analysts does a detailed study about
whether the desired system and its
functionality are feasible to
develop.
• This feasibility study is focused towards goal of the
organization.
• This study analyzes whether the software product can be
practically materialized in terms of implementation, contribution
of project to organization, cost constraints and as per values and
objectives of the organization.
• It explores technical aspects of the project and product suchas
usability, maintainability, integration ability.
• The output of this phase should be a feasibility study
• productivity and report that should contain adequate comments
and recommendations for management to decide whether to
take up the project or not.
3.2.1.2 Requirement Gathering :
• If the feasibility report is positive towards undertaking the
project, next phase starts with gathering requirements
from the user.
• Analysts and engineers communicate with the client
and end-users to know their ideas on what the software
should provide, and which features they want the
software to include.
Requirement Elicitation Techniques:
o Requirements Elicitation(to bring out) is the process to find out the
requirements for a developing software system by communicating
with client, end users, system users and others who have a stake in the
software system development.
o There are various ways to find and finalize the requirements:
 • Interviews are strong ways to collect
requirements. Organization may conduct several
types of interviews such as:
• Structured (closed) interviews, where every
single information to gather is decided in
Interviews: advance.
• Non-structured (open) interviews, where
information to gather is not decided in advance,
more flexible and less biased.
• Oral interviews
• Written interviews
• One-to-one interviews which are held between
two persons.
• Group interviews which are held between groups
of participants. They help to uncover any missing
requirement as group of people are involved.
Example of Structured (Closed) Interviews:
Which of the following would you say is the one best thing
about the information system you currently use to do your job?
a. Having easy access to all of the data you need
b. The system’s response time
c. The ability to run the system concurrently with other
applications.
How many telephone orders are received per day?
How does customer place order?
How many personal computers do you have in this department?
Do you review the reports before they are sent out?
How many hours of training does a clerk receive?
Is the calculation procedure describe in the manual?
How many customers ordered products from the Web site last month?
Example of Non- Structured (Open) Interviews:
1. What would you say is the best thing about the information system you currently
use to do your job?
2. What do you think about the way invoices are currently process?
3. What are the problem encountered daily?
4. How is this task performed?
5. What added features would you like to have in the new billing system?
6. What are the critical objectives of your department?
Surveys:
Organization may conduct surveys among various
stakeholders by querying about their expectation and
requirements from the developing system.

Questionnaires:
A document with pre-defined set of objective questions
and respective options is provided to all stakeholders to
answer, which are collected and compiled later.
Problem of this technique is, if an option for some issue is
not mentioned in the questionnaire, the issue might be left
unattended.
Task Analysis:
• Team of engineers and developers may analyze the operation
for which the new system isrequired.
• Ifthe client already has some software to perform certain operation, it is
studied and requirements of proposed system are collected.

Domain Analysis:
 Every software belongs to some domain category.
 The expert people in the domain can help to analyze general and
specific requirements.
Brainstorming:
It is an informal debate held among various stakeholders and all their
inputs are recordedfor further requirementsanalysis.
Prototyping:
 Prototyping will build user interface without adding detail functionality for
user to interpret the features of developing software.
 It helps giving better idea of requirements.
 If there is no software installed at client’s end for developer’s reference and
the client is not aware of its own requirements, the developer creates a
prototype based on initially mentioned requirements.
 The prototype is shown to the client and the feedback is taken.
 The client feedback serves as an input for requirement gathering.

Observation
 Team of experts visits the client’s organization or workplace.
 They observe the actual working of the existing systems.
 They observe the workflow at client’s end and how execution problems
are dealt.
 The team itself comes with some conclusions which aid to form
requirements expected from the software.
 Summary of the Requirement Gathering Techniques

• Interview. A structured conversation where one participant asks questions, and

the other provides answers.
• Survey. To ask in order to collect data for the analysis of some aspect of a group
or area.
• Questionnaires. A document with pre-defined set of objective questions and
respective options.
• Task Analysis. Understanding tasks that are required for decision-making.
• Domain Analysis. The process of analyzing related software systems in a domain
to find their common part.
• Brainstorming. An informal debate among stakeholders where all inputs are
recorded.
• Prototyping. Building user interface without adding detail functionality.
• Observation. Immersion to the company in order to gain information.
3.2.1.3 Software Requirement Specification:

o SRS is a document created by system analyst after the

requirements are collected from various stakeholders.
o SRS defines how the developing software will interact with
hardware, external interfaces, speed of operation, response time of
system, portability of software across various platforms,
maintainability, speed of recovery after crashing, Security, Quality,
Limitations etc.
o The requirements received from client are written in natural/simple
language.
It is the responsibility of system analyst to document the
requirements in technical language so that they can be understand
and useful for the software development team.
 SRS should come up with following features:
 User Requirements are expressed in natural/simple
language.
 Technical requirements are expressed in
Software structured/technical language, which is used inside the
organization.
Requirement  Design description should be written in Pseudo code.
Specification:  Format of Forms and GUI screen prints.
 Conditional and mathematical notations for DFDs etc.
 • Gathering software requirements is the
foundation of the entire software
development project. Hence, they must be
clear, correct and well-defined.
A complete Software Requirement Specifications
must be:
Software • Clear
Requirement • Correct
Specification: • Consistent
• Coherent
• Comprehensible
• Modifiable
• Verifiable
• Prioritized
• Unambiguous
• Traceable
Software Requirements:
• We should try to understand what sort of requirements may retrieved
in the requirement elicitation phase and what kinds of requirements
are expected from the software system.
• Software requirements are categorized in two categories:
Functional Requirements:
Requirements, which are related to functional aspect of
software are functionalrequirements.
They define functions and functionality within and from the software
system.

 Search option given to student to search topics from various

resources.
 User should be able to mail any report to management.
 Users can be divided into groups and groups can be given
separate rights.
 Should comply business rules andadministrative functions.
 Software is developed keeping downward compatibility intact.
Non-Functional Requirements - are not related to functional aspect
of software are nonfunctional requirements.
They are implicit or expected characteristics of software, which users make
assumption of.
Non-functional requirements include–
o Security
o Storage
o Configuration
o Performance
o Cost
o Interoperability
o Flexibility
o Disasterrecovery
o Accessibility
Examples of Non-Functional Requirements
Performance Cost
• The CIMS must handle • The cost of backlog item
2,000 registration per
second.
is in product compliance
• The response time for all entry. Flexibility
requests must be less than 1 • Adding five modules in • The system can run on
second. the system is at still in handheld devices.
• The system must handle budget stocks. • He will receive a
1,000 transactions per verification e-mail,
second.
• The system has a
restrictions on which have a link to
• The system has the capacity
to refresh the screen every immediate and/or long- website.
• The purchasing system
15ms after any transactions. term cost.
• The interaction between must runs on a bar code
user and the system should scanner.
not exceed 2 sec. Interoperability • The system must have a
• The system must be able to •The advising and verification e-mail,
handle a peak load of thirty registration must works which have a link to
simultaneous users with no website.
more than five second
dependently to one
response times. another through LAN.
•The CIMS has an ability to
share database connection
to the Ministry of
Manpower.
Non-Functional Requirements
Disaster Recovery Accessibility Security
• System must have less than • The system must be a user- • The system Shall be password
1hr downtime per three friendly. protected.
months survivability. • The system must be • Only the ADMIN can access
• The system is automatically accessible to all type of users. the File Maintenance Module.
restart within 5s after the virus • The system has a page • Only direct managers can see
has been detected. navigation. personal records of staff.
• Upon payment, the card is • The CIMS has a HELP • The system shall ensure that
automatically disabled if feature. data is protected from
power or battery is shutdown. • The System has A FAQ in unauthorised access.
• If data or system is corrupt, it order that the user easily • The system shall include a user
has an automatic backup asked on the system. authorisation procedure where
system. • The system provides the users must identify themselves
• The CIMS must be able to training help. using a login name and
restart by itself within 10 password.
minutes after power
interruption. Storage
• The database capacity Configuration
is 5GB. The Online Shopping must
• The storage of each be able to "Update
transaction is 500K Customer" users may
megabytes. choose whether to display
• The transaction of previous name the
CIMS is running using customer has been known
64GB RAM. by.
3.2.1.4 Software RequirementValidation

After requirement specifications are developed, the requirements mentioned

in this document are validated.(Confirmed).

Usermight ask for illegal, impractical solution or experts may interpret

the requirements incorrectly, so validation is required.

Requirements can be checked against following conditions –

 If they can be practically implemented.
If they are valid and as per functionality and domain of software. If there
are any ambiguities.
 If they are complete.
 If they can be demonstrated.
3.3 Structured Analysis
Structured Analysis is a development method that allows the analyst to
understand the system and its activities in a logical way.
During Structured Analysis, various tools and techniques are
used for system development. They are −
 Data FlowDiagrams
 Decision Tables
 Structured English
Data Flow Diagram (DFD) is graphical representation of flow of data
in an information system.
 It is capable of showing incoming data flow, outgoing
data flow and stored data.
 The DFD does not mention anything about how data flows through
the system.
 There is a difference between DFD and Flowchart.
 The flowchart shows flow of control in program modules. DFDs
depict flow of data in the system at various levels.
 Logical DFD - Concentrates on the
system process, and flow of data in the
system.
Example: In a Banking software
Types of system, how data is moved between
DFD: differententities.(Customer,Accounts)
Physical DFD Show how the
data flow is implemented in thesystem.
It is more specific and closer to the
implementation.
Types of
DFD:
DFD Components:
DFD can represent Source, destination, storage and flow of data usingthe following set
of components -
Entities - Entities are source and destination of information data. Entities are
represented by rectangles with their respectivenames.
Process - Activities and actions taken on the data are represented by Circle or
Round-edgedrectangles.
Data Storage - There are twovariants:
1. Itcan either be represented asa rectangle withabsence
of both smallersides.
2. An open-sidedrectanglewithonlyone sidemissing.
Data Flow - Movementof data isshownby pointedarrows.
•Data movementisshownfromthe base of arrowas itssource towards head of the
arrowasdestination.
•Example:
 Components of purchasing order
 Components of customer profile
 Component of account number
Identifying a data flow
Example 1:
External Entity or Entity

 External entities describe the components that interact within the system. In
other words, define the sources and destinations of information that enter and
leave the system. An external entity represents persons, processes or
machines which produce data to be used by the system or receive data that is
output by the system. External entities are also known as terminators,
sources/sinks, and actors.
 Examples of external entities include:
 End User such as Student, Customer, Client
 Purchasing Department
 Inventory System
 Process
• Process is a discrete action that transforms input data to output data. Process is known as data
transforms. The process is identified as follows:
• It shows data transformation or change. A process can only exist once on a data flow
diagram.
• All processes must have inputs and outputs. In other words, a process is asked to do
something and then must deliver.
• Each process is always "running" and ready to accept data.
• Major functions of processes are computations and making decisions.
• Each process should represent one function or action.
• A data process cannot input or output discrete event flows (i.e., a data process should not
control the system, it should do the work).
• A process name should start with an active verb (e.g., Produce Items, Control Production).
• Processes should generally move from top to bottom and left to right.
• For example, top level process would be Process 1.0 next level of detail Processes
  Data stores are created to store information for later use.
They represent temporary or permanent repositories of
information that are inputs to or outputs of processes.
 For example, a data store is needed to store data that is
generated on a daily basis but is required for a process that
runs weekly.1 Data stores are usually derived from the entities.
 The data store creation must be as follow:
Data Store  Data stores are named with an appropriate name, not to
include the word "file".
 Only processes may connect with data stores.
 There can be two or more systems that share a data store.
 The name of the store as well as the number are recorded in
between lines as in figure:
Rules of DFD
Process
• No process can have only outputs (a miracle)
• No process can have only inputs (black hole)
• A process has a verb phrase label

 Data Store
• Data cannot be moved directly from one
store to another
• Data cannot move directly from an outside
source to a data store
• Data cannot move directly from a data store
to a data sink
• Data store has a noun phrase (label)
Common mistakes in DFDs
Levels of DFD
Level 0 DFD or Context Diagram :
• Highest abstraction level DFD is known as Level 0 DFD.
• Shows the entire information system as one diagram.
• Level 0 DFDs are also known as context level DFDs.

Context Diagram
The context diagram is the highest level in a data flow diagram that
represents the entire system, it can also show the internal data flows within
a system which contains the following:
One process (which represents the entire system)
All sources/sinks (external entities)
Data flows linking the process to the sources and sinks (external entities)
  DFD Rules— Context Diagram
• One process, numbered 0.
• Sources and sinks (external entities) as squares
• Main data flows depicted
•
DFD Rules - •
No internal data stores are shown
They are inside the system
Context • External data stores are shown as external entities

Diagram
Level 1 DFD:
• The Level 0 DFD is broken down into more specific, Level 1 DFD.
• Shows basic modules in the system and flow of data among various
modules.
• Mentionsbasic processes and sourcesof information.
• Level 1 diagram of DFD as it called system diagram describes the overall processing of
the system. It shows the major process or the functional requirements and the data
flows that are extend from the context diagram.
Level 2 DFD:
• Shows how data flows inside the modules mentioned in Level 1.
• Higher level DFDs can be transformed into more specific lower level
DFDs with deeper level of understanding unless the desired level of
specification is achieved.
  A student wants to register for a course in Course
Example No. Registration System. The student sends the
1: Draw DFD Application details containing the student’s details and
desired course details. The Registration System checks
Context (Level (Process) that the course is available from the course
0) and Level 1 file. If the course is available, the student is enrolled
(Process) in the course and it will be stored in the
Course Student file. The Registration System confirms
Registration (Process) the registration by sending a confirmation
note that they are registered for the course to the
student with the course schedule details. Or if the
course is unavailable the student is sent a rejection
note.
Example-1:

Solution
Example 3: You are required to create a DFD (Context Diagram-Level
0 and Level-1) Grocery Order System. Suppose you are given the
details of a small mail order (P) catalogue system through WhatsApp that
allows people to shop from home. When a customer receives the
catalogue (DF) and wants to buy something, they can telephone, fax or
email their order to the company. The company gets the order (P) and
sends the goods (DF) and an invoice (DF). When the customer receives
the goods with a delivery note, they send payment (P) and receive a
receipt (DF) for their payment.
 Context Diagram

DFD- Level 1
Example 2: You are required to create a DFD (Context Diagram-Level 0 and
Level-1) for Online hotel booking system. This system will be used by
customers who want to book a hotel room in advance. Customer can search for
rooms, types, prices, and availability from the Room file. In order to search,
customer must provide check-in and check-out dates. Based on the provided
dates, the system checks for the availability of rooms and its specifications.
Then, the system provides room status notification to the Customer. If room is
available, customer can book the room by making online payment (via debit or
credit card) and it will be stored in the Booking file. If payment is successful,
system will generate the payment receipt and booking confirmation number
will be given to the Customer. Customer can print the payment and
confirmation details.
Example No. 4 – Case Scenario (Classroom Exercise). Draw DFD Context(Level 0) and
Level 1 Diagram
Case Study: Payroll system
After completing the fact finding activities, the system analyst now understand how the current payroll system operates
and the new requirements of the system. The current system operates as following
The payroll system has 3 main processes.
Verify and update the timesheet
Salary calculation
Pay check preparation
Verify and update timesheet
When the timesheet is received from the head of department, the HR department clerks verify the timesheet and enter
the details of the timesheet into timesheet file. The leave details received from the head of departments are also will be
verified by the HR department clerks to prepare the updated timesheet and the leave details will be updated to Timesheet
file. The updated timesheet will be used to calculate the salary.
Salary calculation
To calculate the salary of employees, the updated timesheet from the timesheet file and the deduction details from the
deduction file will be used. The deduction details are updated to the deduction file by the accounting department’s loan
section.
After calculation, the salary details of each employee will be stored in salary file.
Pay check preparation.
The Pay check preparation process will be done by taking salary details stored in salary file. After preparing the pay
check, the salary statement will be sent to the employee and the payment report will be sent to bank. The bank will send
a check clearing report to the company to complete the payment process.
Example No. 8 – Case Scenario (Classroom Exercise). Draw DFD Context(Level 0) and
Level 1 Diagram
Billing System
The four main tasks in billing system are Take request, Prepare bill, Payment process and create
report
Take request
When the order is received from the customer, the employees will check the availability of the
items by taking the details from menu file. The restaurant staff will give the information about
availability of item. The details of the order will be sent to prepare the Bill.
Prepare Bill
The price details will be taken from the menu file. The quantity is entered and the system calculates
the total price for that item. The total order value is also calculated by the system. The bill will be
sent to the customer. The copy of the bill will be sent to the Accounting Department also. The bill
details will be stored in account file.
Payment process
The payment process will be done by taking the details of the invoice stored in accounts file. Every
week the company will deposit the money to bank account of different restaurants. The payment
details will be saved in payment file.
Create report
After completing the payment process the manager will prepare a weekly report by taking the
details from payment file and account file. The report will be sent to accounts department.
Example No. 5 – Case Scenario (Classroom Exercise). Draw DFD
Context(Level 0) and Level 1 Diagram- Kids Haven Day care
Registration and Assessment System
When parents come by with children we ask them to fill out application form. The
application form details includes child information and parent information. We have
to record the parent’s information in emergency contact file and child’s information in
the child file. Then, the child will be registered and the parents will receive the child’s
registration card.
Once the child has been registered, we need to place the child in a group, by getting
and analyze the abilities of the child and record the findings in the ability file. Then,
we are assessing (assessment) the child abilities and select the child appropriate
group with similar abilities and interests to place the child and stored in the ability file.
The assessment result will be given to the Parents. Then, we determine the tuition fee
and tell to the parents from the tuition file. Every month, the parents received a
monthly bill from the tuition file. When the parents make the payment, we will issue
them a receipt and stored in the tuition file.
Case Scenario No. 6(Classroom Exercise) - Online Tools for Construction
An online company sells tools for construction. The customers can place an order by
providing the order details into the system. Then, the system checks the stock availability
in the warehouse and provides order status to the customer. The system will generate a
shipping order to the warehouse. When the order is shipped, the warehouse will send
shipping confirmation to the system. The customer will make payment through
credit/debit card Details and the system will send an invoice. The system will generate an
inventory report to the Account Department.

Case Scenario No. 7. You are required to create a DFD (Context Diagram and level-1)for
elibrary system.
This system will be used by students who want to access the book online. A student has
to register first by providing student details in order to become a member of e-library. The
student details will be stored in the Student_Mem file. After registration, the student can
send the request to access the desired book from the e-book repository. The system will
check automatically into the ebook repository, if book found student will get the access of
his requested book. The system provides accessed book details to the Student. Another
hand, the ebook system manager has the rights to add the new books into the ebook
repository and has the option to generate the Book report that will be submitted to the
Library Manager of e-Book System.
3.3.2 Structured English
• Most programmers are unaware of software so they only
depend on what their managers tell them to do.
• It is the responsibility of software management team to provide correct
information to the programmers to develop correct code.
• Methods and Techniques which use graphs or diagrams, may are
sometimes interpreted differently by different people.
• So analysts and designers of the software come up with tools such as
StructuredEnglish.
• Itisthe description of what isrequired to code and how to
code it.
• Structured English helps the programmer to write error-free
code.
• Here, both Struc tured English and Pseudo-Code tries to
mitigate(reduce, lessen) the understanding gap.
• Structured English uses plain English words in structured
programming paradigm.
The following are some tokens of structured programming.
• So analysts and designers of the software come up with tools such as
StructuredEnglish.
• It is the description of what is required to code and how to
code it.
• Structured English helps the programmer to write error-free
code.
• Here, both Struc tured English and Pseudo-Code tries to
mitigate(reduce, lessen) the understanding gap.
• Structured English uses plain English words in structured
programming paradigm.
The following are some tokens of structured programming.
1. IF-THEN-ELSE,
2. DO-WHILE-UNTIL
• Analyst uses the same variable and data name, which are
stored in Data Dictionary, making it much simpler to write and
understand the code.
• Example of Customer Authentication in the online shopping
Example of Structured English
If customer pays advance then
Give 5% Discount
Else
If Bill Amount >=1000 RO then
If the customer is a regular customer then
Give 5% Discount
Else
No Discount
end if
Else
No Discount
end if
end if

52
Example No. 1:

A course registration system needs to follow two

conditions to allow student to take admission in advanced
diploma course. A student must need his/her CGPA >=2.5
and TOEFL score >= 4.5 for admission in advanced diploma
course. Student will not be given an admission, if he/she
fails to meet any one condition.
 Based on the scenario above, write the Structured
Example. 1: English statements and construct the Decision Table.

PROCESS 1.0 COMPUTE ADMISSION

READ CGPA, TOEFL
BEGIN IF
IF(CGPA >=2.5)&& (TOEFL>=4.5)THEN
ADMISSION ACCEPTED
ELSE
ADMISSION REJECTED
ENDIF
3.3.3 Decision Tables
• A Decision table represents conditions and the respective actions to be taken to
address them, ina structured tabular format.
• Itisa powerful tool to debug and prevent errors.
• Ithelps group of similar information into a single table and then by combining
tables itdelivers easy and convenient decision-making.
Creating Decision Table:
 To create the decision table, the developer must follow basic four steps:
 Identify all possibleconditions
 Determineactionsforallidentified conditions
 Create Maximum possiblerules
 Define action foreach rule

 Decision Tables should be verified by end-users and can later be

 simplified by eliminating duplicate rules and actions.
  In a supermarket, when paying your
bill amount, if your amount exceeds
RO.100, You have an option of Cash or
Credit Card. If you pay as cash, you
Example No. 1: will get 6% discount from your original
amount, but for Credit Card there is no
discount. When your amount is less
than RO.100 you will have to pay by
cash only with the discount of 3%.
 Conditions Values_________

Bill Amount 1) More than or Equal to R.O. 100

Example 1: Sol. 2) Less than R.O. 100

Mode of Payment 1) Cash

2) Credit Card
 Steps in Constructing Decision Table

Example 1: Sol.
 Steps in Constructing Decision Table

Example 1: Sol.
 Steps in Constructing Decision Table

Example 1: Sol.
 Steps in Constructing Decision Table

Example 1: Sol.
Example No. 1:

 Example 2: A course registration system needs to follow

two conditions to allow student to take admission in
advanced diploma course. A student must need his/her
CGPA >=2.5 and TOEFL score >= 4.5 for admission in
advanced diploma course. Student will not be given an
admission, if he/she fails to meet any one condition.
 Based on the scenario above, write the Structured English
statements and construct the Decision Table.
Example 2: Sol.
Conditions Rules
  Construct a Structured English for the Salary Payroll of Salaried
Type and Hours worked Type:
 Salaried Type will receive Pay base salary.
 Hours worked Type who are working less than 40 will calculate
hourly wage and produce absence report.
 Hours worked Type who are equal to 40 will calculate hourly
wage.
 Hours worked Type who are working greater than 40 will
calculate hourly wage and calculate overtime.
Example No. 2:
 Sohar Bakery Company sells merchandise to
wholesale and retail outlets. Wholesale
customers receive a two percent discount on
all orders. The company also encourages
Example No. 3: both wholesale and retail customers to pay
cash on delivery by offering a two percent
extra discount for this method of payment.
Another two percent discount is given on
orders of 50 or more units.
Example No. 3:
Example No. 4:
  Toys-unlimited decided to give discounts for their toys based on
the following criteria:
 VIP customers who will buy more than 10 items will get 20%
discounts.

Example No. 5:  VIP customers who will buy less than 10 items will get 10% discounts
 Regular customers who will buy more than 10 items will get 10%
discounts.
 Regular customers who will buy less than 10 items will get 0%
discounts
Example No. 6:

 Convert the following scenario into Structured

English and Decision Table.
 Criteria: If age of passenger is less than or equal to
Example No. 6: 2 years, he/she will get a discount of 80% on the
ticket for domestic flights. If age of passenger is
less than or equal to 2 years, he/she will get a
discount of 70% on international flights; otherwise,
he/she will get 50% on the ticket amount.
  Convert the following scenario into Structured
English and Decision Table.
Lulu Online Grocery decided to give discounts to their
customers in celebration of the National Day based on
the following criteria:
Example No. 7:  All new customers who purchased products below
300 OMR will receive 5% discount and 10% if above
300 OMR.
 All regular customers who purchased below 300
OMR will receive 7% discount and 15% if above 300
OMR.
 References…

http://www.tutorialspoint.com/
Recommended books :
 Sommerville, Ian, Software engineering. — 10th
ed,
 Pressman, Roger S, Software engineering: a
practitioner’s approach / Roger S. Pressman.8th
ed

https://www.tutorialspoint.com/software_engineering/software_requirements.htm