CHAPTER I

INTRODUCTION

1.1 OVERVIEW
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.
Purpose

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.

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

OVERALL DESCRIPTION
1.3

PRODUCTPERSPECTIVE

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.
SoftwareInterface
1. OS - windows XP/vista.
2. Front end Tool - Rational Rose Enterprise suite.
3. Back end Tool - Oracle 10i
HardwareInterface
1. Processor - Intel Pentium IV-2.0 GHZ.
2. Hardware - 40 GB.
3. RAM - 512mb
4. DVD RAM - 1 nos.
1.4 DEFINITIONS AND ABBREVATIONS
TERMS

DESCRIPTION

MEMBER

The one who registers himself and

purchase books from the bank.

DATABASE

Database is used to store the details of

members and books.

ADMINISTRATOR

The one who verifies the availability of

book and issue them

USER

Member

SOFTWARE REQUIREMENT
SPECIFICATION

This software specification documents full

set of features and function for online
recruitment system that is performed in
company website

TECHNOLOGIES TO BE USED
HTML
JavaScript
Java
XML
TOOLS TO BE USED
Eclipse IDE ( Integrated Development Environment)
Rational Rose tool ( for developing UML Patterns)
1.5 SYSTEM FUNCTIONS
REGISTER:
The register module contains the application form or registration form which contains following
details.
Name, Address, Contact number, E-mail id, Password etc.
LOGIN :
The Login module contains the form which contain membership name and member password.
It includes Username and Password.
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.
DISPLAY DETAILS:
Display the details about the students particulars, the payments, the books, rental and schedule
times for books etc.
MAINTAIN BOOK DETAILS:
The administrator maintains the details of books.
LOGOUT:
To sign off from the webpage or your account log off.

1.6 USER CHARESTERISTICS

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
buyed 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 boook but he must register to buy or download the book.
1.7 ENVIRONMENTAL SPECIFICATION
SOFTWARE FUNCTIONS
Front End Client - The investor and buyer online interface is built using JSP and

HTML.The buyers local interface is built using Java.

Web Server - Glassfish application server(Oracle Corporation).
Back End - Oracle database.

1.8 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.
USE CASE MODELLING DESCRIPTION
Use Case diagrams identify the functionality provided by the system (use cases), the
users who interact with the system (actors), and the association between the users and the
functionality.Use Cases are used in the Analysis phase of software development to articulate the
high-level requirements of the system. The primary goals of Use Case diagrams include:

Providing a high-level view of what the system does.

Identifying the users ("actors") of the system.

Determining areas needing human-computer interfaces.

ASSUMPTIONS AND DEPENDENCIES

The Applicants and Administrator must have basic knowledge of computers and English
Language.
The applicants may be required to scan the documents and send.
1.9 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.
1.10 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.

CHAPTER 2
DEVELOP THE USECASE MODELING

2.1 INTRODUCTION TO USE CASE MODELING

Use case diagrams identify the functionality provided by the system,the users who
interact with the system(actors),and the association between the users and the functionality. Use
cases are used in the analysis phase of the software development to articulate the high level
requirements of the system.
Basic Elements:
Actor
Actor is something with behaviour,and is depicted using a stick figure. Actors are not
limited to humans. If a system communicates with another application, the that application can
also be considered an actor.
Use case
A Use case describes a sequence of actions that provide something of measurable value to
an actor. A use case is the functionality provided by the system.
Association
Associations are used to link Actors with Use cases ,and indicate that an actor participate
in the use case in some form. Associations are depicted by a line connecting the actor and the use
case.

<<communicate>>
<Actor Name>
(f rom Actors)

We had mentioned the use case in fully dressed style.

2.3 UML USE CASE DIAGRAM

<Use Case Name>

(from <Use Case Name>)

Fig 1:UML Use case Diagram

CHAPTER 3
DEVELOPING UML ACTIVITY DIAGRAM

3.1 INTRODUCTION TO UML ACTIVITY DIAGRAM

