CS6511case Tools Lab Manual Updated

CS6511 Case Tools Lab Manual
Ex. No:1
Date:
Introduction to Case Tools
Introduction:
CASE tools known as Computer-aided software engineering tools is a kind of component-based development which
allows its users to rapidly develop information systems. The main goal of case technology is the automation of the
entire information systems development life cycle process using a set of integrated software tools, such as modeling,
methodology and automatic code generation. Component based manufacturing has several advantages over custom
development. The main advantages are the availability of high quality, defect free products at low cost and at a faster
time. The prefabricated components are customized as per the requirements of the customers. The components used
are pre-built, ready-tested and add value and differentiation by rapid customization to the targeted customers.
However the products we get from case tools are only a skeleton of the final product required and a lot of
programming must be done by hand to get a fully finished, good product.
Characteristics of CASE:
Some of the characteristics of case tools that make it better than customized development are;
It is a graphic oriented tool.
It supports decomposition of process.
Some typical CASE tools are:
Unified Modeling Language
Data modeling tools, and
Source code generation tools
Introduction to UML (Unified Modeling Language)
The UML is a language for specifying, constructing, visualizing, and documenting the software system and its
components. The UML is a graphical language with sets of rules and semantics. The rules and semantics of a model
are expressed in English in a form known as OCL (Object Constraint Language). OCL uses simple logic for
specifying the properties of a system. The UML is not intended to be a visual programming language. However it
has a much closer mapping to object-oriented programming languages, so that the best of both can be obtained. The
UML is much simpler than other methods preceding it. UML is appropriate for modeling systems, ranging from
enterprise information system to distributed web based application and even to real time embedded system. It is a
very expensive language addressing all views needed to develop and then to display system even though understand
to use. Learning to apply UML effectively starts forming a conceptual mode of languages which requires learning.
UML DIAGRAMS
There are three classifications of UML diagrams:
Behavior diagrams. A type of diagram that depicts behavioral features of a system or business process.
This includes activity, state machine, and use case diagrams as well as the four interaction diagrams.
Interaction diagrams. A subset of behavior diagrams which emphasize object interactions. This includes
communication, interaction overview, sequence, and timing diagrams.
Structure diagrams. A type of diagram that depicts the elements of a specification that are irrespective of
time. This includes class, composite structure, component, deployment, object, and package diagrams.
Diagram
Description
Learning Priority
Activity Diagram
Class Diagram
Communication
Diagram
Component Diagram
Composite
1
Structure
Depicts high-level business processes, including data flow,

or to model the logic of complex logic within a system.
Shows a collection of static model elements such as
classes and types, their contents, and their relationships.
Shows instances of classes, their interrelationships, and the
message flow between them. Communication diagrams
typically focus on the structural organization of objects
that send and receive messages. Formerly called a
Collaboration Diagram.
Depicts the components that compose and application,
system, or enterprise. The components, their
interrelationships, interactions, and their public interfaces
are depicted.
Depicts the internal structure of a classifier(such as a class,
Prepared By: Mrs. S. Selvakanmani & Mr. R. Raja, CSE Department
High
High
Low
Medium
Low
Diagram
Deployment Diagram
Interaction Overview
Diagram
Object Diagram
component, or use case), including the interaction points

of the classifier to other parts of the system.
Shows the execution architecture of systems. This includes
nodes, either hardware or software execution
environments, as well as the middleware connecting them.
A variant of an activity diagram which overviews the
control flow within a system or business process. Each
node/activity within the diagram can represent another
interaction diagram.
Depicts objects and their relationships at a point in time,
typically a special case of either a class diagram or a
communication diagram.
Medium
Low
Low
Package Diagram
Show how model elements are organized into packages as

well as the dependencies between packages.
Low
Sequence Diagram
Models the sequential logic, in effect the time ordering of

messages between classifiers.
High
State
Machine
Diagram
Describes the states an object or interaction may be in, as

well as the transitions between states. Formerly referred to
as a state diagram, state chart diagram, or a state-transition
diagram.
Medium
Timing Diagram
Depicts the change in state or condition of a classifier

instance or role over time. Typically used to show the
change in state of an object over time in response to
external events.
Low
Use Case Diagram
Shows use cases, actors, and their interrelationships.
Medium
USE CASE DIAGRAM:

A use case diagram is a type of behavioral diagram defined by the Unified Modeling Language (UML).
Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their
goals- represented as use cases- and any dependencies between those use cases.
Use case diagram depict:
Use cases. A use case describes a sequence of actions that provide something of measurable value to an
actor and is drawn as a horizontal ellipse.
Actors. An actor is a person, organization, or external system that plays a role in one or more interactions
with your system. Actors are drawn as stick figures.
Associations. Associations between actors and use cases are indicated in use case diagrams by solid lines.
An association exists whenever an actor is involved with an interaction described by a use case.
Associations are modeled as lines connecting use cases and actors to one another, with an optional
arrowhead on one end of the line. The arrowhead is often used to indicating the direction of the initial
invocation of the relationship or to indicate the primary actor within the use case. The arrowheads are
typically confused with data flow and as a result I avoid their use.
System boundary boxes (optional). You can draw a rectangle around the use cases, called the system
boundary box, to indicate the scope of your system. Anything within the box represents functionality that is
in scope and anything outside the box is not. System boundary boxes are rarely used, although on occasion
I have used them to identify which use cases will be delivered in each major release of a system.
Packages (optional). Packages are UML constructs that enable you to organize model elements (such as
use cases) into groups. Packages are depicted as file folders and can be used on any of the UML diagrams,
including both use case diagrams and class diagrams. I use packages only when my diagrams become
unwieldy, which generally implies they cannot be printed on a single page, to organize a large diagram into
smaller ones.
List Items
View Item
Edit Item
Actor
Create Item
Delete Item
RELATIONSHIPS IN USE CASE DIAGRAM:
Three relationships among use cases are supported by the UML standard, which describes graphical
notation for these relationships.
Include : In one form of interaction, a given use case may include another. The first use case often depends on the
outcome of the included use case. This is useful for extracting truly common behaviors from multiple use cases into
a single description. The notation is a dashed arrow from the including to the included use case, with the label
<<include>>. This usage resembles a macro expansion where the included use case behavior is placed inline in
the base use case behavior. There are no parameters or return values.
Extend: In another form of interaction, a given use case, (the extension) may extend another. This relationship
indicates that the behavior of the extension use case may be inserted in the extended use case under some conditions.
The notation is a dashed arrow from the extension to the extended use case, with the label <<extend>>. This can be
useful for dealing with special cases, or in accommodating new requirements during system maintenance and
extension.
To make the points at which extension may occur explicit extension points may be defined in use cases
which are listed in a compartment below the use case name.
Generalization : In the third form of relationship among use cases, a generalization/ specializationrelationship
exists. A given use case may be specialized form of an existing use case. The notation is a solid line ending in a
hollow triangle drawn from the specialized to the more general use case. This resembles the object-oriented concept
of sub-classing, in practice it can be both useful and effective to factor common behaviors, constraints and
assumptions to the general use case, describe them once, and deal same as except details in the specialized cases.
SEQUENCE DIAGRAM:
The well-known Message Sequence Chart technique has been incorporated into the Unified Modeling
Language (UML) diagram under the name of Sequence Diagram. A sequence diagram shows, as parallel vertical
lines, different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a
graphical manner.
Sequence diagrams are typically used to model:
1. Usage scenarios. A usage scenario is a description of a potential way your system is used. The logic of a usage
scenario may be part of a use case, perhaps an alternate course. It may also be one entire pass through use case, such
as the logic described by the basic course of action or a portion of the basic course of action, plus one or more
3

alternate scenarios. The logic of a usage scenario may also be a pass through the logic contained in several use
cases. For example, a student enrolls in the university, and then immediately enrolls in three seminars.
2. The logic of methods. Sequence diagrams can be used to explore the logic of a complex operation, function, or
procedure. One way to think of sequence diagrams, particularly highly detailed diagrams, is a visual object code.
3. The logic of services. A service is effectively a high-level method, often one that can be invoked by a wide
variety of clients. This includes web-services as well as business transactions implemented by a variety of
technologies such as CICS/COBOL or CORBA-compliant object request brokers (ORBs).
Fred Patron
Bob Waiter
Hank Cook
Renee
Cashier
order food()
order food()
serve Pepsi()
Pickup()
serve food()
Pay()
ACTIVITY DIAGRAM:
In the Unified Modeling Language, an activity diagram represents the business and operational step-bystep workflows of components in a system. An activity diagram shows the overall flow of control.
Describing the basic notations:
4
Initial node. The filled in circle is the starting point of the diagram. An initial node isnt required although
it does make it significantly easier to read the diagram.
Activity final node. The filled circle with a border is the ending point. An activity diagram can have zero
or more activity final nodes.
Activity. The rounded rectangles represent activities that occur. An activity may be physical, such as
Inspect Forms, or electronic, such as Display Create Student Screen.
Flow/edge. The arrows on the diagram. Although there is a subtle difference between flows and edges I
have never seen a practical purpose for the difference although I have no doubt one exists. Ill use the term
flow.
Fork. A black bar with one flow going into it and several leaving it. This denotes the beginning of parallel
activity.
Join. A black bar with several flows entering it and one leaving it. All flows going into the join must reach
it before processing may continue. This denotes the end of parallel processing.
Condition. Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to true in
traverse the node.
Decision. A diamond with one flow entering and several leaving. The flows leaving include conditions
although some modelers will not indicate the conditions if it is obvious.
Merge. A diamond with several flows entering and one leaving. The implication is that one or more
incoming flows much reach this point until processing continues, based on any guards on the outgoing
flow.
Partition. Activity Diagram is organized into many partitions, also called swim lanes, indicating who/what
is performing the activities (the Applicant, Registrar, or System).
Sub-activity indicator. The rake in the bottom corner of an activity, such as in the Apply to University
activity, indicates that the activity is described by a more finely detailed activity diagram.
Flow final. The circle with the X through it. This indicates that the process stops at this point.
Verify
reservation
[incorrect]
[correct]
Send to airport
travel agency
Get
preferences
[no baggage]
[baggage]
Print
boarding Card
Receive baggage
and print receipt
Give travel documentation

