lOMoARcPSD|45111667

OOSE LAB Manual - CCS356 OOSE

oose (Anjalai Ammal Mahalingam Engineering College)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Chola Raja ([email protected])
 lOMoARcPSD|45111667

Anjalai Ammal Mahalingam Engineering College

Kovilvenni-614 403
Department of Computer Science and Engineering

LAB MANUAL

Laboratory Course Code : CCS356

Laboratory Course Title : Object Oriented Software Engineering Laboratory

Semester : VI

Branch & Section : CSE ‘A’& ‘B’

Course Teacher : Mr.P.Dinesh

Department : CSE

Batch : 2023-2024

Academic Year : 2021-2025

Signature of the faculty Signature of the HOD

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

LIST OF EXPERIMENTS
1. Identify a software system that needs to be developed.
2. Document the Software Requirements Specification (SRS) for the identified system.
3. Identify use cases and develop the Use Case model.
4. Identify the conceptual classes and develop a Domain Model and also derive a Class
Diagram from that.
5. Using the identified scenarios, find the interaction between objects and represent them
Using UML Sequence and Collaboration Diagrams
6. Draw relevant State Chart and Activity Diagrams for the same system.
7. Implement the system as per the detailed design
8. Test the software system for all the scenarios identified as per the usecase diagram
9. Improve the reusability and maintainability of the software system by applying appropriate
design patterns.
10. Implement the modified system and test it for various scenarios
SUGGESTED DOMAINS FOR MINI-PROJECT
1. Passport automation system.
2. Book bank
3. Exam registration
4. Stock maintenance system.
5. Online course reservation system
6. Airline/Railway reservation system
7. Software personnel management system
8. Credit card processing
9. e-book management system
10. Recruitment system
11. Foreign trading system
12. Conference management system
13. BPO management system
14. Library management system

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

15. Student information system

TOTAL: 45 PERIODS
Requirements
HARDWARE REQUIREMENTS
Standard PC
SOFTWARE REQUIREMENTS
1. Windows 7 or higher
2. Rational Suite
3. ArgoUML that supports UML 1.4 and higher
4. Selenium, JUnit or Apache JMeter

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

INTRODUCTION
OBJECT-ORIENTED ANALYSIS AND DESIGN (OOAD)
Object oriented analysis and design is a software engineering approach which models the
system as interacting objects. Each object represents a system entity which plays a vital role
in building of that system.
Analysis
1. Analysis emphasizes an investigation of the problem and requirements, rather than a
solution.
2. “Analysis” is a broad term, best qualified, as in requirements analysis(an investigation of
the requirements) or object-oriented analysis(an investigation of the domain objects)
3. Analysis means do the right thing.
Design
1. The design emphasizes a conceptual solution (in software and hardware) that fulfills the
requirements, rather than its implementation. For example, a description of a database
schema and software objects.
2. Design ideas often exclude low level or “obvious” details.
3. Design means do the thing right.

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.1(a) IDENTIFY A SOFTWARE SYSTEM THAT NEEDS TO BE DEVELOPED

AIM
To develop a problem statement for the suggested domain of mini-project.

PROBLEM STATEMENT
A problem statement is a clear concise description of the issue(s) that need(s) to be
addressed by a problem solving team. It is used to center and focus the team at the beginning,
keeps the team on track during the effort, and is used to validate that the effort delivered an
outcome that solves the problem statement. It has a specific form:
 Vision - What is the problem? This should explain why the team is needed
 Issue Statement - one or two sentences that describe the problem using specific issues.
It is not a "lack of a solution" statement.
 Method - the process that will get followed to solve the problem.
The primary purpose of a problem statement is to focus the attention of the problem solving
team. However, if the focus of the problem is too narrow or the scope of the solution too
limited, the creativity and innovativeness of the solution can be stifled.A good problem
statement should answer these questions:
1. What is the problem? This should explain why the team is needed.
2. Who has the problem or who is the client/customer? This should explain who needs
the solution and who will decide the problem has been solved.
3. What form can the resolution be? What is the scope and limitations (in time, money,
resources, and technologies) that can be used to solve the problem?

