OOAD LAB Record

SRIRAM ENGINEERING COLLEGE
Perumalpattu, Tiruvallur Dist-602 024.
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
(2018-19)
CS6511-CASE TOOLS LAB
NAME:
REGNO:
CLASS: III YEAR CSE
SEMESTER: V SEM
SRIRAM ENGINEERING COLLEGE
Perumalpattu, Thiruvallur Dist-602 024.
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
Register No:
BONAFIDE CERTIFICATE
This is to certify that this is a bonafide record of work done by

____________________________________ of III Year / V semester B.E CSE in CS6511/CASE
TOOLS LAB during the academic year 2018-2019.
Signature of Lab In-Charge Signature of HOD
Submitted for the Practical Examination held on __________________
Internal Examiner External Examiner

INDEX
S.NO DATE NAME OF EXPERIMENT PAGE SIGN
NO
1 INTRODUCTION TO UML DIAGRAMS
2 PASSPORT AUTOMATION SYSTEM
3 BOOK BANK MANAGEMENT SYSTEM
4 EXAM REGISTRATION SYSTEM
5 STOCK MAINTENANCE SYSTEM
6 ONLINE COURSE RESERVATION SYSTEM
7 E-TICKETING
8 SOFTWARE PERSONNEL MANAGEMENT

SYSTEM
9 CREDIT CARD PROCESSING
10 E-BOOK MANAGEMENT SYSTEM
11 RECRUITMENT SYSTEM
12 FOREIGN TRADE SYSTEM
13 CONFERENCE MANAGEMENT SYSTEM
14 BPO MANAGEMENT SYSTEM
15 LIBRARY MANAGEMENT SYSTEM
16 STUDENT INFORMATION SYSTEM
EXTRA EXPERIMENT
17 HOSPITAL MANAGAMENT SYSTEM

INTRODUCTION TO CREATE UML DIAGRAM
CASE TOOLS
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 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 TOOLS:

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 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

 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.
4.Interaction diagram
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.
5.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
6.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.
7.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.
8.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.
9.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
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 diagram:
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.
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.
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.
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 diagram:
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.
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.
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.
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.
Ex NO: 1 INTRODUCTION TO CREATE THE UML DIAGRAMS
DATE:
To Create Use Case Diagram


Use Case  New  Usecase diagram
Include the actors
Use Oval symbols for operations Use arrow symbols for associations
To create Activity Diagram


Logical view  New 
New activity Diagram
Use the start, activity, decision, arrow, end symbols
To create Class Diagram

Logical view  New  Class diagram
For each actor create the class diagram
Insert the class symbol, right click  new attributes, new operations
To Create Sequence Diagram

Logical  New  Sequence Diagram
For each user draw the sequence diagram
Drag the actor from the left side of the logical view and give a name
Place the object messages
To Create Collaboration Diagram
Press F5 in the sequence diagram

To create a Component Diagram

Component viewnewComponent 
Diagram Draw a component
diagram and assign a name Right
click on it, select the open

specification option
In the dialog window click on the General tab, set the language
(VB,C,C++,etc any one ) Click on the Realize tab
Right click on the class  assign
To create the code template
Select tools  (select the language) for example VB

Select the Update code
Save the file
EX.NO: 2 PASSPORT AUTOMATION SYSTEM
DATE:
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 resource,
time in a cogent manner. The online register form is filled by applicant and is being verified by the
passport administrator system and entered in the database. The application is processed manually based
on the report produced by system and any forfeiting might cause the applicant liable to penalty. The
admin will display the current status of application to the applicant which they can view in online
interface. After all formalities all the original information added to database the passport is sent to the
applicant.
GLOSSARY:
APPLICANT:
One who applies through online interface and checks the status of application to obtain the
passport.
ADMIN:
One who checks the genuine of the info of the applicant and provide the passport.
REGISTRATION:
BRIEF DESCRIPTION:
The application register for the passport. Applicant request for registration and fills in the
details and then submits to the system.
BASIC WORKFLOW:
The system provides the registration form; the applicant fills in the details and submits.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The system must provide the proper registration from and the applicant fills it.
POST-CONDITION:
If the applicant fills in wrong details, then he is liable to penalty as per the law.
CHECK STATUS:
BRIEF DESCRIPTION:
The applicant fills up the registration form and then submits. The admin via the online
interface responds by sending the status.
BASIC WORKFLOW:
The applicant after submitting the details in registration form, receives the status message.
ALTERNATIVE FLOW:
If application not found, then it will form as invalid applicant id.
PRE-CONDITION:
The applicant id is to be mentioned correctly.
POST-CONDITION:
System fetches details for applicant form database.
PROCESS APPLICATION:
BRIEF DESCRIPTION:
The administrator processes the application. The details of the applicant which has been submitted are
verified for genuine.
BASIC WORKFLOW:
The administrator enter the applicant id to the database and send back status message to the applicant.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The applicant must submit his details and his id has to be checked for validity.
POST-CONDITION:
If there is any mistake in the way of filling, then the application is resent to the applicant to recheck
the details.
DISPATCH PASSPORT:
BRIEF DESCRIPTION:
After the application is completely verified by the administrator, sends the passport to the applicant.
BASIC WORFLOW:
The details sent by the applicant are verified thoroughly by the administrator before further
proceedings.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
Before the administrator dispatches the passport to the applicant through post, verification is done to
check if the details given by the applicant id valid.
POST-CONDITION:
The passport is finally dispatched to the applicant by the administrator.
Risk Management:
Risk Identification:
(i) Authenticity problem
(ii) Updation problem.
(iii) Data coherency risk
Risk Analysis:
 Authenticity problem: Wrong details given by the applicant which may be more convincing.
 Updation problem: The problem with renewal is that you can have a separate thread to check the renewal
status of all entries in the database.
 Data coherency risk: The entered data may be inadvertently modified in the phase transitions.
Risk Planning & Avoidance:

 A stricter verification is required to overcome the authenticity problem.
 The Applicant is given the duty to renew his/her passport on the renewal date.
 A relational database can be used to mitigate the inadvertent data modification.
Risk Monitoring:
 The practice of unauthenticated detail submission can be stated as a punishable offence by international
law.
 The passport renewal date must always be noted by the verifiers before its use.
 The database should be compared before and after a phase transaction.
GANTT CHART:
Passport Automation System
UML DIAGRAMS:
USE CASE DIAGRAM:
Registration
Applicant check status
Administrator
process Application
Dispatch passport
ACTIVITY DIAGRAM:
NEW REGISTRATION:
Passport automation
system
New
registration
Enter
details
Register
CHECK STATUS:
ADMIN PANEL:
CLASS DIAGRAM
SEQUENCE DIAGRAM:
NEW REGISTRATION:
Applicant System Database
1.Request for registration
2.Registration form
3.Fill in details
4.Submit
5.Give Applicant id
6.Store full details

CHECK STATUS:
Applicant System Database
1.Enter Applicant id
2.fetch details for applicant
3.Display the status
ADMIN PANEL:
Administrator System Admin panel Database applicant
1.username/password 2.Authentication succeed
3.details of applicant yet to br processed
4.details of applicant dispatches
5.enter applicant id to process
6.give details
7.Dispatch eligible passports
COLLABORATION DIAGRAM:
NEW REGISTRATION:
1: 1.Request for registration
3: 3.Fill in details
4: 4.Submit
Applicant System
2: 2.Registration form
5: 5.Give Applicant id
6: 6.Store full details

Database
CHECK STATUS:
1: 1.Enter Applicant id
Applicant System
3: 3.Display the status
2: 2.fetch details for applicant

Database
ADMIN PANEL:
1: 1.username/password 2: 2.Authentication succeed

Administrator System Admin panel
3: 3.details of applicant yet to br processed

4: 4.details of applicant dispatches
7: 7.Dispatch eligible passports
5: 5.enter applicant id to process

6: 6.give details
applicant
Database
STATE CHART DIAGRAM:

PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
Applicant
ADMIN
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
Registration status Admin Panel Authentication
Database
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
FORMS:
Code for Form1:
Private Sub Command1_Click()

Form2.Show
End Sub
Form3.Show
End Sub
Form3.Show
End Sub
Form5.Show
End Sub
End
End Sub
Code for Form2:

Adodc1.Recordset.Add
End Sub
End
End Sub
Code for Form3:

Form3.Show
End Sub
End
End Sub
Code for Form4:

If Text1.Text = "vicky" And Text2.Text = "varunsai" Then
Form2.Show
Else
End
End If
End Sub
Code for Form4:

Adodc1.Recordset.update
End Sub
Form2.Show
End Sub
End
End Sub
GENERATED CODE:
Passport Automation System:

Option Explicit
'##ModelId=532C405001C1
Public Sub passport_automation_system()
End Sub
New Registration:
Option Explicit
'##ModelId=532C405001C7
Private name As String
'##ModelId=532C405001C8
Private age As Number
'##ModelId=532C405001C9
Private date_of_birth As Date
'##ModelId=532C405001CA
Private place_of_birth As String
'##ModelId=532C405001CB
Private gender As Variant
'##ModelId=532C405001CC
Private father_name As String
'##ModelId=532C405001CD
Private mother_name As String
'##ModelId=532C405001CE
Private address As String
'##ModelId=532C405001C6
Public Sub newregistration()
End Sub
Application Status:
Option Explicit
'##ModelId=532C405001DB
Private Application_no As Number
'##ModelId=532C405001DA
Public Sub Application_Status()
End Sub
Admin Panel:
Option Explicit
'##ModelId=532C405001E7
Private YetToBeProcessedApplication As dategrid
'##ModelId=532C405001E8
Private DispatchApplication As dategrid
'##ModelId=532C405001E9
Private Application_id As Number
'##ModelId=532C405001E6
Public Sub adminpanel()
End Sub
Admin Authentication:
Option Explicit
'##ModelId=532C405001E0
Private User_name As String
'##ModelId=532C405001E1
Private Password As Password
'##ModelId=532C41EB0273
Public Sub adminAuthentication()
End Sub
Gender:
Option Explicit
'##ModelId=532C405001D5
Private Male As radio_button
'##ModelId=532C405001D6
Private Female As radio_button
'##ModelId=532C405001D4
Public Sub gender()
End Sub
Result:
EX.NO: 3 BOOK BANK MANAGEMENT SYSTEM
DATE:
PROBLEM STATEMENT:
A book bank system is a software project used to maintain the book details of a book bank. In
this project the scenario lets us know the details of the book issue and return by the student and
administrator of the book bank. This allows the student to obtain the book and return the books to the
administrator to verify the student id as soon they student. This project mainly helps database to
maintain the issue and return of books which helps a administrator.
GLOSSARY:
STUDENT:
One who borrows the books and return it to the book bank.
ADMINISTRATOR:
One who issues the books , maintains the student and book details.
DATABASE:
One which maintains details of book, student and branches of book bank.
SUBMIT ID:
BRIEF DESCRIPTION :
This allows the student to retrieve his/her book.
BASIC WORKFLOW:
Student is requesting the system to verifying their id to obtain books.
ALTERNATIVE WORKFLOW:
If the id submitted does not matches then it displays error.
PRE-CONDITION:
Enter the correct id number to obtain books.
POST-CONDITION:
None.
VERIFY-ID:
BRIEF DESCRIPTION:
This use-case allows to verify whether the student belongs to book bank.
BASIC WORKFLOW:
Adminstrator is provided with student id and other details.