to passenger
CLASS DIAGRAM:
In the Unified Modeling Language (UML), a class diagram is a type of static structure diagram that
describes the structure of a system by showing the systems classes, their attributes, and the relationships between
the classes.
Relationships
A relationship is general term covering the specific types of logical connections found on class and object
diagrams. UML shows the following relationships:
Instance-Level Relationships
Link : A Link is the basic relationship among objects. It is represented as a line connecting two or
more object boxes. It can be shown on an object diagram or class diagram. A link is an instance
or an association.
Association: An Association represents a family of links. Binary associations (with two ends) are
normally represented as a line, with each end connected to a class box. Higher order associations
can be drawn with more than two ends. In such cases, the ends are connected to a central diamond.
An association can be named, and the ends of an association can be adorned with role names,
ownership indicators, multiplicity, visibility, and other properties. There are five different types of
association. Bi-directional and uni-directional associations are the most common ones. For
instance, a flight class is associated with a plane class bi-directionally. Associations can only be
shown on class diagrams.
Aggregation: Class diagram showing Aggregation between two classes.

Aggregation is a variant of the has a or association relationship; composition is more specific
than aggregation. As a type of association, an aggregation can be named and have the same
adornments that an association can. However, an aggregation may not involve more than two
classes.
Aggregation can occur when a class is a collection or container of other classes, but where the
contained classes do not have a strong lifecycle dependency on the containeressentially, if the
container is destroyed, its contents are not.
In UML, it is graphically represented as a cleardiamond shape on the containing class end of
the tree of lines that connect contained class(es) to the containing class.
Composition: Composition is a stronger variant of the has a or association relationship;

composition is more specific than aggregation.
Composition has a strong life cycle dependency between instances of the container class and
instances of the contained class(es): If the container is destroyed, every instance that it contains is
destroyed as well.
The UML graphical representation of a composition relationship is a filled diamond shape on the
containing class end of the tree of lines that connect contained class(es) to the containing class.
Differences between Composition and Aggregation

The whole of a composition must have a multiplicity of 0..1 or 1, indicating that a part must be for
only one whole. The whole of an aggregation may have any multiplicity.
When attempting to represent real-world whole-part relationships, e.g., an engine is part of a car,
the composition relationship is most appropriate. However, when representing a software or
database relationship, e.g., car model engine ENG01 is part of a car model CM01, an aggregation
relationship is best, as the engine, ENG01 may be also part of a different car model, CM02. This is
often called a catalog relationship.
Class Level Relationships

o
Generalization
Class diagram showing generalization between one super class and two subclasses
The generalization relationship indicates that one of the two related classes (the subtype) is considered to be a
specialized form of the other (the supertype) and supertype is considered as GENERALIZATION of subtype. In
practice, this means that any instance of the subtype is also an instance of the supertype. The relationship is most
easily understood by the phrase A is a B.
The UML graphical representation of a Generalization is a hollow triangle shape on the supertype end of the
line (or tree of lines) that connects it to one or more subtypes.
The generalized relationship is also known as the inheritance or is arelationship.
The supertype in the generalization relationship is also known as the parent, super class, base class, or
base type.
7

The subtype in the generalization relationship is also known as the child, subclass, derived class, derived
type, inheriting class, or inheriting type.
Generalization-Specialization relationship
A is a type of B
E.g.an oak is a type of tree, a sedan is a type of vehicle
Realization
In UML modeling, a realization relationship is relationship between model elements, in which one model
element (the client) realizes the behavior that the other model element (the supplier) specifies. A realization is
displayed in the diagram editor as a dashed line with an unfilled arrowhead towards the supplier.
o
General Relationship
Dependency(UML)
A dependency exists between two defined elements if a change to the definition of one would
result in a change to the other. This is indicated by a dashed pointing from the dependent to the independent element.
Several named varieties exist. A dependency can be between instances, class, or both.
o
Multiplicity
The association relationship indicates that (at least) one of the two related classes makes reference to the
other. In contrast with the generalization relationship, this is most easily understood through the phrase A has a
B{a mother cat has kittens, kittens have a mother cat}.
The UML representation of an association is a line with an optional arrowhead indicating the role of the
object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that
entity ( the number of objects that participate in the association). Common multiplicities are:
Indicator
0..1
1
0..* or *
1..*
n
0..n
1..n
Meaning
No instances, or one instance(optional, may)
Exactly one instance
Zero or more instances
One or more instances(at least one)
Exactly n instances(n>1)
Zero or n instances(n>1)
One or n instances(n>1)
<<Class Module>>
main window
+1
+1
+1
<<Class Module>>
login window
+1
<<Class Module>>
welcome window
<<Class Module>>
login control
<<Class Module>>
error message
COMPONENT DIAGRAM:
In the Unified Modeling Language, a component diagram depicts how a software system is split up into
physical components and shows the dependencies among these components. Physical components could be, for
example, files, header, link libraries, modules, executables, or packages. Component diagrams can be used to model
and document any systems architecture.
Component diagrams are particularly useful with larger teams. Your initial architectural modeling efforts
during cycle 0 should focus on identifying the initial architectural landscape for your system. UML component
diagrams are great for doing this as they enable you to model the high-level software components, and more
8

importantly the interfaces to those components. Once the interfaces are defined, and agreed to by your team, it
makes it much easier to organize the development effort between sub teams. You will discover the need to evolve
the interfaces to reflect new requirements or changes to your design as your project progresses, changes that need to
be negotiated between the sub teams and then implemented appropriately.
<<ActiveX DLL>>
view courses
details
<<ActiveX DLL>>
login
<<ActiveX DLL>>
security
<<ActiveX DLL>>
registration
<<ActiveX DLL>>
validation
INTRODUCTION TO RATIONAL ROSE

Rational rose
Rational Rose is an object-oriented Unified Modeling Language(UML) software design tool intended for
visual modeling and component construction of enterprise-level software applications. In much the same way a
theatrical director blocks out a play, a software designer uses Rational rose to visually create(model) the framework
for an application by blocking out classes with actors(stick figures), use case elements(ovals), objects(rectangles)
and messages/relationships(arrows) in a sequence diagram using drag-and-drop symbols. Rational Rose documents
the diagram as it is being constructed and then generates code in the designers choice of C++, Visual Basic, Java,
Oracle8,CORBA or Data Definition Language.
Two popular features of Rational Rose are its ability to provide iterative development and round-trip
engineering. Rational Rose allows designers to take advantage of iterative development(sometimes called
evolutionary development) because the new application can be created in stages with the output of one iteration
becoming the input to the next.(This is in contrast to waterfall development where the whole project is completed
from start to finish before a user gets to try it out.) Then, as the developer begins to understand how the components
interact and makes modifications in the design, Rational Rose can perform what is called round-trip engineering
by going back and updating the rest of the model to ensure the code remains consistent.
Rational rose is extensible, with downloadable add-ins and third-party applications. It supports
COM/DCOM(ActiveX), JavaBeans, and Corba component standards.
Views in UML/Rational Rose
There are four views for a model created in Rational Rose, each representing the system from a different point of
view.
The Use Case View: The use case view contains the diagrams used in analysis(use case, sequence, and
collaboration), and all the elements that compromise these diagrams(e.g., actors).More recent versions of Rational
Rose also allow for additional documentation in the form of word-processed documents and/or URLs to Web-based
materials. The purpose of the use case view is to envisage what the system must do, without dealing with the
specifics of how it will be implemented.
Logical View: The logical view contains the diagrams used in object design(class diagrams and state transition
diagrams). It offers a detailed view of how the system envisaged in the use case view will be implemented. The
basic element in this view is the class, which includes an outline of its attributes and operations. This directly
corresponds to a class created in your chosen implementation language. From the logical view, skeletal code can be
generated for implementation into a computer language. More recent versions of Rational Rose not only can
9

