Stock Management

System

DR. VIRENDRA SWARUP INSTITUTE OF COMPUTER

STUDIES

MCA FINAL SEMESTER PROJECT

REPORT

ON

“STOCK MANAGEMENT SYSTEM”

SUBMITTED BY:-

RAHUL SAMADDAR

MCA2K5

0504714031

pg. 1
 Stock Management
System

CERTIFICATE

Dr. VIRENDRA SWARUP INSTITUTE OF COMPUTER STUDIES

810, W1 BLOCK, JUHI, SAKET NAGAR, KANPUR-208014

This is to certify that the project entitled

STOCK MANAGEMENT SYSTEM

Submitted by

Rahul Samaddar

0504714031

In the partial fulfillment of the requirement for the award of the degree of
MCA to

UTTAR PRADESH TECHNICAL UNIVERSITY - LUCKNOW

In the Academic year 2007-2008

Is a record of student’s own work carried out at

HEWLETT PACKARD INDIA SALES PVT. LTD. NOIDA

Mr. Rekhnath Singh Mr. S.S. Pandey

Director HOD (Computer Application) Director (VSICS)
pg. 2
 Stock Management
System

Content……………………………………………………

 Company profile……….The work place

 Our Project……Stock MANAGEMENT system …….The basics

Problem domain

Initial Requirement

Feasibility Analysis

Document of the Proposed system…Software Requirement Specification

System Analysis

Software Design

Testing

Implementation

Post implementation

 Technologies..used

 About Me…………

pg. 3
 Stock Management
System

pg. 4
 Stock Management
System

bstract

The project titled “Stock MANAGEMENT System” aims at developing a system which will
automate the functioning of the MANAGEMENT shares online. This web application provides
the full functionality to create and manage accounts as well as trade online. These activities
constitutes tasks like

• User activities
• Create a new saving account
• Get a generated demat account
• Capture new user details.
• User registration facility.
• Authorized login facility for applicant.
• Information facility.
• Maintain Database of users.
• Transfer funds from saving to demat account.
• Assets report generation
• User login and exact authentication.
• Proper list of available shares.
• Buying and selling shares.
• Profit loss evaluation.
• Report generation system.
• Verification and validation system.
• Search facility of shares.
• User four filter search report
• Administrator activities
• Adding and removing shares.
• Modifying and updating share quantity and prices
• Adding, modifying and removing new Roles and their Role Codes.
• Activate and deactivate users.

pg. 5
 Stock Management
System
• Provide privilege to user and moderators.

• Verification and validation facility of data at client side.

• Verification and validation facility of data at server side.
• Report and search of four filtered mechanism according to shares, users, date and
other details.
• These activities were all being performed manually prior to the implementation of this
system. This entailed lots of unnecessary wastage of resources, especially for the book
keeping related tasks of the Recruitment Department. A need for the automation of all
these activities was felt. To this effect the front end was deemed to be an internet
browser and the data store backend was Oracle. The Java programming language has
been selected to be the go between the data store and the application. The Java
programs will be accessed by the browser using the JSP technology.

The project goes about breaking down the main problem into various modules and then
providing the functionalities for these modules and establishing relationships among the
various modules. It provides facilities for data updating of each module with stress on ease of
use and clarity. The security aspect for providing access to the various modules is very
important since the project is online and can be accessed by the Administrator as well as
moderators and the candidates. Hence an elaborate system of roles has been put in place. The
Administrator who has all the powers and permissions is allowed to create roles.

The aspect of testing and implementation was also a very important phase. The user needed to
be educated about the various facilities available and how best these can be used; the
Administrator for one has to be completely familiar with the system and the use of internet.

This project report will go about elucidating each and every aspect of this project in detail.

pg. 6
 Stock Management
System

pg. 7
 Stock Management
System

ckowledgement

Completing a task is never a one-man effort. It offers the results of valuable contribution of a
number of individuals in a direct or indirect manner that helps in shaping and achieving an
objective.

This project would not have taken shape, but for the guidance provided by Mr. Jeetendra, Our
Trainer who help us on our project and resolve all the technical as well as other problems
related to the project and else and Mr. Khalid Mustafa, Kean India Ltd our guide who gave us
the details of the project and the technical aspects of the project. Mr. Sudhir has helped me so
much he has the extreme grip over Java and J2EE fundamentals which were the great tool to
me to develop this project. I profusely thank them for the support provided to me.

I also express my gratitude to Mr. Mukesh who has provided the opportunity of organizing
project for me which will be great support in coming future.

I express a deep sense of gratitude to my project guide Mrs. Jeetendra for his efforts in giving
start and his keen interest, criticism and valuable guidance were indeed a source of
inspiration for me. I am grateful to them for lending their precious time and the patient
listening they gave me every time I needed help; in spite of their busy schedule.

Above all I wish to express my heartfelt gratitude to my family, who has always been the
singular source of inspiration in all my ventures I have undertaken.

I believe this endeavor support has greatly boosted my self-confidence and will go a long way
on helping me to reach further milestones and greater height.

Special thanks to Gaurav Asthana, Rajesh Jain, Javed and Shweta Mishra. As Always, this
has been a joint effort.

Rahul Samaddar

pg. 8
 Stock Management
System

Company Profile……..Hewlett Packard ES

India (p) Ltd.
The Hewlett-Packard Company (NYSE: HPQ), commonly referred to as HP, is an
American information technology corporation, specializing in personal computers, notebook
computers, servers, network management software, printers, digital cameras, and
calculators, among other technology related products.

Headquartered in Palo Alto, California, United States, it has a global presence in the fields of
computing, printing, and digital imaging, and also provides software and services. The
company, which once catered primarily to engineering and medical markets—a line of
business it spun off as Agilent Technologies in 1999—now markets to households and small
business products such as printers, cameras and ink cartridges found in grocery and
department stores.

HP posted US $91.7 billion in annual revenue in 2006 compared to US$91.4 billion for IBM,
making it the world's largest technology vendor in terms of sales. In 2007 the revenue was
$104 billion, making HP the first IT Company in history to report revenues exceeding $100
billion.

HP is the largest worldwide seller of personal computers, surpassing rival Dell, according to
market research firms Gartner and IDC reported in October 2006;[4] the gap between HP and
Dell widened substantially at the end of 2006, with HP taking a near 3.5% market share lead.

 Founded

Palo Alto, California. (1939)

 Headquarters

Palo Alto, California, USA

 Key people

William(Bill) Hewlett, Co-founder

David Packard, Co-founder
Mark V. Hurd, Chairman, CEO and President
Cathie Lesjak, CFO and EVP
Randall D. Mott, CIO and EVP
Michael Holston, General Counsel and EVP

pg. 9
 Stock Management
System

 Industry Computer Systems

Computer Peripherals
Computer software
Consulting
IT Services
Education Services

 Revenue ▲$104.3 billion USD (2007)

 Net income ▲$7.3 billion USD (2007)

 Employees 156,000 (2007)

 Slogan Invent.

 Website www.hp.com
www.hpshopping.com
www.Compaq.com
www.voodooPC.com
www.Snapfish.com
www.lightscribe.com
www.hpesindia.com

bout training Centre

HPES has many training centers all around the world. We have accomplished our training at
one of the center located at C-58 , Noida. Here the best corporate training is provided by all
the intellectuals.

The Whole program was conducted by Mr. Mukesh The whole sole of the institution and
motivator too. He used to come to the institution just to discuss the problems to resolve and
pushed the trainee with his great energetic and enthusiastic speech.

Our trainer is Mr Jeetendra who is the most energetic trainer and filled with the extreme
knowledge. He has resolved all the problems concerned with our project as well as our java
and j2ee concepts.

nvironment ……..The environment of the training center was really good. There was a full
air conditioned class room where class lectures was taken by Mr. Jeetendra equipped with a
pg. 10
 Stock Management
System
projector and a white board. All the slides were demonstrated by the projector. This is all
about Class room. The lab was equipped with computer having excellent configuration. And

all the systems are connected via local area network. The upper floor was our cafeteria where
we take our lunch meal.

Our Project…….STOCK MANAGEMENT SYSTEM…The

basics
 What is Stocks?

 Stock represents a piece of ownership of a particular company. Though stock investing

carries a certain degree of risk, it can be very profitable for an educated investor.

 What is Stocks MANAGEMENT?

 Companies throughout the world issue new stock shares every day. They do so to raise
capital in order to invest in the business. Once stock shares have been issued the public
is free to buy and sell those issues through a stock broker. As the supply and demand
for the shares changes so too does the price. Changing stock prices means
opportunities to profit for a trader.

Advantages of Stocks MANAGEMENT

Better returns

Huge Choice

Familiarity.

Disadvantages of Stocks MANAGEMENT

Leverage.

Pattern Day Trader Rules

Uptick Rule on Short Selling

Costs.

Need to Borrow Stock to Short

pg. 11
 Stock Management
System
 IPO Basics and Strategies

 Initial Public Offerings (IPO’s) represent the transition point of companies from a
private status to a publicly held status. Thus, IPO’s represent a new MANAGEMENT
opportunity.

 Stock exchanges

 Stock exchanges are the major places where stock trades are executed. These types of
markets manage to bring together buyers and sellers who are willing and able to
purchase and sell securities. Example: NSE, BSE, NYSE.

 Brokers represent you and act on your behalf concerning the selling and purchasing
of securities. Example Share khan

 Stocks and Inflation Rate

 Inflation can eat up a substantial part of your earnings. So, whenever the levels of
inflation go out of control you should be very careful about the negative impacts it may
have on your investments.

 Mode of MANAGEMENT shares : Interday and Intraday

 Intraday : Buy a share and sell it on the same day………….Marginal MANAGEMENT

 Interday: Buy a share and sell it without any restriction of time .

 Pool of shares

 Many companies releases their IPO and stock exchange release the pool of shares for
the particular company Example: RPL, SBI etc.

 Demat Account

 Every user get a unique Account for the MANAGEMENT purpose .For the generation
of Demat account, user must have his/her saving account.

 Assets: no. of shares

 Buy Low - Sell High, Buy High - Sell Higher

 Many investors prefer to pay low for a stock and hope that its price will eventually
rise. However, they fail to realize that sometimes it is better to pay a higher price for a
stock that has the potentials for a future growth.
pg. 12
 Stock Management
System
 Stock Price Forecast
 Generally investors try to forecast the movement of stocks in a particular direction.
Study the company’s business activity in order to determine whether it is in a current
state or a consistent losing position.

 When to Sell a Stock

 Many investors find it difficult to judge when the right time has come to sell a
particular stock. Besides the personal reasons that may guide your decision there are
times when the market requires you to sell a stock.

 Stock Market Prices and Buying Strategies

 Before you make a decision about the purchase of a stock you should do an extensive
research and analysis. If the market shows that you should follow an investment
strategy that doesn’t conform to your research, double-check the latter and proceed
according to the results.

 Before You Buy Stocks

 No stock buying should be done without a thorough preliminary check on its
potentials. This is required in order not to wake up in the next morning and wonder
why you have put your money in this stock at all.

 When to Buy and Sell Stocks

 The most common rule of thumb that most financial advisors give is to buy at a low
price and sell when the price is high. However, many investors miss the right time.

 Stock Trader vs. Company Investor

 Some people get confused when they are asked whether they invest in a company or a
particular stock. No matter what answer they give it will be the right one. However,
the problem is when people don’t make a difference between investing in a company
and investing in a stock.

 NYSE and Market Specialists

pg. 13
 Stock Management
System
 The New York Stock Exchange (NYSE) is the oldest stock exchange in the US. The key
role in NASDAQ is played by a market maker, whereas in the NYSE it is allocated for a
specialist, who is a market professional part of a specialist firm.

 Bid and Ask Prices

 As an educated investor you should be acquainted with the meaning of bid and ask
prices and the difference between ask and bid prices, referred to as the spread.

Scope

• Market Watch The purpose of Stock MANAGEMENT system is to setup and view
MANAGEMENT detail of securities that are of interest to users. For each securities in the
market watch, market information is dynamically updated.

pg. 14
 Stock Management
System

• Security Descriptor The Following information is displayed in the Security

Descriptor – Security Name, Book Closure and Start and End Dates, Ex-Date,
No-Delivery Start and End Dates, Tick Size, Rating and Remarks. The label

DPR i.e. Daily Price Range displays the permissible price band for a security for
the current MANAGEMENT day.

• Market By Price The Purpose of Market by Price (MBP) is to enable the user
to view outstanding orders in the market aggregated at each price and are
displayed in order of beast prices.

• Order Status The purpose of the Order Status (OS) is to look into the status of
one of dealer’s own specific orders. The screens provide the current status of
order and other order details. The order status screen is not dynamically
updated. In case the order is traded, the trade details are also displayed. In case
of multiple trades the display is scrolled.

• Trade Management A Trade is activity in which a buy & sell order match
with each other. Matching of two orders is done automatically by the system.
Whenever a trade takes place, the system sends a trade confirmation message
to each of the users involve in the trade.
The confirmation slip gets printed at the trader work station of the user with a
unique trade number. The system also broadcast a message to the entire market
through the ticker window displaying the detail of the trade.

