INDEX

Introduction
System requirement analysis
Preliminary Design
Detailed Design
Module Description
Preliminary Testing
Detailed Testing
Concluding Remarks
References

INTRODUCTION
In the present scenario every one uses computer.
Todays busy life, people have no time waiting response. This project
investment.com is very customized and user-friendly project customer. It
has been designed to easily manage, and look after the over all processing of
even very large market. In this project capable of managing enquiry such as
company name, company share It also provide help for managing the record
a of sell and buy share . Shares are the best investment available over a long
period of time. The growth of share prices comfortably out-paces inflation
most years because the best share prices represent the growth in earnings of
the best companies. Although the stock market is seen as "high risk" this
depends very much on timing and the sort of shares you invest in. It is very
useful for the customer.

SYSTEM REQIREMENT ANALYSIS

In system analysis phase we are doing the job of identifying the need
of the system enhancement. And various types of investigation are made
according to the need of the candidate system.
For analyzing the system there are two basic steps have to followed
Identification of need
Preliminary investigation

IDENTIFICATION OF FICATION:
Identification of need for this step of SDLC for software development needs
are generally generated from the customer , managerial staff , competition
employees and agent. in our case and user are person , who are requesting
for a change , honors need is to make various types of reports about
student and other transaction ,which are required for taking any action ,if
report are present then it provides the supporting information to make any
rigid action based on quantitative details.

PRELIMINARY INVESTIGATION:
Preliminary investigation for the candidate is the second step of SDLC for
software development. Here needs are evaluate at are at this step our
intention is to find out what is actual problem. In this phase we are not
dealing with the solution domain. For evaluate of needs we are not first
collecting the details about the system, working process of the system is
studied and information gathered according to the problem. For

information we are using the four basic tools given by the

software engineering methodology they are given below.
Record Review
Onsite observation
Interview
Questionnaire

SYSTEM REQUIREMENT

SOFTWARE REQUIREMENT:

Operating system-window XP
Front-end Netbean editor
Back end as MY SQL server
Querying language SQL query

HARDWARE REQUIREMENT:
Ram :512 MB Ram for memory access
Hard Disk 2GB Hard Disk
Processor Intel dual or Higher processor

FRONT END

Java is a programming language developed by Sun

Microsystems. It implements a strong security model, which prevents
compiled Java programs from illicitly accessing resources on the system
where they execute or on the network. Popular World-Wide Web browsers,
as

well

as

some World-Wide

Web servers

and

other

systems

implement Java interpreters. These are used to display interactive user