generate skeletal code for Visual C++, Visual Java, or Visual BASIC, but also reverse engineer programs created in
these languages into Rational Rose models. This allows existing components to be included in documented models,
if there is access to the source code. In addition, changes that need to be made during implementation can be
reflected in the documentation of the design model.
Component View: The component view is a step up from the logical view and contains diagrams used in system
design(component diagrams). This includes information about the code libraries, executable programs, runtime
libraries, and other software components that comprise the completed systems. Components can be pre-existing; for
example, a Windows program in Visual C++ will utilize Microsoft Foundation Class to provide the framework for
the Windows interface. Components that do not exist and need to be created by the developers will have to be
designed in the logical view.
Deployment View: The deployment view illustrates how the completed system will be physically deployed. This
view is necessary for complex applications in which a system will have different components located on different
machines. For example, interface components may be located on a user machine while other components may be
located on a network server.
INTRODUCTION TO VISUAL BASIC
Visual Basic (VB) is an event driven programming language and associated development environment
from Microsoft for its COM programming model. Visual Basic was derived from BASIC and enables the rapid
application development(RAD) of graphical user interface(GUI) applications, access to databases using DAO, RDO,
or ADO, and creation of ActiveX controls and objects. Scripting languages such as VBA and VBScript are
syntactically similar to Visual Basic, but perform differently.
A programmer can put together an application using the components provided with Visual Basic itself.
Programs written in Visual Basic can also use the Windows API, but doing so requires external function
declarations.
LANGUAGE BASICS:
Visual Basic was designed to be easy to learn and use. The language not only allows programmers to create
simple GUI applications, but can also develop fairly complex applications as well. Programming in VB is a
combination of visually arranging components or controls on a form, specifying attributes and actions of those
components, and writing additional lines of code for more functionality. Since default attributes and actions are
defined for the components, a simple program can be created without the programmer having to write many lines of
code. Performance problems were experienced by earlier versions, but with faster computers and native code
compilation this has become less of an issue.
Forms are created using drag and drop techniques. A tool is used to place controls (e.g., text boxes, buttons,
etc.) on the form (window). Controls have attributes and event handlers associated with them. Default values are
provided when the control is created, but may be changed by the programmer. Many attribute values can be
modified during run time based on user actions or changes in the environment, providing a dynamic application. For
example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on
the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the
program can automatically translate the case of the text being entered, or even prevent certain characters from being
inserted.
Unlike many other programming languages, Visual Basic is generally not case sensitive, although it will
transform keywords into a standard case configuration and force the case of variable names to conform to the case of
the entry within the symbol table entry. String comparisons are case sensitive by the default, but can be made case
insensitive if so desired. The Visual Basic compiler is shared with other Visual Studio languages(C, C++), but
restrictions in the IDE do not allow the creation of some targets (Windows model DLLs) and threading models.
Result: Thus the UML diagrams and introduction to Visual Basic was studied.
EX.NO:2
DATE:
PASSPORT AUTOMATION SYSTEM
AIM:
To analyze and design a system for Passport Automation using Rational Rose tool.
1.
PROBLEM STATEMENT
10

To create a software system for the applicant(s), applying for the passport by verifying the information
provided by them.
2. OVERALL DESCRIPTION
The modules are for
1. Applicant
Applicant has to provide the information like Name, Gender, Age, Qualification,
Parents Name, Communication address, Phone no, etc. Also, they need to provide
the DD details.
2. Passport Issuing Authority
This system will verify the details provided by the applicant. And check whether the
applicant is provided with passport or not. The details of the applicant are stored in
the Database.
3. Database
This will store the details of the applicant for future reference.
2.1 SOFTWARE REQURIEMENTS
1.
Rational Rose
2.2 HARDWARE REQURIMENTS

1.
2.
3.
128MB RAM
Pentium III Processor
DESIGN
3.1 USE CASE DIAGRAM
applying for pas s prot
Applicant
Pas s port iss ue

authority
Is s ue applicant details
Verify the applicant details

Is sue Pas s port
Cancellation
DB
3.2 CLASS DIAGRAM
11
3.2 SEQUENCE DIAGRAM
3.3 COLLABORATION DIAGRAM

12
3.4 COMPONENET DIAGRAM
JAVA CODING:
Database.java
public class database
{
private int applicantDetails;
public database()
{ }
public void storeTheDetails()
{ }
public void issueDetailsToAuthortiy()
{ }
}
Applicant.java
public class APPLICANT
{
private int firstName;
private int surname;
private int Sex;
private int DOB;
13

private int placeOfBirth;
private int district;
private int qualification;
private int height;
private int weight;
private int presnetAddress;
private int permanentAddress;
private int fathersName;
private int mothersName;
private int emailId;
private int phoneNumber;
private int DDNO;
private int DDDATE;
public passportIssueAuthority thePassportIssueAuthority;
}
public APPLICANT()
{ }
PassportIssueAuthority.java
public class passportIssueAuthority
{
private int authorityName;
private int authorityId;
private int workPlace;
public APPLICANT theAPPLICANT;
public database theDatabase;
public passportIssueAuthority()
{}
public void issuePassport()
{ }
public void verify()
{ }
public void cancellation()
{}
}
RESULT:
Thus the UML diagrams for Passport Automation System was analyzed and designed using Rational Rose.
Ex.No: 3
Date :
14
BOOK BANK SYSTEM

AIM:
To analyze, design and develop code for Book Bank system using Rational Rose software.
PROBLEM STATEMENT
To create an Book Bank Maintenance System software that will meet the needs of the customer and help
them in registering for the book bank ,enquiry about the issue of book, return book and available books.
OVERALL DESCRIPTION
The Book Bank Maintenance System is an integrated system that has four modules as part of it. The four
modules are,
1) Registration for the new user:
In this module, the user can register as new user in the database.
2) Issue Book: In this module, it shows the details of issued book to the existing user and it shows the
available book to the particular user.
3) Return Book: In this module, shows and modify the database and store the return book from the user and
shows the fine amount.
SOFTWARE REQUIRMENTS
Microsoft Visual Basic 6.0

Rational Rose
Microsoft Access
HARDWARE REQUIRMENTS
128MB RAM
USECASE DIAGRAM
ENTER INTO SYSTEM
DATA BASE ADMIN

USER
NEWUSER
EXISTING USER
ISSUE
RETURN
CLASS DIAGRAM
15
STORE
DataBase
Book issue
Book Return
User information
Book Information
Main()
Validate user()
User
name
Regno
Available books
fine
Book Search
Book name
Author
Available books
Regno
New user()
Existing User()
Book Search()
ACTIVITY DIAGRAM
start
Login
No
New user
Registration
Yes
Existing
user
Book
search
Return
Book
Available
Books
Fine
Issue book
End
SEQUENCE DIAGRAM
16
user
system
data base
1: new user
2: save
3: existing user
4: retrieve
5: display information
6: issue
7: update
8: close
9: save
10: return
11: update
12: close
13: save
COLLABORATION DIAGRAM
1: new user
3: existing user
6: issue
8: close
10: return
12: close
system
user
5: display information
data
base
2: save
4: retrieve
7: update
9: save
11: update
13: save
COMPONENT DIAGRAM
17
BookSearch
User
Database
DEPLOYMENT DIAGRAM
Book
Bank
User
Access
Database
IMPLEMENTATION
Form1
Private Sub Command1_Click()

Dim a As Boolean
a = False
If (Text1.Text = "admin" And Text2.Text = "admin") Then
a = True
Form2.Show
Unload Me
End If
If (a = False) Then
MsgBox ("Enter Correct Username and Password")
End If
End Sub
Form2
Form3.Show
Unload Me
End Sub
Form4.Show
Unload Me
End Sub
Form5.Show
Unload Me
End Sub
18

Form6.Show
Unload Me
End Sub
Unload Me
End Sub
Form3

Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
cn.Open "dsn=BookBank"
rs.ActiveConnection = cn
With rs
.CursorType = adOpenStatic
.CursorLocation = adUseClient
.LockType = adLockOptimistic
.Open "select * from Students"
End With
With rs
.AddNew
.Fields(0) = Val(Text1.Text)
.Fields(1) = Text2.Text
.Update
19

End With
Text1.Text = ""
End Sub
Form2.Show
Unload Me
End Sub
Form4

Dim rs As New ADODB.Recordset
rs.ActiveConnection = cn
With rs
.Open "select * from Books"
End With
With rs
.AddNew
.Fields(1) = Text2.Text
.Update
End With
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
End Sub
Form2.Show
Unload Me
End Sub
Form5
20

Dim rs1 As New ADODB.Recordset
Dim a As Boolean
Dim b As Boolean
a = False
b = False
rs1.ActiveConnection = cn
With rs1
End With
With rs2
End With
rs1.MoveFirst
While Not rs1.EOF
If (Val(Text1.Text) = rs1(0)) Then
a = True
rs2.MoveFirst
While Not rs2.EOF
b = True
If (rs2(2) > 0) Then
rs2(2) = rs2(2) - 1
rs2.Update
MsgBox "Book is Issued"
Else
MsgBox "No copies of books is avilable"
End If
End If
rs2.MoveNext
Wend
End If
rs1.MoveNext
21

Wend
Text1.Text = ""
Text2.Text = ""
If (a = False) Then
MsgBox ("Enter correct Student ID")
End If
If (a = True And b = False) Then
MsgBox ("Enter correct Book ID")
End If
End Sub
Dim a As Boolean
Dim b As Boolean
a = False
b = False
With rs1
End With
With rs2
End With
rs1.MoveFirst
While Not rs1.EOF
a = True
rs2.MoveFirst
While Not rs2.EOF
b = True
If (rs2(2) > 10) Then
MsgBox "Book is Renewed"
Else
MsgBox "Please return the Book."
End If
End If
rs2.MoveNext
Wend
End If
rs1.MoveNext
Wend
22

Text1.Text = ""
Text2.Text = ""
If (a = False) Then
End If
End If
End Sub
Form2.Show
Unload Me
End Sub
Form6

