Está en la página 1de 79

A

Project Report
ON

SHAREBAZAR.COM
Submitted By
ATUL KUMAR (0709513008)
RISHABH UPADHYAY (0709513042)
SAURABH DUA (0809533057)
Submitted to the department of Information Technology
In partial fulfillment for the mini project lab
Of
BACHELOR OF TECHNOLOGY
IN
INFORMATION TECHNOLOGY

Mahatma Gandhi Mission’s


College of Engineering & Technology
A-9, Sector -62, NOIDA (U.P.)

GAUTAM BUDDH TECHNICAL UNIVERSITY: LUCKNOW

2010-2011

1
DECLARATION

we hereby declare that this submission is our own work and that, to the best of my knowledge
and belief, it contains no material previously published or written by another person nor material
which to a substantial extent has been accepted for the award of any other degree or diploma of
the university or other institute of higher learning, except where due acknowledgment has been
made in the text.

2
CERTIFICATE

This is to certify that project report entitled “SHARE BAZAR.COM ” which is submitted by
“SAURABH,RISHABH,ATUL” in partial fulfillment of the requirement for the mini project lab
in fifth semester of B.Tech. in Information Technology of Gautam Buddh Technical University,
is a record of candidate own work carried out by them under my supervision..

(Mrs. Anuradha)
SUPERVISOR
MGMCOET,
Noida, U.P.

3
ACKNOWLEDGEMENT

It gives us a great sense of pleasure to present the report of the mini project undertaken during B.
Tech, Third year. We owe special debt of gratitude to Mrs. Anuradha, Department of
Information Technology & Engineering, Mahatma Gandhi Mission’s College Of Engineering
And Technology, Noida for his constant support and guidance throughout the course of our
work.
We also do not like to miss the opportunity to acknowledge the contribution of all faculty
members of the department for their kind assistance and cooperation during the development of
our project. Last but not the least, we acknowledge our friends for their contribution in the
completion of the project.

SAURABH DUA (0809533057)


RISHABH UPADHYAY(0709513042)
ATUL KUMAR (0709513008)

4
ABSTRACT

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. This portal is 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 sell share
more quickly. 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 buy because market rates keep on changing frequently.

5
TABLE OF CONTENTS

TITLE PAGE NO.


LIST OF FIGURES……………………………………………………………………………………………..08
LIST OF TABLES………………………………………………………………………………………..........09
CHAPTER 1: INTRODUCTION………………………………………………………………………………10-13
1.1) - General Market
1.2) - Registration Of New Customer
1.3) - Selling Share On-Line
1.4) - Buying Share On-Line
1.6) - Share Listing
1.7) - Objective
1.8) - Identification of Need

CHAPTER 2: FEASIBILITY STUDY…………………………………………………………………..……14-15


2.1) - Technical Feasibility
2.2) - Operational Feasibility
2.3) - Economic Feasibility

CHAPTER 3: SOFTWARE REQUIREMENT SPECIFICATIONS……………………………………….16-18


4.1) - Phases of SRS
4.2) - Format of SRS
4.3) - Software Requirement
4.4) - Hardware Requirement
4.5) - Why Java Server Pages (Jsp)
4.6) - Features Of Java server Pages
4.7) - Features Of Sql Server 2000

CHAPTER 4: SYSTEM DEVELOPMENT METHODOLOGIES…………………………………………..19-22


5.1) - Software Development Life Cycle
5.1.1) - SDLC Phases
5.1.2) - SDLC Objectives
5.2) Waterfall Model

CHAPTER 5: SYSTEM TESTING……………………………………………………………………………...23-26


6.1) Testing Objectives
6.2) Goals of Testing
6.3) Unit Testing
6.4) Integration Testing
6.5) System Testing
6
6.6) Levels of Testing

CHAPTER 6: IMPLEMENTATION…………………………………………………………..…………………27

CHAPTER 7: MODULE DESCRIPTION……………………………………………………………………….28-41


User Interface
Home Page Screen
Customer Module
Company Module
Registration Module
Share Listing Modul
Feedback Module
Buy & Sell Module
Data Flow Diagrams
Entity Relationship Diagram
Designing of the system
Data design

CHAPTER 8: SYSTEM SECURITY……….………………………………………………………………….42-43


9.1) Physical Security
9.2) Data Security
9.2.1) Identification
9.2.2) Authentication
9.2.3) Authorization
9.3) Need For Security

CHAPTER 09: SCREEN SHOT………………………………………………………………………………...44-72

CHAPTER 10: COST ESTIMATION…………………………………………………………………………..73-76


10.1) - Cost Estimation Of The Project
10.2) - Pert Chart, Gantt Chart:

CHAPTER 11: Scope Of Future Enhancement……………….………………………………………………77


CHAPTER 12: CONCLUSION……………………………………………………………………………………78
CHAPTER 13: BIBLIOGRAPHY…………………………………………………………………………………79

7
LIST OF FIGURES

Fig.1: Relationship Diagram_________________________________________________


