LabManual Final 2

Ex No: 1
Date:
PRACTICING THE DIFFERENT TYPES OF CASE TOOLS SUCH AS

(RATIONAL ROSE & OTHER OPEN SOURCE) USED FOR ALL THE
PHASES OF SOFTWARE DEVELOPMENT LIFE CYCLE.
AIM:
To Practice the different types of case tools such as used for all the phases of software
development life cycle.
INTRODUCTION:
CASE tools known as Computer-Aided Software Engineering tools is a kind of
component-based development which allows its users to rapidly develop information systems.
The main goal of case technology is the automation of the entire information systems
development life cycle process using a set of integrated software tools, such as modeling,
methodology and automatic code generation. Component based manufacturing has several
advantages over custom development. The main advantages are the availability of high quality,
defect free products at low cost and at a faster time. The prefabricated components are
customized as per the requirements of the customers. The components used are pre-built, readytested and add value and differentiation by rapid customization to the targeted customers.
However the products we get from case tools are only a skeleton of the final product required
and a lot of programming must be done by hand to get a fully finished, good product.
Characteristics of CASE:
Some of the characteristics of case tools that make it better than customized development
are;
It is a graphic oriented tool.
It supports decomposition of process.
Some typical CASE tools are:
Unified Modeling Language
Data modeling tools, and
Source code generation tools
Introduction to UML
The UML is a language for specifying, constructing, visualizing, and documenting the
software system and its components. The UML is a graphical language with sets of rules and
semantics. The rules and semantics of a model are expressed in English in a form known as OCL
(Object Constraint Language). OCL uses simple logic for specifying the properties of a system.
The UML is not intended to be a visual programming language. However it has a much closer
mapping to object-oriented programming languages, so that the best of both can be obtained. The
UML is much simpler than other methods preceding it. UML is appropriate for modeling
systems, ranging from enterprise information system to distributed web based application and
even to real time embedded system. It is a very expensive language addressing all views needed
to develop and then to display system even though understand to use. Learning to apply UML
effectively starts forming a conceptual mode of languages which requires learning.
Three major language elements:
UML basic building blocks
Rules that dictate how this building blocks put together
Some common mechanism that apply throughout the language
The primary goals in the design of UML are:
Provides users ready to use, expressive visual modeling language as well

so they can develop and exchange meaningful models.
\Provide extensibility and specialization mechanisms to extend the core

concepts.
Be independent of particular programming languages and development

processes.
Provide formal basis for understanding the modeling language.
Encourage the growth of the OO tools market.
Support higher-level development concepts.
Integrate best practices and methodologies.
Every complex system is best approached through a small set of nearly independent
views of a model. Every model can be expressed at different levels of fidelity. The best models
are connected to reality.
The UML defines nine graphical diagrams:
Class diagram
Use-case diagram
Behavior diagram
4.
Interaction diagram
sequence diagram
collaboration diagram
state chart diagram
activity diagram
Implementation diagram
component diagram
deployment diagram
Use Case Diagram

The behavior of the system under development (i.e. what functionality must be provided by the
system) is documented in a use case model that illustrates the system's intended functions (use
cases), its surroundings (actors), and relationships between the use cases and actors (use case
diagrams).
Actors
Are NOT part of the system they represent anyone or anything that must interact with
the system.
Only input information to the system.
Only receive information from the system.

Both input to and receive information from the system.
Represented in UML as a stickman.
Use Case
A sequence of transactions performed by a system that yields a
measurable result of values for a particular actor
A use case typically represents a major piece of functionality
that is complete from beginning to end. A use case must
deliver something of value to an actor.
Use Case Relationships
Between actor and use case.

Association / Communication.
Arrow can be in either or both directions; arrow indicates who initiates
communication.
Between use cases (generalization):
Uses
Where multiple use cases share pieces of same functionality.
Extends
Optional behavior.
Behavior only runs under certain conditions (such as alarm).
Several different flows run based on the users selection
Documenting Flow of events

Background
Each use case is documented with a flow of events. The flow of events for a use case is a
description of the events needed to accomplish the required behavior of the use case. Activity
diagrams may also be created at this stage in the life cycle. These diagrams represent the
dynamics of the system. They are flow charts that are used to show the workflow of a system;
that is, they show the flow of control from one activity to another in the system,
Flow of Events
A description of events required to accomplish the behavior of the use case, that:
Show WHAT the system should do, not HOW the system does it.
Written in the language of the domain, not in terms of implementation.
Written from an actor point of view.
A flow of events document is created for each use case:
Actors are examined to determine how they interact with the system.
Break down into the most atomic actions possible.
Contents of Flow of Events
When and how the use case starts and ends.

What interaction the use case has with the actors.
What data is needed by the use case.
The normal sequence of events for the use case.
The description of any alternate or exceptional flows.
Template for the flow of events document

Each project should use a standard template for the creation of the flow of events document. The
following template seems to be useful.
X Flow of events for the <name> use case
X.1 Preconditions
X.2 Main flow
X.3 Sub-flows (if applicable)
X.4 Alternative flows
where X is a number from 1 to the number of use cases.
Activity Diagram
Activity diagrams are flow charts that are used to show the workflow of a system. They also:
Represent the dynamics of the system.
Show the flow of control from activity to activity in the system.
Show what activities can be done in parallel, and any alternate paths through the flow.
Activity diagrams may be created to represent the flow across use cases or they may be created
to represent the flow within a particular use case. Later in the life cycle, activity diagrams may
be created to show the workflow for an operation.
Activity Diagram Notation
Activities- performance of some behavior in the workflow.

Transition- passing the flow of control from activity to activity.
Decision- show where the flow of control branches based on a decision point:
Guard condition is used to determine which path from the decision point is taken.
Synchronization-what activities are done concurrently? What activities must be
completed before processing may continue (join).
Class Diagram
Background
Classes: a description of a group of objects with common properties (attributes), common

behavior (operations), common relationships to other objects and common semantics.
Object-Oriented Concepts
Attribute: the basic data of the class.

Method (operation): an executable procedure that is encapsulated in a class and is
designed to operate on one or more data attributes that are defined as part of the class.
Object: when specific values are assigned to all the resources defined in a class, the result
is an instance of that class. Any instance of any class is called an object.
Specifying Classes
Each class is given a name, and then you need to specify:
Attributes: initially those that capture interesting object states. Attributes can be public,
protected, private or friendly/package.
Operations: can be delayed till later analysis stages or even till design. Operations also
can be public, protected, private or friendly/package.
Object-Relationships:
Associations: denote relationships between classes.
An aggregation: a special case of association denoting a consists of hierarchy.
Composition: a strong form of aggregation where components cannot exist without
the aggregate.
Generalization relationships: denote inheritance between classes.
This will build the class diagram, which is a graphical representation of the classes (including
their attributes and operations) and their relationship with other classes.
Discovering Classes
Discovering and defining classes to describe the structure of a computerized system is not an
easy task. When the problem domain is new or unfamiliar to the software developers it can be
difficult to discover classes; a cookbook for finding classes does not exist.
Classes Categories
Classes are divided into three categories:

Entity: models information and associated behavior that is long-lived, independent of the
surrounding, application independent, and accomplishes some responsibility
Boundary: handles the communication between the system surroundings and the inside of the
system, provides interface, and facilitates communication with other systems
Control: model sequencing behavior specific to one or more use cases. Control classes
coordinate the events needed to realize the behavior specified in the use case, and they are
responsible for the flow of events in the use case.
Discovering Classes Approaches
Methods of discovering classes:
Noun Phrase Approach: Examine the requirements and underline each noun. Each noun
is a candidate class; divide the list of candidate classes into:
Relevant classes: part of the application domain; occur frequently in requirements.

Irrelevant classes: outside of application domain
Fuzzy classes: unable to be declared relevant with confidence; require additional
analysis
Common Class Patterns: Derives candidate classes from the classification theory of
objects; candidate classes and objects come from one of the following sources:
Tangible things: e.g. buildings, cars.

Roles: e.g. teachers, students.
Events: things that happen at a given date and time, or as steps in an ordered
sequence: e.g. landing, request, interrupt.
Interactions: e.g. meeting, discussion.
Sources, facilities: e.g. departments.
Other systems: external systems with which the application interacts.
Concept class: a notion shared by a large community.
Organization class: a collection or group within the domain.
People class: roles people can play.
Places class: a physical location relevant to the system.
Use Case Driven Method: The scenarios - use cases that are fundamental to the system
operation are enumerated. Going over each scenario leads to the identification of the
objects, the responsibilities of each object, and how these objects collaborate with other
objects.
CRC (Class-Responsibility-Collaboration): Used primarily as a brainstorming tool for
analysis and design. CRC identifies classes by analyzing how objects collaborate to
perform business functions (use cases).
A CRC card contains: name of the class, responsibilities of the class and collaborators of
the class. Record name of class at the top; record responsibilities down the left-hand side;
record other classes (collaborators) that may be required to fulfill each responsibility on
the right-hand side.
CRC cards are effective at analyzing scenarios; they force you to be concise and clear;
they are cheap, portable and readily available.
Mixed Approach: A mix of these approaches can be used, one possible scenario is:
Use CRC for brainstorming.

Identify the initial classes by domain knowledge.
Use common class patterns approach to guide the identification of the classes.
Use noun phrase approach to add more classes.
Use the use case approach to verify the identified classes.
Class Elicitation Guidelines
A class should have a single major role.