pg. 15
 Stock Management
System
Advantages of Stocks MANAGEMENT

• Better returns : Stock system returns a large amount of data in respect

Of there dividant.

• Huge Choice : The user and brokers have huge choices of companies
Who that releases there shares. And user can chose the

Shares of that particular company in which he wants to Invest.

Evaluation of the existing system

Overview of the Existing System

The existing system for MANAGEMENT shares online was much tedious job. Initially it was
not online the whole MANAGEMENT was conducted on telephone and statements and status
are recorded using the book keeping system. A big team will work together to afford this trade
system. Then online sharing comes into the market and the booming IT industry was ready to
adopt it. Resultantly the Share broker web sites like share Khan and India bulls come into the
market.

User can register online and get their login id. Using this Id one can buy/sell the shares. User
has got now some controls in their own hands. The processing get fast and accurate. But there
was still one intermediary between the user and stock exchange that is the broker…….

Constraints and limitations in the existing system

• Based on telephony system and reliability on phone are not much good.

• Time taking processes as user can’t trade the book keeping process are fulfilled
properly.

• Lack of visibility of shares to the user totally dependent on the broker.

• Users have to pay commission for every trade to the broker.

Draw backs in existing system:

• Existing system was slow and man driven, was also involving to much of
paper work

pg. 16
 Stock Management
System
• As a broker one can always handle transactions of 4 of 5 companies but once it
goes beyond that and that too with large number of buyers and sellers so one
would certainly need a some technological help. And that is what precisely this
system is being designed for.
• Manual entries have made jobs person dependent, no one can help the user
except that person who is handling that portion of job.
• Person dependent jobs lead to delay in transaction and increase the processing
time to a great amount.
• Communication with customers was really difficult as searching address and pone
numbers was really a cumbersome task.
• Customer’s enquiries takes longer time since searching records has a high
response time.
• Stock inventor management dose not seems to be solving any purpose, since there
was no ready comparison available when management wants them

pg. 17
 Stock Management
System

Problem Domain
 This section defines the problem area i.e. the need of recognition

 Time …..Delay factor

 Transactions take place in delayed time. (Sell out of one holding and use the proceeds
to buy takes much time). You need to remember that it can take as much as five
working days to draw money down from your MANAGEMENT account, so don’t leave
it until the last minute if you need the cash smartly. But you can typically upload funds
from your bank account to the MANAGEMENT facility in a couple of days.

 The most cumbersome and tedious job for offline traders...Paperwork.

 User can not access a valuation anytime user needs it. Depends upon broker to invest.

 Investors are unaware to live market prices and quotes real-time.

 Based on telephony System.

 If you don’t like the provider you’re with, you can not generally shift the whole
portfolio to another provider free of charge.

 Orders cannot be placed after the market has closed down.

STATEMENT: To develop a system that handles the above mentioned problem.

pg. 18
 Stock Management
System

ecognition of need

Initial Investigation For initial investigation we cover three primitive areas... Which are
as follows:

From Stock brokers: we have collected information from India bulls and Share khan’s
office. From where we collect the complete information that what type of problems a
consumer can face while MANAGEMENT stocks. And some stock related problems and
guidelines.

Key Question: What are the major problems? And what can be its solutions?

From Website: We have collected the major problems of the users and the current operating
system for the purpose of MANAGEMENT from various blogs and responses are quite enough
to go through to the new system.

Well this is all about our initial investigation phase.

PR

roject planning

Guidelines for Project Plans.

• Use project plans to coordinate rather than to control.

• Make use of different personalities within the project environment.
• Prescheduled frequent revisions to project plans.
• Empower workers to estimate their own work.
• Describe value-creating tasks rather than activities.
• Define specific and tangible milestones.
• Use check lists, matrices, and other supplements to project plans

In the initial stage of project planning, the internal and external factors that influence the
project should be determined and given priority weights. Examples of influences include the
following:

pg. 19
 Stock Management
System
Internal Factors

• Infrastructure ……..Not an issue. One client machine and a server can execute our plan

• Project scope …..Not satellite communication so restricted real time facility.

• Project location….Simple p4 systems and a server located any where in the world.
• Project leadership…governed by Gaurav Asthana
• Management approach……Prototyping is used to manage project
• Resource and capital availability….Simple PCs and some legal software’s for
development.

External Factors

• Public needs ………very extensive

• Market needs …….much extensive
• National goals …...to increase public sharing in business
• State of technology ….latest and upgraded
• Industrial competitors …..much competition
• Government regulations ….all regulation must be followed strictly.

pg. 20
 Stock Management
System

easibility analysis

The feasibility of a project can be ascertained in terms of technical factors, economic factors,
or both. A feasibility study is documented with a report showing all the ramifications of the
project. In project finance, the pre-financing work (sometimes referred to as due diligence) is
to make sure there is no "dry rot" in the project and to identify project risks to ensure they can
be mitigated and managed in addition to ascertaining "debt service" capability

Technical Feasibility. Technical feasibility refers to the ability of the process to take
advantage of the current state of the technology in pursuing further improvement. The
technical capability of the personnel as well as the capability of the available
technology should be considered. Technology transfer between geographical areas and
cultures needs to be analyzed to understand productivity loss (or gain) due to differences (see
Cultural Feasibility). Since we are using Java 6 , struts 1.3, Tomcat 5.5,weblogic 8.1
and so on so technically our project is feasible.

Managerial Feasibility. Managerial feasibility involves the capability of the

infrastructure of a process to achieve and sustain process improvement. Management
support, employee involvement, and commitment are key elements required to ascertain
managerial feasibility.

Economic Feasibility. This involves the feasibility of the proposed project to generate
economic benefits. A benefit-cost analysis and a breakeven analysis are important
aspects of evaluating the economic feasibility of new industrial projects. The tangible and
intangible aspects of a project should be translated into economic terms to facilitate a
consistent basis for evaluation.

Financial Feasibility. Financial feasibility should be distinguished from economic

feasibility. Financial feasibility involves the capability of the project organization to raise the
appropriate funds needed to implement the proposed project. Project financing can be a
major obstacle in large multi-party projects because of the level of capital required. Loan
availability, credit worthiness, equity, and loan schedule are important aspects of financial
feasibility analysis.

Cultural Feasibility. Cultural feasibility deals with the compatibility of the proposed
project with the cultural setup of the project environment. In labor-intensive projects,
planned functions must be integrated with the local cultural practices and beliefs. For
example, religious beliefs may influence what an individual is willing to do or not do.

pg. 21
 Stock Management
System
Social Feasibility. Social feasibility addresses the influences that a proposed project may
have on the social system in the project environment. The ambient social structure may be
such that certain categories of workers may be in short supply or nonexistent. The effect of
the

Project on the social status of the project participants must be assessed to ensure
compatibility. It should be recognized that workers in certain industries may have certain
status symbols within the society.

Safety Feasibility. Safety feasibility is another important aspect that should be

considered in project planning. Safety feasibility refers to an analysis of whether the project
is capable of being implemented and operated safely with minimal adverse effects on the
environment. Unfortunately, environmental impact assessment is often not adequately
addressed in complex projects. As an example, the North Americal Free Trade Agreement
(NAFTA) between the U.S., Canada, and Mexico was temporarily suspended in 1993 because
of the legal consideration of the potential environmental impacts of the projects to be
undertaken under the agreement.

Political Feasibility. A politically feasible project may be referred to as a "politically

correct project." Political considerations often dictate direction for a proposed project. This is
particularly true for large projects with national visibility that may have significant
government inputs and political implications. For example, political necessity may be a
source of support for a project regardless of the project's merits. On the other hand, worthy
projects may face insurmountable opposition simply because of political factors. Political
feasibility analysis requires an evaluation of the compatibility of project goals with the
prevailing goals of the political system.

Environmental Feasibility. Often a killer of projects through long, drawnout approval

processes and outright active opposition by those claiming environmental concerns. This is
an aspect worthy of real attention in the very early stages of a project. Concern must be
shown and action must be taken to address any and all environmental concerns raised or
anticipated. A perfect example was the recent attempt by Disney to build a theme park in
Virginia. After a lot of funds and efforts, Disney could not overcome the local opposition to the
environmental impact that the Disney project would have on the historic Manassas
battleground area.

Market Feasibility. Another concern is market variability and impact on the project.
This area should not be confused with the Economic Feasibility. The market needs analysis to
view the potential impacts of market demand, competitive activities, etc. and "divertable"
market share available. Price war activities by competitors, whether local, regional, national
or international, must also be analyzed for early contingency funding and debt service
negotiations during the start-up, ramp-up, and commercial start-up phases of the project.

pg. 22
 Stock Management
System

pg. 23
 Stock Management
System
Feasibility Areas

The Feasibility Study is the preliminary study that determines whether a proposed systems
project is technically, financially, and operationally viable. The Alternatives Analysis, usually
included as part of the Feasibility Study, identifies viable alternatives for the system design
and development. Between them, the documents provide:

An analysis of the system objectives, functional requirements, and system design concepts;

• A determination of the feasibility of applying automated systems to effectively,

efficiently, and economically improve program operations;
• An evaluation of alternative approaches for reasonably achieving the objectives and
goals; and
• Identification of a proposed approach.

1.1 Overview The Feasibility Study is a critical document which defines the initial
system concepts, objectives, requirements, and alternatives. The study
also forms the framework for the system development project and
establishes a baseline for further studies.

1.2 Describe the Following a general overview of the project, the Feasibility Study should
Status Quo establish the "status quo" in the State's management of benefit programs.
The current environment may be a manual process, an automated
process, or a combination of manual and automated functions. The
environment may be paper intensive or dominated by electronic records.
The environment may be centralized or distributed. Regardless of
attributes, the current operating environment should be described.

Depending on the systems project being analyzed, the following factors

may be addressed:

• Programmatic functions;
• Information architecture;
• System architecture;
• Hardware and software inventory;
• Interface and matching;

pg. 24
 Stock Management
System
• Processing and data flow diagrams;
• Storage and retrieval;
• Inputs;
• Outputs;
• Workload,
• Validation / internal control;
• Security / Privacy;
• Emergency response, back-up, and disaster recovery;
• Personnel; and

• Space and Environment.

1.3 Define the Once the current operating environment has been described, the
Problems problems with the current system (previously stated in the Planning
APD) should be detailed. Problems may be functional - that is, the system
may be incomplete, not fulfilling all the program requirements. Problems
may be technical - for example, the system may be too slow, sized too
small, or be obsolete and inefficient in terms of hardware or software.
Problems may also relate to system cost or to access, limiting the ability
of personnel to use system information to full potential.

This step should also include a determination of the seriousness of each

problem and its effects on factors such as program clients and program
financial considerations.

1.4 Convert Once the current operational problems are identified, the State can
Problems to develop specific system objectives. For example, the system may need to
System be redesigned to use the powerful attributes of database management
software. Or the system may need to be redesigned to provide better
Objectives service to clients or to support the distributed use and processing of
information. Or the system may need to be re-engineered to simplify and
streamline work processes for greater efficiency and economy.

In defining objectives, various elements must be considered: program

needs, costs, level of effort, time schedules, allowable operational
changes, ease of future modification and expansion, and system security
and reliability. Whatever the element needing improvement, objectives
should be defined in a clear, specific, and measurable manner and in
terms general enough to be met using different automation strategies.

System objectives are critical to ensuing analysis - whether conducted to

support the Feasibility Study, requirements analysis, or development of
testing plans. In terms of the Feasibility Study, the objectives form the
framework for the formulation of the initial system requirements, are
used to ascertain the acceptability of alternatives, and form the basis for
generating costs and benefits during the ensuing Cost/Benefit Analysis.
See Table 2-1 on the following page for examples of system objectives.

1.5 Identify Constraints are factors that lie outside - but have a direct impact on - the

pg. 25
 Stock Management
System
System system design effort. Constraints may be:
Constraints and
Assumptions • Laws and regulations - for example, State, Federal, or
independent regulatory agencies may require specific design
approaches for new systems or mandate specific changes to
existing systems.
• Technological - for example, new equipment must be compatible
with existing equipment;
• Socio-political - for example, the Governor mandates that all
public assistance ADP functions be combined and managed by a
common data base management system;
• Financial - for example, proposed development and
implementation costs must remain within a specified budget.
• Operational - for example, space, staffing levels, skill mix, and
capability and competence factors may limit system options.

However, system constraints should not be used to artificially restrict or

direct the system. The objective is to plan the best system for the problem
to be solved, not to fabricate and impose constraints that limit the system
alternatives.

As with objectives, system constraints are critical to ensuing phases of

the feasibility study. They can affect system requirements and the
acceptability of alternatives.

Assumptions are factors predicted to apply to the program or systems

project. For example, the project's operational or system life - the time
required to plan, design, acquire, and implement the system plus its
operational life - must be predicted and thus forms a critical assumption
during the Feasibility Study. This assumption directly affects the period
of time for comparison of costs and benefits of system alternatives and -
for all practical purposes - sets the range of time within which the system
development breakeven point must occur.

Four rules apply to making assumptions:

• Make assumptions when essential information cannot be

