Download Requirements Analysis in Software Engineering: A Comprehensive Guide and more Lecture notes Software Engineering in PDF only on Docsity!
CHAPTER 3
REQUIREMENTS
ANALYSIS
SOURCE OF PP SLIDES :
- SOMMERVILLE, I. 2011. SOFTWARE ENGINEERING. 9 T H EDN. ADDISON-
WESLEY.
- LAMSWEERDE, A. V. 2011. REQUIREMENTS ENGINEERING: FROM SYSTEM
GOALS TO UML MODELS TO SOFTWARE SPECIFICATION. 2
N D ED.WILEY.
- WEIGERS, K. AND BEAT TY, J. 2013. SOFTWARE REQUIREMENTS. 3
R D EDN.
MICROSOFT PRESS.
- BENNETT, MCROBB AND FARMER: OBJECT ORIENTED SYSTEMS ANALYSIS AND
DESIGN USING UML, (4TH EDITION), CHAPTER 8, MCGRAW HILL, 2010.
LESSON OBJECTIVES:
Explain different classification of
requirements
Understand conceptual modeling
- (^) Introduce some notations defined in
the Unified Modeling Language(UML)
- (^) Understand architectural design and
requirements allocation
Understand some commonly used
requirements analysis approaches
REQUIREMENTS CLASSIFICATION (1)
- Analyst must classify the requirements to
various categories so that they can document
and use it appropriately
- Requirements can be classified on a number of
dimensions (next slide…)
REQUIREMENTS CLASSIFICATION (2)
Some common requirements classified
dimensions:
- (^) Functional or Nonfunctional Requirements (as
discussed in previous chapter – recall)
- (^) Product or Process Requirements (as discussed
in previous chapter – recall)
- (^) Data Requirements – eg…
- (^) External Interface Requirements – interface
requirements with hardwares, other softwares and
users
REQUIREMENTS CLASSIFICATION (4)
- Other classification may be appropriate
depending upon the organization’s normal
practice and the software application itself
- Reading : Text books and research from internet
on other classification of requirements …
REQUIREMENTS ANALYSIS: OUTLINE
Requirements Classification
Conceptual Modelling
- (^) Context Models
- (^) Interaction Models
- (^) Structural Models
- Behavioral Models
Architectural Design and Requirements Allocation
Requirements Negotiation
Requirements Analysis Approaches
CONCEPTUAL MODELING
- (^) Several kinds of models can be developed during
requirements analysis
- (^) Represent using some kind of graphical notation, which is
now almost always based on notations in the Unified
Modeling Language(UML)
- (^) Some common diagrams generated during requirements
analysis stage include:
- Use case diagram
- (^) State diagram UML Notation
- (^) Class diagram
- (^) Sequence diagram
- Data flow diagram
- (^) Data model
- (^) etc
CONCEPTUAL MODELING
i) Context Models
ii) Interaction Models
iii) Structural Models
iv) Behavioral Models
EXAMPLE : CONTEXT DIAGRAM
CONCEPTUAL MODELING
i) Context Models
ii) Interaction Models
iii) Structural Models
iv) Behavioral Models
CONCEPTUAL MODELING
Generally,
Data flow diagram (DFD) is a graphical representation of the
"flow" of data through an information system, modelling
its process aspects. A DFD shows what kind of information
will be input to and output from the system, where the data
will come from and go to, and where the data will be stored. It
does not show information about the timing of process or
information about whether processes will operate in
sequence or in parallel. {refer to SAD course for details}
Use case diagram at its simplest is a representation of a
user's interaction with the system that shows the
relationship between the user and the different use cases in
which the user is involved.
EXAMPLE : DATA FLOW DIAGRAM
Clinic System Clinic System
USE CASE DIAGRAM
Dispenser
Overview Use Case
Nurse
Maintain
Appointment
Dispense
Medicine
Nurse
Add
Appointment
Delete
Appointment
Edit
Appointment
Detail Use Case
NOTATION OF USE CASE DIAGRAMS