A class should have defined responsibilities (use CRC cards if needed).
Classes should be of a manageable size: if a class has too many attributes or
operations, consider splitting it.
A class should have a well-defined behavior, preferably by implementing a given
requirement or an interface.
Interaction diagrams:
Sequence diagrams
Collaboration diagrams
Background
Interaction diagrams describe how groups of objects collaborate in some behavior. An interaction
diagram typically captures the behavior of a single use case.
Interaction diagrams do not capture the complete behavior, only typical scenarios.
Analyzing a Systems Behavior
UML offers two diagrams to model the dynamics of the system: sequence and collaboration
diagrams. These diagrams show the interactions between objects.
Sequence Diagrams
Sequence diagrams are a graphical way to illustrate a scenario:
They are called sequence diagrams because they show the sequence of message passing
between objects.
Another big advantage of these diagrams is that they show when the objects are created
and when they are destructed. They also show whether messages are synchronous or
asynchronous
Creating Sequence Diagrams
You must know the scenario you want to model before diagramming sequence diagrams.
After that specify the classes involved in that scenario.
List the involved objects in the scenario horizontally on the top of the page.
Drop a dotted line beneath every object. They are called lifelines.
The scenario should start by a message pass from the first object.
You must know how to place the objects so that the sequence is clear.
You may start the scenario by an actor.
Timing is represented vertically downward.
Arrows between life lines represents message passing.
Horizontal arrows may pass through the lifeline of another object, but must stop at some
other object.
You may add constraints to these horizontal arrows.
Objects may send messages to themselves.
Long, narrow rectangles can be placed over the lifeline of objects to show when the
object is active. These rectangles are called activation lines.
Collaboration Diagrams
They are the same as sequence diagrams but without a time axis:
Their message arrows are numbered to show the sequence of message sending.
They are less complex and less descriptive than sequence diagrams.
These diagrams are very useful during design because you can figure out how objects
communicate with each other.
Notes
Always keep your diagrams simple.

For IF... then ... else scenarios, you may draw separate sequence diagrams for the
different branches of the if statement. You may even hide them, (at least during the
analysis phase) and document them by the text description accompanying the sequence
diagrams.
Toggling between the sequence and collaboration diagrams

When we work in either a sequence or collaboration diagram, it is possible to view the
corresponding diagram by pressing F5 key.
State Diagrams
State diagrams show how one specific object changes state as it receives and processes
messages:
Since they are very specific, they are used for analyzing very specific situations if we
compare them with other diagrams.
A state refers to the set of values that describe an object at a specific moment in time.
As messages are received, the operations associated with the objects parent class are
invoked to deal with the messages.
These messages change the values of these attributes.
There is no need to prepare a state diagram for every class you have in the system.
Creating State Transition Diagrams
States are represented by rectangles with rounded corners with an attribute name with a
values associated with it.
The name of the state is placed within the box.
Events are shown by arrows.
An event occurs when at an instant in time when a value is changed.
A message is data passed from one object to another.
The name of a state usually refers to the name of the attribute and the values associated to
it.
Example, a student object may receive a message to change its name. The state of that
object changes from the first name state to the new state name.
The name of the state is placed in the top compartment.
State variables are placed in the next compartment.
The operations associated with the state are listed in the lowest compartment of the state
box.
In the operations part, we usually use one of the following reserved words:
Entry: a specific action performed on the entry to the state.
Do: an ongoing action performed while in the state.
On: a specific action performed while in the state.
Exit: a specific action performed on exiting the state.
There are two special states added to the state transition diagram- start state and end state.
Notation of start state is a solid black circle and for the end state a bulls eye is used.
State Transition Details
A state transition may have an action and/or guard condition associated with it and it may
also trigger an event.
An action is the behavior that occurs when the state transition occurs.
An event is a message that is sent to another object in the system.
A guard condition is a Boolean expression of attribute values that allows a state transition
only if the condition is true.
Both actions and guards are behaviors of the object and typically become operations.
Also they are usually private operations (used by the object itself)
Actions that accompany all state transitions into a state may be placed as an entry action
within the state.
Actions that accompany all state transitions out of a state may be placed as exit actions
within the state
A behavior that occurs within the state is called an activity.
An activity starts when the state is entered and either completes or is interrupted by an
outgoing state transition.
A behavior may be an action, or it may be an event sent to another object.
This behavior is mapped to operations on the object.
State transition diagram notation:
UML Implementation Diagrams

The main implementation diagrams we have in UML are: component diagrams and
deployment diagrams.
UML Component Diagram

Component diagrams capture the physical structure of the implementation.
Remember always that when you talk about components, you are talking about the
physical models of code.
You can name them and show dependency between different components using arrows.
A component diagram shows relationships between component packages and
components.
Each component diagram provides a physical view of the current model.
Component diagrams contain icons representing:
Component packages.
Components.
Main programs.
Packages.
Subprograms.
Tasks.
Dependencies.
Deployment Diagram
A deployment diagram shows processors, devices and connections. Each model contains a single
deployment diagram which shows the connections between its processors and devices, and the
allocation of its processes to processors.
Deployment Diagrams: Processor
A processor is a hardware component capable of executing programs.
A processor is given a name and you should specify the processes that will run on that
processor.
You can also specify the scheduling of these processes on that processor.
Types of scheduling are:
Pre-emptive: a higher priority process may take the process from lower priority
one.
Non-preemptive: a process will own the processor until it finishes
Cyclic: control passes from one process to another.
Executive: an algorithm controls the scheduling of the processes
Manual: scheduling buy the user.
Deployment Diagrams: Device
A device is a hardware component with no computing power. Each device must have a name.
Device names can be generic, such as modem or terminal.
Deployment diagrams: Connection
A connection represents some type of hardware coupling between two entities. An entity is either
a processor or a device. The hardware coupling can be direct, such as an RS232 cable, or
indirect, such as satellite-to-ground communication. Connections are usually bi-directional.
ATM SYSTEM
Problem statement:
This system is build for the bank client and the manager.
The bank client must be able to deposit and withdraw amount from his/her
accounts using the ATM machine. Each transaction must be recorded and the
client must be able to review all transactions performed in his/her account.
Recorded transactions must include the date, time, transaction type, amount and
account balance after the transaction.
The bank manager must be able to view the ATM machine status that is the total
balance of the ATM machine, todays withdrawal, todays balance and the
limitations of the machine.
The bank client is provided by login verification. If it is valid he/she will access
their account otherwise an appropriate message is displayed to the client.
Software requirements:
Microsoft visual basic 6.0 is used as front-end for our project and ms-access is used as
back-end to store the data.
USE-CASE diagram:
The ATM transaction use cases in our system are:
Login
Withdraw
Mini statement
ATM machine status
Deposit
Actors involved:
User
Bank manager
USE-CASE name: Login
The user enters a user name and password. If it is valid, the users account becomes
available. If it is invalid, an appropriate message is displayed to the user.
USE-CASE name: Withdraw
The user tries to withdraw an amount from his or her checking account. The amount is
less than or equal to the checking accounts balance, the transaction is performed and the
available information is displayed. The system creates a record of the transaction and the display
confirmation message is displayed to the client.
USE-CASE name: Mini statement

The bank user requests a history of transactions for a checking account. The system
displays the transaction history for the checking account. The transaction history consists of
amount, date, transaction type and balance of the particular account.
USE-CASE name: ATM machine status
The bank manager enters a username and password. If it is valid, the bank manager
accesses the machine status. If it is invalid, an appropriate message is displayed to the user.
USE-CASE name: Deposit
The bank user requests the system to deposit money to an account. The user accesses the
account for which a deposit is going to be made and enters the amount. The system creates a
record of the transaction and an appropriate confirmation message (display confirmation) is
displayed to the client. The transaction must include the date, type, amount and account balance
after the transaction.
Use-case diagram for ATM system
Class diagram
The class diagram, also referred to as object modeling is the main static analysis diagram.
The main task of object modeling is to graphically show what each object will do in the problem
domain. The problem domain describes the structure and the relationships among objects.
The ATM system class diagram consists of four classes:
User class
ATM machine status
Account
Transaction
1) User class:
It consists of four attributes and two operations. The attributes are user name, password,
address and DOB. The operations of this class are read (), display () and write ().
2) ATM machine status:
The attributes of this class are ATM balance, todays withdrawal, todays balance, and
limitations. The operations are login verification (), ATM status () and display confirmation ().
3) Account:
The attributes are account no. and balance and the operations are withdraw (), deposit ()
and display availability ().
4) Transaction:
The attributes of this class are account no, transaction type, data, amount, balance and the
operations are mini statement () and create transaction ().
Class diagram for ATM system
Sequence diagram:
A sequence diagram represents the sequence and interactions of a given USE-CASE or
scenario. Sequence diagrams can capture most of the information about the system. Most object
to object interactions and operations are considered events and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external devices.
An event also is considered to be any action by an object that sends information. The
event line represents a message sent from one object to another, in which the form object is
requesting an operation be performed by the to object. The to object performs the operation
using a method that the class contains.
It is also represented by the order in which things occur and how the objects in the system
send message to one another.
The sequence diagram for each USE-CASE that exists when a user withdraws, deposits,
needs information about ATM machine status and account are drowned.
Sequence and collaboration diagram for deposit process
The diagrams show the entire deposit process in an ATM system. The user has to login to
the ATM machine and deposit the amount of money as required by the user. The user may wish
to get a mini statement and a screen about the details of the transaction.
Sequence and collaboration diagram for login
The diagrams show the process of login by the user to the ATM system. The user has to enter his
details. The details entered are verified by the system and the user is approved if the details
match, otherwise an appropriate error message is displayed.
Sequence and collaboration diagram for checking machine status
The Administrator of the ATM system has to maintain the details about the ATM, He has to
check if there is enough money in the ATM and if the ATM is functional without major errors.
For this, he may check the ATM machine status occasionally. The process is shown in the above
diagrams.
Sequence and collaboration diagram for printing mini statement
After a transaction is carried out successfully, the user must get a mini statement to tell him his
accounts details such as balance and transaction number. This process is depicted in the above
diagrams.
Sequence and collaboration diagram for withdraw process
The user can make withdraw money from his account. The process is depicted in the
diagrams above. The user has to login to the system using his username and password, which are
verified by the system. After successful verification, the user can choose the amount of money he
wants to withdraw from his account. The amount specified by the user is checked by the system
to make sure there is enough balance in his account to carry out the transaction. After the
transaction is carried out the resulting amount is displayed and the details are updated to the
database.
RESULT:
Successfully practiced the different types of case tools such as used for all the phases of
software development life cycle.
Ex No: 2
Date:
DATA MODELING
AIM:
To deeper understanding of the Data modeling
INTRODUCTION:
Data modeling in software engineering is the process of creating a data model for an
information system by applying formal data modeling techniques. Data modeling is a process
used to define and analyze data requirements needed to support the business processes within the
scope of corresponding information systems in organizations. Therefore, the process of data
modeling involves professional data modelers working closely with business stakeholders, as
well as potential users of the information system.
DATA MODEL TYPES:
There are three different types of data models produced while progressing from
requirements to the actual database to be used for the information system. The data requirements
are initially recorded as a conceptual data model which is essentially a set of technology
independent specifications about the data and is used to discuss initial requirements with the
business stakeholders. The conceptual model is then translated into a logical data model, which
documents structures of the data that can be implemented in databases. Implementation of one
conceptual data model may require multiple logical data models. The last step in data modeling
is transforming the logical data model to a physical data model that organizes the data into tables,
and accounts for access, performance and storage details. Data modeling defines not just data
elements, but also their structures and the relationships between them.
USES OF DATA MODEL:
Data modeling techniques and methodologies are used to model data in a standard,
consistent, predictable manner in order to manage it as a resource. The use of data modeling
standards is strongly recommended for all projects requiring a standard means of defining and
analyzing data within an organization, e.g., using data modeling:
To assist business analysts, programmers, testers, manual writers, IT package selectors,

