Synopsis

INDEX
S NO. TOPIC

1. TITLE OF THE PROJECT.
2. INTRODUCTION

3. OBJECTIVE OF THE PROJECT
4. PROJECT CATEGORY

5. TOOLS AND PLATFORMS
 Hardware Requirements
 Software Requirements

6. PROJECT PLANNING AND SCHEDULING
7. SYSTEM ANALYSIS
 Identification of Need
 Preliminary Investigation
 Feasibility Study
 Software Requirements Specification (SRS)
 Software Engineering Paradigm Applied
 Data Flow Diagram (DFD)
 Entity Relationship Diagram (ERD)
 Use Case Diagram

8. SYSTEM DESIGN
 Module Diagram
 Name of Module and their Description
 Data Integrity
 Constraints
 Data Structure
 Report Generation
 Process Logic of Each Modules

9. FUTURE SCOPE OF THE PROJECT

Anuj kumar (Enrol No.- 095836815)

10. BIBLIOGRAPHY

TITLE OF THE PROJECT


INTRODUCTION

My project is on the topic “Share Monitoring system “ Which gives information

about the Share Market, about Company information, Share rate, Brokers

information, Stock Exchange share rate fluctuation, Top 10 gainers / losers

etc.My project is based on how share shall be purchased from companies by no

of brokers or shareholders. Today the most profitable business is share market.

Today there are many companies who wants to earn too much profit due to

which they sell their shares .Generally Share be of two types 1) Prefence Share

2)Equity Share. When Company is in deep trouble then they issue Prefence

share but when Company is running in great deal of demand then they they

offer equity share.Normally Company do not want to issue prefence share due

besides of this company pays fixed profit to the shareholders either it has profit

or loss.

Today most of the companies issues their share such as Reliance ,Satyam

,Infosys etc. To open your account in Share business you must have an account

which is called Demat account. You must have knowledge about internet and

some basic concepts of Accounts due to which you can easily understand about

company information such as :

⇒ Balance Sheet

⇒ Profit and Loss Account

⇒ Goodwill

⇒ Assets

The proposed software is designed to develop a Share market

management system that will increase the effectiveness, efficiency, and

controlling functions of stock services by providing more timely, relevant and

accurate information to the concerned Customers.

The proposed software, with good implementation, will help in all types

of job related to stock services. Based on this software analysis the hurdles in the

way of development can easily be known and its timely information can help to

overcome these hurdles.

Registered users can trade in shares listed on the National Stock Exchange

(NSE) and which are in the compulsorily demat list. Currently there are 761

stocks which are traded in the demat form. Scrips in the rolling settlement will

be traded in the rolling format while those permitted in the normal settlement

cycles will be executed under the weekly settlement schedule.ICICIDirect.com

provides full services so that a customer can easily handle the site or knowing

about different terms of the stock exchange.

BUyINg ShaReS

In order to place a buy order the user has to click on the ‘Buy’. The exchange,

stock, symbol and the quantity have to be specified in the provided space. The

user has the facility to specify his limit price and a stop-loss trigger price. The

user has also the option to disclose only a part of the quantity that he wishes to

buy in the market. The user can also specify the product (Cash / Margin) in

which he wants to place the buy order. All orders are Good Till Day (GTD) and

valid only for the day and will get automatically cancelled at the end of the day

if not executed. A confirmation request will appear before the order is

transmitted to exchange.

SellINg ShaReS

To sell shares click on the ‘Sell’. The exchange, scrip, symbol and quantity will

have to be specified. As in the case of buying shares, the limit price and a stop-

loss trigger price need to be mentioned. A user may disclose only a part of the

quantity to be sold. The user can also specify the product (Cash / Margin) in

which he wants to place the sell order. All orders are Good Till Day (GTD) and

would automatically be cancelled at the end of the day if not executed. A

confirmation will be asked before it is transmitted to the exchange.

ORDeR BOOk

The status of buy/sell orders can be obtained by clicking on the ‘Order Book’.

The order book will furnish details of all the buy/sell orders along with the status

