NADAR SARASWATHI COLLEGE OF

ENGINEERING AND TECHNOLOGY

(Approved by AICTE, New Delhi and Affiliated to Anna University, Chennai)

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING

LAB MANUAL
 NADAR SARASWATHI COLLEGE OF
ENGINEERING AND TECHNOLOGY
(Approved by AICTE, New Delhi and Affiliated to Anna University, Chennai)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

LAB MANUAL
Subject Code : CCS356

Subject Name : OBJECT ORIENTED SOFTWARE ENGINEERING

Year : III

Department : Computer Science and Engineering

Semester : V

Regulation : 2021

Prepared by : Mr.R.Udhaya Kumar

Assistant Professor/CSE
Verified and : Mr.J.Mathalai Raj
Approved
HOD/CSE
by

Name
Register No
Year/Dept./Semester
Batch No
 NADAR SARASWATHI COLLEGE OF
ENGINEERING AND TECHNOLOGY
Vision
To establish ourselves as a leading technological institution.

Mission
To provide professional, constructive and learner centered education.

To make learners contribute to the development of the nation through academic

and industrial excellence.

To encourage learners involve in innovative researches with ethics.

To produce competitive and confident graduates to face the ever growing chal-
lenges of the labour market.

Department of Computer Science and Engineering

Vision
To become a leading hub in the field of Computer Engineering.

Mission
• To provide a strong theoretical and practical knowledge
emphasizing on software developments.
• To encourage autonomous learning, foster interactions and
establish partnership with renowned software industries.
• To inculcate soft skills, leadership qualities and innovative research skills with
ethical values.
 NADAR SARASWATHI COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
PROGRAM OUTCOMES (POs)
PO Graduate Attribute Program outcome

1. Engineering Apply the knowledge of mathematics, science, engineering fundamentals,

knowledge and an engi- neering specialization to the solution of complex engineering
problems.
2. Problem analysis Identify, formulate, review research literature, and analyze complex
engineering prob- lems reaching substantiated conclusions using first
principles of Mathematics, natural sciences, and engineering sciences
3. Design/developmen Design solutions for complex engineering problems and design system
t of solutions components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal,
and environmental considerations
4. Conduct Use research-based knowledge and research methods including design of
investigations of experiments, analysis and interpretation of data, and synthesis of the
complex problems information to provide valid
conclusions
5. Modern tool usage Create, select, and apply appropriate techniques, resources, and modern
engineering and IT tools including prediction and modeling to complex
engineering activities with an understanding of the limitations.
6. The engineer and Apply reasoning informed by the contextual knowledge to assess societal,
society health, safety, legal and cultural issues and the consequent responsibilities
relevant to the professional engineering practice.
7. Environment and Understand the impact of the professional engineering solutions in societal
sustain- ability: and environ- mental contexts, and demonstrate the knowledge of, and need
for sustainable develop- ment.
8. Ethics Apply ethical principles and commit to professional ethics and
responsibilities and norms of the engineering practice.

9. Individual and team Function effectively as an individual, and as a member or leader in diverse
work teams, and in multidisciplinary settings.

10. Communication Communicate effectively on complex engineering activities with the

engineering com- munity and with society at large, such as, being able to
comprehend and write effective reports and design documentation, make
effective presentations, and give and receive
clear instructions.
11. Project management Demonstrate knowledge and understanding of the engineering and
and finance management princi- ples and apply these to one’s own work, as a member
and leader in a team, to manage projects and in multidisciplinary
environments.
12. Life-long Learning Recognize the need for, and have the preparation and ability to engage in
independent and life-long learning in the broadest context of technological
change.
 NADAR SARASWATHI COLLEGE OF ENGINEERING AND
TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

PROGRAMME EDUCATIONAL OBJECTIVES (PEO)

I. Apply their technical competence in computer science to solve real world

problems, with technical and people leadership.
II. Conduct cutting edge research and develop solutions on
problems of social relevance.
III. Work in a business environment, exhibiting teams
kills, work ethics, adaptability and lifelong
learning.

PROGRAM SPECIFIC OUTCOMES (PSOs)

On successful completion of the Computer science and Engineering Degree program, the
Graduates shall exhibit the following:
PSO1: Exhibit design and programming skills to build and automate business
solutions using cutting edge technologies.

PSO2:Strongtheoreticalfoundationleadingtoexcellenceandexcitementtowardsresearch,t
o provide elegant solutions to complex problems.

PSO3: Ability to work effectively with various engineering fields as a team to

design,build and develop system applications.
 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CCS356 OBJECT ORIENTED SOFTWARE ENGINEERING

LTPC
3024

SYLLABUS

LIST OF EXPERIMENTS

1. Study of UML

2. Passport automation system.

3. Book bank
4. Exam registration
5. Stock maintenance system.
6. Online course reservation system
7. Airline/Railway reservation system
8. Software personnel management system
9. Credit card processing
10. e-book management system
11. Recruitment system
12. Foreign trading system
13. Student information system
14. Conference management system
15. BPO management system

TOTAL: 30 PERI
 NADAR SARASWATHI COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
CCS356 - Object Oriented Software Engineering Laboratory

Course Objectives
OB1: To understand Software Engineering Lifecycle Models
OB2: To Perform software requirements analysis.
OB3: To gain knowledge of the System Analysis and Design concepts using UML.
OB4: To understand software testing and maintenance approaches
OB5: To work on project management scheduling using DevOps
Course outcome
At the end of the course, the student should be able to:

COs Outcomes Bloom’s Tax-

onomy
CO1 Compare various Software Development Lifecycle Models L2

CO2 Evaluate project management approaches as well as cost and schedule L5

estimation strategies.
CO3 Perform formal analysis on specifications. L4

CO4 Use UML diagrams for analysis and design. L4

CO5 Architect and design using architectural styles and design patterns, and test the L6
system

CO-PO, PSO Correlation Matrix: (3- > Strong, 2- > Moderate, 1 – >| Low)

CO-
PO,
PO10

PO11

PO12

PSO1

PSO2

PSO3
PO1

PO2

PO3

PO4

PO5

PO6

PO7

PO8

PO9

PSO

2 2 1 2 2 - - - - 1 1 2 2 2 1
CO1
2 3 2 3 2 - - - 2 2 3 2 3 2 1
CO2

2 3 2 1 1 - - - 2 2 3 2 2 3 1
CO3

2 3 2 2 3 - - - 2 2 3 2 2 3 1
CO4
2 3 1 2 2 - - - - - - 1 3 2 2
CO5
 CO – PO MAPPING WITH EXPERIMENTS
S.NO TITLE OF EXPERIMENT CO PO
1. Study of UML CO1 1,2,3,4 ,9,11

2. Passport automation system. CO2 1,2,3,4 ,9,11

3. CO3 1,2,3,4 ,9,11

Book bank

4. CO3 1,2,3,4 ,9,11

Exam registration

5. CO3 1,2,3,4 ,9,11

Stock maintenance system.

6. CO3 1,2,3,4 ,9,11

Online course reservation system

7. CO5 1,2,3,4 ,9,11,12

Airline/Railway reservation system

8. CO5 1,2,3,4 ,9,11,12

Software personnel management system

9. CO5 1,2,3,4 ,9,11,12

Credit card processing

10. CO5 1,2,3,4 ,9,11,12

e-book management system

11. CO5 1,2,3,4 ,9,11,12

Recruitment system

12. CO5 1,2,3,4 ,9,11,12

Foreign trading system

13. CO5 1,2,3,4 ,9,11,12

Student information system

14. CO5 1,2,3,4 ,9,11,12

Conference management system

15. CO5 1,2,3,4 ,9,11,12

BPO management system
 INDEX

S.NO EXPERIMENT MARKS SIGN

Study of UML
1.
Passport automation system.
2.

Book bank
3.

4. Exam registration

5. Stock maintenance system.

6. Online course reservation system

7. Airline/Railway reservation system

8. Software personnel management system

9. Credit card processing

10. e-book management system

11. Recruitment system

12. Foreign trading system

13. Student information system

14. Conference management system

15. BPO management system

EX.NO:1 STUDY OF UML

DESCRIPTION

The heart of object-oriented problem solving is the construction of a model. The

model abstracts the essential details of the underlying problem from its usually
complicated real world. Several modeling tools are wrapped under the heading of the
UML, which stands for Unified Modeling Language. The purpose of this course is to
present important highlights of the UML.

At the center of the UML are its nine kinds of modeling diagrams, which we
describe here.

• Use case
diagrams
• Class diagrams
• Sequence
diagrams
• Collaboration
diagrams
• State chart
diagrams
• Activity diagrams
• Component
diagrams
• Deployment
diagrams

The UML is applicable to object-oriented problem solving. Anyone interested in

learning UML must be familiar with the underlying tenet of object-oriented problem
solving -- it all begins with the construction of a model. A model is an abstraction of the
underlying problem. The domain is the actual world from which the problem comes.
Models consist of objects that interact by sending each other messages. Think of an
object as "alive." Objects have things they know (attributes) and things they can do
(behaviors or operations). The values of an object's attributes determine its state.
Classes are the "blueprints" for objects. A class wraps attributes (data) and
behaviors (methods or functions) into a single distinct entity. Objects are instances of
classes.
AN INTRODUCTION TO UML DIAGRAM
The Unified Modeling Language is a language for specifying, constructing,
visualizing, and documenting the artifacts of a software- intensive system. Analogous
to the use of architectural blueprints in the construction industry, UML provides a
common language for describing software models, and it can be used in conjunction
with a wide range of software lifecycles and development processes.
USE CASE DIAGRAM
Use Case diagrams identify the functionality provided by the system (use cases),
the users who interact with the system (actors), and the association between the users
and the functionality. Use Cases are used in the Analysis phase of software development
to articulate the high-level requirements of the system. The primary goals of Use Case
diagrams include:
• Providing a high-level view of what the system does
• Identifying the users ("actors") of the system
• Determining areas needing human-computer interfaces.

GRAPHICAL NOTATION
The basic components of Use Case diagrams are,
• Actor

• Use Case
• Association.

ACTOR
An Actor, as mentioned, is a user of the system, and is depicted using a stick
figure. The role of the user is written beneath the icon. Actors are not limited to humans.
If a system communicates with another application, and expects input or delivers output,
then that application can also be considered an actor.

USE CASE
A Use Case is functionality provided by the system, typically described as verb
+ object (e.g. Register Car, Delete User). Use Cases are depicted with an ellipse. The
name of the use case is written within the ellipse.
ASSOCIATION
Associations are used to link Actors with Use Cases, and indicate that an Actor
participates in the Use Case in some form. Associations are depicted by a line
connecting the Actor and the Use Case.

The following image shows how these three basic elements work together to
form a use case diagram.

Use case diagrams describe what a system does from the standpoint of an
external observer. The emphasis is on what a system does rather than how.

Use case diagrams are helpful in three areas.

 Determining features (requirements). New use cases often generate new

requirements as the system is analyzed and the design takes shape.
 Communicating with clients. Their notational simplicity makes use case
diagrams a good way for developers to communicate with clients.
 Generating test cases. The collection of scenarios for a use case may
suggest a suite of test cases for those scenarios.

SEQUENCE DIAGRAM

Sequence diagrams document the interactions between classes to achieve a

result, such as a use case. Because UML is designed for object- oriented programming,
these communications between classes are known as messages. The Sequence diagram
lists objects horizontally, and time vertically, and models these messages over tim
NOTATION
In a Sequence diagram, classes and actors are listed as columns, with vertical
lifelines indicating the lifetime of the object over time.
OBJECT
Objects are instances of classes, and are arranged horizontally. The pictorial
representation for an Object is a class (a rectangle) with the name prefixed by the object
name (optional) and a semi-colon.

Actor
Actors can also communicate with objects, so they too can be listed as a column. An
Actor is modeled using the ubiquitous symbol, the stick figure.

LIFELINE
The Lifeline identifies the existence of the object over time. The notation for
a Lifeline is a vertical dotted line extending from an object.

ACTIVATION
Activations, modeled as rectangular boxes on the lifeline, indicate when the
object is performing an action.

MESSAGE
Messages, modeled as horizontal arrows between Activations, indicate the
communications between objects.

ACTIVITY STATES
Activity states mark an action by an object. The notations for these states are
rounded rectangles, the same notation as found in State chart diagrams.
TRANSITION
When an Activity State is completed, processing moves to another Activity State.
Transitions are used to mark this movement. Transitions are modeled using arrows.

SWIM LANE
Swim lanes divide activities according to objects by arranging objects in column
format and placing activities by that object within that column. Objects are listed at the
top of the column, and vertical bars separate the columns to form the swim lanes.

INITIAL STATE
The Initial State marks the entry point and the initial Activity State. The notation
for the Initial State is the same as in State chart diagrams, a solid circle. There can only
be one Initial State on a diagram.

FINAL STATE
Final States mark the end of the modeled workflow. There can be multiple Final
States on a diagram, and these states are modeled using a solid circle surrounded by
another circle.
COMPONENT DIAGRAM
Component diagrams fall under the category of an implementation diagram, a
kind of diagram that models the implementation and deployment of the system. A
Component Diagram, in particular, is used to describe the dependencies between
various software components such as the dependency between executable files and
source files. This information is similar to that within make files, which describe source
code dependencies and can be used to properly compile an application.

COMPONENT
A component represents a software entity in a system. Examples include source
code files, programs, documents, and resource files. A component is represented using
a rectangular box, with two rectangles protruding from the left side, as seen in the image
to the right.

DEPENDENCY
A Dependency is used to model the relationship between two components. The
notation for a dependency relationship is a dotted arrow, pointing from a component to
the component it depends on.