RESULT

Thus the problem statement for the given mini-project is created.

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

SRS (Software Requirement Specifications) Document

A Software requirements specification (SRS), a requirements specification for a software

system, is a complete description of the behavior of a system to be developed and may include
a set of use cases that describe interactions the users will have with the software.

In addition it also contains non-functional requirements. Non-functional requirements impose

constraints on the design or implementation (such as performance engineering requirements,
quality standards, or design constraints).

The software requirements specification document enlists all necessary requirements that
are required for the project development. To derive the requirements we need to have clear
and thorough understanding of the products to be developed. This is prepared after detailed
communications with the project team and customer.

The purpose of the SRS is to:

1. Establish the basis for agreement between the customers and the suppliers on what
the software product is to do.

2. Provide a basis for developing the software design.

3. Reduce the development effort.

4. Provide a basis for estimating costs and schedules.

5. Provide a baseline for validation and verification.

6. Facilitate transfer.

7. Serve as a basis for enhancement.

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.2 (a) PROJECT CREATION USING RATIONAL SOFTWARE

AIM
To create a project in rationaladministrator using rational software.
RATIONAL ADMINISTRATOR
Rational Administrator is a tool for managing association between Rational Aircrafts
such as Test Data stores, Requisite pro project, clear quest databases and Rose Models with
the help of Rational Administrator. It is used to create and manage rational projects and also
create and maintain the rational users and groups.It upgrade the project asserts, such as
requisite pro database and test data store.
PROCEDURE
1. Choose rational administrator from rational suite enterprise.
2. Right click on the “projects “tree and create a new project.
3. For the new project created, the assets for requirement i.e. requisite pro and test data
store assets are created.
4. After creation, the project in the rational administrator is connected to requisite pro and
test data store.
5. The templates used for creating requirements are the use case template.
6. When the project is available in the administrator, it can be connected to any tool.
7. From the rational administrator, the test data store is connected to the project .It contains
trees new test users and new groups.
8. New users can be inserted by right click option of the trees.
9. The user can be assigned to one or more groups. The privileges of groups are assigned to
users privileges.
10. The group can also be assigned to administrator privileges.
RESULT
Thus a new project,users and new groups are created and the privileges are assigned
for the project created and connected in rational administrator.
SAMPLE VIVA QUESTIONS

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

1. What is rational software?

2. What is test data?
3. What is business modeling?

Ex No.2(b) CREATION OF SOFTWARE REQUIREMENT SPECIFICATION USING

RATIONALR EQUISITE PRO

AIM
To analyze the requirement for a project created in rational administrator and to
create new packages, documents and views for the project using Rational Requisite Pro.
REQUIREMENT ANALYSIS
The purpose of system requirement analysis is to obtain a through and detailed
understanding of business needs as defined in project organization and captured in business
case and to break if down into discrete requirements, which are then clearly defined,
reviewed and agree upon with the customers and decision makers. During the system
requirement analysis the framework for the application is developed and providing the
foundation for future design and development efforts.
Requirement analysis is also called as requirement engineering which is the process of
determining user expectation for new or modified project. These features are called
requirement it must be quantifiable. In software engineering such requirement are often
called as functional specification.
Requirement Analysis is an aspect in Management. It is a team effort and that demands
a co-ordination of hardware, software and human efforts. Rational requisite pro is a powerful
and integrated requirement management tool that is easy to use and provides better
requirement specification view.
REQUIREMENT VIEWS
1. Attribute Matrix
This matrix provides a precise visualization of requirements, priority, cost,
status and the unique ID created for each of these.
2. Traceability Matrix
It is a 2-D with rows & columns for the requirements selected. It is a pictorial
view of the hierarchy in the analysis.

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

3. Traceability INTO
It is an extension of traceability matrix where only the requirements that is
traced to parent is viewed as a tree.

4. Traceability OUT OF
It is another extension of traceability matrix in which only the requirements
that trace the child are depicted.