of each order. The report will be as follows and is updated real-time.

Requested: Order is placed when market is closed

Queued: Order sent to the exchange

Ordered: Exchange has sent an acknowledgement of receipt of order

Executed: Order has been executed

Part executed: Order is part executed


Rejected: Order rejected by the exchange

Cancelled: Order is cancelled

Expired : Orders remaining unexecuted at the end of the day getting expired.

Transaction details against each order can be viewed by clicking on ‘View

Transactions’. modify or cancel unexecuted orders by using the order book.

TRaDe BOOk

The Trade Book shows the details of the trades executed for you. The details are

updated on a real time basis and the latest status can be verified by refreshing the

page.

Multiple trades for the same Order Ref. No. to be aggregated and shown as a

single entry in the Trade Book. Clicking the Order Ref. No. will show you the

details of the trades for that particular Order Reference Number.

It also contains links for settlement obligations of cash and securities for the

executed order. The detailed view contains the date and the amount of Cash Pay

In / Cash Pay Out debited/credited to your bank account with date and time.

MaRgIN POSITIONS

All margin position (Buy/Sell) created by the user, which are open (yet to be

squared off) are displayed on this page along with other relevant details like

average buy/sell price, current market price, real time mark to market profit/loss,

total margin blocked on each such position, etc.


It also contains the links for actions like adding margin to your open position,

converting the open position into Cash segment (for delivery) and to place

square off order(s).

CONveRTeD TO DelIveRy

All margin position converted to delivery would be reflected on this page for his

reference.

DeMaT aCCOUNT BalaNCe

On clicking ‘Demat Account Balance’ the stocks in the user’s demat account and

the status can be accessed. The balance indicates the number of shares that can

be sold. If some shares have already been sold then such quantity will be

indicated as blocked and cannot be sold.

The quantity shown in the TIFD (Transfer Instruction For Delivery) column

would indicate the quantity that is in the process of being debited from the

account on settlement. Please note that no separate instructions need to be issued

to the depository participant (DP) for debiting the account in case of a net sell

obligation. The shares get automatically debited from the DP account in case of

a net sell obligation and credited in the event of a buy obligation.

CaSh PROjeCTIONS

Details of the cash balance can be obtained by clicking on ‘Cash Projections’.

The status report of the net obligations is available after the settlement. The net

amount by which the bank account would be debited in case of a net payable

position or the net amount by which the account would be credited in case of a

receivable position for the settlement can also be seen. Information on the dates

on which such debit or credit will take place and the closing balance after the

respective debit or credit will also be displayed. Transaction details for each

debit and credit can also be viewed.

SeCURITy PROjeCTIONS

Securities projections will give information on the date on which a particular

stock will be debited from the DP account in case of a net sell position for the

settlement. Similarly, the date on which the stock will get credited to the DP

account in case of a net buy position for the settlement is also available.

MODIfy allOCaTIONS

You can increase or decrease the amount set aside for trading from your bank

account through the options. You can also view the net with drawalable for add

by allocating or de-allocating.


lIMITS

‘Limits’ is the amount set aside for trading from the bank account and the

amount realized from the sale of shares in cash segment after deducting the

amount of purchases in cash segment. The limit increases/decreases once the

registered user allocates funds for trading using the "Modify Allocations"

screen.In case of shares sold in Cash segment , the limit increases by the amount

receivable and for buy orders in cash segment the appropriate amount will be

deducted and hence the limits will be reduced by such an amount. All

calculations are executed automatically. However, it is important to specify the

exchange and settlement cycle to access the limits. Limits are appropriately

reduced by the applicable margin percentage on the order value while placing

the orders in the margin segment. Once the margin position is squared off, the

margin amount blocked thereon is released after giving effect to the profit or loss

booked on such square off. On clicking ‘Modify Allocations’ you can allocate

funds from the available clear bank balance for trading. Similarly, the amount

can also be reduced. Please note that on bank holidays and on weekly off days

this facility is not available.

MaRkeT MeSSageS