Activity diagrams are used to document workflows in a system, from the business
level down to the operational level. The activity diagram is a variation of the state diagram where
the states represent operations, and the transition represent the activities that happen when the
operation is compleate. The general purpose of Activity diagrams is to focus on flows driven by
internal processing vs. external events.
Basic Elements
1)Activity states
Activity states mark an action by an object. The notations for these states are rounded
rectangles, the same notation as found in state chart diagrams.
2)Transition
When an activity state is completed, processing move to the other activity state.
Transitions are used to mark this movement and modeled using arrows.
3)Initial state
The initial state marks the entry point and the initial activity state. The notation for the
initial state is the same as in state chart diagrams, a solid circle. There can only be one initial
state diagram.
4)Final state
Final states mark the end of the modeled work flow. There can be multiple final states
on a diagram and these states are modeled using a solid circle surrounded by another circle.
5)Synchronization bar
Activities often can be done in parallel. To split processing, or to resume processing
when multiple activities have been completed, synchronization bars are used. These are modeled
as solid rectangles, with multiple transactions going in and/or out.

3.2 DRAWING UML ACTIVITY DIAGRAM

Fig 2: UML Activity Diagram

Login operation

10

enter a/c no.and

password

authenticatio
n
invalid
valid
allowing
access

Trading account details

11

storing information
about a/c holder
invalid
valid
checking amount
withheld
no money
held
record trading
history

Broker operations

12

buyng the amount

from bank authority

verify the market

status

sell it to the
investor

CHAPTER 4

13

DEVELOPING THE DOMAIN MODEL

4.1 INTRODUCTION TO UML CLASS DIAGRAM

A Class diagram in the UML gives an overview of the system by showing its classes and
the relationships among them. Class diagrams are static-they display what interacts but not what
happens when they do interact.
Basic Elements
1) Class
A class is a set of objects that share a common structure and common behavior. Its
represented by a rectangle divided into three parts: class name, attributes and operations.
<CLASS NAME>

<ATTRIBUTES>

<OPERATIONS>

2) Relationships
Relationships between classes are the connecting links. Relationships between
classes are generally represented in class diagrams by a line or an arrow joining the two classes.
a) Dependency
If A depends on B then this is shown by a dashed arrow between A and B.

3) Association

14

There is an association between two classes if an instance of one class must know about
the other in order to perform its work. An association between A and B shown by a line joining
two classes.
4)Aggregation
Aggregation is the association in which one class belongs to the collection.if B aggregates
A,then A is the part of B.

5)Generalization
Generalization is an inheritance link indicating one class is a superclass of the other.A
genalization has a triangle pointing to the superclass.An inheritance relationship is indicated in
the UML by an arrow with a triangular arrow head pointing towards to the general

4.2DRAWING UML CLASS DIAGRAM

15

Fig 3: UML class diagram

CHAPTER 5

16

DEVELOPING UML INTERACTION DIAGRAM

5.1 INTRODUCTION TO UML INTERACTION DIAGRAM

Interaction diagram describes how group of objects are collaborated with each other.
Two types of Interaction diagrams
1) SEQUENCE DIAGRAM
2) COLLABORATION DIAGRAM
SEQUENCE DIAGRAM
Sequence diagram document the interactions between classes to achieve a result,such as a
usecase.Because UML is designed for object-oriented programming.These communications
between classes are known as messages.The sequence diagram lists objects hirizondally,and time
vertically,and models these messages overtime.
Basic Elements
1)object
An object has state ,behavior, an identity.object intracts through there links to other
objects .the pictorial representation for an object is a class with pre fixed by the object name and
semicoloun.

:Object 1

17

5.2 DRAWING THE SEQUENCE DIAGRAM

Fig 4: UML sequence Diagram

18

Login Operation

Investor

trading
account
1: submitt account no.and password

2: invalid ,enter correct details

3: reset a/c no.,password

19

Trading A/C details

market
authority

investment

bank
database

1: buy
2: bank a/c balance> trading a/c balance

3: make investment

4: sell

20

Broker operations

broker

trading
database
1: buying the amount from bank
2: if no money.then confirmation
3: verify the market status
4: if status is profit
5: selling operation

21

5.3 DRAWING COLLABORATION DIAGRAM

Fig 5: UML Collaboration Diagram

22

CHAPTER 6
DEVELOPING THE STATE CHART DIAGRAM

6.1 INTRODUCTION TO UML STATE CHART DIAGRAMS

