The document discusses the requirements analysis and specification phase of software development. This phase has two main goals: 1) fully understand the user requirements through gathering and analyzing requirements, and 2) document the requirements properly in a Software Requirements Specification (SRS) document. The SRS document forms the basis for future development activities. It systematically organizes the functional and non-functional requirements as well as any constraints into a clear and unambiguous specification.
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Honest Reviews of Tim Han LMA Course Program.pptxtimhan337
Personal development courses are widely available today, with each one promising life-changing outcomes. Tim Han’s Life Mastery Achievers (LMA) Course has drawn a lot of interest. In addition to offering my frank assessment of Success Insider’s LMA Course, this piece examines the course’s effects via a variety of Tim Han LMA course reviews and Success Insider comments.
More Related Content
Similar to 3.Requirements gathering and Analysis_SRS _Functional and Non Functional Requirements.ppt
How to Make a Field invisible in Odoo 17Celine George
It is possible to hide or invisible some fields in odoo. Commonly using “invisible” attribute in the field definition to invisible the fields. This slide will show how to make a field invisible in odoo 17.
Honest Reviews of Tim Han LMA Course Program.pptxtimhan337
Personal development courses are widely available today, with each one promising life-changing outcomes. Tim Han’s Life Mastery Achievers (LMA) Course has drawn a lot of interest. In addition to offering my frank assessment of Success Insider’s LMA Course, this piece examines the course’s effects via a variety of Tim Han LMA course reviews and Success Insider comments.
Macroeconomics- Movie Location
This will be used as part of your Personal Professional Portfolio once graded.
Objective:
Prepare a presentation or a paper using research, basic comparative analysis, data organization and application of economic information. You will make an informed assessment of an economic climate outside of the United States to accomplish an entertainment industry objective.
Welcome to TechSoup New Member Orientation and Q&A (May 2024).pdfTechSoup
In this webinar you will learn how your organization can access TechSoup's wide variety of product discount and donation programs. From hardware to software, we'll give you a tour of the tools available to help your nonprofit with productivity, collaboration, financial management, donor tracking, security, and more.
Francesca Gottschalk - How can education support child empowerment.pptxEduSkills OECD
Francesca Gottschalk from the OECD’s Centre for Educational Research and Innovation presents at the Ask an Expert Webinar: How can education support child empowerment?
Operation “Blue Star” is the only event in the history of Independent India where the state went into war with its own people. Even after about 40 years it is not clear if it was culmination of states anger over people of the region, a political game of power or start of dictatorial chapter in the democratic setup.
The people of Punjab felt alienated from main stream due to denial of their just demands during a long democratic struggle since independence. As it happen all over the word, it led to militant struggle with great loss of lives of military, police and civilian personnel. Killing of Indira Gandhi and massacre of innocent Sikhs in Delhi and other India cities was also associated with this movement.
Palestine last event orientationfvgnh .pptxRaedMohamed3
An EFL lesson about the current events in Palestine. It is intended to be for intermediate students who wish to increase their listening skills through a short lesson in power point.
Biological screening of herbal drugs: Introduction and Need for
Phyto-Pharmacological Screening, New Strategies for evaluating
Natural Products, In vitro evaluation techniques for Antioxidants, Antimicrobial and Anticancer drugs. In vivo evaluation techniques
for Anti-inflammatory, Antiulcer, Anticancer, Wound healing, Antidiabetic, Hepatoprotective, Cardio protective, Diuretics and
Antifertility, Toxicity studies as per OECD guidelines
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...Levi Shapiro
Letter from the Congress of the United States regarding Anti-Semitism sent June 3rd to MIT President Sally Kornbluth, MIT Corp Chair, Mark Gorenberg
Dear Dr. Kornbluth and Mr. Gorenberg,
The US House of Representatives is deeply concerned by ongoing and pervasive acts of antisemitic
harassment and intimidation at the Massachusetts Institute of Technology (MIT). Failing to act decisively to ensure a safe learning environment for all students would be a grave dereliction of your responsibilities as President of MIT and Chair of the MIT Corporation.
This Congress will not stand idly by and allow an environment hostile to Jewish students to persist. The House believes that your institution is in violation of Title VI of the Civil Rights Act, and the inability or
unwillingness to rectify this violation through action requires accountability.
Postsecondary education is a unique opportunity for students to learn and have their ideas and beliefs challenged. However, universities receiving hundreds of millions of federal funds annually have denied
students that opportunity and have been hijacked to become venues for the promotion of terrorism, antisemitic harassment and intimidation, unlawful encampments, and in some cases, assaults and riots.
The House of Representatives will not countenance the use of federal funds to indoctrinate students into hateful, antisemitic, anti-American supporters of terrorism. Investigations into campus antisemitism by the Committee on Education and the Workforce and the Committee on Ways and Means have been expanded into a Congress-wide probe across all relevant jurisdictions to address this national crisis. The undersigned Committees will conduct oversight into the use of federal funds at MIT and its learning environment under authorities granted to each Committee.
• The Committee on Education and the Workforce has been investigating your institution since December 7, 2023. The Committee has broad jurisdiction over postsecondary education, including its compliance with Title VI of the Civil Rights Act, campus safety concerns over disruptions to the learning environment, and the awarding of federal student aid under the Higher Education Act.
• The Committee on Oversight and Accountability is investigating the sources of funding and other support flowing to groups espousing pro-Hamas propaganda and engaged in antisemitic harassment and intimidation of students. The Committee on Oversight and Accountability is the principal oversight committee of the US House of Representatives and has broad authority to investigate “any matter” at “any time” under House Rule X.
• The Committee on Ways and Means has been investigating several universities since November 15, 2023, when the Committee held a hearing entitled From Ivory Towers to Dark Corners: Investigating the Nexus Between Antisemitism, Tax-Exempt Universities, and Terror Financing. The Committee followed the hearing with letters to those institutions on January 10, 202
Acetabularia Information For Class 9 .docxvaibhavrinwa19
Acetabularia acetabulum is a single-celled green alga that in its vegetative state is morphologically differentiated into a basal rhizoid and an axially elongated stalk, which bears whorls of branching hairs. The single diploid nucleus resides in the rhizoid.
2. 2
Requirements Analysis and
Specification
Goals of requirements analysis and
specification phase:
fully understand the user
requirements
remove inconsistencies, anomalies,
etc. from requirements
document requirements properly in
an SRS document
4. 4
Requirements Analysis and
Specification
The person who undertakes
requirements analysis and specification:
known as systems analyst:
collects data pertaining to the product
analyzes collected data:
to understand what exactly needs to be
done.
writes the Software Requirements
Specification (SRS) document.
5. 5
Requirements Analysis and
Specification
Final output of this phase:
Software Requirements
Specification (SRS) Document.
The SRS document is reviewed
by the customer.
reviewed SRS document forms
the basis of all future
development activities.
6. 6
Analyst gathers requirements
through:
observation of existing systems,
studying existing procedures,
discussion with the customer and
end-users,
analysis of what needs to be
done, etc.
Requirements Gathering
7. 7
Requirements Gathering
(CONT.)
In the absence of a working
system,
lot of imagination and creativity
are required.
Interacting with the customer to
gather relevant data:
requires a lot of experience.
9. 9
Analysis of the Gathered
Requirements
After gathering all the requirements:
analyze it:
Clearly understand the user requirements,
Detect inconsistencies, ambiguities, and
incompleteness.
Incompleteness and inconsistencies:
resolved through further discussions
with the end-users and the customers.
10. 10
Inconsistent requirement
Some part of the requirement:
contradicts with some other part.
Example:
One customer says turn off heater
and open water shower when
temperature > 100 C
Another customer says turn off
heater and turn ON cooler when
temperature > 100 C
11. 11
Incomplete requirement
Some requirements have been
omitted:
due to oversight.
Example:
The analyst has not recorded:
when temperature falls below 90 C
heater should be turned ON
water shower turned OFF.
12. 12
Analysis of the Gathered
Requirements (CONT.)
Requirements analysis involves:
obtaining a clear, in-depth
understanding of the product to
be developed,
remove all ambiguities and
inconsistencies.
ambiguities=incomplete information
13. 13
Analysis of the Gathered
Requirements(CONT.)
Several things about the project should
be clearly understood by the analyst:
What is the problem?
Why is it important to solve the problem?
What are the possible solutions to the
problem?
What complexities might arise while solving
the problem?
14. 14
Analysis of the Gathered
Requirements(CONT.)
After collecting all data regarding
the system to be developed,
remove all inconsistencies and
anomalies from the requirements,
systematically organize requirements
into a Software Requirements
Specification (SRS) document.
17. 17
Software Requirements Specification: A
Contract Document
Requirements document is a
reference document.
SRS document is a contract
between the development team and
the customer.
Once the SRS document is approved
by the customer,
any subsequent controversies are settled
by referring the SRS document.
18. 18
Software Requirements Specification:
A Contract Document
Once customer agrees to the SRS
document:
development team starts to develop the
product according to the requirements
recorded in the SRS document.
The final product will be acceptable to the
customer:
as long as it satisfies all the requirements
recorded in the SRS document.
19. 19
SRS Document (CONT.)
The SRS document is known as black-box
specification:
the system is considered as a black box
whose internal details are not known.
only its visible external (i.e. input/output)
behaviour is documented.
S
Input Data Output Data
20. 20
SRS Document (CONT.)
SRS document concentrates on:
what needs to be done
carefully avoids the solution (“how to do”)
aspects.
The SRS document serves as a contract
between development team and the
customer.
Should be carefully written
21. 21
Properties of a good SRS
document
It should be concise
and at the same time should not be
ambiguous.
It should specify what the system must do
and not say how to do it.
Easy to change or modifiable.,
i.e. it should be well-structured.
It should be consistent.
It should be complete.
22. 22
Properties of a good SRS
document (cont...)
It should be traceable
you should be able to trace which part of the
specification corresponds to which part of the
design and code, etc and vice versa.
It should be verifiable
23. 23
SRS Document (CONT.)
SRS document, normally
contains three important parts:
functional requirements,
Non functional requirements,
constraints on the system.
24. 24
SRS Document (CONT.)
It is desirable to consider every
system:
performing a set of functions {fi}.
Each function fi considered as:
transforming a set of input data to
corresponding output data.
Input Data Output Data
fi
25. 25
Example: Functional
Requirement
F1: Search Book
Input:
an author’s name:
Output:
details of the author’s books and the
locations of these books in the library.
Author Name Book Details
f1
26. 26
Functional Requirements
Functional requirements
describe:
A set of high-level requirements
Each high-level requirement:
takes in some data from the user
outputs some data to the user
Each high-level requirement:
might consist of a set of
identifiable functions
27. 27
Functional Requirements
For each high-level requirement:
every function is described in terms
of
input data set
output data set
processing required to obtain the
output data set from the input data
set
30. 30
Constraints
Constraints describe things that the
system should or should not do.
For example,
standards compliance
how fast the system can produce results
• so that it does not overload another
system to which it supplies data, etc.
31. 31
Examples of constraints
Hardware to be used,
Operating system
or DBMS to be used
Capabilities of I/O devices
Standards compliance
Data representations
by the interfaced system
32. 32
Organization of the SRS
Document
Introduction(purpose, scope,
environment)
Functional Requirements
Nonfunctional Requirements
External interface requirements
Performance requirements
Constraints
33. 33
Example Functional
Requirements
List all functional requirements
with proper numbering.
Req. 1:
Once the user selects the “search”
option,
he is asked to enter the key words.
The system should output details of all
books
whose title or author name matches any of
the key words entered.
Details include: Title, Author Name,
Publisher name, Year of Publication, ISBN
Number, Catalog Number, Location in the
Library.
34. 34
Example Functional Requirements
Req. 2:
When the “renew” option is selected,
the user is asked to enter his
membership number and password.
After password validation,
the list of the books borrowed by him
are displayed.
The user can renew any of the books:
by clicking in the corresponding renew
box.
35. 35
Req. 1:
R.1.1:
Input: “search” option,
Output: user prompted to enter the key words.
R1.2:
Input: key words
Output: Details of all books whose title or author
name matches any of the key words.
Details include: Title, Author Name, Publisher name, Year
of Publication, ISBN Number, Catalog Number, Location in
the Library.
Processing: Search the book list for the keywords
36. 36
Req. 2:
R2.1:
Input: “renew” option selected,
Output: user prompted to enter his
membership number and password.
R2.2:
Input: membership number and password
Output:
list of the books borrowed by user are
displayed. User prompted to enter books to be
renewed or
user informed about bad password
Processing: Password validation, search
books issued to the user from borrower list
and display.
37. 37
Req. 2:
R2.3:
Input: user choice for renewal of the
books issued to him through mouse
clicks in the corresponding renew box.
Output: Confirmation of the books
renewed
Processing: Renew the books selected
by the in the borrower list.
38. 38
Examples of Bad SRS
Documents
Unstructured Specifications:
Narrative essay --- one of the worst
types of specification document:
Difficult to change,
difficult to be precise,
difficult to be unambiguous,
scope for contradictions, etc.
Forward References:
References to aspects of problem
defined only later on in the text.
39. 39
Examples of Bad SRS
Documents
Overspecification:
Addressing “how to” aspects
For example, “Library member names should
be stored in a sorted descending order”
Overspecification restricts the solution space
for the designer.
Contradictions
Wishful thinking
Noise
40. 40
Summary
Requirements analysis and
specification
an important phase of software
development:
any error in this phase would affect
all subsequent phases of
development.
Consists of two different activities:
Requirements gathering and analysis
41. 41
Summary
The aims of requirements analysis:
Gather all user requirements
Clearly understand exact user requirements
Remove inconsistencies and
incompleteness.
The goal of specification:
systematically organize requirements
document the requirements in an SRS
document.