engineers, managers, related organizations and clients to understand and use an agreed
semi-formal model the concepts of the organization and how they relate to one another
To manage data as a resource
For the integration of information systems
For designing databases/data warehouses
Data modeling may be performed during various types of projects and in multiple phases of
projects. Data models are progressive; there is no such thing as the final data model for a
business or application. Instead a data model should be considered a living document that will
change in response to a changing business. The data models should ideally be stored in a
repository so that they can be retrieved, expanded, and edited over time. Whitten (2004)
determined two types of data modeling:
Strategic data modeling: This is part of the creation of an information systems strategy,
which defines an overall vision and architecture for information systems is defined.
Information engineering is a methodology that embraces this approach.
Data modeling during systems analysis: In systems analysis logical data models are
created as part of the development of new databases.
Data modeling is also used as a technique for detailing business requirements for specific
databases. It is sometimes called database modeling because a data model is eventually
implemented in a database.
HOW DATA MODELS DELIVER BENEFIT.
Data models provide a structure for data used within information systems by providing
specific definition and format. If a data model is used consistently across systems then
compatibility of data can be achieved. If the same data structures are used to store and access
data then different applications can share data seamlessly. The results of this are indicated in the
diagram. However, systems and interfaces often cost more than they should, to build, operate,
and maintain. They may also constrain the business rather than support it. This may occur when
the quality of the data models implemented in systems and interfaces is poor.
Business rules, specific to how things are done in a particular place, are often fixed in the
structure of a data model. This means that small changes in the way business is conducted
lead to large changes in computer systems and interfaces. So, business rules need to be
implemented in a flexible way that does not result in complicated dependencies, rather
the data model should be flexible enough so that changes in the business can be
implemented within the data model in a relatively quick and efficient way.
Entity types are often not identified, or are identified incorrectly. This can lead to
replication of data, data structure and functionality, together with the attendant costs of
that duplication in development and maintenance. Therefore, data definitions should be
made as explicit and easy to understand as possible to minimize misinterpretation and
duplication.
Data models for different systems are arbitrarily different. The result of this is that
complex interfaces are required between systems that share data. These interfaces can
account for between 25-70% of the cost of current systems. Required interfaces should be
considered inherently while designing a data model, as a data model on its own would not
be usable without interfaces within different systems.
Data cannot be shared electronically with customers and suppliers, because the structure
and meaning of data has not been standardized. To obtain optimal value from an
implemented data model, it is very important to define standards that will ensure that data
models will both meet business needs and be consistent.
CONCEPTUAL, LOGICAL AND PHYSICAL SCHEMAS:
THREE KINDS OF DATA-MODEL INSTANCE:
Conceptual schema: describes the semantics of a domain (the scope of the model). For
example, it may be a model of the interest area of an organization or of an industry. This
consists of entity classes, representing kinds of things of significance in the domain, and
relationships assertions about associations between pairs of entity classes. A conceptual
schema specifies the kinds of facts or propositions that can be expressed using the model.
In that sense, it defines the allowed expressions in an artificial "language" with a scope
that is limited by the scope of the model. Simply described, a conceptual schema is the
first step in organizing the data requirements.
Logical schema: describes the structure of some domain of information. This consists of
descriptions of (for example) tables, columns, object-oriented classes, and XML tags. The
logical schema and conceptual schema are sometimes implemented as one and the same.
Physical schema: describes the physical means used to store data. This is concerned with
partitions, CPUs, table spaces, and the like.
This approach allows the three perspectives to be relatively independent of each other.
Storage technology can change without affecting either the logical or the conceptual schema. The
table/column structure can change without (necessarily) affecting the conceptual schema. In each
case, of course, the structures must remain consistent across all schemas of the same data model.
DATA MODELING PROCESS:

The data modeling process. The figure illustrates the way data models are developed and
used today. A conceptual data model is developed based on the data requirements for the
application that is being developed, perhaps in the context of an activity model. The data model
will normally consist of entity types, attributes, relationships, integrity rules, and the definitions
of those objects. This is then used as the start point for interface or database design.
The process of designing a database involves producing the previously described three
types of schemas - conceptual, logical, and physical. The database design documented in these
schemas are converted through a Data Definition Language, which can then be used to generate a
database. A fully attributed data model contains detailed attributes (descriptions) for every entity
within it. The term "database design" can describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical design
of the base data structures used to store the data. In the relational model these are the tables and
views. In an object database the entities and relationships map directly to object classes and
named relationships. However, the term "database design" could also be used to apply to the
overall process of designing, not just the base data structures, but also the forms and queries used
as part of the overall database application within the Database Management System or DBMS.
In the process, system interfaces account for 25% to 70% of the development and support
costs of current systems. The primary reason for this cost is that these systems do not share a
common data model. If data models are developed on a system by system basis, then not only is
the same analysis repeated in overlapping areas, but further analysis must be performed to create
the interfaces between them. Most systems within an organization contain the same basic data,
redeveloped for a specific purpose. Therefore, an efficiently designed basic data model can
minimize rework with minimal modifications for the purposes of different systems within the
organization.
MODELING METHODOLOGIES:
Data models represent information areas of interest. While there are many ways to create data
models, two modeling methodologies are stand out, top-down and bottom-up:
Bottom-up models are often the result of a reengineering effort. They usually start with
existing data structures forms, fields on application screens, or reports. These models are
usually physical, application-specific, and incomplete from an enterprise perspective.
They may not promote data sharing, especially if they are built without reference to other
parts of the organization.
Top-down logical data models, on the other hand, are created in an abstract way by
getting information from people who know the subject area. A system may not implement
all the entities in a logical model, but the model serves as a reference point or template.
Sometimes models are created in a mixture of the two methods: by considering the data needs
and structure of an application and by consistently referencing a subject-area model.
Unfortunately, in many environments the distinction between a logical data model and a physical
data model is blurred. In addition, some CASE tools dont make a distinction between logical
and physical data models.
Conceptual Data Modeling - used to figure out how major electronic and communication
systems are connected together
Enterprise Data Modeling - contains many of the same aspects of conceptual data modeling,
but streamlined for unique capabilities of an individual organization.
Logical Data Modeling - has two main functions, to serve as the building block for physical
data modeling, and to document certain identified relationships in a business function
Physical Data Modeling serves as a direct representation of the implementation plan of a

logical data model
RESULT:
Successfully understand the concepts of Data Modeling.
Ex No: 3
Date:
SOURCE CODE GENERATORS
AIM:
To practice and understanding the concepts of source code generation using Rational
Rose Software.
Rational Rose:
Rational Rose is the design tool of choice for Java programmers. It provides many features, most
interesting for us is its ability to provide design, modeling and visualization of java constructs
including packages, classes, fields, interfaces, imports, inheritance, fields, methods and
modifiers.
Forward engineering is the process of generating Java source from one or more classes,
packages, or components in a Rational Rose model.
Some Rational Rose Terms:

Components: A component represents a software module (source code, binary code,
executable, DLL, etc) with a well-defined interface. A system may be composed of several
software modules of different kinds. Each software module is represented by a component in the
model. Typically, a component name is the name of a file that the component represents.
In terms of Java, a .java file represents a component in a Rational Rose model. A .java file may
have only one class or several classes.
Frameworks: A framework in Rational Rose is a set of predefined model elements that are
needed to model a certain kind of system. The purpose of a specific framework can be to define
the architecture of systems of a certain kind or to provide a set of reusable components.
Frameworks are used as templates when creating a new model.
Working with Rational Rose:

Start Rational Rose. Click on File > New to start a new Model.
Setting a Models Language:

In a new model, click on model properties in the model browser as shown below. In the dialog
box shown on the right below, select the default language as Java in the notation tab.
Setting the Classpath:

Before attempting an example of Forward Engineering a .java class, click on Tools > Java >
Project Specification and make sure the class path is correct. Rational Rose retrieves the class
path from the Systems class path variable. Additional directories where you may have your
own .java files may be added in the dialog box as shown below:
Depending upon which version of JDK you are using you may give a classpath to src.jar, src.zip
or other appropriate library file.
Creating a class
In the logical view of your new model create a class called Point.
2. Right click the class Point and click New Attribute. Name the attribute itsX and itsY.
3. Right click again, click New Operation. Name the new operation getX(), and getY().
4. Your model should now look as follows:
5. In the browser window, click on Logical View and then expand on Point.
5. Double click itsX and set its type to int and also set its various modifiers [private, etc.], also for itsY.
6. Similarly, double-click getX() and getY() in the browser and set its various attributes {return type,
etc.}
7. In the browser, left-click the Component View to create a new component called Point.
8. In the browser, drag the Point class to the Point component to assign the class to the Component.
9. Check the browser to make sure the class now has the component name next to it in parenthesis.
10. The browser should now look as follows:
11. In the browser or in the diagram, right-click the Point class, click Java > Generate Java.
12. Since this is the first time youve generated code for this model, Rational Rose displays a mapping
dialog prompting you to map the file it will generate to a directory in your class path. Click on the class
path name to select it, click on the component name to select it, then click Map:
13. If code generation is successful, a successful dialog will be seen:

14. Click on Java > Browse Java Source to view the Java source:
15. Complete your code.

