Scribd
Upload
16 views

Building The Analysis Model

this is software engineering

Uploaded by

inforocks86
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
16 views

Building The Analysis Model

this is software engineering

Uploaded by

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

Software Engineering

Subject code:19CS302
B.Tech III Year – I semester

UNIT II
Building the analysis model
Session VI

S.NYAMATHULLA
ASSISTANT PROFESSOR
DEPARTMENT OF INFORMATION TEHCNOLOGY
agenda /outcomes
Why Data Modeling concepts?
Data Objects
Data Attributes
Relationships
Class - Based Modeling
Specifying Attributes
Defining Operations
Why Data Modeling concepts?

Software Team create a data model.

A software engineer or analyst defines all data objects.

The entity-relationship diagram (ERD) addresses these issues and

represents all data objects.


Data Objects
A data object is a representation of composite information that must be
understood by software.
Width would not be a valid data object, but dimensions could be
defined as an object.
A data object can be an external entity. a thing (e.g., a report or a
display) an occurrence (e.g., a telephone call), event (e.g., an alarm), a
role (e.g., salesperson), an organizational unit (e.g., accounting
department), a place (e.g., a warehouse), or a structure (e.g., a file).
Data Objects
A data object encapsulates data only.

—there is no reference within a data object to operations that act on the


data.
Data Attributes
Data attributes define the properties of a data object and take on one of
three different characteristics:
name an instance of the data object
describe the instance, or
 make reference to another instance in another table
In addition, one or more of the attributes must be defined as an
identifier.
Data Attributes
Relationships
Data objects are connected to one another in different ways. Consider
the two data objects, person and car
class based modeling
Class-based modeling represents the objects that the system will
manipulate, the operations that will be applied to the objects to effect
the manipulation, relationships between the objects, and the
collaborations that occur between the classes that are defined
Identifying Analysis Classes
To identify classes by examining the usage scenarios developed as part
of the requirements model and performing a “grammatical parse” on
the use cases developed for the system to be built.
Classes are determined by underlining each noun or noun phrase and
entering it into a simple table
If the class (noun) is required to implement a solution, then it is part of
the solution space; otherwise, if a class is necessary only to describe a
solution, it is part of the problem space.
Identifying Analysis Classes
But what should we look for once all of the nouns have been
isolated?
External entities (e.g., other systems, devices, people)

Things (e.g., reports, displays, letters, signals)

Occurrences or events(e.g., division, group, team)

Roless (e.g., manager, engineer, salesperson)

Organizational unitss (e.g., division, group, team)

Placess (e.g., manufacturing floor or loading dock)

Structures (e.g., sensors, four-wheeled vehicles, or computers)


Specifying Attributes
Attributes describe a class that has been selected for inclusion
in the requirements model.
It is the attributes that define the class.
Specifying Attributes
baseball statistics for professional baseball players

The attributes of the class PLAYER

Professional baseball pension system

In the former, attributes such as name, position, batting average,


fielding percentage, years played, and games played
average salary, credit toward full vesting, pension plan options
chosen, mailing address,
Specifying Attributes
System class defined for SafeHome

Sensor information : system ID+ verification phone number+


system status.
 alarm response information: delay time+ telephone number

activation/deactivation information: master password+


number of allowable tries+ temporary password.
Defining Operations
Operations define the behavior of an object

operations that manipulate data in some way .

operations that perform a computation.

operations that inquire about the stateof an object.

operations that monitor an object for the occurrence of a


controlling event
Defining Operations
 SafeHome processing narrative(Example)

sensor is assigned a number and type” or “a master password is


programmed for arming and disarming the system.” These phrases
indicate a number of things.
That an assign() operation is relevant for the Sensor class.

 That a program() operation will be applied to the System class.

 That arm() and disarm() are operations that apply to System class.
Class-Responsibility-Collaborator

Class-responsibility-collaborator (CRC) modeling provides


a simple means for identifying and organizing the classes
that are relevant to system or product requirements.
Ambler describes CRC modeling in the following way:

A CRC model is really a collection of standard index cards that represent


classes.
The top of the card you write the name of the class.

In the body of the card you list the class responsibilities on the left and the
collaborators on the right
Class-Responsibility-Collaborator

The intent is to develop an organized representation of classes.

 Responsibilities are the attributes and operations that are relevant for the class.

Stated simply,

A responsibility is “anything the class knows or does”

Collaborators are those classes that are required to provide a class with the
information needed to complete a responsibility.
collaboration implies either a request for information or a request for some action
Class-Responsibility-Collaborator

A CRC model index card


Class Types

• Entity classes, also called model or business classes, are extracted directly
from the statement of the problem (e.g., Floor Plan and Sensor).

• Boundary classes are used to create the interface (e.g., interactive screen or
printed reports) that the user sees and interacts with as the software is
used.
Class Types

• Controller classes : manage a “unit of work” from start to finish. That is,
controller classes can be designed to manage .
The creation or update of entity objects;

The instantiation of boundary objects as they obtain information from entity


objects;
Complex communication between sets of objects;

Validation of data communicated between objects or between the user and the
application.
Collaborations
• Classes fulfill their responsibilities in one of two ways:
A class can use its own operations to manipulate its own attributes,
thereby fulfilling a particular responsibility, or
A class can collaborate with other classes.
Collaborations identify relationships between classes
Collaborations are identified by determining whether a class can fulfill
each responsibility itself
Collaborations
• Three different generic relationships between classes

• the is-part-of relationship


• the has-knowledge-of relationship
• the depends-upon relationship
Collaborations
A composite aggregate class
Associations and Dependencies
• Two analysis classes are often related to one another in some fashion
• In UML these relationships are called associations
• Associations can be refined by indicating multiplicity
• In many instances, a client-server relationship exists between two
analysis classes.
• In such cases, a client-class depends on the server-class in some way and a
dependency relationship is established
Associations and Dependencies
Multiplicity
Associations and Dependencies

Dependencies
Analysis Packages

Various elements of the analysis model (e.g., use-cases, analysis classes)


are categorized in a manner that packages them as a grouping
The plus sign preceding the analysis class name in each package
indicates that the classes have public visibility and are therefore
accessible from other packages.
A minus sign indicates that an element is hidden from all other
packages and a # symbol indicates that an element is accessible only to
packages contained within a given package.
Analysis Packages
conclusion
What Data Modeling concepts?
Data Objects
Data Attributes
Relationships
Class - Based Modeling
Specifying Attributes
Defining Operations

You might also like