All important broadcast messages received from the National Stock Exchange

can be viewed by clicking on the ‘Market messages’ hyperlink.


OBjeCTIveS Of The PROjeCT

Since it is the project for automating the share monitoring System. So its

objectives are quite obvious. Designing such system which keeps all the

information about:

• Company Information

• Numbers of share sold

• Brokers Information

• Stock Exchange Status Chart of all in a day

• Share Holder Information

Some important objectives of the project are :

• Improve the quality of service to the share holder at large.

• Reduce expenses.

• Increase revenue.


• Better communication between share holder and stock exchange.

Finally the application tries to automate almost the whole system so that a fast

and reliable system could be established.

Since the existing system is manual, so it

is time consuming. There is no facility of report generation of tickets sold,

customer information etc. more paper work is required. Since all the words are

performed manually in register for keeping track of all information. Keeping

these drawbacks in mind we developed a project, which can eliminate the above

drawbacks. With the help of this project the query facility becomes faster about

availability of seats in the requested Route and date. Better management of

manpower can be achieved through automation. The project provides faster

report generation in comparison of the existing manual system.

The other purposes of this System are as follows:-

o To improve the processing speed of the work

o To reduce the paper work

o To manage the database in effectively and efficent way

o To improve the morale of the system.

o To make the system userfriendly


PROjeCT CaTegORy
Category of this project will be “Object Oriented Programming System”

(OOPS). Object oriented technologies leads to reuse, and reuse leads to faster

software development and higher-quality programs. Object oriented software is

easier to maintain because its structure is inherently decoupled. This leads to

fewer side effects when changes have to be made and less frustration for the

software developer and the customer.

The OO model of computer software must exhibit data and procedural

abstraction that lead to effective modularity. The data abstractions (attributes)

that describe the class are enclosed by a “wall” of procedural abstractions that

are capable of manipulating the data in some way. The only way to reach the


attributes is to go through one of the methods that form the wall (data

encapsulation and hiding).There are various reasons to use OOPS concept

behind developing this software as–

1. Encapsulation

2. Polymorphism

3. Robustness

4. Modularization

5. Inheritance

6. Data Abstraction

7. Data Persistence

8. Data Hiding

haRDWaRe & SOfTWaRe ReQUIReMe ¥©®NTS

 HARDWARE REQUIREMENT:

• Microprocessor-P IV

• Motherboard – 845 E

• Hard Disk-40 GB

• RAM – 128 MB

• Cache Memory –1 MB

• Multimedia Keyboard


• Standard Floppy Disk Drive (FDD)

• CD Rom Drive 8X

• UPS 300 VA

 SOFTWARE REQUIREMENTS :

• OPERATING SYSTEM : WINDOWS 2000

• PROGRAMMING LANGUAGE : JAVA

• DOCUMENTATION : MS-WORD 2000

• BACK END : ORACLE 8i

EDITOR : JCREATOR

PROjEcT PlANNINg

Planning for projects requires effective management controls to ensure the

desired result. The project planning activities is undertaken before the

development starts. Project planning consists of the following essential

activities; through I make the project planning to starts the project development.


 Estimating some basic attributes of the project.

Cost:-To develop this project there is a need of some following costs like,

♦ Traveling cost

♦ Food cost.

♦ Maintenance cost.

♦ Management cost.

♦ Miscellaneous Expenses.

Here the above all costs are only related to student, which will be spend

during developing the project.

Duration:-To develop this project I estimate the 45 days after proposal

approval date. With these days I can going through every phase related aspects

of the project and can develop the project.

Effort: Here is only one student are working on this project. There is also need

of some management effort to develop this project.

RISk IdENTIFIcATION, ANAlySIS, ANd AbATEMENT

PlANNINg.

To identify the risk related to the project, I analyzed the every phase and

steps to project development. Through that analysis I also ensured that the every


aspect related to abatement. This phase will support me at any phase of

development through analysis to installation.

MIScEllANEOUS PlANS SUch AS QUAlITy ASSURANcE