ALTERNATE WORKFLOW:
If the student does not belong to the book bank then don’t issue bank.
PRE-CONDITION:
Checks the student-id .
POST-CONDITON:
None.
BOOK ISSUE:
BRIEF DESCRIPTION:
This use-case allows issuing the book required by the student.
BASIC WORKFLOW:
Administrator issues books required by student.
ALTERNATE WORKFLOW:
If book is not available during issue it will be conducted later.
PRE-CONDITION:
Check the number of books taken.
POST CONDITION:
None.
BOOK RETURN:
BRIEF DESCRIPTION:
This use-case allows returning the books to the administrator of the book bank.
BASIC WORKFLOW:
Students returns book to the book bank.
ALTERNATE FLOW:
Nil.
PRE-CONDITION:
Number of books issued to each student.
RETURN DATE:
BRIEF DESCRIPTION:
This use-case allows the administrator to store return dates of book in database.
BASIC WORKFLOW:
Date of book return.
ALTERNATE WORKFLOW:
None.
PRE-CONDITION:
Number of books returned by each student.
POST-CONDITION:
None.
UML DIAGRAMS:
USECASE DIAGRAM:
Submit id
Admin
Verify id
Student
Book issue
Book Return
Issue Date
Data base
Return Date
ACTIVITY DIAGRAM:
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
Student Intranet Library
login to the system
search for the book
available or not
available
check the user id
issue the book
3: available or not
1: login to the system

2: search for the book
Student Intranet
6: issue the book
5: check the user id
4: available
Library
Id Book
transfer
Databas
e
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
students books
administrator
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
STUDEN ADMINS BOOKS

T TRATOR
Database
DEPOLYMENT DIAGRAM:
MOUS
E
CPU
KEYB
OARD
PRINT
ER
Student details
BookDetails
Forms:
Code for Form1:
If Text1.Text = "111" And Text2.Text = "vimal" And Text3.Text = " shameer"Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
Code for Form2:

End Sub
Adodc1.Recordset.Delete
End Sub
End
End Sub
Code For Form3:

If Text1.Text = "12345" And Text2.Text = " shameer " Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
GENERATED CODE:
Admin :
Option Explicit
'##ModelId=532C692601E2
Private Id As Integer
'##ModelId=532C692601E3
Private Password As String
'##ModelId=532C692601E1
Public Sub admin()
End Sub
Author:
Option Explicit
Private Authorname As String
'##ModelId=532C692601DC
Private Publication As String
'##ModelId=532C692601DD
Private Price As Integer
Public Sub author()
End Sub
Student:
Option Explicit
'##ModelId=532C692601D3
Private StudentID As Integer
'##ModelId=532C692601D4
Private Name As String
'##ModelId=532C692601D5
Private Address As String
'##ModelId=532C692601D2
Public Sub student()
End Sub
RESULT:
EX.NO: 4 EXAM REGISTRATION SYSTEM
DATE:
PROBLEM STATEMENT:
The student registers for an examination student fills in the application and submits it.
The student has to send the DD to the mentioned address. The authority checks details of the student
and validates. The student details is registered to the database where the register number is provided.
The authority sends the acknowledgement along with the hall ticket to the student. The student
checks for the date and venue and attends the exam.
GLOSSARY:
STUDENT:
Fills and submits the application and sends DD.
AUTHORITY:
Receives the application and checks details. Send the acknowledgement and the hall
ticket.
DATABASE:
Stores the student’s details and generates a unique register number to all the students.
WORKFLOW:
FILL AND SUBMIT APPLICATION:
BRIEF DESCRIPTION:
The student registers for the examination by filling up and submitting the filled
application to the authority.
BASIC FLOW:
The student gets the application and based on his qualification he fills the application.
ALTERNATE FLOW:
Nil.
PRECONDITION:
The student fills in the application.
POSTCONDITION:
Student sends the DD.
SEND DD:
BRIEF DESCRIPTION:
The student has to send DD in order to register for the exam.

BASIC FLOW:
The authority in prior tells the added to submit the DD. The student obtains a DD and
posts it to the specified address.
ALTERNATE FLOW:
Nil
PRECONDITION:
The authority’s address to submit the DD is known.
POST CONDITION:
Authority receives the DD.
REGISTER STUDENT:
BRIEF DESCRIPTION:
The students when the details are validated are provided the register number by database.
BASIC FLOW:
Authority feeds the students details in to the database.
ALTERNATE FLOW:
If the details are not valid or illegal, then the student registration is registered.
PRECONDITION:
The student details are to be perfect and eligible
POST CONDITION:
NiL
USE CASE DIAGRAM:
hall ticket for stu

apply for DD
college
ack for verify
hall ticket provide
verify stu details

student
exam details of fee &date
verify stu detailsack for stu details

exam details of feestu
anddetail
date with fee
stu details
pay DD
bank
student details exam details of fee and date

providing DD
university
update stu details
DB
ACTIVITY DIAGRAM:
student bank college
collecting info
abt fees
check for arrear

details no get fees from
students
yes
adding arrear
details
applying for
DD in bank get details
and money
get DD provide DD
from bank
register fee details

paying DD and give bonafide
get
bonafide
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
bank student college university database

exam details
exam details
student details
apply for DD
providing DD
pay DD
student detail with fee

store std details to db
get std details
confirm hall ticket
confirm hall ticket
ack
ack
update std details
get std details
hall ticket
hall ticket
3: student details
6: pay DD
12: ack
student college
2: exam details
11: confirm hall ticket
17: hall ticket
4: apply for DD
1: exam details
5: providing DD 10: confirm hall ticket
16: hall ticket
bank 7: student detail with fee

13: ack
8: store std details to db

14: update std details databas
e
universit
y 9: get std details
15: get std details
fill and submit

application
send
acknowledgement
store student
details
PACKAGE DIAGRAM:
Entity boundaries
Hal l T i cket DD student details Databas e
Control
college university
COMPONET DIAGRAM:
studen Authori Databa

t ty se
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
FORMS:
Code for Form1:

If Text1.Text = "12345" Then
Form2.Show
Else
End
End If
End Sub
Code for Form2:

If Text1.Text = "varun" And Text2.Text = "2345" Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
Code For Form3:

MsgBox ("success fully submitted")
End Sub
End
End Sub
GENERATED CODE:
Authority:
Option Explicit
'##ModelId=531AD6100393
'##ModelId=531AD6100394
Private designation As String
'##ModelId=531AD6100395
Private id As Integer
'##ModelId=531AD6100392
Public Sub Authority()
End Sub
Database:
Option Explicit
'##ModelId=531AD610039A
Private studentid__ As Variant
'##ModelId=531AD6100399
Public Sub Database()
End Sub
Student:
Option Explicit
'##ModelId=531AD610038B
'##ModelId=531AD610038C
Private dept As String
'##ModelId=531AD610038D
Private year As Integer
'##ModelId=531AD6100388
End Sub
'##ModelId=531AD6100389
Public Sub fillApplication()
End Sub
'##ModelId=531AD610038A
Public Sub submit()
End Sub
RESULT:
EX.NO: 5 STOCK MAINTENANCE SYSTEM
DATE:
PROBLEM STATEMENT:
A Stock Management System is a software project used to maintain the stock details of a Super Market. In this
project it is a useful scenario which is used to know the details of the product of the super market by the
customer. This project keeps track of the product sales of the Super Market. This project alerts the Supervisor
of the super market for less quantity products availability or if any product is not available in the super market.
This project allows the customer to view the availability of any product and it shows the rate of the product.
This project allows the supervisor to set the price for the product.
GLOSSARY:
CUSTOMER:
One who purchases the products from the super market.
SUPERVISOR:
One who purchases the product from the manufacturer and maintain the stock details of the stock market.
WORKFLOW:
USER:
BRIEF DESCRIPTION:
This use case allows the user to know the details of the products of the super market.
BASIC WOKFLOW:
Customer is requesting the system for knowing the details of the product which is currently available in the
super market.
ALTERNATE FLOW:
If the products are not available in the super market, then it displays the error message.
PRE CONDITION:
The system must display the list of products available in the super market to the customer.
POST CONDITION:
Customer had purchased the products from the super market.
ADMIN LOGIN:
BRIEF DESCRIPTION:
This use case allows the supervisor to login on to the system for maintaining the stock details.
BASIC WOKFLOW:
Supervisor is provided with the username and password to login into the system.
ALTERNATE FLOW:
If the supervisor enters the wrong username and password, then the admin is blocked by the system.
PRE CONDITION:
The supervisor must have username and password allotted for him to access the system.
POST CONDITION:
The supervisor is allowed to do changes in the stock availability of the stock market
ADMIN MAINTANANCE:
BRIEF DESCRIPTION:
This use case allows the supervisor to keep track of information about the products availability, rate,
and etc..,
BASIC WOKFLOW:
Admin has a control for editing the various activities of the project management and maintains the
record in the database.
ALTERNATE FLOW:
NIL
PRE CONDITION:
The supervisor must log on to the system.
POST CONDITION:
The changes of the product characteristics have been updated.
UML DIAGRAMS:
UES CASE DIAGRAM:
UER/ADMIN OPTION
CUSTOMER
AVALABILITY
ADMIN LOGIN
ADMIN
MANAGE
ACTIVITY DIAGRAM:
ADMIN LOGIN:
LOGIN
USERID/PASS
NO
YES
VALID INVALID
ADMIN ADMIN
ADMIN MAINTANANCE:
MAINTAIN
STOCK
DETAILS
NO
YES
SHOW ADD, EDIT

USER OPTIONS:
USER
OPTIONS
AMOUNT
YES NO
AMOUNT ACCOUNT
W ITHDRAW N BLOCKED
CLASS DIAGRAM:
USER OPTION:
SEQUENCE DIAGRAM:
ADMIN LOGIN:
LOGIN
: ADMIN
USER NAME, PASSWORD
CHECK
VALID
INVLAID
USER OPTIONS:
ADMIN MAINTANANCE:
ADMIN LOGIN:
2: CHECK
1: USER NAME, PASSWORD

LOGIN
3: VALID
: ADMIN 4: INVLAID
UESR OPTIONS:
1: STOCK ID
AVAILABIL
ITY
: CUSTOMER
3: SEARCH
4: DISPLAY 2: VIEW
DATABAS
E
ADMIN MAINTANANCE:
1: STOCK ID, VIEW