CLASS DIAGRAM

A Class diagram gives an overview of a system by showing its classes and the
relationships among them. Class diagrams are static -- they display what interacts but
not what happens when they do interact.

Our class diagram has three kinds of relationships.

 Association -- a relationship between instances of the two classes. There is

an association between two classes if an instance of one class must know
about the other in order to perform its work. In a diagram, an association is
a link connecting two classes.
 Aggregation -- an association in which one class belongs to a collection. An
aggregation has a diamond end pointing to the part
 containing the whole. In our diagram, Order has a collection of
OrderDetails.
 Generalization -- an inheritance link indicating one class is a superclass
of the other. A generalization has a triangle pointing to the superclass.
Payment is a superclass of Cash, Check, and Credit.
An association has two ends. An end may have a role name to clarify the nature of the
association. For example, an OrderDetail is a line item of each Order.
A navigability arrow on an association shows which direction the association can be traversed or
queried. An OrderDetail can be queried about its Item, but not the other way around. The arrow also
lets you know who "owns" the association's implementation; in this case, OrderDetail has an Item.
Associations with no navigability arrows are bidirectional.

The multiplicity of an association end is the number of possible instances of the class associated
with a single instance of the other end. Multiplicities are single numbers or ranges of numbers. In our
example, there can be only one Customer for each Order, but a Customer can have any number of
Orders.

This table gives the most common multiplicities.

Multiplicities Meaning

0..1 zero or one instance. The notation n . . m indicates n to m

instances.

0..* or * no limit on the number of instances (including none).

1 exactly one instance

1..* at least one instance

Every class diagram has classes, associations, and multiplicities. Navigability and
roles are optional items placed in a diagram to provide clarity.
PACKAGES AND OBJECT DIAGRAMS

To simplify complex class diagrams, you can group classes into packages. A package
is a collection of logically related UML elements. The diagram below is a business model in
which the classes are grouped into packages.
 Packages appear as rectangles with small tabs at the top. The package name is on the tab or
inside the rectangle. The dotted arrows are dependencies. One package depends on another if changes
in the other could possibly force changes in the first.

Object diagrams show instances instead of classes. They are useful for explaining small
pieces with complicated relationships, especially recursive relationships.

This small class diagram shows that a university Department can contain lots of other
Departments.

The object diagram below instantiates the class diagram, replacing it by a concrete example.
 Each rectangle in the object diagram corresponds to a single instance. Instance names are
underlined in UML diagrams. Class or instance names may be omitted from object diagrams as
long as the diagram meaning is still clear.

COLLABORATION DIAGRAMS

Collaboration diagrams are also interaction diagrams. They convey the same information
as sequence diagrams, but they focus on object roles instead of the times that messages are sent.
In a sequence diagram, object roles are the vertices and messages are the connecting links.

The object-role rectangles are labeled with either class or object names (or both). Class
names are preceded by colons ( : ).

Each message in a collaboration diagram has a sequence number. The top-level message
is numbered 1. Messages at the same level (sent during the same call) have the same decimal
prefix but suffixes of 1, 2, etc. according to when they occur.

STATE CHART DIAGRAMS

Objects have behaviors and state. The state of an object depends on its current activity or
condition. A statechart diagram shows the possible states of the object and the transitions that
cause a change in state.
States are rounded rectangles. Transitions are arrows from one state to another. Events or
conditions that trigger transitions are written beside the arrows. Our diagram has two self-
transition, one on Getting SSN and another on Getting PIN.

COMPONENT AND DEPLOYMENT DIAGRAMS

A component is a code module. Component diagrams are physical analogs of class diagram.
Deployment diagrams show the physical configurations of software and hardware.

The following deployment diagram shows the relationships among software and hardware
components involved in real estate transactions.
The physical hardware is made up of nodes. Each component belongs on a node.
Components are shown as rectangles with two tabs at the upper left.
EX.NO:2 PASSPORT AUTOMATION SYSTEM

AIM

To develop the passport automation system using Argo UML software, MySql
software and top implement the software in Netbeans 8.2 6.0.

PROBLEM STATEMENT

Passport Automation System is used in the e ective dispatch of passport to all of

the applicants. This system adopts a comprehensive approach to minimize the manual
work and schedule resources, time in a cogent manner. The core of the system is to get
the online registration form (with details such as name, address etc.,) filled by the
applicant whose testament is verified for its genuineness by the Passport Automation
System with respect to the already existing information in the database. This forms the
first and foremost step in the processing of passport application. After the first round of
verification done by the system, the information is in turn forwarded to the regional
administrator's (Ministry of External Aairs) once. The application is then processed
manually based on the report given by the system, and any forfeiting identified can
make the applicant liable to penalty as per the law. The system also provides the
applicant the list of available dates for appointment to 'document verification' in the
administrator's o ce, from which they can select one. The system forwards the necessary
details to the police for its separate verification whose report is then presented to the
administrator. The administrator will be provided with an option to display the current
status of application to the applicant, which they can view in their online interface. After
all the necessary criteria has been met, the original information is added to the database
and the passport is sent to the applicant.

SCOPE

The system provides an online interface to the user where they can fill their
personal details and submit the necessary documents(may be by scanning).

• The authority concerned with the issue of passport can use this system to
reduce his workload and process the application in a speedy manner.

• Provide a communication platform between the applicant and the

administrator.

• Transfer of data between the passport issuing authority and the local
SOFTWARE REQUIREMENTS SPECIFICATION

S.NO Content
1.0 Introduction
1.1 Purpose Scope
1.2 Definition, Acronyms and Abbreviations Reference
1.3 Technology to be used Tools
1.4 to be used
1.5 Overview
1.6
1.7
2.0 Overall description
2.1 Productive description
2.2 Software interface Hardware
2.3 interface System function
2.4 User Characteristic
2.5 Constraints
2.6 Assumption and Dependences
2.7

1.0 Introduction
Passport Automation System is an interface between the Applicant and the
Authority responsible for the Issue of Passport. It aims at improving the efficiency in the
Issue of Passport and reduces the complexities involved in it to the maximum possible
extent.

1.1 Purpose
If the entire process of 'Issue of Passport' is done in a manual manner then it would
take several months for the passport to reach the applicant. Considering the fact that the
number of applicants for passport is increasing every year, an Automated System becomes
essential to meet the demand. So this system uses several programming and database
techniques to elucidate the work involved in this process. As this is a matter of National
Security, the system has been carefully verified and validated in order to satisfy it.

1.2 Scope

• The System provides an online interface to the user where they can fill in their
personal details
• The authority concerned with the issue of passport can use this system to reduce
his workload and process the application in a speedy manner.
• Provide a communication platform between the applicant and the
administrator
1.3 Definitions, Acronyms and the Abbreviations
• Administrator - Refers to the super user who is the Central
Authority who has been vested with the privilege to manage the
entire system. It can be any higher official in the Regional
Passport Office of Ministry of External Affairs.
• Applicant - One who wishes to obtain the Passport. ™
PAS - Refers to this Passport Automation System.

1.4 References
IEEE Software Requirement Specification format.

1.5 Technologies To Be Used

Microsoft Netbeans 8.2 6.0

1.6 Tools To Be Used

Argo UML software, MySql 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

2.1 Product Perspective
The PAS acts as an interface between the 'applicant' and the 'administrator'. This
system tries to make the interface as simple as possible and at the same time not risking
the security of data stored in. This minimizes the time duration in which the user
receives the passport.

2.2 Software Interface

 Front End Client - The applicant and Administrator online interface is built using
Microsoft Netbeans 8.2 6.0.
 Back End – MS Access 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.

2.4 User Characteristics

 Applicant - They are the people who desires to obtain the passport and submit the
information to the database.
  Administrator - He has the certain privileges to add the passport status and to
approve the issue of passport. He may contain a group of persons under him to
verify the documents and give suggestion whether or not to approve the dispatch
of passport.
 Police - He is the person who upon receiving intimation from the PAS, perform a
personal verification of the applicant and see if he has any criminal case against
him before or at present. He has been vetoed with the power to decline an
application by suggesting it to the Administrator if he finds any discrepancy with
the applicant. He communicates via this PAS.

2.5 Constraints
 The applicants require a computer to submit their information.
 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.6 Assumptions And Dependencies

 The Applicants and Administrator must have basic knowledge of computers and
English Language.
 The applicants may be required to scan the documents and send.

UML DIAGRAMS

The following UML diagrams describe the process involved in the passport
automation system

• Use case diagram

• Class diagram
• Sequence diagram
• Collaboration diagram
• State chart diagram
• Activity diagram
• Component diagram
• Deployment diagram
• Package diagram
USE CASE DIAGRAM
CLASS DIAGRAM

STATE CHART DIAGRAM

database
 SEQUENCE DIAGRAM

COLLABORATION DIAGRAM
ACTIVITY DIAGRAM AND COMPONENT DIAGRAM

Passport
Automation

Passp Applica Poli Databa

ort
DEPLOYMENT DIAGRAM

Passport
Automation
system

Applicant Passport Databas Police

Admin e
CODINGS
FORM 1 : WELCOME FORM

Private Sub Command1_Click()

Form1.Hide
Form3.Show
End Sub
Private Sub Command2_Click()
Form1.Hide
Form2.Show
End Sub

FORM 2: APPLICATION FOR NEW PASSPORT

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
r As Integer

Private Sub Command1_Click() r =

r+1
Text8.Text = r
If (Text1.Text = "") Then MsgBox
"enter the name"

ElseIf (Text2.Text = "") Then

MsgBox "enter the age"

ElseIf (Text3.Text = "") Then

MsgBox "enter the sex"

ElseIf (Text4.Text = "") Then MsgBox

"enter the date of birth"

ElseIf (Text5.Text = "") Then

MsgBox "enter the citizenship"

ElseIf (Text6.Text = "") Then

MsgBox "enter the address"

ElseIf (Text7.Text = "") Then MsgBox

"enter the contact number"
 Else
MsgBox "updated", vbInformation con.Execute "insert into pass2 values( '" &
Text1.Text & "' , '" & Text2.Text & "' , '" & Text3.Text & "' , '" & Text4.Text &
"' , '" & Text5.Text & "' , '" & Text6.Text & "' , '" &
Text7.Text & "' , '" & Text8.Text & "' )" con.Execute
"commit"
MsgBox "Registration
complete"
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
End If
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select * from pass2", con, adOpenDynamic MsgBox "welcome
to registration"
End Sub
FORM 3 : ADMINISTRATOR LOGIN
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

con.Execute "select * from
thistocklog" Do While Not rs.EOF If
(rs.Fields(0) = Text1.Text) Then If
(rs.Fields(1) = Text2.Text) Then
Form2.Hide
Form4.Show
Text1.Text = ""
Text2.Text = ""
End If
Exit Sub
End If
Next
Loop End
Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
rs.Open "select * from thistocklog", con, adOpenDynamic End
Sub

FORM 4: SEARCHING APPLICANTS DETAILS

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
r As Integer

Private Sub Command3_Click()

con.Execute "delete from pass2 where name='" & Text1.Text & "' "
MsgBox "Successfully Deleted"
Text1.Text = ""
Text8.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
End Sub
Private Sub Command4_Click()
con.Execute "insert into pass2 values('" & Text1.Text & "','" & Text2.Text & "','" &
Text3.Text & "','" & Text4.Text & "','" & Text5.Text & "','" & Text6.Text & "','" &
Text7.Text & "','" & Text8.Text & "')"
MsgBox "Registration complete" End
Sub
Private Sub Command5_Click()
Form4.Hide
Form1.Show
End Sub
Private Sub Command6_Click()
con.Execute "select * from pass2 where name='" & Text1.Text &
"'" rs.MoveFirst Do While Not rs.EOF
If rs.Fields(0) = Text1.Text Then
Text1.Text = rs.Fields(0) Text2.Text
= rs.Fields(1) Text3.Text =
rs.Fields(2) Text4.Text = rs.Fields(3)
Text5.Text = rs.Fields(4) Text6.Text
= rs.Fields(5) Text7.Text =
rs.Fields(6) Text8.Text = rs.Fields(7)
End If
rs.MoveNext
Loop
End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select * from pass2", con, adOpenDynamic
End Sub SNAPSHOTS

WELCOME FORM
APPLICATION FOR NEW PASSPORT

ADMINISTRATOR LOGIN
SEARCHING APPLICANTS DETAILS
UPDATING APPLLICANTS DETAILS

DELETING APPLICANTS DETAILS

CONCLUSION

The System provides an online interface to the user where they can fill in their personal details
and submit the necessary documents (may be by scanning).The authority concerned with the issue
of passport can use this system to reduce his workload and process the application in a speedy
manner. It provide a communication platform between the applicant and the administrator. It
transfers data between the Passport Issuing Authority and the Local Police for verification of
applicant's information. Users/Applicants will come to know their status of application and the
date in which they must subject themselves for manual document verification.
EX.NO:3 BOOK BANK MANAGEMENT SYSTEM

AIM
To develop a project of Book bank management system using Argo UML
software, MySql Software and to implement the software in Netbeans 8.2.

PROBLEM ANALYSIS AND PROJECT DESIGN

The book bank management system is an software in which a member can register
themselves and then he can borrow books from the book bank. It mainly concentrates on
providing books for engineering students.

PROBLEM STATEMENT

The process of members registering and purchasing books from the book bank are
described sequentially through following steps:

 First the member registers himself if he was new to the book bank.
 Old members will directly select old member button..
 They select their corresponding year.
 After selecting the year they fill the necessary details and select