To quality assurance related plan I measure

every function definition before implementation before implementation in the

phase and after implementation. Apart from this I measure every phase, unit and

modules aspect and whole separately. To ensure the Quality Assurance there is a

need of good definition of the problem; to ensure this definition I define every

problem to each module very accurately and clearly. Through this I can ensure

the better quality.


PROjEcT SchEdUlINg

Scheduling the project tasks is an important

project planning activity. It involves deciding which tasks would be taken up

when. The following are the task that is done by me in the project scheduling

phase:

Identifying The task

I divide the project development in the following task:

 Conducting interviews from different Key members

 Preparing DFD’s and determines every aspect of modules took

another half week.

 Studying facts and system analysis completion report took half

week.

 Preparing Process logic & Flow Chart took another week.

 Coding and debugging of each module took another two weeks.

 Finally, documentation and implementation of new developed

system took one week.


Break Down Large Tasks Into Small Activities:

When I break down the task -1, I found that the all

small activities support me to better understand the system. So following are the

small task related to task-1.

 Analyzing the facts after preliminary or whole investigation to

the system.

 Measuring the feasibility study separately.

 Creation of data related to system.

 Finally document all these activities.

I break down the task-2, I get following subtasks:-

 Collection of data related to system.

 Division and creation of different modules.

 Preparation of DFD’s of different module.

 Maintaining the Integrity with System.

I divide task-3, in following subtasks:-

 On the basis of Flow Chart and pseudo code, coding the

different module unit.

 Testing each unit.

 Comparing with the modules needs.

 Integration of different modules.

 Finally system testing.


I divide the task-6, in following subtasks:

 Finally document the project.

 Training of system user or agency operator.

 Finally implementation of system.

 Maintenance of the system.

After preliminary investigation we get some knowledge about the system.

Before analyzing the fact, there is need of reviewing the system to determine the

feasibility study. So without reviewing and analyzing we can’t be preceding next

task. Without preparation of pseudo code or process logic we can’t be go to code

generation.


SySTEM ANAlySIS

Analysis modeling uses a combination of text and diagrammatic

forms to depict requirement of data, functions, and behavior in a way that is

relatively easy to understand, and more important, straight forward review for

correctness, completeness, and consistency.

 Identification of Need

On the basis of my observation to whole system

I have defined the following goals of the system.

• Fully User Friendly

Here the user friendly means that system or

software is worked according to needs and provides a fully interaction with

system to user. The system is fully user-friendly, since it is developed in java,

which is being object oriented environment having very easy understandable

facilities.

• Paper Work reduced

Since there is no unnecessary printing and

photocopying of the document for the various department and management.


Faster Access of information:

System provides the faster accessing of

information by using greater internal definition of function and through the

better internal configuration.

• Efficient traceability

Whatever too much information are stored tracing of

particular Share, company ,Broker information will be easy.

• Report Generation can be Done Easily

As after the automation of the system report

about any modules can be generated easily.

• Query Can be done Easily

Query option makes it easy to get the information

about particular module.


PRElIMINARy INvESTIgATION

One must know that the problem is before it can

be solved. This phase starts as the initiation of investigation of system. An

important outcome of the preliminary investigation is determining whether

the system requested is feasible or not. Following are the

things that are found after the Preliminary Investigation.

• Identifying The responsible Users:

• Users Need:

• Current problem to User:

• Determine Objective For The New system:

FEASIbIlITy STUdy

The main of the feasibility study activity is to

determine whether it would be financially and technically feasible to develop the

project. In this context I have done following observation.

I have used the following three types of feasibility study:

EcONOMIc FEASIbIlITy

To examine economical feasibility of the project I

studied the economical feasibility of current working system. I have found

several things in this regard which are described below:-


(a) Current system is more costly and not beneficial for the

agency.

(b) Unnecessary wastage of manpower, time and effort.

(c) Paper Cost

To solve above described economical problems we have introduced

several provisions in our project which are as follows:

Before establishing economical feasibility so as to justify the expenses

