Beruflich Dokumente
Kultur Dokumente
Engineering
Lecture
2:
So5ware
Requirements
and
Requirement
Types
User
Quality
Requirements
A^ributes
b)
User
Requirements
- Describe
tasks
or
goals
that
specific
classes
of
users
must
be
able
to
perform
with
the
product.
- Describe
what
the
user
will
be
able
to
do
with
the
system.
- Valuable
ways
to
represent
user
requirements
include
use
cases,
scenario
descripEons,
or
user
stories.
c)
FuncDonal
Requirements
- Specify
the
so5ware
funcEonality
that
the
developers
must
build
into
the
product
to
enable
users
to
accomplish
their
tasks,
thereby
saEsfying
the
business
requirements.
- These
are
the
tradiEonal
"shall"
statements.
- They
are
also
called
behavioral
requirements.
- They
are
documented
in
the
so5ware
requirements
specificaEon
(SRS).
UAZ
-‐
Requirements
Engineering
Course
14
Requirements
Types
Examples?
d)
System
Requirements
- Describe
the
top-‐level
requirements
for
a
product
that
contains
mulEple
subsystems
- A
system
can
be
all
so5ware
or
it
can
include
both
so5ware
and
hardware
subsystems.
e)
Business
Rules
- Include
corporate
policies,
government
regulaEons,
industry
standards,
accounEng
pracEces,
and
computaEonal
algorithms.
- In
general,
they
exist
outside
the
boundaries
of
any
specific
so5ware
system.
- Restrict
who
can
perform
certain
use
cases
or
they
dictate
that
the
system
must
contain
funcEonality
to
comply
with
the
perEnent
rules.
UAZ
-‐
Requirements
Engineering
Course
16
Requirements
Types
Examples?
e)
Quality
AGributes
- Augment
the
descripEon
of
the
product's
funcEonality
by
describing
the
product's
characterisEcs
in
various
dimensions
that
are
important
either
to
users
or
to
developers.
- These
characterisEcs
include
a^ribu^es
such
as
usability,
portability,
integrity,
efficiency,
or
robustness.
f)
Constraints
- Impose
restricEons
on
the
choices
available
to
the
developer
for
design
and
construcEon
of
the
product.