interfaces, and to script behaviour on these systems.
While implementation problems have opened security
vulnerabilities in some Java interpreters (Java Virtual Machines or JVM's),
the design of this language makes it at least theoretically possible to execute
program with reasonable assurances about its Security, and in particular its
ability to cause harm.

WHAT IS JSP
Java Server Pages (JSP) is a server-side programming
technology that enables the creation of dynamic web pages and applications.
This is accomplished by embedding Java code into HTML, XML, DHTML,
or other document types. When a client such as a web browser makes a
request to the Java application container, which is typically a web server, the
static page is converted behind the scenes, and displayed as dynamic content
to the viewer. It has been speculated that JSP was released to compete with
PHP, a commonly used open-source programming language. While JSP is
sometimes associated with Active Server Pages (ASP), these are actually
two different technologies. The biggest difference is that ASP is developed
by Microsoft, and largely considered as a framework. This is due to its

ability to support a wide variety of programming languages enabled by

Microsoft's Component Object Model (COM). Created by Sun
Microsystems, JSP is considered an object-orientated programming
language. Stands for "Java Server Page." This standard was developed by
Sun Microsystems as an alternative to Microsoft's active server page (ASP)
technology. JSP pages are similar to ASP pages in that they are compiled on
the server, rather than in a user's Web browser. After all, they don't call them
"server pages" for nothing. However, JSP is Java-based, whereas ASP is
Visual Basic-based. JSP pages are useful for building dynamic Web sites and
accessing database information on a Web server. Though JSP pages may
have Java interspersed with HTML, all the Java code is parsed on the server.
Therefore, once the page gets to the browser, it is only HTML. JavaScript,
on the other hand, is usually parsed by the Web browser, not the Web server.

INTRODUCTION OF NEATBEAN EDITOR

NetBeans is a great little tool for those who build web applications and for
software developers. It is an IDE ( Integrated Development Environment )
which is available as open source software. Best of all, you can run this
program on most operating systems including Windows, Linux, Mac OS X
and Solaris.

What Can It Do?

With NetBeans you can develop applications for use via the desktop or on
the web. You can also develop software for use with mobile devices. The
applications can be developed with NetBeans using a variety of coding
languages including Java, Ruby (with support for Rails), and C/C++. The
feature rich software gives you great options and visual abilities that allow
you to not only create the applications that you want but to view them and
perform testing to work out all of the kinks and bugs in your software.

What is glassfish server

GlassFish is an open source application server project started by Sun
Microsystems for theJava EE platform and now sponsored by Oracle
Corporation. The supported version is calledOracle GlassFish Server.
GlassFish is free software, dual-licensed under two free software licences:
the Common Development and Distribution License (CDDL) and the GNU
General Public License (GPL) with the classpath exception.
GlassFish supports all Java EE API specifications (by definition since it is
the Java EEReference implementation), such as JDBC, RMI, e-mail, JMS,
web services, XML, etc., and defines how to coordinate them. Java EE also
features some specifications unique to Java EE for components. These
include Enterprise JavaBeans, Connectors, servlets, portlets (following the
Java Portlet specification), JavaServer Pages and several web service
technologies. This allows developers to create enterprise applications that
are portable and scalable, and that integrate with legacy technologies.

BACK END
My SQL SERVER:
Modern day web sites seem to be relying more and more
on complex database systems. These systems store all of their critical data,
and allow for easy maintenance in some cases. The Structured Query
Language (SQL) is a very popular database language, and its standardization
makes it quite easy to store, update and access data. One of the most
powerful SQL servers out there is called MySQL and surprisingly enough,

its free. Some of the features of MySQL Include: Handles large databases, in
the area of 50,000,000+ records. No memory leaks. Tested with a
commercial memory leakage detector (purify). A privilege and password
system which is very flexible and secure, and which allows host-based
verification. Passwords are secure since all password traffic when
connecting to a server is encrypted.
The aim of backend software is to maintain the data base
used to store the records for customer so the SQL server has distinguished
and select for this job. If lets us to group multiple list together and related
to each other creating a type of data base called relational data base each
list is stored in a different table every data base begins with a problem or
need that can be solved by creating a systematic data tracking system.
My SQL is a powerful relational data base management system
(RDMS) which are will used to learn principals of data base and data
manipulation using structured query language statements. SQL is a data base
language this is used to access, insert, deleted and update stored data

10

PRELIMINARY DESIGN
Software actually starts from the requirement analysis. The requirement gathering
process is intensified & focused specially on software. To understand the actual
nature of the program to be built the software engineer must understand the
information domain for the software. As well as the required function behavior
performance & interface. Requirement for both software & system are
documented & reviewed with customer. Software Requirement analysis is
software engineering task that bridges the gap between system level requirement
engineering & software design. In problem recognition we have some regular
meeting with the customer & classified the customer requirements into three
categories.

11

- Normal Requirements: These include the objectives & the goals that are started
for a product. If these requirements are there the customer is satisfied.
- Expected Requirements: These requirements are implicit to the product or the
system & are so fundamental that customer does not explicitly state them but their
absence may cause considerable dissatisfaction to the customer.
- Exciting Requirements: These features go beyond the customers expectation &
prove to be very satisfying when present.

1.Database Tables
Database tables which have been created in the project
Investment.com are as follow:1. customer_master
2. Feed back
3. buyller
4. Seller
5. CB_balance

12

Column Name

Data Type

Allow null

Cid

Integer

Unchecked

Name

Nvarchar(50)

Unchecked

1 Database

Address

Nvarchar(50)

checked

Design:-

Phone_R

Nvarchar(50)

Unchecked

Phone_M

Nvarchar(50)

Unchecked

Phone_O

Nvarchar(50)

Unchecked

Fax

Nvarchar(50)

Unchecked

City

Nvarchar(50)

Unchecked

State

Nvarchar(50)

Unchecked

DOB

Date

Unchecked

Pincode

Integer

Unchecked

Email Id

Nvarchar(30)

Unchecked

Occupation

Nvarchar(30)

Unchecked

Income

Nvarchar(20)

Unchecked

Loginname

Nvarchar2(20)

Password

Nvarchar2(20)

Longname

Nvarchar2(30)

13

Unchecked
Unchecked
Unchecked

Customer_master
Table primary key:
Cid

CB_balance table

primary key & unique key : Cid

Column Name

Data Type

Allow null

Cid

Integer

Unchecked

Balance

Integer

Unchecked

Mode_of_pay

Varchar210)

