Estd: 2008

BABA INSTITUTE OF TECHNOLOGY AND SCIENCES (A)

Approved by AICTE New Delhi, accredited by NAAC with “A ‘Grade, Affiliated to JNTU GV
An ISO 9001:2015 Certified Institution Bakkannapalem Village, Madhurawada Post, Visakhapatnam – 530 048

DEPARTMENT OF COMPUTER SCIENCE

PRACTICAL RECORD NOTEBOOK

Name of the Student :

Registered Number :
Subject code :
Subject Title : CASE TOOLS LAB

BONA FIDE CERTIFICATE

This is to Certify that the bona fide record of practical work done in the Computer
Laboratory of Baba Institute of Technology and Sciences, Visakhapatnam during the
academic year 2024.

Subject Incharge Head of the Department

Submitted for JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY-

GURAJADA VIZIANAGARAM, Practical Examination held on

Internal Examiner External Examiner

 Index

S.NO. DATE EXPERIMENT TITLE REMARKS

 CASE TOOLS
EX. NO.:
DATE:

Introduction:
CASE tools known as Computer-aided software engineering tools is a kind of
component-based development which allows its users to rapidly develop information
systems. The main goal of case technology is the automation of the entire information
systems development life cycle process using a set of integrated software tools, such as
modeling, methodology and automatic code generation. Component based manufacturing
has several advantages over custom development. The main advantages are the availability
of high quality, defect free products at low cost and at a faster time. The prefabricated
components are customized as per the requirements of the customers. The components used
are pre-built, ready-tested and add value and differentiation by rapid customization to the
targeted customers. However the products we get from case tools are only a skeleton of the
final product required and a lot of programming must be done by hand to get a fully
finished, good product.

Characteristics of CASE:
Some of the characteristics of case tools that make it better than customized
development are;
 It is a graphic oriented tool.
 It supports decomposition of process.

Some typical CASE tools are:

 Unified Modeling Language
 Data modeling tools, and
 Source code generation tools

Introduction to UML (Unified Modeling Language):

The UML is a language for specifying, constructing, visualizing, and documenting
the software system and its components. The UML is a graphical language with sets of
rules and semantics. The rules and semantics of a model are expressed in English in a form
known as OCL (Object Constraint Language). OCL uses simple logic for specifying the
properties of a system. The UML is not intended to be a visual programming language.
However it has a much closer mapping to object-oriented programming languages, so that
the best of both can be obtained. The UML is much simpler than other methods preceding
it. UML is appropriate for modeling systems, ranging from enterprise information system
to distributed web based application and even to real time embedded system. It is a very
expensive language addressing all views needed to develop and then to display system
even though understand to use. Learning to apply UML effectively starts forming a
conceptual mode of languages which requires learning.

Three major language elements:

 UML basic building blocks

Page 1
  Rules that dictate how this building blocks put together.
 Some common mechanism that apply throughout the language The
primary goals in the design of UML are:
1. Provides users ready to use, expressive visual modeling language as
well so they can develop and exchange meaningful models.
2. Provide extensibility and specialization mechanisms to extend the
core concepts.
3. Be independent of particular programming languages and
development processes.
4. Provide formal basis for understanding the modeling language.
5. Encourage the growth of the OO tools market.
6. Support higher-level development concepts.
7. Integrate best practices and methodologies.

Every complex system is best approached through a small set of nearly independent
views of a model. Every model can be expressed at different levels of fidelity. The best
models are connected to reality. The UML defines nine graphical diagrams:

1. Class diagram
2. Use-case diagram
3. Behavior diagram
3.1. Interaction diagram
3.1.1. sequence diagram
3.1.2. collaboration diagram
3.2. state chart diagram
3.3. activity diagram
4. Implementation diagram
4.1 component diagram
4.2 deployment diagram

1. UML class diagram:

The UML class diagram is also known as object modeling. It is a static analysis
diagram. These diagrams show the static structure of the model. A class diagram is a
connection of static model elements, such as classes and their relationships, connected as a
graph to each other and to their contents.

