Ex.

no:1
CASE TOOLS

INTRODUCTION:
CASE tools enable rapid development of information systems by automating the software
development life cycle using integrated tools like modelling and code generation. They offer
advantages such as high-quality, defect-free products at lower costs and faster development
times. Prefabricated components are pre-built, tested, and customizable for specific needs.
However, CASE tools primarily generate a basic framework, requiring additional manual
programming to achieve a fully functional 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) :

UML is a graphical language used for specifying, constructing, visualizing, and documenting
software systems. It follows defined rules and semantics, utilizing OCL (Object Constraint
Language) for system properties. UML is not a programming language but aligns closely with
object-oriented programming. It is simpler than earlier methods and applicable to various
systems, from enterprise applications to embedded systems.
Key Elements of UML:
Basic building blocks
Rules for combining blocks
Common mechanisms applied across the language
UML Diagrams
1. Structural Diagrams

• Class Diagram – Represents system structure, including classes and their

relationships.
• Component Diagram – Shows software components and their dependencies.
• Deployment Diagram – Represents system runtime architecture.
2. Behavioral Diagrams
• Use-Case Diagram – Depicts user interactions with the system.
• Activity Diagram – Models workflows and parallel processes.

1 711722244043
 • State Chart Diagram – Represents object state transitions.
3. Interaction Diagrams (Subtype of Behavioral Diagrams)
• Sequence Diagram – Shows time-ordered object interactions.
• Collaboration Diagram – Displays object communication and relationships.
UML DIAGRAM DESCRIPTIONS
1. Class Diagram
Represents static structure of a system. Defines classes, attributes, operations, and relationships
between objects.
2. Use-Case Diagram
Illustrates system functionality from the user’s perspective. Includes actors, use cases,
communication associations, and generalization relationships.
3. Behavior Diagram
Represents dynamic behavior of objects. Shows object behavior in response to use-case
interactions.
4. Interaction Diagram
Combination of sequence and collaboration diagrams. Depicts message flow between objects
over time.
5. State Chart Diagram
Represents possible object states and transitions. Used to model object lifecycles.
6. Activity Diagram
Models workflows and process dependencies. Useful for depicting parallel processing in
systems.
7. Component Diagram
Represents modular parts of a system. Shows software components, source code structure, and
interfaces.
8. Deployment Diagram
Illustrates runtime system configurations. Represents hardware nodes and software
components in deployment.
UML NOTATION ELEMENTS
Graphical symbols used to annotate UML models.
Provides clarification and details for diagrams.
Relationships in UML
Dependency – A change in one element affects another.

2 711722244043
Association – Defines links between objects.
Generalization – Establishes inheritance relationships.
Realization – Specifies implementation relationships.
Where UML Can Be Used
Software modeling for applications, databases, and architectures.Non-software domains like
business process modeling and hardware design.
USE-CASE DEFINITION
1. Description
A use-case consists of scenarios tied to a user goal. It is a behavioral diagram showing user
actions and system responses.
2. Purpose
Example: Email Client
Main Flow: User logs in and sends a message.
Class Diagram
1. Description
Defines system objects and relationships. Used in both analysis and design phases.
2. Representation
CopyEdit <<Class Name>> <<Attributes>> <<Operations>>
Relationships: Associations, Dependencies, Generalizations.
State Chart Diagram
1. Description
Represents dynamic behavior of individual objects.Shows states, transitions, and events.
2. Key Components
Decision – Workflow branching condition.
Synchronization – Parallel process handling.
Start State – Entry point of workflow.
End State – Terminal point of workflow.
Activity Diagram
1. Description
Models workflow execution in a system.
2. Key Elements