16. Save your model as Lab09.mdl file.
Creating an abstract Class:
Use the same technique of creating a class, create an abstract class name Shape.
Double click on the class Shape to open Class specification and change its modifier into abstract.
Add a member itsCenter with the type of Point.

Add a function getCenter() with return type is Point.
Add a function getArea() with return type is double and its modifier is abstract, your model should
look like the following:
Do step 7 16 as describe above, to generate Java file of this model, and save the model.
Creating Relationship between Classes:

Inheritance
Create a new concrete class Circle with radius (double) as a member and getRadius() (returning
double) as its operation. It should be look like :
Generate inheritance relationship between Circle (subclass) and Shape (super class). Click on
generalization icon (see below figure) or select Tool Create Generalization.
While the pointer is displaying up arrow (generalization mode), drag it from Circle class to Shape
abstract class. Your model should look like :
Validate your model by double-clicking the class Circle, then verify that abstract class Shape has been
added in extends fields.
Do step 7 16 as describe above, to generate Java file of this model, and save the model. If it is
successful then the getArea() operation will automatically added to Circle class. As following figure:
Association, Composition, Aggregation, Navigation and Multiplicity:

Association relationships capture the static relationships between entities. These generally relate to one
object having an instance of another as an attribute or being related in the sense of owning (but not being
composed of). For example a Shape has an association to its center point.
Aggregation relationships define whole/part relationships. The weak form of aggregation is denoted with
an open diamond. This relationship denotes that the aggregate class (the class with the white diamond
touching it) is in some way the whole, and the other class in the relationship is somehow part of that
whole.
Composition relationships are a strong form of containment or aggregation. The black diamond
represents composition.
Multiplicity defines how many objects participate in a relationship.
Navigation is the direction of the relationships between the classes.
Suppose that we would like to create the Association relationship between Shape and Point. These are
steps:
Select Association icon (as shown bellow) or select Tool Create Association.
While the pointer is displaying up arrow (Association mode), drag it from Shape class to Point class.
Your model should look like:
Double click on the line between Shape and Point to open Association specification, to update the
properties such as Name, the Roles etc.
To modify type of relationship to Aggregate / Composition, or to add navigations and multiplicity,

select either Role A detail or Role B detail accordingly.
RESULT
Successfully gained more knowledge and understood the source code generation.
STUDENT MARK ANALYSIS SYSTEM
EX.NO: 4
DATE:
ABSTRACT:
The Student Mark Analysis System deals with the complete academic details of
the students .It comprises of the Roll No, Name, Mark, Total and average. It can be accessed by
the faculty who alone can change or update the marks of the student. It is also the duty of the
faculty to maintain the records, the duty of the administrator is to generate the report cards to the
faculty members. The faculty will calculate the total marks based on the percentage obtained by
the student. The role of the Student of the student is to just to view the marks entered by the
faculty.
SCOPE OF THE PROJECT:
The main scope of the project is to get the student mark and update it whenever
necessary and then to display it for the students and faculties.
REQUIREMENTS:
HARDWARE:
Intel Pentium 4 processor
256 MB RAM
80GB HARDDISK
SOFTWARE:
Visual Studio 2005
Sql Server 2000
DESIGN:
Student details
Mark analysis
USE CASE
CLASS DIAGRAM
SEQUENCIAL DIAGRAM
COLLOBORATION DIAGRAM
CODING:
Form2:
Dim rs As Recordset
Private Sub Command1_Click()
Data1.Recordset.AddNew
Data1.Recordset.Update
MsgBox ("Added")
End Sub
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
End Sub
If Data1.Recordset.EOF <> True Then
If Data1.Recordset.Fields(0) = Text1.Text Then
Text2.Text = Data1.Recordset.Fields(1)
End If
End If
End Sub
End
End Sub
Form4.Show
End Sub
Private Sub Form_Activate()
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
End Sub
Form3:
End If
End If
End Sub
End
End Sub
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "

Text5.Text = " "
Text6.Text = " "
Text7.Text = " "
Text8.Text = " "
End Sub
Private Sub Text7_Click()
Text7.Text = ((Val(Text4.Text) + Val(Text5.Text)) + Val(Text6.Text))
End Sub
Text8.Text = Val(Text7.Text) / 3
End Sub
Login Form:
Student Details:
Student Mark Analysis:
TESTING:
Software Testing
The design of text for software and other engineered products can be challenging as
the initial design of the protect
White Box testing:

White box testing sometimes called glass box testing is a test case design method
that users the control structures of the procedural design to device test cases
Logic errors and incorrect assumptions
Logical path is not likely executed
Typographical errors are random
Black Box testing:

It is also called behavioural testing .The testing enables the software,engineer to
device set of input condition black box testing is not an alternative to whitebox testing
techniques.
Unit testing:
Unit testing forces verification effort on the smaller unit of sofrware design the
software component or module.
Integration Testing:
Integration testing is a systametic technique for constucting the program structure
while at the same time conducting tests to uncover errors associated with interfacing
.Incremental integration is the anthesis of thebig bang approach
Smoke Testing:
Smoke testing is an integration testing approach that is commonly used when
stringk warappedsoftware.Products are being developed.It is designed as a pacing mechanism
for time critical projects.
CONCLUSION:
This software could be installed far more quickly. It is, however, a useful tool which may
help lecturers to update the student marks easily, and it can be extended to include many more
functions.
EX.NO: 5
LIBRARY MANAGEMENT SYSTEM
DATE:
ABSTRACT:
Library management system can be used to view books, issue the books and make return and
renewal process this is the case of the prevailing system, but in this project the student could
view his own syllabus and question papers and can downloaded it as if he could do from his mail
id,Student and faculty can make use of this system to search what could do from his mail
id.Student and faculty can make use of this system to search what book he wants and where it is
placed in the library without searching through the racks.

The scope of this project is to simplify the operation of a library in order to manage their
requirements. Issue and update the books easily managed by two different administrators. The
total system is maintained by main administrator.
REQUIREMENTS:
HARDWARE:
Intel Pentium 4 or later
2GB RAM
80GB HARDDISK
SOFTWARE:
Macromedia Dreamweaver(PHP)
MySQL (phpmyadmin)
Member details
Book details
DIAGRAMS:
USE CASE
CLASS DIAGRAMS
SEQUENCE DIAGRAM
COLLBORATION DIAGRAM
CODING:
Form1:
Private Sub Option1_Click()
Form3.Show
End Sub
Form4.Show
End Sub
Form5.Show
End Sub
Form6.Show
End Sub
Form7.Show
End Sub
Form2:
MsgBox "Record Added"
End Sub
If Text1.Text = Data1.Recordset.Fields(0) Then
End If
End Sub
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
End Sub
MsgBox "Record Updated"
End Sub
Form3:
MsgBox "Record added"
End Sub
End If
End Sub
MsgBox "Record Updated"
End Sub
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
End Sub
End
End Sub
Text6.Text = Val(Text4.Text) - Val(Text5.Text)
End Sub
Form4:
End Sub

End If
End Sub
MsgBox "Record Update"
End Sub
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
End Sub
End
End Sub
'Text1.Text = " "
'Text2.Text = " "
'Text3.Text = " "
'Text4.Text = " "
'Text5.Text = " "
'Text6.Text = " "
End Sub
Form5:
MsgBox "Book Returned"
End If
End Sub
End
End Sub
'Text1.Text = " "
End Sub
Form6:
MsgBox "book Reneval"
End Sub
Form1:
Form2:
Form3:
Form4:
Form5:
Form6:
Form7:
TESTING:
Generate report cards:
This module allows the faculty to generate the report cards that are going to contain
the student academic details.
Software Estimation:
A successful project is one delivered on time,within budget and with the required
quality.A porjcet manager producer estimate of effort,which affect costs and of activity
durations which affect the delivery time.
Cost Estimation:
Project cost can be obtained by multiplexing the estimated effort with the man power
cost per month.
The overhead cost would include the costs of hardware and software required for the
porject and the company overheads for adminstrations,office space.
Software Testing
White Box testing:
Black Box testing:

techniques.
Unit testing:
Smoke Testing:
Software Debugging :
Software debugging is one of the major tasks of programming with advent of
concurrent programming with complexity was added to the already difficut debugging process.
The basic concept inheritance in software debugging as well as list of error related to
concurrency.
CONCLUSION:
From our conclusion we declare that the project is completely based on spell checking and
the error words will be displayed in red color font as well as the count of the errors will be
displayed. We have successfully presented the program progress without any backend support
and connecting with local disk directory has been done.
EX.NO:
TELEPHONE DIRECTORY
DATE:
ABSTRACT:
To develop a project that manages the telephone line numbers under a single platform for
effective searching and viewing the information of the any telephone subscribers that any
customer want to know. A customer can demand any type of information such as telephone
numbers, address, or name of the particular person by specifying any one of the details
mentioned above in the search column or he/she can browse through the list of pages for the
information he wants. He can also know the latest news and call tariffs and new facilities
available for the existing customers.
The yellow page consists of the information of various private agencies and
organizations under single category. This will be very useful for the people who are involved in
the business field and people in the field of commerce.
The search is the function and this connected to the server. The Server searches the value
in the database (Ms access or oracle) and returns the match found. If it doesnt found any match
an error message is given.
The Std&Isd Search is associated with Std and Isd number, which is stored in the server.
The user can specify the number to find the address or the user can give the subscriber name and
get the phone number from the various set information displayed.
The Emergency numbers can also be displays according to the selected options like
Hospitals, ambulance, etc, the address of the nearest available home will also be displayed in an
interactive format.
The call tariff also gives the various options available and customer is allowed to choose
any scheme. The user can make use of the listed facilities. The user can further link to the
www.chennaibsnl.nic.in website for further enquiry details.