2. Use-case diagram:
The functionality of a system can be described in a number of different use- cases,
each of which represents a specific flow of events in a system. It is a graph of actors, a set
of use-cases enclosed in a boundary, communication, associations between the actors and
the use-cases, and generalization among the use-cases.

3. Behavior diagram:
It is a dynamic model unlike all the others mentioned before. The objects of an object
oriented system are not static and are not easily understood by static diagrams. The behavior
of the class’s instance (an object) is represented in this diagram. Every use-case of the
system has an associated behavior diagram that indicates the behavior of the object. In
conjunction with the use-case diagram we may provide a script or interaction diagram to
show a time line of events. It consists of sequence and collaboration diagrams.

1. Interaction diagram

Page 2
 It is the combination of sequence and collaboration diagram. It is used to depict the
flow of events in the system over a timeline. The interaction diagram is a dynamic model
which shows how the system behaves during dynamic execution.

2. State chart diagram:

It consists of state, events and activities. State diagrams are a familiar technique to
describe the behavior of a system. They describe all of the possible states that a particular
object can get into and how the object's state changes as a result of events that reach the
object. In most OO techniques, state diagrams are drawn for a single class to show the
lifetime behavior of a single object.

3. Activity diagram:
It shows organization and their dependence among the set of components. These
diagrams are particularly useful in connection with workflow and in describing behavior
that has a lot of parallel processing. An activity is a state of doing something: either a real-
world process, or the execution of a software routine.

4. Implementation diagram:
It shows the implementation phase of the systems development, such as the source
code structure and the run-time implementation structure. These are relatively simple high
level diagrams compared to the others seen so far. They are of two sub- diagrams, the
component diagram and the deployment diagram.

5. Component diagram:
These are organizational parts of a UML model. These are boxes to which a model
can be decomposed. They show the structure of the code itself. They model the physical
components such as source code, user interface in a design. It is similar to the concept of
packages.

6. Deployment diagram:
The deployment diagram shows the structure of the runtime system. It shows the
configuration of runtime processing elements and the software components that live in
them. They are usually used in conjunction with deployment diagrams to show how
physical modules of code are distributed on the system.

Notation elements:
These are explanatory parts of UML model. They are boxes which may apply to
describe and remark about any element in the model. They provide the information for
understanding the necessary details of the diagrams.

Relations in the UML:

These are four kinds of relationships used in an UML diagram, they are:
 Dependency
 Association
 Generalization
 Realization

Page 3
Dependency:
It is a semantic relationship between two things in which a change one thing affects
the semantics of other things. Graphically a dependency is represented by a non-continuous
line.

Association:
It is a structural relationship that describes asset of links. A link is being connected
among objects. Graphically association is represented as a solid line possibly including
label.

Generalization:
It is a specialized relationship in which the specialized elements are substitutable
for object of the generalized element. Graphically it is a solid line with hollow arrow head
parent.

Realization:
It is a semantic relation between classifiers. Graphically it is represented as a cross
between generalization and dependency relationship.

Where UML can be used:

UML is not limited to modeling software. In fact it is expressive to model non-
software such as to show in structure and behavior of health case system and to design the
hardware of the system.

Conceptual model be UML:

UML you need to form the conceptual model of UML. This requires three
major elements:
 UML basic building blocks.
 Rules that dictate how this building blocks are put together.
 Some common mechanism that apply throughout the language.

Once you have grasped these ideas, you may be able to read. UML create some
basic ones. As you gain more experience in applying conceptual model using more
advanced features of this language.

Building blocks of the UML:

The vocabulary of UML encompasses these kinds of building blocks.

Use CASE definition:

Description:
A use case is a set of scenarios tied together by a common user goal. A use case is a
behavioral diagram that shows a set of use case actions and their relationships.
Page 4
Purpose:

The purpose of use case is login and exchange messages between sender and
receiver (Email client).

Main flow:
First, the sender gives his id and enters his login. Now, he enters the message to the
receiver id.

Alternate flow:
If the username and id by the sender or receiver is not valid, the administrator will
not allow entering and “Invalid password” message is displayed.