PROCEDURE
1. Open the project that is created in rational administrator in exclusive mode.
2. Choose the requirement type necessary for the project.
3. Configure the documents and document types.
4. Confirm the attributes for the project selected and finally enumerate the requirements
that are satisfied.
5. A new package is created or the project. This package holds all the documents and
view necessary for the user verification.
6. Under the packages a new document is created .This is used to preserve all the revision
history of the project.
7. For the document, four different kinds of views are created for the requirements.
8. The views provide an inherent list of the requirement attributes and traceability of the
requirements.
SOFTWARE REQUIREMENTS SPECIFICATION (SRS)
2.1 INTRODUCTION
Passport Automation System is an interface between the Applicant and the Authority
responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of
Passport and reduces the complexities involved in it to the maximum possible extent.
2.1.1 PURPOSE
If the entire process of 'Issue of Passport' is done in a manual manner then it would
take several months for the passport to reach the applicant. Considering the fact that the
number of applicants for passport is increasing every year, an Automated System becomes
essential to meet the demand. So this system uses several programming and database

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

techniques to elucidate the work involved in this process. As this is a matter of National
Security, the system has been carefully verified and validated in order to satisfy it.
2.1.2 SCOPE
The System provides an online interface to the user where they can fill in their
personal details. The authority concerned with the issue of passport can use this system to
reduce his workload and process the application in a speedy manner. Provide a
communication platform between the applicant and the administrator Transfer of data
between the Passport Issuing Authority and the Local Police for verification of applicant's
information.
2.1.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
1. Administrator - Refers to the super user who is the Central Authority who has been
vested with the privilege to manage the entire system. It can be any higher official in
the Regional Passport Office of Ministry of External Affairs.
2. Applicant - One who wishes to obtain the Passport.
3. PAS - Refers to this Passport Automation System.
2.1.4 REFERENCES IEEE Software Requirement Specification format.
2.1.5 TECHNOLOGIES TO BE USED • Microsoft Visual Basic 6.0
2.1.6 TOOLS TO BE USED • Rational Rose tool (for developing UML Patterns)
2.1.7 Overview
SRS includes two sections overall description and specific requirements - Overall
description will describe major role of the system components and inter-connections. Specific
requirements will describe roles & functions of the actors.
2.2 OVERALL DESCRIPTION
2.2.1 PRODUCT PERSPECTIVE
The PAS acts as an interface between the 'applicant' and the 'administrator'. This
system tries to make the interface as simple as possible and at the same time not risking the
security of data stored in. This minimizes the time duration in which the user receives the
passport.
2.2.2 SOFTWARE INTERFACE
1. Front End Client - The applicant and Administrator online interface is built using
Microsoft Visual Basic 6.0.

10

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

2. Back End – MS Access database

2.2.3 HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have access
to the database in the server.
2.2.4 SYSTEM FUNCTIONS
1. Secure Registration of information by the Applicants.
2. Message box for Passport Application Status Display by the Administrator.
3. Administrator can generate reports from the information and is the only authorized
personnel to add the eligible application information to the database.
2.2.5 USER CHARACTERISTICS
1. Applicant - They are the person who desires to obtain the passport and submit the
information to the database.
2. Administrator - He has the certain privileges to add the passport status and to approve
the issue of passport. He may contain a group of persons under him to verify the
documents and give suggestion whether or not to approve the dispatch of passport.
3. Police - He is the person who upon receiving intimation from the PAS, perform a
personal verification of the applicant and see if he has any criminal case against him
before or at present. He has been vetoed with the power to decline an application by
suggesting it to the Administrator if he finds any discrepancy with the applicant. He
communicates via this PAS.
2.2.6 CONSTRAINTS
1. The applicants require a computer to submit their information.
2. Although the security is given high importance, there is always a chance of intrusion in
the web world which requires constant monitoring.
3. The user has to be careful while submitting the information. Much care is required.
2.2.7 ASSUMPTIONS AND DEPENDENCIES
1. The Applicants and Administrator must have basic knowledge of computers and
English Language.
2. The applicants may be required to scan the documents and send.
RESULT