Fig.2: Testing and turnover diagram___________________________________________
Fig.3: Level 0 dfd for share bazaar.com_________________________________________
Fig.4: Level 1 dfd for share bazaar.com_________________________________________
Fig.5: Level 2 dfd for share bazaar.com_________________________________________
-- Level 2 dfd for share bazaar.com(main screen)___________________________
-- Level 2 dfd for share bazaar.com(customer)_____________________________
-- Level 2 dfd for share bazaar.com(share)________________________________
-- Level 2 dfd for share bazaar.com(company)_____________________________
Fig.6: E-R diagram________________________________________________________
Fig.7: Waterfall model_____________________________________________________
Fig.8: Prototype model of system testing_______________________________________
Fig.9: Level of testing______________________________________________________
Fig.10: Pert chart_________________________________________________________

8
LIST OF TABLES

Table 1: Data design


Table 1.1: Customer master
Table 1.2: Company master
Table 1.3: Seller
Table 1.4: Buyer
Table 1.5: Feedback
Table 1.6: Share master
Table 1.7: Contact

9
CHAPTER 1 – INTRODUCTION

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. System perform following function

o Registration of New Customer


o Selling Share On -Line
o Buying Share On -Line
o Share Listing

Registration of New Customer

This part covers up the registration of new customer into our website and
providing other details to customers. It also provides different links to get information
about ShareBazar.

Selling Share On-Line : This part covers up online trading i.e selling of share to a
specified customer at a listed price which is given in ShareListing.

Buying Share On -Line: This part covers up online trading i.e buying of share from a
specified customer at a listed price which is given in ShareListing.

Share Listing: This part covers up the detailed listing of shares like type of
share,name of the company,their respective price and availability of shares for trading.

10
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

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. Security of transaction over the telephone was again a major issue.
3. Searching the detail of any customers was very difficult, as the user has to go through all the books
thoroughly.
4. Manual entries have made jobs person dependent, no one can help the user except that person who is
handling that portion of job.
5. Person dependent jobs lead to delay in transaction and increase the processing time to a great
amount.
6. Existing system has sorting and filtering features since all records are chronologically entered date
wise on the day they happened.
7. Communication with customers was really difficult as searching address and pone numbers was really
a cumbersome task.
8. Customers enquiries takes longer time since searching records has a high response time.
9. 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 possib le in multi-user enviournment

11
 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.
The proposed system can be summarized as

Since every information is available at click of a button there is no need to maintain


lethargic paper reports.

System has separate modules named as:


1) Home Page screen
1. Registration
2. Login
3. Feedback
4. FAQ’s
2) Customer Module
o Buy Share
o Sell Shares
o Edit your details
o Check listing of shares
o Contact companies
o Give payments online
o Give feedback.
3) Company Module
o Shares listing
o Change login details

12
o En-list Share holders
o Delete old share listings
o Change his profile
o Change share rates
o Feedback
4) Registration Module
5) Share listing Module
6) Feedback Module
7) Buy and Sell Module
o Buy Shares
o Sell Shares
o See buying history
o See selling history
o Change requisition

13
CHAPTER 2- FEASIBILITY STUDY

FEASIBILITY STUDY
Feasibility is the determination of whether or not a project is worth doing the process followed making this
determination is called feasibility study. This of determines if a project can and should be taken. Once it has
been determined that a project is feasible, the analyst can go ahead and prepare the project specification
which finalizes project requirements. Generally, feasibility studies are undertaken within right time
constraints and normally culminate in a written and oral feasibility report. The contents and
recommendations of such a study will be used as a sound basis for deciding whether to proceed, postpone
or cancel the project. Thus, since the feasibility study may lead to the commitment of large resources, it
becomes necessary that it should be conducted competently and that no fundamental errors of judgment
are made.
There are following types of inter -related feasibility. The are:
i) Technical feasibility
ii) Operational feasibility
iii) Economic feasibility

Technical feasibility:
This is concerned with specifying equipment and software and hardware that will successfully satisfy the
user requirement. The technical needs off the system may vary considerably, but might include:
 The facility to produce output in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.

According to the definition of technical feasibility the compatibility between front-end and back-end is very
important. In our project the compatibility of both is very good. The degree of compatibility of JSP and SQL

14
Sever 2000 is very good. The speed of out put is very good when we enter the data and click button then
the response time is very fast and give result very quickset. I never find difficulty when we use complex
query or heavy transaction. The speed of transaction is always smooth and constant. This software
provides facility to communicate data to distant location.

Operational Feasibility:
It is mainly related to human organizational and political aspects. The points to be considered are:

 What changes will be brought with the system?


 What organization structures are disturbed?
 What new skills will be required? Do t he existing staff members have these
skills? If not, can they be trained in due course of time?

At present stage all the work is done manually. So, throughput and response time is too much. Major
problem is lack of security check that should have been applied. Finding out the detail regarding
customer’s transaction was very difficult, because data store was in different books and different places. In
case of any problem, no one can solve the problem until the person responsible is not present.