determined or where the analysis is critically dependent on
certain factors, conditions, or future events;
• State assumptions realistically and in precise terms;
• Include only assumptions which will affect the analysis; and
• Document the logic underlying the assumption in the event its
soundness needs to be reassessed.

In addition to systems life, other common assumptions in cost/benefit

analysis are project development and implementation schedule,
estimated future workloads, and projected costs and values. Assumptions
can be categorized as:

• Cost/Resource,

pg. 26
 Stock Management
System
• Functional/Programmatic,

• Technical and Systems Life.

Table: Representative System Objectives

Cost/Resource Functional/Programmatic Technical

Reduced Costs Improved Services to Clients Faster Record Retrieval

• by area • by area • what records

• by how much • in what manner • by how much

Controlled Costs Reduced Error Rate More Timely Reporting

• by area • by area • what reports

• in what • by how much • by how much
manner
Increased Collections Less Processing Time
Streamlined
Processes • by area • by area
• by how much • by how much
• in what
manner Improved Management Improved Access
• by what Information
measure • by area
• by area • by how much
Reduced Staffing • in what manner
Improved Security
• by area Improved Controls
• by how much • in what manner
• by area • by what measure
Improved Staffing • by what measure
Utilization Increased Automation
Interface / Matching
• in what • by function

pg. 27
 Stock Management
System
• in what manner
manner • by area
• by what • in what manner Improved Emergency Response,
measure Back-up, and Recovery
Less Data Redundancy
Increased • by function
Productivity • by area
• in what manner • in what manner
• by area
• by how much Compliance with Federal
Requirements
Fewer Manual
Functions • by area

• by area • in what manner

• in what
manner

Increased Resources

• by area

• by how much

2.6 Develop Initial The Feasibility Study should include an initial statement of the
Functional and functional and technical requirements for the system. The baseline
Technical requirements should relate to the objectives and constraints discussed
in the previous sections, summarized as follows:
Requirements
• Functional Objectives - the requirements should support
mission and program needs. For example, the State may
require that the new system improve service to the public and
be compatible with and capable of accessing information in
related State benefit systems.
• System Objectives - the requirements should be developed in a
manner which will support the objectives. For example, if a
system objective is to allow processing at the local level, the
initial system requirements should reflect a distributed system
and the need to analyze the new information architecture
during the system design phase.
• System Constraints - The functional and technical
requirements should conform to, rather than oppose, the
system constraints. For example, if the Governor has
mandated a single, integrated data base, systems built of

pg. 28
 Stock Management
System
separate data bases should not be considered.

An overview of the system requirements should reflect a broad range

of factors, for example:

• Functional, programmatic requirements;

• Information needs;
• System needs;
• Interface and matching requirements;
• Processing and data flow needs;
• Storage and retrieval requirements;
• Inputs;
• Outputs;
• Workload, projected over time;
• Validation and internal control needs;
• Security / Privacy requirements;
• Emergency response, back-up, and disaster recovery;
• Accessibility requirements for the disabled; and/or
• Space and Environment.

The requirements should be stated briefly and in functional terms, to

the extent possible. Their development during the Feasibility Study
supports the selection of suitable alternatives. These functional and
technical needs are greatly expanded later in the planning phase
through the Requirements Analysis.

2.7 Assess Project Once the initial system requirements are defined, the State should
Feasibility verify the technical, operational, and financial feasibility of the
project.

Technical feasibility refers to the capability of current technology and

methods of operation in meeting user requirements. Technical
feasibility should include consideration of the state of the technology -
for example, is the technology "leading edge" (with commensurate
risk) or is the technology "mature" (with associated industry
standards and lesser risk).

Operational feasibility refers to the ability of the enhanced system to

fit the operational pattern and resources of the organization.

Financial feasibility refers to the ability of the State to fund (with

Federal financial participation) the costs of developing and
implementing the system.

Since limited resources - especially human and dollars - may affect

feasibility, findings from the technical, operational, and financial
feasibility analysis may require redefining or appending the system
objectives and constraints.

pg. 29
 Stock Management
System
2.8 Identify The first step in identifying alternatives is to survey the possibilities
Alternatives and to consider the wide range of alternatives which may be
available. The first part of the process is analytical and judgmental,
resulting in eliminating alternatives which are not technically or
operationally feasible. Therefore, alternatives are measured against
considerations of project feasibility.

States should consider more than one technological design

alternative when considering an automation project. For example, a
system may be centralized, relying on mainframes for the bulk of
processing. Or a system may be distributed, relying on personal
computers and minicomputers for the bulk of entry and processing.
Table 2-2 suggests representative alternatives for different types of
requirements.

Regardless of technological approach, current systems can frequently

be modified - or another State's system may fulfill the programmatic
requirements of Federal benefit programs and serve as a transfer
model.

States are required by regulation [45 CFR §95.605.1(vi)] to consider

transferring systems developed in other States to meet the
requirements. This helps expedite system development, minimize cost,
and ensure project success.

Whenever possible, several alternatives reflecting different

technological approaches - including the options of modifying current
systems and transferring another State's system - should be
analyzed. The alternatives may represent opposing strategies and
should be described in sufficient detail to permit differentiation.

All alternatives should meet the established objectives within the

system constraints, and depend on costs and benefits to determine the
most favorable alternative.

2.9 Determine Risks For each alternative developed, the effects and risks of the proposed
and Effects alternative on the current environment should be described:

• Program impacts - determine how the new system initiative

will affect current program operations and new program
requirements;
• Equipment impacts - determine how new equipment
requirements will affect current systems and whether
technological risks, such as obsolescence, maintainability,
availability, expandability, reliability, flexibility, and
compatibility, are inherent;
• Software impacts - describe what additions, conversions, or
modifications are needed on existing applications and support
software;
• Information impacts - determine how information will be

pg. 30
 Stock Management
System
affected, including accessibility, conversion, reformatting into
databases, and storage media;
• Organizational impacts - describe organizational, schedule,
accountability, personnel, and skill requirement risks and
changes;
• Operational impacts - set forth the effects on operations, such
as user and operating center procedures; user / operator and
other relationships; source data processing; data entry
procedures; information storage, retention, and retrieval
requirements; privacy; output reporting, media, and
schedules; system failure and recovery procedures; and
security and back-up requirements;
• Developmental impacts - identify the effect of the development
activity on current computing, staffing (including users),
space, system security, and contractual support resources;
• Space and facility impacts - describe the effect on space, both
in terms of square footage and necessary modifications to
facilities; and

• Cost impacts - set forth financial risks and factors that may
affect developmental or operational costs and influence the
development, design, and operation of the proposed system.

Table: Representative Alternatives

Alternative Platforms/Capacity Alternatives for Implementing

Enhancement Applications

Platform (or architecture) alternatives Alternatives range from modifying current

range from stand-alone solutions to
mainframes to distributed processing
networks. Requirements for capacity
increases may affect platforms as well as
other options.
systems, transferring and modifying another
State's system, incorporating off-the-shelf
solutions, to initiating custom development
(when more cost-effective and timely solutions
do not exist).

Architecture Transferring/Modifying another State's

System
• Client/server LAN and micros
• Distributed • Using In-house Services
• Mainframe • Using Contract Services
• Minicomputer

pg. 31

System
• Work station
• Microcomputer (stand-alone)
Outsourcing (Contracting out)
Acquire Services (other than equipment)
• From other State agencies
• Commercially
Reconfigure Existing Resources
Use of Non-automated Alternatives
• Reallocating or increasing personnel
• Manual systems or work processes
Alternatives for Acquiring Services
Services include teleprocessing, computer
time, electronic mail, voice mail, and cellular
telephone. Alternatives include using both
in-house and contractual solutions, as well
as sharing or borrowing resources.
Increase in In-House Resources<r> In-
house Development of Service Capability
Resources Sharing with other State Agencies
Contractual Commercial Services
Temporary Commercial Services
Stock Management
• Using a Combination
Off-the-shelf Software
• Generalized, such as RDBMS
Modifying or Redesigning Current Systems
• Using In-house Resources
• Using Contract Services
• Using a Combination
Custom Development
• Using In-house Services
• Using Contract Services
• Using a Combination
Alternatives for Obtaining Support
Services
Support Services include source data entry,
training, custom software development,
systems analysis and design, software
conversion, facilities management,
maintenance, equipment operation, network
management, studies, and evaluation.
Increase in Permanent Staffing
In-house Development of Service Capability
Resources Sharing with other State Agencies
Contractual Commercial Services
• Manpower Based
• Project Based
• Full Service, Per Call, On Call
Temporary Commercial Services
pg. 32
 Stock Management
System
2.10 Determine For each alternative developed, the effects and risks of the proposed
Risks and alternative on the current environment should be described:
Effects
• Program impacts - determine how the new system initiative will
affect current program operations and new program requirements;
• Equipment impacts - determine how new equipment requirements
will affect current systems and whether technological risks, such as
obsolescence, maintainability, availability, expandability,
reliability, flexibility, and compatibility, are inherent;
• Software impacts - describe what additions, conversions, or
modifications are needed on existing applications and support
software;
• Information impacts - determine how information will be affected,
including accessibility, conversion, reformatting into databases,
and storage media;
• Organizational impacts - describe organizational, schedule,
accountability, personnel, and skill requirement risks and changes;
• Operational impacts - set forth the effects on operations, such as
user and operating center procedures; user / operator and other
relationships; source data processing; data entry procedures;
information storage, retention, and retrieval requirements;
privacy; output reporting, media, and schedules; system failure
and recovery procedures; and security and back-up requirements;
• Developmental impacts - identify the effect of the development
activity on current computing, staffing (including users), space,
system security, and contractual support resources;
• Space and facility impacts - describe the effect on space, both in
terms of square footage and necessary modifications to facilities;
and

• Cost impacts - set forth financial risks and factors that may affect
developmental or operational costs and influence the development,
design, and operation of the proposed system.

2.11 Rank If more than three or four alternatives have been developed, the State
Alternatives should rank alternatives so that only the most likely to achieve the system
objectives efficiently, effectively, and economically are analyzed during the
cost/benefit analysis. Criteria for ranking the alternatives should be
established and may include factors which:

• Minimize personnel expenses over the system's operational life;

• Require minimal physical facility changes;
• Assure high levels of availability, reliability, maintainability, or
expandability;
• Meet requirements for ease of use and ready access to information;
• Achieve desired distribution of processing to minimize point-of-
entry delays;
• Achieve redundancy to guard against total system outages;

pg. 33
 Stock Management
System
• Limit development time; or
• Retain a centralized information repository for reasons of security.

Once the State has isolated no more than four and no less than two viable
alternatives - one of which is the status quo - the cost/benefit determination
may proceed.

Table: Feasibility Study - Suggested Outline

Executive Summary Initial Functional and Technical

Overview Requirements

• Purpose and Scope • Functional, programmatic

• Study Methodology requirements
• Points of Contact • Information needs
• References (such as prior APDs) • System needs
• Interface and matching
Current Environment, generally: requirements
• Processing and data flow needs
• Storage and retrieval requirements
• Programmatic functions
• Inputs
• Information Architecture
• Outputs
• System(s) Architecture
• Workload, projected over time
• Hardware and Software Inventory
• Validation / internal control needs
• Interface and matching
• Security / Privacy requirements
• Processing and data flow
• Emergency response, back-up, and
• Storage and retrieval
disaster recovery
• Inputs
• Accessibility for Disabled
• Outputs
• Space and Environment
• Workload
• Validation / internal control
• Security / Privacy Alternatives
• Emergency response, back-up, and
disaster recovery • Overview
• Personnel • Ranking Criteria, if used
• Space and Environment • Description of each alternative,
including:
Current Problems • Program impacts
• Equipment impacts
• Software impacts
• Functional
• Information impacts
• Technical
• Organizational impacts
• Access
• Operational impacts
• Cost
• Developmental impacts
• Space and facility impacts

pg. 34
 Stock Management
System
System Objectives • Cost impacts

• Cost/Resource [Cost/Benefit Analysis]*

• Functional/Programmatic [Comparison of Alternatives]*
• Technical [Recommended Alternative]*

System Constraints

• Laws and Regulations

• Technological
• Socio-Political
• Financial
• Operational

Assumptions

• Cost/Resource
• Functional/Programmatic
• Technical

• Systems Life

Scope of Feasibility Analysis

In general terms, the elements of a feasibility analysis for a project should cover the following:

Need Analysis. This indicates recognition of a need for the project. The need may affect
the organization itself, another organization, the public, or the government. A preliminary
study is then conducted to confirm and evaluate the need. A proposal of how the need may be
satisfied is then made. Pertinent questions that should be asked include:

• Is the need significant enough to justify the proposed project?

• Will the need still exist by the time the project is completed?
• What are the alternate means of satisfying the need?
• What are the economic, social, environmental, and political impacts of the need?

• Process Work. This is the preliminary analysis done to determine what will be
required to satisfy the need. The work may be performed by a consultant who is an
expert in the project field. The preliminary study often involves system models or
prototypes. For technology-oriented projects, artist's conception and scaled-down
models may be used for illustrating the general characteristics of a process. A
simulation of the proposed system can be carried out to predict the outcome before the
actual project starts.