that the top management has sanctioned for computerization, it is necessary to

look to the agency status. The organization has to purchase a fully equipped

computer according to departments needs. An employee needs to operate

computer with this system. The training cost is also need to trained the operator

who has to work. Once the initial investment is made soon it would nullify the

initial cost as in later stage when system will developed, it would give profit in

operations. The system will be very user friendly, so organization has to invest

amount initially to operating the system.

TEchNIcAl FEASIbIlITy

To examine technical feasibility of the project, I have

studied that what types of technology is presently being used in current working

system. I have found numerous problems in this regard which are described

below:

o The agency currently used the register to maintain record that is various

tedious to manage and recording.


o Addition of new data, deletion, modification and updating of data is

most tedious task for the Munsi.

o There is too much registers are stocked, so it also creates a difficulty.

o Information gathering is also a difficult task.

o Report generation is also difficult one for the past recorded data.

o Lacking of security related to data.

o Too many employees are worked to maintain the record.

o Unnecessary wastage of time.

o Controlling on the record is also tedious task for employee.

OPERATIONAl FEASIbIlITy:-

To examine the operational

feasibility of this project, I studied that what types of operation, in different level

management system presently used in current working system. I have found

several short coming that are described below:

o Present system is poor in operationally because user maintains the records

on register, so when retrieving the data from two or more register,

adding , deletion, updating, all these works are most tedious to do.

o Management information is not properly operation management system.


To solve above problem I have decided to educate the operator to

understand the system. In my project I provide uniform platforms all across the

agency as much as possible to overcome these difficulties. I settled the computer

use friendly, having less paper work, efficient traceability, and query can be

generated and report generation also can be done easily.

System Requirement Specification(SRS):-
Requirements specification is very important activity after the problem
definition. This is the way to represent requirements in a consistent format.
Requirements specification is called Software Requirements Specification
(SRS).

The SRS is a specification for a particular Software product, program or set of
programs that performs certain functions in a specific environment. It servers a
number of purposes depending on who is writing it. First, the SRS could be
written by the customer of the system. Second, the SRS could be written by a
developer of the system. The two scenarios create entirely different situations
and establish entirely different purposes for the document. First case, SRS is
used to define the needs and expectations of the users. The second case, SRS is
written for different purpose and serve as
Functional Requirements:- The main purpose of functional requirements
within the requirement specification document is to define all the activities or
operations that take place in the system. These are derived through interactions
with the users of the system. A summary of major functions that the software
will perform: Company Information
• Numbers of share sold

• Brokers Information

• Stock Exchange Status Chart of all in a day

• Share Holder Information

• Some important objectives of the project are :

• Improve the quality of service to the share holder at large.

• Reduce expenses.

• Increase revenue.

• Better communication

Context Level DFD for Share monitoring system

Request for Broker
Share status Status of Share
Broker

Enquiry Information /report
Customer
Customer
Accepted/
Rejected
Apply for Reg. Customer
Share
Monitoring
Customer System
Broker

Information

Broker

Receipt

Anuj kumar Customer
(Enrol No.- 095836815)
Customer
Update Information
Company Pay for Share
Information Company

DFD For Share apply 1 level

Customer / Client

Applying Registration Form

Not Available

Registration
Process Rejected

Accepted

Updation in Master Table
Registration,Customer,Company,Brokes


DFD For Share payment

Customer / Client

Fills up Payment Form
Not
Available

Data Entry &
Rejected
Verification

Accepted

Company Master Table

Payment

Calculation
of Share Holder
Payments
of Shares
Company

Updating in Master Table Customer , Reg. , Company


ER-Diagram

Entity-relationship (E-R) diagram is detailed logical representation of data for an organization.
It is data oriented model of a system. The ER diagram represents data at rest. ERD does not
provide any information regarding functionality of data. It has three main components – data
entities, their relationships and their associated attributes.

Entity:
It is most elementary thing of an organization about which data is to be maintained. Every
entity has unique identity. It is represented by rectangular box with the name of entity written
inside.