Current communication is entirely on telephonic conversation or personal meetings. Post


computerization staff can interact using internet.

Economic feasibility

At present Company has ten systems with following configuration:


o Ram 32 MB or above for fast execution and reliability
o P-III 100MHz or above
o MOTHER Board 810
o Color Monitor 14” and 17”
o Hard Disk 10 / 40 GB
Hence the economical feasibility is very

15
CHAPTER 3
SOFTWARE REQUIREMENT SPECIFICATIONS

SOFTWARE REQUIREMENT SPECIFICATION

A SRS document or Software Requirements Specification document is an important textual


document between the end user and the developer. The software requirement specification is
produced after the culmination of the feasibility analysis phase. The function and performance
allocated to software as part of system engineering are defined by establishing a complete
information description, a detailed functional description and a presentation of a system
behavior, an indication of performance requirements and design constraints, appropriate
validation criteria, and other information pertinent to requirements.

Software requirements specifications is a document that completely describes what proposed


software would do? The basic goal of requirements phase is produced software requirements
specification document, which describes complete external behavior of proposed software. The
basic limitation of this is that the user needs to change with the environment in which system
was to function changes with time. Good software requirements specification job should be done
in requirements phase to produce high quality and stability.

As systems grew more complex, it became evident that the goals of the entire system cannot be
easily comprehended. Hence the need for the requirement analysis phase arose. Now, for large
software systems, requirements analysis is perhaps the most difficult activity and also the most
error prone.

Some of the difficulty is due to the scope of this phase. The software project is initiated by the
client’s needs. In the beginning these needs are in the minds of various people in the client
organization. The requirement analyst has to identify the requirements by talking to these people
and understanding their needs. In situations where the software is to automate a currently manual
process, most of the needs can be understood by observing the current practice.
16
The SRS is a means of translating the ideas in the minds of the clients (the input), into formal
document (the output of the requirements phase). Thus, the output of the phase is a set of
formally specified requirements, which hopefully are complete and consistent, while the input
has none of these properties.

3.1) PHASES OF SRS:


 Problem recognition
 Evaluation and synthesis of this problem
 Modeling of the SRS (System Requirements Specification) document
 Review

3.2 ) FORMAT FOR SRS:


 Introduction
 Information Description
 Functional Description
 Behavioral Description
 Validation Criteria

SOFTWARE and HARDWARE REQUIREMENT SPECIFICATION

Hardware Requirements
MICROPROCESSOR: PENTIUM - 100 MHz or above.
HARD DISK SPACE: Minimum 50 MB for installation and running.
RAM: 32 MB RAM or above for fast execution and reliability.

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

18
CHAPTER 4
SYSTEM DEVELOPMENT METHODOLOGIES

SYSTEM DEVELOPMENT METHODOLOGY


5.1) SYSTEM DEVELOPMENT LIFE CYCLE:
5.1.1) SDLC Phases:
Initiation Phase:
The initiation of a system (or project) begins when a business need or opportunity is identified. A Project
Manager should be appointed to manage the project. This business need is documented in a Concept
Proposal. After the Concept Proposal is approved, the System Concept Development Phase begins.

System Concept Development Phase:


Once a business need is approved, the approaches for accomplishing the concept are reviewed for
feasibility and appropriateness. The Systems Boundary Document identifies the scope of the system and
requires Senior Official approval and funding before beginning the Planning Phase.

Planning Phase:
The concept is further developed to describe how the business will operate once the approved system is
implemented, and to assess how the system will impact employee and customer privacy. To ensure the
products and /or services provide the required capability on-time and within budget, project resources,
activities, schedules, tools, and reviews are defined. Additionally, security certification and accreditation
activities begin with the identification of system security requirements and the completion of a high level
vulnerability assessment.

Requirements Analysis Phase:


Functional user requirements are formally defined and delineate the requirements in terms of data, system
performance, security, and maintainability requirements for the system. All requirements are defined to a
level of detail sufficient for systems design to proceed. All requirements need to be measurable and
testable and relate to the business need or opportunity identified in the Initiation Phase.
Design Phase
19
The physical characteristics of the system are designed during this phase. The operating environment is
established, major subsystems and their inputs and outputs are defined, and processes are allocated to
resources. Everything requiring user input or approval must be documented and reviewed by the user. The
physical characteristics of the system are specified and a detailed design is prepared. Subsystems
identified during design are used to create a detailed structure of the system. Each subsystem is partitioned
into one or more design units or modules. Detailed logic specifications are prepared for each software
module.

Development Phase
The detailed specifications produced during the design phase are translated into hardware,
communications, and executable software. Software shall be unit tested, integrated, and retested in a
systematic manner. Hardware is assembled and tested.

Integration and Test Phase


The various components of the system are integrated and systematically tested. The user tests the system
to ensure that the functional requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system. Prior to installing and operating the system in a production
environment, the system must undergo certification and accreditation activities.