Dim a As Boolean
Dim b As Boolean
a = False
b = False
With rs1
End With
With rs2
End With
23
rs1.MoveFirst
While Not rs1.EOF
a = True
rs2.MoveFirst
While Not rs2.EOF
b = True
rs2(2) = rs2(2) + 1
MsgBox ("Book is Returned")
End If
rs2.MoveNext
Wend
End If
rs1.MoveNext
Text1.Text = ""
Text2.Text = ""
Wend
If (a = False) Then
End If
End If
End Sub
Form2.Show
Unload Me
End Sub
CONCLUSION:
This project was carried out in a sequential manner to design and implement the Book Bank System.
Thus the outcome of the project is efficient. The Book Bank System caters the varied requirements of the user to
perform various options.
Ex. NO: 4
DATE :
EXAM REGISTRATION SYSTEM
AIM:
To analyze and design a system for Exam registration using Rational Rose tool.
1.
PROBLEM STATEMENT
24

To create an Exam registration software that will meet the needs of the applicant and help them in
registering for the exam ,enquiry about the registered subject ,modification in database and cancellation for
the registered project.
2.
OVERALL DESCRIPTION
The Exam Registration System is an integrated system that has four modules as part of it.the four
modules are
1. Registration for the exam
In this module, the user can select the subject to register for the exam, Enquiry
about the registered subject, Modification in the student database, canceling the
registered subject
2. Form for Registration
In this module the user can apply for the exam by giving the details about the
candidate and selecting the subject for the registration.
3. Modification in the Database
In this module the user can change the datas like the phone number, address can
be done.
4. Cancellation for the registered subject
In this module the user can cancel their name which is registered for the exam.
1. Rational Rose
1.128MB RAM
2. Pentium III Processor
USE CASE DIAGRAM:
register for exam
student
(from use case)
(from actor)
databse
(from actor)
select the exam

(from use case)
cancel the exam registration

enter datas
(from use case)
(from use case)
maintain student info

modify databse
(from use case)
(from use case)
ACTIVITY DIAGRAM:
25
enter into
system
cancel
regisrtation
select the
subject
apply the exam
modify databse
DEPLOYMENT DIAGRAM
exam
registration
student
Databse
CLASS DIAGRAM:
student
name
id
address
phone number
subject name
exam database
id
name
address
phone number
subject
select the subject()

apply()
cancel()
modify()
update()
modify()
select()
display id()
database
if
name
phone no
subject
display registartion()
display subject()
update()
SEQUENCE DIAGRAM:
26
student
database
examregistratio
n
1: enter the data
2: select the subject
3: apply for the exam

5: generation fo registration id
6: note id
7: modify databse
8: cancel the subject registration
COLLABRATION DIAGRAM:
1: enter the data
2: select the subject
student
examregist
ration
6: note id
7: modify databse
8: cancel the subject registration
5: generation fo registration id
databas
e
COMPONENT DIAGRAM
student
exam
registration
Databse
JAVA CODING:
Student.java
public class student
27
{
private int name;

private int id;
private int address;
private int phoneNumber;
private int subjectName;
public examdatabase theExamdatabase;
public student()
{ }
public void selectthesubject()
{ }
public void apply()
{ }
public void cancel()
{ }
public void modify()
{ }
}
Examdatabase.java
public class examdatabase
{
private int id;
private int name;
private int phhonenumber;
private int subject;
public database2 theDatabase;
public examdatabase()
{ }
public void update()
{ }
public void modify()
{ }
public void select()
{ }
public void display()
{ }
}
Database.java:
{
private int id;
private int name;
private int phoneno;
private int subject;
public studentex theStudent;
public database()
{ }
public void displayregistration()
{ }
public void displaysubject()
{ }
{ }
}
void database.calculate(){
}
void database.resultdisplay(){
}
RESULT:
Thus the UML diagrams for Exam Registration was analyzed and designed using Rational Rose.
STOCK MAINTENANCE SYSTEM

Ex. No: 5
Date:
AIM:
To analyze and design a system for Stock Maintenance System using Rational Rose tool.
28

Problem Statement:
INVENTORY SYSTEM is a real time application used in the merchants day to day system. This
is a database to store the transaction that takes places between the Manufacturer, Dealer and the Shop Keeper that
includes stock inward and stock outward with reference to the dealer. Here we assume our self as the Dealer and
proceed with the transaction as follows:
The Manufacturer is the producer of the items and it contains the necessary information of the
item such as price per item, Date of manufacture, best before use, Number of Item available and their Company
Address.
The Dealer is the secondary source of an Item and he purchases Item from the manufacturer by
requesting the required Item with its corresponding Company Name and the Number of Items required. The Dealer
is only responsible for distribution of the Item to the Retailers in the Town or City.
The Shop Keeper or Retailer is the one who is prime source for selling items in the market. The customers get
Item from the Shop Keeper and not directly from the Manufacturer or the Dealer. The Stock is the database used in
our System which records all transactions that takes place between the Manufacturer and the Dealer and the Dealer
and the Retailer.
USE CASE DIAGRAM :
Sales
Purchase
Company name
Company name
DEALER
Price/item
PRODUCER
SHOP KEEPER
Price/Item
Items ordered
Items ordered
Total price
Total price
COMPONENT DIAGRAM :
MANUFA
CTURER
DEALER
DATABASE
ACTIVITY DIAGRAM :
29
SHOPKE
EPER
Inventory
System
Select from
the Menu
Purchase
Sales
Stock
Exit
Display the
Transaction Det ails
Company
Name
Price/Item
No of Items
ordered
If Availability > No of
Items Ordered
Total Price
Displays Insufficient
no of items
Displays price
of Items
SEQUENCE DIAGRAM :
PRODUCER
DEALER
SHOPKEEPER
1.P URCHASE
1.S ALES
2.COMPANY NA ME
2.COMPANY NAME
3.P RICE/ITEM
3.PRICE/ITEM
4.NO OF ITE MS ORDERE D
4.NO OF ITE MS ORDERE D
5.TOTAL PRICE
5.CHECKING W ITH AVAILABILITY
6.ITEMS INSUFFICIENT/TOTAL PRICE
COLLABORATION DIAGRAM :
30
5: 3.PRICE/ITEM
9: 5.TOTAL PRICE
PRODUC
ER
DEALER
1: 1.PURCHASE
3: 2.COMPANY NAME
7: 4.NO OF ITEMS ORDERED
4: 2.COMPANY NAME
8: 4.NO OF ITEMS ORDERED
10: 5.CHECKING WITH AVAILABILITY
2: 1.SALES
6: 3.PRICE/ITEM
11: 6.ITEMS INSUFFICIENT/TOTAL PRICE
SHOPKEE
PER
CLASS DIAGRAM :
MANUFACTURER
Manufacturer Name
Company Name
Date of Manufactured
Address
Contact Number
Price
Purchase()
Sales()
DEELER
Dealer Name
Date of Items Received
Address
Contact Number
Price
No of Items Ordered
No of Items Sold
Purchase()
Sales()
Show stock Details()
SHOPKEEPER
ShopKeeper Name
Address
Contact Number
Price
No of Items Ordered
Purchase()
Sales()
DEPLOYMENT DIAGRAM :
Process
or
Printer
Mouse
Keyboar
d
Javacoding:
31
Manufacturer.java
public manufacturer theManufacturer;

public shopkeeper theShopkeeper;
public class manufacturer

{
private int manufacturername;
private int companyname;
private int dateofmanufactured;
private int addres;
private int contactno;
private int name;
public dealer theDealer;
public dealer()
{ }
public void purchase()
{ }
public void sales()
{ }
public void showstockdetails()
{ }}
public manufacturer()
{ }
{ }
public void sales()
{ }
}
Dealer.java
public class dealer
{
private int dealername;
private int dateofitemsreceived;
private int contactnumber;
private int price;
private int noofitemsordered;
private int noofitemssold;
Shopkeeper.java
public class shopkeeper
{
private int shopkeepername;
private int contactnumber;
private int price;
private int numberofitemsordered;
public dealer theDealer;
public shopkeeper()
{ }
{ }
public void sales()
{ }}
RESULT:
Thus the UML diagrams for Stock Maintenance was analyzed and designed using Rational Rose.
Ex No: 6
Date:
ONLINE COURSE REGISTRATION SYSTEM
32
AIM:
To create a system through which students can register to the courses desired by them, using Rational Rose
tool.
Problem statement
The system is built to be used by students and managed by an administrator.

The student and employee have to login to the system before any processing can be done.
The student can see the courses available to him and register to the course he wants.
The administrator can maintain the course details and view all the students who have registered to any
course.
System requirements
Rational Rose Software
Use-case diagram
The course registration system has the following use-cases
Login
View course details
Registration
Display details
Maintain course details
Logout
The actors involved in the system are
1.
2.
Student
Administrator
Use-case name: Login

The user enters the username and password and chooses if the user is
student or administrator. If entered details are valid, the users account becomes
available. If it is invalid, an appropriate message is displayed to the user.
Use-case name: View course details
In this use case, a student can search all the courses available to him and choose
the best course he wants. The student can view the course duration, faculty and
department of the courses he may choose.
Use-case name: Registration
When a student has successfully chosen a course, he can register to that course.
Upon registration, the students details are stored in the database.
Use-case name: Display details
After registration to any course, the student may see the details of his current course.
He may wish to know details about fees and other information. The administrator also has
the privilege to display details of the the students and the corresponding course for which
they have registered.
Use-case name: Maintain course details
The administrator has to perform the duties of maintaining the course details.
Any change to the course structure is maintained by the administrator.
Use-case name: Logout
After all the desired transactions are made, the user may choose to logout
33

from the system to save all he changes they have made.
Use-case diagram for course registration system
Class diagram
The class diagram is a graphical representation of all the classes used in the
system and their operations, attributes and relationships.
The course registration system makes use of the following classes:
1.
2.
Stud(student details)
Administrator
1) Stud
It consists of the details of all the students present in the database. The
attributes present in this class are student id, password, name, age, sex,
course and attendance. The object of this class is created as soon as the
student registers to a course. The operations available to this class are
login (), logout (), confirmation (), register (), and view course details ().
2) Administrator
It consists of details of all the courses available to the student. The
attributes present in this class are username, password, course fees,
fees due, marks, and attendance. The operations available to this class
are login (), logout (), ma course details (), display course (), and
confirmation ().
Class diagram for course registration system
34
Sequence diagram
Sequence and collaboration diagram for login to the system
Sequence and collabaration diagram for logout

