OOAD Full Record

STUDY OF UML
UML NOTATION
Unified Modeling Language.
Set of notations and conventions used to describe and model an application.
Universal language for modeling systems.
Standard notation for OO modeling systems.
Does not specify methodology to develop an application.
UML DIAGRAMS
Class Diagram
Use Case Diagram
Behavioral Diagram
Interaction Diagram
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
Implementation Diagram
Component Diagram
Deployment Diagram
CLASS DIAGRAM
Shows the static structure of the model.
Collection of static modeling elements such as classes and their relationships connected as a graph.
Provides visual representation of objects, relationships and their structures.
Class: A class is a set of objects that share a common structure and common behavior.
It is represented as:
<Class Name>
<Attributes>
<Operations>
Interface: Specifies the externally-visible operations of a class and/or component.

ASSOCIATION
1
Model properties of associations.

The properties are stored in a class and linked to the association relationship.
Example,
GENERALIZATION: A generalize relationship is a relationship between a more general class or use case and a more
specific class or use case.
Example,
Vehicle
Bus
Truck
Car
USE CASE DIAGRAM

Set of use cases enclosed by system boundary, communication association between actors and use
cases, and generalization among use cases.
Actors: External factors that interacts with the system from the user's perspective.
Use Cases: Set of scenarios that describe how actor uses the system.
Represented as,
RELATIONSHIP: Communication communications with the use case normally.

Uses Shown by generalization arrow from the use cases.
Extends Used when one case does more than another that is similar to it.
2
BEHAVIOR DIAGRAM
INTERACTION DIAGRAM
Diagrams that describes how group of objects are collaborated.
SEQUENCE DIAGRAM:
Describes the behavior of the system through interaction between the system and the
environment in time sequence.
Two dimensions:
Vertical dimension represents time.
Horizontal
dimension represents objects.

Life line Object's existence during the interaction.
COLLABORATION DIAGRAM
An interaction diagram that shows the order of messages that implement an operation or a
transaction.
Collaboration diagrams show objects, their links, and their messages.
Object: An object has state, behavior, and identity.

Objects interact through their links to other objects.
Link: A link is an instance of an association, analogous to an object.
Message: A message is the communication carried between two objects that trigger an event.
3
STATE CHART DIAGRAM

Models the dynamic behavior of individual classes or any other kind of object.
Shows the sequences of states, events, and actions.
State: Represents a condition or situation during the life of an object during which it satisfies some
condition or waits for some event.
<state>
Start State: Shows the beginning of workflow.

End state: Represents the final or terminal state
ACTIVITY DIAGRAM
Used for modeling the sequence of activities in a process
Special case of a state machine in which most of the states are activities and most of the transitions
are implicitly triggered by completion of the actions in the source activities.
Activity: Represents the performance of task or duty in a workflow.
<Activity>
Swim lanes: Represents organizational units or roles within a business model.

IMPLEMENTATION DIAGRAM
Shows the implementation phase of system development.
Two types of implementation diagrams:
Component diagram
Deployment diagram
4
COMPONENT DIAGRAM
Models the physical components in the design.
A graph of the designs components connected by dependency relationships.
Includes concept of packages.
Package is used to show how classes are grouped together.
DEPLOYMENT DIAGRAM
Shows the configuration of runtime processing elements and software components.
It is a graph of nodes connected by communication association.
Nodes are the components that are connected to other components through dependencies.
Used in conjunction with component diagrams to show the distribution of physical modules.
PASSPORT AUTOMATION SYSTEM
Exp No : 1
PASSPORT AUTOMATION SYSTEM
DATE:
AIM
To develop the Passport Automation System using rational rose tools.
PROBLEM ANALYSIS AND PROJECT PLAN
To simplify the process of applying passport, software has been created by designing through
rational rose tool, using visual basic as a front end and Microsoft access as a back end.The applicant
apply passport in the online, after submitting his details then verification process started. During
verification process the status of the verification process is displayed. The applicant can view their
passport status.
After the verification process completed successfully the passport is issued to applicant.
PROBLEM STATEMENT
Passport Automation System is used in the effective dispatch of passport to all of the
applicants. This system adopts a comprehensive approach to minimize the manual work and schedule
resources, time in a cogent manner.
The core of the system is to get the online registration form (with details such as name,
address etc.,) filled by the applicant whose testament is verified for its genuineness by the Passport
Automation System with respect to the already existing information in the database.
This forms the first and foremost step in the processing of passport application. After the
first round of verification done by the system, the information is in turn forwarded to the regional
administrator's (Ministry of External Affairs) office.
The application is then processed manually based on the report given by the system, and
any forfeiting identified can make the applicant liable to penalty as per the law.
The system forwards the necessary details to the police for its separate verification whose
report is then presented to the administrator. After all the necessary criteria have been met, the
original information is added to the database and the passport is sent to the applicant.
USE CASE DIAGRAM
Use case is shown as an ellipse containing the name of use case .An actor is shown as a stick figure
with the name below it. Use case diagram is a graph of actors.
DOCUMENTATION OF USECASE DIAGRAM

The actors in use case diagram are Applicant, regional administrator, database, passport
Administrator, Police.
The use cases are Login, givedetails, logout, collectdetails, verification, issue.
The actors uses the use case are denoted by the arrow
CLASS DIAGRAM
A class is drawn as rectangle box with three compartments or components separated by
horizontal lines. The top compartment holds the class name and middle compartment holds the
attribute and bottom compartment holds list of operations.
DOCUMENTATION OF CLASS DIAGRAM

The classes are Applicant, database, regional administrator, passport administrator, and police.
The applicant has attribute such as name and password and operations are login, givedetails and
logout.
The database has attribute such as name and operation is store.
The regional administrator has attribute such as name and operation are get details, verify details
and send.
The passport administrator has attribute such as name and operation are get details, verify details
and issue.
The police has attribute such as name and operation are get details, verify details and send.
SEQUENCE DIAGRAM
A sequence diagram shows an interaction arranged in time sequence,
It shows object participating in interaction by their lifeline by the message they exchange arranged in
time sequence.Vertical dimension represent time and horizontal dimension represent object.
DOCUMENTATION OF SEQUENCE DIAGRAM.

The applicant login the database and give his details and database store the details.
The passport administrator get the details from the database and do verification and the forward to
regional administrator.
The regional administrator get details form passport administrator and perform verification and
send report to passport administrator.
The police get the details form passport administrator and perform verification and send report to
passport administrator
A collaboration diagram is similar to sequence diagram but the message in number format.
In a collaboration diagram sequence diagram is indicated by the numbering the message
10
DOCUMENTATION OF COLLABORATION DIAGRAM

The applicant, passport administrator, regional administrator, police and database functions are
show in sequence number
The applicant first login the passport automation system and submit his details the passport
administrator, regional administrator and police verification are denoted.
STATE CHART DIAGRAM
The state chart diagram contains the states in the rectangle boxes and starts in indicated by
the dot and finish is indicated by dot encircled.The purpose of state chart diagram is to understand
the algorithm in the performing method.
DOCUMENTATION OF STATE CHART DIAGRAM

The states of the passport automation system are denoted in the state chart diagram
Login state represent authentication for login the passport automation system.
In this state, it checks whether the applicant has provided all the details that is required.
Police,regional administrator and passport administrator get necessary details and verification of
the applicant are denoted from the Getdetail state and verification state
ACTIVITY DIAGRAM
An activity diagram is a variation or special case of a state machine in which the states or
activity representing the performance of operation and transitions are triggered by the completion of
operation.
11
The purpose is to provide view of close and what is going on inside a use case or among
several classes.An activity is shown as rounded box containing the name of operation.
DOCUMENTATION OF ACTIVITY DIAGRAM

In this diagram, the activities taken place are login, give details, get details, verification and issuing
of passport.
Initially, the user has to login into the website through their id and password.
After, signing in successfully the user have to give the necessary details
. The given details are then verified, if the verification is successful then passport is issued else
penalty as per law.
COMPONENT DIAGRAM
The component diagram is represented by figure dependency and it is a graph of design of figure
dependency.
12
DOCUMENTATION OF COMPONENT DIAGRAM

The modules in the component diagram are applicant, passport administrator, regional
administrator, police and passport automation system.
The applicant passport administrator regional administrator and police are dependent on the
passport automation system are shown by the dotted arrow
DEPLOYMENT DIAGRAM
It is a graph of nodes connected by communication association. It is represented by a three
dimensional box
DOCUMENTATION OF DEPLOYMENT DIAGRAM

The modules in the deployment diagram are applicant, passport administrator, regional
administrator, police and passport automation system.
The applicant passport administrator regional administrator and police are dependent on the
passport automation system are shown by the arrow
Implementation:
Code for Applicant
public class Applicant
{
private int Name;
private int Fathername;
private int DateofBirth;
private int PermanantAddress;
private int TemporaryAddress;
private int EmailId;
private int PhoneNo;
13
private int PanNO;

private int ApplicationNo;
private int UserName;
private int Password;
public DataBase theDataBase;
/**
@roseuid 551BBAA1025B
*/
public Applicant()
{
}
/**
@roseuid 551BB90B033A
*/
public void Login()
{
}
/**
@roseuid 551BB913009E
*/
public void SubmitDetails()
{
}
/**
@roseuid 551BB91B02C3
*/
public void CheckStatus()
{
}
}
Code for Passport Admnistrator:

public class PassportAdministrator
14
{
private int Name;
/**
@roseuid 551BBAC30020
*/
public PassportAdministrator()
{
}
/**
@roseuid 551BB9D50197
*/
public void GetDetails()
{
}
/**
@roseuid 551BB9DF00BD
*/
public void Verify()
{
}
/**
@roseuid 551BB9E300D5
*/
public void Store()
{
}
/**
@roseuid 551BB9E50361
*/
public void IssuePassport()
{
}
}
15
Code for Police:

public class Police
{
private int name;
/**
@roseuid 551BBAD2029E
*/
public Police()
{
}
/**
@roseuid 551BBA3E03C6
*/
{
}
/**
@roseuid 551BBA460282
*/
{
}
/**
@roseuid 551BBA4A0059
*/
public void Store()
{
}
}
Code for Regional Administrator:
public class RegionalAdministrator
{
private int Name;
16
/**
@roseuid 551BBADB0274
*/
public RegionalAdministrator()
{
}
/**
@roseuid 551BBA0800D9
*/
{
}
/**
@roseuid 551BBA1003A9
*/
{
}
/**
@roseuid 551BBA13027C
*/
public void Store()
{
}
}
TESTING
FORMS:
FORM1:
17
FORM2:
18
FORM3:
19
FORM4:
20
FORM5:
21
22
FORM6:
FORM7:
RESULT:
Thus the Passport Automation System is successfully done and the UML diagram are
implemented by using the Rational rose.
23
BOOK BANK
24
EXP NO : 2
BOOK BANK
DATE :
AIM
To implement book bank system online.
To provide the students with the information on books and scheduled times of book rental
available.
To ensure validity and security in the online book bank management system.
SCOPE OF THE PROJECT
The book bank system project is a software tool created to help and access the students gather
required information about the various books in the institution the project is web based interactive
application. Focus is laid solely on the book display, schedule, categories, syllabus and payment as
per required.
PROJECT DESCRIPTION
USER PERSONAL AND CHARACTERISTICS
The target client for our software are students who lively are interested in rental of books be it
either from engineering or medical genre in the institution. They can log into our website and browse
the courses which they have aspiration to study. The student must register themselves online, which
is free. The booking or reservation of the books is online, the detailed description about their book
package and necessary terms and condition norms would be emailed to the students registered email
address which he/she may provide during the time of registration.
PRODUCT PERSPECTIVE
This product requires a web browser which is capable of playing flash media.
This program will not be dependent on any other software and is not a component of another
program.
This program does not require any new hardware.
REQUIREMENTS
(a)FUNCTIONAL REQUIREMENTS:
A functional requirement defines a function of a software system on its component. A
function is described as a set of input,the behavior and output.
i. A main menu including a brief help section.
ii. Login
25
iii. Viewing book details.