Relationship:
Entities are connected to each other by relationships. It indicates how two entities are
associated. A diamond notation with name of relationship represents as written inside. Entity
types that participate in relationship is called degree of relationship. It can be one to one (or
unary), one to many or many to many.

Attributes:
Attribute is a property or characteristic of an entity that is of interest to the organization. It is
represented by oval shaped box with name of attribute written inside it.


Reg_no name Location

has Company

Est Date State
Name Location

Noofshare Rate/Share
Keeps
Stock_ex Share

Regno

Regist
er
Choos
e
borro
ws

Id Name Id Name

Broker Works Share Holder
for

Location State Location State
Date of
Reg


SyStem DeSIGn

System design develops the architectural detail required to build a system or

product. The system design process encompasses the following activities

 Partition the analysis model into sub-systems.

 Identify concurrency that is dictated by the problem.

 Allocate sub-systems to processor and tasks.

 Develop a design for the user interface.

 Choose a basic strategy for implementing data management.

 Identify global resources and the control mechanism required to access

them.

 Design an appropriate control mechanism for the systems, including task

management.

 Consider how boundary condition should be handled.

Basic Modules

The whole system is divided into seven main Modules:-

• Stock exchange management module

• Company management module

• Brokers management module

• Share apply management module


• Query management module

• Report management module

• Login Management Module

Data Design:

The data design transforms the information domain model created during

analysis into the data structures that will be required to implement the software.

The data objects and relationships defined in the entity relationship diagram and

the detailed data content depicted in the data dictionary provide the basic for the

data design activity. Part of data design occurs in conjunction with the design of

software architecture. More detailed data design occurs as each software

component is designed.

Schema design:

The schema design defines the relationship between major structural element

software, the “design patterns” that can be used to achieve the requirements that

have been defined for the system, and the constraints that affect the way in

which architectural design patterns can be applied. The architectural design

representation- the framework of computer-based system- can be derived from

the system specification, the analysis model and the interaction of sub-system

defined within the analysis model.


DATA INTEGRITY & CONSTRAINTS:

Data integrity means that the data contained in the database is both accurate and

consistent. Therefore, data values being entered for storage could be checked to

ensure that they for within a specified range and are of the correct format. e.g.

the value for the age of passenger should be greater than 5 years. Another

integrity check that should be incorporated in the database is to ensure that if

there is a reference to certain object, that object must exists.

proCeDUral DeSIGn

Component level design also called procedural design occurs after data

architectural and interface designed have been established. The intent is to

translate the design model into operational software.

LOGIC DIAGRAMS:-

 Control flow chart: -

A graphical technique is available for determining whether changes and

variation in metrics data are meaningful called the control flow chart.

 Process diagram: -

Process diagram is the systematical flow of procedure that improves its

comprehensive and helps the programmer during implementation.


Data StrUCtUre :-

This is a cataloged storing the details of data being used in the system. Data

dictionary serves the following purposes –

 Up gradation in the existing program

 Maintenance, which facilitates the effectiveness of the system.

 Data query

table USeD

Table Name: stock
Field Type Constraint
s_e_name CHAR(20)
regno CHAR(10) Primary Key
location CHAR(20)
dist CHAR(20)
state CHAR(20)
phno CHAR(15)
fax CHAR(15)
website CHAR(20)
est_date DATE


Table Name: company
s_e_name CHAR(20)
regno CHAR(10) Primary Key
company CHAR(20)
location CHAR(20)
dist CHAR(20)
state CHAR(20)
no_of_share NUMBER
rate_per_share NUMBER
est_date DATE

Table Name: broker
FIELD TYPE CONSTRAINT
brokerid CHAR(10) Primary Key

brokername CHAR(20)

location CHAR(20)

district CHAR(20)

state CHAR(20)


phone CHAR(20)

company CHAR(20)

dateofreg CHAR(20)

Table Name: shareholder

id CHAR(10) Primary Key

name CHAR(20)

add CHAR(25)

dist CHAR(25)

state CHAR(25)

pin CHAR(10)

