Requirements/Systems analyst
Person performing the tasks of determining
the requirements for a proposed software
system
(problem analysis) breaking down what the
customer wants into discrete requirements
Requirements
What is requirements?
An expression of desired behaviour
Deals with objects/entities, states they can be
in, and functions that are performed to change
state or object characteristics
Designates what behaviour the customer wants
without saying how the behaviour will be
realised
Requirements process
Asking questions
Examining current behaviour
Demonstrating similar systems
10
12
Requirements Elicitation
Critical part of the process
Stakeholders in Requirements
Elicitation Process
1.
2.
3.
4.
5.
6.
7.
Clients
Customer
Users
Domain Experts
Market Researchers
Lawyers or auditors
Software engineers or other technology experts
15
Stakeholders in Requirements
Elicitation Process
14
Stakeholders in Requirements
Elicitation Process
Clients
Pay for software to be developed
Ultimate stakeholders as they have final say on what
product does
Customers
Buy software after it is developed
Users
Experts on how current system works (most useful
features, features that need improvement)
Need to understand particular needs of special groups
(differently-abled individuals, persons unfamiliar with
16
computers, expert users)
Stakeholders in Requirements
Elicitation Process
Lawyers/auditors
Domain experts
Familiar with the problem that software must automate
(financial expert for a financial package, meteorologist
for software to model weather)
Also know about kinds of environment to which
product will be exposed
Market Researchers
Conduct surveys to determine future trends and
potential customers needs
17
18
19
20
1. Interviewing stakeholders
22
24
Fit criteria
Objective standards for judging whether a
proposed solution satisfies the requirements
25
26
Process constraint
28
30
Different Purposes of
Requirements
Requirements analysts
and their clients
Designers
Test team
Maintenance team
Requirements Documents
1. Requirements Definition
To explain their
understanding of how the
system would behave
Used as constraints on what
would be considered an
acceptable solution
To derive a suite of
acceptance tests
To help ensure that the
system enhancements do
not interfere with the
systems original intent
2. Requirements Specification
31
Characteristics of Requirements
Characteristics of Requirements
1.
2.
3.
4.
5.
6.
7.
8.
1. Correctness
Correctness
Consistency
Unambiguity
Completeness
Feasibility
Relevance
Testability
Traceability
2. Consistency
3. Unambiguity
33
Characteristics of Requirements
34
Characteristics of Requirements
5. Feasibility
4. Completeness
32
6. Relevance
7. Testability
8. Traceability
35
Purpose of characteristics
Purpose of characteristics
38
40
39
41
42
43
44
45
46
47
48
49
50
51
52
53
54
Questions
What are crucial process steps of requirement
engineering ? Discuss with the help of a diagram
What do you understand with the term
requirements elicitation?
What are components of a use case diagram.
Explain their usage with the help of an example
Draw the ER diagram for a hotel reception desk
management
56
55
ADD INVENTORY
Thank you
ADD FAULTY
DAMAGED INVENTORY
ADD SITE ID
SHIPPED INVENTORY
REMOVED INVENTORY
CURRENT INVENTORY
INVENTORY ANALYSIS
TRENDING
USER INTERFACE
57
SITE MANAGEMENT
SPARE MANAGEMENT
DATABASE
ACTIVE WORKS
PRE-SUBMISSION
USER INTERFACE
PLANNED WORKS
SUPPORT ENGINEERS
COMPLETED WORKS
PLANNED WORKS
Diagram 3
58
ACTIVE OUTAGE
C
U
S
T
O
M
E
R
A
R
E
A
PRE-SUBMISSION
OUTAGE REPORT
SUPPORT ENGINEERS
RESTORED OUTAGES
OUTAGE REPORTING
59
60
10
SRS
ID
Name
Semester Details with Year and Month
List of Courses
Grades obtained
CGPA for that semester
61
62
ID
Name
Semester Details with Year and Month
List of Courses
Grades obtained
CGPA for that semester
63
64
66
11
Develop DFDs
Develop E-R Diagrams
68
12