iv. Displaying details.
v. Maintain and update book details.
vi. Logout.
1. REQUIREMENTS:
The system should have the requirements of the project. The developer should prepare the
requirements of the project. They should prepare the requirements which are need for the software.
2. ANALYSIS:
Analyze the requirements whether it provides proper operations/output and performs the task.
3. DESIGN:
Project manager should design the layout of the project before going to implement time
allocation, cost allocation and staff allocation wil coming under design process.
4. IMPLEMENTATION:
After encompassing all the diagrams, we have to generate code for each and every diagrams
i.e. from use case to deployment.
5. TESTING:
After implementing the diagram with domain language, we have to test the particular
projects.
6. MAINTAINENCE:
The system should be easily updated. The system should utilize the interchangeable plug-in
software developed should maintain the cost and time schedule of the project.
NON- FUNCTIONAL REQUIREMENTS:
Nonfunctional requirements define the needs in terms if performance, logical database
requirements, design constraints, standard compliance, reliability, availability, security,
maintainability and portability.
i. PERFORMANCE REQUIREMENTS:
Performance requirements define acceptable response times for system functionality.
The total time for user interface screens will take no longer than two seconds.
The login information shall be verified within the seconds.
Queries shall results within five seconds.
ii. DESIGN CONSTRAINTS:
26
The software shall be a standard system running in a windows environment. The system shall
be developed using rational enterprise suite and oracle 10i database.
iii. RELIABILITY:
Specify the factors required to establish the required reliability of the software system at time
of delivery.
iv. AVAILABILITY:
The system should have an availability of 99.99%.
v. PORTABILITY:
The system should be extremely via the USB drive.
The system shall be easy to migrate or backed up via another use drive.
vi. MAINTAINABILITY:
The system shall utilize interchangeable plug-in.
The system shall be easily updateable for fixes and patches.
(c)HARDWERE REQUIREMENTS:
1. Processor - Intel Pentium IV-2.0 GHZ.
2. Hardware - 40 GB.
3. RAM - 512mb
4. DVD RAM - 1 nos.
(d)SOFTWARE REQUIREMENTS
1. OS - windows XP/vista.
2. Front end Tool - Rational Rose Enterprise suite.
3. Back end Tool - Oracle 10i.
MODULE DISCRIPTION:
In this project we have defined different modules to enable the Book Bank system in
successful manner.
i. REGISTER:
The register module contains the application form or registration form which contains
following details.
Name, Address, Contact number, E-mail id, Password etc.
ii. LOGIN:
The Login module contains the form which contain membership name and member
password. It includes Username and Password.
27
iii. SEARCH BOOK:

The search book module contain list of books, from this list we search for the book which we
need. This also contains another field called as categories where can select the category of the book.
iv. DISPLAY DETAILS:
Display the details about the students particulars, the payments, the books, rental and
schedule times for books etc.
v. MAINTAIN BOOK DETAILS:
The administrator maintains the details of books.
vi. LOGOUT:
To sign off from the webpage or your account log off.
DOMAIN MODEL:
A domain model is a visual representation of conceptual classes or real situations object in a
domain.
In object oriented analysis, the domain model is the most important.
It illustrates the concept in the domain.
It act source of inspiration as a for designing some software objects.
PARTIAL LAYERED ARCHITECTURE:
Sequence diagram is an interaction overview diagram. It provides a big picture overview of
how a set of interaction are related in terms of logic and process flow.
This Partial layer architecture shows the interface of the sequence diagram, here the administrator
shows the interface by displaying actor symbol.
LOGICAL ARCHITECTURE:
The Logical architecture is large scale organization of software class into packages, sub
system layer, It is called logical architecture because there is no direction about how these elements
are display on different operating system.
RISK ACTIVITY:
Personal short falls.
Unrealistic schedules and budgets.
Developing the wrong functions and programs.
Developing the wrong user interface.
Continuing stream of requirements changes.
Short falls in externally furnished component.
Real time performance short falls.
Straining computer science capabilities.
RISK ASSESSMENT:
28
Figure out what the risks are and what to focus on.
Making a list of all of the potential dangers that will affect the project.
Assessing the probability of occurrence and potential cross of each item listed.
POST- FUNCTION AND PRE-FUNCTION:
MODULE: Registering
PRE-FUNCTION:
Login to the website.
Collection the required documents to be submitted for registration.
POST-FUNCTION:
Verification of documents submitted.
Conformation email sent accessing that authentication can be prevailed for the individual.
MODULE
: Display book details
PRE-FUNCTION
: Analyze the course of semester of logger.
POST-FUNCTION : Display the required book details.
USE CASE DIAGRAM:

UML provides use case diagram notation to illustrates the names of use case and author
relationship between them. Use case diagram and case relationship are secondary in use case work
use case text document.
29
30
UML CLASS DIAGRAM:

The UML class diagram is to illustrate class interfaces as their actions. They are used for
static object modeling, we have already introduced and used their UML diagram while domain
modeling.
31
LOGIN
BOOK REGISTRATION
32
VIEW BOOK DETAILS
MAINTAIN DETAILS
33
LOGOUT
DISPLAY DETAILS
34
UPDATE
35
UML SEQUENCE DIAGRAM:

A sequence diagram illustrates a kind of format in which each object interact via message. It
is generalize between two or more specialized diagram.
36
UML COLLABRATION DIAGRAM:

COLLABRATION diagram illustrate that object interact on a graph or network format in
which object can be placed where the diagram. In collaboration diagram the object can be placed in
anywhere on the diagram. The collaboration comes from sequence diagram.
37
UML STATE CHART DIAGRAM:

A UML state machine represents the interaction events and states of an object and behavior of
an object in reaction to an event.. Transaction shown as allows labeled with their event. It is included
with initial pseudo state and fins end state.
38
UML ACTIVITY DIAGRAM:

A UML activity diagram shows sequential and parallel activates in a process, work flows,
data flows and compiler algorithm
.
39
UML COMPONENT DIAGRAM:

Components are slightly fuzzy concept in this Uml, because both class and components can
be used to model the something.
40
UML DEPLOYEMENT DIAGRAM:

Deployment diagram shows the assignment of concrete software artifact to computational
nodes. It shows the deployment of software elements to the physical elements. Deployment diagram
are useful to communicate or deployment architecture.
41
IMPLEMENTATION
After the completion of UML diagrams for BOOK BANK SYSTEM we should generate the
code. Select the tools option from main menu then select the sub option program module in which
we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the generate code
option as a result of code generation.
CODE FOR ADMIN:
public class Admin
{
private membershipno;
public payment;
public Authentication;
public void update()
{
}
}
CODE FOR STUDENT
public class Student
{
public Application;
public Verification;
public Submission;
public Admin myAdmin;
public void payment()
{
}
}
CODE FOR BOOKBANK EMPLOYEE
public class Book bank Employee
{
public Semester_book_list;
public Authentication_from_application_form;
public Integer payment;
public void update()
{
}
42
}
TESTING
To perform the testing for the generated code again select the tools option from menu bar and
choose quality architecture option a sub window gets opened. We are going to perform Unit Test and
Scenario testing for our project. So, select these testing option one by one and testing activity is
carried out for all the coding and testing is carried out.
43
CONCLUSION
Thus the project for BOOK BANK SYSTEM has been successfully executed and codes are
generated.
44
STOCK
MAINTENANCE
45
Exp No : 3
STOCK MAINTENANCE
DATE :
AIM
The process of unified approach is to be applied to STOCK MANAGEMENT SYSTEM. The
outcome of OOAD is to be obtained as corresponding UML diagram.
PROBLEM STATEMENT
To specify the usecase by using description of specification and flow of events such as basic
flow, alternate flow, precondition and post condition in STOCK MAINTENANCE.
ABSTRACT
The aim of this project is how to maintain the stack details and customer relationship between
the products through the class sequences, activities and collaboration diagram. All the details about
the stock are stored in the system through this the owner can communicate. Both the user and owner
can access the product details, purchase details. The owner can alone update the stock in shop. When
a customer purchases the stock the manager updates the purchased details in particular customer
details.
FUNCTIONAL REUIREMENTS
ACTORS:
1. Administrator - who has the entire control
2. Supplier
- who supplies the product
3. Customer
- who purchase the product.
USECASES:
1. Supply the product.
2. Purchase the product
3. Customer details
4. Purchase details
5. Product details
6. Sales details
7. Stock details.
NON-FUNCTIONAL REQUIREMENTS
System should be designed simple enough to the customer to buy the product without any hesitation.
System must handle network and the power failure of software must be efficient to use and provide
quick recovery from fault.
User interface screen and it must be designed to operate easily. If should have visual operations
software and system must be secured and protected.
The steps involved in the analysis must be followed thoroughly.
The system is embedded with Antivirus software and its system is free from the virus attack.
46
The system must have its own update for the software. Thus enhances the performance and secure
from the viruses.
SYSTEM REQUIREMENTS
SOFTWARE SPECIFICATION
Front End: Visual Basic 6.0
Back End: UML
Operating System: Windows Family
RAM: 64MB-256MB
Application Software: Argo UML
HARDWARE SPECIFICATION
Processor: Intel P-3 base
Processor Speed:250MHz-833MHz
Hard Disk:2GB-30GB
BASIC FLOW:
1. Administrator wants to enter the product details. He must goto the product form. The system
displays the product details form and he extends details such as product name and also the amount of
the product.
2. Then the administrator wants to enter the sales details he must goes to sales form .the system
shows the sales form he entered the details such as customer name and product code similarly the
product price and quantity.
ALTERNATE FLOW:
If the admin entered an existed product code that should be make out the error.
PRECONDITION:
The admin must log on the Product details form.
POST CONDITION:
The system shows the details about the product, sales and also purchase. So, admin must go
these forms.
47
USECASE DIAGRAM
In USE CASE diagram, there are three major actors namely Admin, agent and customer. The
actor admin is responsible For manages the following information such as product details, Purchase
details, stock details, sales details. Agent holds following information. Supply the product details.
Customer is responsible for purchasing the product.
ACTIVITY DIAGRAM
They are useful in doing the following things:
1. business process modeling
2. data flows
3. control flows
There are various symbols there to explain the each activity in project. They are
start
action
object
fork
join
partition
stop
In this diagram we are going to enter the product id that is purchased Our customer in this. If
purchase the correct product then there we can give the certain details like we should enter the
product name, entering the amount of the appropriate product and store them in the opening (i.e.)
updating the purchase details. Decision making is used in order to explain condition based statements
such as if we enter that is not in the sales system then it will return that it is not in the system if
existing item id is given then it will return the error message.
48
SEQUENCE DIAGRAM
Sequence Diagram is one kind of interaction diagram which explains the flow of message
and interaction between the objects. It describes the interaction in fence format. In stock maintenance
the flow of message takes place between the administrator, verifier and the database. Whenever the
administrator wants to check the stock details then he will enter the login details and verifier checks
it and allow him to view the stock details. Then the availability of stock is checked into database and
availability status is returned to the verifier. Based on the availability details the products are
purchased and stored in stock details.
49
COMPONENT DIAGRAM
Component diagram is used to identify replaceable components and use those components to our
process. In stock maintenance system login, stock details and database are the replaceable
components.
CLASS DIAGRAM
Product Details:
It holds the details about the various products available in the shop. It contains Price, name and
unique ID of the product. New products can be added into this class using the method Add (). Any
updating in the product details can be performed by using the method Update (). The method Clear ()
is used to clear the current product detail and view the next product, Exit () is used to exit from the
product details form.
Purchase Details:
This class encompasses the details about the purchase made by the shop keeper from the supplier. It
contains methods like Purchase save (), Purchase delete() and Edit() Which are used for saving,
deleting and modifying the purchase details.
Sales Details:
This class explains the sales transaction in the shop. We can add the sales transaction using the
method Add sales () and the Exit () is used to move the control to the Specified process.
Stock Details:
50
The administrator will maintain the stock details and this class contains the last modified date of the
stock and the administrator view all the stock details using the method View stock(). Whenever the
customer purchasing a product from the shop the quantity of particular product is decremented by
one from the stock details. All these process are done by the administrator of the shop.
Admin Details:
Administrator holds the entire control of the shop. He will maintain product, purchase, sales, stock,
and customer details using the method Maintain ().
MAIN CLASS:
STOCK DETAILS
51
PRODUCT DETAILS
PURCHASE DETAILS
52
SALES DETAILS
CUSTOMER DETAILS
53
DEPLOYMENT DIAGRAM
A deployment diagram shows the assignment concrete software artifacts to computational nodes.
STATE CHART DIAGRAM