5: ADD NEW,EDIT
MAINTANA
NCE
: ADMIN
3: SEARCH
4: DISPLAY 2: CHECKS
7: STOCK UPDATED 6: UPDATE
MAINTAIN
DATABASE
STATECHART DIAGRAM:
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
user Database
ADMIN
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
Forms:
Login:
If Text1.Text = "srec" And Text2.Text = "student" Then
User.Show
Else
MsgBox "Invalid Password, try again!"
End If
End Sub
User:
Database.Show
End Sub
Database:-
Adodc1.Recordset.AddNew
End Sub
End Sub
Adodc1.Recordset.Update
End Sub
End
End Sub
Code generation:
Database:
Option Explicit
'##ModelId=530B07530148
Private id As Integer
'##ModelId=530B077C0399
Private name As String
'##ModelId=530B0784008C
Private quantity As Integer
'##ModelId=530B078E0119
Private price As Integer
'##ModelId=530B079E01C5
Public Sub database()
End Sub
RESULT:
EX.NO: 6 ONLINE COURSE RESERVATION SYSTEM
DATE:
PROBLEM STATEMENT:
A Course Reservation Project is a software which is used to manage the seats allocation of the various
colleges of various departments for the eligible students. It also gives full access to the students to check the
availability of the seats in the colleges according to the community which the students belong to. The student
can check for the information of the college, such as the year which the college is started, where the college is
situated and the chairman of the college.This software allows the administrator to allot the seat for the eligible
candidates to the group which they wish and the group and college which are available at that tilme.
GLOSSARY:
STUDENT:
One who check for the information of the college and availability of the seats in the specified college
ADMINISTRATOR:
One who allocates seats for the eligible candidates according to their wish and also the seats available at that
time.
WORKFLOW:
USER OPTIONS:
BRIEF DESCRIPTION:
This use case allows the user to know the information and the guidance provided to the students.
BASIC WOKFLOW:
Student request the system for gathering the facility that is provided by the university to the user.
ALTERNATE FLOW:
NIL.
PRE CONDITION:
The system must display the list of options available in the university to the user.
POST CONDITION:
User can check for the ir provided options.
ADMIN LOGIN:
BRIEF DESCRIPTION:
This use case allows the administrator to login on to the system for maintaining the course allocation.
BASIC WOKFLOW:
Administrator is provided with the username and assword to login in to the system.
ALTERNATE FLOW:
If the administrator enters the wrong username or password then the admin is blocked by the system.
PRE CONDITION:
The administrator must have username and password allotted for him to access the system.
POST CONDITION:
The administrator is allowed to allocate the course to the eligible candidates by the universities.
COURSE RESERVATION:
BRIEF DESCRIPTION:
This use case allows the administrator to allocate the course for the candidates according to their wish and
maintains the clear database of them.
BASIC WOKFLOW:
Administrator has a control of allocating the seats to the eligible candidates according to their marks and
maintains their details in the clear database.
ALTERNATE FLOW:
No seats had been selected by the student.
PRE CONDITION:
The administrator must log on to the system.
POST CONDITION:
The seats had been allocated to the student.
AVALABILITY:
BRIEF DESCRIPTION:
This use case allows the user to check for the availability of the seats in accordance with the groups and
community.
BASIC WOKFLOW:
User had specified the college name and search for the seats in accordance with groups and community.
ALTERNATE FLOW:
NIL
PRE CONDITION:
The user must logged on and access the system.
POST CONDITION:
The user comes to know the availability of the seats.
INFORMATION:
BRIEF DESCRIPTION:
This use case allows the user to know the information of the college which they specified.
BASIC WOKFLOW:
User specifies the college name and system shows the respective details of the college such as address, phone
number etc..,
ALTERNATE FLOW:
NIL
PRE CONDITION:
POST CONDITION:
The system shows the information of the college specified by the user.
UML DIAGRAMS:
USE CASE DIAGRAM:

ACTIVITY DIAGRAM:
USER OPTION:
USER
OPTIONS
AVAILABILITY/INFORMATION
NO
YES
AVAILABILITY INFORMATION
AVAILABILITY:
INFORMATION:
INFORMATION
COLLEGE ID
NO
YES
COLLEGE INVALID
DETAILS
ADMIN LOGIN:
LOGIN
USER ID/PASS
NO
YES
VALID ADMIN INVALID

ADMIN
COURSE RESERVATION:
RESERVATION
COLL ID, GROUP,

COMMUNITY
NO
YES
SEAT NO SEAT
ALLOCATED AVAILABLE
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
STUDENT Course Catalog

PROFESSOR
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
STUDEN COURSE REGISTR

T AR
Database
DEPLOYMENT DIAGRAM:
FORMS:
Code for form 1:

If Text1.Text = "sandy" And Text2.Text = "cse" Then
Form2.Show
Else
End
End If
End Sub
Code for form 2:
Form3.Show
End Sub
Form3.Show
Else
End If
End Sub
Form3.Show
End Sub
Code for form3:

End
End Sub
CODE GENERATION:-
Administration:
Option Explicit
'##ModelId=53144E0303B9
Private username As Variant
'##ModelId=53144E1B01E4
Private password As Variant
'##ModelId=53144E3A0148
Public Sub login()
End Sub
College information:
Option Explicit
'##ModelId=53144E6103C8
Private college_name As Variant
'##ModelId=53144E690261
Private address As Variant
'##ModelId=53144E6D0232
Private phone_no As Variant
'##ModelId=53144E810271
Public Sub view()
End Sub
Database:
Option Explicit
'##ModelId=53144DBA030D
Private student_no As Variant
'##ModelId=53144DC4000F
Private seat_allocated As Variant
'##ModelId=53144DD90148
Public Sub allot()
End Sub
Reservation seats:
Option Explicit
'##ModelId=53144F0901A5
Private student_no As Variant
'##ModelId=53144F13036B
Private seat_allocated As Variant
'##ModelId=53144F1D01A5
Public Sub allots()
End Sub
Seats:
Option Explicit
'##ModelId=53144ED403C8
Private groupname As Variant
'##ModelId=53144EDD0280
Private no_of_seats As Variant
User option:
Option Explicit
'##ModelId=53144D8902BF
Private information As Variant
'##ModelId=53144D950271
Private availablity As Variant
'##ModelId=53144DA40271
Public Sub view()
End Sub
RESULT:
EX.NO: 7 E-TICKETING
DATE:
PROBLEM STATEMENT:
An online reservation system is a software that helps in reservation of airline tickets in the internet and check
for the availability of tickets. This system shows all the information about the transport services including
their source and destination, and the time arrival and departure of all flights and the availability of seats in all
the flights. This system also has the facility of cancellation of tickets. If the tickets are not available then the
current status of the system also known through this system.The online reservation system maintains the full
details of the entire passenger who are reserving the tickets in the specified airline services.
GLOSSARY:
PASSENGER:
One who reserve tickets for traveling in the specified airline services.
ADMINISTRATOR:
One who book the tickets for the passenger needs and cancel the tickets, if the passenger doesn’t need
it or cancellation of the trip. Administrator maintains all the details in the airline and passenger database.
DATABASE:
One which stores the details of the arrival and departure of the airlines. It also stores the details of the
passengers who were booked the ticket for the specified airlines. It also stores the current status of the ticket in
the specified airlines.
WORKFLOW:
ADMIN LOGIN:
BRIEF DESCRIPTION:
This use case allows the administrator to login onto the system for maintaining the seats allocation.
BASIC WORKFLOW:
Administrator is provided with the username and password to login into the system.
ALTERNATE FLOW:
If the administrator enters the wrong username or password then the admin is blocked by the system.
PRE CONDITION:
The user must have username and password allotted for him to access the system.
POST CONDITION:
The administrator is allowed to reserve/cancel the tickets for the passenger.
AVAILABILITY:
BRIEF DESCRIPTION:
This use case allows the passenger to check for the availability of seats in accordance with the airline
services.
BASIC WORKFLOW:
Passenger wants to specify the airline services name and the arrival and departure place and the date
of boarding.
ALTERNATE FLOW:NIL
PRE CONDITION:
The passenger must logged on and access the system.
POST CONDITION:
The passenger comes to know the information about the airline which they specified
INFORMATION:
BRIEF DESCRIPTION:
This use case allows the passenger to know the information about the airline which they specified.
BASIC WORKFLOW:
Passenger specifies the airline name and then the system shows the respective details of the airline
such as arrival and departure place ant time.
ALTERNATE FLOW: nil
PRE CONDITION:
POST CONDITION:
The system shows the information of the airlines specified by the user.
SEATS RESERVATION:
BRIEF DESCRIPTION:
This use case allows the administrator to allocate the seats for the passenger to their wish and
maintains the clear database of them.
BASIC WORKFLOW:
Administrator has a control of allocating the seats to the passenger who are reserving the seats for the
specific airlines and maintains their details in the clear database.
ALTERNATE FLOW:
No seats had been reserved by the passenger, if not available.
PRE CONDITION:
POST CONDITION:
The seat had been allotted to the passenger.
SEATS CANCELLATION:
BRIEF DESCRIPTION:
This use case allows the administrator to cancel the seats for the passengers who are canceling their
trips and maintains the clear database of them.
BASIC WORKFLOW:
Administrator has a control of canceling the seats to the passenger who are reserved the seats for the
specific airlines and they don’t need to board.
ALTERNATE FLOW:
No seats had been reserved by the passenger, if not available.
PRE CONDITION:
POST CONDITION:
The seats had been cancelled for the passenger.
UML DIAGRAMS:
USE CASE DIAGRAMS:
Login
Reserve/Cancel
system admin
Availability
user Details
Database
ACTIVITY DIAGRAMS:
ADMIN LOGIN:
ADMIN
USERNAME/
PASSWORD
INVALID
VALID
FLIGHT DETAILS:
USER
FLIGHT
DETAILS
NO
YES
NO DETAILS
DETAILS FOUND
AVAILABILITY:
USER/ADMIN
AVAILABILTY
YES NO
SEATS
AVAILABLE FILLED
SEATS
RESERVATION/ CANCELLATION:
ADMIN
RES/CANC
RES CAN
CANCELLED
RESERVED
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
ADMIN LOGIN:
Login
: system admin Database
Login
Username/Password
Verify
Valid/Invalid
FLIGHT DETAILS:
Login Database
: system admin
Login
Access
Update/View
Result
AVAILABILITY:
Login Availability
: user
Login
Availability
Check
Result
RESERVATION / CANCELLATION:
Log in Reserve/Cancel Database

: user
login
Res/Cancel
Register
Update
Result
ADMIN LOGIN:
1: Login
Login
: system admin
3: Verify
4: Valid/Invalid 2: Username/Password
Database
FLIGHT DETAILS:
1: Login
Login
: system admin
3: Update/View
4: Result 2: Access
Database
AVAILABILITY:
1: Login
Login
: user
3: Check
4: Result 2: Availability
Availability
RESERVATION/ CANCELLATION:
1: login
Log in
: user
5: Result
2: Res/Cancel
4: Update
Database Reserve/Ca
ncel
3: Register
login
reserve/c
ancel
availabilit
y
details
UML PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
system admin user
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
system user
admin
DATABASE
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
FORMS:
Code For Form1:

Form2.Show
Else
End
End If
End Sub
Code For Form2:

Form3.Show
End Sub
Form4.Show
End Sub
Form5.Show
End Sub
End
End Sub
Code For Form3:
End Sub
End Sub
End Sub
Form2.Show
End Sub
Code For Form4:

Form2.Show
End Sub
Code For Form5:
MsgBox ("success fully reserved")
End Sub
Form2.Show
End Sub
CODE GENERATION:-
Class login:-
Option Explicit
'##ModelId=531D88420213
'##ModelId=531D884B003E
'##ModelId=531D88530177
Public Sub login()
End Sub
Database1:-
Option Explicit
'##ModelId=531D886B003E
'##ModelId=531D887001E4
'##ModelId=531D8888009C
Public Sub verify()
End Sub
Database2:-
Option Explicit
'##ModelId=531D892B00EA
Private register As Variant
'##ModelId=531D89320280
Private reserve_cancel As Variant
'##ModelId=531D8949009C
Public Sub update()
End Sub
reservation:
Option Explicit
'##ModelId=531D890A01A5
Private reserve As Variant
'##ModelId=531D8910029F
Private cancel As Variant
'##ModelId=531D8916037A
Public Sub register()
End Sub
View:
Option Explicit
'##ModelId=531D889A0213
Private availabl_ity As Variant
'##ModelId=531D88B8034B
Private flight_details As Variant
'##ModelId=531D88A50167
Public Sub view()
End Sub
RESULT:
EX.NO: 8 SOFTWARE PERSONNEL MANAGEMENT SYSTEM
DATE:
PROBLEM STATEMENT:
To compute the gross pay of a person using the software personnel management system software and to add
new details to the existing database and update it, using visual basic 6.0 and MS Access.The employ details,edit
details,exit command buttons are present.we can choose the required command button.fill in the form with details
such as employee id,employee name,department,experience and basic pay in the text boxand submit using
calculate command button update it in the database using update command button.uddate database would be
present.we can search for required pay details using search command button.
GLOSSARY:
EMPLOYEE:
Employee submits the software which his/her HR order to create .
HR:
The HR has the employee details. The HR asks his employee to create a software .After the employee
submits the software ,the HR checks for the correctness of the software and verifies it.
DB:
If the HR is satisfied with the software, then stores the details about the software into the database.
ASKS TO CREATE SOFTWARE :
BRIEF DESCRITPION:
The HR asks the employee to create the software for which the correctness has to be proved.
BASIC WORKFLOW:
The HR has employee details and asks the apt employee to create the software.
ALTERNATE WORKFLOW:
Nil
PRE-CONDITION:
Nil
POST-CONDITION:
Nil
SUBMITS THE SOFTWARE AND VERIFICATION:
BRIEF DESCRIPTION:
The employee works hard to create the software which the HR has ordered and then submits the
finished software.
BASIC WORKFLOW:
The employee submits the software .The HR receives the software and verifies if it is valid.
ALTERNATE WORKFLOW:
If the software is not valid and incorrect,then HR rejects it and also asks the employee to reconstruct
the software.
PRE-CONDITION:
The employee submits the software is correct and the HR is satisfied,then the HR stores the software details
into the DB and uses the software in the project,
STORES SOFTWARE DETAILS:
BRIEF DESCRIPTION:
The employee submits the software and of the HR is satisfied,then he stores the details of software
into the database.
BASIC WORKFLOW:
If the software is working correctly,then HR stores its details into DB.
ALTERNATE FLOW:
If the software does not work correctly ,then the HR rejects it.
PRE-CONDITION:
The employee has to submit the correct software .
POST-CONDITION:
The employee reconstructs if the software fails.
UML DIAGRAMS:
USECASE DIAGRAM:
ACTIVITY DIAGRAM:
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
employee
details
calculate
salary
edit details
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
employee Database
administrator
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
database
employe administr
e ator
DEPLOYMENT DIAGRAM:
databas
e
admin user
display
Forms:
Code For Form1:

If Text1.Text = "vimal" And Text2.Text = "venkat" Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
Code For Form2:

Adodc1.Recordset.Update
End Sub
End Sub
End
End Sub
Code For Form3:

If Text1.Text ="12345" And Text2.Text = "Shameer" Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
GENERATED CODE:
Admin:
Option Explicit
'##ModelId=532C692601E2
Private Id As Integer
'##ModelId=532C692601E3
'##ModelId=532C692601E1
Public Sub admin()
End Sub
Author:
Option Explicit
Private Authorname As String
'##ModelId=532C692601DC
Private Publication As String
'##ModelId=532C692601DD
Private Price As Integer
Public Sub author()
End Sub
Student:
Option Explicit
'##ModelId=532C692601D3
Private StudentID As Integer
'##ModelId=532C692601D4
'##ModelId=532C692601D5
'##ModelId=532C692601D2
End Sub
RESULT:
EX.NO: 9 CREDIT CARD PROCESSING
DATE:
PROBLEM STATEMENT:
The Credit Card Processing System involves the processing of credit card. When the person applies
for credit card. There takes place some actions on both sides. A person is the one who applies for credit card
and the admin is the one who verifies the details of the person and clarifies all the information and approves
the person’s request and gives a credit card. The admin should have note about the person’s account details
and gets the information for processing the credit card.
GLOSSARY:
PERSON:
The person applies for the credit card.He submits his details and the id and details of the person are
verified. If valid, then the person obtains the credit card.
ADMIN:
The admin verifies the id and details of the person who applies for the credit card.If he finds that the
details are valid, then the admin provides him the credit card.
WORK FLOW :
APPLY:
BRIEF DESCRIPTION:
The person is the one who applies for the credit card to a particular bank. The person sends the form
after filling all details.
BASIC WORKFLOW:
The person applies for that credit card providing all the necessary information.
ALTERNATE WORKFLOW:
The person may not apply for the credit card.
PRECONDITION:
The person should get the form.
POSTCONDITION:
The person sends the form for processing it.
VERIFY:
BRIEF DESCRIPTION:
The admin is the one who verifies the details that are sent by the person.
BASIC WORKFLOW:
The admin after leaving all the details of the person starts the processing.
ALTERNATE FLOW:
The person’s application not received.
PRECONDITION:
The person should have sent the application.
POSTCONDITION:
The credit card processing is started.
PROCESS:
BRIEF DESCRIPTION:
The admin process the credit card after he/she accepts the applicant’s form for processing.
BASIC WORKFLOW:
The processing starts when all the conditions of the bank is fulfilled by the applicant.
ALTERNATE FLOW:
The form is rejected.
PRECONDITION:
The person/applicant should have sent the form.
POSTCONDITION:
The processing is done successfully.
UML DIAGRAMS:
USECASE DIAGRAM:
apply
person
verify
admin
process
obtain credit card

ACTIVITY DIAGRAM:
APPLY:
Apply
no
yes
Sent not sent
PROCESS:
Process
no
yes
complete incomplete
VERIFY:
verify
no
yes
Accept Reject
OBTAIN CREDIT CARD:
Obtain
credit card
no
yes
got no reply
CLASS DIAGRAM:
APPLY:
VERIFY:
PROCESS:
OBTAIN CREDIT CARD:
SEQUENCE DIAGRAM:
VERIFY:
Verify database
: admin
person name,person details
send
verify
display
PROCESS:
Process
: admin
bank details,account details
send details
display
OBTAIN CREDIT CARD:
credit card database
: person
credit card no,credit card info send credit card details
check
send credit card
APPLY:
1: person name,person details
Apply
: person
4: send
3: check
2: bank details
database
VERIFY:
1: person name,person details
Verify
: admin
3: verify 4: display
2: send
database
PROCESS:
3: process
2: send details
Process
database
4: display
1: bank details,account details
: admin
OBTAIN CREDIT CARD:
1: credit card no,credit card info
: person
credit card
4: send credit card
3: check
2: send credit card details
database
apply
verify
process
credit card
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
apply verify process
.
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
database
person admin
DEPLOYMENT DIAGRAM:
Keyboar
d
Process
or
Databas
e
FORMS:
Code for Form1:

If Text1.Text = "123456" And Text2.Text = "1210" Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
Code For Form2:

MsgBox ("success fully purchased")
End Sub
End
End Sub
GENERATED CODE:
Apply:
Option Explicit
'##ModelId=532CB2CE004E
Private person_name As String
'##ModelId=532CB2DB0157
Private person_details As String
'##ModelId=532CB2EA007D
Private person_bank_det As String
'##ModelId=532CB2FE01E4
Public Sub apply()
End Sub
Database1:
Option Explicit
'##ModelId=532CB313005D
'##ModelId=532CB32400EA
Private person_details As String
'##ModelId=532CB32F0138
Private person_bank_det As String
'##ModelId=532CB33E0290
Public Sub db1()
End Sub
Database2:
Option Explicit
'##ModelId=532CB3B90290
'##ModelId=532CB3C40138
Private person_bank_details As String
'##ModelId=532CB3D5032C
Public Sub db2()
End Sub
Verify:-
Option Explicit
'##ModelId=532CB38A005D
'##ModelId=532CB396009C
Private person_bank_details As String
'##ModelId=532CB3A803A9
Public Sub verify()
End Sub
RESULT:
EX.NO: 10 E-BOOK MANAGEMENT SYSTEM
DATE:
PROBLEM STATEMENT:
The user logs into the system and tries to search for a e-book online.The user enters the URL in to the address
bar,enters in to the website and finds for an option to download the e-book is being downloaded.The database
stores the details about the user and the e-book for future reference.
GLOSSARY:
USER:
The user searches for the e-book by entering the URL and then downloads the book.
LOGIN:
BRIEF DESCRIPTION:
This allows the administration to lof on to the system for searching the details for thw book.
BASIC WORKFLOW:
Administrator is provided with the username and password to login to the system.
ALTERNATIVE FLOW:
If the user enters the wrong username and password then the admin is blocked by the system.
PRE-CONDITION:
The user must have username and password allocated for him to access the system.
POST-CONDITION:
The administration is allocated to locate the eligible candidates by internet.
WEBSITE:
BRIEF DESCRIPTION:
This allows to enter the URL address of the required website for the purpose of searching.
BASIC WORKFLOW:
Each website has unique URL address .The user enters the URL address to the address bar for
accessing the website.
ALTERNATE FLOW:
If user enters wrong URL address then blocked the webpage.
PRE-CONDITION:
The user must know the correct URL address for the required website to access.
POST-CONDITION:
The administrator is allowed to allocate the web-page to access the details of the book.
SEARCH:
BRIEF DESCRIPTION:
The user enter the details of the required book then allow to search the particular book.
BASIC WORKFLOW:
The user provide the book id and author name of the book to the book bank.
ALTERNATE WORKFLOW: Nil.
PRE-CONDITION:
The user must know the book id and author name for required book to be downloaded.
POST-CONDITION:
The user must know the correct book-id and author name for required book to be downloaded.
BRIEF DESCRIPTION:
This allows to download the required book its details from the website.
BASIC WORKFLOW:
Enter the book id and author name for required books to download.
ALTERNATE FLOW:
If the id and author name is worng,the download process is blocked.
PRE-CONDITION:
Nil
POST-CONDITION:
The administrator is allowed to download the required block to the user.

USECASE DIAGRAM:
USE CASE DIAGRAM FOR E-BOOK MANAGEMENT
LOGIN
SEARCH
MODE OF PAYMENT
FREEWARE system
COST
user
DOWNLOADING BOOK
books sold at freeware books sold at cost money in e-bank

receipt received
CANCEL
update
MONEY TRANSFER
banker
database
ACTIVITY DIAGRAM:
SEARCH:
Search
Enter the book

name
Enter the author

name
Enter the
edition
Sorry ,book not

book found? found
Display
MODE OF PAYMENT:
Mode of Payment
What is your mode of paym ent?
No
Cost? Freeware?
Yes
Yes
Enter your bank account no
No
Verify?
Yes
Accepted
LOGIN:
LOGIN FOR E-BOOK
Enter your
username
Enter your
password
false
Re-enter
Verification? password
true
Accept
DOWNLOADING BOOK:
DOWNLOADING BOOK
no
ok
Download file?
yes
no Open the file

Save the file?
yes
File
downloaded
CANCEL:
Cancel
Cancel the download? Continue
File cancelled
Money
Refunded
Update
Database
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
SEARCH: SEARCH
: us er : s ystem
Enter the book name
Enter the author name
Enter the edition
Book found
Dis play
Mode of payment
: banker : us er : s ys tem
What is your m ode of paym ent
Cos t
Enter your bank acc no
Money Trans fer
verify
Receipt received
Accept
LOGIN:
Login
: us er : s ys tem
Enter us ernam e
Ener pass word
Verification
Accept
DOWNLOADING BOOK:
Downloading file
: us er : s ys tem
Download file
Save the file
File downloaded
CANCEL:
Cancel
: user : system
: banker : database
Cancel the
download
File cancelled
Money refunded Update database
SEARCH:
4:
book found
1: enter the book name

2: enter the author name
3: enter the edition
user system
5: display
MODE OF PAYMENT:
7: receipt received
banker user
4: money transfer
enter your bank acc no

6:
2: cost
5: verify what is your mode of payment
1:
3: accept
system
LOGIN:
verification
3:
1: Enter username
2:
Enter password
user system
4: Accept
DOWNLOAD BOOK:
download the file