Implementation Phase
The system or system modifications are installed and made operational in a production environment. The
phase is initiated after the system has been tested and accepted by the user. This phase continues until the
system is operating in production in accordance with the defined user requirements.

Operations and Maintenance Phase


The system operation is ongoing. The system is monitored for continued performance in accordance with
user requirements, and needed system modifications are incorporated. The operational system is
periodically assessed through In-Process Reviews to determine how the system can be made more
efficient and effective. Operations continue as long as the system can be effectively adapted to respond to
an organization’s needs. When modifications or changes are identified as necessary, the system may
reenter the planning phase.

20
5.1.2) SDLC Objectives:
This guide was developed to disseminate proven practices to system developers, project managers,
program/account analysts and system owners/users throughout the DOJ. The specific objectives expected
include the following:

 To reduce the risk of project failure


 To consider system and data requirements throughout the entire life of the system
 To identify technical and management issues early
 To disclose all life cycle costs to guide business decisions
 To foster realistic expectations of what the systems will and will not provide
 To provide information to better balance programmatic, technical, management, and cost aspects
of proposed system development or modification
 To encourage periodic evaluations to identify systems that are no longer effective
 To measure progress and status for effective corrective action
 To support effective resource management and budget planning
 To consider meeting current and future business requirements

21
5.2) WATERFALL MODEL:

Fig. 1: Waterfall model

22
CHAPTER 5
SYSTEM TESTING

6.1 TESTING OBJECTIVE


6.2 GOALS OF THE SOFTWARE TESTING
6.3 UNIT TESTING
6.4 INTEGRETION TESTING
6.5 SYSTEM TESTING
6.6 ACCEPTANCE TESTING
6.7 LEVEL OF TESTIN

SYSTEM TESTING

6.1) TESTING OBJECTIVE:

The aim of the testing process is to identify all defects existing in a software product. Testing a program
consists of subjecting the program to a set of test inputs and observing if the program behaves as
expected. If the program fails to behave as expected, then the conditions under which failure occurs are
noted for later debugging and correction.

The main objective of testing is to finding a host of errors, systematically and with minimum effort and time.
We can say as follows:

 Testing is a process of executing a program with the intent of finding an error.


 A good test case is one that has a high probability of finding error, if it exists.
 The tests are inadequate to detect possibly present errors.
 The software should be based on the quality and reliable standards.

23
 Uncover as many as errors (or bugs) as possible in a given timeline.
 Demonstrate a given software product matching its requirement specifications.
 Validate the quality of software testing using the minimum cost and efforts.

6.2) GOALS OF SOFTWARE TESTING:

Uncover the errors (defects) in the software, including errors in:


 Requirements from requirement analysis.
 Design documented in design specifications.
 Coding (implementation).
 System resources and system environment.
 Hardware problems and their interfaces to software.

6.3) UNIT TESTING:

The testing of different units or modules of a system in isolation as it makes debugging easier. Unit testing
focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the
process specifications, testing is done to uncover errors within the boundary of the module. All modules
must be successful in the unit test before the start of the integration testing begins.

In this project each service can be thought of a module. There are so many modules like administrator,
user, visitor. Each module has been tested by giving different sets of inputs. When developing the module
as well as finishing the development, the module works without any error. The inputs are validated when
accepting them from the user.

6.4) INTEGRATION TESTING:

After unit testing, we have to perform integration testing. The goal here is to see if modules can be
integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be
considered as testing the design and hence the emphasis on testing module interactions.

24
In this project the main system is formed by integrating all the modules. When integrating all the modules I
have checked whether the integration effects working of any of the services by giving different
combinations of inputs with which the two services run perfectly before integration.

6.5) SYSTEM TESTING:

System testing involved is the most widely used testing process consisting of five stages as shown in the
figure. In general, the sequence of testing activities is component testing, integration testing, and then user
testing. However, as defects are discovered at any one stage, they require program modifications to
correct them and this may require other stages in the testing process to be repeated.

Fig. 10: Prototype model of system testing

Here the System testing involved is the most widely used testing process consisting of five stages as
shown in the figure. In general, the sequence of testing activities is component testing, integration testing,

25
and then user testing. However, as defects are discovered at any one stage, they require program
modifications to correct them and this may require other stages in the testing process to be repeated.

System tests are designed to validate a fully developed system to assure that it meets its requirements.
Three main kinds of system testing:
i. Alpha testing: Alpha testing refers to the system testing carried out by the test team within
the developing organization.
ii. Beta testing: Beta testing is the system testing performed by a select group of friendly
customers.
iii. Acceptance testing: The system testing performed by the customer to determine whether
to accept or reject the delivery of the system.

6.6) ACCEPTANCE TESTING:

Acceptance Testing is performed with realistic data of the client to demonstrate that the software is working
satisfactorily. Testing here is focused on external behavior of the system of the internal logic of program is
not emphasized.

Test cases should be selected so that the largest number of attributes of an equivalence class is exercised
at once. The testing phase is an important part of software development. It is the process of finding errors
and missing operations and also a complete verification to determine whether the objectives are met and
the user requirements are satisfied.