3 711722244043
Activities – Represent tasks/processes.
Decisions – Conditional branches in workflow.
Synchronization – Parallel execution support.
Start/End States – Define process boundaries.
Sequence Diagram
1. Description
Represents object interactions in a timeline-based order. Shows message exchange between
objects.
2. Key Components
Objects – System entities (e.g., User, Website, Login).
Message Icons – Arrows indicating communication flow.
Collaboration Diagram
1. Description
Alternative representation of sequence diagrams. Displays objects, links, and messages.
2. Purpose
Analysis Phase: Defines primary and secondary interactions.
Design Phase: Represents system mechanisms.
Toggling Between Sequence and Collaboration Diagrams
Press F5 to switch between views in modeling tools.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the study for case tools was done.

4 711722244043
 Ex.no:2
PASSPORT AUTOMATION SYSTEM

AIM:
To create an automated system to perform the Passport Process.
PROBLEM STATEMENT:
Passport Automation System is used in the effective dispatch of passport to all of the applicants.
This system adopts a comprehensive approach to minimize the manual work and schedule
resources, time in a cogent manner. The core of the system is to get the online registration form
(with details such as name, address etc.,) filled by the applicant whose testament is verified for
its genuineness by the Passport Automation System with respect to the already existing
information in the database.
SOFTWARE REQUIREMENT SPECIFICATION:
• Front End Client - The applicant and Administrator online interface is built using JSP
and HTML. The Administrators's local interface is built using Java.
• Web Server - Glassfish application server(Oracle Corporation).
• Back End - Oracle database.
HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have access to the
database in the server.

USE CASE DIAGRAM

5 711722244043
ACTIVITY DIAGRAM FOR REGISTER

ACTIVITY DIAGRAM FOR ADMINISTRATION

CLASS DIAGRAM:

6 711722244043
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

SEQUENCE FOR CHECKING STATUS:

7 711722244043
COLLABORATION DIAGRAM FOR CHECKING STATUS

PARTIAL LAYERED LOGICAL ARCHITECTURE DIAGRAM

8 711722244043
DEPLOYMENT DIAGRAM

COMPONENT DIAGRAM:

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for passport automation system has been successfully executed
and codes are generated.

9 711722244043
 Ex.no:3
BOOK BANK SYSTEM

AIM:
To develop a system for managing book bank operations, including lending, urchasing,
and reserving books/magazines.

PROBLEM STATEMENT:
The system registers members, handles book/magazine lending, purchases new titles, and
removes outdated or damaged books. Users can reserve unavailable books and get notified
when available. The system allows easy management of titles, members, loans, and
reservations.

SOFTWARE & HARDWARE REQUIREMENTS:

Front End: JSP, HTML (Student & Librarian Interface), Java (Librarian Local Interface)
Web Server: Glassfish (Oracle)
Back End: Oracle Database
Hardware: Client-server architecture with database access.
USE CASE DIAGRAM:

10 711722244043
ACTIVITY DIAGRAM:

CLASS DIAGRAM:
The class diagram, also referred to as object modeling is the main static analysis diagram. The
main task of object modeling is to graphically show what each object will do in the problem
domain. The problem domain describes the structure and the relationships among objects.

11 711722244043
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.

COLLABORATION DIAGRAM

12 711722244043
PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

13 711722244043
 <<databas>e> <<client
:MySQL workstation>>:
GenericPC
SQL HTTP

<<serve>r>:To
mcat6

COMPONENT DIAGRAM:
Component diagrams are used to visualize the organization and relationships

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for Book Bank System has been successfully executed and codes are
generated.

14 711722244043
 Ex.no:4
EXAM REGISTRATION SYSTEM

AIM:
To create a system to perform the Exam Registration system

PROBLEM STATEMENT:
Exam Registration system.is used in the effective dispatch of registration form to all of the students.
This system adopts a comprehensive approach to minimize the manual work and schedule resources,
time in a cogent manner. The core of the system is to get the online registration form (with details
such as name, reg.no etc.,) filled by the student whose testament is verified for its genuineness by
the Exam Registration System
SOFTWARE REQUIREMENT SPECIFICATION:
The server is directly connected to the client systems. The client systems have access to
the database in the server.