pg. 35
 Stock Management
System
• Engineering & Design. This involves a detailed technical study of te proposed
project. Written quotations are obtained from suppliers and subcontractors as needed.
Technology capabilities are evaluated as needed. Product design, if needed, should be
done at this time.

• Cost Estimate. This involves estimating project cost to an acceptable level of

accuracy. Levels of around -5% to +15% are common at this level of a project plan.
Both the initial and operating costs are included in the cost estimation. Estimates of
capital investment and of recurring and nonrecurring costs should also be contained in
the cost estimate docuement. Sensitivity analysis can be carried out on the
estimated cost values to see how sensitive the project plan is to the estimated cost
values.
• Financial Analysis. This involves an analysis of the cash flow profile of the
project. The analysis should consider rates of return, inflation, sources of capital,
payback periods, breakeven point, residual values, and sensitivity. This is a critical
analysis since it determines whether or not and when funds will be available to the
project. The project cash flow profile helps to support the economic and financial
feasibility of the project.

• Project Impacts. This portion of the feasibility study provides an assessment of the
impact of the proposed project. Environmental, social, cultural, political, and
economic impacts may be some of the factors that will determine how a project is
perceived by the public. The value added potential of the project should also be
assessed. A value added tax may be assessed based on the price of a product and the
cost of the raw

material used in making the product. The tax so collected may be viewed as a contribution
to government coffers.

• Conclusions and Recommendations. The feasibility study should end with the
overall outcome of the project analysis. This may indicate an endorsement or
disapproval of the project. Recommendations on what should be done should be
included in this section of the feasibility report.

pg. 36
 Stock Management
System

Requirement specification & Analysis:

An accurate and through understanding of system requirements is essential to the

success of any Software Development Process. All further stages of SDLC like system analysis,
design and coding depend on how accurate well prepared and thoroughly understood the
System Requirements Specification is. Poorly analyzed requirements will disappoint the user
no matter how well designed and the well coded the software is.

Requirement specification appears to be a relatively simple task but the chances of

misinterpretation is very high, ambiguity is probable and communication gap between
pg. 37
 Stock Management
System
customer and developer is bound to bring confusions. Requirement Specifications begin with
a clear and concise heading stating in a sentence the task to be performed (i.e. work objective).
For this, we have to identify the problem first. Problem specifications serve as the basis for
identifying work objective that helps in describing the requirements in technical and precise
statements. After the initial specification reports are received, they are analyzed and refined
through customer developer interaction. System Analysis follows to determine feasibility and
Cost Benefit Analysis.
A complete understanding of requirement specification of the new system is very
important for the successful development of the software product. Requirement specification
is the foundation in the process of software development. All further development like System
Analysis, System Design, and Coding will depend on how accurate and well prepared the
requirement.

Overall Description

Requirement specification appears to be relatively simple task, but appearances are

often deceiving. There is always a chance of wrong specification because of communication
gap between user and developer, ambiguity in requirement or a wrongly specified problem.
Requirement Specification begins with a clear statement of the problem and the task to be
performed. Then requirements are described in a technical manner in precise statements.
After

the initial specification reports are received, they are analyzed and refined through
user developer interaction. System Analysis follows to determine and cost benefit analysis.

An SRS is basically an organization's understanding (in writing) of a customer or

potential client's system requirements and dependencies at a particular point in time (usually)
prior to any actual design or development work. It's a two-way insurance policy that assures
that both the client and the organization understand the other's requirements from that
perspective at
pg. 38
 Stock Management
System

The SRS document itself states in precise and explicit language those functions and
capabilities a software system (i.e., a software application, an ecommerce Web site, and so on)
must provide, as well as states any required constraints by which the system must abide. The
SRS also functions as a blueprint for completing a project with as little cost growth as
possible. The SRS is often referred to as the "parent" document because all subsequent project
management documents, such as design specifications, statements of work, software
architecture specifications, testing and validation plans, and documentation plans, are related
to it.

It's important to note that an SRS contains functional and nonfunctional requirements
only; it doesn't offer design suggestions, possible solutions to technology or business issues, or

any other information other than what the development team understands the
customer's system requirements to be.

pg. 39
 Stock Management
System

It consists following phases.

 Introduction

 Purpose

 Objective

 Scope

 Overall Description

 Product Functions

 User Characteristics

 Constraints

 Specific Requirements

 User Interfaces

 Hardware Interfaces

 Software Interfaces

 Functional Requirements

Performance Requirements

Introduction………………….

pg. 40
 Stock Management
System
Companies throughout the world issue new stock shares every day. They do so to raise capital
in order to invest in the business. Once stock shares have been issued the public is free to buy
and sell those issues through a stock broker. As the supply and demand for the shares changes
so too does the price. Changing stock prices means opportunities to profit for a trader.

Purpose…….With the arrival of the internet it is now possible to buy and sell stocks
relatively cheaply and almost instantly. This, coupled with increased volatility has given rise
to more and more people MANAGEMENT stocks rather than just buying and holding them for
years.

Objective…….Develop a web application that is fully dedicated to stock MANAGEMENT

functionalities and equipped with all modern facilities

Scope…….Since it is a web application hence its scope tends to localization as well as

globalization. It flows the information with client and server bidirectional.

Abbreviations:
1. SLA: SLA is a formal written agreement made between two parties’ .The bank &
Customer. It defines the term of engagement - the fundamental rules that will govern
the relationship.
2. Payment transaction: It includes all the Cash transaction between bank and
customer.
3. Personal details: Details of customer such as username, company, phone number,
address, website, e-mail address etc.
4. Contact details: Details of contact persons associated with the Bank (customer).
5. SMS: Stock Management System our project.

References:
• Software Engineering-Roger S. Pressman
• Java Core– Herbert Schiltd
• Oracle 9i – Ivan bayross
• Servlets and JSP – Core servlets and Jsp and head First Servlets and JSP.
• Struts- James Goodwill and Richard Hightower
• And various other resources from internet and tutorials.

Overall Description…………………..

The product is dedicated to Stock MANAGEMENT System, in which we can perform all the
operations related to stock MANAGEMENT like buying and selling of shares of different
companies by using various modes of MANAGEMENT.

pg. 41
 Stock Management
System
This product provide information about the shares exist in the current market in context of
their type and popularity.

This product also provide various techniques like real time graph and charts which helps us to
understand the market in a simulated environment. This is really a great tool to asses the
profitability of our shares in the MANAGEMENT.

Proposed System Architecture

The basic architecture of the project is divided into three layers as described below

Presentation
Layer

Business
Layer

DAO (Data Access

Objects) Layer

Fig. Layered description of Stock MANAGEMENT System

pg. 42
 Stock Management
System
Technologies and Architecture used

Software Life cycle Model: Prototype Model

Platform: Microsoft Windows XP and its latest versions

Primary Interface/Frame (Front End): JSP and HTML

Core Technology: Core Java and J2EE

Core Framework: Struts

Environment: Net Beans IDE 5.5

Web Server: Tomcat web Server

Application Server: BEA Web Logic Application Server

Connectivity: JDBC (Java database connectivity)

Secondary Interface (Back End): Oracle 9i

Application Components: Java Beans and Enterprise Java Beans

Core Architecture: MVC (Model-view-controller)

Product Functions

The major functions provided in the project are:

There are basically five modules …and the functions for every module are as described.

 Administrator Module

 Administrator, Moderator and User Account Management

 Share Quantity and its price maintenance

 Activation and deactivation of user and moderator accounts

 Privilege accessibility control.

 MANAGEMENT share report and search facility.

pg. 43
 Stock Management
System

 Registration Module

 Logging : Sign in and Sign up

 Demat Account Generation

 Bank Account generation

 User Module

 Account information view

 User information view

 Real time Market picture view (using charts and graphs)

 User Assets report

 User search facility

 MANAGEMENT Module

 Buying and selling shares

 Real time share Quantity and price updating.

 Transferring and updating funds

 Profit and loss evaluation

 MANAGEMENT Report generation

 Real time trade events fluctuations.

 Exception handling Module

 Account related Exception handling

 Amount related Exception handling

 Fake Account registration handling

 Technical exceptions handling.

 Security and other facilities

pg. 44
 Stock Management
System
 Password authentication

 Privileges authorization

 Tedious Arithmetic calculations.

User Characteristics…………………

 The user types and their characteristics are :

 Administrator

 Having all privileges

 Manage shares and accounts.

 Visualization and forecasting on the basis of

market picture view.

 Moderator

 Handling Accounts and shares.

 Monitoring information flow.

 User

 Account characteristics

 MANAGEMENT shares

Constraints

 GUI is only in English.

 There is a delay (buffering time) between the user and the observer ends during
streaming.

 The screen resolution must be set to the pre-specified settings (800X600).

pg. 45
 Stock Management
System

Specific Requirements

 User Interface:

 GUI

 Web based

 Menu Based
interface

• Hardware Interface:

• Visual: Color CRT, TFT, LCD etc

• Primary Storage: RAM min 256 for efficient result

• Secondary storage: min 10 GB recommended

• Network: fast broadband connection up to in MB/s is good.

• Processor: Pentiums are quit well.

• Software Interface:

Servlet 2.4, JSP 2.0, JavaBeans , DAO design pattern, Core Java1.6, Oracle 9i, Struts 1.2.9,
Apache Tomcat web server 5.5.12, JavaScript, Net Beans 5.5 .

Communication Interface:
Customer of bank can interact with bank by their basic information’s like account number and
account type with the help of GUI interface of the software product etc.

Assumptions & Dependencies

This system will keep on operating successfully under the following assumptions

• The hardware never fails.

• No user fiddles with source code or database of the system.
• None of the external components used are removed from the system.
• Only one (if possible) administrator should handle the server operation at a time.

pg. 46
 Stock Management
System

• All the intermediate users are assumed to have the overview of how the complete IS
will work, should work. Proper training program should be arranged to properly
work on the system.

Performance Requirement

• It is a multi-user system with no limit on the number of users.

• It is a truly online transactional processing system with capability to be accessed
simultaneously by many users at the site of the organization as well as at the end of
other people involved.
• It is having the auto as well as manual backup facility for the databases.
• It is capable of working on windows based operating systems like Windows
XP/NT/2000.
• It is user-friendly with online help, error messages, pop up menus, list down data etc
for data entry, report generation, query generation and MIS reports.
• Necessary pull down menus and list boxes are provided for easy data entry.
• Validation rules for data entry prior to updating of records are supported.
• At each stage of the enquiry process, necessary reports are generated and printed in
the specified formats.
• It provides an Online management information to the top management on the status,
progress, summary, reports, POs and expenditure involved in the form of tables /
charts on weekly and / or monthly basis.
• The software is flexible and easily upgradeable to add any additional modules and to
modify and process parameters. It has the capability to seamlessly integrate any
additional modules by the users in future.
• Further maintenance is possible by the users.

pg. 47
 Stock Management
System
• The software is compatible with the available hardware status of the organization's
system.
• Any enquiry being made by any customer is never deleted from the records. Instead is
marked from LIVE to DEAD.

Accuracy Requirement

• This software has a very fine capability for multi-level data access security for each user
including the data access filtering and restrictions at records & fields levels.
• Distribution and control of rights for data viewing, modifying, updating, deleting,
inserting, etc. are configurable to each and every user by the DBA.
• There is a full proof data and information security against deletions/modifications by an
unauthorized user.
• The transactional log and user loggings are maintained at each stage to trace the user
activity and to audit the data and resources.
• Disaster recovery procedure is laid down for all possible modes of disasters and all
preventive measures are being taken to avoid the disaster / breakdown. It is documented
and displayed at all user locations.
• Necessary checks are being incorporated for Validation & Verification (V&V) rules for
each field.
• There is a provision of double-checks are incorporated for committing /saving a
transaction, for passing the flow to the next stage and for updating / inserting of records
in the databases.
• The deletion of any sort of data is prevented for all users.

pg. 48
 Stock Management
System

Functional requirements

 All the functions described above provided by the software are the major requirements.

 Example :

 MANAGEMENT Module login process

 Function name: Sign in

 Description: User accessibility gateway by checking

security aspects.

 Input: Any User (including Administrator or

Moderator)

 Process: Check its User id and password authentication

 Output: Redirect to the corresponding page.

 Normal flow of Events:

 A) Select the logging option

 B) choose the sign in option

 C) Enter ID and PASSWORD

 D) Verification takes place.

 E) Displaying the corresponding result.

pg. 49
 Stock Management
System

Interaction between the user and the system in Sign-in high level functional requirement

pg. 50
 Stock Management
System

Use Case Diagram

pg. 51
 Stock Management
System

Nonfunctional Requirements

Fig: nonfunctional requirements

• Availability: - The system should be properly supported by the required H/W and S/W
interface needs so that any user can access the data from any place sitting on the internet
connectivity node.

Maintainability: - It is a system which incorporates this feature as it is the system

whose defects can be easily removed by the programmers. This system can be easily

pg. 52
 Stock Management
System
adapted to meet the changing requirements of its users or the changing environment in
which it operates.

• Portability: - its design is relatively machine independent. It is being coded in languages

which are well-defined & meet to the standards, hence more portable.