1:
2: save the file
user system
3:
file downloaded
CANCEL:
1: money refunded
banker user
file cancelled
2:
3: cancel the download
4: update dataabase
system database
STATECHART DIAGRAM:
STATE CHART DIAG FOR E-BOOK

MANAGEMENT
Login
Search
Mode of
Payment
Downloading
book
Cancel
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
user system Database
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
database
user system
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
FORMS:
Code for Form1:

Form2.Show
Else
End
End If
End Sub
End
End Sub
Code For Form2:

End Sub
End Sub
End
End Sub
Generated Code:
Author:
Option Explicit
'##ModelId=532D5971039D
Private Book_Name As String
'##ModelId=532D59810392
Private AuthorName As String
'##ModelId=532D59A103BA
Public Sub author()
End Sub
Database
Option Explicit
'##ModelId=532D59F8023B
Private Id As String
'##ModelId=532D5A05027E
Public Sub database()
End Sub
System:
Option Explicit
'##ModelId=532D59D00369
Private speed As Integer
'##ModelId=532D59E001D7
Private Memory As String
'##ModelId=532D5A100129
Public Sub system()
End Sub
'##ModelId=532D5A190293
Public Sub downloadBook()
End Sub
USER:
Option Explicit
'##ModelId=532D594400B2
'##ModelId=532D594D0299
Private Id As String
'##ModelId=532D595A00C8
'##ModelId=532D599501A3
Public Sub login()
End Sub
'##ModelId=532D599B007C
Public Sub user()
End Sub
RESULT:
EX.NO: 11 RECRUITMENT SYSTEM
DATE:
PROBLEM STATEMENT:
A recruitment system project is a software which is used for the recruitment purpose of various
company’s or organization for the person who is eligible for the post. It alos gives access for the person who
sends the resume details to check the availability and for the details of organization .This allows the person to
send the resume online and alos software allows the administration of organization to check the details and
eligibility of each person.
GLOSSARY:
PERSON:
One who send his/her resume to the organization afterverifying the company details and eligibility
factor.
ADMINISTRATOR:
One who verifies the resume of the person who has posted his/her resume.Also checks the eligibility
nothing the post availability.
BRIEF DESCRIPTION:
This username allows the person know the information and details about the organization.
BASIC WORFLOW:
The person requests the system for gathering information that is provided by the organization.
ALTERNATE FLOW: Nil
PRE-CONDITION:
The system must display the list of available post in the organization to the user.
POST-CONDITION:
The user can check for other provided option.
ADMINISTRATION OPTION:
BRIEF DESCRIPTION:
This use-case allows the administrator to login to the system for maintaining the post allocation.
BASIC WORKFLOW:
Administrator is allowed to have user-name and password to login to the system.
ALTERNATE FLOW:
If the administrator enters wrong username and password then the admin is blocked by the system.
PRE-CONDITION:
The administrator must have username and password allocated for hiom to access the system.
POST-CONDITION:
The administrator is allowed to allocate the post according to the eligibility.
RESUME:
BRIEF DESCRIPTION:
This use-case allows the person to login for sending his/her resume and maintain a database.
BASIC WORKFLOW:
The person can have full details about the organization to which the resume is sent according to the
eligibility.
ALTERNATE FLOW: Nil
PRE-CONDITION:
The person must have logged onto the system.
POST-CONDITION:
Resume is sent to the organization.
VERIFY:
BRIEF DESCRIPTION:
This use-case allows the administrator for checking the resume that is send by the person.
BASIC WORKFLOW:
The administrator should check for the qualification and experience considering the post.
ALTERNATE FLOW:
The resume may be rejected if admin condition are not satisfied.
PRE-CONDITION:
The resume should have been send to asdministrator.
POST-CONDITION:
The person will be called for interview.
INTERVIEW:
BRIEF DESCRIPTION:
This use-case allows the admin to decide whether to select or reject the candidate.
BASIC WORKFLOW:
The person attends the interview in the company.
ALTERNATE FLOW: Nil
PRE-CONDITION:
The person should have been called for interview before.
POST-CONDITION:
The administrator conducts the interview and may or maynot be satisfied with person performance.
RESULT INTIMATION:
BRIEF DESCRIPTION:
This use-case allows the admin decide on whether to selct or reject the candidate.
BASIC WORKFLOW:
The admin sends the results intimation along with same information about selection.
ALTERNATE FLOW: Nil
PRE-CONDITION:
The person should have attended interview.
POST-CONDITION:
The intimation may be given to the person about selection.
USECASE DIAGRAM:
ACTIVITY DIAGRAM FOR RECRUITMENT PROCESS:
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
STATECHART DIAGRAM:
UML PACKAGE DIAGRAM:

COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
FORMS:
Code for Form1:

If Text1.Text = ("admin") And Text2.Text = ("1234") Then
Form2.Show
Else
MsgBox ("invalid value please re Enter")
End If
End Sub
End
End Sub
Code for Form2:

Form3.Show
End Sub
Form5.Show
End Sub
End Sub
Form6.Show
End Sub
Form1.Show
Form2.Hide
End Sub
Code for Form3:

If Text1.Text = ("306") And Text2.Text = ("raja") Then
Form4.Show
Else
MsgBox ("error")
End If
End Sub
Form2.Show
Form3.Hide
End Sub
Code for Form4:

If Text2.Text = ("BE") Then
Form7.Show
Else
MsgBox ("not eligible")
End If
End Sub
Text1.Text = (" ")
Text2.Text = (" ")
Text3.Text = (" ")
Text4.Text = (" ")
Text5.Text = (" ")
Text6.Text = (" ")
End Sub
Form2.Show
Form6.Hide
End Sub
Private Sub Form_Load()
End Sub
CODE GENERATED:
Candidate:-
Option Explicit
'##ModelId=530D2C50003E
'##ModelId=530D2C6100AB
Private D_O_B As String
'##ModelId=530D2C7A005D
Private Gender As String
'##ModelId=530D2C8601B5
'##ModelId=530D2C9201A5
Private Qualification As String
'##ModelId=530D2CD9031C
Public Sub candidate()
End Sub
HR:-
Option Explicit
'##ModelId=530D2D9C0157
'##ModelId=530D2DA90290
'##ModelId=530D2DBD0167
Private idNumber As String
'##ModelId=530D2DD2000F
Public Sub recruit()
End Sub
'##ModelId=530D2DD9033C
Public Sub HR()
End Sub
JOB PORTAL:-
Option Explicit
'##ModelId=530D2CB4037A
Private OrgReg As String
'##ModelId=530D2CC70000
Private OnlineReg As String
'##ModelId=530D2CE70196
Public Sub JobPortal()
End Sub
'##ModelId=530D2D060148
Public Sub send()
End Sub
'##ModelId=530D2D0D032C
Public Sub receive()
End Sub
'##ModelId=530D2D14037A
Public Sub infoDetails()
End Sub
JOB PORTAL DB:-

Option Explicit
'##ModelId=530D2D52003E
Public Sub store()
End Sub
'##ModelId=530D2D5A03D8
Public Sub JobPortalDB()
End Sub
ORGANISATION ATTENDER:-
Option Explicit
'##ModelId=530D2E3700FA
'##ModelId=530D2E660167
'##ModelId=530D2E720280
Private idNumber As String
'##ModelId=530D2E8502CE
Public Sub OrganisationAttender()
End Sub
ORGANISATION ONDB:-
Option Explicit
'##ModelId=530D2DF703C8
'##ModelId=530D2E020222
Public Sub OrganisationOnDb()
End Sub
RESULT:
EX.NO: 12 FOREIGN TRADE SYSTEM
DATE:
AIM:
To create a system to perform foreign trading system.
PROBLEM STATEMENT:
The main activity of international marketing is the export-import procedure. This procedure
involves the actual and operational procedure of export and import trade. It also involves
documentation, procedures, rules and regulations imposed by both the exporting and importing
countries. These procedures include excise clearance, foreign exchange, etc.
SOFTWARE REQUIREMENTS SPECIFICATION: 1.0
INTRODUCTION
Foreign trading system is the interface between the exporter and buyer. It aims at improving
the efficiency in the production, export process and reduce the complexities involved in it to the
maximum possible extent.
PURPOSE
Considering the fact that the number of buyer is increasing every year, an Automated System
becomes essential to meet the demand. So this system uses several programming and database
techniques to elucidate the work involved in this process. The system has been carefully verified
and validated in order to satisfy it.
SCOPE
The System provides an online interface to the buyer where they can fill in their personal
details and submit the necessary documents (may be by scanning). The authority concerned with the
production and shipment of goods can use this system to reduce his workload and process the
application in a speedy manner.
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
  Exporter – One who wishes to export the goods
 Importer - One who wishes to obtain the goods

 Regional authorities – Who provide service authority to individual and business
 firms intending to export and/or import goods
 IEC Number – Importer-Exporter Number

 QC – Quality Control in order to ensure the quality of products
TECHNOLOGIES TO BE USED
 HTML
 JSP
 Java script
 Java
TOOLS TO BE USED
 Eclipse IDE (Integrated Development Environment)

 Rational Rose tool (for developing UML Patterns)
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.0 OVERALL DESCRIPTION:
It will describe major role of the system components and inter-connections.
2.1 PRODUCT PERSPECTIVE
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.
2.2 SOFTWARE INTERFACE
 Front End Client - The exporter online interface is built using JSP and HTML.
 Web Server – Apache Tomcat Server (Oracle Corporation)
 Back End - Oracle 11g database 
 
2.3 HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have access to the
database in the server.
(III)USE-CASE DIAGRAM:
The Foreign Trading use cases are:
1. Preliminaries
2. Offer order
3. Production of goods
4. Shipment
5. Negotiation of documents
ACTORS INVOLVED:
1. Exporter
2. Buyer
USECASE NAME: PRELIMINARIES

Individual and business firms intending to export and/or import goods and/or services should obtain
an Importer-Exporter Number from the regional licensing authorities.
USECASE NAME: OFFER ORDER
Offer is a proposal submitted by an exporter expressing his intention to export specific goods at a
specific price with specific terms and conditions. Exporter usually makes an offer in the form of a
‘Performa Invoice’.
USECASE NAME: PRODUCTION OF GOODS
The exporting house after obtaining a confirmed order should produce the goods exactly as
specified in the invoice. If the exporting house does not have facilities, it has to procure the
products from others.
USECASE NAME: SHIPMENT
The exporter transports the goods to the buyer.
USECASE NAME: NEGOTIATION OF DOCUMENTS
The exporter submits the relevant documents to his buyer (banker) for getting the payment for the
goods exported.
Fig. USE-CASE DIAGRAM FOR FOREIGN TRADING SYSTEM
ACTIVITY DIAGRAM:
An activity diagram is a variation or special case of a state machine in which the states or activity
representing the performance of operation and transitions are triggered by the completion of
operation.
The purpose is to provide view of close and what is going on inside a use case or among several
classes. An activity is shown as rounded box containing the name of operation.
DOCUMENTATION OF ACTIVITY DIAGRAM
 Perform preliminaries activities ie, getting IEC number from regional licensing
authorities
 Submit a proposal order to the buyer
 After obtaining a confirmed order should produce the goods exactly as specifies in the
invoice.
 If the exporting house does not have production facilities, it has to procure the
products from others.
 Transport the goods to the buyer.
 The exporter submits the relevant documents to his buyer (banker) for getting the
payment for the goods exported.