The name of the diagram itself clarifies the purpose of the diagram and other details. It
describes different states of a component in a system. The states are specific to a component/object
of a system. A State chart diagram describes a state machine. It also used for forward and reverse
engineering of a system. But the main purpose is to model reactive system.
State chart diagrams are very important for describing the states. States can be identified as
the condition of objects when a particular event occurs. In our domain there are four states such as
login, Registration, Manage student details and close registration.The login is the initial state then it
goes to the registration state. If the student is valid they are add to the student group otherwise they
will be dropped.
54
CHECKING
PROCESS
DELIVERY
WAITING
DISPATCH
CANCELLING
EXIT
LOGICAL ARCHITECTURE DIAGRAM
55
Package diagrams can use packages containing use cases to illustrate the functionality of a
software system. Package diagrams can use packages that represent the different layers of a software
system to illustrate the layered architecture of a software system. The dependencies between these
packages can be adorned with labels / stereotypes to indicate the communication mechanism
between the layers. In our domain the exam registration with application is the package. It have
dependency with other packages like Administrator, Student, Faculty.
SOURCE CODE
Customer:
#ifdef customer_h
#define customer_h
#include <vector>
56
#include "string.h"
class product supplier;
class stock;
class customer {
public:
virtual void purchase();
public:
null custid:integer;
string cname;
public:
product supplier *myproduct supplier;
/**
* @element-type stock
*/
std::vector< stock* > mystock;
};
#endif // customer_h
Product supplier:
#ifndef product supplier_h
#define product supplier_h
class product supplier {
public:
null pname:string;
null pid:intrger;
};
#endif // product supplier_h
Stock:
#ifndef stock_h
#define stock_h
class admin;
class stock {
public:
virtual void insert();
public:
57
admin *myadmin;
};
#endif // stock_h
#ifndef admin_h
#define admin_h
Admin class:
class admin {
public:
virtual void update();
};
#endif // admin_h
Customer class:
#ifndef customer_h
#define customer_h
#include "string.h"
class supplier;
class customer {
public:
virtual void details();
public:
string cname;
null custid:int;
public:
supplier *mysupplier;
};
Supplier:
#ifndef supplier_h
#define supplier_h
class admin;
class supplier {
public:
58
virtual void update details();

public:
null name:string;
null id:int;
public:
admin *myadmin;
};
#endif // supplier_h
Customer:
#ifndef customer_h
#define customer_h
class supplier;
class customer {
public:
virtual void buy();
public:
null pname:string;
null pcode:integer;
null custid:integer;
null qty:integer;
public:
supplier *mysupplier;
};
Payment: sales class
#ifndef payment_h
#define payment_h
class admin;
class payment {
public:
virtual void calculate();
virtual void total();
59
public:
null qty:integer;
null price:integer;
public:
admin *myadmin;
};
#endif // payment_h
Stock details:
#ifndef stockdetails_h
#define stockdetails_h
class admin;
class stockdetails {
public:
virtual void add();
virtual void delete();
virtual void update();
public:
admin *1;
};
#endif // stockdetails_h
Customer: sales
#ifndef customer_h
#define customer_h
class admin;
class payment;
class customer {
public:
virtual void details();
public:
null custname:string;
null id:integer;
public:
60
admin *myadmin;
payment **;
};
Checkdetails:
#ifndef check details_h
#define check details_h
#include "integer.h"
class check details {
public:
virtual void check();
public:
integer pcode;
integer quantity;
};
#endif // check details_h
TESTING
carried out for all the coding and testing is carried out.Some of the text cases identified for the
inventory management system to make the product efficiency, correct, easy to maintain and user
friendly are listed.
USABILITY TESTING:
Testing objectives are
Product should support current operation for various clients.
All clients should be able to access the supplier.
System should support a bulk list printing.
VERIFICATION AND VALIDATION:
Fault encountered during recognition of stock id.
Insufficient order detail.
Network failure.
Time delay.
USER INTERFACE TEST CASES:
61
It should be easy to operate.

It should be visually appending.
It must be flexible.
FORMS DESIGN:
LOGIN FORM:
62
STOCK DETAILS:
CUSTOMER DETAILS:
63
ADMIN DETAILS:
PRODUCT DETAILS:
64
SALES DETAILS:
65
DELIVERY DETAILS:
PURCHASE DETAILS:
66
CONCLUSION
Thus the UML diagrams and code generation were developed for stock maintenance system
using Rational rose software.
67
ONLINE COURSE
RESERVATI0N
Exp No : 4
ONLINE COURSE RESERVATION
DATE :
AIM
To design the UML diagrams and to generate code for the online course reservation system
using Argo UML software.
PROBLEM STATEMENT
Online course reservation system is automated using client server architecture, this application
helps us to reserve for any course through Online without going to the reservation centre and wait in
queue.For this, applicant has to login into the appropriate site check the Course availability they
prefer reserve for that course, register his/her qualification details and check their eligibility. After all
confirmations the payment is made.
FUNCTIONAL REQUIRMENT
68
LIST OF USECASES:
Check course availability
Login and enter applicant details
Close Registration
Payment
LIST OF ACTORS:
Applicant
Billing system
1. Check course availability
Brief Description:
This use case allows a applicant to select the course offerings from the course catalog for the courses
that he/she is eligible for and wishes to study and the gets information whether the seat is available or
not.
b) Flow of events:
Basic flow:
This use case starts when a applicant wishes to sign up to select some course offerings.
The applicant request information about the course offerings provided in online registration.
From the courses displayed the applicant selects the desired course from the list of courses
available.
The available seats are checked to reserve if seats are available.
Alternative flows:
If the applicant does not wish to select any course close the registration.
If the seats are full close the registration.
Special Requirements:
None
Pre-conditions:
The applicant must sign up on to the system before selecting the course offering
Post-conditions:
If the use case was successful, the applicant can able to select for the course. Otherwise, the
use case terminates.
f) Extension Points:
69
None
2. Login and enter the applicant Details
Brief Description:
This use case allows an applicant to maintain applicant information in the registration system. This
includes adding, modifying and deleting applicants from the system.
b) Flow of events:
Basic flow:
This use case starts when a applicant wishes to sign up to add or change or delete applicant
information in the system. The system requests that the applicant specify the function he/she would
like to perform Once the applicant provides the requested information, one of the sub flows is
executed.
If the applicant selected Add a applicant, the Add a applicant sub flow is executed.
The system requests the applicant information. This includes,
Name
Date of Birth
Security number
Status
Graduation date
Once the applicant provides the requested information, the system generates and assigns a
unique id number to the applicant. The applicant is added to the system. The system provides the
applicant with the new applicant id.
If the applicant selected Update a applicant, the Update a applicant sub flow is executed.
The system requests the applicant to enter the name and password. The applicant enters the
name and appropriate password. The system retrieves and displays the Applicants Information. Now
the applicant can make the desired changes to the already present Applicants Information. Once the
applicant updates the necessary information, the system updates Applicants information.
If the applicant selected Delete a applicant, the Delete a applicant sub flow is executed.
The system requests the applicant to enter the name and password. The applicant enters the
name and appropriate password. The system retrieves and displays the Applicant information.The
system prompts the applicant to confirm the deletion of the applicant and if the applicant verifies the
deletion, the system deletes the applicant from the system.
Alternative flows:
If, in the Update a Applicant or Delete a Applicant sub-flows, a applicant with the specified id
is invalid, the system displays an error message.
70
The applicant can then enter a different id or correct password or else cancel the operation,
at which point the use case ends.
SPECIAL REQUIREMENTS
None
Pre-conditions:
The applicant must sign up on to the system before selecting reservation for the course.
Post-conditions:
If the use case was successful, the applicant details can be added or updated or deleted from the
system. Otherwise, the system state is unchanged.
Extension Points:
None
3. Close Registration
Brief Description:
This use case allows an applicant to close the registration process. Course offerings that do not
have enough students are cancelled. Course offerings must have a minimum of three students in them
and any professor has signed up to teach the course.
b) Flow of events:
Basic flow:
This use case starts when the applicant requests the close registration
The system checks to see if the registration is in progress. If it is, then a message is displayed to the
applicant, and the use case terminates. The close registration processing cannot be performed if
registration is in process.
For each course offering, the system checks if a professor has signed up to teach the course offering
and at least three students have registered. If so, the system commits the course offering for each
schedule that contains it.
For each schedule, the system levels the schedule: if the schedule does not have the maximum
number of primary courses selected, the system attempts to select alternates from the schedules list
of alternates. The first available alternate course offerings will be selected. If no alternates are
available, then no substitution will be made.
For each course offering, the system closes all course offerings. If the course offerings do not have at
least three students at this point (some may have been added as a result of leveling), then the system
cancels the course offering. The system cancels the course offering for each schedule that contains it.
ALTERNATIVE FLOWS:
71
If, in the basic flow, there is no professor signed up to teach the course offering, the system
will cancel the course offering. The system cancels the course offering for each schedule that
contains it.
SPECIAL REQUIREMENTS
None
PRE-CONDITIONS:
The applicant must be logged onto the system in order for this use case to begin.
POST-CONDITIONS:
If the use case was successful, the applicant is now closed. If not, the system state remains
unchanged.
Extension Points:
None
4.Payment:
A)
BRIEF DESCRIPTION:
The system calculates the tuition owed by each applicant for this current semester schedule and
sends a transaction to the billing system. Then the applicant needs to pay the amount through DD or
credit card with in specified period.The Billing system checks the bill whether the correct amount is
received with in specified period or else resends the bill.
Flow of events:
Basic flow:
The Billing system is notified for each course offering that is not cancelled and sends to the
applicant.
The applicant pays the bill through DD and needs to enter the security number for bill system to
verify.
System communicates with the billing system and sends the transaction has been successfully
completed.
Alternative flow:
If the system is unable to communicate with billing system, the system will attempt to re-send the
request after the specified period. The system will continued to attempt to re-send until the billing
system becomes available.
Special Requirements:
None
Pre- conditions:
72
The applicant must be logged on to the system in order for this use case to begin.
d) Post conditions:
If the use case was successful, payment is now closed. If not, the system re-sends the bill
until the use case was successful.
Extension Points:
None
USE CASE DIAGRAM
UML provides use case diagram notation to illustrate the names of use case and author
relationship between them. Use case diagram and case relationship are secondary in use case work use
case text document.
ACTIVITY DIAGRAM
A UML activity diagram shows sequential and parallel activities in a process, work flows, data
flows and compiler algorithm.
Check course availability
73
LOGIN AND ENTER APPLICANT DETAILS
74
CLOSE REGISTRATION
75
PAYMENT
CLASS DIAGRAM
76
The UML class diagram is to illustrates class interfaces and their actions. They are used for
static object modeling, we have already introduced and used their UML diagram while domain
modeling.
SEQUENCE DIAGRAM
77
A sequence diagram illustrates a kind of format in which each object interacts via message. It is
generalize between two or more specialized diagram.
78
COMPONENT DIAGRAM
Components are slightly fuzzy concept in this Uml, because both class and components can be
used to model the something.
DEPLOYEMENT DIAGRAM
79
UML LAYERED ARCHITECTURE DIAGRAM

A package diagram provides a way to group element. Here we have grouped the 6 main
elements of software project grouped the in order register, login, search book. It goes to update and
sales record. A package name may be based on tab if the package shows the inner member of main
package.
a) USER INTERFACE LAYER:

In this layer the user can interact by logging in into the website.
b) DOMAIN SERVICES LAYER:

We are going to generate the coding in java or VB the project domain is now finalized in
JAVA/VB.
COURSES:
It provides the available list of courses.
APPLICANT DETAIL:
The applicant can register as a new visitor for the website. Check for the course available and
register his/her details.
BILLING SYSTEM:
If the Applicant needs to pay the Billing system will provide service.
80
c) TECHNICAL SERVICES LAYER:

Technical service layer describes the relationship between different actors; components of the
software process for any applicant seek the registration for new visitor. So that the new visitor can
login the website and search for course and if need can register it.
UI
Login
Authentication
Application / Domain layer
Courses
Billing
system
ApplicantDeTAT
TATAtails
Technical service layer
Web
Personal
service
SQL
SOURCE CODE
CLASS LOGINID:
public class loginid

{
public String name;
public String password;
public controlsystem mycontrolsystem;
public void signin(){}
public void signup() {}
public void signout() {}
}
CLASS APPLICANTDETAILS
81
public class applicantdetails

{
public String name;
public Integer DOB;
private Integer socialsecuritynumber;
public Integer status;
public Integer graduationdate;
public void add() {}
public void update() {}
public void delete() {}
}
CLASS COURSES:
public class courses
{
public coursename;
public Integer courseduration;
public String university;
public void show() {}
public void update() { }
public void cancel() {}
}
CLASS PAYMENT:
public class payment
{
public String name;
public Integer securitynumber;
public String modeofpayment;
public Integer amount;
public billingsystem mybillingsystem;
public void send() {}
public void update() {}
public void exit() {}
public void newOperation() {}
}
INTERFACE CONTROLSYSTEM:
public interface controlsystem
{
public applicantdetails myapplicantdetails;
public courses mycourses;
public billingsystem mybillingsystem;
public void control();
}
82
INTERFACE BILLING SYSTEM:

public interface billingsystem
{
public void pay();
}
IMPLEMENTATION
After the completion of UML diagrams for ONLINE COURSE REGISTRATION we should
generate the code. Select the tools option from main menu then select the sub option program module
in which we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the generate
code option as a result of code generation.
TESTING
LOGIN FORM:
PAYMENT FORM:
83
PERSONAL DETAILS FORM:
BOOKING FORM:
84
COURSE FORM:
85
CONCLUSION
Thus the UML diagrams and code generation were developed for online course registration
using rational rose software.
E-TICKETING
86
Exp No : 5
E-TICKETING
DATE :
AIM
To design a online ticket reservation system using Rational rose software.
ABSTRACT
In this project, we will illustrate our system by providing DFD, STD on some functions. And
we will also provide some process description and data dictionary. For simply, we just focus on two
processes (Buy ticket & Member login) in our project. The main purpose of our online ticket
booking system is to provide another way for the customer to buy train ticket. It is an automatic
system. After inserting the data to database, staff need not to due with the order receive through the
system. In fact, there is similar system on the internet, but there is no refund method found in the
existing system
PROBLEM STATEMENT
Online ticket reservation system for railway department has to be developed.
The System developed should contain following features
1. The System should provided information about arrival and departure trains along with information
about stations through which it passes.
2. Search about train passing through stations can be obtained either by means of train no, train name
or specifying the source and destination stations.
3. While displaying information about train it has provide following informations
a) Stations through which train passes along with arrival and departure time.
b) Availability of seats in different classes along with waiting list.
87
4. While reserving ticket online the system obtain following informations from the user
a)
Passenger name, Sex, Age, Address
b)
b) Credit Card No, Bank Name
c) Class through passenger is going to travel i.e First class or Second class or AC
d) Train no and Train name, Date of Journey and number of tickets to be booked.
5. Based on the availability of tickets the ticket has to be issued. The ticked issued should contain the
following informations PNR NO, Train No, Date, K.M., no of adults and children, Ticket No, Class,
Ticket No, Coach, Seat/Berth, Sex, Age, Reservation fee, Total Cash, Train Name, Departure time.
6. Cancellation of booked tickets should be available.
FUNCTIONAL REQUIREMENT
1. RESERVATION
1.1Brief Description
This use case helps the passenger to reserve for tickets in a train
1.2.1 Basic flow
1. The user reserves the ticket by giving following
a) Passenger name, Sex, Age, Address
2. If the ticket is available in a train then the ticket will be issued with PNR No, else the ticket will be
issued with a waiting list number.
1.2.2 Alternative flow
If the passenger gives an invalid credit card no or specified a bank where does have any account.
Error message will be displayed.
1.3Special Requirements
None
1.4Pre-Conditions
The passenger has to decide about the train he is going to travel.
1.5Post-Conditions
If the use case was successful, the passenger will get the ticket.
1.6Extension Points
None
88
2. Cancelation
2.1 Brief Description
This use case helps the passenger to cancel the ticket, which he/she had booked earlier
2.2.1 Basic flow
This use case used by passenger to cancel the ticket, which he/she booked earlier by
Entering PNR No. The cancellation has been done reallocating the tickets allotted to the Passenger.
2.2.2 Alternate flow
If the Passenger had entered invalid PNR No then has been asked to enter valid PNR No.
2.3 Special Requirements
None
2.4 Pre-Conditions
The Passenger had reserved tickets in a train.
2.5 Post-Conditions
If the use case was successful, the passenger can cancel the ticket.
2.6 Extension Points
None
3.VERIFICATION
3.1Brief Description
The passenger to know status of ticket has used this usecase by entering PNR No.
3.2.1 Basic flow
1. The passenger should give PNR No to know the status of ticket, which he/she booked earlier.
2. If the PNR No is valid, the status of the ticket will be displayed.
3.2.2 Alternate flow
If passenger had entered an invalid no or PNR NO, which does not exists then error Message will
be displayed.
None
3.4 Pre-Conditions
89
3.5 Post-Conditions
If the use case was successful, the passenger can view status of the ticket.
None
4.PAYMENT
4.1 Brief Description
This use case helps the passenger to bill the ticket.
4.2 Basic Flow
1.The passenger verify the tickets.
2.Pay the cash and receive the ticket
None
4.4 Pre-Conditions
4.5 Post-Conditions
If the use case was successful, the passenger can view status of the ticket.
None
NON-FUNCTIONAL REQUIREMENT
System should be designed simple enough to enable participants To operate correctly
without any formal training or delay System should band network and power failure, software must
be efficient to use and provide access for data.
TESTING
ONCE SOURCE CODE HAS BEEN GENERATED SOFTWARE MUST BE TESTED TO UNCOVER
MANY ERRORS POSSIBLE BEFORE TO CUSTOMER. ITS GOAL IS DESIGN SERIES OF TEST
CASES THAT HAVE LIKELIHOOD OF FINDING ERRORS SOFTWARE TESTING TECHNIQUE
PROVIDE SYSTEMATIC GUIDANCE FOR DESIGNING TEST THAT :-A) EXERCISE INTERNAL
LOGIC OF SOFTWARE COMPONENTS EXERCISE THE I/P & O/P DOMAINS OF PROGRAM
FUNCTIONAL BEHAVIOR & PERFORMANCE. TESTING PHASE MUST MAXIMIZE THE NUMBER
OF ERRORS DETECTED &MINIMIZE THE NUMBER OF TEST CASES.
TESTING IS OF TWO TYPES:

A ) F UNCTIONAL
90
B)
S TRUCTURE
FUNCTIONAL TESTING HAS

A)EQUIVALENCE
PARTITIONING
IT USED TO REDUCE THE NUMBER OF TEST CASES THAT NEED TO DEVELOP BY DIVIDING THE
OUTPUT DOMAIN OF PROGRAMMED INTO CLASSES. IT IS SYSTEMATIC METHOD OF IDENTIFYING
SETS OF CLASSES OF INPUT CONDITIONS TO BE TESTED. EACH EQUIVALENCE CLASS IS
REPRESENTATIVE OF LARGE SET OF TEST CASES MAY B TAKEN TO INFER THE ELEMENTS OF
CLASS .A VALID INPUT IS AN ELEMENT OF THE INPUT DOMAIN THAT IS EXPECTED TO RETURN AN
ERRONEOUS VALUE.
B)
BOUNDARY VALUE ANALYSIS
IT IS ONE OF THE BLACK BOXES TESTING TECHNIQUE. IT IS BASED ON THE OBSERVATION

THAT FAULTS TEND TO CLUSTER AROUND BOUNDARY IN PROGRAMS. IT IS ALSO ASSUMED THAT
IF TESTING CASES FAILS TO PRODUCE AN ERROR ALL OTHER DOMAINS IN THE SYSTEM WILL FAIL
TO PRODUCE AN ERROR. ON THE BASIS OF THIS AN ATTEMPT CAN BE MADE TO COVER THE
STRUCTURE OF THE PROGRAM. IT FOCUSES ON EXCEPTION HANDLING; IT HAS THE HIGH
PROBABILITY OF FINDING BUGS.
C)
CAUSE EFFECT GRAPHING
Above techniques do not consider combination of inputs.Cause Effect Graphing is a technique

that aids in selectingcombinations of input in a systematic way such that number of test-cases do not
become unmanageably large. A cause isdistinct input condition and effect is a distinct outputconditions.
The conditions should be stated such that they havea true or a false VALUE.
STRUCTURAL TESTING HAS

A)CONTROL
FLOW GRAPH
ANY PROCEDURAL DESIGN CAN BE DESIGNED INTO A CONTROL FLOW GRAPH. LINES OR ARROWS
ARE USED TO SHOW THE GRAPH WHERE LINES ARE EDGES AND CIRCLES ARE USED TO SHOW ONE
OR MORE ACTIONS OF THE NODES. IT IS USED TO SHOW THE LOGICAL AND CONTROL FLOW OF
THE GRAPH.
B)
DATA FLOW BASED TESTING.
IT MAINLY FOCUSES ON TESTING THE VALUE ASSIGNMENT OF EACH VARIABLE IN PROGRAM BY

EXECUTING SUB PATHS FROM THE ASSIGNMENT OR DEFINITION TO SOME PROGRAM POINTS IN
WHICH THE VARIABLE IS USED.
D)MUTATION TESTING
IS A FAULT BASED TESTING TECHNIQUE USED TO TEST THE QUALITY OF THE TEST SUITE. IT IS
GENERALLY COMPUTATIONALLY EXPENSIVE.
CYCLOMATIC COMPLEXITY
91
DERIVES A QUANTITATIVE MEASURE OF LOGICAL COMPLEXITY. IT GIVES THE