11

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Thus the requirements specification, requirement views and packages for the project
created in rational administrator using rational requisite pro is analyzed successfully.

SAMPLE VIVA QUESTIONS

1. What is rational requisite pro?
2. What is functional specification?
3. What is requirement view?
4. What is a package?
5. What is requirement engineering?

12

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

UNIFIED MODELING LANGUAGE

DESIGN
Design has the great impact on the overall success of the software development
projects. A large pay off is associated with creating a good design up from before writing a
single code, while this is due to all programming classes and objects understand approach
even more good design usually simplifies the implementation and maintenance.During design
phase we must evaluate the model to actual objects that can be perform the required
tasks.There is a shift in emphasis from the application domain to implementation. The classes
during analysis provides as a framework for design phases.
MODELING
Building a model for a software system prior to its construction is as essential ashaving a
blueprint for building a large building. Good models are essential forcommunication among
project teams. A modeling language must include
 Model elements-fundamental modeling concepts and semantics.
 Notation-visual rendering of model elements.
 Guidelines-expression of usage within the trade

The use of visualnotation to represent or model a problem can provide us several benefits
relating toclarity, familiarity, maintenance, and simplification.
UNIFIED MODELING LANGUAGE
The Unified Modeling Language (UML) is a language for specifying,visualizing,
constructing, and documenting the artifacts ofsoftware systems and its components.The UML
is agraphical language with sets of rules and semantics. The rules and semantics of a modelare
expressed in English, in a form known as object constraint language(OCL). OCL is
aspecification language that uses simple logic for specifying the properties of a system.The
UML is not intended to be a visual programming language in the sense of having allthe
necessary visual and semantic support to replace programming languages.

13

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

UML DIAGRAMS
UML defines nine graphical diagrams
 Use-case diagram
 Class diagram
 Behavior Diagram
 Interaction Diagram
 Sequence Diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Implementation diagram
 Component diagram
 Deployment diagram.
RATIONAL ROSE
RequisitePro is a CASE tool from Rational that supports team-work based
requirements management.RequisitePro is integrated with Microsoft Word to capture
requirements documents.RequisitePro automates management of requirements traceability.
Traceability is a link or relationship between two requirements.
Rational rose enables visual modeling of software system architecture components
and data in a graphical representation.ROSE stands for Rational Object oriented Software
Engineering. Rational Rose is used for object-oriented analysis, modeling, design, and
construction.

14

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.3 UML- USE CASE DIAGRAM

AIM
To identify Use Cases and develop the Use Case model for the identified requirements
using Rational Enterprise Edition.
USE CASE DIAGRAM
A use-case diagramis a graph of actors, a set of use cases enclosed by a
systemboundary, communication (participation) associations between the actors and the
usecases, and generalization among the use cases. It shows the relationship among the actors
and use cases within a system .Use case diagram isused during the analysis phase of a project.
They separate the system into actors and use cases. Actor represents the roles that can be
played by user of the system. Use case describes the behavior of the system.
1. Use cases. A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse.
2. Actors. An actor is a person, organization, or external system that plays a role in one
or more interactions with your system. Actors are drawn as stick figures.
3. Associations. Associations between actors and use cases are indicated in use case
diagrams by solid lines. An association exists whenever an actor is involved with an
interaction described by a use case.
4. System boundary boxes (optional).A rectangle around the use cases is called the
system boundary box and is used to indicate the scope of the system.
5. Packages (optional). Packages are UML constructs that enable you to organize model
elements (such as use cases) into groups.
RELATIONSHIPS IN USE CASE DIAGRAM
Three relationships are supported among use cases by the UML standard, which
describes graphical notation for these relationships.
1. Include(<<include>>)

15

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

A given use case may include another. The first use case often depends on the
outcome of the included use case. This is useful for extracting truly common behaviors
from multiple use cases into a single description.