• Visibility: - Any user can view the menu of the system and can work out the processing
even from a remote place. There is no hiding of data and incorporates easy availability
and accessibility.

• Efficiency: - It is an efficient system because it fulfills most of the requirements being

mentioned by the users. It uses least amount of devices & memory space for execution of
the package on the systems at the client’s end.

• Reliability: - It is a very reliable system. Two separate processes of the package are
unique & non-interdependent to each other. The execution of one process does not effect the
processing of second one. The complete processing does not effect the normal operations of
the company terminals.

• Safety & Security: - The processes/operations under each consideration are completely
equipped with alert messages as and when required. The software never permits any
mishandling or misfiring of data in the database tables at any point of processing.

• Standard Compliance: - It follows a standard format or layout in the designing as well

as operational phases. This helps the user to work on the system in an effective and
efficient way at any site of the office. They can work on its database to keep all the
concurrent updating.

pg. 53
 Stock Management
System

SDLC Methodology

Computerization of Stock Management System development follows an iterative or

evolutionary model. Iterative development is an approach to build software in which the
overall lifecycle is composed of several iterations in sequence. Each iteration is a self-
contained mini-project composed of activities such as requirement analysis, design,
programming, and test. The goal for the end of iteration is an iteration release, a stable,
integrated and tested partially complete system. Most iteration releases are internal, a
baseline primarily for the benefit of the development team-they are not released externally.
The final iteration release is the complete product

System Overview
Stock management system is the upgraded and most flexible system till now. This system will
manage all the shares , price , and user details as well as their MANAGEMENT details. The six
major modules are:

1. Banking module
2. Administration Module
3. Registration Module
4. User Module
5. MANAGEMENT Module
6. Exception handling module

The “Stock management system” is software that automates the stock MANAGEMENT process
of shares for the users online. By using this web application all the manual works can be done
by using computers from:

1. Account opening
2. registration
3. MANAGEMENT
4. Administration
pg. 54
 Stock Management
System
5. Searching n surfing and report generation
6. Question bank preparation for test according to company’s rule.
7. Database view
8. Preparation of reports.

User Categories:

1. Server side- Administrator and employees/ operator/Moderator.

2. Client side- users.

Design and Implementation Constraints

The constraints that are imposed on the development of this project are outlined below.

• The system will be accessed through an internet browser (predominantly Microsoft’s

Internet Explorer). The front end has to therefore be a HTML based screen designer.
The proposed system will be using HTML only.
• The data store will be Oracle Server. This is the data store. A plug in to this site must
also use Oracle.
• The data from Oracle will be retrieved using the Java Data Base Connectivity
technology, with the usage of the JDBC-ODBC bridge feature of Java.
• JSP technology will be used as the go between Java and HTML. The JSP script will be
embedded in HTML.
• The above requirement imposes that a JSP server will be available and running to
access the proposed system.
• The security measures should be as outlined before. Only Moderator or administrator
should be able to access a particular module.
• The project is to be developed in a modular fashion adhering to standard
programming practices.

pg. 55
 Stock Management
System

Assumptions and Dependencies of the system

The system depends on a few parameters that are necessitated by Sierra Atlantic. These
dependencies are as outlined below.

• The login will be a part of the existing database. SMS is a portal which enables every
employee of SMS to login using his user ID and password. On a successful login the
user will be able to access all the resources, this project included.
• The user ID for the session is maintained by SMS. This will be used by the proposed
system also for the user ID.
• The proposed system assumes that the maintenance of the database will be done
externally to this system. Any changes to the existing table structure will mean that the
proposed system’s coding might also need to be altered.
• For the purposes of developing this system, a dummy database will be used. This will
serve as a place holder for the original database.

pg. 56
 Stock Management
System

APPROACH TO DEVELOP THE SYSTEM

System/Information

Engineering

Analysis Design Code Test

Prototyping Approach
Implementation

The company has already aware of that what should the proposed system will do and how. So
we follow the prototyping approach for the analysis and design phase and then linear model
of software development.

The prototype paradigm begins with requirement gathering. Development and customer meet
and define the overall objectives for the software, identify whatever requirements are known,
and outline areas where further definition is mandatory. A “quick design” occurs. The quick
design focuses on a representation of those aspects of the software that will be visible to the
customer/user. The quick design leads to the construction of a prototype. The prototype is
evaluated by the customer/user and used to refine requirements for the software to be

pg. 57
 Stock Management
System
developed. Iteration occurs as the prototype is tuned to satisfy the needs of the customer, while
at the same time enabling the developer to better understand what needs to be done.

After design phase is approved, we follow the linear model to develop the complete system.
After design phase we move to coding and testing then implementation phase.

In prototyping model we first develop a working prototype of the software instead of

developing the actual software. The working prototype is developed as per current available
requirements. The developers use this prototype to reefing the requirements and prepare the

Final specification document. Because the working prototype has been evaluated by the
customer, it is reasonable to expect that the resulting specification document will be correct.

When the prototype is created, it is reviewed by the customer. Typically this review gives

feedback to the developers that helps to remove uncertainties in the requirements of the

software, and starts an iteration of refinement in order to further clarify requirements. The

prototype being developed is not the final product to be delivered and the code generated in

the prototype is being get thrown away but the experience gathered from developing the

prototype helps in developing the actual system.

The developers should develop prototype as early as possible to speed up the software
development process. After all, prototype has to be discarded. After the finalization of
software requirement specification (SRS) document, the prototype is discarded and actual is
then being get developed.

pg. 58
 Stock Management
System

pg. 59
 Stock Management
System

PROTOYPING MODEL

pg. 60
 Stock Management
System
Working of Prototype model can be described as :

Requirements

Quick Design

Refinement of
Requirements as per
Implement
suggestions

Customer Evaluation

Design

Implementation and Unit Testing

Integration and System Testing

Operation and Maintenance

pg. 61
 Stock Management
System
T

heoretical framework

Introduction

The technologies at the back-end and front-end are used, is discussed in this chapter

About Java
HISTORY OF JAVA

Java language was developed by James Gosling and his team at sun micro systems and
released formally in 1995. Its former name is oak. Java Development Kit 1.0 was released in
1996. To popularize java and is freely available on Internet.

Overview of Java

Java is loosely based on C++ syntax, and is meant to be Object-Oriented Structure of

java is midway between an interpreted and a compiled language. The java compiler into Byte
Codes, which are secure and portable across different platforms, compiles Java programs.
These byte codes are essentially instructions encapsulated in single type, to what is known as
a java virtual machine (JVM), which resides in standard browser.

JVM verifies these byte codes when downloaded by the browser for integrity. Jvms available
for almost all OS. JVM converts these byte codes into machine specific instructions at runtime.

FEATURES OF JAVA

• Java is object-oriented language and supports encapsulation, inheritance,

polymorphism and dynamic binding, but does not support multiple inheritances.
Every thing in java is an object except some primitive data types.
• Java is portable architecture neutral that is java programs once compiled can
be executed on any machine that is enabled.
• JAVA is distributed in its approach and used for Internet programming.
• Java is robust, secured, high performing and dynamic in nature.

pg. 62
 Stock Management
System
• Java supports multithreading. There for different parts of the program can be
executed at the same time.

About JSP

OVERVIEW OF JSP TECHNOLOGY

The JSP technology will be used to interface HTML with Java. The JSP technology provides a
seamless connection with Java and presents an easy to use, Java-like programming
constructs that can be scripted within HTML files. Java Server Pages is a technology for
developing web pages that include dynamic content.

A JSP page contains standard markup language elements, such as HTML tags, just like a
regular web page. A JSP page also contains special JSP elements that allow the server to
insert dynamic content in the web page.

ARCHITECTURE DESIGN

The system will be designed using the three-tier model. The database server will form one tier
of the three tiers. The database server used will be Oracle 9i. The next tier is the component,
which will retrieve data from the database. The component used for this purpose will be Java
language with its rich data communicating abilities. The JDBC – ODBC Bridge will be used
for interlinking Oracle and Java. The last tier is the Web Server, which will process the
requests from the user front end, i.e. the browser and translate them into calls to the Java
language. The web server used for this project is the JSP server. For purposes of developing
this project Tomcat Server will be used, though any JSP server can be used as the web server.

The web server will form the interface between the JSP scripting and Java functions. This tier
will acts as a proxy for all client requests. In this environment, the client requests are
translated into calls to the java functions. These java functions will communicate with the

pg. 63
 Stock Management
System

database server and perform the required data handling and then return data back to the web
server. The web server then sends these data back to the client after converting them into

CLIENT (BROWSER)

Client requests
data using JSP
Web server
processes the
information and DATABASE SERVER
sends back
HTML stream to
the browser

Database server
WEB SERVER sends back the
Required data is
sent back to the appropriate data
web server

JDBC request
the data
required from
Web server locates java the database
file to process the server
request for data

pg. 64
 Stock Management
System
HTML statements, which are displayed by the Internet browser. The way this arrangement
works can be explained using the figure.

ADVANTAGES OF JSP

 JSP supports both scripting and element-based dynamic content.

 Allows developing custom tag libraries.
 JSP pages are precompiled for efficient server processing.
 JSP pages can be used in combination with servlets that handle the business logic.
 High Security.
 Can run on any J2EE compatible web Server.
 It can run on any OS that have J2EE compatible web server.
 JSP separates the dynamic and static parts.
 High Quality tool supports.
 JSP supports N tier Application.
 Write Once, Run Everywhere.
 JSP is vender Neutral.

ABOUT ORACLE 9i

Oracle 9i is the current database server being used by Sierra Atlantic and the system was
developed using Oracle as the database server to be compatible with Sierra Atlantic’s “My
Sierra” network. The system draws some of its data from the existing database of the
company, which also means that the system being developed should use the same database
server that is being used for the existing data.

pg. 65
 Stock Management
System

ABOUT HTML

HTML (hyper text markup language) is a language used to create hypertext documents that
have hyper links embedded in them. It consists of tags embedded in the text of a document.
With HTML we can build web pages or web document s. it is basically a formatting language

and not a programming language. HTML is used to design the interface to the application.
HTML is platform independent.

Examples of browsers used to be web pages include:

• Netscape
• Internet Explorer

ABOUT INTERNET EXPLORER 5.0

An Internet browser is required to access the training function automation system. IE 5.0 is
the most widely used browser at Sierra Atlantic. Hence the system was designed for IE; it will
work equally efficiently with any other browser.

ABOUT JAVA SCRIPT

Java script is a general purpose, prototype based, object oriented scripting language
developed jointly by sun and Netscape and is meant for the WWW. Java script borrows most
of its syntax from java but also inherits from awk and perl, with some indirect influence from
self in its object prototype system.

Java Script is almost as easy to learn as HTML and it can be included directly in HTML
documents. Java Script was developed independently of java. Java script is a high level
pg. 66
 Stock Management
System
scripting language that does not depend on or expose particular machine representations or
operating system services.

FEATURES:

• Java script is embedded into HTML documents and is executed with in them.
• Java script is browser dependent.

• JavaScript is an interpreted language that can be interpreted by the browser at

run time.
• Java script is loosely typed language
• Java script is an object-based language.
• Java script is an Event-Driven language and supports event handlers to specify
the functionality of a button.

ABOUT WEB SERVER

TOMCAT SERVER

The Tomcat web server supports the JSP technology. This was the server used to develop the
system. Tomcat is a very simple, but functional web server. It also does not occupy much disk
space and it is very easy to start and stop the web server. Any web server, which supports the
JSP technology, can also be used.

ABOUT APPLICATION SERVER

WEBLOGIC SERVER

The Tomcat web server supports the JSP technology as well as EJB technology. This was the
server used to develop the system. Weblogic is a very simple, but functional Application

pg. 67
 Stock Management
System
server. It also does not occupy much disk space and it is very easy to start and stop the web
server. Any web server, which supports the JSP technology, can also be used.

ABOUT STRUTS FRAMEWORK

The Struts framework provides the flexibility to develop the much less coupled applications . It
generalizes and strictly implements MVC-model View Controller Architecture. That is the
basic need of our architecture.

nalysis

INTRODUCTION

Requirements analysis is the process of analyzing the information needs of the end
users, the organizational environment, and any system presently being used, developing the
functional requirements of a system that can meet the needs of the users.

After detailed studying and analysis I found that in the existing system the land
records are being maintained by the stock brokers manually. As the users were facing many
problems as discussed in problem domain.

System Analysis Methods

• Review the written documents Studying: the existing manuals and forms we
gather information regarding the existing system. There are some manuals that
describe the role of each person in the share MANAGEMENT department .They keep
user and shares record for the concerned persons.
• On-site observation: Observation must be carried out to gather the information
about the existing system. On visiting the India bulls and Share khan office in Noida
the massive information is collected about the existing system. The enormous volume
of inefficiency and disorganization was there regarding to users expectations. Each
user are dependent on the brokers.

pg. 68
 Stock Management