• Front End: JSP, HTML (Student & Controller interfaces).

• Back End: SQL database.
• Web Server: Glassfish.

Hardware Interface: Client systems access the database via a central server.

USE CASE DIAGRAM:

15 711722244043
ACTIVITY DIAGRAM:

CLASS DIAGRAM:
The class diagram, also referred to as object modeling is the main static analysis diagram. The
main task of object modeling is to graphically show what each object will do in the problem
domain. The problem domain describes the structure and the relationships among objects.

16 711722244043
INTERACTION 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.

COLLABORATION DIAGRAM
5: conformation

3: pay
: ExamControl ler

: student

1: login
2: confirmation 4: register
7: logout
6:vi ewexamdetails

Databaes

PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:

17 711722244043
DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a system
where the software components are deployed.

<<client
<<databas>e> workstation>>:
:MySQL GenericPC
SQL HTTP

<<server>> :To
mcat6

18 711722244043
COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships among components in
a system.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for Exam Registration system has been successfully executed and
codes are generated.

19 711722244043
 Ex.no:5
STOCK MAINTENANCE

AIM:
To create a system to perform the Stock maintenance.

PROBLEM STATEMENT:
The stock maintenance system must take care of sales information of the company and must
analyze the potential of the trade. It maintains the number of items that are added or removed.
The sales person initiates this Use case. The sales person is allowed to update information and
view the database.

SOFTWARE REQUIREMENT SPECIFICATION

The entire process of Stock maintenance is done in a manual manner. Considering the fact that
the number of customers for purchase is increasing every year, a maintenance system is
essential to meet the demand.
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

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.

ACTIVITY DIAGRAM
An activity is a state of doing something: either a real-world process, or the execution of a
software routine.

20 711722244043
CLASS DIAGRAM
A class diagram describes the type of objects in system and various kinds of relationships that
exists among them.

UML INTERACTION DIAGRAMS

The interaction diagram is a dynamic model which shows how the system behaves during
dynamic execution.

21 711722244043
COLLABORATION DIAGRAM
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.

PARTIAL LAYERED ARCHITECTURAL DIAGRAM:

22 711722244043
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships among
components in a system.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for stock maintenance system has been successfully executed
and codes are generated.

23 711722244043
 Ex.no:6
ONLINE COURSE RESERVATION SYSTEM

AIM:
To design an object-oriented model for a course reservation system.

PROBLEM STATEMENT:
Whenever the student comes to join the course he/she should be provided with the list of course
available in the college. The system should maintain a list of professor who is teaching the
course. At the end of the course the student must be provided with the certificate for the
completion of the course.

SYSTEM REQUIREMENTS:
Objectives: Define system requirements and functionality. Ensure efficient processing of
student course reservations.
Scope: Specifies system reliability, usability, and performance.
Functionality: Handles student-course transactions smoothly.
Usability & Performance: User-friendly interface with high efficiency for multiple users.

USE CASE DIAGRAM:

CLASS DIAGRAM:
A class diagram describes the type of objectors in the system the various kinds of static
relationship that exist among them.

24 711722244043
SEQUENCE DIAGRAM

A sequence diagram is one that includes the object of the projects and tells the lifetimes and
also various action performed between objects.

25 711722244043
COLLOBORATIION DIAGRAM

It is same as the sequence diagram that involved the project with the only difference that we
we give the project with the only difference that we give sequence number to each process.

ACTIVITY DIAGRAM:
It includes all the activities of particular project and various steps using join and forks.

26 711722244043
COMPONENT DIAGRAM:
The component diagram is represented by figure dependency and it is a graph of design of
figure dependency.

DEPLOYMENT DIAGRAM:
It is a graph of nodes connected by communication association. It is represented by a three
dimensional box. A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets.