35
Sequence and collabaration diagram for registration to a course
ACTIVITY DIAGRAM :
36
login
view the
course
register
display
logout
JAVA CODE:
Public class stud
{
Private int sid;
Private string passwd;
Private int age;
Private int sex;
Public admin;
Public stud()
{
}
Public void logout()
{
}
Public void confirm()
{
}
RESULT:
Thus the Online course registration system was designed and analyzed using Rational Rose.
37
Ex No: 7
Date:
ONLINE TICKET RESERVATION SYSTEM
38

(E Ticketing)
AIM:
To analyze and design a system for Online Ticket Reservation System (E Ticket) using Rational Rose tool.
1.
PROBLEM STATEMENT
To book a ticket for a user online ticket reservation system software and to confirm the ticket booking,
making the payment, printing the tickets has to designed using Rational Rose tool.
2.
OVERALL DESCRIPTION
1. LOGIN
Before entering the system, users have to login
Get the username and password from existing users.
Give new users the option to sign up.
2. AVAILABILITY
Get the source and destination.
Provide a dropdown box for the date.
Check availability of tickets.
3. RESCHEDULE
If tickets are available, get the number of passengers.
Get the name and age of all passengers.
If tickets are not available, reschedule.
4. PAYMENT DETAILS
Print the cost of the tickets.

Get the payment details from the user.
Confirm the details and the ticket.
Display confirmed ticket to the user.
USECASE DIAGRAM
Choose source, destination
Check availability
Customer
Booking Server
Enter details
Request booking
Make payment
Bank System
Confirm booking
ACTIVITY DIAGRAM
39
Display
availability
Get booking
request
Display
payment details
Get user's
payment details
No
If complete
Print ticket
CLASS DIAGRAM
CustomerDetails
Name
Address
Email
Age
book()
Booking
Booking_no
Date
Total
Status
name
Pay()
2: Yes
1: Check availability
4: Enter information
Customer
Server
3: If no, reschedule
5: Reconfirm booking
8: Get ticket
7: Confirm payment
6: Payment
Bank
SEQUENCE DIAGRAM
40
Payment
Date
Amount
Customer
Server
Bank
Check availability
Yes
If no, reschedule
Enter information
Reconfirm booking
Payment
Confirm payment
Get ticket
STATE CHART DIAGRAM

Displaying
availability
Request
booking
Check availability
Displaying
payment details
User's payment
details
Print Ticket
COMPONENT DIAGRAM
41
Bank
Online
Booking Server
Customer
DEPLOYMENT DIAGRAM
Server Update
Railway
Database
User PC
Javacoding:
Customerdetails.java
public class customerdetails
{
private int name;
private int email;
private int age;
public booking theBooking;
public customerdetails()
{
}
42

public void book()
{
}
}
Booking.java
public class booking
{
private int booking_no;
private int date;
private int total;
private int status;
private int name;
public payment thePayment;
public booking()
{
}
public void pay()
{
}
}
Payment.java
public class payment
{
private int date;
private int amount;
public payment()
{
}
}
RESULT:
Thus the Online Ticket Reservation System have been designed and verified using Rational Rose Tool.
43
Ex No:8
Date:
SOFTWARE PERSONNEL MANAGEMENT SYSTEM
AIM:
To analyze and design a system for Software Personnel Management System using Rational Rose tool.
44
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 Rational Rose tool.
The three modules are
1.
Login
The employee details has to be entered and if needed the details
can be edited.
2. Pay slip
It contains details such as employee id, employee name, department, experience, and
basic pay.
3.View
Updated database would be present. The details of the employee can be used for
further reference.
2.1 SOFTWARE REQURIEMENTS:
1. Rational Rose
2.2 HARDWARE REQURIMENTS:
4.
5.
128MB RAM
3. DESIGN
USECASE DIAGRAM
CLASS DIAGRAM
45
SEQUENCE DIAGRAM
46
SEQUENCE DIAGRAM
ACTIVITY DIAGRAM
47
JAVA CODING:
PAYROLLLOGIN.JAVA
public class payrolllogin
{
private int enterdetails;
private int editdetails;
public payslip thePayslip;
public viewdetails theViewdetails;
public payrolllogin()
{
}
public void exit()
{
}
}
VIEWDETAILS.JAVA
public class viewdetails
{
private int eid;
private int ename;
private int dept;
private int exp;
48

private int basicpay;
private int hra;
private int da;
private int bpf;
private int gpay;
public viewdetails()
{
}
public void view()
{
}
public void exit()
{
}
}
PAYSLIP.JAVA
public class payslip
{
private int name;
private int eid;
private int department;
private int experience;
private int basicPay;
private int har;
private int da;
private int bpf;
private int gpay;
public payslip()
{
}
public void delete()
{
}
public void new1()
{
}
public void save()
{
}
public void calculate()
{
}
public void exit()
{
}
}
RESULT:
Thus the Software personnel management system was designed and analyzed using Rational Rose.
49
Ex No:9
Date:
CREDIT CARD PROCESSING
AIM
50

To analyze, design and develop code for Credit Card Processing System using Rational Rose software
PROBLEM STATEMENT
We envision a banking system that provides the customer holing a bank credit card can make deposits,
withdraws, check balances and perform transfer to and from their accounts. Credit card processing will be attractive
to banking customer because they allow access to their accounts outside of regular business hours.
Participating Banks want to make sure the access to their customer account information is safe and
secure transaction information is accurate and reliable. Bank Customer-Want easy, low-cost, remote access to their
accounts, but want to be assured that their accounts are secure and not accessible to hackers or other their parties.
Bank must be able to handle multiple simultaneous transactions (and possible simultaneous transaction
to the same joint account).Bank owning a credit card must be able to determine the cash on hand in the creditcard.
The cash in the creditcard must be secure.
OVERALL DESCRIPTION
The Credit Card Processing System is an integrated system that has four modules as part of it. The four
modules are,
1) User Login: Using this module user login to the system using his/her unique username and password
2) Withdraw: The purpose of this module to withdraw money from the account
3) Deposit: The purpose of this module to deposit money to the account
4) Balance Enquiry: Using this module the user can check his/her account balance and the loan amount to pay
if any.
Microsoft Visual Basic 6.0

Rational Rose
Microsoft Access
128MB RAM
USE CASE DIAGRAM
Login
Transaction
Customer
Deposit
Withdraw
Bank Database
Balance Enquiry
CLASS DIAGRAM
51
bank
balance
accountNo
FinancialAccount
report
+theFinancialAccount
getavaliableReport()
FinancialAccount()
getBalance()
buyersAccount()
bank()
systemSecurity
key
+theSystemSecurity
+theReportingSystem
ReportingSystem
report
key
getsystemClerance()
systemSecurity()
avaliableReport()
ReportingSystem()
ACTIVITY DIAGRAM
Login
Withdraw
Deposit
Balnce Enquiry
Logout
SEQUENCE DIAGRAM
52
Customer
Credit System
Bank Database
Login
Validate Details
Validation Success
Login Success
Transaction
Validate Transaction
Transaction Validated
Transaction Success
Pin Change
Update Details
Details Updated
Pin Change Success
COLLABRATION DIAGRAM
1: Login
5: Transaction
9: Pin Change
Customer
Credit
System
4: Login Success
8: Transaction Success
12: Pin Change Success
3: Validation Success
7: Transaction Validated
11: Details Updated
2: Validate Details
6: Validate Transaction
10: Update Details
Bank
Database
COMPONENT DIAGRAM
53
Customer
Credit
Card
Databas
e
Bank
DEPLOYMENT DIAGRAM
Customer
Credit Card
Processi...
Access
Database
JAVA CODE :
Bank.java
private int report;

private int key;
public systemSecurity theSystemSecurity;
public class bank