System
• Interview: To know staff or officers perception regarding the manual system an
interview is conducted .During the interview we came to know about various steps
they follow in handling of shares and records of persons, what are the difficulties they
face and other correspondences.
• Questionnaires: Questionnaires can be used to get information from large groups of
people. Advantages of questionnaires are anonymity and evidence of trends. Various
questionnaires are made to the employee or staff in regard to the requirement they
need. A set of question are asked to know about various necessity the desire like Hindi
Subject data entry, edit the wrong entry made, listing the pending details, security to
the records etc.

Analysis Modeling:

At a technical level software engineering begins with a series of modeling a tasks that lead to
a complete specification of requirements and a comprehensive design representation for the
software to be built. The analysis model, actually a set of models, is the first technical
representation of a system .Over the years many methods have been proposed for the analysis
modeling. However, two now dominate. The first, structured analysis is a classical modeling
method and another approach, Object-oriented analysis.

The Elements of the Analysis Model:

The analysis model must achieve three primary Objectives:

• To describe what the customer requires,

• To establish a basis for the creation of a software design, and
• To define a set of requirements that can be validated once the software is built.
To accomplish these objectives, the analysis model derived model derived

During structured analysis takes the form illustrated in fig below.

Data
pg. 69
DFD
ERD
Dictio
nary
 Stock Management
System

At the core of the model lies the Data Dictionary- a repository that contains descriptions of all
data objects consumed or produced by the software. Three different diagrams surround the
core. The entity relation diagram (ERD), depicts relationships between data objects. The ERD
is the notation that is used to conduct the data modeling activity. The attributes of each data
object noted in the ERD can be described using a data object description.

The data flow diagram (DFD) serves two purposes:

• To provide an indication of how data are transformed as they move through the
system and
• To depict the functions (and sub functions) that transforms the data flow. The DFD
provides additional information that is used during the analysis of the information
domain and serves as a basis for the modeling of function. A description of each function
presented in the DFD is contained in a process specification (PSPEC).
• The state transition diagram (STD) indicates how the system behaves as a
consequence of external events. To accomplish this, the STD serves as the basis for
behavioral modeling. Additional information about the control aspects of the software is
contained in the control specification.

pg. 70
 Stock Management
System
Components of the System

Based on the analysis done, the system was partitioned into various functional modules to
bring down the complexity of the system. These modules help in identifying specific functions
and also create an easy to understand and develop approach during system development.

The system is decomposed into the following main modules:

• Server-Side
The main use of the software at server side is for administrative purpose. To
administer the selection procedure following modules are identified:

1) User data management

o User account Management
o Share MANAGEMENT Process
2) Registration Module
o New user
o Demat account generation
o Registration
o Evaluation of entries & record updating
o Login ID and password generation
3) User Module
o Handling queries and providing search facility.
o Providing Information about users and modifications
o User Assets report
4) MANAGEMENT Module
o Buying and selling shares
o Trade report generation
o Profit loss evaluation
o Search for shares to be purchased in the market
5) Help and Support Module (Exception Handling module).
• Client –Side

pg. 71
 Stock Management
System
Here the user may be novice of using computers so all the consideration are done
according to that level. Following are the modules that are identified and used by the
client-side user:

1) New Registration
2) Login
3) On Line MANAGEMENT
4) search & Information facility
Once the modules have been identified, the next task is to identify the inter relationship among
these modules. These modules must work together to achieve the overall goal of Graduate
Selection Procedure. The process of identifying each module’s tasks, the inputs to this module
and the outputs expected from them have been identified and represented in the next few sub
sections.

Server Side:

Table 1. user data management

Table 1.1 user Acccount Management:

Expected Inputs

• Information regarding user.

Expected Outputs

• After submitting that confirmation message will be displayed.

Other Tasks

• Validation of fields.
• Proper checking and authentication for valid entry.

Table 1.2 Account generation Process :

Expected Inputs

• Verifying all the fields and verify its demat account.

Expected Outputs

• Provide login and password

Other Tasks

pg. 72
 Stock Management
System
• Validation of fields.
• Proper checking and authentication for valid entry.

MANAGEMENT regarding Management:

Table 2.1 index display

Expected Inputs

• Its login id and it’s demat account details.

Expected Outputs

• Display the list of tradable shares so that he/she can trade.

Other Tasks

• Validation of fields.
• Proper checking and authentication for valid entry.

Table 2.2 Buying process

Expected Inputs

• Its login id and its demat account details.

• Its Exposure details and shares selected and its price details and its status too.
Expected Outputs

• Shares credited and exposure debited in the corresponding user account.

Other Tasks

• Validation of fields.
• Proper checking and authentication for valid entry.

pg. 73
 Stock Management
System

Table 2.3 Selling process

Expected Inputs

• Its login id and it’s demat account details.

• Its Exposure details and shares selected and its price details and its status too.
Expected Outputs

• Shares debited and exposure credited in the corresponding user account.

Other Tasks

• Validation of fields.
• Proper checking and authentication for valid entry.

Table 2.3 Searching process

Expected Inputs

• Its login id and it’s demat account details.

• Shares selected.
Expected Outputs

• Shares description, price and availability of the corresponding selected share.

Other Tasks

• Validation of fields.
• Proper checking and authentication for valid entry.

pg. 74
 Stock Management
System

ystem Design

INTRODUCTION

This project has to design and implement a web application for the purpose of online share
MANAGEMENT. The system will be available to every one via Internet. The system must be
designed to retrieve data from a database server and display the results in a formatted
manner on any browser. Any modifications to the data must also be done through an
interface provided by the browser.

System design provides the understanding and procedural details necessary for
implementing the system recommended in the system study .Emphasis is on translating the
performance requirements into design specifications . The Design phase is a transition from
a user – oriented document (System proposal) to a documented oriented to the programmers
or database personnel.

System design goes through following phases of development :-

Physical design

Logical design

Database & file design

Interface design

Functional Architecture Design / Physical design

pg. 75
 Stock Management
System
The system will be designed using the three tier model. The database server will form one tier
of the three tiers. The database server used will be Oracle 9i. The next tier is the component
which will retrieve data from the database. The component used for this purpose will be Java
language with its rich data communicating abilities. The JDBC – ODBC Bridge will be used
for interlinking Oracle and Java. The last tier is the Web Server which will process the
requests

from the user front end, i.e. the browser and translate them into calls to the Java language.
The web server used for this project is the JSP server. For purposes of developing this project
Tomcat Server will be used, though any JSP server can be used as the web server.

The web server will form the interface between the JSP scripting and Java functions. This tier
will acts as a proxy for all client requests. In this environment, the client requests are
translated into calls to the java functions. These java functions will communicate with the
database server and perform the required data handling and then return data back to the web
server. These data are then sent back to the client by the web server after converting them into
HTML statements, which are displayed by the internet browser. The way this arrangement
works can be explained using the figure

pg. 76
 Stock Management
System

CLIENT (BROWSER)

Client requests
data using JSP
Web server
processes the
information and DATABASE SERVER
sends back
HTML stream to
the browser

Database server
WEB SERVER sends back the
Required data is
sent back to the appropriate data
web server

JDBC request
the data
required from
Web server locates java the database
file to process the server
request for data

pg. 77
 Stock Management
System

Architectural Design The basic architecture for the proposed system is like that

Presentation Layer: All the Jsp and html pages are designed in this tier

Business Layer: All the business logic and service code are written here.

DAO Layer: All the database connections and resultset related codes are written here

Detailed Design uses standard MVC Architecture

pg. 78
 Stock Management
System

The Model-View-Controller Design Pattern

A design pattern is a series of objects and object relationships that provide a proven,
extensible solution to a particular software design problem. The Model-View-Controller
(MVC) pattern is arguably the best known, most famous design pattern of them all.

MVC was originally developed in the late 1970s at the Xerox Palo Alto Research Center
(PARC). It was originally built to manage the GUI and user interaction on some of the first
window-based computers (another innovation from the PARC—in addition to Ethernet, local
area networks, mice for input devices, and numerous other firsts).

The design problem that MVC solves is that of simplifying three primary functions that are
common in many applications:

• Maintaining the data in a back-end store or remote system

• Building the end-user presentation layer
• Maintaining the conditional logic that decides which screens are presented to the user,
what happens when errors occur, and exactly how and when the remote systems are
updated

pg. 79
 Stock Management
System
It is possible to combine all this processing into a single module and get a system to work. (In
fact, a significant amount of early JSP development did exactly that!) Problems primarily
occur when you try to perform maintenance on the code. In the case of JSP, this is
compounded by the fact that the HTML designers who maintain the look and feel of the
application are different people (and have different skill sets) from those who maintain the
Java code that controls the processing.

MVC addresses this problem by separating the code into three distinct areas:

• Model components that maintain data in a back-end store or remote system

• Views that build the end-user presentation layer
• Controllers to maintain conditional logic that decides which screens are presented to
the user, what happens when errors occur, and exactly how and when the remote
systems are updated

MVC simplifies maintenance by keeping all this logic from becoming intertwined. It allows the
details of each piece to be hidden from the others and reduces the coding linkages between
them. This is how MVC provides a natural boundary between the people who write the Java
and the people who maintain the HTML and presentation layer.

A good example of this is in how MVC can simplify exception processing. Imagine that after a
user logs in, you send a request to a remote system to fetch the user's customer information.
What do you do if the remote system is unavailable? In normal JSP processing, it's common to
embed logic at the top of your JSP file to detect this and change what you display to the user
when the problem occurs. Using MVC, you can pull this logic out of the JSP page altogether:
You create a page dedicated to presenting the error message and have the Controller
determine which page to send the user to. If the remote system is available, the user gets the
first page. If not, the Controller sends him to the error page.

This approach to exception processing has multiple benefits. The first comes from the fact that,
on many pages, multiple types of exceptions must be handled. Having a single JSP page that
detects all possible errors and presents a different message when each error happens can
become complicated fast. Moving that logic into a Controller makes things easier to maintain:
The logic is maintained in the Controller, and only the presentation is maintained in the JSP
file.

Of course, another primary benefit of pulling the exception logic out of the main JSP pages is
that it makes maintaining the JSP pages easier!

These benefits really extend to all forms of conditional processing. Here are some other
examples:

• If different Views are required depending on what data is retrieved from a database or
remote system (for example, products on sale versus products not on sale), the
Controller component can make the decision about which page to present. This keeps
the logic out of the JSP page itself.

pg. 80
 Stock Management
System
• If your site changes based on either the time of day or the day of the week, that logic is
easy to implement in the Controller. You simply have the Controller check the date and
forward the user to the appropriate page.
• Sometimes a data entry process can span several pages, some of which are optional.
An example of this is signing up for insurance: You need to be shown the data entry
pages for dependents only if you choose family coverage. In cases like this, MVC makes
it easy to control the flow of pages that are shown to the user. Trying to embed this
logic into the JSP pages makes things much more complex.

ntity Relationship Diagram

In order to make the physical 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 object that can be identified.
According to its entities have relationship with each other an entity relationship diagram can
represent various entities of any system.

pg. 81
 Stock Management
System

ata Flow Diagram

pg. 82
 Stock Management
System

pg. 83
 Stock Management
System

pg. 84
 Stock Management
System

pg. 85
 Stock Management
System

Procedural Design / Logic Design

For a System it describes the input(source),output(destination) ,database(datastores) And

procedures (data flow) all in a format that meets the user’s requirement When analysis
prepare the logical system design , they specify the user needs at a level of detail that
virtually determines the information flow in and out of the system required data resources .
The logical design also specifies , input forms and screen layout .The activities following
logical design are the procedure followed in the physical design e.g. Producing programs,
software, file and a working system. Design specification instructs the user about what the
system should do.

pg. 86
 Stock Management
System
Flow diagram of MANAGEMENT module

pg. 87
 Stock Management
System

ogical Design

Database Design

We have used relational data model as the model for our database design.
Database is optimized up to Third Normal Form

The database has been implemented for banking system by using Oracle Environment .This
environment facilitates all the necessities for the database design as well as it take care of the
integrity constraints and normalization phenomenon.

Normalization

Normalization provides for table optimisation through the investigation of entity

relationships. Main purpose of normalization is to avoid Data redundancy and some
unforeseen scalability factors. Normalization is done to remove Insertion, Updating and
Modification anomalies and redundancy of data. A certain level of normalization of tables in
database gives a particular normal form based of particulars steps followed. Database can be
normalized up to any defined normal forms according as the need of application and its
effectiveness.
Database of Stock management system is normalized up to Third Normal Form.
Further normalization of database was not considered taking into account the need of
application and ease of working with database.
 The database is in First Normal Form as all the fields of all tables are atomic. There
is no multivalued field in any table. Table Inquiry needs to store more than one inquiry
officers but as it was known that not more than two inquiry officers are appointed, so
two different fields for each inquiry officers are used. Hence the tables satisfy the
constraint of atomicity of first normal form.

pg. 88
 Stock Management
System
 The database is in Second Normal Form as it satisfies the constraint of full
functional dependency. All the fields of all tables are fully functional dependent on the
primary key.
• The database is in Third Normal Form as all its tables satisfy the constraint that
there should be no transitive dependency. No field has transitive dependency on the
key field. Thus database also satisfies the constraints of third normal form.