2. Extend(<<extend>>)
A given use case, (the extension) may extend another. This relationship
indicates that the behavior of the extension use case may be inserted in the extended
use case under some conditions. This can be useful for dealing with special cases, or in
accommodating new requirements during system maintenance and extension.
3. Generalization
Ageneralization/ specializationrelationship exists among use cases. A given use case
may be specialized form of an existing use case. The notation is a solid line ending in a hollow
triangle drawn from the specialized to the more general use case. This resembles the object-
oriented concept of sub-classing, in practice it can be both useful and effective to factor
common behaviors, constraints and assumptions to the general use case, describe them once,
and deal same as except details in the specialized cases.
PROCEDURE
1. Identify distinct actors and use cases.
2. The external actors are placed to the left of the use case and the internal actors to the
right.
3. Open Rational Rose enterprise edition and right click on the project then select use
case view to create a new workspace for the diagram.
4. Name the diagram and draw the diagram using the symbols present in Rational Rose
enterprise edition according to the identified actors and use cases
5. Draw the relationship between the use cases and actors as extend, include and
generalization types using the symbols.
RESULT
Thus the use case diagram is drawn successfully using rational enterprise edition for
the identifiedrequirements.
SAMPLE VIVA QUESTIONS

16

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

1. What is rational rose?

2. What is data modeling?
3. Who isan actor?
4. In what view a use case diagram is drawn?
5. What is OCL?

Ex No.4 UML-CLASS DIAGRAM

AIM
To identify conceptual classes and develop a domain model with UML Class diagram
using Rational Enterprise Edition.
CLASS DIAGRAM
In the Unified Modeling Language (UML), a class diagramis a collection of static
modeling elements, such as classes and their relationships,connected as a graph to each other
and to their contents; their internal structures, and their relationships to other classes.
A class is drawn as a rectangle with three components separated by horizontal
lines. The top name compartment holds the class name, other general properties of theclass,
such as attributes, are in the middle compartment, and the bottom compartment holds a list of
operations. Either or both the attribute and operation compartments may be suppressed.
A separator line is not drawn for a missingcompartment if a compartment is
suppressed; no inference can be drawn about thepresence or absence of elements in it. The
class name and other properties should bedisplayed in up to three sections. A stylistic
convention of UML is to use an italic font forabstract classes and a normal (roman) font for
concrete classes.
PROCEDURE
1. Identify the classes that are taking part in the diagram.
2. Open the rational rose enterprise edition from rational software andselect logical
view.
3. Select class diagram, specify the attributes, operations or methods.
4. Create the class diagram for the project.
5. Explicitly denote the relation between classes by generalizations, associations,
multiplicities and cardinalities.

17

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

6. Save the file.

RESULT
Thus the class diagram is drawn successfully using rational enterprise edition for the
identified requirements.

SAMPLE VIVA QUESTIONS

1. What is rational rose?
2. What is data modeling?
3. Who is an actor?
4. In what view a class diagram is drawn?
5. How attributes and operations are represented in a class diagram?

18

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.5 UML- SEQUENCE AND COLLABORATION DIAGRAMS

AIM
To draw sequence and collaboration diagrams for the identified scenarios and the
interaction between objects using Rational Enterprise Edition.

INTERACTION DIAGRAM
Sequence diagram describes the behavior of the system by viewing the
interaction between the system and its environment. It represents the class at
the top and their lifetime, their interactions as relations.
A collaboration diagram, also called a communication diagram or interaction diagram,
is an illustration of the relationships and interactions among software objects in the Unified
Modeling Language (UML).

PROCEDURE
SEQUENCE DIAGRAM
1. Identify the initiator of the process.
2. Associate each actor with a class whether it uses or provides services.
3. Each actor is represented as a rectangle.
4. The sequence of flow is denoted by the name of the operations to be done.
5. The actors are separated by vertical dashed lines and sequence flowis indicated
through arrows.
6. Open the rational rose enterprise edition from rational software.
7. Select logical view and sequence diagram.
8. Create the sequence diagrams, showing the interaction between the objects and
environmental.
9. Save the file.
COLLABORATION DIAGRAM