{
private int balance;
private int accountNo;
public FinancialAccount theFinancialAccount;
public bank()
{ }
public void getBalance()
{ }
public void buyersAccount()
{ }
public ReportingSystem()
{ }
public void avaliableReport()
{ }
}
SystemSecurity.java
public class systemSecurity
{
private int key;
public systemSecurity()
{ }
ReportingSystem.java
public class ReportingSystem
{
public void getsystemClerance()

{ }
}
RESULT:
Thus the credit card system was designed and analyzed using Rational Rose.
Ex.no: 10
Date:
54

E-BOOK MANAGEMENT SYSTEM
AIM:
To analyze and design a system for E - Book Management System using Rational Rose tool.
1. PROBLEM STATEMENT
To maintain and find the required e book(s). The 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.
The four modules are
1. Login
The user has to be enter his/her login details and if needed the details
can be edited.
2. Select E - book
It contains the list of e-book(s) available along with the search option.
3. Search Topic:
Choose the required topic and double click on it. Then the page
with the contents of the selected topic will be displayed
4. Update
The database can be updated with new arrived e - book in the future.
USE-CASE DIAGRAM:
SELECT TOPIC
DISPLAY TABLE CONTENTS
USER
SYSTEM
SEARCH FOR TOPIC
DISPLAY THE INFORMATION
EXIT
ACTIVITY DIAGRAM:
55
START
SELCET
E-BOOK
CHOOSE
MAIN TOPIC
SELECT SUB-TOPIC
(1 TO n)
STOP
SEQUENCE DIAGRAM:
USER
SYSTEM
SELECT TOPIC
DISPLAY TABLE CONTENTS
SEARCH FOR TOPIC
DISPLAY INFORMATION
EXIT
COLLABORATION DIAGRAM:
56
1: SELECT TOPIC
3: SEARCH FOR TOPIC
5: EXIT
USER
SYSTEM
2: DISPLAY TABLE CONTENTS

4: DISPLAY INFORMATION
DEPLOYMENT DIAGRAM:
CPU
KEY
BOARD
PRINTER
MOUSE
Javacoding:
System.java
public class system
{
private int info;
public system()
{
}
{
}
}
User.java
57
public class user

{
private int name;
private int topic;
public system theSystem;
public user()
{
}
public void search()
{
}
public void exit()
{
}
}
RESULT:
Thus the E Book management system was designed and analyzed using Rational Rose.
EX.NO:11
Date:
RECRUITMENT SYSTEM
AIM:
To analyze and design a system for Recruitment using Rational Rose tool.
58
1. PROBLEM STATEMENT
To create a software system this can test the skills of the candidate by generating random question and
answer.
The three modules are
1. Login
User can login using the username and password and they can start attend the test for
the specified vacancy
2. Recruitment test
This system will generate random question to test the skills of the Candidate and
check whether the candidate is suitable for the position offered by the company.
3. Result
This will show whether the candidate is selected or not selected for the position by
displaying the message.
2.1 SOFTWARE REQURIEMENTS
1. Rational Rose
2.2 HARDWARE REQURIMENTS
1. 128MB RAM
2. Pentium III Processor
3. DESIGN
3.1 USE CASE DIAGRAM
login
(from usecase m odel)
candidate
(from usecase model)
database
view the questions
attend the test

display result
3.2 ACTIVITY DIAGRAM
59
(from usecase m odel)
login
invalid user
answer the
question
get the result
3.3 CLASS DIAGRAM

databse
question
score
id
candidate
login
password
name2
display()
calculate()
result display()
attend()
result()
recruitment test
question
display question()
submit the answer()
display msg()
3.4 COMPONENET DIAGRAM

candidat
e
recruitment
system
database
3.5 COLLABORATION DIAGRAM

60
1: enter by login and password

6: answer all the questions
candidat
e
recritment
system
5: display questions
9: display message
2: verify login
3: request for questions for the test
7: verify the answer
4: send question
8: display
for test result
Databas
e
3.6 SEQUENCE DIAGRAM

candidate
recritment
system
Database
enter by login and password

verify login
request for questions for the test
send question for test

display questions
answer all the questions

verify the answer
display result
display message
3.7 DEPLOYMENT DIAGRAM

61
DATAB
SE
CANDID
ATE
RECRUI
TME...
JAVA CODING:
Candiate.java
public class candiate

{
private int login;
private int password;
private int name2;
public recruitmentTest theRecruitmentTest;
public void calculate()

{
}
public void resultDisplay()
{
public candiate()
{
}
}
public void attend()

{
}
RecruitmentTest.java
public class recruitmentTest
{
private int question;
public dataBase theDataBase;
public void result()

{
public recruitmentTest()
{
}
}
DataBase.java
public class dataBase
{
private int question;
private int score;
private int id;
}
public void displayQuestionj()
{ }
public void submitTheAnswer()
{
}
public dataBase()
{
}
{
public void displayMessage()

{
}
}
RESULT:
Thus the UML diagrams for Recruitment System was analyzed and designed using Rational Rose.
Ex. No: 12
Date:
62
Foreign Trading System


AIM:
To analyze and design a system for Foreign Trading System using Rational Rose tool.
1.
PROBLEM STATEMENT
This project emphasizes about the Foreign Trade System which is an interface between the Account
holder and the market.
2.
MODULES AND DESCRIPTION
Login:
The Login module contains the form which contain membership name and member password.
It includes Username and Password.
Trading Account Details:
This form contains the information about account holder, market status, currency held, trading histories,
etc.
Buy:
After the user logged in they can buy stocks online the user can buy stock only
it is available for buying.
Sell:
After the user logged in they can sell stocks online , the user can sell his own
stocks only
Bank Account Database:
After the trading is finished user has to select the type of transaction whether credit card Demat account.
1. Rational Rose
3.
USECASE DIAGRAM
browse for products
request for price
customer
product seller
product selection
request for bill

system
administration
issue bill
4.
CLASS DIAGRAM
63
Customer
id
address
phone_no
products
total_price
pay_mode
Productseller
id
address
phone_no
product_list
cost_of_item
add_to_cart()
remove_from_cart()
req_for_bill()
make_payment()
generate_bill()
systemadministrator
total_cost
list_of_items
generate_total_bill()
5.
SEQUENCE DIAGRAM
customer
productseller
system
administrator
request for products list

issue list with price
request for particular product
bill for requested product
issue bill
generate seller's bill copy
generate customer's bill copy
6.
COLLOBORATION DIAGRAM
1: request for products list
3: request for particular product
custome
r
products
eller
2: issue list with price
5: issue bill
6: generate seller's bill copy
7: generate customer's bill copy
4: bill for requested product
system
administrator
7.
STATECHART DIAGRAM
64
product
request
product
selection
product
deselection
request for
bill
bill
generation
bill issue
8.
9.
COMPONENT DIAGRAM
ACTIVITY DIAGRAM
product
request
product
selection
product
deselection
request for
bill
bill
generation
bill issue
10. DEPLOYMENT DIAGRAM

65
CPU
KEY
BOARD
PRINTER
MOUSE
JAVA CODING:
Customer.java
public class customer
{
private int id;
private int phone_no;
private int products;
private int total_price;
private int pay_mode;
public product seller the productseller;
public systemadministration the
systemadministration;
public customer()
{
}
public void add_to_cart()
{
}
public void remove_from_cart()
{
}
public void req_for_bill()
{
}
public void make_payment()
{
}
}
Productseller.java
public class productseller
{
private int id;
private int phone_no;
private int product_list;
private int cost_of_item;
public customer thecustomer;
public systemadministration the
systemadministration;
public productseller()
{
}
public void generateBill()
{
}
}
SystemAdministration.java
public class systemadministration
{
private int total_cost;
private int list_of_items;
public customer thecustomer;
public productseller theproductseller;
public system administration()
{
}
public void generate_total_bill()
{
}
}
Result:
Thus the Foreign Trading system was designed and analyzed using Rational Rose.
Ex No: 13
Date:
66

CONFERENCE MANAGEMENT SYSTEM
AIM:
To analyze and design a system for Conference Management System using Rational Rose tool.
1.
PROBLEM STATEMENT:
This project deals with the conference management system. As a students or staff members are required to
view the details of conference is going to conduct in various colleges or institutions and to attend the conference to
gain knowledge from the conferences.
Administrator will add the details about the various conferences
available to attend for various department students and staff members.
2. OVERALL DESCRIPTION:
1. Login:
Authenticate the user and administrator.
2. Department Selection:
This form will give the options for selecting the department to get knowledge about the
conference.
3.Conference view:
This form contains the details about the conferences is conducting by various institutions and we
can see the date and time for the conference.
4. Database:
The details about the conferences going to conduct by various institutions. Administrator can add
the details about the conference for the students and also for the staff members.
Rational Rose
2.2 HARDWARE REQURIMENTS:
1.
2.
128MB RAM
3. USE CASE DIAGRAM:
login
(from use case)
admin
user
(from actor)
(from actor)
enquriy
(from use case)
view details
(from use case)
add details
(from use case)
4. ACTIVITY DIAGRAM:
67
enter the id
select
department
exit
view the details
5. CLASS DIAGRAM:
administrator
admin_pass : variant
user
pass : variant
depat : variant
validate_pass()
add details()
view detals()
view the details()
6. SEQUENCE DIAGRAM:
USER
DEPARTMENT
ADMINISTRAT
OR
DATABASE
Enter the username and password

Verify password
Ok
display the selection of department
select the department
verify the department
verify
ok
ok
view the details
7. COLLABORATION DIAGRAM:
68
5: select the department

USER
DEPART
MENT
1: Enter the username and password

10: view the details
9:
6: ok
verify the department
4: display the selection of department
3: Ok
8: ok
DATABA
SE
ADMINIST
RATOR
2: Verify password
7: verify
8. COMPONENT DIAGRAM:
Admin
Database
Display
Student
9. DEPLOYMENT DIAGRAM:
databas
e
admin
user
Javacodings:
69
display
Administrator.java
public class administrator
{
private variant admin_pass;
public administrator()
{
}
public void validate_pass()
{
}
public void adddetails()
{
}
public void viewdetails()
{
}
}
User.java
public class user
{
private variant pass;
private variant depat;
public Administrator;
public user()
{
}
public void viewthedetails()
{
}
}
Result:
Thus the Conference management system was designed and analyzed using Rational Rose.
Ex No: 14
Date:
BPO MANAGEMENT SYSTEM
AIM:
To analyze and design a system for BPO Management System using Rational Rose tool.
70
PROBLEM STATEMENT:
The objective is to develop a software for BPO management system. Business process outsourcing (BPO) is a
subset of outsourcing that involves the contracting of the operations and responsibilities of specific business
functions (or processes) to a third-party service provider. BPO management system is used to effectively manage the
business activities of a BPO organisation. This system adopts a comprehensive approach to minimize the manual
work and schedule resources, time in a cogent manner. It is designed for hiring any company, that is, it is generalised
system for business process management. The core of the system is to maintain employee details and customer
details and company details.
1.ANALYSIS
1.1 Identifying the actors
1.2 Identifying the use cases
2.DESIGN
2.1 Use Case Diagram
2.2 Class Diagram
2.3 Sequence diagram
2.4 Collaboration Diagram
2.5 Activity Diagram
2.6 State Diagram
UML USE-CASE DIAGRAM
Attend the call

Customer
Customer details
BPOAgent
Service provided
Canvashing the customer
Interface
Get the feedback
Report the feedback
Update
Quit the call
UML CLASS DIAGRAM
71
Admin
BPOAgent
s erviceProvider
canvas hingTheCustomer
attendingTheCall()
reportingFeedback()
Cus tom er
(f rom Us e Case View)
Admin
cus tomerDetails
requirements
Bpo Services
(f rom Use Case View)
canvas h
interface
cus tomerDetails
update()
faultDetails ()
givingFeedback()
Cus tom er()
provide services to cus tomer()
UML SEQUENCE DIAGRAM

BPO agent
Admin
Customer
Bpo services
reporting feedback
Providing the services
canvashin the customer

providing details
interface with customer

providing fault details
UML COMMUNICATION DIAGRAM

1: reporting feedback
BPO
agent
Adm in
4: providing details
2: Providing the s ervices

7: providing fault details
5:
Cus tom e
r
Bpo
s ervices
3: canvas hin the cus tom er

6: interface with cus tom er
UML STATE CHART DIAGRAM

72
providing service to
customer
services of
bpo agents
canvashing the
customer
customer receiving
the services
getting feedback
from customers
reporting feedback
to admin
interface with
customer
UML ACTIVITY DIAGRAM
bpo agent
s ervices
s ervice provided to
cus tomer
providing
s olutions ...
canvas hing by
bpo agents
interfacing with
customers
To buy new
product
providing and getting

inform ation ab...
s ervice received by
cus tomer
getting
feedbacks
update feedback
to admin
UML COMPONENT DIAGRAM
73
BPO
agent
Admin
providing and
updating the
details
provide
s ervices ,interface
and canvas hing the
customer
cus tomer
providing
requirements
and fault details
UML DEPLOYMENT DIAGRAM
telecommunicat
ion device
BPO agent
provide
services,interf
ace ...
Admin
Customer
providing
requireme...
providing and
updating ...
JAVA CODING:
BPOAgent.java
public class BPOAgent
{
private int ServiceProvider;
private int CanvasingTheCustomer;
public BPOAgent()
{
}
public void AttendingTheCall()
{
}
74

public void ReportingFeedback()
{
}
BPOServices.java
public class BPOServices extends BPOAgent
{
private int Canvash;
private int Interface;
public BPOServices()
{
}
public void ProvideServicesToCustomer()
{
}
}
admin.java
public class admin extends BPOAgent
{
private int CustomerDetails;
public admin()
{
}
public void Update()
{
}
}
customer.java
public class customer extends BPOAgent
{
private int CustomerDetails;
private int Requirements;
public customer()
{
}
public void FaultDetails()
{
}
public void GivingFeedback()
{
}
}
RESULT:
Thus the BPO Management System was designed and analyzed using rational Rose.
75
Ex. No. 15
Date:
LIBRARY MANAGEMENT SYSTEM
AIM
To develop a model for Library management systems using Rational Rose Software tool
76

PURPOSE
The purpose of Library Management system is to provide a medium for the public libraries to computerize their
entire functioning and would contribute as a first step in digitalizing their libraries. The system would provide basic
set of features to add/update members, add/update books and manage check in specifications for the systems based
on the clients statement of need.
USECASE DIAGRAM
Use cases represent typical set of scenarios that help to structure, relate and understand the essential requirement. A
use case diagram is a diagram that help system analyst to discover the requirement of target system from the users
perspective. Use case diagram can be used to describe the functionality of system in horizontal way. Usecase
diagram are used to represent functionality of the system from a top down perspective.
ACTIVITY DIAGRAM
Activity diagram is one of the important uml diagram which describes the flow of activity in system. Activity
diagram is basically a flowchart which shows connection between one activity of system to another activity. Before
drawing activity diagram you should list activity of user and connection between both activity. Activity diagram of
library management system may defer according to users such as administrator, customer etc.
77
CLASS DIAGRAM
In uml class diagram describes the structure of system by showing the system classes, attributes, methods, and
associations between classes.
SEQUENCE DIAGRAM
Sequence diagram descries interaction among classes in terms of an exchange of message over time. Sequence
diagram demonstrate the behavior of objects in a use case by describing the object and messages they pass. A
sequence diagram depicts the sequence of actions that occurs in system.
78
Collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects that send
receive message. A collaboration diagram is very similar to sequence diagram. Collaboration diagram shows the
objects and their association with other objects. Modeling objects in a system and representing the association
between the object as links are easily represented in a collaboration diagram.
COMPONENT DIAGRAM
Component diagram are one of the two kind of diagram found in modeling the physical aspects of object oriented
system. A component diagram shows the organization and inter relationship between a set of component. We use
component diagram to visualize the static aspect of the physical component and their relationship and to specify
their details for construction. Component diagram is essentially class diagram that focus on a systems component.
79
Java Code
Student.java
public class student
{
private int s_name;
private int s_id;
private int s_dept;
public librarian thelibrarian;
public student()
{
}
public void borrowbook()
{
}
public void returnbook()
{
}
}
Librarian.java
public class librarian
{
private int l_id;
private int l_name;
private int s_doj;
public database thedatabase;
public supplier thesupplier;
public librarian()
{ }
public void issuebook()
{
}
public void checkid()
{
}
public void grantpermission()
{
}
public void updateddb()
{
}
public void addbook()
{
}}
Supplier.java
public class supplier
{
private int s_id;
private int s_name;
public supplier()
{
}
public void search()
{
}
public void tellavailability()
{
}
public void opname()
{}
}
Database.java
{
private int filename;
public database()
{}
{
}
public void delete()
{
}}
RESULT
Thus the Library Management System has been modeled using Rational rose Suite.
Ex. No. 16
80
STUDENT INFORMATION SYSTEM


Date:
AIM
To develop a project Student Information System using Rational Rose Software tool
PROBLEM ANALYSIS AND PROJECT PLANNING
A Student information system (SIS) is a software application for educational establishments to manage
student data. Student information systems provide capabilities for entering student test and other assessment scores,
building student schedules, tracking student attendance, and managing many other student-related data needs in a
school, college or university.
PROBLEM STATEMENT
a. Effective for Administration Purpose
b. Cheap
c. Better Service
UML DIAGRAMS:
The following UML diagrams describe the process involved in the online recruitment system
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. Activity diagram
f. Component diagram
USE CASE DIAGRAM:
The actors in this use case diagram are Admin, Student, Database. The use cases are the activities performed by
actors.
a. Admin register login, and store the student records details in database.
b. Student Register from the Student Login process.
c. Then the database is searched for details and verified.
d. Database stores the details and returns acknowledgement
For Administrator:
Admin Login
Add Student
Admin
Delete Student
Update Student Records
For Student:
81
Database
Student Login
Message
Attendance
Student
Databases
Profile
Result
Time Table
Fee
Library
Log Out
CLASS DIAGRAM:
This class diagram has three classes Login, Student details and Update details in database.
a. Students is the class name. Its attributes are name, Address, DOB, Gender, College, Subjects, Semester,
Year, Degree, Branch. The operations Performed in the students class, Store database and Update.
b. Administration is the class name. Its attributes are Login, Password and database. The operations
performed are Student Details store in database and send acknowledgement.
c. Database is the class name. The operations performed are storing Search and storing the values.
Login
Student details
+username
+password
+Name
+Address
+Age
+Course
+Department
+Phone no
+Login()
+validation()
+get_data()
+display()
+get_data()
+Display()
Update details
+Student details
+Result details
+Update_info()
+get_detail()
+Display()
SEQUENCE DIAGRAM:
The sequence diagram describes the sequence of steps to show
82
a. The Admin login and registering for Add Stduent Details.

b. The verification done by the interface and sending acknowledgement
c. Searching the database with login and displaying it for maintenance.
for registration.
For Validity:
Admin/Student
Validation
Database
1 : Request for validity()
2 : Check for validity()
3 : Validate()
4 : Successful validate()
For Administrator:
Login
Admin
ReqAdd Student
ReqUpdate Student
1 : Enter Credentials for login()

3 : Valid user()
4 : Successful login()
5 : Enter details for adding a student()
6 : Add()
7 : Successful()
8 : Successfully added()
9 : Enter credentials for update student record()
10 : Update()
11 : Successful()
12 : Successfully Updated()
For Student:
83
Database
Login
Student
ReqView Profile
ReqView Details
Database
1 : Enter credentials for login()

2 : Check for Validity()
3 : Valid()
4 : Valid login()
5 : Request for view profile()
6 : Request()
7 : Set Details()
8 : Get the details()
9 : Request for view Details()
10 : Request()
11 : Set Details()
12 : Get the Details()
COLLABRATION DIAGRAM:
The collaboration diagram is to show how the Student registers and the authorities maintains the details of the
registered students in the Information system. Here the sequence is numbered according to the flow of execution.
For Validity:
Database
3 : Validate()

Validation
1 : Request for validity()
4 : Successful validate()
Admin/Student
For Administrator:
84
Database
3 : Valid user()
6 : Add()
10 : Update()
7 : Successful()
11 : Successful()

Login
ReqAdd Student
ReqUpdate Student
1 : Enter Credentials for login()
8 : Successfully added()
12 : Successfully Updated()
4 : Successful login()
9 : Enter credentials for update student record()

5 : Enter details for adding a student()
Admin
For Student:
Database
3 : Valid()
6 : Request()
2 : Check for Validity()
10 : Request()
7 : Set Details()
Login
11 : Set Details()
ReqView Profile
8 : Get the details()
ReqView Details
4 : Valid login()
1 : Enter credentials for login()
Object1
5 : Request for view profile()

9 : Request for view Details()
12 : Get the Details()
Student
ACTIVITY DIAGRAM:
This activity diagram flow of stepwise activities performed in recruitment system.
a. The student details are Add and stored in database.
b. Select the course from the given Course by student.
c. Search Profile and Result with login and if data present in the database.
d. The searched data is displayed if available and then Log Out.
85
Login
Student Registration
back to registration
If No
Yes
Select Course
Profile
Result
Fee
Library
Log Out
COMPONENT DIAGRAM:
The main component in this component diagram is Student Information system. And register, User and Manage,
Request details are the components comes under the main component.
86
User
IUser
<<application>>
Management
<<infrastructure>>
Persistence
Request
IRequest
DB
J DBC
DEPLOYMENT DIAGRAM:
The processor in this deployment diagram is the Student Information System which is the main part and the Student
are the Admin, verify and search which are the some of the main activities performed in the system.
Student Information System
Administrator
87
Student
Access Database

Java Coding
Login.java
public class login
{
private int username;
private int password;
public Studentdetails the Studentdetails;
public Updatedetails theUpdatedetails;
public login()
{ }
public void validation()
{ }
public void get_data()
{ }
{ }
}
Studentdetails.java
public class Studentdetails
{
private int name;
private int age;
private int course;
private int department;
private int phoneno;
public Studentdetails()
{ }
public void get_data()
{ }
{ }
}
Updatedetails.java
public class Updatedetails
{
private int Studentdetails;
private int Updatedetails;
public Updatedetails()
{ }
public void update_info()
{ }
public void get_detail()
{ }
{ }
}
Result
Thus the model for Student Information System using Rational Rose Software tool has been developed.
Content Beyond Syllabus
88

Ex No : 1.a
Gantt Chart for Passport Automation System
Date:
Aim:
To develop a risk management and project plan for passport automation system using Gantt Chart.
Introduction:
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts illustrate the start and
finish dates of the terminal elements and summary elements of a project. Terminal elements and summary elements
comprise the work breakdown structure of the project. Some Gantt charts also show the dependency (i.e.,
precedence network) relationships between activities. Gantt charts can be used to show current schedule status using
percent-complete shadings and a vertical "TODAY" line as shown here.
Passport Automation System

For the project, the activities considered are:
1. Requirement Analysis
2. Literature Survey and Specification
3. Preliminary Design
4. Detailed Design
5. Testing
6. Operation and Maintenance
Result:
Thus the risk management and project plan for passport automation system was designed using Gantt
Chart.
89
Ex.No:2. a
QUIZ SYSTEM
DATE:
90
MODULE 1
Get login details of the user
If new user, create a new account
Verify password and ID
MODULE 2
Display the questions
The user selects an option for each question or skips it.
Move to next question
MODULE 3
Check if the answers for each question are right or wrong.
Sum up all scores to get the total marks
Get the total of all users.
MODULE 4
Find the winner.
If a user is a winner, print you win.
Else print, game over.
SEQUENCE DIAGRAM
partcipant
Switch Over The

Question
Compiler
Central System
Reg For
NAME
Ask Question
Answer the Questions
Keep Record Score
No Answer
Calculate The
Participant Score
Won The Game
Lose The Game
CLASS DIAGRAM
91
Is It High
Score
Admin
ID
Password
registration()
calculation()
CentralSystemManagement()
user
user name
ID
Password
compiler
namelist
question
answer
plays()
sign up()
askquestion()
keepsmark()
compilers()
USECASE DIAGRAM
92
ACTIVITY DIAGRAM
STATE CHART DIAGRAM
93
Log in
Enter the
system
Select
option
Next
question
Add marks
End game
COMPONENT DIAGRAM
Server
User
Quiz UI
Printer
DBMS
Server
DEPLOYMENT DIAGRAM
Server
Get details
DBMS
Server
Get question
Printer
UI
Print result
RESULT:
The above models for the Quiz System have been designed and verified.
CS6511 Case Tools Laboratory

VIVA QUESTIONS & ANSWERS
94

1. Define Object Oriented Analysis?
Object Oriented Analysis (OOA) is a method of analysis that examines requirements from the perspective of the
classes and objects found in the vocabulary of the problem domain.
2. What is meant by Object Oriented?
Object Oriented means we organize the software as a collection of discrete objects that incorporate both data
structure and behavior.
3. Write the characteristics of an object.
Identity, classification, polymorphism, and inheritance.
4. What is a class?
A class is a set of objects that share a common structure and a common behavior.
5. Name two types of object diagram.
Class diagram and instance diagram.
6. What is an attribute? Give example.
An attribute is a data value held by the objects in a class .Example: name, age and weight are attributes of Person
class.
7. What is multiple inheritance?
When one class inherits its state (attributes) and behavior from more than one super class, it is referred to as multiple
inheritances.
8. What is dynamic binding?
The process of determining (dynamically) at run time which functions to invoke is termed dynamic binding.
9. What is static binding?
The process of determining at compile time which functions to invoke is termed static binding.
10. Write the four quality measures for software development?
Correspondence, correctness, verification, and validation.
11. What is object persistence?
Objects have life time. They are created and can exist for a period of time. A file or a database can provide support
for objects having a longer life timelonger than the duration of the process for which they were created. This
characteristic is called object persistence.
12. What is polymorphism? Give an example.
Polymorphism means that the same operation may behave differently on different classes. Ex. Move operation.
(Behave differently on the window class and chess Piece class).
13. What is cardinality?
Cardinality specifies how many instances of one class may relate to a single instance of an associated class.
14. What is a formal class or abstract class?
Formal or abstract classes have no instances but define the common behaviors that can be inherited by more specific
classes.
15. What is a meta-class?
A meta-class is a class about a class. They are normally used to provide instance variables and operations.
16. Define Encapsulation?
Encapsulation is the process of compartmentalizing the elements of an abstraction that constitute its structure and
behavior.
17. What is the need of an Object diagram?
An object diagram is used to show the existence of objects and their relationships in the logical design of a system.
18. What is state of an object?
The state of an object encompasses all of the properties of the object plus the current values of each of these
properties.
19. Write some applications of object model?
They include Air traffic control, Animation, Avionics, Database, Robotics etc.
20. Define Concurrency.
Concurrency is the property that distinguishes an active object from one that is not active.
21. Name the three general approaches for classification?
They are Classical categorization, Conceptual clustering and Prototype theory.
22. Name the five levels of process maturity in OOD?
95

They are Initial, Repeatable, Defined, Managed and Optimized.
23. Name the two process used by Grady BOOCH in his OO software development?
They are Macro and Micro development process.
24. Name the four steps in Micro development process?
They are Identify the classes and objects, Give semantics to the classes, Identify class and object relationships,
Identify class and object interfaces and implementation.
25. What are the steps followed in macro development process?
Conceptualization, analysis and development of the model, Design or create the system architecture, evolution or
implementation, maintenance.
26. Short notes on OMT functional model.
OMT functional model uses dataflow diagram that shows the flow of data between different processes in a
business .Data flow diagrams use four primary symbols. They are process, data flow, data store, external entity.
27. Names the diagrams of Booch Methodology.
Class diagram, object diagram, state transition diagram, module diagram, process Diagram, interaction diagram.
28. Name the models in objectory.
Use case model, domain object model, analysis object model, implementation model, test model.
29. What is unified modeling language?
Unified modeling language is a language for specifying, conducting, visualizing and documenting the software
system and its components.
30. Name the available layers of the three layered approach to software development.
Business layer, access layer, view (user interface) layer.
96

CS6511case Tools Lab Manual Updated

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CS6511case Tools Lab Manual Updated

Încărcat de

Drepturi de autor:

Formate disponibile

CS6511 Case Tools Lab Manual

Introduction to Case Tools

Depicts high-level business processes, including data flow,

Prepared By: Mrs. S. Selvakanmani & Mr. R. Raja, CSE Department