Pre-condition:
A person has to register himself to obtain a login ID.

Post-condition:
The user is not allowed to enter if the password or user name is not valid.

Page 5
Class diagram:

Description:
 A class diagram describes the type of objects in system and various
kinds of relationships that exists among them.
 Class diagrams and collaboration diagrams are alternate
representations of object models.

During analysis, we use class diagram to show roles and responsibilities of

entities that provide email client system behaviors design. We use to capture the
structure of classes that form the email client system architecture.

The classes used in system are:

1. user
2. login
3. s
4. ds

A class diagram is represented as:

<<Class name>>
<<Attribute 1>>
<<Attribute n>>
<<Operation ()>>

Relationship used:
A change in one element affects the other

Generalization:
It is a kind of relationship

State chart:

Description:
 The state chart diagram made the dynamic behavior of individual classes.
 State chart shows the sequences of states that an object goes through events
and state transitions.
 A state chart contains one state ‘start’ and multiple ‘end’ states.

Page 6
The important objectives are:

Decision:
It represents a specific location state chart diagram where the work flow may
branch based upon guard conditions.

Synchronization:
It gives a simultaneous workflow in a state chart diagram. They visually
define forks and joints representing parallel workflow.

Forks and joins:

 A fork construct is used to model a single flow of control.
 Every work must be followed by a corresponding join.
 Joints have two or more flow that unit into a single flow.
State:
A state is a condition or situation during a life of an object in which it satisfies
condition or waits for some events.
Transition:

It is a relationship between two activities and between states and activities.

Start state:
A start state shows the beginning of a workflow or beginning of a state
machine on a state chart diagram.

End state:
It is a final or terminal state.

Activity diagram

Description:

Activity diagram provides a way to model the workflow of a development

process. We can also model this code specific information such as class operation
using activity diagram. Activity diagrams can model different types of diagrams.
There are various tools involved in the activity diagram.

Activity:
An activity represents the performance of a task on duty. It may also represent
the execution of a statement in a procedure.

Page 7
Decision:
A decision represents a condition on situation during the life of an object,
which it satisfies some condition or waits for an event.

Start state:
It represents the condition explicitly the beginning of a workflow on an
activity.

Object flow:
An object on an activity diagram represents the relationship between activity
and object that creates or uses it.

Synchronization:
It enables us to see a simultaneous workflow in an activity.

End state:
An end state represents a final or terminal state on an activity diagram or state
chart diagram.

Sequence diagram:

Description:
A sequence diagram is a graphical view of scenario that shows object
interaction in a time based sequence what happens first what happens next. Sequence
diagrams are closely related to collaboration diagram.
The main difference between sequence and collaboration diagram is that
sequence diagram show time based interaction while collaboration diagram shows
objects associated with each other.

The sequence diagram for the e-mail client system consists of the following
objectives:

Object:
An object has state, behavior and identity. An object is not based is referred to
as an instance.
The various objects in e-mail client system are:
 User
 Website
 Login
 Groups

Page 8
Message icon:
A message icon represents the communication between objects indicating that
an action will follow. The message icon is the horizontal solid arrow connecting
lifelines together.

Collaboration diagram:

Description:
Collaboration diagram and sequence diagrams are alternate representations of
an interaction. A collaboration diagram is an interaction diagram that shows the order
of messages that implement an operation or a transaction. Collaboration diagram is an
interaction diagram that shows the order of messages that implement an operation or a
transaction. Collaboration diagram shows object s, their links and their messages.
They can also contain simple class instances and class utility instances.

During, analysis indicates the semantics of the primary and secondary

interactions. Design, shows the semantics of mechanisms in the logical design of
system.
Toggling between the sequence and collaboration diagrams

When we work in either a sequence or collaboration diagram, it is possible to

view the corresponding diagram by pressing F5 key.

Page 9
 E- TICKETING
Ex. NO.:
DATE:

Introduction:

The manual system of ticket reservation takes more time and the number of
reservations per day is limited. To increase the efficiency of the process, we go for
online ticket reservation system. This system supports online ticket booking.