Table : HP19_ROLE_TYPES
S.No. Field No. Data type Constraints
1 Role_Code Varchar2(50) Primary Key
2 Role_Desc Varchar2(75) NOT NULL
3 Create_Date Date NOT NULL
4 Created_By Varchar2(30) NOT NULL
5 Modify_Date Date NULL
6 Modified_By Varchar2(30) NULL

Table : HP19_USER_Registration
S.No. Field No. Data type Constraints
1 Registration_Id Varchar2(25) Primary Key
2 First_Name Varchar2(50) NOT NULL
3 Second_Name Varchar2(50) NOT NULL
4 Third_Name Varchar2(50) NOT NULL
5 Dob Number(3) NOT NULL
6 Gender Char(10) NOT NULL
7 Address_Line1 Varchar2(50) NOT NULL
8 Address_Line2 Varchar2(50) NULL
9 Address_Line3 Address_Line3 NULL
10 Country Varchar2(20) NOT NULL
11 State Varchar2(20) NOT NULL
12 City Varchar2(25) NOT NULL
13 Pin Code Number(10) NOT NULL
14 Contact_Number Number(10) NOT NULL
15 Email_Id Varchar2(30) NOT NULL
16 Pan_Number Number(30) NOT NULL
17 Deemat_Account_Numbe Number(30) NOT NULL
r
18 Bank_Name Varchar2(40) NOT NULL

pg. 89
 Stock Management
System
19 Create_Date Date NOT NULL
20 Modify_Date Date NULL
21 Created_By Varchar2(30) NOT NULL
22 Modified_By Varchar2(30) NULL

Table : HP19_USER_Login
S.No. Field No. Data type Constraints
1 Login_Id Varchar2(25) references HP_USER_Registration,
2 Password Varchar2(50) NOT NULL,
3 Role_code Varchar2(50) Reference HP_Role_Type
4 Registration_I varchar2(25) references HP_USER_Registration
d

Table : HP19_SHARE_MASTER
S.No. Field No. Data type Constraints
1 Share_Code Varchar2(25) Primary Key
2 Share_Desc Varchar2(50) NOT NULL
3 Total_Shares Number(20) NOT NULL
4 Available_Share Number(20) NOT NULL
s
5 Create_Date Date NOT NULL
6 Created_By Varchar2(30) NOT NULL

Table : HP19_USER_EXPOSURE_DETAILS
S.No. Field No. Data type Constraints
1 User_Exposure_Deatils_Id Varchar2(200 Primary Key
)
2 Login_Id Varchar2(25) ReferencesHP_USER_Registration
3 Total_Exposure Number(30) NOT NULL
4 Used_Exposure Number(20) NOT NULL
5 Available_Exposure Number(30) NOT NULL
6 Modify_Date Date NOT NULL

pg. 90
 Stock Management
System

Table : HP19_USER_MANAGEMENT_DETAILS
S.No. Field No. Data type Constraints
1 User_MANAGEMENT_Details_I Varchar2(25) Primary Key
d
2 Login_Id Varchar2(50) references
HP_USER_Registration
3 Share_Code Varchar2(50) references
HP_SHARE_MASTER
4 Share_Quantity Number(20) NOT NULL
5 Share_Unit_Price Number(3) NOT NULL
6 Trade_Amount Number(20) NOT NULL
7 Trade_Mode Varchar2(50) NOT NULL
8 Trade_Date Date NULL

Table : HP19_CURRENT_SHARE_PRICE
S.No. Field No. Data type Constraints
1 Share_Code Varchar2(15) References HP_SHARE_MASTER
2 Current_Share_Price Number(30) NOT NULL
3 Create_Date Date NOT NULL
4 Created_By Varchar2(30) NOT NULL
5 Modify_Date Date NULL
6 Modified_By Varchar2(30) NULL

Table : HP19_Demat_Assests
S.No. Field No. Data type Constraints
1 Demat_Account_Number Date references DematAccount
2 Share_Code Varchar2(30) References HP_SHARE_MASTER
3 Share_Quantity Number(20) NULL

Table : CREATE TABLE HP_login

S.No. Field No. Data type Constraints

pg. 91
 Stock Management
System
1 UserId VARCHAR2(10) PRIMARY KEY,
2 PassWord VARCHAR2(10) NOT NULL
3 Type VARCHAR2(30 NOT NULL
)

Table : CREATE TABLE HP_Savings

S.No. Field No. Data type Constraints
1 AccNo Varchar2(25) Primary Key
2 AccType Varchar2(50) NOT NULL
3 Name Varchar2(50) NOT NULL
4 Opendate Date NOT NULL
5 Address Varchar2(50) NOT NULL
6 Phone Number NOT NULL
7 Occupation Varchar2(50) NULL
8 Nation Varchar2(20) NOT NULL
9 Cheque Varchar2(25) NOT NULL
10 Income Number(10) NOT NULL
11 Status Varchar2(20) NOT NULL
12 Dob Date NOT NULL

Table : CREATE TABLE HP_Reports

S.No. Field No. Data type Constraints
1 TransNo Varchar2(25) Primary Key
2 AccNo Varchar2(50) NOT NULL
3 Name Varchar2(50) NOT NULL
4 AccType Varchar2(20) NOT NULL
5 TDate Date NOT NULL
6 TraType Varchar2(30) NOT NULL
pg. 92
 Stock Management
System
7 TraAmt Number(9,2) NULL

Table : CREATE TABLE HP_DematAccount

S.No. Field No. Data type Constraints
1 DmatId Varchar2(25) Primary Key
2 AccNo Varchar2(50) NOT NULL
3 Name Varchar2(50) NOT NULL
4 AccType Varchar2(20) NOT NULL
5 PanNo Varchar2(20) NOT NULL

nterface Design

I/O Design……….

These are in the form of JSP’s and HTML with in struts standard

pg. 93
 Stock Management
System

Screen: logIn.jsp

pg. 94
 Stock Management
System

Screen: userIndex.jsp

pg. 95
 Stock Management
System

Screen: MANAGEMENTIndex.jsp

pg. 96
 Stock Management
System

Screen: search.jsp

pg. 97
 Stock Management
System

Screen: searchResult.jsp

pg. 98
 Stock Management
System

Screen: shareDescription.jsp

pg. 99
 Stock Management
System

pg. 100
 Stock Management
System
Screen: buy.jsp

pg. 101
 Stock Management
System
Screen: buyConfirm.jsp

pg. 102
 Stock Management
System

Screen: MANAGEMENTIndex.jsp

pg. 103
 Stock Management
System

Screen: sell.jsp

pg. 104
 Stock Management
System

Screen: sellConfirm.jsp

pg. 105
 Stock Management
System

Screen: MANAGEMENTIndex.jsp

Client Side Validations

pg. 106
 Stock Management
System

pg. 107
 Stock Management
System

pg. 108
 Stock Management
System

Server Side validations

Buy Validation

pg. 109
 Stock Management
System

Share Quantity Validations

pg. 110
 Stock Management
System

User Exposure Validations

pg. 111
 Stock Management
System

Sell validation

pg. 112
 Stock Management
System

Trade Reports

pg. 113
 Stock Management
System

pg. 114
 Stock Management
System

System Development

PURPOSE

Software developers may install (or modify and then install) purchased software or they may
write new, custom-designed programs. The choice depends on the cost of each option, the time
available to write software, and the available to write software, and the availability of
programmers. Typically, in large organizations computer programmers (or combination of
system analyst’s programmers) are part of the permanent professional staff. In smaller firms,
without programmers, outside programming service may be retained on a contractual basis.
Programmers are also responsible for documenting the program, providing an explanation of
how and why certain procedures are coded in specific ways. Documentation is essential to test
the program and carry on maintenance once the application has been installed.

Before starting any coding of any subsystem we were required to carefully study the
information and requirements regarding that application. Once the problem was well though
off, and ideas were shared/ discussed among other team members about, how exactly the user
interface should be and what is the best way to deduce the logic of the application, we are
required to write down the flow of logic and other parameters being used or getting affected
on a document of Stock Management System called program specifications document (P S D).
This P S D has to get approved from, our manager and users to get further suggestions; also
this P S D’s are used to prepare the documentation of the final system at later stages and help
to keep trace of the changes subsequently made in logic.

The whole application is maintained in the menu from so that it remains user friendly and
easy to use and less complex. The system security is maintained by means of the starting form,
which takes the required user name and the password.

Developing law’s of software:

There are following point must be considering at the development phase:

Performance requirement

Exceptional handling

Acceptance criteria

pg. 115
 Stock Management
System
Design hints and guidelines

PERFORMANCE REQUIREMENTS

The following performance characteristics were taken care of in developing the systems:

User Friendliness:

The system is easy to learn and understand. A native user can also use the

System effectively, without any difficulty.

User satisfaction: The system is such that it stands unto the user’s expectation.

Response time:

The response time of all the operations is very low. This has been made possible by careful
programming.

Error handling:

Response to user errors and undesired situations has been taken care of to ensure that the
system operations without halting in case of such situation and proper are given to user.

Safety:

The program is able to avoid catastrophic behavior.

Robustness:

The system recovers from undesired events without human intervention.

Security:

This system provides protection of information through the mechanism of password

which is incorporated in it. Therefore only authorized people can access the Databases to
validations. This results in a thorough testing of the details, and the system is such that likely
to change and modifications can be easily incorporated in it.

pg. 116
 Stock Management
System
Portability:

The system can move to a new hardware/ operating system after making minor modifications
to it.T ensured that the system does not halt in case of undesired situation or events exception
conditions are taken care of providing the corresponding exception responses while
developing the system.

esting

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the
software engineering process that could be viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software. Testing is the set
of activities that can be planned in advance and conducted systematically. The underlying
motivation of program testing is to affirm software quality with methods that can
economically and effectively applied to both strategic to both large and small-scale systems

Objective of Testing

A good testing case is one that has high probability of finding as yet undiscovered errors.
Testing is a process of executing a program with the intent of finding errors in it .A successful
test is one that uncovers an as yet undiscovered error .The aim of testing is to determine that a
program works by showing that it has no errors .

Levels of Testing:-

Testing is usually relying on to detect the faults on each phase, in addition to the faults
introduced during the coding phase itself. Due to this, different levels of testing are used in the
testing process, each level of testing aims to test different aspect of a system.

client Acceptance

pg. 117
 Stock Management
System

Requirements
System Testing

Design
Integration Testing

Code Unit Testing

STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially, system engineering
defines the role of software and leads to software requirement analysis where the information
domain, functions, behavior, performance, constraints and validation criteria for software
are established. Moving inward along the spiral, we come to design and finally to coding. To
develop computer software we spiral in along streamlines that decrease the level of
abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vertex of the spiral and concentrates on each unit of the software as implemented
in source code. Testing progresses by moving outward along the spiral to integration testing,
where the focus is on the design and the construction of the software architecture. Taking
another turn on outward on the spiral we encounter validation testing where requirements
established as part of software requirements analysis are validated against the software that
has been constructed. Finally we arrive at system testing, where the software and other
system elements are tested as a whole.

Table Given below outlines the tests that were performed on the system to ensure correctness
and unearth errors, which were subsequently debugged.

pg. 118
 Stock Management
System

Table shows the Tests Conducted on the System

Testing
Objectives
Phase

Unit The various functions within each program and the program
blocks are tested for proper working.
Testing

Module A module is composed of various programs related to that

module. Module testing is done to check the module
Testing functionality and interaction between units within a module

Integration Integration testing is done to test the functionality and

Testing interfacing between the modules.

Acceptance Acceptance testing is done after implementation to check if the

Testing system runs successfully in the customer environment/site.

.
pg. 119
 Stock Management
System

UNIT TESTING

Unit Testing will be done to test field validations, navigation, functionality of the programs
and its blocks. These tests are applied on various functions within each program and other
critical program blocks. Table given below gives the outline of three-sample test cases for
Unit Testing performed on the system

Table Unit Testing – Test Case 1

Test Case Description

This test case deals with the entering of basic details related with the registered and
logged in user in the MANAGEMENT Module. This process takes many inputs. The
test case should check for proper inputs and verify whether the function for
validating the inputs is called properly or not.

Expected Inputs

• Details Related With The logged in user in a Standard Format.

Expected Outputs

• Alert window for erroneous inputs.

• Confirmation of Successful Completion of Basic Details Entry Process.

pg. 120
 Stock Management
System
Actual Test Results

• An alert window was shown whenever the user gave some erroneous data.
• Confirmation of Completion of Basic Details Entry was displayed on submission,
implying that the functions were called properly.

Table Unit Testing – Test Case 2

Test Case Description

This test case deals with the updating of Basic Details related with the users trade by
the java function. The test will check if the java function receives the updating details
properly and checks if the updating is performed correctly or not.

Expected Inputs

• Updated Basic Details from the web server.

Expected Outputs

• The java function should return the correct row count. Row count denotes the
number of rows being updated.
Actual Test Results

• The java function received the details to be updated properly.

• On updating the correct row count was returned by the function.

pg. 121
 Stock Management
System

Table Unit Testing – Test Case 3

Test Case Description

This test case deals with the real time share Management and fluctuation in the
market. The test is done by java function and an oracle trigger and will check if there
are some percent increase in the demand of the shares then a trigger will fire and
and price of the current share increases regarding some mathematical and real-time
calculations. And vice – versa for price decrement. Hence share fluctuation occurs.