27 711722244043
PACKAGES DIAGRAM:

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for online course reservation system has been successfully
executed and codes are generated.

28 711722244043
 Ex.no:7
AIRLINE / RAILWAY RESERVATION SYSTEM

AIM :

To develop the Airline/Railway reservation System using Rational Rose Software.

PROBLEM ANALYSIS AND PROJECT PLANNING:

In the Airline/Railway reservation System the main process is a applicant have to login the database
then the database verifies that particular username and password then the user must fill the details
about their personal details then selecting the flight and the database books the ticket then send it to
the applicant then searching the flight or else cancelling the process.

OVERALL DESCRIPTION
Functionality - The database should be act as an main role of the e-ticketing system it can be
booking the ticket in easy way.
Usability - The User interface makes the Credit Card Processing System to be efficient.
Performance - It is of the capacities about which it can perform function for many users at the
same times efficiently that are without any error occurrence.
Reliability - The system should be able to process the user for their corresponding request.

USE CASE DIAGRAM

The passenger can view the status of the reserved tickets. So the passenger can confirm his/her travel.

29 711722244043
CLASS DIAGRAM

SEQUENCE DIAGRAM

Sequence diagram is a kind of interaction diagram that shows how processes operate with one
another and in what order. It is a construct of a Message Sequence Chart.

COLLABRATION DIAGRAM

A collaboration diagram, also called a communication diagram or interaction diagram,.

30 711722244043
STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in performing a method.
It is also called as state diagram. A state is represented as a round box, which may contain one or
more compartments. An initial state is represented as small dot. A final state is represented as circle
surrounding a small dot.

ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams
can be used to describe the business and operational step-by-step workflows of components in a
system. An activity diagram shows the overall flow of control. An activity is shown as an rounded
box containing the name of the operation.

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association.

31 711722244043
 MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT :
Thus the mini project for Airline/Railway reservation System has been successfully
executed and codes are generated.

32 711722244043
 Ex.no:8
SOFTWARE PERSONNEL RESERVATION SYSTEM

AIM:
To implement a software for software personnel management system.
PROBLEM STATEMENT:
Human Resource management system project involves new and/or system upgrades of
software of send to capture information relating to the hiring termination payment and
management of employee. He uses system to plan and analyze all components and performance
of metrics driven human resource functions, including recruitment, attendance, compensation,
benefits and education.

SOFTWARE REQUIREMENT SPECIFICATION:

Front End Client - The applicant and Administrator online interface is built using JSP and
HTML. The HR's local interface is built using Java. Server - Glassfish application server(SQL
Corporation). Back End - SQL database.
Hardware Interface - The server is directly connected to the client systems. The client
systems have access to the database in the server.

USECASE DIAGRAM:
The HR of an organization involves recruitment training, monitoring, involves gives salary as
observed in the payroll sheet and motivation of an employee

33 711722244043
ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency.

CLASS DIAGRAM:
A class diagram describes the type of objectors in the system the various kinds of static
relationship that exist among them.

INTERACTION 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.

34 711722244043
COLLABORATION DIAGRAM:

STATE TRANSITION DIAGRAM:

States of object are represented as rectangle with round corner, the transaction between the
different states. A transition is a relationship between two state that indicates that when an event
occur the object moves from the prior state to the subsequent.

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

HR recruits employee for a company employee recruited by HR goes under training before
actually working. Training period is given to the employee with the training details. The
salary details for the employee are provided.

35 711722244043
COMPONENT DIAGRAM:

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for software personnel management system has been
successfully executed and codes are generated.

36 711722244043
 Ex.no:9
CREDIT CARD PROCESSING