Problem statement
This system is built for user to directly access the system online to book
tickets. The user can book, print, delete tickets without the help of a clerk. The
administrator has control over the adding flights available for booking and has control
over deleting flights that are not necessary. The administrator and user can both enter
the system using their respective login details

System requirements
Microsoft visual basic 6.0 is used as the front-end for our project and ms-
access is used as the back-end.

Use-case diagram
The online ticket reservation system uses the following use cases:
1. Login
2. Book ticket
3. Print ticket
4. Cancel ticket
5. View flight
6. Add flight
7. Delete flight
8. Logout

Actors involved
1) Administrator
2) Passenger

Use-case name: login

The user enters a username and a password. And if the entered details are
valid, the user’s details are brought to the screen; if they are invalid then an
appropriate message is displayed.

Page 10
Use-case name: Book ticket

The user is allowed to book a ticket on the flight he requires and the date and
time as is necessary for the user. The user has to provide details such as name, flight
number, date of travel, departure time, and can view the price of the ticket.
Use-case name: Print ticket
The user after booking a ticket can print a copy of the ticket reserved. The user
has to provide the details about ticket number for searching in the database and
passenger name for confirming passenger identity.

Use-case name: Cancel ticket

A passenger can decide to cancel a ticket after the ticket is booked. The
passenger has to provide details about ticket for searching and details about him for
confirmation of identity.

Use-case name: View flight

The passenger can view the flights available in the database for deciding
which flight’s ticket he wishes to book. The passenger can view the details of flights
such as, flight number, Flight Company, price, departure and arrival times.

Use-case name: Add flight

Only the administrator has privilege to add flights. The administrator can add
the flight on which tickets can be booked by the passengers. The administrator has to
provide details about a new flight such as flight number, flight company name, price,
departure time, date of travel.

Use-case name: Delete flight

The administrator also has the privilege to delete flights that are not necessary.
The administrator has to provide details about the flight for searching and inform any
passengers that have booked tickets on the flight about the change and make
necessary arrangements.

Use-case name: Logout

After the necessary operations have been performed on the system, the user
can choose to logout from the system.

Page 11
Use-case diagram for airline reservation

Page 12
Class diagram
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.

The online ticket reservation system makes use of the following classes:

o Ticket system
o Flight details
o Ticket

Ticket system
It consists of two attributes and two operations. The attributes are username
and password. The operations used are login () and logout ().

Flight details
It stores the details of all the flights such as flight number, Flight Company,
flight capacity, and cost. The operations available are add (), delete () and view ().

Ticket
It records the details of every ticket booked such as ticket number, passenger
name, and flight number, from place, to place, date of travel, departure time, arrival
time, and price. The operations available are add (), delete (), view (), and print ().

Page 13
Class diagram for airline reservation system

Page 14
Sequence diagram
A sequence diagram represents the sequence and interactions of a given use-
case or scenario. Sequence diagrams can capture most of the information about the
system. Most object-to-object interactions and operations are considered events and
events include signals, inputs, decisions, interrupts, transitions and actions to or from
users or external devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message from one object to another, in which
the “from” object is requesting an operation be performed by the “to” object. The “to”
object performs the operation using a method that the class contains.

It is also represented by the order in which things occur and how the objects in
the system send message to one another.

The sequence diagram for each use-case that exists when a user logs in, adds,
views, updates or deletes records in the system.

Page 15
Sequence and collaboration diagram for adding a flight

The Administrator has the privilege to add flight. He has to provide details
about the new flight that is being created in the database.

Page 16
 Sequence and collaboration diagram for booking a ticket

A passenger can book a ticket by himself. He can view the flight details he
wants to book a ticket on and as per his necessity may book an appropriate ticket.

Page 17
 Sequence and collaboration diagram for canceling a ticket

Canceling a ticket can be performed by the passenger himself. He may view

the ticket he wants and cancel it.

Page 18
 Sequence and collaboration diagram for deleting a flight

A flight can be deleted only by the administrator. The flight to be deleted is selected
and removed from the database.