STATE DIAGRAM:
A state–chart diagram shows a state machine that depicts the control flow of an object from one state to
another. A state machine portrays the sequences of states which an object undergoes due to events and their
responses to events.
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.
The Foreign Trading system class diagram consists of four classes:
1. ExporterInfo
2. OfferOrder
3. Production
4. BuyerInfo
1) EXPORTER INFO:
It consists of six attributes and two operations. The attributes are exportername, IEC_No,
Reg_no, address, contactno, and Email_id. The operations of this class are getIECNo() and getReg().
2) OFFERORDER:
This class includes the following items:

Buyer name, order_no, description of goods, price, condition of sale, payment terms
(credit, bill of exchange, etc,)
3) PRODUCTION:
It consists of packing and marking process, quality control process, shipment and
submission of documents.
4) BUYERINFO:
This class is used to maintain the buyer information such as buyer name, buyer address, etc.
Fig. CLASS DIAGRAM FOR FOREIGN TRADING SYSTEMM
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 sent from one object to another, in which the “form” 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.
Fig. SEQUENCE DIAGRAM FOR FOREIGN TRADING SYSTEM
Collaboration diagrams are interaction diagrams that illustrate the structure of the objects
that send and receive messages.
Notations − In these diagrams, the objects that participate in the interaction are shown using
vertices. The links that connect the objects are used to send and receive messages. The message is
shown as a labeled arrow
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components
of a system where the software components are deployed.
Fig. DEPLOYMENT DIAGRAM
IMPLEMENTATION OF DOMAIN OBJECTS LAYER AND TECHNICAL SERVICE

LAYER
//Source file: D:\\BuyerInfo.java
public class BuyerInfo
private String BuyerId;
private String BuyerName;
private String BuyerAddress;
private nteger BcontactNo;
private String BEmailId;
public Production theProduction;
/**
@roseuid 515917A5029F
*/
public BuyerInfo()
{
}
/**
@roseuid 515916D502DE
*/
public void SendConfirmedOrder()
//Source file: D:\\exporterInfo.java
public class exporterInfo
private String ExporterName;
private String IEC_no;
private String Reg_no;
private String Address;
private Integer ContactNo;
private String Email_id;
public OfferOrder theOfferOrder;
/**
@roseuid 515917A50213
*/
public exporterInfo()
/**
@roseuid 51591524006D
*/
public void getIECNo()
/**
@roseuid 51591530035B
*/
public void getReg()
//Source file: D:\\OfferOrder.java
public class OfferOrder
private String Order_No;
private String BuyerName;
private String DescriptionOfGoods;
private Double Price;
private String ConditionOfSale;
private String Payment_Terms;
private String StatusOfOrder;
public exporterInfo theExporterInfo;
/**
@roseuid 515917A502DE
*/
public OfferOrder()
{
}
/**
@roseuid 515917A502DE
*/
public OfferOrder()
/**
@roseuid 515916510213
*/
public void SendOfferOrder()
/**
@roseuid 5159165A009C
*/
public void RecieveRecieptOfOrder()
//Source file: D:\\Production.javaWWW.VIDYARTHIPLUS.COM
public class Production
{
private String Order_no;
private String StatusOfProduction;
private String BuyerId;
public BuyerInfo theBuyerInfo;
/**
@roseuid 515917A50261
*/
public Production()
/**
@roseuid 5159157C0186
*/
public void PackingAndMaking()
/**
@roseuid 5159158C0261
*/
public void QC()
/**
@roseuid 5159158F037A
*/
WWW.VIDYARTHIPLUS.COM
public void Shipment()
/**
@roseuid 5159159602BF
*/
public void SubmitDocuments()
RESULT:
EX.NO: 13 CONFERENCE MANAGEMENT SYSTEM
DATE:
AIM:
To implement a software for Conference management system
PROBLEM STATEMENT:
The Conference Management System is an online website in which candidate can

submit the paper and register themselves and then attend the conference. The paper will be
reviewed. The details of the conference, date and time wil l be made available to them through
the website. After getting the confirmation details the candidate should submit the revised
ready paper. Then the registration process will be done.
SOFTWARE REQUIREMENT SPECIFICATION:
1.0 INTRODUCTION
This software specification document consists full set of features and function for online
conference management system. In this we give specification about the system requirements
that are apart from the functionality of the system to perform the candidate paper valuation. It
tells the usability, reliability defined in use case specification.
1.1 PURPOSE
The purpose of the conference management system is that the system can easily review
the process. The main process in this document is the submission of paper by the candidate,
reviewing process by the reviewer and sending of acknowledgement to the candidates whose
paper is selected.
SCOPE
The scope of this conference management process is to select the best candidate from
the list of candidates based on their performance in the process.
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
 CANDIDATE - 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 - Reviewer will reviews the paper and sending acknowledgement to
the candidate
 DATABASE - Database is used to verify login and store the details of selected
candidates.
 HTML - Markup Language used for creating web pages.
 J2EE – Java 2 Enterprise Edition is a programming platform java platform for
developing and running distributed java applications.
 HTTP - Hyper Text Transfer Protocol.

 TCP/IP – Transmission Control Protocol/Internet Protocol is the communication
protocol used to connect hosts on the Internet.
TECHNOLOGIES TO BE USED
• HTML
• JSP
• Java
TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)
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.
OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIV
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.
2.2 SOFTWARE INTERFACE
  Front End Client - The exporter online interface is built using JSP and HTML.
 Web Server – Apache Tomcat Server (Oracle Corporation)

 Back End - Oracle 11g database
2.3 HARDWARE INTERFACE
The BPO system’s server is directly connected to the client systems via ftp. The client systems
have access to the database in the server.
2.4 SYSTEM FUNCTIONS
This process of on conference management system are described sequentially

through following steps,
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
2.5 USER CHARACTERISTICS
 Candidate - Logins the conference system and submits the paper then do the
registration process.
 Reviewer – Review the paper, select best candidate and send
acknowledgement to them.

2.6 CONSTRAINTS
 Although the security is given high importance, there is always a chance of

intrusion in the web world which requires constant monitoring.
 The user has to be careful while submitting the information. Much care is
required.

2.7 ASSUMPTIONS AND DEPENDENCIES
 The candidate and reviewer must have basic knowledge of computers and English
Language.

 Provide privacy and security for the documents and candidate information
( III )USECASE DIAGRAM:
A use case is a methodology used in system analysis to identify, clarify, and

organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a particular
goal. It is represented using ellipse.
Actor is any external entity that makes use of the system being modeled. It is
represented using stick figure.
The conference management system use cases are:
1. Paper submission
2. Review the paper
Send confirmation
3. details
4. Send revised paper
5. Registration
ACTORS:
Actors are as follows:
Candidate
Reviewer
ACTORS DOCUMENTATION:
 Candidate - Logins the conference system and submits the paper then do the
 registration process.
 Reviewer – Review the paper, select best candidate and send

 acknowledgement to them.
  Paper submission – Candidate submits the paper.
 Review the paper– The paper is been reviewed by the reviewer and the paper is
 selected.
 Paper confirmation details – The reviewer can send the confirmation details
 to the candidate.
 Revised and camera ready paper – After the paper is selected and the camera
 ready paper should be submitted to the reviewer by candidate.
 Registration – After submitting the revised paper the candidate wants to register.
USECASE:
Fig. UML USE CASE DIAGRAM
ACTIVITY DIAGRAM
Fig..UML ACTIVITY DIAGRAM FOR CONFERENCE MANAGEMENT SYSTEM

An activity diagram is a variation or special case of a state machine in which the states or
activity representing the performance of operation and transitions are triggered by the
completion of operation.
The purpose is to provide view of close and what is going on inside a use case or
among several classes. An activity is shown as rounded box containing the name of
operation.
UML 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. It is represented using a rectangle
with three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment with operations.
This class diagram has three classes candidate, reviewer and database.
• Candidate – Its attributes are name , collegename , department , paper title. The
operations performed in the candidate class are login, submit the paper, submit revised and
camera ready paper and registration.
• Reviewer – Its attributes are name, department, reviewer ID The operations performed
are review the paper and send the paper confirmation details.
• Database –The operations performed are storing candidate details and verifying login .
142
Fig.UML CLASS DIAGRAM
UML SEQUENCE DIAGRAM:
A sequence diagram illustrates a kind of format in which each object interacts via
message. It is generalizing between two or more specialized diagram.
143
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.
Fig. COLLABRATION DIAGRAM
COMPONENT DIAGRAM
Component diagrams are integral to building your software system. Drawn out with UML
diagramming software, they help your team understand the structure of existing systems and
then build new ones. Keep reading to learn more about component diagrams.
144
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.
Fig. DEPLOYMENT DIAGRAM
IMPLEMENTATION OF DOMAIN OBJECTS LAYER AND TECHNICAL

SERVICE LAYER
//Source file: D:\\Candidateinfo.java
public class Candidateinfo
public integer candid;
public string candname;
public integer age;
public string qualification;
public string institutionname;

145
public string gender;
public integer phoneno;
public string emailid;
public string paperTitle;
public reviewer theReviewer;
public registrations theRegistrations;
/**
@roseuid 5142F919001F
*/
public Candidateinfo()
/**
@roseuid 5142F3D10119
*/
public void submitpaper()
/**
146
@roseuid 5142F3D202CE
*/
public void sendcamreadypaper()
/**
@roseuid 5142F3D4031C
*/
public void register()
/**
void CandidateInfo.register(){
CandidateInfo.CandidateInfo()
void CandidateInfo.submitPaper(){
void CandidateInfo.sendCamReadyPaper(){
*/
//Source file: D:\\conferenceInfo.java
public class conferenceInfo

147
private string conferenceTitle;
private date dateOfConference;
private string conductingInsti;
private string address;
private string emailid;
private integer contactno;
public review theReviewer;
/**
@roseuid 513441B80222
*/
public conferenceInfo()
/**
@roseuid 513440F60167
*/
public void addConfInfo()
/**
@roseuid 5134410002BF
*/
public void updateConf()