6.7) LEVELS OF TESTING:

In order to finding the errors present in different phases, we have the concept of levels of testing. The basic
levels of testing are:

Client Needs Acceptance Testing

Requirements System Testing

Integration Testing
Design

Code Unit Testing


26
CHAPTER 6

IMPLEMENTATION

IMPLEMENTATION

System implementation is the stage when the user has thoroughly tested the system and approves
all the features provided by the system. The various tests are performed and the system is approved only
after all the requirements are met and the user is satisfied.

The new system may be totally new, replacing an existing manual or automated system, or it may be a
major modification to an existing system. In case of, proper implementation is essential to provide a reliable
system to meet organizational requirements. Successful implementation may not guarantee improvement
in the organization using the new system, but improper will prevent it.

Implementation is the process of having systems personnel check out and put new
equipment into use, train users, install the new application and construct any file s of
data needed to use it. This phase is less creative than system design. Depending on
the size of the organization that will be involved in using the application and the risk
involved in its use, systems developers may choose to test the operation in on ly one
area of the firm with only one or two persons. Sometimes, they will run both old and
new system in parallel way to compare the results. In still other situations, system
developers stop using the old system one day and start using the new one the ne xt.

27
CHAPTER 7
MODULE DESCRIPTION

User Interface

System has separate User Interface modules namely:

1) Home Page screen


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.

It provide some important links along with other like…

1. Registration
Allows customer to give their details and create accounts.
2. Login
Allows first level of of login validation to site.
3. Feedback
Customers and company’s can give feedback to site etc.
4. FAQ’s
List commonly asked questions and their solutions to, and also allow customers and client
to ask new queries.

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.
28
As a customer you can do the following

o Buy Share
o Sell Shares
o Edit your details
o Check listing of shares
o Contact companies
o Give payments online
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.

As similar to customer you need to re logon by giving you secret company id and password to perform
all the above operations.

Company module allows company to logon for transaction and do the following

o Shares Details
o Change login details
o En-list Share Holder
o Delete old share listings
o Change his profile
o Change share rates
o Feedback

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 transacti
29
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.

Feedback Module
A small but very important module whish is the only interaction between customer and client and site
owners.

It allows customers and company’s to give feedback about different portions of the site and what
owners may improve.

Buy and Sell Module


Mostly used by customers to buy and sell their shares.

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.

Customers can do following here.

o Buy Shares
o Sell Shares
o See buying history
o See selling history
o Change requisition

30
Data Flow Diagrams

INPUT DATA PROCESS DISLPAY


DATA RESULTS

ShareBazar DB

Level 0 Data Flow Diagram for ShareBazar.com

2. Admin

1. User Login
Process
3. User

Level 1 Data Flow Diagram for ShareBazar.com

31
MAIN SCREEN (Home Page)

Main Screen /
Client
Homepage

Select
Select
Login
Select Select
Registration

FAQ Feedback
C
Authenticate
Customer Retrieve &
USTO Check
Client ClientMaster
MER
Share
Listing
Sell
Shares Buy Shares

Fetch &
Store Fetch

Seller Buyer

Level 2 Data Flow Diagram for ShareBazar.com

32
Customer

Customer

Add Customer Edit


Customer
Store Edit & Save

CustomerMaster

Level 2 Data Flow Diagram for ShareBazar.com

SHARE

Add
Add Share
ShareListing
Sharee
Category
Store Sold

Delete Share Shares Bought


Category
Edit & Store
Delete Save
Edit & Edit Share
Issue Shares
Save Category
Share_List
ShareTransaction
Rate Buyer & Seller Table

Save
&
Delete

Share_List

Level 2 Data Flow Diagram for ShareBazar.com

33
COMPANY

Company

Add share list Add new


Records Comany
Edit share Edit
list Records company
Store profile
Edit & Save Store
Edit & Save

ShareList Company_Master

Level 2 Data Flow Diagram for ShareBazar.com

34
Feedback

Customer’s
Feedback DayEnd
Feedback ShareList
Fetch records

FEEDBACK
Feedback Fetch records
Selling Details ShareList

Buying Details

Fetch records Fetch records

Seller Buyer

CategoryWise
Share Summary
Share Details

Fetch records Fetch records

ShareList CatWiseShareDetails

Level 2 Data Flow Diagram for ShareBazar.com

35
Entity Relationship Diagram

Address
Name
NanN
Phone_R
Aame
CustomerMaster

Income

Cid
Logname

CanBe

Seller

Cid
Type_Share

No_Of_Shares
Company_Name

ustoeraster
Can
Be

Cid
Buyer

Company_Name

Rate_Per_Share
No_Of_Share

36
37
Profile

Cid CompanyMaster

Company_Nam
e
Launch

Checks
sssssss

Share_Category
Share_List

Share_Id
Mkt_Val

C_ID Face_Val

Company_Name