Unchecked

Card_type

Varchar2(10)

Unchecked

Card_no

Integer

Unchecked

Card_holdername Varchar2(20)

unchecked

Expiry_date

Date

Unchecked

Cheque_no

Integer

Unchecked

Cheque_date

Date

Unchecked

Bank_drawn

Varchar2(20)

Unchecked

Location

Varchar2(20)

Unchecked

14

Buyller tabley: primary key : Cid

Column Name

Data Type

Allow null

Cid
Company name
No_of_shares
Rate_per_share
Type_share

Integer
Varchar2(10)
Integer
Integer
Varchar2(20)

Unchecked
Unchecked
Unchecked
Unchecked
Unchecked

Date

Date

Unchecked

Flg_B

Varchar2(10) unchecked

Seller table primary key:Cid

Column Name

Data Type

Allow null

Cid
Company name
No_of_shares
Rate_per_share
Type_share

Integer
Varchar2(10)
Integer
Integer
Varchar2(20)

Unchecked
Unchecked
Unchecked
Unchecked
Unchecked

Date

Date

Unchecked

Flg_S

Varchar2(10) unchecked

15

Feedback table primary key:Sno

Column Name

Data Type

Allow null

Sno
Name
Email
Comments

Integer
Varchar2(10)
Varchar2(10)
Varchar2(30)

Unchecked
Unchecked
Unchecked
Unchecked

DETAILED DESIGEN
1. E-R Diagram
The overall logical structure of database can be expressed graphically by an E-R
diagram. It consist a set of basic objects called entities and of relationships among
these objects.An entity is represented by a set of attributes. Attributes are
descriptive

properties possessed by each member of

an entity set.The ER diagram consist of the following major components.

The rectangle represents entity sets.

16

The ellipses represents attributes.

The diamond box represents relationship sets.

The line links attributes to entity sets ans entity sets to

relationship sets.

The double ellipses represents multivalued attributes.

2) Data Flow Diagram(DFD)

1. Data Flow Analysis:Documents are the finding in data flow diagrams, which data flow analysis studies
the use of data in each activity. It graphically shows the relation between process
and data. Data flow analysis examines the use of data to carry out specific business
processes within the scope of systems investigation. You might think of it as
viewing the activities of system from the viewpoint of the data originate, how they
are used or changed, and where they go including the steps along the way their
origin to their destination.
Data flow analysis means use of the following tools:

17

2.Data flow diagram:A data flow diagram (DFD) is a graphical technique that depicts information flow
and transforms that are applied as data moves from input to output.The DFD is
also known as data flow graph or bubble chart.
Named circles show the processes in DFD or named arrows entering or
leaving the bubble represent bubbles and data flow. A rectangle represents a source
or sinks and is a net originator or consumer of data .

3.Data Dictionary:The data dictionary is a repository that contains description of the entire data
object consumed or produced by the software . The associated data dictionary
states precisely the structure of each data flow in the DFD.Components in the
structure of a data flow may also be specified in the data dictionary, as well as the
structure of file shown in the DFD. In other words, it shows:

What goes in

How it is changed

What comes out

The following symbols are generally used:

Data flow is represented by a labeled arrow

Processes are represented by labeled circles (bubbles)

Information sources and sinks are represented by boxes

Files are represented by a double line

2.DATA FLOW DIAGRAM:

18

1. DFD showing the flow of Data at the Top Abstract Level

User

Registration
&
searching

Server

Database

2.CONTEXT LEVEL DFD(DFD Level 0)

Sign up :Create, View
Website on
Book Gallery

User

Requirements are fulfilled

Registration

19

2) Data Flow Diagram (DFD Level 1)

1.Login
Registration

LOGIN
PAGE

USER
AUTHENTCATIO
N

LOGIN
ERROR

Search

AUTHENTICATION

View all
applicant

Select
applicant
profile

2.Appllic

ant Login:-

Login
Page

Applicant Registration

admin information

Admin

Sign Up
error

Admin DB

confirmation

ROLES

Admin Login

3.Registration:-

20

Applicant Registration

Login
Page

User information

User registration

Registration
DB

Db

confirmation

ROLES

Return msg
page

Registration
error page

4.Result:Login
Page

Request result

Book DB

Fetching
Result

Result information

Display

Result
information

3)UML DIAGRAM:
USE CASE DIAGRAM
A Use Case is a named capability of a structural entity in a model. Use Case define
a System-Level capability without revealing or implying any particular
implementation of that capability. Use Cases are implemented by collaboration of
classes.

User

Admin

Registration

21

Login

Sell

buy

Update

Logout

22

Passwor
d
User
Email id

UserI
d

Login

23

MODULE DESCRIPTION
Project Will contain following modules:We separate modules into two categories:

Admin Part:In this site Admin is person which is responsible for maintaining a website(s). The
duties of the webmaster may include generating and revising web pages, replying
to user comment, and examination traffic through the site.
1. Registration
2. Home
3. Login
4. Add new company name
5. check the user information
.

24

USER PART:1.Registration page

2.Login page
3.Home page
4.Get current business news
5.terms and condition
6.logout

25

PRELIMINARY TESTING
When we have completed the coding part then the important work is to test them.
Before that we should know what is Testing and what are its types, which are
described as under:

1. SOFTWARE TESTING FUNDAMENTALS

The development of software system involves a series of production activities,
where there are very natural that there will be some human faults.Software testing
in critical element of software quality assurance and represents the ultimate review
of specification, design and coding.
Testing presents an interesting errors or inconsistencies for the software
engineers. The engineer attempts to build software from system. Now comes
testing. The engineer creates a series of test cases that are intended to destroy
errors in the software that has been build. In fact, testing is the one step in software
engineering process.

1.TESTING OBJECTIVES:There are number of rules that can serve well as testing objectives.
1.) Testing is a process of executing a program with the intent of finding an
error.
2.) A good test case is one that has a high probability of finding an as yet
Undiscovered error.
3.) A successful test is one that uncovers an as yet undiscovered error.

26

These objectives implies that a successful test is one in which no errors are found.
Our objective is to design tests that systematically uncover different classes of
errors and do so with minimum amount of time and effort.
If testing is conducted successfully it will uncover errors in software.
The secondary benefit, testing demonstrates that software functions are working
according to specification and requirement appears to have been met.

2. TESTING PRINCIPLES:Before applying methods to design effective test cases a software engineer must
understand the basic principles that guide, software testing.
* All tests should be traceable to customer requirements.
* Test should be planned long before testing begins.
* There is one principle that implies, that 80% of all errors uncovered during
testing, will likely be traceable to 20% of all program modules.
* The testing should focus on individual program modules. Then testing
should progress towards "in the large" that is progresses should go
towards the final errors in entire system.
* Exhaustive testing is not possible.
* To be most effective, testing should be conducted by an independent third
party.