The scope of this project is to simplify the operation of a telephone in order to manage their
requirements. Issue and update the calls easily managed by two different administrators. The
total system is maintained by main administrator.
REQUIREMENTS:
HARDWARE:
2GB RAM
80GB HARDDISK
SOFTWARE:
MySQL (phpmyadmin)
DESIGN:
Search by name
Addnew
DIAGRAMS:
USECASE DIAGRAMS
CLASS DIAGRAMS
SEQUENCE DIAGRAM
CODING:
Login Form:
If Trim(Text1.Text = "admin") And Trim(Text2.Text = "sec") Then
Form2.Show
Else
MsgBox "Check UserName and Password"
End If
End Sub
End
End Sub
MainForm:
Form3.Show
End Sub
Form4.Show
End Sub
Form5.Show
End Sub
Form6.Show
End Sub
Form7.Show
End Sub
MsgBox "Record added"
End Sub
End Sub
Text1.Text = " "
Text2.Text = " "
End Sub
End
End Sub
Text1.Text = " "
Text2.Text = " "
End Sub
AddNewEntry:
End Sub
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
End Sub
End
End Sub
Update Entry:
MsgBox "data updated"
End Sub
End
End Sub
Search Standard Code:
If Combo1.Text = Data1.Recordset.Fields(4) Then
Label4.Caption = Data1.Recordset.Fields(1)
End If
End Sub
Search By Name:
End If
Output Form:
Login Form:
Form1:
Form2:
Form3:
Form4:
Form5:
TESTING:

Cost Estimation:
cost per month.
Software Testing
White Box testing:
Black Box testing:

techniques.
Unit testing:

Smoke Testing:
concurrency.
CONCLUSION:
The TELEPHONE DIRECTORY SYSTEM is the greatest improved achieved and
implemented over the manual system using case fields and paper. The computerization of the
system has speeded up the process to a greater extent. The telephone directory system by large
proves to be very reliable. The system has been checked with some dummy values and has been
explored as much as it could be possible.
EX.NO:
TEXT EDITOR
DATE:
ABSTRACT:
The text editor mainly aims at developing an application that helps us in creating and
editing text files. The application is more user friendly and platform independent.
Creating a new file, opening an existing file, saving a file and editing the typed text.

CREATE FILE:
This option allow user to create a new file and perform various functions on that file.
OPEN FILE:
This option allow the user to open an already existing file. We should make sure that the
file is already available in the hard disk of the system being used.
SAVE A FILE:
This is an usual operation which is performed before closing the file.
CLOSE FILE:
This option allow the required file to be closed. The file is saved before closing.
CUT THE TEXT:
Another option that can be enabled only when atleast one file is opened.
COPY THE TEXT:
Very similar to the cut option is the copy option.
PASTE THE TEXT:
This option is enabled only when a cut or copy is already performed.
DOCUMENTATION:
Usecase specification:<CUT THE TEXT>
REQUIREMENTS:
HARDWARE:
2GB RAM
80GB HARDDISK
SOFTWARE:
MySQL (phpmyadmin)
USECASE DIAGRAM
CLASS DIAGRAM
SEQUENCE DIAGRAM
COLLOBORATE DIAGRAM
CODING:
Dim t As String
Dim a As String
Private Sub ffont_Click()
C2.Flags = cdlCFBoth
C2.ShowFont
r1.SelFontName = C2.FontName
r1.SelFontSize = C2.FontSize
End Sub
Private Sub mabout_Click()
MsgBox ("version 1.1")
End Sub
Private Sub mcentre_Click()
r1.SelAlignment = rtfCenter
End Sub
Private Sub mcolor_Click()
C2.ShowColor
r1.SelColor = C2.Color
End Sub
Private Sub mcopy_Click()
a = r1.SelText
End Sub
Private Sub mcut_Click()
r1.SelText = ""
End Sub
Private Sub mdelete_Click()
a = r1.SelText
r1.SelText = ""
End Sub
Private Sub mexit_Click()
End
End Sub
Private Sub mfind_Click()
t = InputBox("find what")
r1.Find t
End Sub
Private Sub mleft_Click()
r1.SelAlignment = rtfLeft
End Sub
Private Sub mnew_Click()
Dim h As String
If r1.Text = "" Then
r1.SetFocus
Else
h = MsgBox("the text in the file has changed, Do you want to save?", vbExclamation +
vbYesNo)
If h = vbYes Then
C2.Filter = "*txt"
C2.ShowSave
r1.SaveFile (C2 > FileName)
If h = vbNo Then
'h = vbNo
r1.Text = ""
r1.SetFocus
End If
End If
End If
r1 = ""
End Sub
Private Sub mopen_Click()
C2.Filter = "*txt"
C2.DefaultExt = "txt"
C2.ShowOpen
r1.SaveFile (C2.FileName)
End Sub
Private Sub mpaste_Click()
r1.SelText = a
End Sub
Private Sub mprint_Click()
C2.ShowPrinter
End Sub
Private Sub mright_Click()
r1.SelAlignment = rtfRight
End Sub
Private Sub msave_Click()
C2.Filter = "*.txt"
C2.ShowSave
End Sub
Private Sub msaveas_Click()
C2.Filter = "*txt"
C2.DefaultExt = "txt"
C2.ShowSave
End Sub
LOGIN FORM
TESTING:
Software Testing
White Box testing:
Black Box testing:

techniques.
Unit testing:
Smoke Testing:
concurrency.
CONCLUSION:
The TEXT EDITOR to perform the cut, copy, paste operations. Then also performing the
font format. The computerization of the system has speeded up the process to a greater extent.
EX.NO:
DICTIONARY
DATE:
ABSTRACT:
The Dictionary projects ongoing, voluntary program that provides information to its
members regarding membership details, new words to update, and the detail specified by the
members. It is intended to provide intensive facilities to its members.
To provide new words and their synonyms and antonyms
To update the database
To maintain the words that are inserted
FUNCTIONALITIES:
The main functionalities in the dictionary are user administrator and maintain database.
After getting the access by the user they will do search of the particular word.
REQUIREMENTS:
HARDWARE:
2GB RAM
80GB HARDDISK
SOFTWARE:
MySQL (phpmyadmin)
DATABASE DESIGN:
ADDNEW
SCANNING:
DIAGRAMS:
USE CASE DIAGRAMS
CLASS DIAGRAMS
SEQUENCE DIAGRAM
COLLOBORATION DIAGRAMS
FORM2: DICTIONARY
Form3.Show
End Sub
Form4.Show
End Sub
Form5.Show
End Sub
End
End Sub
FORM3:ADDNEW

MsgBox ("recordes is added")
End Sub
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
End Sub
Form2.Show
End Sub
FORM4:SEARCH BY WORD
Data1.Recordset.MoveFirst
While Not Data1.Recordset.EOF
End If
Data1.Recordset.MoveNext
Wend
End Sub
Form2.Show
End Sub
FORM5: SCANNING
Data1.Recordset.MoveFirst
While Data1.Recordset.EOF = False
If Data1.Recordset.Fields(0) = List1.Text Then
Text2 = Data1.Recordset.Fields(1)
End If
Data1.Recordset.MoveNext
Wend
End Sub
End
End Sub
LOGIN:
DICTIONARY
ADD NEW
SEARCH BY WORD
SCANNING THE WORD
TESTING:
Software Testing
White Box testing:
Black Box testing:

techniques.
Unit testing:
Smoke Testing:
concurrency.
CONCLUSION:
The CREATING DICTIONARY to perform the search by name, scanning process. The
computerization of the system has speeded up the process to a greater extent.
INVENTORY SYSTEM
EX.NO: 9
DATE:
ABSTRACT:
The main objective of this project is to overcome the work load and time
consumption which makes the maintenance of the stock In an organization as a tedious process.
This project provides complete information about the details of the stock to the users. This
project Identifies the amount of stock available, the product that is purchased faults in the
product ,products that are replaced, products that have been sold and date at which are bought
and sold in a particular concern.Seperate modules have been created for purchasing, viewing
stock details,selling,details and delivery details. As a whole, marketing process can be improved
if stock has been maintained properly.

The Internet and other technologies have opened up innovative new ways to give
and maintain and to communicate and collaborate across boundaries. This application is able to
provide following functionalities. Basic share trading functionalities such as user can busy share,
sell the share, view the company portfolio,etc. and admin can add company, delete company, edit
company information, news information, change the company share price etc,. Modules of a user
these application facilities like share the company share and viewing transaction.
REQUIREMENTS:
HARDWARE:
Intel PENTIUM 4 OR LATER
CPU Speed 1.0 GHZ
2 GB RAM
SOFTWARE:
Visual Studio 2008
SQL Server Management Studio 2005
DATABASE DESIGN
BILL:
PURCHASE
SALES
DIAGRAMS:
USECASE DIAGRAM
CLASS DIAGRAM
SEQUENCE DIAGRAM
CODING:
INVENTORY REPORT FORM
Private Sub command2_Click()

MsgBox ("records are updated")
End Sub
Data1.Recordset.Delete
MsgBox ("records are deleted")
End Sub
End If
End If
End Sub
End
End Sub
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
End Sub
PURCHASE FORM
MsgBox ("RECORDS ARE ADDED")
End Sub
End Sub

Data1.Recordset.Delete
MsgBox ("records are deleted")
End Sub
End If
End If
End Sub
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
End
End Sub
SALES FORM
MsgBox ("DATA IS ADDED")
End Sub
End If
End If
End Sub
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
End Sub
LOGIN:
Form2: INVENTORY REPORT
PURCHASE FORM
TESTING:
Cost Estimation:
cost per month.
Software Testing
White Box testing:
Black Box testing:

techniques.
Unit testing:
Smoke Testing:
concurrency.
CONCLUSION:
The INVENTOTORY STSTEM is the greatest improvement achieved by design and

implementation of an online personal stock trading system that would be deliverable over the
World Wide Web replete with interactive modules.
EX.NO: 10
DATE:
QUIZ
SYSTEM AIM:
To implement the Quiz System using Rational Software.
ALGORITHM:
Step 1: Identify the Actors and Use cases.
In this system,the actors and use
cases are: Actors: User ,System and
Database.
Use cases: Login,Option,answering questions,calculating marks and Display
score card.
Step 2: Build the relationship between actors and use cases.
The use case diagram for the quiz system is given in Fig(1).
Fig (1): Use case diagram for the Quiz System
WWW.VIDYARTHIPLUS.COM
TEAM
V+
2. ALGORITHM FOR SEQUENCE

