Professional Documents
Culture Documents
Topic Page No
General Market......................................................................................4
Objective...............................................................................................5
Identification Of Need...........................................................................5
Software Requirements.................................................................17
Hardware Requirements................................................................17
Why Java Server Pages (Jsp)...............Error: Reference source not found17
Features Of Javaserver Pages..............Error: Reference source not found18
Features Of Sql Server 2000................Error: Reference source not found19
Jdbc.....................................................................................................19
User Interface.....................................................................................20
Customer Module.................................................................................21
Company Module.................................................................................22
Registration Module.............................................................................22
Feedback Module.................................................................................23
Customer..........................................................................................26
Share................................................................................................27
Page 2 of 40
Company...........................................................................................28
Feedback..........................................................................................29
Error Messages.................................................................................30
Designing Of System............................................................................30
Data Design......................................................................................40
Development Of Software.................................................................43
Development Of Front-End.................................................................45
Development Of Back-End..................................................................74
Developing Law’s Of Software.............................................................77
Performance Requirements.................................................................77
Code Efficiency:..............................................................................273
Code Optimization:..........................................................................273
System Implementation.....................................................................280
Conclusion.........................................................................................282
Bibliography......................................................................................288
Glossary............................................................................................289
GENERAL MARKET
This is a portal designed to facilitate companies and customers who deals in
direct equity market to come online and do transactions.
Main motto of the clinic is to provide the buyers and sellers of equity a common
platform where they can transact fast and securely using latest web technologies
all that with “any time any where” feature.
OBJECTIVE
I am developing this portal for companies who want to sell shares and for the
customers who want to buy these shares. This portal helps in financial dealing
So, we can say that it will help the companies as well as customers to buy share
and sel share with the spead of light. It will also help in stock monitoring
according to predefine format
This portal will help in getting the current sale and purchase status of shares of
to a particular company.
Customers will have this advantage buying share at “CURRENT RATE” and
exactly when they want to but because we all know how swifty market rate
changes.
IDENTIFICATION OF NEED
DRAW BACK IN EXISTING SYSTEM
1. Existing system was slow and man driven , was also involving to much of
paper work.
2. As a broker I can always handle transactions of 4 ot 5 companies but once it
goes beyond that and that too with large number of buyers and sellers I
would certailnt need a some technological help. And that is precisely this
system is being dsigned.
3. Security of transaction over the telephone was again a major issue.
4. Searching the detail of any customers was very difficult, as the user has to
go through all the books thoroughly.
5. Manual entries have made jobs person dependent, no one can help the user
except that person who is handling that portion of job.
6. Person dependent jobs lead to delay in transaction and increase the
processing time to a great amount.
7. Existing system has sorting and filtering features since all records are
chronologically entered date wise on the day they happened.
8. Communication with customers was really difficult as searching address and
pone numbers was really a cumbersome task.
9. Customers enquiries takes longer time since searching records has a high
response time.
10. Stock inventor management dose not seems to be solving any purpose, since
there were no ready comparison available when management wants them.
PROPOSED SYSTEM
The basic aim in the new proposed system was to provide improvised
functionality and flavor of the existing system minus all the drawbacks or short
coming analyzed.
With the front end like JAVA SERVER PAGES and back end MS SQL Server
2000 major bottlenecks of conventional file system, would be removed without
major efforts .The advantage that accrue from having centralized control of data
are as follows:
• Data Redundancy would be removed.
• Simultaneous data access would be possible in multi-user
enviournment
• Standards can be enforced.
• Security restrictions could be applied.
• Backup can be maintained.
• Integrity can be maintained.
• Conflicting requirement could be balanced.
The proposed system allow easy handling and management thru
menu driven applications in GUI enviournment.
1. Registration
2. Login
3. Feedback
4. FAQ’s
2) Customer Module
o Buy Share
o Sell Shares
o Contact companies
o Give feedback.
3) Company Module
o Shares listing
o Feedback
4) Registration Module
6) Feedback Module
o Buy Shares
o Sell Shares
o Change requisition
Business modeling:
Business modeling solves the following question in our project.
o What information drives the business process?
o What information is generated?
o Where does the information go?
o Who process it?
The goal of business process engineering is to define architectures that will
enable a business to use information effectively.
In our project I have determined three different architecture of
business objective and goals:
• data architecture
• application architecture
• technology architecture
Data architecture
The data architecture provides framework for our project, to develop
a business function. The individual building blocks of the
architecture are the data objects that are used by the business.
Data objects contain a set of attributes that define some aspect,
quality, characteristics, or descriptor of the data that are being
described.
Once a set of data objects is defined, their relationships are
identified. A RELATIONSHIP indicates how objects are connected to
one another.
Example:
Now I am describing only one example of relationship among
all the relationship, consider the
Application architecture:
In this concept we determine those element that transform objects
within the data architecture for some business purpose. We consider
the relationship architecture to be the system of program that
performs this transaction.
Technology infrastructure:
The Technology infrastructures provide the foundation for the data
and application architectures. This includes computers, operating
systems, network, and links storage.
DATA MODELING:
The information flow defined as part of the business
modeling phase is refined into a set of data objects that are needed
to support the business .the characteristics (called attributes) of
each object are identified and the relationship’s between these
objects defined.
In our project first we concentrate to establish the following
points
i) data objects
ii) attributes
iii) relationship
Data object:
In this project the data object is a representation of any
composite information that must be understand by software. By
COMPOSITE INFORMATION, we mean something that has a number
of different properties or attributes.
Data object can be external or internal (i.e., anything that
produce or consumes information) data object encapsulates data
only there is no reference within a data object to operations that act
on the data. Therefore the data object can be represent as a table
as below. The table reflects attributes of the object .In this case, a
item is defined in term of ShareId, ShareCategory,
mktval,CompanyName .
Attributes:
Attributes define the properties of a data object.
Attribute names, describe its characteristics, and in some cases,
make reference to another object.
Relationships:
Relationships indicate the manner in which data
object are “connected” to one another.
Now we will explain the relation with the help of our project
component, for example we consider two data object , Company and
customer. These objects can be represented using the simple
notation as below:
PROCESS MODELING:
After defining the data in data modeling phase. I have transformed
the data to achieve the necessary information for implementing a
business function. Processing descriptions are created for adding,
modifying, deleting, or retrieving a data object.
Application generation:
RAD assumes the use of fourth generations. Rather than creating
software using conventional third generation programming language
the RAD process works to reuse existing program components or
create reusable component. In all cases automated tools are used to
facilitate construction of the software.
Business
Modeling
Business Data
Modeling Modeling
Process
Modeling
Data
Modeling Application
Generation
Testing &
Turnover
Process
Modeling
Application
Generation
Testing
&
Turnover
Near about 180 days
SOFTWARE AND HARDWARE REQUIREMENT
SPECIFICATION
Hardware Requirements
1) MICROPROCESSOR: PENTIUM - 100 MHz or above.
2) HARD DISK SPACE: Minimum 50 MB for installation and
running.
3) RAM: 32 MB RAM or above for fast execution and reliability.
Software Requirements
Server – Apache Tomcat 5.0/websphare (any web server which
support JSP)
PLATFORM: Windows 9x,Windows NT, Windows XP,linux,solaris.
Driver: ODBC Driver
Database Server: Microsoft SQL Server2000.
Some highlights
• Portability across platforms and servers
• Robust exception management and memory management
• Access to the wide range of Java APIs (JDBC, JavaMail, etc.)
• Portable, reusable logic components
• High performance for multiple concurrent requests
• Easy deployment and maintenance
Features of JavaServer Pages
o Reusable Components
o The same database engine can be used across platforms ranging from
laptop computers running Microsoft Windows® 98 through large,
multiprocessor servers running Microsoft Windows 2000
o Summary data for online analytical processing. SQL Server also includes
tools for
o Visually designing databases and analyzing data using English-based
questions.
JDBC
User Interface
This page is the first page of the web site allows you to select your path to
the different section of the web site.
As a customer/Company you can directly logon to the site from here and do
further operations.
It allows first level of log on only for doing transaction you need to further
logon using your company/customer ID’s.
1. Registration
2. Login
3. Feedback
2) Customer Module
Once you login on to the site as customer you can browse site’s
different sections and also perform transactions like buying and
selling of shares, securities and bonds.
But to be able to perform transactions you need to further logon using your
customer Id and password.
o Buy Share
o Sell Shares
o Contact companies
o Give feedback.
3)Company Module
Once you logon as a company you can do transactions on the site. You can
enlist new sharer delete old once and allow and reject share applications.
o Shares Details
o Feedback
4) Registration Module
This screen allows you create new login ids for the site. Both customers and
company’s can give their personal and professional details to become the
member of the site.
You also need to enter you payment details by which you’ll pay your
registration fees.
Most importantly it generate your secret ID which allows you to logon to the
site to perform transaction.
5) Share listing Module
Here both company and Customer to see the current situation of the market
and latest share prizes.
Here company’s can update share prizes and see what it need to do to cope
up with the current marker scenario.
Customers can come here and compare share of different companies , go and
buy or sell their shares.
6) Feedback Module
A small but very important module whish is the only interaction between
customer and client and site owners.
Customers can give requisition to buy and sell shares to companies and to
brokers.
They can further go down and check their buying and sell history.
o Buy Shares
o Sell Shares
o Change requisition
DATA FLOW DIAGRAMS
ShareBazar DB
2. Admin
1. User Login
Process
3. User
Main Screen /
Client Homepage
Select
Select
Login
Select Select
Registeration
Feedbac
USTOME
FAQ
k
Authenticate
C
Fetch &
Store Fetch
Seller Buyer
Customer
CustomerMaster
Add
Add Share
ShareListing Sharee
Category
Store Sold
Save
&
Delete
Share_List
Company
ShareList Company_Master
Customer’s
Feedback DayEnd
Fetch records Feedback ShareList
Feedback Fetch records
ShareList
Buying Details
Selling Details
Fetch records Fetch records
Seller Buyer
CategoryWise
Share Summary
Share Details
ShareList CatWiseShareDetails
• when any field is blank then gives error message, the field
is blank
• When we input character in numeric field then give error
message.
• When the data is less than or grater than range then gives
error message.
• When unauthorized person access the data or any matter
then gives error message.
• At searching when code is not matching then error the code
is present.
DESIGNING OF SYSTEM
The design of the information system produce the detail that
state how a system will meet the requirement identified during
system analysis often refer to this stage as logical design, in
contrast to the process of developing program software, which
is referred to as physical design.
Design objectives:
The following goals were kept in mind while
designing the new system:
i) To reduce the manual works required to be done in the
existing system.
ii) To avoid errors inherent in the manual works and hence
make the output consistent and correct.
iii) To improve the management of permanent information of
the company by keeping it is properly structured tables
and to provide facilities to update this information as
efficient as possible.
iv) To make the system complete menu-driven and hence
user-friendly. This is necessary so that even non-
programmers could use the system effectively and system
could act as catalyst in achieving objective.
v) To make the systems compatibility i.e. it should “fit in” in
the total, integrated system.
vi) To design the system in such a way that reduces feature
maintenance and enhancement times and efforts.
vii) To make the system reliable, understandable and cost
effective.
Design overview:
The design stage takes the final specification of the system
from analysis and finds the best way of fulfilling them, give the
technical environment and previous decision on required level
of automation.
The system design is carried out in two phase:
iii) Normalization:
The entities were normalized. After first
and second normalization go to bcnf was achieved for all the
entities of systems.
i v ) I n t e r fa c e :
Interfacing with other system was done and
attributes related to external entities were identified.
Once the entities and their attributes were defined, entity
relationship diagrams.
Module design:
This screen is used to enter module information
during the design stage of business system development. The
application systems, function, tables and columns must already
exist in CASE* dictionary before being referenced.
User preferences:
Based on user preference like form name,
validation of primary key, layout of forms, layout of fields.
Creating title for forms, mandatory input field prompts etc. was
incorporated here.
Program specification:
The program specifications were written
for the master, transaction, report, and queries. The logic for
each fields, from were so that anyone who does not know
system will be able to code the logic. Field validations and
user-friendly error message were written as a part of the
program specification.
This is done mainly for two reasons:
1) Saving the development time
As the procedures will be common to many
programs, the development time be saved substantially by
keeping.
2) Testing become easier
As the procedures become an independent
entity, it can be easily tested.
DESIGN DECISION:
The system has been decided to develop on
Java Server Pages and Java Script and back-end SQL Server
2000.
SQL Server 2000 has been chosen since the system has
the following requirement and it categorized all:
1. Large database and space management control
Java Server Pages and
Java Script and back-end SQL Server 2000 supports the large
amount of database. It stores the data in the form of tables
making optimal use of the available storage. To make efficient
use of expensive hardware devices, it fulls control of space
usage.
2. Many concurrent database users
Front-end Java Server Pages and
Java Script and back-end SQL Server 2000 support large
number of concurrent users existing a variety of database
application operating on the same data.
3. High transaction processing performance
Java Server Pages and
Java Script with back-end SQL Server 2000 maintains the
preceding features with a high degree of overall system
performance. Database user does not suffer slow processing
performance.
4. Controlled availability
SQL SERVER 2000 can
selectively control the availability of data, at the database level
and sub-database level. For example, an administrator can
disallow use of a specific application so that applicant’s data
can be related, without affecting other application
ENTITY RELATIONSHIP DIAGRAM
Na
Name m Address
Phone_R
e
CustomerMaster
Income
Cid Lognam
e
CanBe
Seller
Cid
Type_Share
Company_Nam
e No_Of_Sha
res
Can
Be
Cid
Buyer
Company_Nam
e
Rate_Per_Shar
No_Of_Share e
has
CBalance
Card_Hol
Cid der_Nam
e
Mod_of_Paym
Cheque_N
o
Give
s
Feedback
Name Comment
Email
Profile
Cid CompanyMaster
Compan
y_Name
Launc
h
Check
ssssss
ss
Share_Category
Share_List
Share_
Mkt_Va
Id
l
C_ID Face_Val
Company _
Name
CustomerMaster
CompanyMaster
Name varchar (20) NOT NULL ,
Address varchar (50) NOT NULL ,
City varchar (10) NOT NULL ,
State varchar (10) NOT NULL ,
Country VarChat(10) NOT NULL
Pincode varchar (7) NOT NULL ,
Phone varchar (10) NOT NULL ,
Fax Varchar(10) NOT NULL
Email varchar (25) NOT NULL ,
Personcon varchar (15) NOT NULL ,
Logname varchar (10) NOT NULL ,
Pwd Varchar(10) NOT NULL ,
Combackground IVarchar(100) NOT NULL,
memID VarChar(10) NOT NULL ,
sno Int NOT NULL
SELLER
Cid varchar (10) NOT NULL ,
CompanyName varchar (20) NOT NULL ,
No_of_Share Int NOT NULL ,
Type_Share varchar (20) NULL ,
Party_Name varchar (20) NULL ,
Date datetime NULL ,
Fax varchar (12) NULL ,
ContactPerson varchar (50) NULL ,
Mobile varchar (20) NULL ,
Email varchar (50) NULL
Buyer
Cid varchar (10) NOT NULL ,
Company_Name varchar (20) NOT NULL ,
No_of_Share Int NOT NULL ,
Type_Share varchar (20) NULL ,
Party_Name varchar (20) NULL ,
Rate_per_Share Int NOT NULL ,
Date datetime NULL
Feedback
Name varchar (10) NOT NULL ,
Email varchar (100) NOT NULL ,
Comment varchar (100) NOT NULL ,
Date Date NOT NULL
ShareMaster
memID char (10) NOT NULL ,
comName varchar (15) NOT NULL
Qty Int NOT NULL
Rate float NOT NULL ,
Type char (1) NOT NULL ,
issueDate Date NOT NULL ,
balance Int NOT NULL ,
Sno Int NOT NULL
Contact
comName varchar (15) NOT NULL ,
Email varchar (25) NOT NULL ,
Phone Varchar(10) NOT NULL
Reason varchar (100) NOT NULL ,
Date Date NOT NULL ,
Conclusion
The E-stock.com is looking forward to a more
efficient and streamlined processing system and better
coordination between customers and the finance leading to
desired results in terms of quality, service, profits, market,
share and competitive ness.
BIBLIOGRAPHY