3. TYPES OF TESTING
WHITE BOX TESTING
White Box Testing, sometimes called Glass Box Testing or Structured Testing is a
test case design method that uses the control structure of the procedural design to
derive test cases. The tester can analyze the code and use knowledge about the
structure of a component to derive test data. "Knowing the internal working of a

27

product, test can be conducted to ensure that internal operation performs according
to specification and all internal components have been adequately exercised", is
called White Box Testing.
White Box Testing of software is predicted on close
examination of procedure detail. Logical paths of the white software are tested by
providing test cases that exercise specific sets of condition or loops.
Using White Box Testing methods, the software engineer can derive test cases
that:1.) All independent paths within a module have been exercised at least once.
2.) Exercise all logical decisions and their true and false sides.
3.) Execute all loops at their boundaries and within their operational bounds.
4.) Exercise internal data structure to ensure their validity.
The advantage of White Box Testing is that an analysis of the code can be used to
find how many test cases are needed to guarantee a given level of test coverage.

BLACK BOX TESTING

Sometimes called Behavioral Testing or Particular Testing. Black Box Testing
focuses on the functional requirements of the software. That is, Black Box Testing
enables the software engineer to derive sets of input condition that will fully
exercise all functional requirements for a program. Black Box Testing is not an
alternative to White Box techniques. Rather, it is a complementary approach that is
likely to uncover a different class of errors than White Box methods.
Black Box Testing attempts to find errors in the following categories:1.) Incorrect or missing function.
2.) Interface errors.
3.) Errors in data structures or external data base access.

28

4.) Performance errors.

5.) Initialization and termination errors.
Unlike White Box Testing which is performed easily in the testing process Black
Box Testing tends to be applied during data stages of testing. Because Black Box
Testing purposely disregards control structure, attention is focused on the
information domain. Tests are designed to answer the following question:* How is functional validity tested?
* What classes of input will make good test cases?
* Is the system particularly sensitive to certain input values?
* How are the boundaries of data class isolated?
* What data rates and data volume can the system tolerate?
* What effect will specific combinations of data have on system operations?

By applying Black Box techniques we derive a set of test cases that satisfy the
following criteria:
1.) Test cases that reduce, by a count that is greater than one, the number of
additional test cases that must be designed to achieve reasonable testing.
2.) Test cases that tell us something about the presence or absence of classes
of errors, rather than errors associated only with the specific test at hand.

29

ALPHA AND BETA TESTING

It is virtually impossible for a software developer to foresee how the customer will
really use a program. When custom software is built for one customer, a series of
acceptance tests are conducted to enable the customer to validate all requirements.
Conducted by the end user rather than the system developer, an acceptance test can
range from an informal test drive to a planned and systematically executed
series of tests. If software is developed as a product to be used by many customers,
it is impractical to perform formal acceptance tests with each one.
Most software product builders use a process called alpha and beta testing
to uncover errors that only the end user seems able to find.

ALPHA TESTING
The alpha test is conducted at the developers site by a customer. The software is
used in a natural setting with the developer looking over the shoulder of the user
and recording errors and usage problems. Alpha tests are conducted in a controlled
environment.

BETA TESTING
The beta test is conducted at one or more customer sites by the end user(s) of the
software. Unlike alpha testing, the developer is generally not present. Therefore,
the beta test is a live application of the software in an environment that cannot
be controlled by the developer. The customer records all problems that are
encountered during beta testing and reports these to the developer at regular
intervals. As a result of problems reported during beta test, the software developer

30

makes modifications and then prepares for release of the software product to the
entire customer base.
While performing testing following errors were encountered which
are handled properly and prompts where required

31