DIAGRAM: Step 1: Identify the objects.
In this system, the objects are: User, System and
Database. Step 2: Identify the sequence of events.
Step 3: Login to the system to check the
validity. Step 4: Select the option in the
system.
Step 5: Answer the questions for the selected
options Step 6: Evaluate the answer and
calculate the mark. Step 7: Save the score in
the database.
Step 8: Display the score.
USER
ENTER THE LOGIN NAME
DATABASE
DISPLAY CATAGORIES FORM
SELECT ANY CATAGORIES
DISPLAY THE QUESTIONS
ANSWER THE QUESTIONS
DISPLAY THE SCORE

STORE THE SCORE
Fig(2): Sequence diagram for Quiz System
WWW
WW.VIDYARTHIPLUS.COM
3. ALGORITHM FOR CLASS DIAGRAM:

Step 1: Create class diagram for each identified objects under sequence
diagram. Identified objects are: User, System and
Database.
Step 2: Class diagram for each object is divided into three
parts. Top portion represents the Class Name.
Middle portion represents the
Attributes. Bottom portion
represents the Methods.
The Class diagram for Quiz System is shown in Fig(3).
Fig(3):Class diagram for Quiz system

Procedure to write the software for the Quiz System using Rational
Software tool Selecting the Software:
1. Click start-> Rational Software->Rational Rose Enterprise
Edition. Create the project:
2. In the Create New Model window select VB6 Standard Framework->A screen
appears;select the untitled project from the browser window and save it
To draw the diagram:
3.Right Click the Use case view->New->Use case diagram->Sequence diagram>Class diagram(name and save the files)
4. Click Use case diagram->using the tool box build the use case
diagram. 5. Click Sequence diagram->using the tool box build the
sequence diagram. 6. Click Class diagram-> using the tool box build
the class diagram.
TEAM
V+
Generate the coding form:

7.Right click component view -> component diagram-> open specification -> select the
stereotype as DLL-> select the language as visual basic ->switch from general tab to
realizes
tab-> select the classes you created in class diagram-> right click ->Assign->Ok.
8.Right click component view -> update code form model-> the tool window for
converting
diagrams to code appears->next->finish->the skeleton code in VB is generated
automatically for the class diagram designed.
SOURCE CODE
LOGIN FORM:
Option Explicit
Public LoginSucceeded As Boolean
Private Sub cmdCancel_Click()
LoginSucceeded = False
End
End Sub
Private Sub cmdOK_Click()
If txtUserName = "mca" Then
If txtPassword = "mca" Then
LoginSucceeded = True
Form1.Show
Me.Hide
Else
MsgBox "Invalid Password, try again!", vbInformation, "Login"
txtPassword.SetFocus
End If
Else
MsgBox "Invalid Username, try again!", vbInformation, "Login"
End If
.IDYARTHIPLUS.COM
End Sub
Form 1:
Form2.Show
Me.Hide
End Sub
Form5.Show
Me.Hide
End Sub
Form6.Show
Me.Hide
End Sub
Form 2:
Dim a As Integer
Text1.Text = ""
If Option2.Value = True Then
Text1.Text = Val(Text1.Text) + 10WW.VIDYARTHIPLUS.COM
Else
Text1.Text = Val(Text1.Text) + 0
End If
Frame2.Visible = True
Frame1.Visible = False
End Sub
Else
End If
Form3.Show
Me.Hide
End Sub
Private Sub Form_Load()
End Sub
TEAM
V+
Private Sub Timer1_Timer()

Me.Hide
Form1.Show
End Sub
Form 3:
Else
End If
Frame2.Visible = True
End Sub
CO
TEAM
V+
Else
End If
Form8.Show
Me.Hide
End Sub
End Sub
RESULT FORM:
Dim db As Database
Dim rs As Recordset
rs(0) = lable2.Caption
rs(1) = Text1.Text
rs(2) = Text2.Text
AddNew
End Sub
TEAM
V+

End
End Sub

If Form1.Option2.Value = True Then
Label2.Caption = Val(Form3.Text1.Text) + Val(Form2.Text1.Text)
ElseIf Form1.Option3.Value = True Then
End If
End Sub
MDIForm1.Label1.Caption = ""
MDIForm1.Picture1.Visible = False
Set db = OpenDatabase("D:\PROJECTS\tittu pro\RESULT.MDB")
Set rs = db.OpenRecordset("res")
End Sub
TEAM
V+
OUTPUT:
LOGIN
FORM :
FO
RM 1:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 2:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 3:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
RESULT FORM:
RE
SULT:
Thus the above program has been successfully completed and drawn in Rational Rose.
TEAM
V+
EX.NO: 11
DATE:
ATM SYSTEM
AIM
To implement the ATM System using Relational Software.
ALGORITHM
1. ALGORITHM FOR USE CASE DIAGRAM:
Step1: Identify the Actors and Use cases.
In the system, the actors and use cases are:

Actors: User, System and Database.
Use cases: Login, Deposit, withdrawal, updation, balance enquiry
Step2: Build the relationship between actors and Use cases.
The use case diagram for the expect system is given in Fig (1).
Fig (1): Use case diagram for the ATM System
WWW.VIDYAR
V+
THIPLUS.COM
TEAM
2. ALGORITHM FOR SEQUENCE DIAGRAM:

Step1: Identify the objects.
In this System, the objects are: User, System and Database.
Step2: Identify the sequence of events.
Step3: Login to the system to check the validity.
Step4: Select the option in the system.
Step5: For the user to deposit or withdraw the amount ,they should enter the option in the
System.
Step6: The System will do the corresponding processing with proper Updation in the Database.
Step7: Finally the balance is displayed to the user.
The sequence diagram for ATM System is give4n in Fig(2).

Fig (2): Sequence diagram for ATM System
.COM
TEAM
WWW.VIDYARTHIPLUS
V+
3. ALGORITHM FOR CLASS DIAGRAM:

Step1: Create class diagram for each identified objects under sequence diagram.
Identified objects are: User, System and Database.
Step2: Class diagram for each object is divided into three parts.
Top portion represents the Class name.
Middle portion represents the Attributes.
Bottom portion represents the methods.
The class diagram for ATM system is shown in Fig (3).
<Implements>
<Implements>
<Implements>
<Implements>
Fig (3): class diagram for ATM system

TEAM
V+
Procedure to write the software for the ATM system using rational Software tool
Selecting the Software:
1. Click startRational SoftwareRational Rose Enterprise Edition.
Create the project:
2. In the Create New model window select VB6 Standard FrameworkA screen
appears; select the untitled project from the browser window and save it.
3. Right Click the use case viewNewUse case diagramSequence diagramclass
diagram (name and save the files)
4. Click use case diagramusing the tool box build the use case diagram.
5. Click sequence diagramusing the tool box build the sequence diagram.
6. Click class diagramusing the tool box build the class diagram.
7.Right click Component viewcomponent diagramOpen specificationselect the
Stereotype as DLLSelect the language as Visual BasicSwitch from General tab to
Realize tabSelect the classes you created in class diagramright clickAssignOk.
8. Right click component viewupdate code from modelthe tool window for
converting diagrams to code appearsnextFinishthe skeleton code in VB is
generated automatically for the class diagram.
TEAM
V+
SOURCE CODE:
PINPROCESS CODING:
Dim DB As Database
Dim RS As Recordset
Dim A As Integer
A = Val(Text1.Text)
RS.MoveFirst
While (True)
If Val(A) = Val(RS(3)) Then
form2.Show
GoTo AA
Else
RS.MoveNext
End If
If RS.EOF = True Then
MsgBox "YOUR PIN NUMBER IS WRONG"
GoTo AA
End If
Wend
AA:
End Sub

Set DB = OpenDatabase("E:\atm\STORAGE.mdb")
Set RS = DB.OpenRecordset("CUSDET")
End Sub
TEAM
V+
DISPLAY CODING:
Dim DB As Database
Dim RS As Recordset
RS.MoveFirst
While (True)
If Val(Form1.Text1.Text) = Val(RS(3)) Then
Form3.Show
GoTo AA
Else
RS.MoveNext
End If
Wend
AA:
End Sub
Form4.Show
End Sub
Form5.Show
End Sub
Form6.Show
End Sub
Form1.Show
End Sub
TEAM
V+

RS.MoveFirst
While (True)
Label2.Caption = RS(2)
GoTo AA
Else
RS.MoveNext
End If
Wend
AA:
End Sub
BALANCE ENQUIRY CODING:

Dim DB As Database
Dim RS As Recordset
Unload Me
Form1.Show
Form1.Text1.Text = ""
Form1.Text1.SetFocus
End Sub
Form1.Show
End Sub
TEAM
V+

RS.MoveFirst
While (True)
GoTo AA
Else
RS.MoveNext
End If
Wend
AA:
End Sub
WITHDRAW CODING:
Dim DB As Database
Dim RS As Recordset
Dim B As Double
B=0
B = Val(Text1.Text)
RS.MoveFirst
While (True)
If (Val(B) > Val(RS(4))) Then
TEAM
V+
MsgBox "YOUR BALANCE IS LOW"

Text1.Text = ""
Text1.SetFocus
GoTo BB
Else
MsgBox "TAKE YOUR CASH "
Text1.Text = ""
B = Val(RS(4)) - Val(B)
RS.Edit
RS(4) = Val(B)
RS(5) = Val(RS(4))
RS.Update
GoTo AA
End If
Else
RS.MoveNext
End If
Wend
AA:
BB:
Form1.Show
End Sub
Text1.Text = ""
Form1.Show
TEAM
V+
End Sub
Text1.Text = ""
End Sub
MOBILE NUMBER CHANGE CODING:

Dim DB As Database
Dim RS As Recordset
Dim B As Double

B=0
B = Val(Text1.Text)
RS.MoveFirst
While (True)
If (Val(B) > Val(RS(4))) Then
MsgBox "YOUR BALANCE IS LOW"
Text1.Text = ""
Text1.SetFocus
GoTo BB
Else
MsgBox "TAKE YOUR CASH "
Text1.Text = ""
B = Val(RS(4)) - Val(B)
RS.Edit
TEAM
V+
RS(4) = Val(B)
RS(5) = Val(RS(4))
RS.Update
GoTo AA
End If
Else
RS.MoveNext
End If
Wend
AA:
BB:
Form1.Show
End Sub
Form1.Show
End Sub
Text1.Text = ""
End Sub
TEAM
V+
PIN NUMBER CHANGE CODING:

Dim DB As Database
Dim RS As Recordset
RS.MoveFirst
While (True)
If Val(Text1.Text) = Val(RS(3)) Then
MsgBox "PIN ALREADY EXIST"
Text1.Text = ""
GoTo BB
Else
RS.MoveNext
End If
If RS.EOF = False Then
GoTo CC
End If
Wend
CC:
RS.MoveFirst
While (True)
RS.Edit
RS(3) = Val(Text1.Text)
Form1.Text1.Text = Val(Text1.Text)
RS.Update
MsgBox "YOUR PIN NO WILL BE CHANGE"
Text1.Text = ""
TEAM
V+
GoTo AA
Else
RS.MoveNext
End If
Wend
AA:
Form1.Show
Unload Me
BB:
End Sub
Text1.Text = ""
Form1.Show
End Sub
RS.MoveFirst
While (True)
GoTo AA
Else
RS.MoveNext
End If
Wend
AA:
End Sub
TEAM
V+

End Sub
OUTPUT:
PIN NUMBER PROCESS FORM:
MEN
U FORM:
WWW.V
V+
IDYARTHIPLUS.COM
TEAM
BALANCE ENQUIRY FORM:
WITH
DRAW FORM:
WWW.VIDYARTHIP
V+
LUS.COM
TEAM
PIN NUMBER CHANGE FORM:
MOBI
LE NUMBER CHAGE FORM:
WWW.V
V+
IDYARTHIPLUS.COM
TEAM
CHECK YOUR BALANCE FORM:
CHECK YOUR PIN NUMBER:
RESULT:
EX.NO: 12
DATE:
TICKET RESERVATION SYSTEM
AIM
To implement the Ticket Reservation System using Rational Software.

ALGORITHM
1. ALGORITHM FOR USE CASE DIAGRAM (TICKET RESERVATION):
Step1:Identify the Actors and Usecases.
In the system ,the actors and use cases are:
Actors :Passenger,System,and Database.
Usecases :Details,seats available,reservation of ticket,and
Print the journey of reservation ticket.
Step2:Build the relationship between actors.
The Use case diagram for Ticket Reservation is given in fig(1).
Information_Cancellation
Seats _Available
Sys
Passenger
Reservation_of_Ticket
Reserve_the_Ticket
Database
View_and_print_the_journey_r...
Fig(1):Use case Diagram for Ticket Reservation
TEAM
V+
2. ALGORITHM FOR USE CASE DIAGRAM (TICKET CANCELLATION):

Step1:Identify the Actors and Usecases.
In the system ,the actors and use cases are:
Actors :Passenger,System,and Database.
Use cases: cancellation of ticket,cancel the ticket,view the cancelled details.
Step2: Build the relationship between actors and use cases.
The Use case diagram for Ticket Cancellation is given in fig(2).
Cancellation_of_Ticket
passenger
sys
Cancel_the _Ticket
d
atabase View_and_Print_Cancelled_Details
Fig(2):Use case Diagram for Ticket Cancellation
TEAM
V+
3. ALGORITHM FOR SEQUENCE DIAGRAM (TICKET RESERVATION):

Step1:Identify the objects.
In this system,the odjects are:Passenger,System Database and Reservation.
Step2:Identify the sequence of events.
Step3:Select the required information for reservation.
Step4:Perforn the reservation process.
Step5:Save the details in database.
Step6:Send the details to the system.
Step7:View and print the journey of reservation ticket details.
The Sequence diagram for Ticket Reservation is given in fig(3).
pass enger
sys tem
databas e
res ervat ion
1.Get the seat availablity
2.Provide details
3.Select information to reserve
4.Perform the reservation process
5.Save the details
6.Send the details
7.View and print the journey of reservation
Fig(3):Sequence diagram for Ticket Reservation
TEAM
V+
4. ALGORITHM FOR SEQUENCE DIAGRAM (TICKET CANCELLATION):

Step1:Identify the objects.
In this system,the objects are:Passenger,System Database and Cancellation.

Step2:Identify the sequence of events.
Step3:Enter the PNR number.
Step4:Perform the cancellation process.
Step5:Send the details to the system.
Step6:View the completion process of ticket cancellation.
The Sequence diagram for Ticket Cancellation is given in fig(4).
system
1.Enter the PNR no
database
cancellation
2.Perform the cancellation

process
3.Cancel
the ticket
4.Send the details
5.View and print the cancellation process
Fig(4):Sequence diagram for ticket cancellation
TEAM
V+
5. ALGORITHM FOR CLASS DIAGRAM (TICKET RESERVATION):

Step1:Create class diagram for each identified Objects under sequence diagram.
Identified objects are:User,System and Database and reservation.
Step2:Class diagram for each object is divided into three parts.
Top portion represents the class Name.
Bottom portion represents the Methods.
The Class diagram for Ticket Reservation is shown in fig(5).
WWW.VIDYARTHIP
V+
LUS.COM
TEAM
6. ALGORITHM FOR CLASS DIAGRAM (TICKET CANCELLATION):

Step1:Create class diagram for each identified Objects under sequence diagram.
Identified objects are:User,System and Database and reservation.
Step2:Class diagram for each object is divided into three parts.
The Class diagram for Ticket Cancellation is shown in fig(6).
WWW.VIDYARTHIPLUS.CO
V+
M
TEAM
Procedure to write the software for the Online Ticket Reservation System Using
Rational Software tool
Selecting the software:
1.click start->Rational Software->Rational Rose Enterprice Edition.
Create the project:
2.In the Create New Model window select VB6 Standard Framework->A screen
appears;select the untitled project from the browser window and save it.

3.Right click the Use case view->New->Use case diagram->Sequence diagram->
Class diagram(name and save the files)
4.Click Use case diagram->Using the tool box build the use case diagram.
5.Click Sequence diagram->Using the tool box build the sequence diagram.
6.Click class diagram->Using the tool box build the class diagram.
TEAM
V+
SOURCE CODE:
FORM 1:
If Text1.Text = "online" And Text2.Text = "mca" Then
MsgBox "WELCOME"
Form2.Show
Form1.Hide
Else
MsgBox "INVALIDE LOGIN"
End If
End Sub
FORM 2:
Form2.Hide
Form3.Show
End Sub
Form2.Hide
Form4.Show
End Sub
TEAM
V+

Form2.Hide
Form6.Show
End Sub
FORM 3:
Dim db As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub Add_Click()
rs.AddNew
rs(0) = Combo1.Text
rs(1) = Text1.Text
rs(2) = Text2.Text
rs(3) = Text3.Text
rs(4) = Text4.Text
rs(5) = Text5.Text
rs(6) = Text6.Text
rs(7) = Text7.Text
rs(8) = Text8.Text
rs(9) = Text9.Text
MsgBox "new Record Added"
End Sub
TEAM
V+

rs.MoveFirst
Combo1.Text = rs(0)
Text1.Text = rs(1)
Text2.Text = rs(2)
Text3.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
Text9.Text = rs(9)
End Sub
rs.MovePrevious
Combo1.Text = rs(0)
Text1.Text = rs(1)
Text2.Text = rs(2)
Text3.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
TEAM
V+
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
Text9.Text = rs(9)
End Sub
rs.MoveNext
Combo1.Text = rs(0)
Text1.Text = rs(1)
Text2.Text = rs(2)
Text3.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
Text9.Text = rs(9)
End Sub
rs.MoveLast
Combo1.Text = rs(0)
TEAM
V+
Text1.Text = rs(1)
Text2.Text = rs(2)
Text3.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
Text9.Text = rs(9)
End Sub
rs.Delete
Combo1.Text = ""
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
TEAM
V+
Text9.Text = ""
End Sub
Form2.Show
Form3.Hide
End Sub
Combo1.Text = ""
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
End Sub
DataReport2.Show
End Sub
TEAM
V+
Private Sub Delete_Click()

rs.Delete
Combo1.Text = ""
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
End Sub
db.CursorLocation = adUseClient
db.Open "Provider=MSDAORA.1;User ID=scott;password=tiger;Data Source=oracle;Persist
Security Info=False"
rs.Open "details", db, adOpenDynamic, adLockOptimistic
Combo1.Text = rs(0)
Text1.Text = rs(1)
Text2.Text = rs(2)
TEAM
V+
Text3.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
Text9.Text = rs(9)
End Sub
Private Sub Home_Click()
Form3.Hide
Form2.Show
End Sub
FORM 4:
Dim db As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub Combo1_Click()
Select Case Combo1.Text
Case "Vaigai Express"
Text4.Text = "TN 28/1234"
Text5.Text = "Chennai"
Text6.Text = "Kovai"
TEAM
V+
Text7.Text = "7.00AM"
Text8.Text = "800"
Case "Kovai Express"
Text5.Text = "Kovai"
Text6.Text = "Delhi"
Text7.Text = "2.00PM"
Text8.Text = "1500"
Case "Blue Mountain"

Text5.Text = "Trichy"
Text6.Text = "Chennai"
Text7.Text = "5.00AM"
Text8.Text = "700"
Case "Pandiyan Express"
Text5.Text = "Salem"
Text6.Text = "Karaikudi"
Text7.Text = "7.00Pm"
Text8.Text = "900"
End Select
TEAM
V+
End Sub
Form4.Hide
Form2.Show
End Sub
rs.Delete
End Sub
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Combo1.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
End Sub
TEAM
V+

Form6.Show
Form4.Hide
End Sub
rs.MoveFirst
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Combo1.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
End Sub
rs.MovePrevious
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
TEAM
V+
Combo1.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
End Sub
rs.MoveNext
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Combo1.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
End Sub
TEAM
V+