38
DATA DESIGN
In order to make the Data Design,the data is first analyzed through ER (Entity
Relationship) modeling technique. This technique emphasizes that a database system
for an application is made of entities.An entity is any comprehensive real world
objectthat can be identified. According to its en tities hava relationship with each other
an entity relationship diagram can represent various entities of any system. What
follows next is an ER diagram of the ShareBazar.com. From this we form the data
design,which is explained next,where the data on whic h the code will work will have the
following structure.

CustomerMaster

Initial varchar (4) NOT NULL ,


Name varchar (15) NOT NULL ,
add char (50) NOT NULL ,
City varchar (10) NOT NULL ,
State varchar (10) NOT NULL ,
Country varchar (15) NOT NULL ,
Pincode varchar (7) NOT NULL ,
Email varchar (20) NOT NULL ,
Dob datetime NULL ,
Occupation varchar (10) NOT NULL ,
Incomegroup varchar (15) NOT NULL ,
Phoneoff varchar (10) NOT NULL ,
Mobile varchar (10) NOT NULL ,
Logname varchar (10) NOT NULL ,
Password varchar (10) NOT NULL ,
memID varchar (10) NOT NULL

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 ,
39
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

40
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 ,

41
CHAPTER 8

SYSTEM SECURITY

9.1) PHYSICAL SECURITY


9.2) DATA SECURITY
9.3) NEED FOR SECURITY

SYSTEM SECURITY

One might think that there is a little reason to be concerned about security in an
intranet. After all, by definition an intranet is internal to ones organization outsider
cannot access it. There are strong arguments for the position that an intranet shoul d be
completely open to its users, with little or no security. One might not have considered
ones intranet on any other light.

On the other hand, implementing some simple, built -in security measures in ones
intranet can allow one to provide resources one m ight not have considered possible in
such context. For example, one can give access to some web pages to some people
without them available to entire customer base, with several kinds of authentication.
There are basically two types of security associated with this system:

8.1) PHYSICAL SECURITY :

Damage due to natural causes like earth tremor, flooding, water logging, fire hazards,
atmospheric or environmental conditions etc. For overcoming these difficulties the
replica of the data are automatically stored at various networks and for environmental
conditions air conditioning environment is created.

42
8.2) DATA SECURITY :
There are basically two problems associated with data sec urity:-
 Data not being available to the authorized person at the time of need.
 Data becoming available to the unauthorized person.
To overcome these difficulties the following access facilities has been provided: -
8.2.1) Identification:
Unique Ids for the different users have been provided.
8.2.1) Authentication:
System checks the password under the particular user identification. The
computer permits
the various resources to the authorized person.

8.2.3) Authorization:
The access control mechanism to prevent unauthorized logging to the system.
8.3) NEED FOR SECURITY:

Many people view computer and network security in a negative light, thinking of it only in terms of restricting
access to services. One major view of network security is that which is not expressly permitted is denied.
Although this is a good way of thinking about how to connect other organization to the Internet, one can,
and possibly should, view intranet security from a more positive angle. Property set up, intranet security
can be an enabler, enriching ones intranet with services and resources one would not otherwise be able to
provide.

43
CHAPTER 9
SCREEN SHOT

The following form are used

Home Page

44
This is the Home Page of the ShareBazar.com. From Here Costomer as well as

the Companies can move further or any new customer can make themselves

register with the System.

Login Screen for Customer

This page is used by any user(customer) of the ShareBazar.com viz. End-User,

Supervisor. Any user wanting the access the system resources must have first

45
to validate himself through this page. This page forms a part of security

measures.

Login Screen for Company

This page is used by any user(companies) of the ShareBazar.com viz. End-

User. Any user wanting the access the system resources must have first to

46
validate himself through this page. This page forms a part of security

measures.

Registration Screen

This page is designed for the user to get themselves register with the

ShareBazar.com. Here, they can choose the category under which they want to

get register with it.

47
Company Module

This is the Company module. Here, the companies can see the detail of the

shares they have offered, they can see list of there share holders, they can

48
change rate of the shares, they can delete shares they have offered, they can

contact there shares holders, edit there profile and can give the feedback about

the ShareBazar.com

Customer Module

This the Customer Module.From there customer can Buy the shares of any

company that is already register with the ShareBazar.com and has offered

49
there shares, he can sell his share, he can contact with the companies, can edit

his profile, and can also give the feedback about the ShareBazar.com.

50
Customer registration screen

This is the Customer registeration screen.Customer will fill this form before

registering himself. He need to fill this form completely otherwise a message

will be prompted to him.

51
Edit Customer Profile Screen

This is the customer edit screen. This form will facilitate the customer to edit

his profile. Customer can edit various details entered by him at the time of

registeration except some fields like name, date of birth, Membership ID.

52
Company Registration Screen

This is the company registeration form. Any company who wish to get register

with ShareBazar.com need to fill this form. All fields are necessary on this form

except the fax number.

53
Edit Company login and other Details Screen