NUMBER OF INDEPENDENT PATHS THROUGH STRONGLY CONNECTED DIRECTED GRAPHS I.E. EACH
NODE CAN BE REACHED FROM ANYWHERE. IT IS USED MAINLY TO FIND THE NUMBER OF PATHS
TO LOOK AT A NODE FOR TESTING, TO HELP PINPOINT AREAS OF POTENTIAL INSTABILITY, TO
PROVIDE QUANTITATIVE INDICATION, AND TO HELP IDENTIFY A UNITS/ COMPONENTS
TESTABILITY, MAINTAINABILITY AND UNDERSTANDABILITY
UML DIAGRAMS
USECASE DIAGRAM
Reservation
1. The user reserves the ticket by giving following
a) Passenger name, Sex, Age, Address
2. If the ticket is available in a train then the ticket will be issued with PNR No.else
ticket will be issued with a waiting list number.
the
Cancellation
This use case used by passenger to cancel the ticket, which he/she booked earlier by Entering
PNR No. The cancellation has been done reallocating the tickets allotted to the Passenger.
VERIFICATION
1. The passenger should give PNR No to know the status of ticket, which he/she booked
earlier.
2. If the PNR No is valid, the status of the ticket will be displayed.
PAYMENT
1. The passenger verify the tickets.
2. Pay the cash and receive the ticket
92
CLASS DIAGRAM
Class diagram that can be either used as the conceptual perspective or software perspective. In
this we use the class passenger ,train detail, train seat details, payment, reservation.
Each has different attribute and operations:
Passenger it has pname, age, sex,doj are the attributes and get pname() and setpname() are the
operation. Passenger send the details to the train details, there we have some attributes and operation.
After performing those operation send it to the train seat details and the information is send to
reservation.
After check the information in the reservation it send to the payment class
There we check the amount.
Train_Details
Attributes
private long no
Passenger
Train_Seatdetails
private String destination
Attributes
private String tname
Attributes
private string pname
private long tno
private String source
private long Age
private date DOJ
private lonf depatiretime
private string Sex
private long seats
private long arrivaltime
private date DOJ
private int coaches
Operations
Operations
public Train_Details()
Operations
public Passenger()
public Train_Seatdetails()
public long getNo()
public string getPname()1..*
public long getTno()
public void setNo(long val
1..*)
public void setPname(string val ) public
public void setTno(long val )
String getDestination()
public long getAge()
public
public void setDestination(String val
) date getDOJ()
public string getSex()
public void setDOJ(date val )
String getTname()
public void setSex(string val ) public
public void setTname(String val ) public long getSeats()
public date getDOJ()
public void setSeats(long val )
public String getSource()
public void setSource(String val ) public int getCoaches()
public void setAge(long val )
public void setCoaches(int val )
public lonf getDepatiretime()
public long getArrivaltime()
1..*
public void setArrivaltime(long val )
public void setDepatiretime(lonf val )
Reservation
Attributes
private long tno
1..*
private date DOJ
private long seatno
private int nop
private int Coaches
Operations
public Reservation()
Payment
public
long getTno()
Attributes
public void setTno(long val )
private float Amount
Operations
public Payment()
public long getSeatno()
public float getAmount()
void setSeatno(long val )
public void setAmount(float val ) public
public int getNop()
public void setNop(int val )
public int getCoaches()
public void setCoaches(int val )
public void reservatio()
93
ACTIVITY DIAGRAM
Activity diagram are graphical representation of work flow of step wise activities and action
which support for choice and activities. In this passenger, reservation, train details, seat details are
the different partitions. The passenger checks the train details and send the detail to the train Details.
If the passenger sends the ticket to the Reservation there we check the availability of seats .if the
seats are available pay the amount and get the ticket. Otherwise stop the process.
Passenger
Reservation
TrainDeatails
Seatdetails
Show train
details
Check train
details
{ From eticketactivity }
{ From eticketa...
Check seat
availability
{ From eticketa...
Reserve
tickets
{ From eticketa...
Request
Payment
Make
Payments
{ From eticketa...
{ From eticketactivi...
Issue
Ticket
{ From eticket...
94
SEQUENCE DIAGRAM
Sequence diagram is the type of interaction diagram which is in the fence format. In this the
passenger sends the reservation form to the Reservation,
The Reservation we send the train availability, seat availability and payment to the Train Details,
Train seat details, payment respectively. If all the availability has occurred send the amount to the
passenger and issue the tickets.
95
SEQUENCE DIAGRAM FOR RESERVATION
96
SEQUENCE DIAGRAM FOR CONFORMATION
97
SEQUENCE DIAGRAM FOR PAYMENT
98
SEQUENCE DIAGRAM FOR CANCELLATION

99
STATE CHART DIAGRAM

A state machine diagram shows life cycle of an object. What events it experiences, its
transition, and the states it is in between these events.
100
REQUEST FOR CREDIT

CARD NUMBER
CREDIT AGENCY
VALIDATION
COMPLETED
TRANSACTION
OVER
COMPONENT DIAGRAM
The component represents a modular part of a system that encapsulate its content and
whose manifestation is replaceable within the environment. A component defines its behavior in
terms of provided and required interface.
101
DEPLOYMENT DIAGRAM
A deployment diagram shows the assignment concrete software artifacts to
computational nodes.
LOGICAL ARCHITECTURE
The Logical Architecture is the large scale organization of the software classes in to packages or
namespaces, subsystems and layers.
Its called Logical Architecture, because there is no decision about how these elements are
deployed across the different operating system or across physical computers in a network.
A Layer is a very coarse grained grouping of classes, packages, or subsystems that has
cohesive responsibility for a major aspect of the system
Typically layers in an object oriented system are of three namely,
User Interface Layer.

Application Logic and Domain Objects Layer.
Technical Services Layer.
102
USER INTERFACE:
Swing is a class of javax package implemented in this UI layer.
Authorization package is included because of the particular people have an
authorization to login to get the Reservation Form.
Web server package is used to book the tickets by the passengers through the internet.
DOMAIN OBJECT LAYER:
Train detail object representing the details of the train such as Seating capacity, Train number,
Train name, Departure time, arrival time, source and destination of the travel.
Reservation object concerns the booking of the ticket using the availability of the seat
number, coaches such as A/C, FIRST CLASS and SECOND CLASS and about the payment.
Payment object represent the amount going to be paid by the passenger using credit, cash or
any gift coupens.
TECHNICAL SERVICES LAYER:
The Train database is used to store the details of the reservation seats and about the train.
Online service is used to book the tickets using the internet.
SQL is the backend is used for storing the details of the databases as tables.
Logging services is application independent and it records the normal activity then mapping
from the request URI to server resource and it is an reusable component used to indicate the errors
during the transaction.
103
SOURCE CODE:
class Train_Seatdetails
public class
{
private long tno;
private date DOJ;
private long seats;
private int coaches;
public Train_Seatdetails()
{
}
class setTno
public void setTno( long val )
{
tno = val;
}
public long getTno()
{
return tno;
}
public void setDOJ( date val )
{
DOJ = val;
}
{
return DOJ;
}
public void setSeats( long val )
{
seats = val; }
public long getSeats()
{
return seats;
}
public void setCoaches( int val )
{
coaches = val;
}
public int getCoaches()
{
return coaches;
}
}
104
105
106
107
CONCLUSION
108
Thus the online railway ticket reservation using Rational rose has been successfully
developed.
CREDIT CARD PROCESSING
109
Exp No : 6
CREDIT CARD PROCESSING
DATE :
AIM
To prepare necessary documents and to develop the CREIDT CARD PROCESSING
with UML diagrams using Software Engineering Methodology.
ABSTRACT
Software is to be designed for supporting a computerized CREDIT CARD PROCESSING
network. All the processing involved in a bank are computerized these days. All the accounts
maintained in the bank and also the transaction effected, including CREDIT CARD transaction, is to
be processed by the computers in the bank. A CREDIT CARD accepts relevant cash card, interacts
with user, communicates with central system to carry out the transaction, dispenses cash, and prints
receipts.
PROBLEM STATEMENT
This application helps the client to access his/her account. The client has to first enter his/her
name and account id number. Once when the details are confirmed the client can access the account,
if the details are wrong then the client has to reenter the details. Next the system should ask for the
type of transaction to perform, where the client has to choose the type of transaction they wish to
carry on. And based on the transaction chosen the actions have to be carried out. And based on their
transaction their account has to be updated.
CONTENTS
1. ANALYSIS
1.1 Identifying the Actors
1.2 Identifying the Use Cases
2. REQUIREMENTS
2.1 System Requirements
2.2 Software Requirements
3. DESIGN
3.1 Use Case Diagram
3.2 Class Diagram
3.3 Sequence Diagram
3.4 Collaboration Diagram
3.5 Activity Diagram
3.6 State Diagram
ANALYSIS
Identifying the Actors
Customer
110
Software
Banking
Dealer
Identifying the Use Cases
Browse Catalog
Select Item
Request Item
Payment Details
Issue Details
Authentication
Check for validity
Issue Goods
REQUIREMENTS
HARDWARE Requirements
Processor : Pentium IV 1.7
RAM : 128 MB
Hard Disk : 40 GB
Software Requirements
CASE Tool: ArgoUml
Language: Visual Basic in Java
Front End: Visual Basic, Visual C++
Back End: MS Access, Oracle
Testing: Win Runner
USECASE DIAGRAM FOR CREDIT CARD PROCESSING
CUSTOMER
BANK CLERK
Swipe the card
Amount for
Transaction
CASHIER
Request for
cash
Check for
balance
111
USECASE
payment
The process of requirement analysis and assigning responsibilities to object is said to be use
case.
ACTORS
The credit card processing usecase diagram actors are
CUSTOMER
CASHIER
BANKCLERK
CUSTOMER
The customer includes some process such as
Swipe the card
Amount for transaction
Request for cash
Check for balance
Payment
CASHIER
The cashier includes some process such as
Request for case
Payment
BANKCLERK
The bank clerk includes some process such as
Request for cash
Check for balance
USECASE DIAGRAM PROCESS
Customer will have to swipe or insert credit card into machine.
Then pin number, id and some details of the card will display on the machine.
Now, the customer will enter the required or desire amount the system.
112
Now, the control is transferred to corresponding bank clerk.

Then the bank clerk will check the detail of the customer account such as withdraw amount,
balance amount.
Bank clerk will sanction the amount by means of transaction.
Finally customer will pay the amount for his purchase and receives his goods.
ACTIVITY DIARGRAM FOR CREDIT CARD PROCESSING
SWIPE THE CARD
Swipe the card
Owner name
Pin number
Enter pin
number
Check PIN number
Wrong
ok
TRANSACTION PROCESSING
Enter the amount for

bill
113
Enter the amount for

transcation
If cash not found on account
if cash found on account
Request for cash and

interset
Transaction processed
Transaction processed
ok
Transaction processing
Enter the amount for required bill.
If the entered amount is in cash, move to find the account for the amount. then transaction
should be processed.
Otherwise, if cash does not found an account, then request is send to banker. To check the
amount in our cart available or not.
The amount is not available in cart, to credit some amount or interest in particular pin
number.
Thus, the banker transfers the amount in particular shopping center.
At last the transaction process is finished, to send the message ok.
114
PAYMENT
Get the amount
Payment received
Receipt returned to
customer
PAYMENT
Get the amount from customer

Paid amount was received &saved particular system.
Cashier returned the receipt to customer.
115
ONLINE PURCHASE CLASS DIAGRAM
116
Customer
ShoppingCard
Attributes
PrefferedCustomer
Attributes
private string addrtoship
Attributes
public float subtotal
private string name
private int discountrate
public float salesmoney
private string addrtobill
public float totalmoney
Operations
private string emailadd
public
PrefferedCustomer()
Operations
private int creditrating
public
int getDiscountrate()
public ShoppingCard()
Operations
public float getSubtotal()
public
void
setDiscountrate
public Customer()
public void setSubtotal(float val )
(int val )
public string getAddrtoship()
public float getSalesmoney()
Customer getCustomer()
public void setAddrtoship(string val ) public
public
void setCustomer
public void setSalesmoney(float val )
* public string getName()
public float getTotalmoney()
(Customer
val ) getCustomer1()
public void setName(string val )
public
Customer
public void setTotalmoney(float val )
public string getAddrtobill()
public
void
setCusotmer1
public void placeOrder()
public void setAddrtobill(string val )
(Customer
val )
public void removeOrder()
public string getEmailadd()
Customer
getCustomer()
public Customervoid[0..*] getCustomer()1 public void setEmailadd(string val ) public
public
void
setCustomer
public void setCustomer(Customer val[0..*]public
)
int getCreditrating()
(Customer val )
public CreditCardvoid[0..*] getCreditCard()public void setCreditrating(int val )
public void setCreditCard(CrdeitCard val[0..*]
)
mCustomer
public void displayCategory()
public Customer[0..*] getCustomer()
1
public void selectItem()
public void setCustomer(Customer val[0..*]public
)
void delieverItem()
public CreditCard[0..*] getCreditCard()
1
public void setCreditCard(CreditCard val[0..*] )
mCustomer
1
mCreditCard
1
mPrefferedCustomer
*
CreditCard
*
Operations
ItemOfPurchase
public
Attributes
public
int getNumber()
CreditCard()
private int quantity
public void setNumber(int val )
private float priceperitem
public date getExpirydate()
public void setExpirydate(date val )
Operations
public
public boolean getIssue()
public
int
public void setIssue(boolean val )
ItemOfPurchase()
public void setQuantity(int
public void authorizeCharge()
getQuantity()
public
float
public Preffered()
val
)
public
void setPriceperitem(float
public ItemOfPurchase getItemOfPurchase()
getPriceperitem()
public
public void setItemOfPurchase(ItemOfPurchase val )
val
) Customer
public
void
setCustomer(Custome
public PrefferedCustomer[0..*] getPrefferredCustomer()
fetCustomer()
public void setPrefferredCustomer(PrefferedCustomer val[0..*] )
rpublic
val ) Product[0..*]
public void setProduct(Product
public PrefferedCustomer[0..*] getPrefferedCustomer()
getProduct()
public
Product[0..*]
public void setPrefferedCustomer(PrefferedCustomer val[0..*] )
val[0..*]
)
public
void setProduct(Product
getProduct()
val[0..*] )
mProduct
1
Product
Attributes
Operations
public Product()
SHOPPING CART
The Shopping Card consists of operations involving making of total amount for items
purchased, individual amount of sales items.
117
Shopping cart has many-to-one [0..*-1] relationship with the customer.

Since many items are to be loaded into the Shopping Cart.
It has many-to-one relationship with the Customer class since a customer will have a
shopping cart of many items.
The totaling has to be made for several items in a shopping cart through the loop.
CUSTOMER
The Customer class consists of the operations involving getting the details of customer like
customer information, their address and mail id.
Another important operation described in here is the credit rating that is one of the main processes
involved.
The main aim of our project is the credit card processing implemented in an application and
hence the customer plays the vital role who pays the bill through the credit card.
As already mentioned Customer is the main actor here and plays the key role it doesnt have any
relationship with any other classes.
ITEM OF PURCHASE
The ItemOfPurchase class consists of the product description about the shopping cart items
purchased by the customer.
This involves operations like getting and assigning the price and quantity of the items
purchased by the customer.
When the item is scanned then the information like the itemed and the description is
displayed by the system. The cashier has to enter the quantity and the price of the item purchased by
the customer.
This class has many-to-one relationship with the Shopping Cart class as many items are held
by the shopping cart and the items description is provided by this class.
This class has one-to-one relationship with the Product class.
CREDIT CARD
The Credit Card class has the operations involving getting the credit card number of the
preferred customer and checking the authority of that particular customer whether he/she has the
access rights.
The expiry date and the validity are checked for that particular customers credit card.
The total amount for the required bill is paid by the particular customer by transacting the
amount.
This class has many-to-one relationship with the Preferred Customer class.
PREFERRED CUSTOMER
The Preferred Customer class has the operations involving setting the customer of the particular
credit card and also providing discount if available.
This class has a relationship with the Customer class.
PRODUCT
This class has the operations of a particular product.
118
NLINE PURCHASE SEQUENCE DIAGRAM
: Shoppingcart
: creditcard
: Customer
public void brow secatalog()
public void displaycatalog()

public void getCreditRating()

public void getAddrToShop()
public void setCreditCard()
public void shipmentDetails()
public void authorizedCharge()
public void getExpiryDate()
validation
public void authorize()
public void setCrediting(int val )
public void setAddrToShip()
public void deleverItem()

public void rejected()
Customer will request shopping card for catalog.

Shopping card sends the reply to the customer by displaying the catalog.
Customer selects an item from the catalog.
Shopping card request credit rating and address to ship from the customer.
Customer will then sets the credit and shipment details in shopping card.
Shopping card then checks the authorize charge and expiry date from the credit card.
119
Validation is checked for that card.

Authorization is returned back to the shopping card.
Customer receives the set crediting and set address to shipment and do level item to the customer.
If so then the authorization is rejected.
Finally the orders of the customer are removed by the shopping card.
ONLINE PURCHASE STATECHART DIAGRAM
CHECKING
PROCESS
WAITING
DELIVERY
CANCELLING
DISPATCH
EXIT
A UML STATE MACHINE REPRESENTS THE INTERACTION EVENTS AND STATES OF AN OBJECT AND
BEHAVIOR OF AN OBJECT IN REACTION TO AN EVENT.. TRANSACTION SHOWN AS ALLOWS
LABELED WITH THEIR EVENT. IT IS INCLUDED WITH INITIAL PSEUDO STATE AND FINS END STATE.
120
The state chart diagram involves the concept of checking the status of the processing in the project.
We need to verify the log in id and password and then we need to perform 2 processes. If the
matching of id is done then we need to wait and bill and then deliver the products. If not then we
need to cancel the process and then dispatch the items and amount is not transacted in the account of
the particular user. This enhances security.
COMPONENT DIAGRAM
Components are slightly fuzzy concept in this UML, because both class and components can be used
to model the something. The Component diagram describes the number of components used in the
project. We are using some important components like cashier, customer and bank clerk in CREDIT
CARD PROCESSING.
The cashier component does the billing operation and then announces the cash for payment to the
customer. The Customer swipes the card and enters the log in procedure in order to transact the
amount. The Bank clerk receives the request of the customer and then transacts the amount to the
particular shop in which we have to pay the amount.
DEPLOYMENT DIAGRAM
121
The deployment diagram describes some of the basic and important components deployed in
CREDIT CARD PROCESSING. Deployment diagram shows the assignment of concrete software
artifact to computational nodes. It shows the deployment of software elements to the physical
elements. Deployment diagram are useful to communicate or deployment architecture
LOGICAL ARCHITECTURE AND PACKAGE DIAGRAMS
User Interface
Login
Swing
Authorization
Swipe
122
Domain layer
Purchase
Transaction
Payment
Technical Services
Database
Oracle
Online Services
Bank Account
A package diagram provides a way to group element. Here we have grouped the 6 main elements of
software project grouped the in order register, login, search book. It goes to update and sales record.
A package name may be based on tab if the package shows the inner member of main package.
The Logical Architecture diagram includes 3 layers:
UI LAYER
The java classes like Swing classes are implemented in this layer.
User interaction operations like logging, authorization checking and the swiping of the card are
included in this layer.
UI layer describes purely about the User Interaction by the system.
DOMAIN LAYER
The domain layer consists of purchase, transaction and payment.
Since the purchase is the application taking place with the help of user then it is implemented in
domain or application layer
Thus all those layers like transaction and payment are also implemented here in this layer.
123
TECHNICAL LAYERS
The technical layers consist of all the technical applications such as database from which the
authorization of the user is verified.
The online services are used in here because we need to transact the amount from the bank into the
particular users account.
The Oracle is used for back end process since the data is being retrieved and verified.
SOURCE CODE
CLASS CUSTOMER
public class Customer()
{
private string name
private string addtoshop
private int creditrating
public Customer()
{
}
public void delieverItem()
{
}
{
}
public void removeItem()
{
}
}
CLASS ITEMOFPURCHASE
public class ItemOfPurchase()
{
private int quantity
private flaot priceperitem
public ItemOfPurchase(){}
public float getPriceperItem(){}
public void setPriceperItem(float val)
{
Item = val
}
}
124
CLASS PRODUCT
public class Product()
{
public Product()
{
}
}
TESTING
UNIT TESTING
Unit testing allows the programmer to refactor code at a later date, and make sure the module still
works correctly (e.g., in regression testing). The procedure is to write test cases for
all functions and methods so that whenever a change causes a fault, it can be quickly identified and fixed.
Readily-available unit tests make it easy for the programmer to check whether a piece of code is still working
properly.
In continuous unit testing environments, through the inherent practice of sustained maintenance, unit
tests will continue to accurately reflect the intended use of the executable and code in the face of any change.
Depending upon established development practices and unit test coverage, up-to-the-second accuracy can be
maintained.
Unit testing provides a sort of living documentation of the system. Developers looking to learn what
functionality is provided by a unit and how to use it can look at the unit tests to gain a basic understanding of
the unit's API.
Unit test cases embody characteristics that are critical to the success of the unit. These characteristics
can indicate appropriate/inappropriate use of a unit as well as negative behaviors that are to be trapped by the
unit. A unit test case, in and of itself, documents these critical characteristics, although many software
development environments do not rely solely upon code to document the product in development.
Functional vs non-functional testing

Functional testing refers to activities that verify a specific action or function of the code.
These are usually found in the code requirements documentation, although some development
methodologies work from use cases or user stories. Functional tests tend to answer the question of
"can the user do this" or "does this particular feature work".
Non-functional testing refers to aspects of the software that may not be related to a specific function
or user action, such as scalability or security. Non-functional testing tends to answer such questions
as "how many people can log in at once".
WHITE-BOX TESTING
Clear box testing, glass box testing, transparent box testing, or structural testing is a method
of testing software that tests internal structures or workings of an application, as opposed to its
functionality (i.e. black-box testing). In white-box testing an internal perspective of the system, as
well as programming skills, are required and used to design test cases. The tester chooses inputs to
125
exercise paths through the code and determine the appropriate outputs. This is analogous to testing
nodes in a circuit, e.g. in-circuit testing(ICT).
While white-box testing can be applied at the unit, integration and system levels of
the software testing process, it is usually done at the unit level. It can test paths within a unit, paths
between units during integration, and between subsystems during a system level test. Though this
method of test design can uncover many errors or problems, it might not detect unimplemented parts
of the specification or missing requirements.
CREDIT CARDS:
CARD DETAILS FORM:
126
CREDIT CARD TRANSACTION FORM:
127
CREDIT CARD USAGE FORM:
128
CREDIT CARD DETAILS FORM:
CONCLUSION
Thus the CREDIT CARD PROCESSING is developed with all necessary documents and
UML diagrams using Software Engineering methodology.
129
RECRUITMENT SYSTEM
130
Exp No :7
RECRUITMENT SYSTEM
DATE:
AIM
To design a UML diagram and generate a code for RECURITMENT SYSTEM using Argo
UML system software and deriving its functional and non-functional requirements.
SCOPE OF THE PROJECT
To ensure the portability and therefore compatibility.
To ensure our system moves with time (i.e.) allow for maintenance, upgrades and periodic
backups by developed and authorized personnel.
To program the system using the appropriate design, application, platform and programming.
PROBLEM DEFINITION
The growth of recruitment has been driven by combination of actual costs savings in the
recruitment process, increased ease and efficiency for the employer along with an improved
experience for candidates.
This software system reduce agency and processing costs, increase speed to hire, improve
productivity and candidate quality.
This project recruitment system is an online website in which job seekers can register
themselves online and apply for job and attend the exam. This software product has facilities, where
perspective candidates can upload their curriculum vita and apply for jobs suited to them.
REQUIREMENTS
(i).FUNCTIONAL REQUIREMENTS
A functional requirement defines a function of a software system on its component. A function is
described as a set of in out, the behaviour and output.
1. REQUIREMENTS
The system should have the requirements of the project. The developer should prepare the
requirements of the project. They should prepare the requirements which are need for the software.
2. ANALYSIS
Analyze the requirements whether it provides proper operations/output and performs the task.
3. DESIGN
Project manager should design the layout of the project before going to implement time allocation;
cost allocation and staff allocation will come under design process.
131
4. IMPLEMENTATION
After encompassing all the diagrams, we have to generate code for each and every diagram i.e.
from use case to deployment.
5. TESTING
After implementing the diagram with domain language, we have to test the particular projects.
6. MAINTAINENCE
The system should be easily updated. The system should utilize the interchangeable plugging
software developed should maintain the cost and time schedule of the project.
(ii).NON- FUNCTIONAL REQUIREMENTS:
Non functional requirements define the needs in terms if performance, logical database
requirements, design constraints, standard compliance, reliability, availability, security,
maintainability and portability.
1. PERFORMANCE REQUIREMENTS
Performance requirements define acceptable response times for system functionality.
The total time for user interface screens will take no longer than two seconds.
The login information shall be verified within the seconds.
Queries shall results within five seconds.
2. DESIGN CONSTRAINTS
The software shall be a standard system running in a windows environment. The system shall be
developed using rational enterprise suite and oracle 10i database.
3. RELIABILITY
Specify the factors required to establish the required reliability of the software system at time of
delivery.
4. AVAILABILITY
The system should have an availability of 99.99%.
5. PORTABILITY
The system should be extremely via the usb drive.
The system shall be easy to migrate or backed up via another use drive.
6. MAINTAINABILITY
The system shall utilize interchangeable plugging.
The system shall be easily updateable for fixes and patches.
(iii) HARDWARE REQUIREMENTS
1. Processor
- Intel Pentium IV-2.0 GHZ.
2. Hardware
- 40 GB (segate)
3. RAM
- 512mb
4. DVD RAM - 1 nos.
132
(iv) SOFTWARE REQUIREMENTS

1. OS
- windows XP/vista.
2. Case Tool
- Argo UML
3. Front end Tool - Visual Basic 6.0
4. Back end Tool - My SQL
MODULE DISCRIPTION
In this project we have defined different modules to enable the RECTUITMENT system in
successful manner.
Modules in this project are,
1. Administrator
2. Job seekers (candidates)
3. Company (organization)
ADMINISTRATOR
Administrator has the full authority over the website. He can view all the registered users and have
the power to delete them. He/she can edit the web pages and update them. He/she can view all the
company details also.
CANDIDATE
A candidate can register himself after registration; he will be directed to his homepage. Here, he can
update his profile, change password and see the examination details and company details.
COMPANY
A company can register itself, conduct online examination, approve or disapprove candidates
attending examination and provide results about the selected candidates.
DOMAIN MODEL
A domain model is a visual representation of conceptual classes or real situations object in a
domain.
In object oriented analysis, the domain model is the most important.
It illustrates the concept in the domain.
It acts as a source of inspiration for designing some software objects.
PARTIAL LAYERED ARCHITECTURE
Sequence diagram is an interaction overview diagram. It provides a big picture overview of
how a set of interaction are related in terms of logic and process flow.
This Partial layer architecture shows the interface of the sequence diagram; here the administrator
shows the interface by displaying actor symbol.
LOGICAL ARCHITECTURE
The Logical architecture is large scale organization of software class into packages, sub system layer;
it is called logical architecture because there is no direction about how these elements are display on
different operating system.
133
RISK ACTIVITY
Risk management is increasingly seen as one of the main jobs of project managers. It involves
anticipating risks that might affect the project schedule or the quality of the software begins
developed and taking actions to avoid these risks,
RISK ACTIVITY such as,
Risk identification
Risk analysis
Risk planning
Risk monitoring
POST- FUNCTION AND PRE-FUNCTION
1. CANDIDATE REGISTRATION
PRE-FUNCTION: Candidate should sign up by giving username and password.
POST-FUNCTION: Enter into the candidate information form, and then candidate
Should enter the personal details, qualification etc.
2. ACKNOWLEDGEMENT
PRE-FUNCTION: Admin sends the reply to the candidate with register numbers.
POST-FUNCTION: Candidate could receive the mail from admin and get the register no.
3. LOGIN
PRE-FUNCTION: Candidate should given the register no as user name and same
Password which has already given while sign up his/her account.
POST-FUNCTION: Enter into the software to attend the aptitude test. It will show the
Home page.
4. APTITUDE TEST
PRE-FUNCTION: Candidate should attend the test which is conducted on online.
POST-FUCTION: Submit the answer sheet to admin.
5. RESULT VERIFICATION
PRE-FUNCTION: Admin should correct the answer sheet which has been sent by candidate.
POST-FUNCTION: Admin should select the candidate on the basis of his/her process and sends the
report to concerned candidate (selected candidate).
6. UPDATE
PRE-FUNCTION: Admin should update the admin tools and company details to
Respective candidates.
134
POST-FUNCTION: Update is correctly views on the screen while user (candidate) browses the
particular webpage.
7. DIRECT HR INTERVIEW
PRE-FUNCTION: Organization should check the certificates (if valid or not).
POST-FUNCTION: Direct questions are shooting out to the particular candidate.
8. JOB CONFORMATION DETAILS
PRE-FUNCTION: Organization should send the conformation letter to the selected
Candidate.
POST-FUNCTION: Candidate should receive the appointment order with his/her posting
Detail
UML USECASE DIAGRAM:
UML provides use case diagram notation to illustrate the names of use case and author
relationship between them. Use case diagram and case relationship are secondary in use case work
use case text document.
135
UML ACTIVITY DIAGRAM

A UML activity diagram shows sequential and parallel activities in a process, work flows, data
flows and compiler algorithm.
136
UML STATE CHART DIAGRAM

A UML state machine represents the interaction events and states of an object and behavior of
an object in reaction to an event.. Transaction shown as allows labeled with their event. It is included
with initial pseudo state and fins end state.
137
UML CLASS DIAGRAM

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

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

Components are slightly fuzzy concept in this UML, because both class and components can be
140
UML DEPLOYMENT DIAGRAM
141

UML PACKAGE DIAGRAM

142
A package diagram provides a way to group element. Here we have grouped the 6 main
elements of software project grouped the in order register, login, search book. It goes to update and
sales record. A package name may be based on tab if the package shows the inner member of main
package.
TECHNICAL SERVICES LAYER

143
Technical service layer describes the relationship between different actors; components of the
software process for any admin seek the registration for new visitor. So that the new visitor can login
the website and search for book and if need can buy it.
DOMAIN SERVICES LAYER
After technical services layer from partial layered architecture, we are going to generate the
coding in java or VB the project domain is now finalized in JAVA/VB.
USER INTERFACE LAYER
ADMIN
The administrator is used to register a new visitor for the website. Admin can keep those records
update. Admin keep sales record i.e, now much book is downloaded and how much book is brought
newly with copy write etc.
REGISTERED USER
Registered user can search the book whatever needs and can read the book in online. If user is
satisfied with this book, can download the book but after payment.
VISITOR:
The visitor can register the application form and become a member of the website. The visitor
can search books and read the book but he must register to buy or download the book.
CODING:
public class Admin
{
public Integer Checking;
public Integer Verification;
public Integer Validation;
public void Acknowledgement( ){}
public void Update( ){}
}
public class Company organization extends Admin
{
public String Login;
private String Result verification;
public String Record of company details;
public void Update(){}
public void Acknowledgement(){}
}
public class Candidatedetailsextends Admin
{
public String Record candidate information;
public String Login;
public String Attend exam;
144
public String Attend interview;

public void Submit( ){}
public void View details( ){}
public void retrieve mails( ){}
}
IMPLEMENTATION
After the completion of UML diagrams for RECRUITMENT SYSTEM we should generate
the code. Select the tools option from main menu then select the sub option program module in
which we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the generate
code option as a result of code generation .
TESTING
ONCE SOURCE CODE HAS BEEN GENERATED SOFTWARE MUST BE TESTED TOUNCOVER
MANY ERRORS POSSIBLE BEFORE TO CUSTOMER.ITS GOAL IS DESIGN SERIES OF TEST CASES THAT
HAVE LIKELIHOOD OF FINDINGERRORS SOFTWARE TESTING TECHNIQUE PROVIDE SYSTEMATIC
GUIDANCE FOR DESIGNINGTEST THAT :-A) EXERCISE INTERNAL LOGIC OF SOFTWARE
COMPONENTS.B) EXERCISE THE I/P & O/P DOMAINS OF PROGRAM FUNCTIONAL BEHAVIOR &
PERFORMANCE.TESTING PHASE MUST MAXIMIZE THE NUMBER OF ERRORS DETECTED
&MINIMIZE THE NUMBER OF TEST CASES.
TESTING IS OF TWO TYPES:
A)
B)
F UNCTIONAL
S TRUCTURE
FUNCTIONAL TESTING HAS

A)EQUIVALENCE
PARTITIONING
IT
USED TO REDUCE THE NUMBER OF TEST CASES THAT NEED TODEVELOPED

BY DIVIDING THE OUTPUT DOMAIN OF A PROGRAMME INTOCLASSES. IT IS SYSTEMATIC
METHOD OF IDENTIFYING SETS OF CLASSES OF INPUT CONDITIONS TO BE TESTED. EACH
EQUIVALENCE CLASS IS AREPRESENTATIVE OF LARGE SET OF TEST CASES MAY BE TAKEN
TO INFER THEELEMENTS OF CLASS .A VALID INPUT IS AN ELEMENT OF THE INPUTDOMAIN
THAT IS EXPECTED TO RETURN AN ERRONEOUS VALUE.
B)BOUNDARY VALUE ANALYSIS
IT IS ONE OF THE BLACK BOX TESTING TECHNIQUE. IT IS BASED ON