148
//Source file: D:\\registration.java
public class registration
private integer candId;
private date regDate;
private string DDNo;
private string bankname;
private date dateofDD;
private integer noofregCan;
private time scheduleTime;
private string paperId;
public candidateInfo theCandidateInfo;
public review theReviewer;
/**
@roseuid 513441B80177
*/
public registration()
/**
@roseuid 5134416402FD
149
*/
public void confirmreg()
/**
@roseuid 5134416D0196
*/
public void sendSchedule()
//Source file: D:\\reviewer.java
public class reviewer
{ public integer reviewerid;
public string reviewername;
public string status;
public integer noofpaperrecd;
public conferenceinfo theConferenceinfo;
public registrations theRegistrations;
/**
@roseuid 5142F89301F4
*/
150
public reviewer()
/**
@roseuid 5142F3E300AB
*/
public void reiviewerpaper()
/**
@roseuid 5142F3E6008C
*/
public void sendconfirmmsg()
/**
String reviewer.reviewPaper(){
return null;
151
String reviewer.sendConfirmMsg(){
*/
RESULT:
152
EX.NO:14 BPO MANAGEMENT SYSTEM
DATE:
PROBLEM STATEMENT:
The BPO management system deals with the interaction between the employee and the customer.
Here the voice process and non-voice process takes place. In the voice process, the employee gives the
product description and queries regarding to it will be asked by the customer.
In the non-voice process, the product description is through mail. The relation between employee
and H.R is that the H.R will have the complete official and personal details of the employee.
GLOSSARY:
EMPLOYEE:
The employee gives the details about the product via voice or non-voice process to the customer.
CUSTOMER:
The customer gives the feedback on the conversation between the employee and them.
H.R:
The H.R will have the official and the personal details about the employee.
VOICE PROCESS:
BRIEF DESCRIPTION:
The voice process gives the queries asked by the customer to the employee.
BASIC WORKFLOW:
The customer asks about the product details and employee clarifies it.
ALTERNATE FLOW: Nil
PRE-CONDITION:
The employee must be in a position to answer to query asked by the customer.
POST-CONDITION:
The customer can give the feedback from the response by the employee
PERSONAL DETAILS:
BREIF DESCRIPTION:
153
The employee gives his/her basic details about himself to the company.
BASIC WORKFLOW:
The employee has to provide their personal details to the company which will be maintained by H.R.
ALTERNATE FLOW: Nil
PRE-CONDITION :
These details are to be submitted by the employee before joining company.
OFFICIAL DETAILS:
BRIEF DESCRIPTION:
The salary details,shift details,technical and non-technical details of the employee are maintained
by H.R.
BASIC WORKFLOW:
The start till the present salary database is maintained by H.R.
PRE-CONDITION: Nil
POST-CONDITION:
Once the employee is appointed the official details by the H.R.
QUERIES/COMPLAINTS:
BRIEF DESCRIPTION:
The queries and complaints related to the voice/non-voice of the employee’s conversation
regarding the product is asked by the customer.
BASIC WORKFLOW:
The cutomers asks queries related to the conversation with the employee .
ALTERNATE FLOW:
If the clarification given by the employee is not satisfactory then the customer gives a complaint
regarding the issue.
PRE-CONDITION: Nil.
POST-CONDITION:
The customer gives the feedback on the voice/non-voice process by the employee.
154
USE CASE DIAGRAM:
ACTIVITY DIAGRAM:
Enter Personal
details
Enter Official
details
Give Product
Information
Attend Complaints
and give query
Voice Process
Non Voice
Process
155
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
Employee HR Customer Database
Provide Personal details
Store Employee Personal details
Make Calls
Provide Product Information
Give Complaints for Product
Provide Queries for Complaints
Update feedback in database

156
1: Provide Personal details

Employe HR
e
4: Provide Product Information

5: Give Complaints for Product 2: Store Employee Personal details
3: Make Calls 6: Provide Queries for Complaints
7: Update feedback in database

Customer Database
STATE DIAGRAM:
Invalid details
Idle Attend Call Check Enquire Customer details[valid customer] Collect
[Invalid Customer]
Enquire Product detils
Valid Service
Solution
Ask Solution
157
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
employee customer HR
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
employee H.R customer
database
158
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
FORMS:
Code For Form1:

If Text1.Text = "Shameer" And Text2.Text = "VickyB" Then
Form2.Show
Else
End
End If
End Sub
End
End Sub
159
Code For Form2:

End Sub
End Sub
End
End Sub
CODE GENERATION:
Customer:
Option Explicit
'##ModelId=530CD73A031C
Private queries_complaints As String
'##ModelId=530CD79701B5
Public NewProperty As h.r1
'##ModelId=530CD7480242
Public Sub customer()
End Sub
HRCLASS
Option Explicit
'##ModelId=530CD75B0196
Private official_detail As String
'##ModelId=530CD76E00CB
Public Sub h_r1()
End Sub
Employee
160
Option Explicit
'##ModelId=530CD62D01A5
Private personal_details As String
'##ModelId=530CD6410157
Private official_details As String
'##ModelId=530CD79003C8
Public NewProperty As customer1
'##ModelId=530CD6AE029F
Public Sub employee()
End Sub
RESULT:
161
EX.NO: 14 LIBRARY MANAGEMENT SYSTEM
DATE:
PROBLEM STATEMENT:
Library Management system is used in the effective use of library to all of the users. This system
adopts a comprehensive approach to minimize the manual work and schedule resource, time in a cogent
manner. The user will register for the library service and admin will validate the user credentials. Users
will search for the books which is stored in the database. The system will search the database for the book
opted by the users. The librarian will display the details of the book which they can view in online
interface. The users(members) will get the books from the librarian and then return it back to the librarian.
If the user exceeded the return date for books, then member has to pay the fine also.
GLOSSARY:
MEMBER:
One who registers for library service through online interface and searches for books.
LIBRARIAN:
One who validates the user and issue book to the member.
REGISTRATION:
BRIEF DESCRIPTION:
The user register for the library service. Users request for registration and fills in the details and
then submits to the system.
BASIC WORKFLOW:
The system provides the registration form; the users fills in the details and submits.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The system must provide the proper registration from and the user fills it.
POST-CONDITION:
If the user fills in wrong details, then he is liable to penalty as per the law
162
VERIFY MEMBER:
BRIEF DESCRIPTION:
The user fills up the registration form and then submits. The admin via the online interface
responds by sending the status.
BASIC WORKFLOW:
The user after submitting the details in registration form, receives the status message.
ALTERNATIVE FLOW:
If application is not found, then it will form as invalid user id.
PRE-CONDITION:
The user id is to be mentioned correctly.
POST-CONDITION:
System fetches details for user form database.
ISSUE BOOK:
BRIEF DESCRIPTION:
The librarian checks for the book suggested by the user and issues it if the book is available and
exist.
BASIC WORKFLOW:
The administrator enter the author name to the database and send back status message to the user.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The user must submit the book details and his id has to be checked.
POST-CONDITION:
If there is any mistake in the details then the application is resent to the user to recheck the
details.
RETURN BOOK:
BRIEF DESCRIPTION:
163
The user will return the book to the librarian and pays if there is any fine.
BASIC WORKFLOW:
The user returns book and updates the database. It sends back status message to the user.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The user must submit the book to the librarian and his id has to be checked.
POST-CONDITION:
If there is any mistake in the details then the application is resent to the user to recheck the
details.
Risk Management:
(iv) Authenticity problem
(v) Updation problem.
(vi) Data coherency risk
Risk Analysis:
 Authenticity problem: Wrong details given by the applicant which may be more convincing.
 Updation problem: The problem with renewal is that you can have a separate thread to check the
renewal status of all entries in the database.

 The Applicant is given the duty to renew his/her passport on the renewal date.
Risk Monitoring:
 The practice of unauthenticated detail submission can be stated as a punishable offence by
international law.
 The book renewal date must always be noted by the verifiers before its use.
164
UML DIAGRAMS:
USE CASE DIAGRAM:
.
165
ACTIVITY DIAGRAM:
166
CLASS DIAGRAM:
167
SEQUENCE DIAGRAM:
ISSUE BOOK:
RETURN BOOK:
168
ISSUE BOOK:
RETURN BOOK:
169
PACKAGE DIAGRAM:
170
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
Processor
Students
Printer
Database
Scanner Books
Staffs
171
CODE GENERATION:-
BOOKS:
public class Books
{
private int bookid;
private int author;
private int name;
private int price;
public Books()
{
}
public void dispdetails()
{
}
public void update()
{
}
}
LIBRARIAN:
public class Librarian
{
private int name;
private int password;
/**
* @roseuid 5601132A024D
*/
public Librarian()
{
}
172
public void validate() { }

public void libr()
{
}
public void returnbooks()
{
}
}
TRANSACTION:
public class Transaction
{
private int id;
private int doi;
private int bookid;
/**
* @roseuid 5601132A026D
*/
public Transaction()
{
/**
* @roseuid 55F91EF302D7
*/
public void transaction()
{
}
}
173
MEMBER RECORD:
public class Memberrecord
{
private int memberid;
private int type;
private int date;
private int maxbooklimit;
private int name;
private int address;
public Memberrecord()
{
}
public void mem()
{
}
public void paybill()
{
}
}
BILL:
public class Bill
{ /**
* @roseuid 5601132A02BB
*/
public Bill()
{
}
}
RESULT:
174
EX.NO: 15 STUDENT INFORMATION SYSTEM

DATE:
PROBLEM STATEMENT:
A Student information system (SIS) is a software application for educational establishments to

manage student data. Student information systems provide capabilities for entering student test and other
assessment scores, building student schedules, tracking student attendance, and managing many other
student-related data needs in a school, college or university.
GLOSSARY:
STUDENT:
One who applies through online interface and checks the status of application to obtain the
students details.
ADMIN:
One who checks the genuine of the info of the student.
REGISTRATION:
BRIEF DESCRIPTION:
The application register for the student’s details. Student request for registration and fills in the
details and then submits to the system.
BASIC WORKFLOW:
The system provides the registration form; the student fills in the details and submits.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The system must provide the proper registration from and the student fills it.
POST-CONDITION:
If the student fills in wrong details, then he is liable to penalty.
CHECK STATUS:
175
BRIEF DESCRIPTION:
The student fills up the registration form and then submits. The admin via the online interface
responds by sending the status.
BASIC WORKFLOW:
The student after submitting the details in registration form, receives the status message.
ALTERNATIVE FLOW:
If application not found, then it will form as invalid student id.
PRE-CONDITION:
The student id is to be mentioned correctly.
POST-CONDITION:
System fetches details for student form database.
PROCESS APPLICATION:
BRIEF DESCRIPTION:
The administrator processes the application. The details of the student which has been submitted
are verified for genuine.
BASIC WORKFLOW:
The administrator enters the student id to the database and send back status message to the
student.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
The student must submit his details and his id has to be checked for validity.
POST-CONDITION:
If there is any mistake in the way of filling, then the application is resent to the student to recheck
the details.
VERIFICATION:
BRIEF DESCRIPTION:
176
After the application is completely verified by the administrator, sends the details to the student.
BASIC WORFLOW:
The details sent by the student are verified thoroughly by the administrator before further
proceedings.
ALTERNATIVE FLOW:
Nil
PRE-CONDITION:
Before the administrator dispatches the details to the student through post ,verification is done to
check if the details given by the student id valid.
POST-CONDITION:
The students are finally verified and admitted.
Risk Management:
(vii) Authenticity problem
(viii) Updating problem.
(ix) Data coherency risk
Risk Analysis:
 Authenticity problem: Wrong details given by the student which may be more convincing.
 Updating problem: The problem with renewal is that you can have a separate thread to check the
renewal status of all entries in the database.