A UML statement diagram illustrate the intresting events and states of an object and
the behavior of an object in reaction to the event transition are shown as arrows , labeled with
their events state are shown as rounded rectangles .
BASIC ELEMENTS
1)Events
An event is a siginificant or noteworthy occurrence
For examples : A telephone reciver is taken off the hook
2)States
A state is a condition of an object at a movement in a time , the time between events
For example
A telephone is in the state of being idle after the reciver is placed on the hook and until it is
taken off the hook.
3)Transitions
Transition is a relation between states that indicates that when an event occurs,the object
moves from the prior state to the subsequent state.
For example
When the event off hookoccurs,transition the telephone from idle to activestate.
4)Transition action
A trancition can cause a action to fire . in a software implementation , this may represent
the invocation of a method of the class of the state chart diagram

23

6.2 DRAWING THE UML STATE CHART DIAGRAM

Fig 6: UML State chart Diagram

CHAPTER 7

24

DEVELOPING THE UML PACKAGE DIAGRAM

7.1 INTRODUCTION TO UML PACKAGE DIAGRAM

The logical architecture is the large scale organization of the software classes into
packages, systems and layers.
Its called the logical architecture because theres no decision about how these elements
are deployed across different operating system process or across physical computers in a
network.
LAYER:
A layer is a very coarse grained grouping of clasess,packages or subsystems that has a
cohesive responsibility for a major aspect of the system.
Layers are organized such that higher layers call upon services of lower layer,but not
normally vise versa.
Layered architecture is divided into
1)Strict layered architecture
2)Relaxed layered architecture
In strict layered architecture, a layer calls upon the services of thee layer directly
below it .This design is common in network protocol stacks, but not in information systems,
which usually have a relaxed architecture, in which a higher layer calls up on several lower
layers.
UML PACKAGE DIAGRAM:
It is used for designing logical architecture of the system using this package we can
group anything
Ex: classes, other packages
Notation: Package name may be placed on the tag if the packages show inner members or
it is placed in the main folder if no members.
It is common to shoe dependency between packages so that developers can see the large
scale coupling in the system.
The UML dependency line is used for a dashed arrow line with a arrow pointing towards
the dependant on packages.

25

Packages are defined by 3 symbols

Embedded packages
UML fully qualified names
Circle cross symbol

7.2 DRAWING THE UML PACKAGE DIAGRAM

26

Fig 7: UML Package Diagram

CHAPTER 8
IMPLEMENT THE TECHNICAL SERVICE LAYER

27

Technical services layer shows general purpose objects and subsystems that
provide supporting technical services, such as interfacing with a database or error logging. These
services are usually application-independent and reusable across several systems. Technical
service layer describes the relationship between different actors, components of the software
process for any admin seek the registration for new members. So that the new visitor can login
the website and search for book and if need can buy it.
SCREENSHOTS:

CHAPTER 9
IMPLEMENT THE DOMAIN OBJECT LAYER

28

Domain object layer shows the software objects representing domain concepts(for
example, a software class sale) that fulfill application requirements, such as calculating the sales
total.
After technical services layer, the coding can be generated in C++ using Rational
Rose Enterprise Suite.
Domain Objects Layer for Foreign Trading System:
ACCOUNT
Option Explicit
'##ModelId=4D64958501F4
Private accoutno As Integer
'##ModelId=4D64958E0186
Private balance As Integer
'##ModelId=4D64959B0290
Private due As Integer
'##ModelId=4D6612990290
Public Sub accountno()
MsgBox "your transaction is successfull"
Form6.Show
End Sub
'##ModelId=4D66130F0128
Public Sub accountpay()
MsgBox "your transaction failed. Do your trading again"
Form5.Show
End Sub
ITEM
Option Explicit
'##ModelId=4D6495B600CB
Private name As String
'##ModelId=4D6495BC0213
Private id As Integer
'##ModelId=4D6495CA0251

29

Private rate As Integer

'##ModelId=4D6495D103C8
Private available As Integer
'##ModelId=4D6612C202CE
Public Sub getperfume()
Form3.Text3.Text = Form3.Text3.Text - Form3.Text5.Text
Form4.Show
End Sub
'##ModelId=4D6612D30167
Public Sub getdoll()
Form7.Text3.Text = Form7.Text3.Text - Form7.Text5.Text
Form8.Show
End Sub
TRADER:
'##ModelId=4D64952500BB
Public Sub login()
If Form1.Text1.Text = "ramya" And Form1.Text2.Text = "ramya" Then
MsgBox "logined successfully"
Form5.Show
Else
MsgBox "invalid login"
End If
End Sub
'##ModelId=4D64952901C5
Public Sub sourcing()
If Form5.Combo1.Text = "perfume" Then
Form3.Show
End If
If Form5.Combo1.Text = "dolls" Then
Form7.Show
End If
End Sub
'##ModelId=4D649531005D
Public Sub placeorder()
Form5.Show
End Sub
'##ModelId=4D64953600FA
Public Sub pay()
Form2.Show
End Sub