Page 19
 Sequence and collaboration diagram for printing a ticket

The passenger may choose to print a ticket after booking a ticket. The ticket which is
booked is selected and printed by the passenger.

RESULT:
Thus the documentation for airline reservation system is created. The output is
verified.

Page 20
 Online Course Registration System
Ex. NO.:
DATE:

Aim
To create a system through which students can register to the courses
desired by them.

Problem statement
 The system is built to be used by students and managed by an administrator.
 The student and employee have to login to the system before any processing
can be done.
 The student can see the courses available to him and register to the course
he wants.
 The administrator can maintain the course details and view all the
students who have registered to any course.

System requirements
Microsoft visual basic 6.0 is used as the front end of our project and ms-
access as the back end.

Use-case diagram
The course registration system has the following use-cases
Login
View course
details
Registration
Display details
Maintain course
details Logout

The actors involved in the system are

1. Student
2. Administrator

Use-case name: Login

The user enters the username and password and chooses if the user is
student or administrator. If entered details are valid, the user’s account becomes
available.
If it is invalid, an appropriate message is displayed to the user.

Page 21
Use-case name: View course details
In this use case, a student can search all the courses available to him and
choose the best course he wants. The student can view the course duration, faculty
and department of the courses he may choose.
Use-case name: Registration
When a student has successfully chosen a course, he can register to that
course. Upon registration, the student’s details are stored in the database.

Use-case name: Display details

After registration to any course, the student may see the details of his current
course. He may wish to know details about fees and other information. The
administrator also has the privilege to display details of the the students and the
corresponding course for which they have registered.

Use-case name: Maintain course details

The administrator has to perform the duties of maintaining the course details.
Any change to the course structure is maintained by the administrator.

Use-case name: Logout

After all the desired transactions are made, the user may choose to logout from
the system to save all he changes they have made.

Page 22
Use-case diagram for course registration system

Page 23
Class diagram
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.

The course registration system makes use of the following

classes:
1. Stud(student details)
2. Administrator

1) Stud
It consists of the details of all the students present in the database. The
attributes present in this class are student id, password, name, age, sex, course
and attendance. The object of this class is created as soon as the student
registers to a course. The operations available to this class are login (), logout
(), confirmation (), register (), and view course details ().

2) Administrator
It consists of details of all the courses available to the student. The
attributes present in this class are username, password, course fees, fees due,
marks, and attendance. The operations available to this class are login (),
logout (), ma course details (), display course (), and confirmation ().

Page 24
Class diagram for course registration system

Page 25
Sequence diagram
A sequence diagram represents the sequence and interactions of a given use-
case or scenario. Sequence diagrams can capture most of the information about the
system. Most object-to-object interactions and operations are considered events and
events include signals, inputs, decisions, interrupts, transitions and actions to or from
users or external devices.

An event also is considered to be any action by an object that sends

information. The event line represents a message from one object to another, in which
the “from” object is requesting an operation be performed by the “to” object. The “to”
object performs the operation using a method that the class contains.

It is also represented by the order in which things occur and how the objects in
the system send message to one another.

The sequence diagram for each use-case that exists when a user logs in, adds,
views, updates or deletes records in the system.

Page 26
 Sequence and collaboration diagram for login to the system

Users have to first login to the system before performing any operation. The
user has to provide the necessary details to the system for login.

Page 27
 Sequnce and collabaration diagram for logout

When the necessary operations have been performed on the system, the user
may choose to save the changes and logout from the system.

Page 28
 Sequence and collabaration diagram for registration to a course

After login, the student has to register to a course of his choice. The
student can view all the courses available to him and register to a course suitable to
him. The student may view the course details before registration.

Page 29
 Sequence and collaboration diagram for viewing course details

A student may wish to view course details before registration. For this, the
student has to first login and select the course details he wishes to see.

Page 30
 Sequence and collaboration diagram for maintaining course details

Course details may be changed as per the requirement every year. So the
administrator can edit the details of the course as necessary.

RESULT:
Thus the documentation for course registration system is created. The output is
verified.

Page 31