AIM:
To create a system to perform the credit card processing.
PROBLEM STATEMENT:
Credit card processing through offline involves the merchant collecting order information
(including credit card numbers), storing this in a database on your site, and entering it using
their on-site merchant credit card processing system. Takes time to manually enter credit card
information for each order. This solution creates following
SOFTWARE REQUIREMENT SPECIFICATION:
• Front End Client - The applicant and Administrator online interface is built using JSP
and HTML. The Administrators's local interface is built using Java.
• Web Server - Glassfish application server(SQL Corporation).
• Back End - SQL database.
Hardware Interface - The server is directly connected to the client systems. The client
systems have access to the database in the server.

USECASE DIAGRAM:

37 711722244043
CLASS DIAGRAM:

SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM

PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

38 711722244043
DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a system
where the software components are deployed.

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships among components in
a system.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for credit card processing system has been successfully executed and
codes are generated.

39 711722244043
 Ex.no:10
E-BOOK MANAGEMENT SYSTEM

AIM:
To create a system to perform E- book Management System.

PROBLEM STATEMENT:
An E- Book lends books and magazines to member, who is registered in the system. Also it
handles the purchase of new titles for the Book Bank. Popular titles are brought into multiple
copies. Old books and magazines are removed when they are out or date or poor in condition.
A member can reserve a book or magazine that is not currently available in the book bank, so
that when it is returned or purchased by the book bank, that person is notified. The book bank
can easily create, replace and delete information about the tiles, members, loans and
reservations from the system.

SOFTWARE RESOURCE SPECIFICATION:

The ORS acts as an interface between the user and the 'e-book manager'.
Front End Client - The Student and Librarian online interface is built using JSP and HTML.
The Librarians local interface is built using Java. Web Server – Glassfish application server
(Oracle Corporation). Back End - Oracle database
HARDWARE INTERFACE - The server is directly connected to the client systems. The client
systems have access to the database in the server.
USE CASE DIAGRAM:

40 711722244043
ACTIVITY DIAGRAM:

CLASS DIAGRAM
The class diagram, also referred to as object modeling is the main static analysis diagram. The
main task of object modeling is to graphically show what each object will do in the problem
domain. The problem domain describes the structure and the relationships among objects.

41 711722244043
SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

42 711722244043
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships among
components in a system.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for E-Book System has been successfully executed and codes are
generated.

43 711722244043
 Ex.no:11
RECRUITMENT SYSTEM

AIM:
To create an automated system to perform the Recruitment System Process.
PROBLEM STATEMENT
The recruitment system allows the job seekers to enroll their names through the process of
registration. The employee also can get the list of available candidates and shortlist for their
company requirement. Once the applicant enrolls he receives an id, which helps him in further
Correspondence. A fees amount is received from the job seekers for enrollment. This system
makes the task of the job seeker easier rather than waiting in queue for enrollment.
SOFTWARE REQUIREMENT SPECIFICATION:
Front End Client - The applicant and Administrator online interface is built using JSP and
HTML. The Administrators's local interface is built using Java. Web Server - Glassfish
application server (SQL Corporation). Back End - SQL database.
HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have access to the
database in the server.
USE CASE DIAGRAM:

44 711722244043
ACTIVITY DIAGRAM:

UML CLASS DIAGRAM:

The UML class diagram is to illustrate class interfaces and their actions. They are used for
static object modeling, we have already introduced and used their UML diagram while domain
modeling.

UML SEQUENCE DIAGRAM:

A sequence diagram illustrates a kind of format in which each object interacts via message. It
is generalize between two or more specialized diagram.
SEQUENCE DIAGRAM FOR REGISTER

45 711722244043
SEQEUENCE DIAGRAM FOR STATUS

SEQUENCE DIAGRAM FOR ADMIN

46 711722244043
UML COLLABRATION DIAGRAM:
Communication diagram illustrate that object interact on a graph or network format in which
object can be placed where on the diagram. In collaboration diagram the object can be placed
in anywhere on the diagram. The collaboration comes from sequence diagram.
COLLABORATION FOR REGISTER

COLLABORATION FOR STATUS

47 711722244043
COLLABORATION FOR ADMIN

PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:

DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

<< databas << client

e>> workstati
: MySQL on>>:Gen
SQ H
<< server >
> : Tomca
t6

48 711722244043
COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships among components in
a system.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for recruitment system has been successfully executed and codes are
generated.

49 711722244043
 Ex.no:12
FOREIGN TRADING SYSTEM USING RATIONAL ROSE

AIM:
To design a project Foreign Trading System using Rational Rose Software and to
implement the software in Visual Basic .

PROBLEM STATEMENT
The foreign trading system begins its process by getting the username and password from the
trader. After the authorization permitted by the administrator, the trader is allowed to perform
the sourcing to know about the commodity details.After the required commodities are chosen,
the trader places the order.The administrator checks for the availability for the required
commodities and updates it in the database. After the commodities are ready for the trade, the
trader pays the amount to the administrator.The administrator in turn provides the bill by
receiving the amount and updates it in the database.The trader logouts after the confirmation
message has been received.

UML DIAGRAMS
The exporter submits the relevant documents to his buyer (banker) for getting the payment for
the goods exported.

CLASS DIAGRAM
A class diagram is a type of static structure diagram that describes the structure of a system.
The class diagram is represented using rectangular boxes each of which contains three parts:

50 711722244043
SEQUENCE DIAGRAM:
Sequence diagram in unified modeling language is a kind of interaction diagram that shows
how processes operate with one another and in what order. This diagram shows a parallel
vertical lines called lifelines. There are two dimensions in this diagram
Vertical dimension-represents time.
Horizontal dimension-represent different object

COLLABORATION DIAGRAM
A collaboration diagram belongs to a group of UML diagrams called Interaction Diagrams.

51 711722244043
COMPONENT DIAGRAM
A component diagram depicts how the components are wired together to form larger
components and or software systems. Components are wired together by using an assembly
connector to connect the required interface of one component with the provided interface of
another component.

DEPLOYMENT DIAGRAM
A deployment diagram models the physical deployment of artifacts on nodes. The nodes appear
as boxes, and the artifacts allocated to each node appear as rectangles within the boxes. Nodes
may have sub nodes, which appear as nested boxes.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT
Thus the mini project for foreign trading system has been successfully executed and
codes are generated.

52 711722244043
 Ex.no:13
CONFERENCE MANAGEMENT SYSTEM

AIM:
To develop a project on Conference management system using Rational Rose
Software.

PROBLEM STATEMENT
The process of the candidates is to login the conference system and submit the paper through
online. Then the reviewer reviews the paper and sends the acknowledgement to the candidate
either paper selected or rejected. The candidate login to the conference management system.
The paper title is submitted. The paper is been reviewed by the reviewer. The reviewer sends
acknowledgement to the candidate. Based on the selection, the best candidate is selected.
Finally the candidate registers all details.

SOFTWARE REQUIREMENT SPECIFICATION

The candidate can login and submit the paper to the reviewer. After getting acknowledgement
the candidate will submit the revised and camera ready paper then registration process will be
carried out. Reviewer will reviews the paper and sending acknowledgement to the candidate.
Database is used to verify login and store the details of selected candidates.

USE CASE DIAGRAM

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements.

CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their attributes, and
the relationships between the classes.

53 711722244043
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order.

COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction diagram.

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between the
components of a system.

54 711722244043
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for conference management system has been successfully
executed and codes are generated.

55 711722244043
 Ex.no:14
BPO MANAGEMENT SYSTEM

AIM:
To implement a software for BPO management system.

PROBLEM STATEMENT:
With the reduction in communication costs and improved bandwidths and associated
infrastructure, BPO as a segment is witnessing a massive growth. One of the key challenges
that BPO companies that provide data entry/data validation services is an efficient and effective
way of getting the source documents from different customers and accurately route the same
to different operators for processing.

SOFTWARE REQUIREMENT SPECIFICATION:

Front End Client - The applicant and Administrator online interface is built using JSP and
HTML. The Administrators's local interface is built using Java. • Web Server - Glassfish
application server (SQL Corporation). • Back End - SQL database.

USECASE DIAGRAM:

56 711722244043
UML CLASS DIAGRAM:
The UML class diagram is to illustrate class interfaces and their actions. They are used for
static object modelling.

UMLSEQUENCE DIAGRAM
A sequence diagram illustrates a kind of format in which each object interacts via message. It
is generalize between two or more specialized diagram.

57 711722244043
COLLABORATION DIAGRAM

PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM:

58 711722244043
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

COMPONENT DIAGRAM
Component diagrams are used to visualize the organization and relationships among
components in a system.

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the mini project for BPO management system has been successfully executed
and codes are generated.

59 711722244043
 Ex.no:15
LIBRARY MANAGEMENT SYSTEM

AIM :
To design an object oriented model for Library Management System using Rational
Rose software and to implement it using Java.

PROBLEM STATEMENT :
The library management system is a software system that issues books and magazines to
registered students only. The student has to login after getting registered to the system. The
borrower of the book can perform various functions.

USE CASE DIAGRAM

Use case is a list of actions or events. Steps typically defining the interactions between a role
and a system to achieve a goal. The use case diagram consists of various functionality
performed by actors like user, librarian, system and DBA.

CLASS DIAGRAM :
A class diagram in the unified modeling language is a type of static structure diagram that
describes the structure of a system by showing the system’s classes, their attributes, operations
and the relationships among objects.

60 711722244043
DEPLOYMENT DIAGRAM
Deployment diagram is a structure diagram which shows architecture of the system as
deployment of software artifacts to deployment target.

COMPONENT DIAGRAM
Component diagram shows the dependencies and interactions between software components.
library management
system

user DBA
librarian

STATECHART DIAGRAM
State chart diagram is also called as state machine diagram. The state chart diagram contains
the states in the rectangular boxes and the states are indicated by the dot enclosed. The state
chart diagram describes the behavior of the system.
login enter requesting displaybook
details for book details

logout returnbook issue book search

book

61 711722244043
COLLABORATION DIAGRAM

SEQUENCE DIAGRAM

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT:
Thus the various UML diagrams for library management system was drawn and the
code was generated successfully.

62 711722244043
 Ex.no:16
STUDENT INFORMATION SYSTEM

AIM:
To design an object oriented model for Student information system using Rational Rose
software.

PROBLEM STATEMENT
The student must register by entering the name and password to login the form. The admin
select the particular student to view the details about that student and maintaining the student
details. This process of student information system is described sequentially through following
steps.

USE CASE DIAGRAM

Use case diagram is a graph of actors, a set of use cases, association between the actors and the
use cases and generalization among the cases. Use case diagram is a list of actions or events.
Use case diagram was drawn to represent the static design view of the system.

CLASS DIAGRAM
The class diagram is the graphical representation of all classes used in the system. The class
diagram is drawn as rectangular box with three components or compartments like class name,
attributes and operations. The student information system makes use of the following classes
like student, staff, system, DBA and server.

63 711722244043
COLLABORATION DIAGRAM:
A Collaboration diagram represents the collaboration in which is a set of objects related to
achieve a desired outcome.

SEQUENCE DIAGRAM

COMPONENT DIAGRAM:
Component diagram carries the major living actors of the system. The component diagram
main purpose is to show the structural relationship between components of the system.

64 711722244043
DEPLOYMENT DIAGRAM:

ACTIVITY DIAGRAM

MARK ALLOCATION
Marks Marks
Details Allotted Awarded
PreLab Questions 20
Software Requirement Specifications 30
Use Case Diagrams 30
Post Lab Questions(Viva) 20
Total 100

RESULT :

Thus the various UML diagrams for student information system were drawn and
code was generated successfully.

65 711722244043