This form is for editing the company’s profile. If any company want to make

any change in the profile then this form must be filled by the company to make

the changes permanently. Name and the membership ID can not be changed.

54
Frequently Asked Questions(FAQ)

This is very important form for the uers of the ShareBazar.com. There are some

queries or questions of the users whose answer are there. This is the static

page. It will not accept any uer input or it will not produce any dynamic output

for the users.

55
How it Works Screen

This is the another static page which will not produce any dynamic output for

the users of the ShareBazar.com instead it will help the customers to know the

ShareBazar.com and it will provide all the necessary information to go through

the site.

56
Buy shares screen(Placing requisition )

This screen will facilitate the customer to buy the shares. First of all customer

will select the name of the company whose share he want to buy then the

number, type and rate per share will be produce to the customer for the

selected company. Customer can buy available share buy giving his

membership ID and the transaction password.

57
Sell share screen

This screen will facilitate the customer to sell the shares. First of all customer

will select the name of the company whose share he want to sell then the

number of share will be produce to the customer for the selected company.

Customer can sell available share buy giving his the transaction password.

58
View Shares Detail

This screen will show the detail of the shares of the selected company. If a

company want to see various details associated with its shares then this screen

is provided. Although this is the dynamic page it will produce outout for the

customer but it will not accept any input from the customer.

59
Company Detail screen

This page is for the customers who are interested in to the details of any

particular company. Just by selecting the name of the company the customer

will be provided the details of the seleceted company that will be the static

page. Customer is not allowed to make any change in the company’s details.

60
Terms and condition screen

This is the static page that will show the terms and condition of the

ShareBazar.com

61
Listing Shares Holder screen

This is the static page in the company’s module. It will facilitate the companies

to see the details of the buyer of the shares of their company.

62
Privacy policy screen

This is the another static page which will not produce any dynamic output for

the users of the ShareBazar.com instead it will present the various policies of

the ShareBazar.com to the customers.

63
Market news

This is the one of the most important page in the ShareBazar.com it provides

various resources of the latest news and this is the one of the objective of the

ShareBazar.com to provide its customer up to date news.

64
Make Payment

To get register himself with the ShareBazar.com it is the necessary for the

customer or for the companies to pay Rs. 1000 as the registration fee and the

payment can be done by the customer or by the companies through the credit

card and this page will facilitate to the customer or to the companies to provide

their Name, Card Number, type of the card and the expiry date of the card.

65
Share Details screen

Whenever a company get register with the ShareBazar.com,the company

provides various details associated with the shares such as the number of

shares issued, type of the shares, and the rate of the shares in to this screen.

66
Feedback Screen

This screen is common for the customer as well as companies. This page is

used by the user of the ShareBazar.com to give their valuable comment and

important suggestion about the ShareBazar.com to make it more atteractive.

67
Dos and Don’ts about online share dealing

This is the static page which shows to the user of the ShareBazar.com that

what he can do and what he can not. By looking on this page the user can

understand his limits within the system .

68
Delete Share Listing Screen

At any stage, any company who is already registered with the ShareBazr.com

and has offered its shares to the public can delete some or all of the remaining

shares for that company need to provide number of share to delete and the

transaction password to make the changes permanent.

69
Contact Company Screen

If any customer want to contact any registered company then he needs to

select the name of the company from the combo box that show all the

registered company, and need to provide E-mail ID Phone Number and a strong

reason to contact the company .

70
Change Share Rate Screen

As we know that the rate of the shares changes frequently. So, to change the

rate of the shares, companies must be able to change the rate of the shares as

and when needed. This page allowes to the companies to change the rate of its

shares by giving the transaction password.

71
Membership ID Allocation Screen

This is the common screen for the customer as well as the companies.

Whenever a new customer or a new ompany get register with the

ShareBazar.com he will be provided with the unique Membership ID which will

be generated by our system. Every user has his own unique membership ID

which will be used by the user in the future.

72
CHAPTER 10

COST ESTIMATION
This model estimates the total effort in term of person -month of technical project staff.
It does not include the cost of the secretarial staff that might be needed. The basic
steps in this model are:

1 ) O b t a in a n in it ia l e st ima t e o f t he d e ve lo p me n t e f f o rt f ro m t h e e st ima te o f
t h o u sa nd s o f d e live red lin e s o f sou rce cod e (K DL ).
2 ) De t e rmin e a se t o f mult ip lyin g f a cto r f ro m d if f e re n t a t t ribu t e o f th e p ro je ct .
3 ) A d ju st th e e f fo rt e st ima t e b y mu lt ip lying t he in it ia l e st ima te wit h a ll th e
mu lt ip lyin g f a ct o r.

Th e in it ia l e st im a te is d e t e rmin ed b y a n e q ua t io n o f th e fo rm u se d in t h e st a t ic,
sin g le -va ria b le mo de s, u sin g K DL a s me a sure o f size . To d e t e rmin e t h e in it ia l e ff o rt
E i in p e rso n -mo n th s th e eq ua t io n u sed is o f t h e t yp e
E i = a *(K DL ) b