ph_no CHAR(15)

age CHAR(3)

sex CHAR(6)

email CHAR(25)

relation CHAR(15)

brokerid CHAR(10)

company CHAR(20)

noofshare NUMBER

full CHAR(10)


min CHAR(10)

amountpaid CHAR(10)

nname CHAR(20)

Table Name: Rating


COMPANY CHAR(20) Primary Key

PRICE NUMBER

CHANGE NUMBER

Table Name:-login


uname CHAR(20) Primary Key

pass CHAR(20)


proCeSS loGIC

My project is an application that provides greater facilities to the user. My

project starts with a main menu that tells to the user to choose an option to get a

particular information. There is an Option of Doctor detail when a user selects

this option a form display with Add, Delete, and Update e.t.c.

1. STOCK EXCHANGE MANAGEMENT MODULE : To work on this

module we will use Stock_Exchange table. This table store many

attributes of stock exchange . Process:

a) Accept value from user for stock exchange .

b) check If entry wrong found then

generate an error message

else

store the information provided by user.

End if


2. COMPANY MANAGEMENT MODULE :- To work on this

module we will use Company table. Blank entries are also not allowed in

mostly field.

Process:

a) Accept value from user for company

b) Check If entry found wrong generate an error message else store the

information provided by the user in table.

3. BROKERS MANAGEMENT MODULE :-To work on this module

we will use Brokers table. Blank entries are also not allowed.

Process:

a) Accept information from user for Brokers

b) Check If wrong entry found generate an error message else store

the information provided by the user in table.

4. SHARE APPLY MANAGEMENT MODULE : To work on this

module we will use several tables as Share Apply ,Company ,Exchange

,Brokers and Customer table.

Process:

a) Accept information from user for share holder details , company share

wanted ,broker used for share purchasing . no of shares wanted

b) If wrong entry found generate an error message

else store the information provided by the user in table.


5 QUERY MANAGEMENT MODULE:- In this module we can get

information about any module, like about company , stock exchange ,

brokers , share holder related. .

Process:

a) Accept field from user for query.

b) If field entry exist in table then show information else show

an error message this field is not exist in table.

6. REPORT MANAGEMENT MODULE :- In this module we can

generate report for a particular table or information. There are many

options to generate report. We can generate this report with individual or all

option button.

Process:

a) Accept INPUT to generate report

b) After accepting input process and generate report.

7. Login Management Module: This module is an important one in the project

.since security is an important issue of any s/w .proper importance is given for

this module. To use this module two table login and login type is used .Login

table manages about the user name ,password ,user type and a unique no to

identify the users .second table login type table manages the login type –general

user Only to view the records. administrator allowed to add ,delete, modify and

register new students.


Process :

 Accept user name and password

 Check if entry valid search with the user stored in the database.

 If found welcome the user and based on type open the s/w. Else Generate error

message “Invalid Username /Password and point the user to enter name /

password again . or cancel the operation

SCOPE OF FUTURE APPLICATION

My project has been developed in Window based programming language and

made of modules, so that in future any types of following important scheme may

easily be changed according to the requirement.

 Reusability code for connect modules

 In future this project support networking through which it may be connected

to Internet.

 In future it supports multi-user operating system like UNIX/ LINUX

 For better support of user this project also support the technique in Future.

Backup file.

Fast searching technique.

Complex Queries.

Support broad range input and output device.


BIBLIOGRAPHY

(1) Object-Oriented Programming – By Robert Lafore

(Galgotia Publication)

(2) Complete reference java2

(3) Object-Oriented Modeling – By James Rumbaugh,

And Design Michael Blaha,

William Premerlani,

Frederick Eddy &

William Lorensen

(Prentice-Hall of India)

(4) Software Engineering – By Roger S. Pressman

Practitioner’s Approach (McGraw Hill)

(5) IGNOU’s CS-05 (Elements of System Analysis and

Design) Blocks.


Synopsis

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (11)

Ähnlich wie Synopsis

Ähnlich wie Synopsis (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Synopsis