19

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

1. This diagram is a numbered transition of sequence diagram in affixed order.

2. The transitions are denoted followed by operation name.
3. By pressing F5 the collaboration diagram can be derived from the sequence diagram.

RESULT
Thus the sequence and the collaboration diagramsfor the identified scenarios and the
interaction between objects are drawn successfully using rational enterprise edition for the
requirements.
SAMPLE VIVA QUESTIONS
1. What are the three types of modeling in UML?
2. What are the various components in sequence diagrams?
3. What are the different elements of a collaboration diagram?
4. What are the building blocks of UML?
5. What are the different views of UML?

20

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.6 UML-STATE CHART DIAGRAM

AIM
To draw the state chart diagram for the identified requirements using Rational
Enterprise Edition.

STATE CHART DIAGRAM

A State chart diagram describes a state machine. State machine can be defined as a
machine which defines different states of an object and these states are controlled by external
or internal events.State chart diagram is used to describe the states of different objects in its
life cycle. So the emphasis is given on the state changes upon some internal or external events.
These states of objects are important to analyze and implement them accurately. States can be
identified as the condition of objects when a particular event occurs.The state chart
diagram shows the sequence of states that an object goes through during its life
in response to outside message. Set of values that describe an object at a
specific point in time.
PROCEDURE
1. Identify important objects to be analyzed.
2. Identify the states.
3. Identify the events.
4. Openthe rational rose enterprise edition from rational software.
5. Select logical view and state chart diagram.
6. Create state transition diagram for project.
7. Use the tools and draw the overall diagram.
8. Save the file.
RESULT
Thus the state chart diagram isdrawnfor the identified requirements
successfullyusingrational enterprise edition for the requirements.

21

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

SAMPLE VIVA QUESTIONS

1. What are the various components in state chart diagram?
2. What is a state machine?
3. State the difference between activity and state chart diagram.
Ex No.7 UML-ACTIVITY DIAGRAM

AIM
To draw activity the diagram for the identified requirements using Rational Enterprise
Edition.

ACTIVITY DIAGRAM
An activity diagram is a variation or special case of a state machine, in which the states
are activities representing the performance of operations and the transitions are triggered by
the completion of the operations. Unlike state diagrams that focus on theevents occurring to a
single object as it responds to messages, an activity diagram can beused to model an entire
business process. The purpose of an activity diagram is to providea view of flows and what is
going on inside a use case or among several classes.
An activity is shown as a round box, containing thename of the operation. When an
operation symbol appears within an activity diagram or other state diagram, it indicates the
execution of the operation.Executing a particular step within the diagram represents a state
within the execution of the overall method. It may be applied to any purpose such as
visualizing the steps of a computer algorithm, but is considered especially useful for
visualizing business workflows and processes, or use cases. Some of the outstanding notation
includes parallel activities, swimlanes, and action-object flow relationship. An activity
diagram allows the reader to see the system execution and how it changes direction based
upon different conditions and stimuli.
PROCEDURE
1. Identify the activities, association, conditions and constraints.
2. Name the correct alternative types.
3. It is essential for the diagram to have a start and end points.
4. Open the rational rose enterprise edition from rational software and select use case
view.

22

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

5. Select activity diagram and create activity diagram for requirements of project using
the tools.
6. Save the file.

RESULT
Thus the activity diagram is drawn successfully using rational enterprise edition for
the requirements.
SAMPLE VIVA QUESTIONS
1. Where to use activity diagrams?
2. What are the different elements of activity diagram?
3. State the difference between activity and state chart diagram.
4. What is the purpose of swim lane?
5. What is business modeling?

23

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.8 PACKAGE DIAGRAM

AIM
To draw the partial layered, logical architecture diagram with UML package diagram
notation for identified the user interface, domain objects, and technical services .

PACKAGE DIAGRAM

A packageis a grouping of model elements. Packages themselves may containother