DETAILED TESTING
TESTING
INTRODUCTION TO SOFTWARE TESTING:Testing is a process used to help identify the correctness, completeness and quality
of developed computer software. With that in mind, testing can never completely
establish the correctness of computer software.
There are many approaches to software testing, but effective testing of complex
products is essentially a process of investigation, not merely a matter of creating
and following rote procedure. One definition of testing is "the process of
questioning a product in order to evaluate it", where the "questions" are things the
tester tries to do with the product, and the product answers with its behavior in
reaction to the probing of the tester. Although most of the intellectual processes of
testing are nearly identical to that of review or inspection, the word testing is
connoted to mean the dynamic analysis of the productputting the product
through its paces.
The quality of the application can and normally does vary widely from system to
system but some of the common quality attributes include reliability, stability,
portability, maintainability and usability. Refer to the ISO standard ISO 9126 for a
more complete list of attributes and criteria.
Testing helps is verifying and Validating if the Software is working as it is
intended to be working. Thins involves using Static and Dynamic methodologies
to Test the application.

32

Because of the fallibility of its human designers and its own abstract, complex
nature, software development must be accompanied by quality assurance
activities. It is not unusual for developers to spend 40% of the total project time on
testing. For life-critical software (e.g. flight control, reactor monitoring), testing
can cost 3 to 5 times as much as all other activities combined. The destructive
nature of testing requires that the developer discard preconceived notions of the
correctness of his/her developed software.

SOFTWARE TESTING FUNDAMENTALS:1. Testing is a process of executing a program with the intent of finding an error.
2. A good test case is one that has a high probability of finding an as yet
undiscovered error.
3. A successful test is one that uncovers an as yet undiscovered error.
Testing should systematically uncover different classes of errors in a minimum
amount of time and with a minimum amount of effort. A secondary benefit of
testing is that it demonstrates that the software appears to be working as stated
in the specifications. The data collected through testing can also provide an
indication of the software's reliability and quality. But, testing cannot show the
absence of defect -- it can only show that software defects are present.

33

TEST PLAN:We want to product to be bug free. We want also want this document describes the
plan for testing for Hospital Management software and basic modules like check
in module, checkout module, main form module, and view module.
In this module we will perform two levels of testing Unit Testing and system
testing. Because the system is small, it is felt that there is no need for elaborate
integration testing. The basic unit to be tested given below:-Feature to be tested:
All the functional features specified in the requirement document are tested.

TESTING START PROCESS

Testing is sometimes incorrectly thought as an after-the-fact activity; performed
after programming is done for a product. Instead, testing should be performed at
every development stage of the product. Test data sets must be derived and their
correctness and consistency should be monitored throughout the development
process.
If we divide the lifecycle of software development into Requirements Analysis,
Design, Programming/Construction and Operation and Maintenance, then
testing should accompany each of the above phases. If testing is isolated as a
single phase late in the cycle, errors in the problem statement or design may incur
exorbitant costs. Not only must the original error be corrected, but the entire
structure built upon it must also be changed. Therefore, testing should not be
isolated as an inspection activity. Rather testing should be involved throughout the
SDLC in order to bring out a quality product.

34

TESTING STOP PROCESS:The Software Assurance Technology Center (SATC) in the Systems Reliability
and Safety Office at Goddard Space Flight Center (GSFC) is investigating the use
of software error data as an indicator of testing status. Items of interest for
determining the status of testing include projections of the number of errors
remaining in the software and the expected amount of time to find some
percentage of the remaining errors.
To project the number of errors remaining in software, one needs an estimate of
the total number of errors in the software at the start of testing and a count of the
errors found and corrected throughout testing. There are a number of models that
reasonably fit the rate at which errors are found in software, the most commonly
used is referred to in this paper as the Muse model. This model is not easily
applicable at GSFC, however, due to the availability and the quality of the error
data.
At GSFC, useful error data is not easy to obtain for projects not in the Software
Engineering Laboratory. Of the projects studied by the SATC, only a few had an
organized accounting scheme for tracking errors, but they often did not have a
consistent format for recording errors. Some projects record errors that were found
but did not record any information about resources applied to testing. The error
data frequently contained the date of entry of the error data rather than the actual
date of error discovery. In order to use traditional models such as the Musa model
for estimating the cumulative number of errors, one needs fairly precise data on
the Time of discovery of errors and the level of resources applied to testing. Real
world software projects are generally not very accommodating when it comes to

35