Th e re a re 15 d if fe ren t a t t ribu t e , ca lle d co st d rive r a t t rib ut e s t h a t de t e rmin e th e


mu lt ip lyin g fa ct o rs. Th e se f a cto rs de p end on p ro d u ct , co mpu t e r, p e rson a l, a nd
t e ch no lo g y.

A ll 1 5 f a cto r a re mu ltip lie d t o ge t he r t o g e t t h e ef f o rt ad ju sme nt f a ct o r(E A F).


Th e f ina l co st e st ima te , E , is o b ta in ed b y mu lt ip lyin g th e in it ia l est ima t e b y t h e E A F.
E = EAF * Ei
Co st e st ima t ion
Th e size e st ima t e s f o r t h e se in lin e s o f co de a re .
6 8 03 =6 .8 0 3 K DL
Ca t e go ry o f p ro je ct is se mid e t a ch ed so co nst ra in t of a & b a fo llo ws
A =3 . 0 & b =1. 1 2
So, E i= 3 . 0 (6 .80 3 ) 1 . 1 2

73
= 3 . 0 (8 . 56 3 )
= 2 5 .6 89
Ra t in g o f mu lt ip lie r for d if f e re nt co st d rive rs.

Cos t dr i v e r Ra ti ng V a l ue s

S oftw a r e rel i a bi li ty v e ry hi gh 1.40


Data base size high 1.08
Product complexity high 1.15
Computer turn around time very high 1.15
Analyst capability high 0.86
Application experience nominal 1.00
Programmer capability high 0.86
Programming language exp. High 0.95
Morden prog. Practice high 0.95
Use of software tools low 1.10
Development schedule nominal 1.00

The effort adjustment factor(EAF) is


E A F = 1. 4 *1. 0 8*1 .1 5 *1 . 1 5 *. 8 6*1 *.8 6 *.9 5 *.95 *1 . 1*1

=1 . 46
t h e in it ia l e f fo rt o f t he p ro je ct is

E = E i*EA F

= 1 .4 6 *2 0 .7 8 9
=3 0 .5 2 P M

74
P E RT CHART, G ANTT CHART:
P E RT, G A NT ch a rt p ro vid e q ua n t ita t ive t oo ls t h a t a llo w t h e so f t wa re
p la n ne r t o d e t e rmin e t h e crit ica l p a t h - t h e ch a in o f t a sks th a t d e te rmin e s t he
d u ra t ion o f th e p ro je ct ; e st ab lish “mo st like ly ” t ime e st ima t e s f o r in d ivid u a l t a sk by
a p p lying st a t ica lly mod e ls ; ca lcu lat e “ b o un d a ry t ime s” t h a t de f in e a t ime “ win d o w”
f o r a pa rt icu la r ta sk
B o u nd a ry t ime ca lcu lat io n s can be ve ry u se fu l in so ft wa re p ro je ct sch e du lin g .

Th e sche d u ling of my p ro je ct is a s f o llo ws:

WO RK TA SK S (we ek) E S TI MA TE D TI ME

P ro b le m E va lua t io n (P E ) 1
Ca lcu la t ing Fa ct (CF) 1
A n a lysis (A ) 3
I d en t if y Nee d & be ne f it s (I NB ) 1
Fe a sib ilit y (F) 1
De sig n L a you t (DL ) 1
De t a il De sign (DD) 2
Te st in g o f De sig n (TD) 2
Co d in g (C) 4
Te st in g o f Co d e (TC) 5
Co d e O p t imiza t ion (CO ) 1
I mp le me n ta t io n (I ) 2

75
N o w t h e P ER T ch a r t o f th e a b o ve d a t a i s a s f o l l o w s :

0
PE (1) CF (1)

2 1

IND (1) F (1) A (3)

4 3
5

DL (1)

DD (2)

TD (2) C (4)

9 8

DUMMY
---- TC (5)

10
C R I T IC A L P A T H 11 CO (1)

I (2)

12

76
CHEPTER 11

SCOPE OF FUTURE ENHANCEMENT

It is unreasonable to consider a computer based information system


complete or finished; the system continues to evolve throughout its life cycle,
even if it’s successful. Due to the creative nature of the design, there remain
some lapses inaccurate communications between the users and the developers.
So, certain aspects of the system must be modified as operational experience is
gained with it. As users work with the system, they dev elop ideas for change
and enhancements.

77
CHEPTER 12

CONCLUSION

The ShareBazar.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.

78
CHEPTER 13

BIBLIOGRAPHY

BOOK NAME AUTHOR NAME

1. Pure Java Server Pages James Goodwill

2. JavaScript Application Cookbook Jerry


(Paperback) Bradenbaugh

3. Java Server Pages OReilly

4. Java Server Pages SAMS

5. Java Script SAMS

6. JavaScript Unleashed (4th Edition) R. Allen Wyke

7. An Introduction To Data Base System Bipin C. Desai

79