packages. A package may contain both subordinate packages and ordinary modelelements.
The entire system can be thought of as a single high-level package witheverything else in it.
All UML model elements and diagrams can be organized intopackages. Package diagrams are
used to illustrate the layers. In the UML,a layer is simply a package.
A package is represented as a folder, shown as a large rectangle with a tabattached to
its upper left corner. If contents of the package are not shown, then the nameof the package is
placed within the large rectangle. If contents of the packageare shown,then the name of the
package may be placed on the tab .The contents of thepackage are shown within the large
rectangle.Thelogical architecture, describes the system in terms of its conceptualorganization
in layers, packages, major frameworks, classes, interfaces, andsubsystems.
PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
components or processes in Component Diagrams (CPDs), or groups of processors in
Deployment Diagrams (DPDs).
There are three types of layer. They are
 User interface layer -graphical interface; windows.
 Domain layer -software objects representing domain concepts that fulfill application
requirements.
 Technical services layer -general purpose objects and subsystems that provide
supporting technical services, such as interfacing with a database or error logging.

24

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

These services are usually application-independent and reusable across several

systems.

PROCEDURE
1. Select the rational rose enterprise edition from rational software.
2. Select the logical view and open the class diagram, from the tools displayed in the class
diagram window select the package tool.
3. Using the package tool the outer layer package and the inner software package along
with the dependencies between the packages are drawn.
4. Save the file.

RESULT
Thus the partial layered, logical architecture diagram with UML package diagram
notation for identified the user interface, domain objects, and technical services package
diagram is drawn using rational software.

SAMPLE VIVA QUESTIONS

1. What is a package?
2. What is logical architecture?
3. State the package notations available?
4. What is a user interface layer?

25

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.9 DEVELOPMENT AND IMPLEMENTATION OF USER INTERFACE, DOMAIN

AND TECHNICAL SERVICES LAYER
AIM
To develop and test the user interface, domain and technical services layer for the
given project.

USER INTERFACE LAYER

This layer provides the user interface (UI) within a composite application. To increase
user productivity, user interfaces should support easy adoption. The limitations on the UI
design resulting from the capabilities of the underlying components should not be seen as
constraints, but rather as some help to provide consistent UIs.
User interfaces consume Web services either from the business logic layer or the back-
end layer to retrieve and update data. They do not contain any business logic. UI and business
logic decoupling is implemented by using services of the business logic layer only.User
interfaces are integrated in the overall composite process by being wrapped into a callable
object.
DOMAIN LAYER
A domain layer also known as the business logic layer (BLL) is a software engineering
practice of compartmentalizing. The business logic layer is usually one of the tiers in a
multitier architecture. It separates the business logic from other modules, such as the data
access layer and user interface. By doing this, the business logic of an application can often
withstand modifications or replacements of other tiers. For example, in an application with a
properly separated business logic layer and data access layer, the data access layer could be
rewritten to retrieve data from a different database, without affecting any of the business
logic. This practice allows software application development to be more effectively split into
teams, with each team working on a different tier simultaneously.
TECHNICAL SERVICES LAYER

26

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

The Infrastructure Layer may be partitioned into different levels (high-level or low-
level technical services). Though, it is not unusual that developers only consider the
persistence (data access) and therefore only talk about the Persistence Layer or the Data
Access Layer (instead of an Infrastructure Layer or Technical services Layer).In other words,
the other kind of technical services are not always being explicitly thought of as being part of
any particular layer.
PROCEDURE
1. Create class diagram and component diagram for the given project using rational rose
enterprise edition.
2. Right click on component diagram and select the software needed to generate code.
3. Right click on class diagram and assign created component with this class.
4. Generate code from tool menu and create a form. Then a window appears with
provision to type coding.
5. Type the coding andExecute the form finally by pressing F5.

RESULT
Thus the user interface, domain and technical services layer for the given project was
developed and testedfor the given project.

SAMPLE VIVA QUESTIONS

1. How to use test manager to organize a test plan?
2. Define domain object layer.
3. Define technical service layer.

27

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.9 (a) CREATION OF TEST PLAN AND TEST CASES