THEOBSERVATION THAT FAULTS TEND TO CLUSTER AROUND BOUNDARY INPROGRAMMES.
IT IS ALSO ASSUMED THAT IF TESTING CASES FAILS TOPRODUCE AN ERROR ALL OTHER
DOMAINS IN THE SYSTEM WILL FAIL TO PRODUCE AN ERROR. ON THE BASIS OF THIS AN
ATTEMPT CAN BE MADE TO COVER THE STRUCTURE OF THE PROGRAMME. IT FOCUSES ON
EXCEPTION HANDLING, IT HAS THE HIGH PROBABILITY OF FINDING BUGS.
145
C)
CAUSE EFFECT GRAPHING

ABOVE TECHNIQUES DO NOT CONSIDER COMBINATION OF INPUTS. CAUSE EFFECT
GRAPHING IS A TECHNIQUE THAT AIDS IN SELECTING COMBINATIONS OF INPUT IN A
SYSTEMATIC WAY SUCH THAT NUMBER OF TEST-CASES DOES NOT BECOME
UNMANAGEABLY LARGE. A CAUSE INDISTINCT INPUT CONDITION AND EFFECT IS A
DISTINCT OUTPUT CONDITIONS. THE CONDITIONS SHOULD BE STATED SUCH THAT THEY
HAVE A TRUE OR A FALSE VALUE.
STRUCTURAL TESTING
CONTROL FLOW GRAPH
ANY PROCEDURAL DESIGN CAN BE DESIGNED INTO A CONTROL FLOW GRAPH. LINES
OR ARROWS ARE USED TO SHOW THE GRAPH WHERE LINES ARE EDGES AND CIRCLES ARE
USED TO SHOW ONE OR MORE ACTIONS OF THE NODES. IT IS USED TO SHOW THE LOGICAL
AND CONTROL FLOW OF THE GRAPH.
DATA FLOW BASED TESTING
IT MAINLY FOCUSES ON TESTING THE VALUE ASSIGNMENT OF EACH VARIABLE IN
PROGRAMME BY EXECUTING SUB PATHS FROM THE ASSIGNMENT OR DEFINITION TO SOME
PROGRAM POINTS IN WHICH THE VARIABLE IS USED.
MUTATION TESTING
IS A FAULT BASED TESTING TECHNIQUE USED TO TEST THE QUALITY OF THE TEST
SUITE . IT IS GENERALLY COMPUTATIONALLY EXPENSIVE.
CYCLOMATIC COMPLEXITY
DERIVES A QUANTITATIVE MEASURE OF LOGICAL COMPLEXITY. IT GIVES THE
NUMBER OF INDEPENDENT PATHS THROUGH STRONGLY CONNECTED DIRECTED GRAPHS
I.E EACH NODE CAN BE REACHED FROM ANYWHERE. ITIS USED MAINLY TO FIND THE
NUMBER OF PATHS TO LOOK AT A NODE FOR TESTING, TO HELP PINPOINT AREAS OF
POTENTIAL INSTABILITY, TO PROVIDEQUATITATIVE INDICATION, AND TO HELP IDENTIFY A
UNITS/ COMPONENTS TESTABILITY, MAINTAINABILITY AND UNDERSTANDABILITY
LOGIN FORM
146
REGISTRATION FORM
APTITUDE TEST FORM
147
RESULT VERIFICATION FORM
RESULT FORM
148
CONCLUSION
Thus the project for RECRUITMENT SYSTEM has been successfully executed and codes are
generated.
149
EXAM REGISTRATION
150
Exp No : 8
EXAM REGISTRATION
DATE :
AIM
To design a UML document for Exam Registration using Rational rose software.
ABSTRACT
This project asses student by conducting objectives tests should be highly customizable. It will
enable educational institute to conduct test &have automated checking of answers based on the
response by candidate who were registered. It allows faculties to create their own test .It would
enable educational institution to perform test. It asks faculty to create his /her set of questions.
Faculty then creates groups &adds related student into the student group can appear for the test. The
result of the response would be available to the faculty of the question set. Further the result would
also be mailed to the student .It would be helpful for certain practice tests say for educational
institution.
FUNCTIONAL REQUIREMENTS
Maintaining details of student.
Registers are authorized.
Results are updated.
Maintaining information of exam.
NON-FUNCTIONAL REQUIREMENTS
Performance
Reliability.
Security.
Registration accuracy.
confidentially.
SYSTEM REQUIREMENTS
HARDWARE REQUIRMENTS
Processor :Intel Pentium III
CPU speed :1.0GHZ
Storage capacity:20GB
Ram capacity:512 GB
SOFTWARE REQUIRMENTS
Front end: visual basic 6.0
Back end: Argo UML
PROBLEM STATEMENT
The EXAM REGISTRATION project is to develop an application to make the students
register for attending the online exams, they appear for the test. At last the result will be generated as
soon as the test becomes over.
151
Before making registrations the student will get the idea of the test by receiving the mail from
the concern organizations. By receiving that information through the mail the student may accept to
appear for the test or they may reject the application.
If the student click on accept then the registration form will be displayed which contains
some of the student details such as name, qualification and other details which has to be filled by the
student.
After filling all the details the user click on submit. Then the form will be submitted.
As soon as it is submitted the student will be provided with the unique login password. While
the student is appearing for the test he\she should login with that particular user name and
password .The user name and password is verified for the authentication then he will proceed with
the test.
After the registration the student will login with that particular login and he may appear for
test. He may also go with the practice test mode in which n the questions and the options will appear
on the screen but the mark will not be taken into considerations.
He may appear straightly to the test mode also rather than attending the practice test mode.
For that purpose the student should click on the test mode. Then the new window will be opened in
which the initial conditions will be displayed on the screen. Then after reading the terms and
conditions the student should click the button with add questions then click on the button with add
choices. Then you may start answering by clicking on the correct options among various choices.
The initial conditions are that once we have clicked the single option then we cannot able to
replace the option for that particular question. Then there will be 30 questions and for each question
we will be provided with the 30 minutes. If timeout or the total questions is answered then the
window gets closed. The mark will be provided in which for a correct answer the system will provide
1 mark. And for every wrong answer there is negative mark. The whole percentage is calculated by
subtracting the percentage of negative mark from the success ratio.
Then at last the mark will be sent through the mail. After that the student will get an
certification through the mail. Then the person may sign-out.
USECASE DIAGRAM OVERVIEW
In this diagram, it contains two primary actors and two secondary actors. The primary actors
are student, administrator. The secondary actors are faculty and system. It contains nine usecases
.They are add facilities, login, user profile, manage student groups, student registration, manage test,
appear for test, result generation, logout. In add faculty use case, there is a one-one association
between administrator and add faculties.
Another one-one association existing between add faculties and the
system. The add faculty use case contains login name and temporary password. In login usecase, the
administrator sends both faculty login name and temporary password to the system. There is a
uniassociation between system, faculty and login use case. One-one association between login use
case and system.
The student and faculty both send the user name and password to the system, the system
verifies username and password. In user profile use case there is a one-one association between
student, faculty, system and user profile.
The student, faculty both send message for changing the user mail address and password.
System manages the changed user mail address and password. In manage student use case there is a
one-one association between the faculty, system and manage student use case. The faculty verifies
the system login and then makes the groups in the system. The faculty sends the logout message to
the system.
In student registration use case , there is a one-one association between the student, system
and student registration use case. The student enters all the details to the system. In manage test use
case, there is a one-one association between the faculty, manage test use case and the system. The
152
faculty conducts the test. In appear for test use case, there is a one-one association between the
student, system and appear test appear test use case.
The student may or may not be appearing the test. In result generation use case, one-one
association between the student, result generation and system.
The system generates the result for those who appeared in the test. In logout use case there
is a one-one association between the student, logout use case and system .After all the above process
were completed, the student logout from the system.
USECASE DIAGRAM
ACTIVITY DIAGRAM
Activity diagram are Graphical representations of workflows of step wise activities and actions
with support for choice, iteration and concurrency.
In the UML activity diagrams can be used to describe the business and operational step by step
workflows of components in a system. An activity diagram shows the overall flow of control.
153
CONSTRUCTION
Rounded rectangles represent activities;
Diamonds represent decisions;
Bars represent the start (split) or end (join) of the workflow;
An encircled black circle represents the end (final state).
Login
Registration
Manage Test
Manage Student Groups
Appear Test
Result Generation
ACTIVITY DIAGRAM FOR OUR DOMAIN
1. LOGIN
The students use the login page to enter the registration. If the username & password valid
means they are able to register.
2. MANAGE STUDENT DETAILS
After login the faculty add the students to make a group of students & select the students by
their details .If student has invalid registration code are removed from lists.
.
3. STUDENT REGISTRATION
After selecting given the invitation for the student, after receive the invitation open registration
with verification code. Then give the user details to submit with student name & password.
4. MANAGE TEST
In manage test the new test editor was opened in which the practice test are also allowed. If the
test editor gets opened then they go for adding the test questions and the choices for that particular
questions and the test timing will be set. The negative marks for each and every questions will be set.
5. APPEAR TEST:
This activity diagram illustrates the process taken down while appearing for test.After login with our
original id ,the student go for selecting test and test groups.Then the student can start answering the
questions until the time out occurs or all the questions are answered.
6. RESULT GENERATION:
Here the comparison of student selected choice with the correct answer was made. If it matches then
add the mark to the total score. If it does not matches then the negative mark will be added to the
total score. Then the result will be sent to the student through the mail.
154
LOGIN - ACTIVITY DIAGRAM
155
MANAGE STUDENT DETAILS-ACTIVITY DIAGRAM
156
STUDENT REGISTRATION-ACTIVITY DIAGRAM
APPEAR FOR TEST-ACTIVITY DIAGRAM
157
RESULT GENERATION ACTIVITY DAIGRAM
-:
CLASS DIAGRAM
Class diagram is the main building block in object oriented modeling. It describes the
structure of the system by the systems class their attributes & the relationships between the classes.
158
It is used both for general conceptual modeling of the systematic application & also the
programming code.
The faculty prepares the test & adds students in the group by the login with username & password.
The students give the response by the given details of the test, the select the choices.
When faculty selects the select the student & then invites them for the test. They also store the result
of the student after test. The Student has student ID & also question ID from the faculty.
159
CLASS DIAGRAM
160
SEQUENCE DIAGRAM
Sequence diagram in unified modeling language (UML) is a kind of interaction diagrams. It
shows how processes operate with one another and in what order. It is a construct a message
sequence chart. Sequence diagram are sometimes called event diagrams, event scenarios, and timing
diagrams. A sequence diagram shows, as parallel vertical lines (lifelines), different processes or
objects that live simultaneously, and as horizontal arrows, the message exchanged between them, in
the order in which they occur. This allows the specification of simple runtime scenarios in graphical
manner. The sequence diagram for login, manage student details & student registration. In login the
interaction between the user & system. in manage student details student, faculty & system has
interaction .In student registration interaction between student & system
161
Collaboration diagram, also called as communication diagram or interaction diagram, is an
illustration of the relationships and interactions among software objects in the Unified Modeling
Language(UML).The concept is more than a decade old although it has been refined as modeling
paradigms have evolved. Objects are shown as Rectangles with naming labels inside. These labels
are preceded by colons and may be underlined, the relationships between the objects are shown as
arrows connecting he rectangles. The messages between objects are shown as arrow connecting the
relevant rectangles along with that define the message sequencing.
Collaboration diagrams are best suited to the portrayal of simple interactions among
relatively small numbers of objects. As the number of objects and messages grows, a collaboration
diagram can become difficult to read. Several vendors offer software for creating and editing
collaboration diagrams. The registration open the registration issue the notice to the students. They
apply for the exam. The registration manager checks the availability then selects the student, give
intimation to them. The Student pays the provisions to the billing system that issue the bills to
student register.
162
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed. So deployment diagrams are used to describe
the static deployment view of a system. Deployment diagrams consist of nodes and their
relationships. Deployment diagrams are used for describing the hardware components where
software components are deployed. Component diagrams and deployment diagrams are closely
related.
UML diagrams are used to handle logical components but deployment diagrams are made to
focus on hardware topology of a system. Deployment diagrams are used by the system engineers. A
deployment diagram consists of nodes. Nodes are nothing but physical hardware used to deploy the
application. In our domain the server terminal is EXAMINER GUI Network. It is a component with
database Management. The client terminal is STUDENT GUI Network. The database server is the
stereotype node. The HTTP protocol is used here.
163
COMPONENT DIAGRAM
Component diagrams are different in terms of nature and behavior. Component diagrams are used
to model physical aspects of a system. Physical aspects are the elements like executables, libraries,
files, documents etc which resides in a node. So component diagrams are used to visualize the
organization and relationships among components in a system. These diagrams are also used to make
executable systems. It does not describe the functionality of the system but it describes the
components used to make those functionalities. A single component diagram cannot represent the
entire system but a collection of diagrams are used to represent the whole. In our domain the
components are Examiner GUI, student GUI ,Database, Main application with Network. The
required interfaces are provided in the component.
STATE DIAGRAM
The name of the diagram itself clarifies the purpose of the diagram and other details. It
describes different states of a component in a system. The states are specific to a component/object
of a system. A State chart diagram describes a state machine. Now to clarify it state machine can be
defined as a machine which defines different states of an object and these states are controlled by
external or internal events. As State chart diagram defines states it is used to model lifetime of an
object. State chart diagram describes the flow of control from one state to another state. It also used
for forward and reverse engineering of a system. But the main purpose is to model reactive
system. State chart diagrams are very important for describing the states. States can be identified as
the condition of objects when a particular event occurs. In our domain there are four states such as
login, Registration, Manage student details and close registration. The login is the initial state then it
164
goes to the registration state. If the student is valid they are add to the student group otherwise they
will be dropped. The next state is collect details from the registered student. Then close the
registration in final state.
LOGICAL ARCHITECTURE WITH PACKAGE DIAGRAM

