Week 7 Lecture Notes
Requirements and Analysis Workflows Revisited
Software Engineering I (CSCI 3250)
Spring 2007
Inputs
Outputs
Who is involved?
Primary focus
Other activities
Language
UML notations
How accomplished
Requirements Workflow
Problem specification
(written out, oral
description, idea); vision
statement (developed by
developer company to use
to determine business
sense
Set of elicited requirements
Customers (users, clients),
system analysts and
requirements team
To determine the client’s
needs by eliciting both
functional and
nonfunctional requirements
To gain an understanding
of the application domain
Requirements written in
general language
Use case diagram
Used to elicit requirements:
interviews, joint application
language (JAD),
questionnaires, forms
analysis, observation,
scenarios
Analysis Workflow
Set of elicited
requirements
Software Requirements
Specification (SRS)
document
Customers (users,
clients), system analysts
and requirements team
To analyze and refine the
requirements (to build
SRS)
To determine classes
involved in application
domain
Requirements written in
precise language
Class diagram
In determining classes:
look for entity, boundary,
or control classes; use
noun identification, input
needs, and brainstorming