 The Student is given the duty to renew his/her passport on the renewal date.
Risk Monitoring:
 The practice of unauthenticated detail submission can be stated as a punishable offence by
international law.
 The database should be verified accordingly
177
UML DIAGRAMS:
USE CASE DIAGRAM:

178
ACTIVITY DIAGRAM:
179
CLASS DIAGRAM
SEQUENCE DIAGRAM:
180
1: Login
3: Add Course
4: Add Teacher
5: Add Student
Admin 6: Add login user
Database
2: Credentials Verified
8: Login Verified
7: Student Login
9: View Course and Fees details
Student
Admin Student
Add Course Login

details
Add student
details
verify login
Add Staff Valid

details
View Course
details
Validate Login
details
181
PACKAGE DIAGRAM:
UI
MS ACCESS WEB
VB
DOMAIN
apply verify process
.
TECHNICAL SERVICE
persistent logging
object rules engine
COMPONENT DIAGRAM:
admin
applicant
managing
fees
students
enrollment
perform security
check
182
DEPLOYMENT DIAGRAM:
KEYBOARD
CPU
MOUSE
PRINTER
CODING:
login :
public class login

{
private int name;
private int username;
private int password;
/**
* @roseuid 5602430D03A0
*/
public login()
{
/**
* @roseuid 560243650123
*/
public void validtion()
{
183
/**
* @roseuid 5602436B01BF
*/
public void get_data()
{
}
student details:
public class studentDetails
{
private int address;
private int age;
private int course;
private int department;
private int phoneNo;
private int name;
/**
* @roseuid 5602447202E3
*/
public studentDetails()
{
/**
* @roseuid 5602437C00C6
*/
{
/**
* @roseuid 5602438402AB
*/public void display()

{
}
}
184
Update details:
public class updateDetails
{
private int studentDetails;
private int updateDetails;
/**
* @roseuid 560244720302
*/
public updateDetails()
{
/**
* @roseuid 560243E5030C
*/
public void updateInf()
{
/**
* @roseuid 560243EF029F
*/
{
/**
* @roseuid 560243F403D8
*/
{
public void display()
}
}
Result:
185
EXTRA EXPERIMENT
EX NO:17 HOSPITAL MANAGEMENT SYSTEM

DATE:
PROBLEM STATEMENT:
Hospital management system helps in registering information about patients and

handles patient’s query. A unique ID is generated for each patient after registration.
This helps in implementing customer relationship management and also maintains
medical history of patient.
This system also monitors the doctor appointments, when the ID is generated the
patient receives the appointment time and number from the receptionist and
accordingly visit the doctor. This system also deals with testing appointments as and
when ID is generated the patient receives the appointment time and number and
accordingly undergoes the test,
It also deals with bed allotments to various patients by checking their ID. It also
undergoes various operations by diagnosing the patients. The system identifies whether
the person is a doctor or staff and handles various activities such as draw salary and give
salary, also it adds doctor/staff information into database. This system is responsible for
handling various other activities like deleting, editing doctor/staff information into the
database. As per doctor diagnoses the patient, gives treatment and gives suggestions to
patients and prescribe laboratory tests and medicines.
This system also takes care of medical equipment, doctor visit, vitals recording, patient
case sheet, diet ordering, blood requisition, transfer information and discharge
information, maintenance of wards, inter and intrawards transfers also it generates
patient’s discharge summary which includes patients health at the time of discharge,
medical history, various diagnosis and drug prescriptions, history of patients illness and
course in hospital. Patient can pay bill through credit card, cash or cheque whose
information is maintained by this system,
186
Use Case Diagram:-

187
Activity Diagram:
188
Class Diagram:-
189
State Chart Diagram :-

190
Sequence Diagram
191
Collaboration Diagram: -
192
Component Diagram:-
Deployment Diagram:-
193
CODING & IMPLEMENTATION:
SET APPOINTMENT FORM
Option Explicit
Dim sqlcmd As String
Dim k, l As ADODB.Recordset
Dim i As Integer
Dim dn, da As Date
Dim rs As ADODB.Recordset
On Error GoTo errdesc
da = Format(DTPicker1.Value, "mm/dd/yy")
dn = Format(Now, "mm/dd/yy")
If Text1.Text = "" Then
MsgBox ("Please enter Doctor's Employee ID!!")
Exit Sub
End If
If Text2.Text = "" Then
MsgBox ("Please enter Patient's ID!!")
Exit Sub
End If
If da < dn Then
MsgBox ("Please enter a valid appiontment date!!")
Exit Sub
194
End If
sqlcmd = "insert into appt38 values (" & Text1.Text & "," & Text2.Text & ", to_date('" & da &
"','mm/dd/yy'),'" & Text3.Text & "',NULL)"
MsgBox sqlcmd
cn.Execute sqlcmd
MsgBox "Appointment Successfully Added!!"
Text1.Text = ""
If (pat = 0) Then
Text2.Text = ""
End If
Text3.Text = ""
Call refresh_grid2
Exit Sub
errdesc:
i = MsgBox(Err.Description, vbCritical)
End Sub
Dim pat_id, emp_id As Integer
Dim dn, da As Date
If (DataGrid2.Visible = True) Then
DataGrid2.Col = 0
pat_id = DataGrid2.Text
DataGrid2.Col = 1
195
emp_id = DataGrid2.Text
DataGrid2.Col = 2
da = CDate(DataGrid2.Text)
sqlcmd = "delete from appt38 where pat_id = " & Str(emp_id) & " and emp_id = " &
Str(pat_id) & " and appt_date = to_date('" & da & "','mm/dd/yy')"
MsgBox sqlcmd
cn.Execute sqlcmd
MsgBox "Appointment Deleted Successfully!!"
Text1.Text = ""
Text3.Text = ""
Call refresh_grid2
Else
MsgBox "There are no appointments to Delete."
End If
Exit Sub
errdesc:
pat_id = MsgBox(Err.Description, vbCritical)
End Sub
If return_to_main = 1 Then
Reception.Show
Else
Appt_doc.Show
End If
Unload Me
196
End Sub
Private Sub DataGrid1_Click()
DataGrid1.Col = 0
Text2.Locked = False
Text1.Text = DataGrid1.Text
Text1.Locked = True
End Sub
Dim i As Integer
Set cn = New ADODB.Connection
On Error GoTo errordesc
With cn
.ConnectionString = cmd1
.CursorLocation = adUseClient
.Open
End With
Call clear_form
If pat <> 0 Then
Text2.Text = Str(pat)
Text2.Locked = True
End If
Set l = New ADODB.Recordset

197
sqlcmd = "select emp_id,title,f_name,m_name,l_name from employee38 where title = 'Dr.'"
l.Open sqlcmd, cn, adOpenStatic, adLockOptimistic
If l.EOF And l.BOF Then
MsgBox "No Doctor Found!!"
l.Close
Else
Set DataGrid1.DataSource = l
End If
DataGrid1.Refresh
Call refresh_grid2
Exit Sub
errordesc:
End Sub
Private Sub clear_form()
Text1.Text = ""
Text3.Text = ""
End Sub
Private Sub refresh_grid2()
Set k = New ADODB.Recordset
sqlcmd = "select * from appt38 where pat_id = " & Str(pat)
k.Open sqlcmd, cn, adOpenStatic, adLockOptimistic

198
If k.EOF And k.BOF Then
DataGrid2.Visible = False
k.Close
Else
DataGrid2.Visible = True
Set DataGrid2.DataSource = k
End If
DataGrid2.Refresh
End Sub
BED ALLOCATION FORM
Private Sub Combo3_Click()
Dim i As Integer
Set rs = New ADODB.Recordset
sqlcmd = "select * from rooms38 where TYPE = '" & Combo3.Text & "' and pat_id = -1"
rs.Open sqlcmd, cn, adOpenStatic, adLockOptimistic
If rs.EOF And rs.BOF Then
MsgBox "Sorry...No such rooms/beds are empty!"
Else
Set DataGrid1.DataSource = rs
End If
199
DataGrid1.Refresh
Exit Sub
errordesc:
End Sub
Dim i, ind As Integer
Dim ad As Date
ind = DataGrid1.Col
DataGrid1.Col = 0
ad = Now
If (ind <> -1) Then
DataGrid1.Col = ind
End If
i = DataGrid1.Text
If i <> -1 Then
If MsgBox("Are you Sure you want to allocate Bed/Room '" & Str(i) & "' ?", vbOKCancel,
"Update?") = vbOK Then
sqlcmd = "Update rooms38 set PAT_ID = " & Str(temp) & ",ALLOC_DATE=to_date('" &
ad & "','mm/dd/yyyy hh:mi:ss am') where ID = " & Str(i)
MsgBox sqlcmd
cn.Execute sqlcmd
MsgBox "Bed/Room has been alloted!"

200
Reception.Show
Unload Me
End If
End If
Exit Sub
errordesc:
End Sub
Reception.Show
Unload Me
End Sub
BILLS FORM
Private Sub Combo3_Click()
Dim i As Integer
Set rs = New ADODB.Recordset
sqlcmd = "select * from rooms38 where TYPE = '" & Combo3.Text & "' and pat_id = -1"
rs.Open sqlcmd, cn, adOpenStatic, adLockOptimistic
If rs.EOF And rs.BOF Then

201
MsgBox "Sorry...No such rooms/beds are empty!"
Else
Set DataGrid1.DataSource = rs
End If
DataGrid1.Refresh
Exit Sub
errordesc:
End Sub
Dim i, ind As Integer
Dim ad As Date
ind = DataGrid1.Col
DataGrid1.Col = 0
ad = Now
If (ind <> -1) Then
DataGrid1.Col = ind
End If
i = DataGrid1.Text
If i <> -1 Then
If MsgBox("Are you Sure you want to allocate Bed/Room '" & Str(i) & "' ?", vbOKCancel,
"Update?") = vbOK Then
202
sqlcmd = "Update rooms38 set PAT_ID = " & Str(temp) & ",ALLOC_DATE=to_date('" &
ad & "','mm/dd/yyyy hh:mi:ss am') where ID = " & Str(i)
MsgBox sqlcmd
cn.Execute sqlcmd
MsgBox "Bed/Room has been alloted!"
Reception.Show
Unload Me
End If
End If
Exit Sub
errordesc:
End Sub
Reception.Show
Unload Me
End Sub
Set cn = New ADODB.Connection
With cn
.ConnectionString = cmd1
.CursorLocation = adUseClient
203
.Open
End With
Exit Sub
errordesc:
End Sub
RESULT:

OOAD LAB Record

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OOAD LAB Record

Caricato da

Copyright:

Formati disponibili

SRIRAM ENGINEERING COLLEGE

Perumalpattu, Tiruvallur Dist-602 024.

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CS6511-CASE TOOLS LAB

CLASS: III YEAR CSE

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

This is to certify that this is a bonafide record of work done by

Signature of Lab In-Charge Signature of HOD

Submitted for the Practical Examination held on __________________

Internal Examiner External Examiner

1 INTRODUCTION TO UML DIAGRAMS

2 PASSPORT AUTOMATION SYSTEM

3 BOOK BANK MANAGEMENT SYSTEM

4 EXAM REGISTRATION SYSTEM

5 STOCK MAINTENANCE SYSTEM

6 ONLINE COURSE RESERVATION SYSTEM

8 SOFTWARE PERSONNEL MANAGEMENT

9 CREDIT CARD PROCESSING

10 E-BOOK MANAGEMENT SYSTEM

12 FOREIGN TRADE SYSTEM

13 CONFERENCE MANAGEMENT SYSTEM

14 BPO MANAGEMENT SYSTEM

15 LIBRARY MANAGEMENT SYSTEM

16 STUDENT INFORMATION SYSTEM

17 HOSPITAL MANAGAMENT SYSTEM

CHARACTERISTICS OF CASE TOOLS:

1. UML class diagram:

5.State chart diagram:

Relations in the UML:

Graphically it is a solid line with hollow arrow head parent.

It is a semantic relation between classifiers. Graphically it is represented as a cross between

Where UML can be used:

UML is not limited to modeling software. In fact it is expressive to model non-software

Conceptual model be UML:

UML basic building blocks.

Some common mechanism that apply throughout the language.

Building blocks of the UML:

The vocabulary of UML encompasses these kinds of building blocks.

Use CASE diagram:

The purpose of use case is login and exchange

A person has to register himself to obtain a login ID.

A class diagram is represented as:

A change in one element affects the other

State chart diagram:

The important objectives are:

A state is a condition or situation during a life of an object in which it satisfies condition or

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

It is a final or terminal state.

Activity diagram provides a way to model the workflow of a development process. We

Collaboration diagram and sequence diagrams are alternate representations of an interaction.

Collaboration diagram shows object s, their links and their messages.

To Create Use Case Diagram

To create Activity Diagram

Use the start, activity, decision, arrow, end symbols

To create Class Diagram

For each actor create the class diagram

To Create Sequence Diagram

For each user draw the sequence diagram

Place the object messages

To Create Collaboration Diagram

Press F5 in the sequence diagram

Right click on the class  assign

To create the code template