Scribd
Upload
68 views24 pages

PUCIT - Lec14 PDF

This document discusses different methods for requirements engineering (RE). It describes that the RE process is usually guided by a requirements method, which are systematic ways of producing system models that act as bridges between analysis and design. There is no single ideal RE method. The document then discusses several modeling techniques used in RE methods, including data flow models, object-oriented approaches, and formal methods. It provides examples and explanations of each technique.

Uploaded by

MOHAMMAD HARIS
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
68 views24 pages

PUCIT - Lec14 PDF

This document discusses different methods for requirements engineering (RE). It describes that the RE process is usually guided by a requirements method, which are systematic ways of producing system models that act as bridges between analysis and design. There is no single ideal RE method. The document then discusses several modeling techniques used in RE methods, including data flow models, object-oriented approaches, and formal methods. It provides examples and explanations of each technique.

Uploaded by

MOHAMMAD HARIS
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

SRE -

Methods for Requirements


Engineering

Lecture 14
Role of Methods in RE

●
Process of requirements engineering (RE) is usually guided by a
requirements method
●
Requirement methods are systematic ways of producing system models
●
System models important bridges between the analysis and the design
process

No Ideal RE Method
Modeling Techniques

● Data Flow models


● Object-oriented
● Formal Methods
●
View-point oriented method
Data-Flow Models

Data-flow diagrams (DFDs) graphically represents the external entities,


processes, data-flow, and data stores

DFD notation:
DFD Example

Consider a simple library system intended to automate the issuing of library


items

The first data-flow diagram derived by the analyst represents the „target‟
system at its context level

The next level (level 1) of the data-flow diagram is constructed by


decomposing the library system bubble into sub-functions
Library system – context level DFD
Library system – Level 1 DFD
Object-oriented approaches
●
Objects: are major actors, agents, and servers in the problem space of the
system
● Such as an account, a sensor, a software design, a car , an organisation
● May be composite - composed of other objects

●
Class - An object is an instance of a class
●
For example, if “John Smith” is a bank customer, then bank customer is the
class and “John Smith” is an instance of the bank customer

Basic Concepts:
● Encapsulation
● Inheritance
●
Operations or Services
Encapsulation

● Packaging together of data and operations that manipulate the data


● Details of how the operation is performed hidden from user
● Prevents the unauthorised access of an object‟s data
Inheritance

●
Objects at a lower level in class hierarchy inherit the operations and
attributes of their parent(s)
●
Objects are able to incorporate data and/or operations specific to themselves
●
Inherits data from more than one parent is called multiple inheritance.
Illustration of object concepts
Messages
● Objects communicate by sending messages
● Message comprises:
● Name of receiver object
● Operation to be invoked
● Optional set of parameters
● When an object receives a message it causes an operation to be invoked
● The operation performs the appropriate method
Message passing
Steps in object-oriented method

Most methods based on the object-oriented model share certain common


analysis steps:
●
Identify core objects
●
Construct the object structures defining the associations between object
classes
●
Define the attributes associated with each object
● Determine the relevant operations for each object- define the messages that
may be passed between objects
Object-oriented notations
Step 1 – Initial classes identified
Step 2 – relationship between classes

We can identify the following relationships from the partial requirements:

● A library user borrows a library item


● A library item is recorded or published
● The system administrator registers the library user
● Library users are students, Staff and External
● The system administrator catalogues the library items
● The library assistant issues the library items
Step 2 - explained
Step 2 – Inheritance of Library User
Step 2 – Inheritance of Library Item
Step 3 – Identify the attributes
Attributes can be revealed by the analysis of the system requirements.

For example, it is a requirement that all library users must be registered before
they can use the library then The library user class has the attributes; Name,
Address and Library ID

Another example would be for library Items / books attributes i.e.; Title,
Description and IBAN
Step 4 – Object operations
This step is intended to describe operations to be performed on the objects

One way to explain object operations is through messages:


Formal Methods
●
Requirements specification techniques can be categorised on a “formality”
spectrum
●
Semi-formal and informal methods
● Use natural language, diagrams, tables and simple notation
● Include structured analysis and object-oriented analysis

●
Formal methods are based on mathematically formal syntax and semantics
●
Not widespread in the industry due to added complexity of mathematics
involved.
– Questions ?

You might also like