rs.MoveLast
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Combo1.Text = rs(3)
Text4.Text = rs(4)
Text5.Text = rs(5)
Text6.Text = rs(6)
Text7.Text = rs(7)
Text8.Text = rs(8)
End Sub
Combo1.AddItem ("Vaigai Express")
Combo1.AddItem ("Kovai Express")
Combo1.AddItem ("Blue Mountain")
Combo1.AddItem ("Pandiyan Express")
db.CursorLocation = adUseClient
db.Open "Provider=MSDAORA.1;Password=tiger;User ID=scott;Data
Source=oracle;Persist Security Info=True"
rs.Open "reser222", db, adOpenDynamic, adLockOptimistic
TEAM
V+
End Sub
Private Sub Report_Click()
DataReport2.Show
End Sub
FORM 5:
Dim a As Integer
Dim b As Integer
Dim c As Integer
Dim d As Integer
Dim i As Integer
'Dim e As Integer
If Option1 = True Then
Text3.Text = "Male"
ElseIf Option2 = True Then
Text3.Text = "Female"
End If
End Sub
TEAM
V+

Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Combo1.Text = ""
Combo2.Text = ""
Combo3.Text = ""
Combo4.Text = ""
End Sub
If Option3 = True Then
Text8.Text = "Firstclass"
ElseIf Option4 = True Then
Text8.Text = "Secondclass"
End If
TEAM
V+
If Text8.Text = "Firstclass" Then

a = Val(Combo1.Text) * 500
b = Val(Combo2.Text) * 300
c = Val(Combo3.Text) * 250
Text7.Text = a + b + c
ElseIf Text8.Text = "Secondclass" Then
a = Val(Combo1.Text) * 300
b = Val(Combo2.Text) * 150
c = Val(Combo3.Text) * 100
Text7.Text = a + b + c
Else
MsgBox "Invalid Entry"
End If
End Sub
End Sub
Private Sub Home_Click()
Form2.Show
Form6.Hide
End Sub
TEAM
V+
Private Sub Text1_Change()

Combo4.Clear
d = Val(Text1.Text) + d
For i = i To Val(d) - 1
Combo4.AddItem i + 1
Next
End Sub
TEAM
V+
OUTPUT:
FORM 1:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 2:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 3:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 4:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 5:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
FORM 6:
RE
SULT:
EX. NO: 13
DATE:
PAYROLL PROCESSING
AIM:
To Implement the Payroll Processing using Rational Software.
ALGORITHM:
1. ALGORITHM FOR USE CASE DIAGRAM:
STEP1: Identify the Actors and Use Cases.
In the system, actors and use cases are:
Actors: Employee, Administrator, System and Database.

Use cases: Employee details, validity check, payroll processing, view and print the salary
details.
STEP2: Build the relationship between actors and Use case.The use case diagram for the
payroll processing is given in Fig(1).
F
ig(1):Use case diagram for the payroll processing
TEAM
V+
2. ALGORITHM FOR SEQUENCE DIAGRAM:

STEP 1: Identify the objects.
In this system, the objects are: Employee, Administrator, System and Database.
STEP 2: Identify the sequence of events.

STEP 3: Enter the employee ID.
STEP 4: Perform the computation.
STEP 5: Return the computed values to the database.
STEP 6: Save the details in database.
STEP 7: View and print the salary details.
The Sequence diagram for payroll processing is given in Fig (2).
Fig (2):
Sequence diagram for payroll processing
TEAM
V+
3: ALGORITHM FOR CLASS DIAGRAM:

STEP 1: Create class diagram for each identified objects under sequence diagram.
Identified objects are: Employee, Administrator, System and Database.
STEP 2: Class diagram for each object is divided into three parts.
The Class diagram for Payroll Processing shown in Fig (3).
Fig (3):class diagram for payroll processing
TEAM
V+
Procedure to write the software for the payroll processing using Rational software tool
Selecting the Software:
1.Click startRational SoftwareRational Rose Enterprise Edition.
Create the project:
2.In the Create New Model window select VB6 Standard FrameworkA screen appears;select the
untitled project from the browser window and save it

3.Right Click the Use case viewNewUse case diagramSequence diagramClass diagram(name
and save the files)
4.Click Use case diagramUsing the tool box build the use case diagram.
5.Click Sequence diagramusing the tool box build the sequence diagram.
6.Click Class diagramUsing the tool box build the class diagram.
7.Right click Component viewcomponent diagramopen specificationselect the Stereotype as
DLLSelect the language as Visual basicSwitch from General tab to Realizes tabSelect the
classes you created in class diagramright clickAssignOK.
8.Right click Component viewUpdate code from modelthe tool window for converting diagrams to
code appearsnextFinish the skeleton code in VB is generated automatically for the class diagram
designed.
TEAM
V+
SOURCE CODE:
LOGIN PROCESS:
Dim db As Database
Dim rs As Recordset
Data1.Recordset.update
MsgBox "RECORDS ARE SUCCESSFULLY UPDATED"
End Sub
admin.Show
End Sub
End
End Sub
Private Sub Data1_Validate(Action As Integer, Save As Integer)
Data1.Visible = False
End Sub
Set db = OpenDatabase("D:\CASE TOOLS\emp.mdb")
Set rs = db.OpenRecordset("emp1")
End Sub
TEAM
V+
ADMIN PROCESS:
Dim db As Database
Dim rs As Recordset
End Sub
Private Sub Label2_Click()
addemp.Show
End Sub
delete.Show
End Sub
update.Show
End Sub

login.Show
End Sub
TEAM
V+
ADDING EMPLOYEE PROCESS:

Dim db As Database
Dim rs As Recordset
End
End Sub
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs(7) = Text8.Text
rs(8) = Text9.Text
rs(10) = Text10.Text
rs(9) = Text11.Text
rs.update
MsgBox "RECORD IS ADDED"
End Sub
TEAM
V+

admin.Show
End Sub
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
rs.AddNew
End Sub
End Sub
Set db = OpenDatabase("D:\CASE TOOLS\emp.MDB")
End Sub
TEAM
V+
Private Sub Text8_Change()

Text9.Text = 2 / 100 * Val(Text8.Text)
Text10.Text = 4 / 100 * Val(Text8.Text)
Text11.Text = Val(Text8.Text) + Val(Text9.Text) - Val(Text10.Text)
'Text5.Text = 12 / 100 * Val(Text3.Text)

End Sub
DELETING PROCESS:
Dim db As Database
Dim rs As Recordset
Adodc1.Recordset.delete
MsgBox "Record deleted"
Text1.Text = ""
End Sub
admin.Show
End Sub
End Sub
TEAM
V+

End Sub
UPDATING PROCESS:
Dim db As Database
Dim rs As Recordset
Data1.Recordset.update
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs(7) = Text8.Text
rs(8) = Text9.Text
rs(9) = Text11.Text
MsgBox "RECORDS ARE SUCCESSFULLY UPDATED"
TEAM
V+
End Sub
admin.Show
End Sub
End
End Sub
rs.Edit
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs(7) = Text8.Text
rs(8) = Text9.Text
rs(9) = Text11.Text
End Sub
TEAM
V+

End Sub
End Sub
SEARCH EMPLOYEES FORM:
Dim db As Database
Dim rs As Recordset
Dim a As Integer

'a = Form9(rs(0))
rs.MoveFirst
While (True)
If Val(Text1.Text) = Val(rs(0)) Then
empdetails.Show
empdetails.Label2.Caption = rs(0)
TEAM
V+
GoToaa
Else
rs.MoveNext
End If
Wend
aa:
End Sub
End
End Sub
End Sub
TEAM
V+

admin.Show
End Sub

Set db = OpenDatabase("D:\CASE TOOLS\emp.MDB")
End Sub
TEAM
V+
OUTPUT:
ADMIN LOGIN FORM:
AD
MINISTRATOR FORM:
WWW.VI
V+
DYARTHIPLUS.COM
TEAM
EMPLOYEE FORM:
DELET
E FORM:
WW
W.VIDYARTHIPLUS.COM
TEAM
V+
UPDATE FORM:
EMPLO
YEE ADMIN FORM:
WW.VID
V+
YARTHIPLUS.COM
TEAM
EMPLOYEE SEARCH FORM:
EMPLO
YEE DETAILS:
RESU
LT:
WWW.VIDYARTHIP
TEAM
V+

LabManual Final 2

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

LabManual Final 2

Diunggah oleh

Hak Cipta:

Format Tersedia

Ex No: 1

PRACTICING THE DIFFERENT TYPES OF CASE TOOLS SUCH AS

It is a graphic oriented tool.

It supports decomposition of process.

Some typical CASE tools are:

Unified Modeling Language

Data modeling tools, and

Source code generation tools

UML basic building blocks

Rules that dictate how this building blocks put together

Some common mechanism that apply throughout the language

The primary goals in the design of UML are:

Provides users ready to use, expressive visual modeling language as well

\Provide extensibility and specialization mechanisms to extend the core

Be independent of particular programming languages and development

Provide formal basis for understanding the modeling language.

Encourage the growth of the OO tools market.

Support higher-level development concepts.

Integrate best practices and methodologies.

The UML defines nine graphical diagrams:

state chart diagram

Use Case Diagram

Only receive information from the system.

Between actor and use case.

Documenting Flow of events

Break down into the most atomic actions possible.

Contents of Flow of Events

When and how the use case starts and ends.

Template for the flow of events document

Activities- performance of some behavior in the workflow.

Classes: a description of a group of objects with common properties (attributes), common

Attribute: the basic data of the class.

Classes are divided into three categories:

Relevant classes: part of the application domain; occur frequently in requirements.

Tangible things: e.g. buildings, cars.

Use CRC for brainstorming.

Class Elicitation Guidelines

A class should have a single major role.

Sequence diagrams are a graphical way to illustrate a scenario:

Creating Sequence Diagrams

Always keep your diagrams simple.

Toggling between the sequence and collaboration diagrams

Creating State Transition Diagrams

State Transition Details

State transition diagram notation:

UML Implementation Diagrams

UML Component Diagram

Deployment Diagrams: Device

USE-CASE name: Mini statement

The ATM system class diagram consists of four classes:

Class diagram for ATM system

Sequence and collaboration diagram for deposit process

Sequence and collaboration diagram for login

Sequence and collaboration diagram for checking machine status

Sequence and collaboration diagram for printing mini statement

Sequence and collaboration diagram for withdraw process

To assist business analysts, programmers, testers, manual writers, IT package selectors,

To manage data as a resource

For the integration of information systems

For designing databases/data warehouses

CONCEPTUAL, LOGICAL AND PHYSICAL SCHEMAS:

THREE KINDS OF DATA-MODEL INSTANCE:

DATA MODELING PROCESS:

Physical Data Modeling serves as a direct representation of the implementation plan of a