Expected Inputs

• Share code and details regarding share.

Expected Outputs

• The java function should increase or decrease price of shares corresponding to per
transaction detail.
Actual Test Results

• The java function returns the new share prices of the shares
• On the page it will display as fluctuation.

MODULE TESTING

Module testing will be done to test the interaction between the various programs within one
module. It checks the functionality of each program with relation to other programs within

pg. 122
 Stock Management
System
the same module. It then tests the overall functionality of each module. Tables given below
outline two sample test cases for Module Testing performed on the system.

INTEGRATION TESTING

Integration testing is done to test the functionality and interfacing between the modules.
The system is built up of various modules, which work together to automate the activities of
the HR department. These modules should work together in a seamless way to achieve the
desired results. Integration testing will test for this property of the modules. The modules
display a cause and effect relationship, if data in one module is changed, then it affects the
data to change in some other module also. Integration testing needs to check if the
modifications do not adversely affect some other modules.

ACCEPTANCE TESTING

Acceptance testing was done after the implementation of the system. The acceptance
testing will check if the system works correctly in the user environment and if the entire
user specified functionalities are present. It also tests if the system adheres to the company
policies and quality standard. The HR Database system was tested and accepted by Sierra
Atlantic after the acceptance testing.

pg. 123
 Stock Management
System

VALIDATION CHECKS

I have use following type of checks/ data validations:

Data type

Length

Constraints

Blank field

Format

Data type:

I have use String type for character, int for numeric, and Date for date type. No numeric field
insert in date. Character never inputted in numeric field as phone no never accept character if
any person input wrongly give message. When this problem is removed then user performs
further operation.

Length:

When we define a max length. Then it never accepts more data .for example if I define numeric
length is 5 then it store either equal to length or less than length. If user gives more character
than required then display message and stop processing.

Constraints:

In this I am defining range of data if data is less than then display error with message. For
example code of password is four characters. The field of date must be 8 characters.

Blank field:

When users add data and some field is blank then it display message with out halt, But stop
processing.

Format:

pg. 124
 Stock Management
System
The pre define format is used not change daily to daily for example format of date
DDMMYYYY: 01012002 is used in all date type field. If user inserts an other format then
display message.

Web Design Constraints

The following design constraints were kept in mind while designing the pages for
the

Whole application.

The pages should be consistent and easy to operate. It should be designed in such a way that
an average user who does not have much idea about JSP and related technology can still be
able to access the information needed. The navigation should be easy and stepwise .A
customer may have multiple accounts and should be able to access all the accounts with a
single password .a request number should be generated so that it is easy to refer to it at a later
date. The entire official should work as administrators and should have access to all the
service areas / pages of the application by the transaction areas / pages are accessible to only
customers whose accounts are not frozen.

DESIGN

With the above constraints in mind, we have designed an interface for the pages that is
consisting of three different components namely:

Header

Header contains information about the company and the logo and like.

Navigation Panel

Navigation panel has all the options available to the user. At any point of time, any of these
options can be selected and used. All these are hyperlink and connect to different JSP files
used.

Main working panel

Main working panel is the area on the screen that is used by the application to allow user to
interact with it. There are some pages where some relative actions must be taken. These
actions are denoted as buttons so that it stands – out from the hyperlink and are easy to use.

To accomplish the state structure two framed pages are used – one for the customers and
another one for the administrator. As the two types of users have different set of operations to
pg. 125
 Stock Management
System
perform in the system. it demanded two separate pages for the purpose . These frames are
called depending on the login process.

mplementation

A crucial phase in system development is the successful implementation of the new system
design. Implementation includes all those activities that take place to convert from the old
system to the new system to the new system. The new system may be completely new
replacing an existing manual or automated system or it may be major modification to an
existing system.

In either case proper implementation becomes necessary so that a reliable system based on
the requirement of the organization can be provided. Successful implementation may not
guarantee improvement in the organization using the new system, but improper installation
will prevent this improvement.

It has been observed that even the best system cannot show good results if the analysts
managing the implementation do not attend every important detail. This is the area where the
system analysts need to work with utmost care.

There are three main aspects of implementation:-

User training

User Manual

Conversion

User Training

Even well designed system can succeed or fail because of the way these are operated and used.
Therefore the quality of training received by the personal involved with the system in various
capacities helps or hinders and may even prevent the with the system development must know
in detail what their roles will he , how they can make efficient use of the system and what the
will not do for them.

An analysis of user training focuses on two factors:-

pg. 126
 Stock Management
System
User capabilities

Nature of the proposed system

When a system is developed then only the developer of it knows its operation. But as the
project is being made for a client (organization) and it is to be used by the employees of that
firm, so there is need of user training. As the system is new for the employees and staff of the

cooperation so there is a necessity to train them because they have to operate the system. For
the live demonstration with personal contact are very effective. No training is complete
without familiarizing users with simple system

User Manual:-

When a system is developed then only the developer of it knows its operation. But as the
project is being made for a client and it is to be used by the employees of that firm, so there is a
need of user manual. It is documentation of the project that describes how to operate the
system? What are the various modules for efficient use of the system? How to start the
system?

The user manual helps to find out the answers of the queries like:-

How to start the system?

How to make entry?

How to generate reports?

The System being developed is web designing application and can be run simply in the Web
browser…

Conversion

Conversion is the process of from the old system to the new one. It should be accomplished in
shortest possible time. Four methods are commonly used –

Parallel system

Direct conversion

Pilot system

Phase – in mind

Phase – in mind

pg. 127
 Stock Management
System
The Stock Management System is being developed with different phases being taken into
mind…the project is developed in different phases starting with the analysis phase and ends
with implementation phase. After implementation phase the maintenance phase will begin
which keeps on going….

ystem Security

CHECKS AND CONSTRAINTS

System security refers to various validations on data in form of checks and controls to avoid
the system from failing. It is always important to ensure that only valid data is entered and
only valid operations are performed on the system. The system employs two types of checks
and controls:

Client Side Security

Various client side validations are used to ensure on the client side that only valid data is
entered. Client side validation saves server time and load to handle invalid data. Some checks
imposed are:
 A JavaScript program is used to fill up date in the date fields only.
 JavaScript is used to ensure that numeric field is filled with numeric data only.
 Maximum lengths of the fields of the forms are appropriately defined.
 Forms can not be submitted without filling up the mandatory data so that manual
mistakes of submitting empty fields that are mandatory can be sorted out at the client side
to save the server time and load.
 Tab-Indexes are set according to the need and taking into account the ease of user while
working with the system.

pg. 128
 Stock Management
System
Server Side Security
Some checks can’t be applied at client side. Server side checks are necessary to save the system
from failing and intimating the user that some invalid operation has been performed or the
performed operation is restricted. Some of the server side checks imposed are:
 Server side constraint has been imposed to check for the validity of Primary key and
foreign key. A primary key value cannot be duplicated. Any attempt to duplicate the
primary key value results into a message intimating the user about that. Values through
the forms using foreign key can be updated only for the existing foreign key values.
 Exceptions are caught in the programs and are used constructively to avoid system
failure. User is intimated through appropriate messages about the successful operations or
exceptions occurring at server side.
 Access permissions to various types of users are controlled according to the organizational
structure. Only permitted users can log on to the system and can have access according to
their category. User-name, passwords and permissions are controlled on the server side.
 Using Oracle as back-end provides best security features of database.

pg. 129
 Stock Management
System

D iscussion

CONCLUSIONS:

This was the first considerably large and important project undertaken by me during my
MCA course. It was an experience that changed the way I perceived project development. The
coding could not be started before the whole system was completely finalized. Even then there
were so many changes required and the coding needed to be changed. I attribute this to
inadequate information gathering from the user. Though there were many meetings with the
user and most of the requirements were gathered, a few misinterpretations of the
requirements still crept in. It made me realize how important the systems analysis phase is.
The project is a classic example for the adage that learning of concepts needs to be
supplemented with application of that knowledge.

On the whole it was a wonderful experience developing this project and I would have
considered my education incomplete without undertaking such a project which allowed me to
apply all that I have learnt.

pg. 130
 Stock Management
System

MERITS OF THE PROJECT

The project is identified by the merits of the system offered to the user. The merits of this
project are as follows -
 This project offers user to enter the data through simple & interactive forms. This is very
helpful for the client to enter the desired information through so much simplicity.
 The user is mainly more concerned about the validity of the data, whatever he is entering.
There are checks in every stage of any new creation, data entry or updating so that the
user cannot enter the invalid data, which can cause problems at a later date.
 Sometimes the user finds in the later stages of using the project that he needs to update
some of the information that he entered earlier. There are options for him by which he can
update the records. Moreover there is restriction for him that he cannot change the
primary data field. This keeps the validity of the data to longer extent.
 From every part of the project the user is provided with the links through framing so that
he can go from one option of the project to other as per the requirement. This is bound to
be simple and very friendly as per the user is concerned. That is, we can say that the
project is user friendly which is one of the primary concerns of any good project.
 Data storage and Retrieval will become faster and easier to maintain because data is
stored in a systematic manner and in a single database.
 Decision making process would be greatly enhanced because of faster processing of
information since data collection from information available on computer takes much less
time then manual system.

pg. 131
 Stock Management
System
 Allocation of Sample Results becomes much faster because at a time the user can see the
records of last years.
 Generation of Acknowledgement, Dispatches and Sample Reports and any type of report
will be much quicker now than done manually and with out much paper handling.
 Through these features it will increase the efficiency, accuracy and transparency.
 Since the Computers would be networked together, information can travel from one
department to other Department and back very quickly. Thus communication will be
rapid.

DEMERITS OF THE PROJECT

The project is tried up to best to provide the simplicity, capability and reliability to the user
but then also there are fields, which cannot be tackled up to best of the results. This project
also has some of the demerits in it. As nothing is perfect in this world, we also not claim that
our software is perfect. As all other, our project also has some demerits.

Those demerits are as follows –

 The user has not provided any option to delete any record, which he has entered once.
 Due to the maintenance of data related with the employee who had either resigned or
retired or currently not working in company, the size of the database becomes too
bulky which leads the processing speed of any request from the client to become a bit
slow.

FUTURE SCOPE OF THE PROJECT

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

pg. 132
 Stock Management
System
experience is gained with it. As users work with the system, they develop ideas for change and
enhancements.

ibliography

Core Java Complete Reference - Herbert Schildt

J2EE The Java EE tutorial – Jennifer ball, Eric Jendrok

Struts The Complete Reference- James Holmes

Servlets and JSP Head first servlets and JSP – Kathy Siera, Core Servlets and JSP –
Marty Hall.

Oracle 9i The Complete reference

JDBC Expert Oracle JDBC- R. M. Menon

Java Script Ivan Bayross

SQL Practical guide for developers – Gregory D. Speegle

E-study

pg. 133
 Stock Management
System
www.sun.com

www.wikipedia.com

www.javaworld.com

A ppendices

Programming

Programming is not only a creative activity but also an intellectually rigorous discipline .It
is the part where the design is actually translated into the machine readable form which is
called program .

Programming Principles

The main activity of coding phase is to translate design into code. If we translate the structure
of the design properly, we will have structured programs. A structured Program doesn’t just
“happen”. It is the end product of series of efforts that try to understand the problem and
develop a structured , understandable solution plan . It is all impossible to write a good
structured program based on unstructured poor design .The coding phase affects both testing
and maintenance , profoundly the time spent in coding is small percentage of the total
software cost , while testing and maintenance consume the major percentage . The goal of
coding phase is not to simplify the job of the tester and maintainer.

pg. 134
 Stock Management
System

Programming style

A well written program is more easily read and understood both by the author and by others
who work that program.

A good Programming style is characterized by the following:-

Simplicity

Readability

Good documentation

Changeability

Predictability

Good Structure

Selection of Coding Language

All the programs coded should be based on a standard which can tend to the needs of all
readers, i.e. it should provide degree of predictability in programs of a common type. There
are many aspects to what the programs must do so to enable the different users to
comfortably work on it.

For example the program should:-

Be corrective of the solution

Have maximum speed of execution

Be comprehensive and east to maintain

Programming language choice affects the productivity and code quality in several ways.
Programmers working with high level language achieve better productivity and quality than
those working with low level language , because former is more expensive in nature .We have
used HTML , JSP , Java script scripting languages for the coding as we have to make the
software and these languages provide great compatibility and flexibility with browser .

pg. 135
 Stock Management
System

A bout me

I am Rahul Samaddar .I belongs to Kanpur. I am pursuing my masters in computer

application from Dr. VSICS Kanpur.

MY ROLE in this Project

I worked on the fourth module that was MANAGEMENT module where I handled both
type of transactions that was Intraday and Interday. The Account opening process took
place through Demat Account. Selling and buying of shares, Amount restrictions, timed
schedules and many more real time transaction handling was done in this project. On this
module all the minor to major functionalities was structured and formulated by me.

CONTACT DETAILS

Rahul Samaddar

pg. 136
 Stock Management
System
Email. samaddar27@gmail.com

Mob. 09891701239

pg. 137