Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
CHAPTER 1
SOFTWARE REQUIREMENT
FUNDAMENTALS
Requirements Determination
Objectives
Understand how to create a requirements definition.
Become familiar with requirements analysis techniques.
Understand when to use each requirements analysis
technique.
Understand how to gather requirements using interviews,
JAD sessions, questionnaires, document analysis, and
observation.
Understand when to use each requirements-gathering
technique.
ISS 2113 SOFT. REQ, CHAPTER 1
What is a Requirement
A requirement is a statement of what
the system must do or
characteristics it must have
written from businessperson perspective (what of
characteristics
their management.
Risk assessment, prioritization, monitoring,
mitigation and control. (Elaboration on the
technical and non-technical project risks will be
included in the software project plan document).
Description of the different types of product users
and other stakeholders.
Context and environment in which the product will
be operating.
ISS 2113 SOFT. REQ, CHAPTER 1
Product vision
Clear statement of the product goals.
Capture the views of possibly many stakeholders and types of
users
Identify main functionalities and product features
List all the assumptions and dependencies
System Requirements
System requirements specifications that define the new
system
Functional requirements
Activities system must perform (use cases)
Based on procedures and business functions
Documented in analysis models
Nonfunctional requirements
Technical requirement hardware and software
Performance requirement workload measures
Usability requirement user interface, workflow
Reliability requirement outages, error detection
Security requirement access & protection
ISS 2113 SOFT. REQ, CHAPTER 1
Types of Models
Different types of models are used in information
systems development
Mathematical formulas that describe
technical aspects of the system
Descriptive narrative memos, reports, or lists
that describe aspects of the system
Graphical diagrams and schematic
representations of some aspect of the system
StakeholdersThe Source of
System Requirements
People with interest in successful system
implementation
Three primary groups of stakeholders
Users (use system)
Clients (pay for and own system)
Technical staff (ensure system operation)
Stakeholders
Who do you involve and talk to?
Stakeholders persons who have an interest in the
Quantifiable Requirements
Avoid vague and unverifiable requirements which
requirements
THE END