the book and he will be directed towards administrator
 The administrator will verify the status and issue the book.

SOFTWARE REQUIREMENT SPECIFICATION

S.NO SOFTWARE REQUIREMENTS SPECIFICATION

1 Introduction
1.1 Objective
1.2 Overview
1.3 Glossary
1.4 Purpose Scope
1.5 Functionality
1.6 Usability
1.7 Performance
1.8 Reliability
1.9

1.0 INTRODUCTION
This system would be used by members who are students of any college to check the
availability of the books and borrow the books, and then the databases are updated. The purpose
of this document is to analyze and elaborate on the high-level needs and features of the book
bank management system. It also tells the usability, reliability defined in use case specification.
 1.1 Objective
The main objective of the system was to design an online book-bank monitoring system
to enable a central monitoring mechanism of the book - bank be more faster and less error prone.
Apart from this,
 To help the students acquire the right books for the syllabus at the right time.
 To ensure availability of basic textbooks to students against limited funds and To
develop students ability to handle property loaned to them

1.2 Overview
The overview of this project is to design a tool for book bank so that it can be used by
any book banks to lend their books as well as colleges.

1.3 Glossary

TERMS DESCRIPTION
MEMBER The one who registers himself and
purchase books from the bank.
DATABASE Database is used to store the details
of members and books.
ADMINISTRATOR The one who verifies the availability
of book and issue them
USER Member
This software specification
SOFTWARE documents full set of features and
REQUIREMENT functionfor online
SPECIFICATION recruitment system that is
performed in company website.

1.4 Purpose
The purpose of the book bank management system is to reduce the manual intervention
1.5 Scope
The scope of this book bank management system is to act as a tool for book bank
administrator for quick reference, availability of the books.

1.6 Functionality
Many members will be waiting to take the book from the book bank at a single day. To
serve all the members
1.7 Usability

User interface makes the Recruitment system to be efficient. That is the system will help
the member to register easily and helps them to get their books easily. The system should be user
friendly.
1.8 Performance
 It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently.
1.9 Reliability

The book bank management system should be able to serve the applicant with correct
information and day-to-day update of information.

UML DIAGRAMS

The following UML diagrams describe the process involved in the online
recruitment system
 Use case diagram
 Class diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
 Package diagram

USE CASE 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

registration

authentications

administrator
Student1 year selection

verification
DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are member and database. The use cases are the
activities performed by actors.
 The member will register himself in the book bank.
 After registration he will select the year to which he belongs
 After selecting he will select books
 Database will verify the status of book will be given.
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 compartments the attributes and the bottom
compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM

This class diagram has 8 classes:

 Member details class- is the class name. Its attributes are name, father name, date of birth,
address, phone number, member id, college, degree, course and semester.
Its operations are registration, authentication, and year selection.
 Administrator- is the class name. Its attributes are name, address, phone, mail id. Its
operations are authentication, verification and issue books.

SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in
what order. It is a construct of a Message Sequence Chart. There are two
dimensions.

 Veritcal dimension-represent time.

 Horizontal dimension-represent different objects.
Student database administrator

registration
year selection

book selection

updation

authentication

verification

issue the book

 DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show

 The member registers himself in book bank
 He will select the year

COLLABRATION DIAGRAM

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

A sophisticated modeling tool can easily convert a collaboration diagram into a sequence
diagram and the vice versa. A collaboration diagram resembles a flowchart that portrays
the roles, functionality and behavior of individual objects as well as the overall operation
of the system in real time

2: year selection

Student
4: updation
1: registration
3: book selection

7: issue the book

5: authentication database

6: verification

administrator
 DOCUMENTATION OF COLLABORATION DIAGRAM
The collaboration diagram is to show how the member registers himself and borrow
the book from the book bank. Here the sequence is numbered according to the flow of
execution.

STATE CHART DIAGRAM

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

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.

 In the first state the member registers himself in book bank ™ After that he will
select the year in next state.
 In the next state he will select the books.
 In the next state database will update the status of book.
 In the next state administrator will log in.
 After authentication he will verify the availability of book.
 If available he will issue the book.
ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operationalstep-by-step workflows of components in a system. An activity diagram shows the
overall flow of control. An activity is shown as an rounded box containing the name of the
operation registration year selection select books updation authenticat ion verification issue book

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in book bank

management system.
 The member registers himself in book bank ™ After that he will
select the year.
 He will select the books.
 Database will update the status of book.
 Database will update the details
 Then the administrator will log in to his account.
 After authentication he will verify the availability of book.

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

Book Bank

member

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is online book bank management
systems. And member details, issue for first year, issue for second year issue for third
year and issue for fourth year are components comes under the main component

DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It
is represented by 3- dimentional box. Dependencies are represented by communication
association.
 Book Bank

member
details

year

issue for 2nd issue for 3rd year issue for 4th yea r
issue for 1st year
year year

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the book bank which is the main part and
which are the some of the main activities performed in the system. And issue for first year,
issue for second year issue for third year and issue for fourth year are some activities
performed in this system.

CODINGS

Administrator.
Class Option
Explicit
'##Model Id=4D5A2FC4038A
Private name As Variant
'##Model
Id=4D6CB83B006D
Private address As
Variant '##Model
Id=4D6CB84902DE
Private phone As Variant
'##Model
Id=4D6CB8510000
Private mail id As
Variant '##Model
Id=4D5A34780280
Public New Property As year
'##Model Id=4D5A348B0290
Public NewProperty2 As
database '##Model
Id=4D5A31B30119
Public Sub authentication ()