30

ADMINISTRATOR
'##ModelId=4D6496030128
Public NewProperty As item
'##ModelId=4D6CAE4001F4
Public Sub paybill2()
Form7.Text3.Text = Form7.Text3.Text - Form7.Text5.Text
End Sub
'##ModelId=4D649563003E
Public Sub bill1()
Form4.Text1.Text = Form3.Text4.Text * Form3.Text5.Text
Form4.Show
End Sub
'##ModelId=4D6CA397008C
Public Sub bill2()
Form8.Text1.Text = Form7.Text4.Text * Form7.Text5.Text
Form8.Show
End Sub
'##ModelId=4D64956F0399
Public Sub traceorder()
Form5.Adodc1.ConnectionString
=
"Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Documents and Settings\Student\Desktop\datum\db.mdb;Persist Security Info=False"
Form5.Adodc1.RecordSource = "select itemname from itemtable"
Set Form5.DataGrid1.DataSource = Form5.Adodc1
Form3.Text5.Text = ""
End Sub
'##ModelId=4D6612B70186
Public Sub paybill1()
Form3.Text3.Text = Form3.Text3.Text - Form3.Text5.Text
End Sub

31

CHAPTER 10
IMPLEMENT THE USER INTERFACE LAYER

USER INTERFACE LAYER for Book Bank System

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
buyed 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 boook but he must register to buy or download the book.
LOGIN
The Login module contains the form which contain membership name and
Member password. It includes Username and Password.

32

CHAPTER 11
DEVELOPING THE IMPLEMENTATION DIAGRAMS

11.1 INTRODUCYION TO IMPLEMENTATION DIAGRAMS

Implementation shows the implementation phase of system development. Two types of
implementation diagrams:
i. Component diagram
ii. Deployment diagram
11.2 COMPONENT DIAGRAM
A component diagram depicts how the components are wired together to form larger
components and or software systems. Components are wired together by using an assembly
connector to connect the required interface of one component with the provided interface of
another component.
The components are slightly fuzzy thing.
It describes the module part of the system which encapsulates its components.
It describes the behaviour in terms of interface.
It is a design level perspective.
11.3DOCUMENTATION OF COMPONENT DIAGRAM
The main component in the component diagram is foreign trading system. The trader
who come to do the trading process and administrator who manages all the other processes is the
sub components.

11.4 DRAWING THE UML COMPONENT DIAGRAM

33

Fig 8: UML Component Diagram

11.5 INTRODUCTION TO DEPLOYMENT DIAGRAM
A deployment diagram models the physical deployment of artifacts on nodes. The nodes
appear as boxes, and the artifacts allocated to each node appear as rectangles within the boxes.
Nodes may have sub nodes, which appear as nested boxes.
It has set of computational nodes
It is the physical deployment of software element.
Two types of computational nodes
i)Device node
It is the physical computing resource.And it has processing and memory services to
execute the software.
ii)EEN(Executive Environment Node)

34

It is the software computing resoursethat runs with a nodeIt provides services to host
and execute the software elements.
11.6 DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this diagram is the foreign trading system. The devices are the trader
and administrator who perform the main activities in the system.

11.7 DRAWING THE DEPLOYMENT DIAGRAM

35

Fig 9: UML Deployment Diagram

36

CHAPTER 12
CONCLUSION
This project is to scientifically approach the foreign exchange market, and to
evaluate whether we can develop a strategy that can automatically trade in the market
successfully, and can outperform existing basic strategies. As the forex market and the number of
individual retail investors grows, a new, successful strategy is valuable to those seeking financial
prosperity by trading currencies.
Our approach was to first understand the various overall market conditions- trending,
directionless, and volatile. This is crucial, since different trading strategies prove appropriate for
differing market conditions. After determining the type of market, we tested basic strategies and
examined their performance. After optimizing these systems, we discovered the best approach
would be to develop our own system, incorporating the most successful features from several
strategies, and come up with a strategy that greatly outperformed the basic ones we had tested.