a package diagram in the unified modeling language depicts the dependencies between the
packages that make up a model. package diagrams can use packages containing use cases to illustrate
the functionality of a software system.
package diagrams can use packages that represent the different layers of a software system to
illustrate the layered architecture of software system.the dependencies between these packages can
be adorned with labels / stereotypes to indicate the communication mechanism between the layers.
in our domain the exam registration with application is the package. it have dependency with other
packages like administrator, student, faculty.
165
CODING
MAILER CLASS
import java.util.Vector;
public class Mailer
{
/**
*
* @element-type Faculty
*/
public Vector myFaculty;
public void sendinvite(void emali) {}
public void sendresult() {}
}
STUDENT CLASS
166
public class Student extends User {

public Integer groupid;
/**
*
* @element-type Student Response
*/
public Vector myStudent Response;
public Group myGroup;
public void getgroupid() {}
public void setgroupid() {}
public void Register() {}
public void selecttest() {}
public void Answerquestion() {}
STUDENT RESPONSE CLASS
public class Student Response {
public Integer studentid;
public questionid;
public choiceSelected;
/**
*
* @element-type Student
*/
public Vector myStudent;
/**
*
* @element-type Test Question
*/
public Vector myTest Question;
public void getstudentid() {}
public void setstudentid() {}
public void getquestionid() {}
public void setquestionid() {}
public void getchoiceSelected() {}
public void setchoiceSelected() {}
}
USER CLASS
public class User {
public Integer userid;
public username;
public password;
public name;
167
public void getuserid() {}

public void setuserid() {}
public void getusername() {}
public void setusername() {}
public void getpassword() {}
public void setpassword() {}
public void getname() {}
public void setname() {}
public void login() {}
public void logout() {}
}
GROUP CLASS
public class Group {
public Integer groupid;
public groupname;
/**
*
* @element-type Student
*/
public Vector myStudent;
/**
*
*/
public void getid() {}
public void setid() {}
public void getgroupname() {}
public void setgroupname() {}
}
TEST CLASS
public class Test {
public Integer testid;
public testname;
public allowpractice;
public timeperquestion;
public timepertest;
/**
*
*/
168

public void gettestid() {}
public void settestid() {}
public void gettsetname() {}
public void settestname() {}
public void gettimeperquestion() {}
public void settimeperquestion() {}
public void gettimepertest() {}
public void settimepertest() {}
}
TEST QUESTION CLASS
public class Test Question extends Test
{
public Integer questionid;
public question;
public choices;
public correctanswer;
/**
*
* @element-type Student Response
*/
public Vector myStudent Response;
public void getquestionid() {}
public void setquestionid() {}
public void getquestion() {}
public void setquestion() {}
public void getchoices() {}
public void setchoices() {}
public void getcorrectanswer() {}
public void setcorrectanswer() {}
}
RESULT CLASS
public class Result {
public Integer studentid;
public testid;
public marks;
public void getstudentid() {}
public void setstudentid() {}
public void gettestid() {}
169
public void settestid() {}

public void calculatemarks() {}
IMPLEMENTATION
After the completion of UML diagrams for ONLINE EXAM REGISTRATION we should
generate the code. Select the tools option from main menu then select the sub option program
module in which we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the
generate code option as a result of code generation.
TESTING
integration testing for our project. So, select these testing option one by one and testing activity is
UNIT TESTING
Components are tested sequentially. When the component is error free then we go for the
construction of next component.
INTEGERATION TESTING
One component is combined with the other component and the testing was performed. If it is error
free then the whole tested component is combined with the other and the process continues.
FOR LOGIN DIAGRAM
170
CREATE QUESTIONS INTERFACE
CONCLUSION
This project provides facility to conduct exam to be registered. It saves time as it allows
number of students to give the exam at a time and displays the results as the test gets over, so no
need to wait for the result.
It is easy to analyze using the UML diagrams. Administrator has a privilege to create, modify
and delete the test papers and its particular questions. User can register, login and give the test with
his specific id, and can see the results as well.
171
BPO MANAGEMENT
SYSTEM
172
Exp No : 9
BPO MANAGEMENT SYSTEM
DATE :
AIM
To prepare the document for BPO Management System and to develop the UML diagrams
using case tools software.
PROBLEM STATEMENT
A call center or call center (see spelling differences) is a centralized office used for the
purpose of receiving and transmitting a large volume of request by telephone
A BPO is operated by a company to administer product support or information inquiries from
customers. Outgoing calls for telemarketing, client and dept collection are also made. In addition to a
calls for center, collective handling of letters, faxes, and e-mails at one location is known as a contact
centre.
A BPO is often operated through an extensive open workspace for call center agents, with
work stations that include a computer for each agent, a telephone set/headset connected to a telecom
switch, and one or more supervisor stations. It can be independently operated or networked with
additional centers, often linked to a corporate computer network, including mainframes,
microcomputers and LANs. Increasingly, the voice and data pathways into the centre are linked
through a set of new technologies called Computer Telephony Integration (CTI).
Most major business use call centers to interact with their customers. Examples include utility
companies, mail order catalogue firms, and customer support for computer hardware and software.
Some business even service internal functions through call centers.
USE CASE DIAGRAM
173
SEQUENCE DIAGRAM
174
CLASS DIAGRAM
ACTIVITY DIAGRAM
175
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
176
TESTING
FORMS
FORM 1
177
FORM 2
FORM 3
178
FORM 4
FORM 5
179
FORM 6
FORM 7
180
FORM 8
RESULT
Thus the BPO Management system is successfully done and the UML diagram are
181
E-BOOK
MANAGEMENT
SYSTEM
Exp No : 10
E-BOOK MANAGEMENT SYSTEM

182
DATE :
PROBLEM DOMAIN
INTRODUCTION:
This E-BOOK should contain index of the topics. When the main page is visited index of
the topics is displayed. Select the required topic and double click on it. Then the page with the
contents of the selected topic will be displayed. A certain option is also present in that page to go
back to main page and search for other topics.
STEPS:
Create a main page.
Main page contains index of certain topics.
When a particular topic is required double click on it.
It displays a page with the contents of that topic.
A separate option is present to go back to main page.
USE-CASE DIAGRAM
CLASS DIAGRAM
183
SELECT E-BOOK CHOOSE THE MAIN TOPIC CHOOSE THE SUB TOPIC
184
ACTIVITY DIAGRAM
STATE CHART DIAGRAM

185
SEQUENCE DIAGRAM
USER SYSTEM
1: SELECT THE TOPIC
2: DISPLAY TABLE OF CONTENTS
3: SEARCH FOR TOPIC
4: DISPLAY THE INFORMATION
5: EXIT
DEPLOYMENT DIAGRAM
186
Deployement diagram shows the assignment of concrete software artifact to computational

nodes. It shows the deployement of software elements to the physical elements. Deployement
diagram are useful to communicate or deployement architecture
COMPONENT DIAGRAM
Components are slightly fuzzy concept in this Uml,because both class and components can be
187
TESTING:
FORMS
FORM 1
188
FORM 2
FORM 3
RESULT
Thus the E-Book management system is successfully done and the UML diagram are
189

OOAD Full Record

Uploaded by

Copyright:

Available Formats

OOAD Full Record

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OOAD Full Record

Uploaded by

Copyright:

Available Formats

STUDY OF UML

Interface: Specifies the externally-visible operations of a class and/or component.

Model properties of associations.

USE CASE DIAGRAM

RELATIONSHIP: Communication communications with the use case normally.

dimension represents objects.

Object: An object has state, behavior, and identity.

STATE CHART DIAGRAM

Start State: Shows the beginning of workflow.

Swim lanes: Represents organizational units or roles within a business model.

PASSPORT AUTOMATION SYSTEM

PASSPORT AUTOMATION SYSTEM

DOCUMENTATION OF USECASE DIAGRAM

DOCUMENTATION OF CLASS DIAGRAM

DOCUMENTATION OF SEQUENCE DIAGRAM.

DOCUMENTATION OF COLLABORATION DIAGRAM

DOCUMENTATION OF STATE CHART DIAGRAM

DOCUMENTATION OF ACTIVITY DIAGRAM

DOCUMENTATION OF COMPONENT DIAGRAM

DOCUMENTATION OF DEPLOYMENT DIAGRAM

private int PanNO;

Code for Passport Admnistrator:

Code for Police:

iii. Viewing book details.

iii. SEARCH BOOK:

: Display book details

: Analyze the course of semester of logger.

POST-FUNCTION : Display the required book details.

USE CASE DIAGRAM:

UML CLASS DIAGRAM:

VIEW BOOK DETAILS

UML SEQUENCE DIAGRAM:

UML COLLABRATION DIAGRAM:

UML STATE CHART DIAGRAM:

UML ACTIVITY DIAGRAM:

UML COMPONENT DIAGRAM:

UML DEPLOYEMENT DIAGRAM:

STATE CHART DIAGRAM

LOGICAL ARCHITECTURE DIAGRAM

virtual void update details();

It should be easy to operate.

ONLINE COURSE RESERVATION

LOGIN AND ENTER APPLICANT DETAILS

UML LAYERED ARCHITECTURE DIAGRAM

a) USER INTERFACE LAYER:

b) DOMAIN SERVICES LAYER:

c) TECHNICAL SERVICES LAYER:

Application / Domain layer

Technical service layer

public class loginid

public class applicantdetails

INTERFACE BILLING SYSTEM:

PERSONAL DETAILS FORM:

TESTING IS OF TWO TYPES:

FUNCTIONAL TESTING HAS

BOUNDARY VALUE ANALYSIS

IT IS ONE OF THE BLACK BOXES TESTING TECHNIQUE. IT IS BASED ON THE OBSERVATION

CAUSE EFFECT GRAPHING

Above techniques do not consider combination of inputs.Cause Effect Graphing is a technique