On Error Go To
Error Handler '##
your code goes
here...
If Form10.Text1.Text = "admin" And Form10.Text2.Text = "1234" Then
MsgBox "login successfully"
Form9
.Show
Else
MsgBox "invalid
password" End If
Call Raise Error (My Unhandled Error, "authentication Sub")
End Sub
'##Model Id=4D5A31E402BF
Public Sub
verification () On
Error Go To Error
Handler '## your
code goes here...
Exi
t
Su
b
Err
or
Ha
ndl
er:
Call Raise Error (My Unhandled Error , "verification Sub")
End Sub
'##Model Id=4D6CB8E403B9
Public Sub
issue_books() On
Error Go To Error
Handler '## your
code goes here...
Call Raise Error (My Unhandled Error, "issue_books
Sub") End Sub
'##Model Id=4D5A2FB00128
Private name As
Variant '##Model
Id=4D51082601C5
Public Sub
update () On
Error Go To
Error Handler
'## your code
goes here...
Call Raise Error (My Unhandled Error , "update
Sub") End Sub
Year .
Class
Option
Explic
it
'##Model Id=4D5A317F00DA
Private year_selection As
Variant '##Model
Id=4D5A319B0128
Public Sub
1styear() On
Error GoTo
ErrorHandler
'## your code
goes here...
Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError, "styear Sub")
End Sub
'##ModelId=4D5A319F0
0CB
Public Sub
2nd_year() On
Error GoTo
ErrorHandler
'## your code
goes here... Exit
Sub
ErrorHandler:
Call RaiseError(MyUnhandledError, "nd_year Sub")
End Sub
'##ModelId=4D5A31A2
032C
Public Sub
3rd_year() On
Error GoTo
ErrorHandler
'## your code
goes here... Exit
Sub
ErrorHandler:
Call RaiseError(MyUnhandledError, "rd_year
Sub") End Sub
Issue for first year.
class Option Explicit
'##ModelId=4D5A33
81006F
Private member_code As
Variant
'##ModelId=4D5A33810070
Private member_name As
Variant
'##ModelId=4D5A33810072
Private book_name As Variant
'##ModelId=4D5A347B03B9
Public NewProperty As year
'##ModelId=4D5A3381006E
Public Sub issue_for_first()
On Error GoTo
ErrorHandler '## your
code goes here...
Form6.Data1.Recordset.AddNew
Form6.Text5.Text = Form6.Text5.Text + 1
Form6.Text4.Text = Form6.Text4.Text - 1 If
(Form6.Text4.Text <= 0) Then
MsgBox "only four books can be selected"
Form8.Show
End If
Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError, "issue_for_first Sub") End
Sub
Issue for second year class Option
Explicit
'##ModelId=4D5A33D902EE
Private member_code As Variant
'##ModelId=4D5A33DC03D8
Private member_name As Variant
'##ModelId=4D5A33E30167
Private book_name As Variant
'##ModelId=4D5A347C03D8
Public NewProperty As year
'##ModelId=4D5A33ED00BB
Public Sub issue_for_second()
On Error GoTo ErrorHandler
'## your code goes here...
Data1.Recordset.AddNew
Form7.Text5.Text = Form7.Text5.Text + 1
Form7.Text4.Text = Text4.Text - 1
If (Form7.Text4.Text <= 0) Then
MsgBox "only four books can be selected"
Form8.Show
End If
Exit Sub
ErrorHa
ndler:
Call RaiseError(MyUnhandledError, "issue_for_second Sub") End
Sub
Issue for third year class Option
Explicit
'##ModelId=4D5A33F2036B

Private member_code As Variant

'##ModelId=4D5A33FA00EA
Private member_name As Variant
'##ModelId=4D5A34010399
Private book_name As Variant
'##ModelId=4D5A347E0138
Public NewProperty As year
'##ModelId=4D5A340F01B5
Public Sub issue_for_third() On
Error GoTo ErrorHandler '##
your
code goes here...
Form8.Data1.Recordset.AddNew
Form8.Text5.Text = Form8.Text5.Text + 1
Form8.Text4.Text = Form8.Text4.Text - 1 If
(Form8.Text4.Text <= 0) Then
MsgBox "only four books can be selected"
Form8.Show
End If
Exit Sub
ErrorHa
ndler:
Call RaiseError(MyUnhandledError, "issue_for_third Sub") End Sub
Form 1
Private Sub Command1_Click()
Form1.Show
End Sub
Private Sub Command2_Click()
Form9.Show
End Sub
Private Sub Command3_Click()
Form5.Show
End Sub
Form 2
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub Command2_Click()
Data1.Recordset.update
Form2.Show
End Sub
Form 3
Private Sub Command1_Click()
Form4.Show

End Sub
Private Sub Command2_Click()
Form6.Show
End Sub
Private Sub Command3_Click()
Form7.Show
End Sub
Form 4
Private Sub Command2_Click()
Dim fi As Issue for first year
Set fi =new Issue for first
year fi.issue_for_first End
Sub
Private Sub Command3_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text4.Text = 5
Text5.Text = 0
End Sub
Private Sub List1_Click()
Text3.Text = List1.Text
End Sub
Form 5
Private Sub Command2_Click()
Dim se As Issue for second
year Set se =new Issue for
second year
se.issue_for_second End Sub
Private Sub Command3_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text4.Text = 5
Text5.Text = 0
End Sub
Private Sub List1_Click()
Text3.Text = List1.Text
End Sub
Form 6
Private Sub Command2_Click()
Dim th As Issue for third
year Set th =new Issue for
third year
th.issue_for_third End Sub
Private Sub Command3_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text4.Text = 5
Text5.Text = 0
End Sub
Private Sub List1_Click()
Text3.Text = List1.Text
End Sub Form 7 private
Sub Command1_Click()
Dim au As Administrator
Set au =new Administrator
au. authentication End Sub
Private Sub Command2_Click() Unload
Me
End Sub
 SNAPSHOTS

HOME PAGE

MEMBERSHIP FORM
 YEAR SELECTION

ISSUE FORM – I YEAR

ISSUE FORM - I YEAR

FORM 6
ISSUE FORM – II YEAR

ISSUE FORM – III YEAR

ADMINISTRATOR LOGIN

MEMBER DETAILS
BOOK DETAILS
CONCLUSION

Thus the project to develop book bank management system using Argo UML software, MySql
Software and to implement the software in Netbeans 8.2 was done successfully.
EX.NO:4 EXAM REGISTRATION SYSTEM

AIM
To develop a project on Conference management system using Argo UML software, MySql
Software and to implement the project in Netbeans 8.2

PROBLEM STATEMENT
To create an online exam registration system that will meet the needs of the applicant
and help them in registering for the exam, cancellation for the registered exam, viewing the
schedule and result.

OVERALL DESCRIPTION
™ REGISTRATION FOR THE EXAM
In this module, the candidate can register for the exam. It is provided for both UG and PG
courses. They can register by selecting the subject. The ID is generated for each candidate
who hava been registered.

™ CANCELLATION FOR THE REGISTERED EXAM

In this module, the candidate can cancel their registration for the cancellation is done by
providing the ID of the candidate.

™ VIEWING THE SCHEDULE

In this module, the user can view the schedule for both the UG and PG
examination.
SOFTWARE REQUIREMENT SYSTEM

S.No Contents
1.0 INTRODUCTION
1.1 OBJECTIVE
1.2 OVERVIEW
1.3 GLOSSARY
1.4 PURPOSE
1.5 SCOPE
1.6 FUNCTIONALITY
1.7 USABILITY
1.8 PERFORMANCE
1.9 RELIABILITY
2.0 FUNCTIONAL REQUIREMENTS
2.1 EXTERNAL INTERFACE REQUIREMENTS
1.0 INTRODUCTION

Exam Registration application is an interface between the Student and the Authority
responsible for the Exams. It aims at improving the efficiency in the registration of exams and
reduces the complexities involved in it to the maximum possible extent.

1.1 OBJECTIVE

The main objective of Exam Registration System is to make applicants register themselves
and apply for the exam. Exam Registration System provides easy interface to all the users to
apply for the exam easily.

1.2 OVERVIEW

The overview of the project is to design an exam registration tool for the registration process
which makes the work easy for the applicant as well as the Authorities of Exam. Authorities
of the exam can keep track of and maintain the database of the registered applicants for the
exams.

1.3 GLOSSARY
Terms Description
APPLICANT OR Applicant can register himself by filling out the
STUDENT registration form and finally paying the payment for
attending the exam.
DATABASE Database is used to maintain and store the details of
registered applicants
SOFTWARE This software specification documents full set of
REQUIREMENT features and function for online recruitment system
SPECIFICATION that is performed in company website.

1.4 PURPOSE
The purpose of exam registration system is to register for the exam in an easier way
and to maintain the registered details in an effective manner.

1.5 SCOPE

The scope of this Exam Registration process is to provide an easy interface to the
applicants where they can fill their details and the authorities maintain those details in an
easy and effective way.

1.6 FUNCTIONALITY
The main functionality of registration system is to make the registration and database
for it to be maintained in an efficient manner.
1.7 USABILITY

User interface makes the Exam Registration system to be efficient. That is the
system will help the applicant to register easily and helps the authorities to maintain details
effectively. The system should be user friendly.

1.8 PERFORMANCE

It describes the capability of the system to perform the registration process of the
applicant without any error and performing it efficiently.

1.9 RELIABILITY

The Exam Registration system should be able to serve the applicant with correct
information and day-to-day update of information.

2.0 FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system.

That is the services that are provided to the applicant who apply for the Exam.

2.1 EXTERNAL INTERFACE

REQUIREMANTS

SOFTWARE REQUIREMENTS

 Front end : IBM Argo UML software, MySql enterprise edition.

 Back end : Netbeans 8.2 8.0.

HARDWARE REQUIREMENTS

 Processor : pentium 4.
 RAM : 256 mb
 Operating syatem : Microsoft windows xp.
 Free disk space : 1GB
UML DIAGRAMS

The following UML diagrams describe the process involved in the Exam
Registration System

 Use case diagram

 Class diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
 Package diagram

USE CASE DIAGRAM

login

display form

register

STUDENT
REGISTER

generate reg no

<< include >>

<< include >> maintain exam shcedule

PG

view shedule
UG

view results
CLASS DIAGRAM

SEQUENCE DIAGRAM

generate register no

maintain exam schedule

display the results

 COLLABORATION DIAGRAM
6: register

stud:stu reg:regis
dent ter
5: display form
7: generate register no

1: login
9: view the shcedule 3: login
11: view the results 8: maintain exam schedule
10: display the results

3: login
8: maintain exam schedule
4: validate 10: display the results

db

ACTIVITY DIAGRAM

NewSwimlane4 NewSwimlane5 NewSwimlane6

db

login display maitain exam

form schedule

maintain
register candidate details

generate
regno

display
results

view
results
COMPONENT DIAGRAM
exam registration
system

login register display

DEPLOYMENT DIAGRAM
exam registration
system

login register display

STATE CHART DIAGRAM

display viewing schedule

results
CODINGS FORM1:

Login

Private Sub Command1_Click()

Form2.Show
End Sub

Private Sub Command2_Click()

Form3.Show
End Sub

Private Sub Command3_Click()

End
End Sub

Form2: Student login

Private Sub Command1_Click() Form4.Show End

Sub

Private Sub Command2_Click()

Form6.Show
End Sub

Private Sub Command3_Click()

Form1.Show
End Sub

Private Sub Command4_Click()

Form9.Show
End Sub

Private Sub Command5_Click()

Form7.Show
End Sub

Form3: Registrar

Private Sub Command1_Click()

Form10.Show
End Sub
 Private Sub Command2_Click()
Form8.Show
End Sub

Private Sub Command3_Click()

Form5.Show
End Sub

Private Sub Command4_Click()

Form1.Show
End Sub

Form4: Registration for UG

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

Text4.Text = Int(Rnd() * 100000) con.Execute "insert into ug1 values('" &
Text1.Text & "','" & Text2.Text & "','" &
Text3.Text & "','" & Combo1.Text & "','" & Text4.Text & "')"

Text6.Text = Val(Text5.Text) * 100

MsgBox "Successfully Registered" End
Sub

Private Sub Command2_Click()

Form2.Show
End Sub

Private Sub Command3_Click()

Combo1.Text = ""
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text1.SetFocus
End Sub
con1.Open "Provider=MSDAORA.1;
Password=tiger;
User ID=scott;Data Source=orcl8i;
Persist Security Info=True"
rs1.Open "select
*from ug3", con, adOpenDynamic

Private Sub
Command4_Click()
con.Execute "select *from
ug1" rs.MoveFirst Do While
Not rs.EOF
If rs.Fields(0) = Text1.Text Then
Text4.Text = rs.Fields(4)
End If
rs.MoveNext
Loop
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True"
rs.Open "select *from ug1", con, adOpenDynamic
Combo1.AddItem "Software Engineering" Combo1.AddItem
"Computer Architecture" Combo1.AddItem "Computer
Networks" Combo1.AddItem "Java Programming"
Combo1.AddItem "DBMS"
End Sub

Form6: Registration for PG

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset
Private Sub Command1_Click()
Text4.Text = Int(Rnd() * 100000)
con.Execute "insert into pgg values('" & Text1.Text & "','" & Text2.Text & "','" &
Text3.Text & "','" & Combo1.Text & "','" & Text4.Text & "')"
Text6.Text = Val(Text5.Text) * 100
MsgBox "Successfully Registered" End
Sub
Private Sub
Command2_Click()

Combo1.Text = ""
 Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text1.SetFocus
End Sub

PrivateSub Command3_Click()
Form2.Show
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select *from pgg", con, adOpenDynamic Combo1.AddItem "E
COMMERCE"
Combo1.AddItem "JAVA SCRIPT" Combo1.AddItem
"MANAGEMENT DATABASE" Combo1.AddItem
"DATA STRUCTURES" Combo1.AddItem
"NETWORKING"
End Sub
Form7: Cancellation of PG

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

con.Execute "delete from pgg where id = '" & Text1.Text & "' "
MsgBox "Ur Registration is cancelled"
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub

Private Sub Command3_Click()

Text1.Text = ""
Text1.SetFocus
End Sub

Private Sub Form_Load() con.Open

"Provider=MSDAORA.1;Password=tiger;User ID=scott;Data

Source=orcl8i;Persist Security Info=True" rs.Open "select * from

pgg", con, adOpenDynamic
End Sub
Form9: Cancellation of UG

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

Text1.Text = ""
Text1.SetFocus
End Sub
Private Sub Command2_Click()
con.Execute "delete from ug1 where id = '" & Text1.Text & "' "

MsgBox "Ur Registration is cancelled"

End Sub
Private Sub Command3_Click()
Form1.Show
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select * from ug1", con, adOpenDynamic
End Sub

Form10: Schedule for UG

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
r, i As Integer
Private Sub back_Click()

Private Sub Command1_Click()

MSFlexGrid1.Visible = True
MSFlexGrid1.FixedRow
s=0
MSFlexGrid1.FixedCols
=0r=0

MSFlexGrid1.ColWidth(0) = 1000
MSFlexGrid1.ColWidth(1) = 1000
MSFlexGrid1.ColWidth(2) = 1000
MSFlexGrid1.ColWidth(3) = 2000

MSFlexGrid1.TextMatrix(0, 0) = "sno"
MSFlexGrid1.TextMatrix(0, 1) = "date"
MSFlexGrid1.TextMatrix(0, 2) = "session"
MSFlexGrid1.TextMatrix(0, 3) = "subject"
rs.MoveFirst
r= 1
 Do Until rs.EOF
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 0
MSFlexGrid1.Text = rs(0)
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 1
MSFlexGrid1.Text = rs(1)
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 2
MSFlexGrid1.Text = rs(2)
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCol
s = 3 MSFlexGrid1.Text
= rs(3) r = r + 1
rs.MoveNext
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True"
rs.Open "select * from scheug", con, adOpenDynamic End
Sub

Form8: Schedule for PG

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
r, i As Integer

Private Sub Command1_Click()

Form3.Show
End Sub

Private Sub Command2_Click()

MSFlexGrid1.FixedRow s
=0
MSFlexGrid1.FixedCols
=0r=0
MSFlexGrid1.ColWidth(0) = 1000
MSFlexGrid1.ColWidth(1) = 2000
MSFlexGrid1.ColWidth(2) = 1000
MSFlexGrid1.ColWidth(3) = 2000

MSFlexGrid1.TextMatrix(0, 0) = "sno"
MSFlexGrid1.TextMatrix(0, 1) = "date"
MSFlexGrid1.TextMatrix(0, 2) = "session"
MSFlexGrid1.TextMatrix(0, 3) =
"subject" rs.MoveFirst r = 1
Do Until rs.EOF
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 0
 MSFlexGrid1.Text = rs(0)

MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 1
MSFlexGrid1.Text = rs(1)

MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 2
MSFlexGrid1.Text = rs(2)

MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCol
s = 3 MSFlexGrid1.Text
= rs(3) r = r + 1

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True"
rs.Open "select * from schepg", con, adOpenDynamic End
Sub

Form5: Result

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
r, i As Integer

Private Sub Command1_Click()

Form1.Show
End Sub

Private Sub Command2_Click()

MSFlexGrid1.FixedRow s
=0
MSFlexGrid1.FixedCols
=0r=0
MSFlexGrid1.ColWidth(0) = 1000
MSFlexGrid1.ColWidth(1) = 1000
MSFlexGrid1.ColWidth(2) = 2000

MSFlexGrid1.TextMatrix(0, 0) = "Name"
MSFlexGrid1.TextMatrix(0, 1) = "ID"
MSFlexGrid1.TextMatrix(0, 2) = "Percentage"
rs.MoveFirst r = 1
Do Until rs.EOF
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCols = 0
MSFlexGrid1.Text = rs(0)
MSFlexGrid1.FixedRows = r
 MSFlexGrid1.FixedCols = 1
MSFlexGrid1.Text = rs(1)
MSFlexGrid1.FixedRows = r
MSFlexGrid1.FixedCol
s = 2 MSFlexGrid1.Text
= rs(2) r = r + 1

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select * from result", con, adOpenDynamic
End Sub

Form11:

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
con1 As New ADODB.Connection Dim
rs1 As New
ADODB.Recordset Private
Sub Command1_Click()
con.Execute "select * from
ug1" rs.MoveFirst Do While
Not rs.EOF
If Text1.Text = rs(0) And Text2.Text = rs(2) Then
Text3.Text = rs(1)
Text4.Text = rs(3)
Text5.Text =
rs(4) End If
rs.MoveNext
Loop
End Sub

Private Sub Command2_Click()

con1.Execute "insert into ug3 values('" & Text1.Text & "','" & Text2.Text & "','" &
Text3.Text & "','" & Text4.Text & "','" & Text5.Text & "' ,'" & Combo1.Text & "')"
MsgBox "Successfully Registered"
End Sub
Private Sub Command3_Click()
Form1.Show
End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select *from ug1", con, adOpenDynamic

Combo1.AddItem "SE"
Combo1.AddItem "CA"
Combo1.AddItem "CN"
Combo1.AddItem "Combo1.AddItem "DBMS"
End Sub

TABLE DESIGN

Table :ug1

Name Null? Type ----------------------------------

NAME
VARCHAR2(20)
AGE NUMBER
DOB VARCHAR2(20)
SUBJECT VARCHAR2(20)
ID NUMBER
NO.OF SUBJECTS NUMBER
TOTAL FEES NUMBER

Table:pgg

Name Null? Type

NAME VARCHAR2(20)
AGE NUMBER
DOB VARCHAR2(15)
SUBJECT VARCHAR2(20)
ID NUMBER
NO.OF SUBJECTS NUMBER
TOTAL FEES NUMBER

Table:scheug

Name Null? Type

- -------- SNO NUMBER

BDATE VARCHAR2(15)
SES VARCHAR2(15)
SUBJECT VARCHAR2(50)

Table:ug3
Name Null? Type

NAME VARCHAR2(20)
DOB VARCHAR2(20)
AGE NUMBER
SUBJECT VARCHAR2(20)
ID NUMBER
ANOTHERSUB VARCHAR2(20)
 SNAPSHOTS

LOGIN FORM
 REGISTRATION FORM FOR UG

REGISTRATION FORM FOR PG

 CANCELLATION FORM FOR UG

CANCELLATION FORM FOR PG

 SCHEDULR FOR UG EXAM

SCHEDULR FOR PG EXAM

RESULT FORM
CONCLUSION
Thus Exam Registration System is one which enables the registration who wishes to register
for exam through online. This helps the candidate to reduce time delays by waiting in queues
while registering for the exam. The candidate can also view the exam schedule. They can also
cancel the registered exam. In older days, all the registration details were maintained in files
which were tedious to maintain. It also occupies lot of space. All these problems can be easily
eliminated by the use of software. Thus, the software is implemented for the Exam
Registration System.
 EX.NO:5 STOCK MAINTENANCE SYSTEM

AIM

To develop a project stock maintenance system using Argo UML software, MySql Software
and to implement the software in Netbeans 8.2.

PROBLEM ANALYSIS AND PROJECT

PLANNING

The Stock Maintenance System, initial requirement to develop the project about the mechanism
of the Stock Maintenance System is caught from the customer. The requirement are analyzed
and refined which enables the end users to efficiently use Stock Maintenance System. The
complete project is developed after the whole project analysis explaining about the scope and
the project statement is prepared.
PROBLEM STATEMENT

The process of stock maintenance system is that the customer login to the
particular site to place the order for the customer product. The stock maintenance
system are described sequentially through steps

 The customer login to the particular site.

 They fill the customer details.
 They place the orders for their product.
 The vendor login and views the customer details and orders.

SOFTWARE REQUIREMENT
SPECIFICATION

S.No Contents
1.0 INTRODUCTION
1.1 OBJECTIVE
1.2 OVERVIEW
1.3 GLOSSARY
1.4 PURPOSE
1.5 SCOPE
1.6 FUNCTIONALITY
1.7 USABILITY
1.8 PERFORMANCE
1.9 RELIABILITY
2.0 FUNCTIONAL REQUIREMENTS
1. 0 INTRODUCTION

This software specification documents full set of features and function for online
stock maintenance system that is performed in company website. In this we give
specification about the customer orders. It tells the usability, reliability defined in use
case specification.

1.1 OBJECTIVE

The main objective of the stock maintenance system is to maintain the stock.
It provides the vendor to maintain the stock in an precise manner.

1.2 OVERVIEW

The overview of the project is to design an online tool for the recruitment process
which eases the work for the customer as well as the companies. Companies can create
their company forms according to their wish in which the applicant can register.

1.3 GLOSSARY

TERMS DESCRIPTION
CUSTOMER The customer can have the username and password after
login to the system. After login they directed to fill the
customer details. And the customer places their order. After
placing orders they lead to verify all the details in a single
form. Then they places the
order successfully.
VENDOR Vendor has the login id. After login vendor verify the
customer details and orders. And maintain the stocks.
DATABASE Database is used to verify the customer details and
orders.
SOFTWARE REQUIREMENT This software specification documents full set of features
SPECIFICATION and function for stock maintenance system
that is performed in company website.

1.4 PURPOSE

The purpose of stock maintenance system is to maintain the stock in an precise

manner.

1.5 SCOPE

The scope of this stock maintenance system is to maintain the stock.

1.6 FUNCTIONALITY

The main functionality of the stock maintenance system is to maintain the

stock.

1.7 USABILITY

User interface makes the stock maintenance system to be efficient. That is the
system will help the customer to place the details and orders easily and helps the vendor
to maintain the stock accurate. The system should be user friendly.

1.8 PERFORMANCE

It describes the capability of the system to maintain the stock without any loss
of stock and performing it efficiently.
1.9 RELIABILITY

The stock maintenance system should be able to maintain the stock with
correct updates from day to day placement of new orders from customer.

2.0 FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system.

That is the services that are provided to the customer who places the orders.

UML DIAGRAMS

The following UML diagrams describe the process involved in the Stock
Maintenance System

 Use case diagram

 Class diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
USECASE DIAGRAM:

A use case diagram is a graph of actors, set of use-cases enclosed by a

system boundary, communication associations between the actors and the
generalization among the use-cases.

 Actor: user playing the role. Eg: Customer

 Use-case: action done by user. Eg: Purchase the item.
 Relationship: includes, extends, generalization, uses

stock reports

customer enquiry administator stock details DB server

cancelling order

Billing balance
stocks

CLASS DIAGRAM

A class diagram, also referred to as object modeling is a main static analysis

diagram.
A class diagram is the collection of static modeling elements, such as
classes and their relationships, connected to each other and to their contents. The
classes in stock maintenance are,
 Customer

 Administrator

 Product

 Enquiry
 NADAR SARASWATHI COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CCS356- OBJECT ORIENTED SOFTWARE ENGINEERING

INTERACTION DIAGRAM
Interaction diagrams capture the behavior of a single use-case, showing the
pattern of the interaction among the objects.There are two kinds of interaction models:
 Sequence diagram
 Collaboration diagram
SEQUENCE DIAGRAM
A sequence diagram shows an interaction arranged in a time sequence. It
shows the objects participating in the interaction by their life lines and the messages
they exchange ,arranged in a time sequence.
 Vertical dimensions :life line
 Horizontal dimensions :message
NADAR SARASWATHI COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CCS356- OBJECT ORIENTED SOFTWARE ENGINEERING

customer admin DB server

1: enquire about stock

2: enter into DB

3: display details of stock

5: enter the stock

6: get stock & bill

8: again place thing into stock

COLLABORATION DIAGRAM

A collaboration diagram represents a collaboration ,which is asset of

objects related in the particular context, and interaction, which is a set of
message exchanged among the objects, here the sequence are numbered

1: enquire
about stock 4:
heck for
availability 7:
custome cancel the admin
r order

3: display details of stock

6: get stock & bill

2: enter into DB
5: enter the stock
8: again place thing into stock
DB
server
NADAR SARASWATHI COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CCS356- OBJECT ORIENTED SOFTWARE ENGINEERING

STATE CHART DIAGRAM

logi check searc plac receiv

availabili stoc orde bil

COMPONENT DIAGRAM

stock maintenance
system

customer administr DB
ator server

DEPLOYMENT DIAGRAM

stock
maint...

customer adminstrato DB server

r
 CODINGS
Form1:
Dim c as new custom
Private Sub
Command1_click()
c.enquiry
End Sub
Private Sub Command2_click()
Form5.show
End Sub
Form2:
Private Sub Command_Click( )
Data1.Recordset.Fields(0)=Text1.Text
Data1.Recordset.Fields(1)=Val(Text2.Text)
Data1.Recordset.Fields(2)=Val(Text3.Text)
Data1.Recordset.Update
Form3.Show
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub
Private Sub Command3_Click()
Data1.Recordset.AddNew
End Sub
Form3.Show
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub
Private Sub Command3_Click()
Data1.Recordset.AddNew
End Sub
Form 3:
Dim c As New customer
Private Sub
Command1_Click()
c.purchaseing
 End Sub Private Sub
Command2_Click()
c.cancelling
End Sub
Private Sub Command3_Click()
Form6.Show
End Sub
Private Sub Command4_Click()
Form1.Show
End Sub

Form 4:
Dim c As New administator
Private Sub Command1_Click()
Text4.Text = Val(Text2.Text) * Val(Text3.Text)
'MsgBox ("The product is purchased successfully")
c.stock_detail
Me.Hide
Form2.Show
End Sub
Private Sub Command2_Click() MsgBox
("Your purchase is cancelled")
Form2.Text2.Text = Form2.Text1.Text + Val(Form4.Text3.Text)
Me.Hide
Form2.Show
End Sub
Private Sub Command3_Click()
Form3.Show
End Sub
Private Sub Command4_Click()
Form6.Show
End Sub
Private Sub Text1_Change()
Data1.Recordset.MoveFirst
While Data1.Recordset.EOF = False

If Trim(Data1.Recordset.Fields(0)) = Trim(Text1.Text) Then

Text2.Text = Data1.Recordset.Fields(1)
Exit Sub
 Else
Data1.Recordset.MoveNext
End If
Wend
End Sub
Private Sub Text3_LostFocus()
Text4.Text = Val(Text3.Text) * Val(Text2.Text) End
Sub

Form 5:
Private Sub Command1_Click() If
Text1.Text = Text2.Text Then
Form7.Show
Else
MsgBox ("invalild password") End
If
End Sub
Form6:
Private Sub Command1_Click()
Form8.Show
End Sub
Private Sub Command2_Click()
Text1.Text = Form4.Text1.Text
Text2.Text = Val(Form4.Text2.Text)
Text3.Text = Val(Form4.Text3.Text)
Text4.Text = Val(Form4.Text4.Text)
End Sub
Private Sub Command3_Click()

Form1.Show
End Sub

Form 7:
Dim a As New administator Dim
p As New DB_server Private Sub
Command1_Click()
Data1.Recordset.AddNew
End Sub
 Private Sub Command2_Click()
Form1.Show
End Sub
Private Sub Command3_Click()
Data1.Recordset.Update
End Sub

Form 8:
Private Sub Command1_Click()
Text2.Text = Val(Text2.Text) - Val(Form6.Text4.Text) Data1.Recordset.MoveFirst
While Data1.Recordset.EOF = False
If Data1.Recordset.Fields(0) = Trim(Text1.Text) Then
Data1.Recordset.Edit
Data1.Recordset.Fields(1) = Val(Text2.Text)
Data1.Recordset.Update
Exit Sub
Else
Data1.Recordset.MoveNext
End If
Wend
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub

Private Sub Command3_Click() Data1.Recordset.AddNew

Data1.Recordset.Fields(0) = Text1.Text
Data1.Recordset.Fields(1) = Val(Text2.Text)
Data1.Recordset.Update
End Sub

Private Sub Command3_Click() Data1.Recordset.AddNew

Data1.Recordset.Fields(0) = Text1.Text
Data1.Recordset.Fields(1) = Val(Text2.Text)
Data1.Recordset.Update
End Sub
 Private Sub Command4_Click()
Text1.Text = ""
Text2.Text = ""
End Sub

Class Module:

Administrator:
Option Explicit
'##ModelId=4B31D12400EA
'Implements DB_server
'##ModelId=4B31D0370128
Public name As Variant
'##ModelId=4B31D03A01C5
Public address As Variant
'##ModelId=4B31D39103B9
Private mDB_serverObject As New DB_server
'##ModelId=4B31D13702EE
Public NewProperty As DB_server
'##ModelId=4B31E71B0138
Public NewProperty2 As customer
'##ModelId=4B31E7260000
Public NewProperty3 As customer
'##ModelId=4B31D08401F4
Public Sub stock_detail()
Form4.Data1.Recordset.MoveFirst
While Form4.Data1.Recordset.EOF = False
If Form4.Data1.Recordset.Fields(0) = Trim(Form4.Text1) And Form4.Data1.Recordset.Fields(2) <
Val(Form4.Text3.Text) Then
MsgBox ("Out of stock")
Exit Sub
ElseIf Form4.Data1.Recordset.Fields(0) = Trim(Form4.Text1) And
Form4.Data1.Recordset.Fields(2) >= Val(Form4.Text3.Text) Then
Form4.Data1.Recordset.Edit
Form4.Data1.Recordset.Fields(2) = Form4.Data1.Recordset.Fields(2) -
Val(Form4.Text3.Text)
Form4.Data1.Recordset.Update MsgBox
("Purchased")
Exit Sub
Else
Form4.Data1.Recordset.MoveNext End If
Wend
End Sub
'##ModelId=4B31D39103D8
Private Sub DB_server_availabity() End
Sub '##ModelId=4B31D39103D9
Private Property Get DB_server_name() As Variant End
Property
'##ModelId=4B31D3920001
Private Property Let DB_server_name(RHS As Variant)
End Property
'##ModelId=4B31D392002E
Private Property Get DB_server_pdt_name() As Variant End
Property
'##ModelId=4B31D392003E
Private Property Let DB_server_pdt_name(RHS As Variant) End Property '##ModelId=4B31D392005D
Private Property Get DB_server_quantity() As Variant End
Property
 '##ModelId=4B31D392007D
Private Property Let DB_server_quantity(RHS As Variant) End
Property

Customer:
Option Explicit
'##ModelId=4B31D01703D8
Public c_name As Variant
'##ModelId=4B31D029006D
Public address As Variant
'##ModelId=4B31D02D03D8
Public ph_no As Variant
'##ModelId=4B31D13F035B
Public NewProperty As administator
'##ModelId=4B31D14902CE
Public NewProperty2 As administator
'##ModelId=4B31D31F036B
Public NewProperty3 As administator
'##ModelId=4B31D32D035B
Public NewProperty4 As administator
'##ModelId=4B31D056003E
Public Sub login()
End Sub
'##ModelId=4B31D05B004E
Public Sub enquiry() Form2.Show
End Sub '##ModelId=4B31D061030D
 SNAPSHOTS
FORM 1:

FORM 2
FORM 3

FORM 4:
FORM 5

FORM 6
FORM 8
CONCLUSION
The stock maintenance system software has been developed using Rational
Software with Netbeans 8.2 successfully.
EX.NO:6 ONLINE COURSE RESERVATION SYSTEM

AIM

To develop the course reservation system using Argo UML software, MySql
Software and to implement the software in Netbeans 8.2.

PROBLEM STATEMENT

A Course Reservation Project is 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 category of the community which the students belong to. The student
can check for the information of the college, such that 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 time
PROBLEM ANALYSIS
™ 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.
SOFTWARE REQUIREMENT
SPECIFICATION

GLOSSARY

Generally a glossary is performed to define the entire domain used in the

problem. It defines about the storage items that are familiar to the uses it provided
these definitions and information about the attribute we are using in the particular
project to the use,

DEFINITIONS
The glossary contain the working definition for the key concept in the course
registration system
 COURSE
The course which are offered by the institution
  COURSE CATALOG
The un a bridged for all the course offered by the institution.

 GRADE
The ranking of a particular student for a particular course offered

 PROFESSOR
A person who reaches the course

 CERTIFICATE
It is the proof for the completion the course

 REGISTER
One who register the course for the student
OBJECTIVES

 The main purpose of creating the document about the software is to know
about the list of the requirement in the software project part of the project to
be developed.

 It specifies the requirement to develop a processing software part that

completes the set of requirement
.
SCOPE
 In this specification, we define about the system requirements that are about
from the functionality of the system.

 It tells the users about the reliability defined in use case specification

FUNCTIONALITY
Many members of the process line to check for its occurrences and transaction,
we are have to carry over at sometimes

USABILITY
The user interface to make the transaction should be effectively

PERFORMANCE
It is the capability about which it can performed function for many user at
sometimes efficiently (ie) without any ever occurrences
RELIABILITY
The system should be able to the user through the day to day transaction
USER OPTION
™ BRIEF DESCRIPTION
This use case allows the user to know the information and the guidance
provided to the students.

™ BASIC WORKFLOW
Student request the system for gathering the facility that is provided
by the university to the user.
™ ALTERNATE WORKFLOW
NIL
™ PRE CONDITION
The system must display the list of options available in the university to
the user.
™ POST CONDITION
User can check for their provided options.
ADMIN LOGIN
™ BRIEF DESCRIPTION
This use case allows the administrator to login on to the system for
maintaining the course allocation.

™ BASIC WORKFLOW
Administrator is provided with the username and password to login in
to the system.
™ ALTERNATE WORKFLOW
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 specified 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 WORKFLOW
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 WORKFLOW
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 students.
AVAILABILITY
™ BRIEF DESCRIPTION
This use case allows the user to check for the availability of seats in
accordance with the groups, colleges and community.
™ BASIC WORKFLOW
User had specified the college name and search for the seats in
accordance with groups and community.
 ALTERNATE WORKFLOW
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 WORKFLOW
User specifies the college name and the system shows the respective
details of the college such as address, phone number etc..,
 ALTERNATE WORKFLOW
NIL.
 PRE CONDITION
The user must logged on and access the system.
 POST CONDITION
The system shows the information of the college specified by the user.
UML DIAGRAMS

The project can be explained diagrammatically using the following diagrams.

 Use case diagram

 Class diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
 Package diagram
USE CASE 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 modelled. It is represented using stick figure.

USECASES

 Draw and drop the actors and usecases from browser window into the
diagram window.

 Associate the use cases and actors.

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

SEQUENCE DIAGRAM
 Create a new package from the database and name it as a sequence
diagram.
 From the toolbar, select the required tools and make corresponding
connections.
STATE CHART if seat available

DIAGRAM
if valid

login select and display about

register course fee of course

database update registration submit to

details of college allocate a seat

ACTIVITY DIAGRAM
 The activity diagram describes the sequencing of activities,with support for
both conditional and parallel behavior.

 The various controls are placed into the diagram window to create activity
diagram

Student Registrar Professor

COMPONENT DIAGRAM
online course
reservation

course login college

detail detail

DEPLOYMENT DIAGRAM
online course
reservation

course details login college details

CODING COURSE

FORM

Private Sub Command1_Click() Unload

Me
End Sub

Private Sub Label2_Click()

Form2.Show
End Sub

Private Sub Label3_Click() Form3.Show

End Sub

Private Sub Label4_Click() Form4.Show

End Sub

COLLEGE FORM

Dim con As New ADODB.Connection

Dim recordset As New ADODB.recordset Private Sub Command1_Click() no = Val(InputBox("Enter
the COLLID"))
con.Execute "select * from COURSE1 where collcode=' " & Text2.Text
& " ' " recordset.MoveFirst Do While Not recordset.EOF If
(recordset.Fields(1) = Text2.Text) Then
Text2.Text = recordset(1)
Text1.Text = recordset(0)
Text3.Text = recordset(2)
End If
rs.MoveNext
Loop
End Sub

Private Sub Command3_Click() Unload

Me
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
recordset.Open "select * from COURSE1", con, adOpenDynamic End Sub

SEAT AVAILABILITY FORM

Dim con As New ADODB.Connection

Dim recordset As New
ADODB.recordset Private Sub
Command1_Click() no =
Val(InputBox("ENTER THE COLLID"))

con.Execute "select * from COURSE1 where collcode=' " & Text2.Text

& " ' " recordset.MoveFirst Do While Not recordset.EOF If
(recordset.Fields(1) = Text1.Text) Then
Text2.Text = recordset(1)
Text1.Text = recordset(0)
Text3.Text = recordset(3)
Text4.Text = recordset(4)
Text5.Text = recordset(5)
Text6.Text = recordset(6)
End If recordset.MoveNext
Loop
End Sub

Private Sub Command6_Click() Unload

Me
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
recordset.Open "select * from COURSE1", con, adOpenDynamic End Sub

LOGIN FORM

Private Sub Command1_Click()

If Text1.Text = "course" And Text2.Text = "course" Then
Form5.Show
Else
MsgBox "Give correct name and password" End If
End Sub

Private Sub Command2_Click() Unload

Me
End Sub

COURSE RESERVATION FORM

Dim con As New ADODB.Connection Dim

con1 As New ADODB.Connection Dim
recordset1 As New ADODB.recordset Dim a
As Integer
Dim b As Integer

Dim recordset As New

ADODB.recordset Private Sub
Command1_Click() recordset.MoveFirst
If Not recordset.EOF Then a =
recordset.Fields(3)
If a > 0 Then
MsgBox "The ECE course has been allocated to the student" Else
MsgBox "no ECE course available"
End If
recordset.MoveFirs t
End If
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text1.SetFocus
End Sub

Private Sub
Command2_Click()
recordset.MoveFirst If Not
recordset.EOF Then a =
recordset.Fields(3) If a > 0
Then
recordset.Fields(3) = recordset.Fields(3) - 1
MsgBox "The CSE course has been allocated to the student" Else
MsgBox "no CSE course available"
End If
recordset.MoveFirs t
End If
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text1.SetFocus
End Sub
 Private Sub
Command3_Click()
recordset.MoveFirst If Not
recordset.EOF Then a =
recordset.Fields(3) If a >
0 Then

MsgBox "The ECE course has been allocated to the student" Else
MsgBox "no EEE course available"
End If
recordset.MoveFirs t
End If
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text1.SetFocus
End Sub

Private Sub
Command4_Click()
recordset.MoveFirst If Not
recordset.EOF Then a =
recordset.Fields(3) If a >
0 Then
MsgBox "The IT course has been allocated to the student" Else
MsgBox "no IT course available"
End If
recordset.MoveFirs t
End If
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text1.SetFocus
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
con1.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True" recordset.Open "select *
from COURSE1", con, adOpenDynamic recordset1.Open
"select * from app", con, adOpenDynamic End Sub

SNAPSHOTS
COURSE FORM
COLLEGE FORM
SEAT AVAILABILITY FORM

LOGIN FORM
COURSE RESERVATION FORM
 CONCLUSION
After we have completed the project we are sure the problems in the existing system
would overcome.The “ONLINE COURSE RESERVATION” process made computerised to
reduce human errors and to increase the efficiency. The maintanence of the record is
made efficient as all the records are stored in the ORACLE database . Our aim of the
project is to get the product deatails clearly and calculate the total amount. The problems
in the earlier system have been removed to a large extent.And it is expected that this project
will go a long way in satisfying user requirements.The computerisation of this system will not
only improves the efficiency but will also reduce human stress thereby indirectly improving
human resources.
EX.NO:7 E-TICKETING SYSTEM

AIM

To develop the E-Ticketing System using Argo UML software, MySql

Software and to implement the software in Netbeans 8.2

PROBLEM STATEMENT

A simple e-ticketing project provides the following facilities to passenger

reserve ticket and cancel the ticket, check availability of train and get a ticket. The train
time and source and destination are available in train details. The class, seats and coach
no are available in ticket.

SOFTWARE REQUIREMENT
SPECIFICATION

S.NO TABLE OF CONTENT

1 INTRODUCTION

1.1 Purpose

1.2 1Scope

1.3 References

1.4 Technology To Be Used

1.5 Tools Be Used

1.6 Overview

2
OVERALL DESCRIPTION
2.1 Functionality

2.2 Usability

2.3 Performance

2.4
Reliability

1.0 INTRODUCTION

1.1 Purpose
The applicant should login to the database for reserving the ticket.
1.2 Scope
In the specification use define about the system requirements that are part
from the functionality of the system. It tells the usability, reliability defined in the use
case specification.

1.3 References
IEEE Software Requirement Specification format.

1.4 Technology To Be Used

Microsoft Netbeans 8.2
6.0

1.5 Tools Be Used

Argo UML software, MySql tool (for developing UML Patterns)

1.6 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

2.1 Functionality
The database should be act as an main role of the e-ticketing system it can be
booking the ticket in easy way.

2.2 Usability
The User interface makes the Credit Card Processing System to be efficient.

2.3 Performance
It is of the capacities about which it can perform function for many users at the
same times efficiently that are without any error occurrence.

2.4 Reliability
The system should be able to process the user for their corresponding request.

UML DIAGRAMS

The following UML diagrams describe the process involved in the E-

Ticketing System

 Use case diagram

 Class diagram
  Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram ™ Package diagram

PROBLEM ANALYSIS
ACTOR
 Passenger
 Railway db
 Railway clerk

USE CASE 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 modelled. It is represented using stick figure.

USECASES

PASSENGER
 Login
 Check for availabity of tickets
 Seats

RAILWAY DATABASE
 Payment
 Update details
 Cancel the ticket

RAILWAY CLERK
 Issue form
 Fill and submit form
 Issue ticket
 Return payment

USE CASE DIAGRAM

CLASS DIAGRAM

SEQUENCE DIAGRAM
ACTIVITY DIAGRAM

COMPONENT DIAGRAM

E-ticket

login checking for

payement
availability
DEPLOYMENT DIAGRAM

E-ticket

login checking for payement

availability

COLLOBORATION DIAGRAM

pass:pass clerk:railway
enger clerk
TABLE DESIGN

TABLE : et1

Name Null? Type

----------- ID VARCHAR2(10)
PWD VARCHAR2(10)

TABLE :ett1
Name Null? Type

SOURCE VARCHAR2(20)
DEST VARCHAR2(20)
TRNAME VARCHAR2(20)
TRNO VARCHAR2(20)
COST NUMBER(20)
TICKETS VARCHAR2(20)

CODING

LOGIN FORM

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

rs.MoveFirst Do
While Not
rs.EOF
If rs(0) = Text1.Text And rs(1) = Text2.Text Then Form2.Show
Form1.Hide
End If
rs.MoveNex t
Loop
End Sub

Private Sub Command2_Click() Unload

Me
End Sub

AVAILABILITY FORM

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub Command1_Click()
rs.MoveFirst Do
While Not
rs.EOF
If Combo1.Text = rs(0) And Combo2.Text = rs(1) Then
Text1.Text = rs(2)
Text2.Text = rs(3)
Text3.Text = rs(4)
End If rs.MoveNext
Loop
End Sub

Private Sub Command2_Click()

rs.MoveFirst Do
While Not
rs.EOF
If Combo1.Text = rs(0) And Combo2.Text = rs(1) Then If
rs(5) >= Val(Text4.Text) Then
MsgBox "Tickets are available"
Else
MsgBox "Sorry!!!!!Tickets are not available" End
If
End If
rs.Move
Next
Loop End
Sub

Private Sub Command3_Click()

Form3.Show
Form2.Hide End
Sub

Private Sub Command4_Click()

Form4.Show
Form2.Hide End
Sub

Private Sub Command5_Click() Unload

Me
End Sub

Private Sub Command6_Click()

Form1.Show
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
rs.Open "select * from ett1", con,
adOpenDynamic
'rs.MoveLast
rs.MoveFirst Do
While Not rs.EOF
Combo1.AddItem
(rs(0))
Combo2.AddItem
(rs(1)) rs.MoveNext
Loop
End Sub

RESERVATION FORM

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset Dim
con1 As New ADODB.Connection Dim
rs1 As New ADODB.Recordset Dim a As
Integer
Private Sub Command1_Click()
Form1.Show
End Sub
Private Sub Command2_Click()
con.Execute "select * from ett2"
con1.Execute "select * from ett1"
rs1.MoveFirst Do
While Not rs1.EOF If
Text6.Text = rs1(3)
Then
con1.Execute "update ett1 set tickets='" & rs1(5) - Val(Text8.Text) & "' where trno='"
& Text6.Text & "'" con.Execute "insert into ett2 values('" & Text1.Text & "','" &
Text2.Text & "' , '" & Combo1.Text & "', '" & Text3.Text & "','" & Text4.Text & "','"
& Text5.Text & "','" &
Text6.Text & "','" & Text8.Text & "','" & Text9.Text & "')"
MsgBox "Ticket is reserved"
Text1.Text = ""
Text2.Text = ""

Combo1.Text = ""
Text8.Text = ""
Exit Sub
End If
rs1.Move
Next
Loop End
Sub

Private Sub Command3_Click() Unload

Me
End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
rs.Open "select * from ett2", con, adOpenDynamic
con1.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
rs1.Open "select * from ett1", con1,
adOpenDynamic
Text3.Text = Form2.Combo1.Text
Text4.Text = Form2.Combo2.Text
Text5.Text = Form2.Text1.Text
Text6.Text = Form2.Text2.Text
Text7.Text = Form2.Text3.Text
Combo1.AddItem "Male"
Combo1.AddItem "Female"
End Sub

Private Sub Text8_LostFocus()

Text9.Text = Val(Text7.Text) * Val(Text8.Text) End
Sub

CANCELLATION FORM

Dim con1 As New ADODB.Connection

Dim rs1 As New ADODB.Recordset Dim
con2 As New ADODB.Connection Dim
rs2 As New ADODB.Recordset

Private Sub Combo2_LostFocus()

rs1.MoveFirst Do
While Not
rs1.EOF

If Combo1.Text = rs1(0) And Combo2.Text = rs1(1) Then

Text3.Text = rs1(2)
Text4.Text =
rs1(3) End If
rs1.MoveNext
Loop
End Sub
Private Sub Command1_Click()
con2.Execute "select * from ett2"
con1.Execute "select * from ett1"
rs2.MoveFirst Do
While Not
rs2.EOF
If rs2(0) = Text1.Text And rs2(1) = Text2.Text Then
con2.Execute "delete ett2 where name='" & Text1.Text & "' and age='" & Text2.Text
 &
"'"
rs1.MoveFirst Do While
Not rs1.EOF If
Text4.Text = rs1(3)
Then
con1.Execute "update ett1 set tickets='" & rs1(5) + Val(Text5.Text) & "' where
trno='" &
Text4.Text & "'"
MsgBox "Ticket is cancelled"
'Text1.Text = ""
'Text2.Text = ""
'Combo1.Text = ""
'Text8.Text =
"" End If
rs1.MoveNext
Loop
Exit Sub
End If
rs2.Move
Next
Loop End
Sub
Private Sub Command2_Click()
Form1.Show
End Sub

Private Sub Form_Load()

con1.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data

Source=orcl8i;Persist Security Info=True" rs1.Open

"select * from ett1", con1, adOpenDynamic
con2.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True"
rs2.Open "select * from ett2", con2,
adOpenDynamic rs1.MoveFirst Do While Not
rs1.EOF
Combo1.AddItem
(rs1(0))
Combo2.AddItem
(rs1(1))
rs1.MoveNext Loop
End Sub

SNAPSHOTS
LOGIN FORM
AVAILABILITY FORM

RESEVATION FORM
CANCELLATION FORM
CONCLUSION
The project for “E-TICKETING” was created and the ticket was reserved successfully. If we
want to cancel the ticket means that also available in this project. Before reserve ticket we check
the availability of tickets using some source and destination place.

EX.NO:8 SOFTWARE PERSONAL MANAGEMENT SYSTEM

AIM
To develop the Software personal management system using Argo UML
software, MySql Software and to implement the software in Netbeans 8.2.
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 Netbeans
8.2 6.0 and ORACLE.
OVERALL DESCRIPTION
The three modules are
™ Entry form
The employee details, edit details and exit command buttons are present.
We can choose the required command button. ™ Pay slip form
Fill in the form with details such as employee id, employee name,
department, experience, and basic pay in the text boxes and submit using
CALCULATE command button Update it in the database using UPDATE
command button.
™ Database form
Updated database would be present. We can search for the required
Pay details using SEARCH command button

SOFTWARE REQUIREMENT
SPECIFICATION

S. NO Table of Contents

1.0 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 References

1.4 Technology To Be Used

1.5 Tools Be Used

 1.6 Overview

2.0 OVERALL DESCRIPTION

2.1 Functionality

2.2 Usability

2.3 Performance

2.4
Reliability

1.1 Purpose
The main purpose of creating the document about the software is to know about
the list of requirements that is to be developed.

1.2 Scope
It specifies the requirements to develop a processing software part that complete
the set of requirements. In this specification, we define about the system requirements
that are apart from the functionality of system

1.3 References
IEEE Software Requirement Specification format.

1.4 Technology to Be Used

Microsoft Netbeans 8.2
6.0 .
1.5 Tools Be Used
Argo UML software, MySql tool (for developing UML Patterns)

1.6 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

2.1 Functionality
The database should be act as an main role of the e-ticketing system it can be
booking the ticket in easy way.

2.2 Usability
The User interface makes the Credit Card Processing System to be efficient.
2.3 Performance
It is of the capacities about which it can perform function for many
users at the same times efficiently that are without any error occurrence.

2.4 Reliability
The system should be able to process the user for their corresponding request.

UML DIAGRAMS

The project can be explained diagrammatically using the following diagrams.

 Use case diagram

 Class diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
 Package diagram

USE CASE 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 modelled. It is represented using stick figure.

USECASES

 Draw and drop the actors and usecases from browser window into the
diagram window.

 Associate the usecases and actors.

CLASS DIAGRAM
A class diagram describes the type of objectrs in the system the various kinds
of static relationship that exist among them.
SEQUENCE DIAGRAM
 Create a new package from the database and name it as a sequence
diagram.
 From the toolbar, select the required tools and make
corresponding connections.
employee2 : allowance : db1 : db controller3 :
employee1 department controller2

view emp details

calculate

calcutate netpay

saves salary

issue payslip

COLLOBORATION DIAGRAM
allowance :
department
employee2 :
employee1

1: view em p details 2: calculate

5: issue payslip

3: calcutate netpay

controller3 :
db1 : db controller2

4: saves salary
ACTIVITY DIAGRAM

The activity diagram describes the sequencing of activities,with support for both
conditional and parallel behavior.

 The various controls are placed into the diagram window to create activity
diagram.

COMPONENT DIAGRAM

<stand>
emp <stand
>
con

CODINGS
FORM1
Dim loginname As String, password As String Dim
flag As Boolean
Dim ctr As Integer

Private Sub Command1_Click()

flag = False
loginname =
Text1.Text password
= Text2.Text ctr = ctr
+1
If loginname = "karthi" And password = "karthi" Then MsgBox
"welcome to payroll system"

Form2.Show
Me.Hide
ctr = 0
Else
If ctr < 3 Then
MsgBox "incorrect username or password plz try again"
Text1.SetFocus
Else
MsgBox "unauthorized access" Me.Hide
End If
End If
End Sub

Private Sub command2_Click()

Form3.Show
End Sub
FORM2
Private Sub Command1_Click()
Form5.Show
End Sub
Private Sub command2_Click()
Form4.Show
End Sub
Private Sub Command3_Click() Me.Hide
End Sub

FORM3
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

con.Execute "select * from
user1" Do While Not rs.EOF
If (rs.Fields(0) = Text1.Text) Then If
(rs.Fields(1) = Text2.Text) Then
MsgBox "success"
Form3.Hide
Form6.Show
Text1.Text = ""
Text2.Text = ""
End If

Exit Sub
End If
rs.Move
Next
Loop End
Sub
Private Sub command2_Click() Me.Hide
End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;User
ID=scott;PassWord=tiger;Data Source=orcl8i;Persist Security
Info=False" rs.Open "select * from user1", con, adOpenDynamic
End Sub

FORM4
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

con.Execute "insert into karthikemp values('" & Text1.Text & "','" & Text2.Text &
"','" &
Text3.Text & "','" & Text4.Text & "','" & Text5.Text & "')"
MsgBox "inserted"
End Sub
Private Sub Command3_Click()
Form5.Show
End Sub

Private Sub Command4_Click() Me.Hide

End Sub

Private Sub
command5_Click()
rs.MoveFirst Text1.Text
= rs(0) Text2.Text
= rs(1) Text3.Text
= rs(2) Text4.Text
= rs(3) Text5.Text
= rs(4) End Sub
Private Sub
Command6_Click()
rs.MovePrevious If Not
rs.BOF Then Text1.Text
= rs(0) Text2.Text =
rs(1) Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Else
MsgBox "Record pointer is in the first record" End If
End Sub

Private Sub
Command7_Click()
rs.MoveNext If rs.EOF
Then
MsgBox "Record pointer is in the last
record" rs.MoveFirst Else
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
End If
End Sub

Private Sub
Command8_Click()
rs.MoveLast Text1.Text =
rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
End Sub

Private Sub Command9_Click()

Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""

Text5.Text = ""
End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;User ID=scott;PassWord=tiger;Data
Source=orcl8i;Persist Security Info=False"
rs.Open "select * from karthikemp", con, adOpenDynamic End
Sub

FORM5:
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset Dim
con1 As New ADODB.Connection Dim
rs1 As New ADODB.Recordset

Private Sub Command1_Click()

con.Execute "select * from karthikemp"
rs.MoveFirst Do
While Not rs.EOF
If Text1.Text = rs(0) Then

Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text =
rs(4) End If
rs.MoveNext
Loop
End Sub

Private Sub command2_Click() Me.Hide

End Sub
 Private Sub Command3_Click()
If (Val(Text5.Text) < 25000) Then
Text7.Text = Val(Text5.Text) * 0.1
Text6.Text = Val(Text5.Text) * 0.3
Text8.Text = 100
Text9.Text = 600
Text10.Text = Val(Text5.Text) * 0.1
End If

If (Val(Text5.Text) >= 25000) And (Val(Text5.Text) < 30000) Then Text7.Text =

Val(Text5.Text) * 0.15
Text6.Text = Val(Text5.Text) * 0.4
Text8.Text = 200
Text9.Text = 700
Text10.Text = Val(Text5.Text) * 0.15
End If
If (Val(Text5.Text) >= 30000) Then
Text7.Text = Val(Text5.Text) * 0.2
Text6.Text = Val(Text5.Text) * 0.5
Text8.Text = 300
Text9.Text = 800
Text10.Text = Val(Text5.Text) * 0.2 End
If
Text11.Text = Val(Text5.Text) + Text7.Text + Text6.Text + Text8.Text Text12.Text
= Val(Text11.Text) - Text9.Text - Text10.Text
End Sub
Private Sub Command4_Click()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""
Text12.Text = "" End
Sub
Private Sub command5_Click() con1.Execute "insert into karthikemp1 values('" &
Text1.Text & "','" & Text2.Text & "','" & Text3.Text & "','" &
Text4.Text & "','" & Text5.Text & "','" & Text6.Text & "','" &
Text7.Text & "','" & Text8.Text & "','" & Text9.Text & "','" & Text10.Text & "','" &
Text11.Text & "','" & Text12.Text & "')"
MsgBox "inserted" End Sub
Private Sub Command7_Click()
DataReport1.Show
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;User
ID=scott;PassWord=tiger;Data Source=orcl8i;Persist Security
Info=False" rs.Open "select * from karthikemp", con,
adOpenDynamic
con1.Open "Provider=MSDAORA.1;User ID=scott;PassWord=tiger;Data
Source=orcl8i;Persist Security Info=False"
rs1.Open "select * from karthikemp1", con, adOpenDynamic End
Sub

FORM6:
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

con.Execute "select * from karthikemp1"
rs.MoveFirst

Do While Not rs.EOF

If Text1.Text = rs(0) Then
Text2.Text = rs(1) Text3.Text
= rs(2) Text4.Text = rs(3)
Text5.Text = rs(4) Text6.Text
= rs(5) Text7.Text = rs(6)
Text8.Text = rs(7) Text9.Text
= rs(8) Text10.Text = rs(9)
Text11.Text = rs(10)
Text12.Text =
rs(11) End If
rs.MoveNext
Loop
End Sub

Private Sub command2_Click()

Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""
Text12.Text = ""
End Sub

Private Sub Command3_Click() Me.Hide

End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;User ID=scott;PassWord=tiger;Data
Source=orcl8i;Persist Security Info=False"
rs.Open "select * from karthikemp1", con, adOpenDynamic End
Sub
SNAPSHOTS
LOGIN FORM

FORM 2
ENTERING DETAILS AND INSERTING INTO DATABASE

DISPLAYING FIRST RECORD

DISPLAYING THE LAST RECO RD

PAYROLL FORM
CALCULATE

EMPLOYEE LOGIN
EMPLOYEE SEARCH DETAILS FORM
CONCLUSION
After we have completed the project we are sure the problems in the existing
system would overcome.The “ONLINE COURSE RESERVATION” process made
computerised to reduce human errors and to increase the efficiency. The
maintanence of the record is made efficient as all the records are stored in the
ORACLE database . Our aim of the project is to get the product deatails clearly
and calculate the total amount. The problems in the earlier system have been
removed to a large extent.And it is expected that this project will go a long way in
satisfying user requirements.The computerisation of this system will not only
improves the efficiency but will also reduce human stress thereby indirectly improving
human resources.
EX.NO:9 CREDIT CARD SYSTEM
AIM

To develop a project credit card system using the Argo UML software, MySql
Software from the UML diagram and to implement the software in Netbeans 8.2

PROBLEM STATEMENT

To develop an CREDIT CARD PROCESSING SYSTEM for the Bank

System developed should contain the following features.
 The Customer login into the system using Credit Card No and Pin
Number. The system checks for validation.

 The System queries the customer for the type of account either S.B
Account or Credit. After getting the type of account the system shows
the amount left.

 The System then queries the customer for required amount. The user
enters the amount to be purchased and it is debited from his account.

SOFTWARE REQUIREMENT
SPECIFICATION

S.No Contents
1.0 INTRODUCTION
1.1 PURPOSE OVERVIEW
1.2 REFERENCES
1.3 TECHNOLOGY TO BE USED
1.4 TOOLS TO BE USED
1.5
2.1 PRODUCT PERSPECTIVE
2.2 FUNCTIONALITY
2.3 USABILITY
2.4 PERFORMANCE
2.5 RELIABILITY
2.6 ASSUMPTION AND DEPENDENCIES
1.0 INTRODUCTION

1.1 PURPOSE

The customer should purchase an item from the shop by using credit card
payment then the vendor should give response to the customers view while a
purchasing item from the shop and required processing of transaction should be
done by the vendor by using a credit card reader.

In the specification use define about the system requirements that are part
from the functionality of the system. It tells the usability, reliability defined in
the use case specification.

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

1.3 REFERENCES
IEEE Software Requirement Specification format.

1.4 TECHNOLOGY TO BE USED

Microsoft Netbeans 8.2 6.0

1.5 TOOLS TO BE USED

Argo UML software, MySql tool (for developing UML Patterns)

2.0 OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The CCP acts as an interface between the 'Customer' and the 'Card Reader'.
This system tries to make the transaction as simple as possible and at the same time
not risking the security of data transaction process. This minimizes the time
duration in which the user receives the item.

2.2 FUNCTIONALITY

Many members of the process lives to checking for the occurrence and
transaction we all have to carry over sometimes user interface to make the
transaction to be efficient.

2.3 USABILITY
The User interface makes the Credit Card Processing System to be
efficient.
 2.4 PERFORMANCE

It is of the capacities about which it can perform function for many users at the same times efficiently that are
without any error occurrence

2.5 RELIABILITY
The system should be able to process the user for their corresponding
request.

2.6 ASSUMPTION AND DEPENDENCIES

The Vendor and Customer must have basic knowledge of computers and
English Language. The vendor may be required to delivered the item purchased
by the customer.
3.0 MODULE DESCRIPTION
3.1 LOGIN
Brief Description
The use case describes how a User logs into the ATM System
Basic Flow
This use case starts when the actor wishes to Login to the ATM
System.
 The System requests that the actor enter his/her name and
password
 The actor enters his/her name and password
 The System validates the entered name and password and logs the
actor into the System

Alternative Flows
 Invalid Name/Password

If, in the Basic flow, the actor enters an invalid name and/or
password, the system displays an error message. The actor choose to
either return to the beginning of the Basic flow or cancel the login, at
which point the use case ends.
 Special Requirements None

Pre-
Condi
tio ns
None
Post-
Condi
tio ns
If the use case was successful, the actor is now logged into the
system. If not, the system State is unchanged.
Extension Points
 None
3.2 FLOW OF EVENTS
Basic Flow
 The Actor enters into the system by entering Credit card no followed by
Pin Number. The System validates and gives access to the system if
credit card no and pin number is valid

 The System shows the customer about the amount left in his account
and queries the customer the amount he/she needed.

 The Customer enters the amount and waits for money.

 The System checks for the minimum balance and returns the money.

Alternative Flow
If Customer wants to take amount more than minimum amount
left in his Account error message will be displayed.

Post-Condition
If the use case was successful, the customer will receive the
amount
UML DIAGRAMS

The following UML diagrams describe the process involved in the Credit Card
Management System
 Use case diagram
 Class diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
 Package diagram
USE CASE DIAGRAM
 Draw and drop the actors and use case from browser window into the
diagram window.
 Associate the use cases and actors.
 purchase

shop keeper
scatrching the card

enter the pin

user

validate

ATM machine
receipt

enter the amount

CLASS DIAGRAM

SEQUENCE DIAGRAM
 Create a new package from the database and name it as a sequence
diagram.
 From the toolbar, select the required tools and make corresponding
connections.
scatrching the card( )

validate( )

enter the amount( )

recepit( )

sign( )

insert the card( )

enter the pin( )

validate( )

collect and update( )

update( )

recepit( )

remove the card( )

ACTIVITY DIAGRAM

COMPONENT DIAGRAM
User Shop Machine
keeper

Admin
DEPLOYMENT DIAGRAM

User Shop Machine

keeper

Admin

CODING
Dim db As New ADODB.Connection
Dim rs As New ADODB.Recordset Dim
db1 As New ADODB.Connection Dim
rs1 As New ADODB.Recordset Dim db2
As New ADODB.Connection Dim rs2 As
New ADODB.Recordset Dim a As
Integer

Private Sub Command1_Click()

db1.Execute "select *from
credit456" rs1.MoveFirst Do
While Not rs.EOF
If Text1.Text = rs1.Fields(0)
Then a = rs1.Fields(2) End If
Loop
If Text3.Text < Text4.Text Then
db2.Execute "insert into credit789 values('" & Text1.Text & "','" & Text4.Text & "'-'"
& Text3.Text & "')"
MsgBox "transacation successful"
db1.Execute "update credit456 set LIMIT='" & Text4.Text & "' - '" & Text3.Text & "'
where cc='" & Text1.Text & "'"
db1.Execute "update credit456 set CBAL='" & Text3.Text & "' + '" & a & "' where
cc='"
& Text1.Text & "'"
ElseIf Text3.Text > rs1.Fields(1) Then
MsgBox "transaction failed"
End If
End Sub

Private Sub Command2_Click()

Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub

Private Sub Command3_Click()

DataReport1.Show
End Sub

Private Sub Command4_Click()

DataReport2.Show
End Sub

Private Sub Command5_Click()

db.Execute "select * from credit123"
rs.MoveFirst Do
While Not
rs.EOF
If Text1.Text = rs.Fields(0) And Text2.Text = rs.Fields(1) Then
MsgBox "correct pin number"
End If
rs.MoveNext
Loop
db1.Execute "select *from
credit456" rs1.MoveFirst Do While
Not rs1.EOF
If Text1.Text = rs1.Fields(0) Then
Text4.Text = rs1.Fields(1)
End If
rs1.MoveNext
Loop
End Sub

Private Sub Form_Load()

db.Open "Provider=MSDAORA.1;User ID=scott;password=tiger;Data
Source=orcl8i;Persist Security Info=False"
db1.Open "Provider=MSDAORA.1;User
ID=scott;password=tiger;Data Source=orcl8i;Persist Security
Info=False" rs.Open "select * from credit123", db, adOpenDynamic
rs1.Open "select * from credit456", db1, adOpenDynamic
db2.Open "Provider=MSDAORA.1;User ID=scott;password=tiger;Data
Source=orcl8i;Persist Security Info=False"
rs2.Open "select * from credit789", db2,
adOpenDynamic a = rs1.Fields(2)
End Sub

SNAPSHOTS

PURCHASE DETAILS
TRANSACTION DETAILS

PURCHASE DETAILS
 CONCLUSION

Thus the CREDIT CARD PROCESSING SYSTEM for the Bank application is
developed successfully which will validate the customer account information and their
credit card limit to purchase any product.In this project we also generate the transaction
report of the customer using Data Environment tool.Using thiscredit card monthly
statement is also generated.

EX.NO:10 E-BOOK MANAGEMENT SYSTEM

AIM
To develop a project E-Book Management system using Argo UML
software, MySql Software and to implement the software in Netbeans 8.2 6.0.

PROBLEM STATEMENT
 This E-BOOK should contain index of the topics. When the main page is visited
index of the topics is displayed. Select the required topic and double click on it. Then
the page with the contents of the selected topic will be displayed. A certain option is
also present in that page to go back to main page and search for other topics.

OVERALL DESCRIPTION
• Create a main page.
• Main page contains index of certain topics.
• When a particular topic is required double click on it.
• It displays a page with the contents of that topic.
• A separate option is present to go back to main page.
SOFTWARE REQUIREMENT SYSTEM

S.No Contents
1.0 INTRODUCTION
1.1 OBJECTIVE
1.2 OVERVIEW
1.3 GLOSSARY
1.4 PURPOSE
1.5 SCOPE
1.6 FUNCTIONALITY
1.7 USABILITY
1.8 PERFORMANCE
1.9 RELIABILITY
2.0 FUNCTIONAL REQUIREMENTS

1. 0 INTRODUCTION
E-book management gives an idea about how e-books are maintained in the
particular concern. The e-books that are to be purchased, the e-books that are to be sold
are maintained here. Further some additional details of the current e-book list that is
available in the website is also given. E-book management in this project is done in an
authorized way.

1.1 OBJECTIVE
The main objective of this project is to overcome the work load and time
consumption which makes the maintenance of the e-book in an organization as a tedious
process. This project provides complete information about the details of the e-book to
the customers. This project identifies the amount of book available, Separate modules
have been created for purchasing, viewing book details, and delivery details
1.2 OVERVIEW
The overview of the project is to Storing of information about the e- books and
updating the e-book list for each organization which is using this system, keeps track of
all the information about the e-books purchased that are made by the customers, having
registration feature of adding up new customers to the organization are provided in this
system.
1.3 GLOSSARY
TERMS DESCRIPTION
CUSTOMER Customer will purchase the books from the Website
DATABASE Database is used to store the books and details of books.
ADMIN Handles all the support features and the technical works
in the application.
SOFTWARE This software specification documents full set of features
REQUIREMENT and function for e-book management system that is
SPECIFICATION performed in application.

1.1 PURPOSE
The purpose of e-book management system is to store and sell the books in a
website effectively.

1.2 SCOPE
The scope of this e-book management is to maintain the book details after the
purchase and list of reaming books available in the same book type.

1.3 FUNCTIONALITY
The main functionality of e-book maintenance system is to store and sell e-
books for a website.

1.4 USABILITY
User interface makes the e-book management system to be efficient. That is the
system will help the admin to maintain stock details easily and helps the store to handle
the stocks effectively. The system should be user friendly.

1.5 PERFORMANCE
It describes the capability of the system to perform the e-book
management system of the store without any error and performing it
efficiently.
1.6 RELIABILITY
The e-book management system should be able to serve the customer with
correct information and day-to-day update of e-book list details.
2.0 FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system.
That is the services that are provided to the website which maintains e-books in
online database.
UML DIAGRAMS

The following UML diagrams describe the process involved in the E- Book
Management System

• Use case diagram

• Class diagram
• Sequence diagram
• Collaboration diagram
• State chart diagram
• Activity diagram
• Component diagram
• Deployment diagram
• Package diagram

USE-CASE DIAGRAM
DESCRIPTION
Use case diagrams describe what a system does from the stand point of an external
observer. The emphasis is an;

“What a system does rather than how it does” Use case diagram
are helpful in 3 cases:
• Use case often generates new requirement as the system is analyzed and
the system is analyzed and the design takes shape.
• Communication with clients.
• Generating test cases.

CLASS DIAGRAM
ACTIVITY DIAGRAM
DESCRIPTION
• Activity diagram focus on the flow of activity involved in the single
process.
• Activity diagram shows how the activities depend on the another.
• It is essentially a FANCY diagram.

SEQUENCE DIAGRAM
 DESCRIPTION
Sequence diagram is an interaction diagram which is dynamic. Sequence
diagram gives information such as:
• How operations are carried out.
• What messages are sent?
• When sequence diagrams are organized according to time.
COMPONENT DIAGRAM
Book
dbs

User Admin

DEPLOYMENT DIAGRAM
 Book dbs

User Admin

DESCRIPTION
• Deployment diagram is also called as component diagram.

• The component is code module.

• Component diagram are physical analog of class diagram.

• It shows the physical configuration of hardware and software.

CODING:
FORM 1:
Private Sub Command1_Click()
Form3.Show
End Sub
Private Sub Command2_Click()
Form2.Show
End Sub

FORM 2:
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub Command1_Click()
con.Execute "select * from members"
rs.MoveFirst Do
While Not rs.EOF
If rs.Fields(0) = Text1.Text And rs.Fields(1) = Text2.Text Then
Form6.Show
Form2.Hid e
End If
rs.MoveNex
t Loop
End Sub
Private Sub ee_Click()
Form1.Show
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True"
rs.Open "select * from members", con, adOpenDynamic End
Sub

FORM 3:
Dim con As New ADODB.Connection
Dim rs As New Recordset
Private Sub
Command1_Click()
con.Execute "select * from
eb1" rs.MoveFirst Do
While Not rs.EOF
If (rs.Fields(0) = Text1.Text()) Then
Text1.Text = rs.Fields(0) Text2.Text
= rs.Fields(1)
Text3.Text = rs.Fields(2)
Text4.Text = rs.Fields(3) MsgBox
"search scccecfully"
End If
rs.MoveNext
Loop
End Sub
Private Sub Command2_Click()
Form4.Show
End Sub
Private Sub Command3_Click()
Form3.Hide
End Sub
Private Sub Command4_Click()
Form5.Show
End Sub
Private Sub Command5_Click()
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
End Sub

Private Sub Form_Load()

con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select * from eb1", con, adOpenDynamic
End Sub

FORM 4:
Private Sub Command2_Click()
Form5.Show
End Sub
Private Sub Command3_Click()
Form3.Show
End Sub
Private Sub Form_Load()
WebBrowser1.Navigate2 ("Z:\WT LAB\JAVA1.html") End
Sub

FORM 5:
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset Dim
con1 As New ADODB.Connection Dim
rs1 As New ADODB.Recordset Private
Sub c_Click()
Text3.Text = " "
End Sub
Private Sub Command1_Click()
If (Text3.Text = rs1.Fields(0)) Then MsgBox
"the book has been downloaded " Else
MsgBox "credit no wrong"
End If
End Sub
Private Sub Command2_Click()
Form3.Show
End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True"
rs.Open "select * from eb1", con, adOpenDynamic con1.Open
"Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=orcl8i;Persist Security Info=True" rs1.Open "select *
from ct", con, adOpenDynamic Text1.Text = rs.Fields(0)
Text2.Text = rs.Fields(3) End
Sub
FROM 6:
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub Command1_Click()
con.Execute "insert into eb1 values('" & Text1.Text & "','" & Text2.Text & "','" &
Text3.Text & "','" & Text4.Text & "')"
con.Execute "commit"
MsgBox "insert
sucessfully"
MsgBox "updated"
End Sub
Private Sub Command2_Click()
con.Execute "delete from eb1 where bid=" & Text3.Text & " "
MsgBox "successfully deleted"
End Sub
Private Sub Command3_Click()
Form2.Show
 End Sub
Private Sub Form_Load()
con.Open "Provider=MSDAORA.1;Password=tiger;User
ID=scott;Data Source=orcl8i;Persist Security Info=True" rs.Open
"select * from eb1", con, adOpenDynamic End Sub

SNAPSHOTS
HOME PAGE

BOOK DETAILS
BOOK DESCRIPTION

ADMINISTRATION LOGIN
DETAILS FORM
 CONCLUSION
After we have completed the project we are sure the problems in the existing system
would overcome. The “E-BOOK MANAGEMENT SYSTEM” process made computerized to
reduce human errors and to increase the efficiency. The maintenance of the record is made
efficient as all the records are stored in the ORACLE database . Our aim of the project is to
get the product details clearly and calculate the total amount. The problems in the earlier
system have bee n removed to a large extent. And it is expected that this project will go a
long way in satisfying user requirements.