either accuracy or completeness of error data. The models developed by the SATC
to perform trending and prediction on error data attempt to compensate for these
shortcomings in the quantity and availability of project data.
In order to compensate for the quality of the error data, the SATC developed a
software error trending models using two techniques, each based on the basic
Musa model, but with the constant in the exponential term replaced by a function
of time that describes the 'intensity' of the testing effort. The shape and the
parameters for this function can be estimated using measures such as CPU time or
staff hours devoted to testing. The first technique involves fitting cumulative error
data to the modified Musa model using a least squares fit that is based on gradient
methods. This technique requires data on errors found and the number of staff
hours devoted to testing each week of the testing activity. The second technique
uses a Kalman filter to estimate both the total number of errors in the software and
the level of testing being performed. This technique requires error data and initial
estimates of the total number of errors and the initial amount of effort applied to
testing.

36

TESTING STRATEGY
Testing is a set of activities that can be planned in advance and conducted
systematically. For this reason a template for software testing a set of steps into
Which we can place specific test case design methods should be defined for the
software engineering process.
There are a number of software testing strategies, all of which have following
general characteristics:
1. Testing begins at the module level and works outwards the integration of
the entire computer based system.
2. Different testing techniques are appropriate at different points in time.
3. Testing and debugging are different activities, but debugging must be
accommodated in any testing strategy.

LEVEL OF TESTING
1.

UNIT TESTING: This is also called program testing. The unit in a

system is modules and routines that are assembled and integrated to perform
a specific function. In a large system, many modules independently of one
another to locate error.

2.

SYSTEM TESTING: When unit testing are satisfactorily concluded the

system, as a complete entity must be tested. System testing must verify that
file size is adequate and that indexes have been built properly.

37

ESTIMATING THE COST OF PROJECT

In developing cost estimates for a system, we need to consider several cost
elements. Among them is hardware, facility, operating and supply cost.
Hardware case relates to the actual purchase or lease of the computer and for
example printers disc, drive, and peripherals tape unit. Determining the actual
cost of hardware is generally more difficult.
when various users for a dedicated stand along system share the system. In
some cases the best way to control is to treat as an operating system.
Personal cost includes EDP staff salaries and benefit health insurance, vacation
time, sick pay, etc. As well as pay for those involved in developing the system.
Costs insured during the development of a system are one time cost and are the
labeled development cost. Once the system is installed, the cost operating and
maintaining the system.
Facility cost are expensive insured in the physical side where the application of
the computer will be in operation this include wiring, lighting and air one time
cost and is in corporate into overall estimate of the candidate system.
Operating cost include all cost associated with the day-to-day system. The
amount demands on the number o operating staff. There are various ways of
covering operating cost. One approach is to treat operating as overhead.
Another approach is to charge an unauthorized user for the amount of
processing the request from the system. The amount charged is based on
necessary to determine how operating costs should be handled. Supply costs
are variable costs that increased with use of paper, ribbon, and disks. A
systemis also expected to provide benefits. The first task is to identify each and
assign an analysis. Benefits may be tangible, direct or indirect.

38

Conclusion remark
In the world of Market and industry today ,in order to survive and business
Beat the completion business needs to manage the future. Managing the
future means managing the information .the real success of orgnization
depends upon resolving gaps in the communication of this information This
project is based on making web based system of Online share trading Any
user easily search the company name. This projectInvestment.com
customized and user-friendly project for college. It has been designed to
easily manage, and look after the over all processing of even very large. In
this project capable of managing enquiry such as customer name, company
name. It also provides help for managing the information about the share.
While working in the terms and by the friends help we also learnt many
technical and non technical thing thus ,improve our skills.

REFERENCES

39

References books
Herbert Schlitz The complete reference-Java
Software Engineering: Pressman
Operating System:-Gallvin , William stalling
Data Base:-Korth for (database design and ER-Diagram and DFD)
Bill Kennedy.HTML Guide

References Sites
http//www.GOOGLE.COM (search engine)
http//www.wikipedia.Org

40

41

42

43