AIM
To create test plan, test cases and test case folder through test user in rational
administrator.

TEST PLAN AND TEST CASES

A test plan documents the strategy that will be used to verify and ensure that a product
or system meets its design specifications and other requirements. A test plan is usually
prepared by or with significant input from test engineers.A test case is a set of conditions
under which a tester will determine whether an application, software system or one of its
features is working as it was originally established for it to do. The mechanism for
determining whether a software program or system has passed or failed such a test is known
as a test oracle.

PROCEDURE
Test Manager
 Open the rational test manager, from rational software .
 Create a new test plan & name it right click on it & create use case folder & create the
test case for chat.
 Right click on the test case, go to properties & make an automatic implementation by
selecting script.
 Run the test case from file menu.
Rational Robot
 Open rational robots from rational software .
 Create script by using file menu in new option.
 Open visual basic program & start record by using start operation & it perform some
operation in project & stop recording.
 Run script file by using play back is file menu.

28

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Rational Pure Coverage

 Open rational pure coverage from rational software-.
 Open project in VB & select the option.
 Run the project by using file menu.
 It provides accurate information & coverage.
 It provides accurate information & coverage information that need to evaluate the test
& properties.
RESULT
Thus new test plan, test case, test case folder are created using rationaltest manager.

SAMPLE VIVA QUESTIONS

1. How to use test manager to organize a test plan?
2. What is a test plan?
3. What is a test case?
4. What is meant by test oracle?

29

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

Ex No.10 COMPONENT AND DEPLOYMENT DIAGRAMS

AIM
To draw component and deployment diagrams for the identified requirements using
Rational Enterprise Edition.

COMPONENT AND DEPLOYMENT DIAGRAMS

Component diagram is a special kind of diagram in UML It does not describe the
functionality of the system but it describes the components used to make those
functionalities. So from that point component diagrams are used to visualize the physical
components in a system. These components are libraries, packages, files etc.It can also be
described as a static implementation view of a system. Static implementation represents the
organization of the components at a particular moment.A single component diagram cannot
represent the entire system but a collection of diagrams are used to represent the whole.
Deployment diagrams are used for describing the hardware components where
software components are deployed. Component diagrams and deployment diagrams are
closely related.Deployment diagrams shows how components are deployed in hardware.A
deployment diagram consists of nodes. Nodes are nothing but physical hardware used to
deploy the application.
PROCEDURE
COMPONENT DIAGRAM
1. Identify the files used in the system, libraries, other artifacts relevant to the application
and the relationships among the artifacts.
2. Visualize the components of a system.
3. Construct executables by using forward and reverse engineering.
4. Describe the organization and relationships of the components.
5. Select rational rose enterprise edition from rational software and open the specific
project.
6. Select component view of the project and draw the diagram along with the
dependencies using appropriate tools.

30

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

7. Save the diagram

DEPLOYMENT DIAGRAM
1. Identify the node and Relationships among nodes
2. Visualize hardware topology of a system.
3. Describe the hardware components used to deploy software components.
4. Describe runtime processing nodes.
5. Select rational rose enterprise edition from rational software and open the specific
project.
6. Select deployment view of the project and draw the diagram along with the device
node and environment node using the appropriate tools.

7. Save the diagram

RESULT
Thus the component and the deployment diagrams are drawn successfully
usingrational enterprise edition.

SAMPLE VIVA QUESTIONS

1. What are the parameters controlled by deployment diagram?
2. How to draw component diagram?
3. What is the purpose of deployment diagram?
4. What are the elements of component diagram?
5. Which diagram shows the static view of the system?

31

Downloaded by Chola Raja ([email protected])

 lOMoARcPSD|45111667

CONTENT BEYOND THE SYLLABUS

1. Draw Component and Deployment diagrams.
2. Apply Change ManagementforProgram, Data and Documentation management.
3. Apply Reverse Engineering approach and compare with the forward engineering
approach. Prepare documents and reports.

32

Downloaded by Chola Raja ([email protected])