PROJECT REPORT

ON

SHARE MANAGEMENT SYSTEM

Submitted in the partial fulfilment of the degree of

Bachelor of Business Management (CAM)

(2018-2019)

SUBMITTED BY:

SIDDHARTH SAXENA (02413401918)

Under the guidance of

DR. SEEMA GUPTA

(Associate Professor)

Ideal Institute of Management & Technology

(Affiliated to Guru Gobind Singh Indraprastha University, Delhi)

 Ideal Institute of Management & Technology

Approval Form
1. Name & Enrollment No.: SIDDHARTH SAXENA (02413401918)

2. Title of the Project: SHARE MANAGEMET SYSTEM

3. Software Used: MICROSOFT WORD

………………………
Dr. Seema Gupta
(Supervisor)

…………………………. ………………………………….…
Dr. Vineeta Sharma Prof. (Dr.) Anil Parkash Sharma
(Principal, BBA 1st Shift) (Director, IIMT)

II
 DECLARATION

I, SIDDHARTH SAXENA, hereby state that this report has been submitted to
Ideal Institute of Management & Technology in partial fulfillment of the
requirements for Bachelor of Business Administration Program on the topic
“SHARE MANAGEMENT SYSTEM”

The information of this report is based on my Project work. Any part of this
project has not been reported or copied from any report of the University and
others.

Date:17 April, 2019 SIDDHARTH SAXENA

02413401918

III
 ACKNOWLEDGEMENT

I am writing this final Project for the program of Bachelor of Business

Administration(CAM) on “SHARE MANAGEMENT SYSTEM” for Ideal
Institute of Management & Technology, Affiliated to Guru Gobind Singh
Indraprastha University.

It has been a great challenge but a plenty of learning and opportunities to gain a
huge amount of knowledge on the way of writing this Project report. I could not
have completed my Project without the constant guidance of Dr. SEEMA
GUPTA, my faculty guide, who helped me along the way and was always
prepared to give me feedback and guidelines whenever I needed it.

SIDDARTH SAXENA
0240131918

IV
 CERTIFICATE

This is to certify that Project Report entitled, “SHARE MANAGEMENT

SYSTEM” which is submitted by SIDDHARTH SAXENA in partial fulfilment
of the requirement for the award of degree of Bachelor of Business
Administration(CAM) to Ideal Institute of Management and Technology
(affiliated to GGSIP University, Delhi) is a record of the candidate’s own work
carried out by him/her under my supervision. The matter embodied in this report
is confide and has not been submitted for the award of any other degree.

(Dr. Seema Gupta)

(Supervisor)
(Associate Professor)

V
 Table of Content

Page
S. No. Content No.
1. Chapter -1 Introduction
1.1. Overview of proposed system
1.2. Scope of proposed system 7-8

Chapter -2 Objective of Proposed System

2. 9
Chapter -3 Tools & Environment of Project (Frontend
3. & Backend Tools)
10-
11
Chapter -4 Software Development Life Cycle
4. 4.1. Feasibility study
12-
4.2. System requirement and specification 15
4.3. Data flow diagram
5. Chapter- 5 Software Testing 16-
18
Chapter -6 Limitations & Future Perspective
6. 19-
20
7. Bibliography 21

VI
 CHAPTER 1
INTRODUCTION

1.1 OVERVIEW OF PROPOSED SYSTEM

SHARE MANAGEMENT SYSTEM is software that will provide the quick and
fast service to the customer. This system not only provides the quick and fast
facility but also error free and smooth facility. Share Management System is a
software, which is used for maintaining and analyzing the stock of the shares of
the customers and also help the customers to exchange their shares which means
customers can buy and sell their shares easily through this system. All the
communication is done through database. The main objective of the project is to
store the record of the customers including their personal details, quantity of
shares, banking transactions, etc. This system gives complete detail about the
customers, their transactions, profit & loss.

7
1.2 SCOPE OF PROPOSED SYSTEM
Here we specify the functions which are available in this software. In this project,
the process of record maintenance is done. In this project the user stores the data
of their customers, this is specially for the user belonging to any broking
company (who deals with purchases and sales of shares). The user thus can fetch
the data of the customers easily and whenever required. This project has a wide
scope. This runs on any machines. The scope of a Share Management System can
cover many needs, including customer details, buying and selling of shares, their
cost of share, etc.

8
 CHAPTER 2
OBJECTIVE OF PROPOSED SYSTEM

1) In this system a user can check the amount of share/shares that he wants to buy
or sell.
2) Users can check their previous meter readings.
3) Users can get all the information about the direct stock exchange market.
4) Users can also check their profit and loss which they earn by buying and
selling of their shares.
5) Users can also check their latest transactions details easily.
6) The main objective of this project is to provide quick and fast services to the
customer.

9
 CHAPTER 3
Tools & Environment of Project (Frontend & Backend
Tools)

HARDWARE REQUIREMENTS:
Computer hardware is the collection of physical elements that constitutes a
computer system. Computer hardware refers to the physical parts or components
of a computer such as the monitor, mouse, keyboard, computer data storage, hard
drive disk (HDD), system unit (graphic cards, sound cards, memory, motherboard
and chips), etc. all of which are physical objects that can be touched. In contrast,
software is instructions that can be stored and run by hardware.
 PROCESSOR: Pentium IV processor or Greater
 RAM: 128 Mega Byte (MB) or Greater
 HARDDISK: 1.2 Giga Byte (GB) or Greater
 Keyboard & Mouse
 MONITOR: Colour (For Best Result)
 Printer

10
SOFTWARE REQUIREMENTS:
Computer software, or just software, is any set of machine-readable instructions
that directs a computer's processor to perform specific operations. The term is
used to contrast with computer hardware, the physical objects (processor and
related devices) that carry out the instructions. Computer hardware and software
require each other and neither can be realistically used without the other.

 Operating System: Windows 2000/xp/7

 Front-End: Visual Basic 6.0
 Back-end: Ms access 2007

11
 CHAPTER 4
SOFTWARE DEVELOPMENT LIFE CYCLE

The Software Development Lifecycle is a systematic process for building

software that ensures the quality and correctness of the software built. SDLC
process aims to produce high-quality software which meets customer
expectations. The software development should be complete in the pre-defined
time frame and cost.
SDLC consists of a detailed plan which explains how to plan, build, and maintain
specific software. Every phase of the SDLC lifecycle has its own process and
deliverables that feed into the next phase.

4.1 FEASIBILITY STUDY

An initial investigation in a proposal that determines whether an alternative
system is feasible. A proposal summarizing the thinking of the analyst is
presented to the user for review. When approved, the proposal initiates feasibility
study that describes and evaluates candidate systems and provides for the
selection of best system that meets system performance requirements.
To do a feasibility study, we need to consider the economic, technical
factors in system development. First a project team is formed. The team develops
system flowcharts that identify the characteristics of candidate systems, evaluate
the performance of each system, weigh system performance and cost data and
select the best candidate system for the job. The study culminates in a final report
to the management.

12
4.2 SYSTEM REQUIREMENT AND ANALYSIS
System analysis refers to the process of examining a situation with the intent of
improving it through better process and methods. Systems analysis is, therefore,
the process of gathering and interpreting facts, diagnosing problem and using the
information to recommend information in system or in other words, it means a
detailed explanation or description. Before computerizing a system under
consideration, it has to analyze. We have to study how it function currently, what
has to be analyzed. We need to study how it function currently, what has to be
analyzed. We need to study how it function currently, what are problems and
what are requirements that proposed should meet.

4.3 DATA FLOW DIAGRAM

A data-flow diagram (DFD) is a way of representing a flow of a data of a process
or a system (usually an information system) The DFD also provides information
about the outputs and inputs of each entity and the process itself. DFD must be
consistent. Each process must have its name, inputs and outputs. Each flow
should have its name (exception see Flow). Each Data store must have input and
output flow. Input and output flows do not have to be displayed in one DFD - but
they must exist in another DFD describing the same system. An exception is
warehouse standing outside the system (external storage) with which the system
communicates.

Level 0 DFD or Context Free Diagram:

The level 0 DFD or a context model represents the entire software element as a
single bubble with input and output data indicated by incoming and outgoing
arrows, respectively.

13
In level 0 diagram shown below, the passenger fills either the reservation or
cancellation form as input. He gets the ticket as the output and the report is sent
to the administration.

Level 1 DFD:
A level 1 DFD is the further refinement of level 0 DFD showing greater details
and functionalities. In this, the single bubble of level 0 DFD is refined further.
Each of the processes depicted at level 1 is a sub-function of the overall system
depicted in the context model.
As shown in the DFD above, the passenger either enquires about the trains or
goes directly for the reservation or the cancellation processes as a result of which
he gets the ticket generated. The reports are then sent to the administration.

14
15
 CHAPTER 5
SOFTWARE TESTING

Testing is the major quality control measures used during software

development. Its basic function is to detect errors in the software. After
the implementation phase, computer programs are available that can be
executed for testing purposes. The goal of testing is to uncover
requirements, design and coding errors in the Programme.
Types of Testing are:
1. Unit Testing:
Focuses on individual software units, groups of related units.
• Unit – smallest testable piece of software.
• A unit can be compiled /assembled / linked/loaded; and put under a test
harness.
• Unit testing done to show that the unit does not satisfy the application and
/or its implemented software does not match the intended designed structure.

2. Integration Testing:
Focuses on combining units to evaluate the interaction among them
• Integration is the process of aggregating components to create larger
components.
• Integration testing done to show that even though components were individually
satisfactory, the combination is incorrect and inconsistent.

16
3. System Testing:
Focuses on a complete integrated system to evaluate compliance with specified
requirements (test characteristics that are only present when entire system is run)

 A system is a big component.

 System testing is aimed at revealing bugs that cannot be attributed to a

component as such, to inconsistencies between components or planned
interactions between components.

 Concern: issues, behaviors that can only be exposed by testing the entire
integrated system (e.g., performance, security, recovery).

4. Regression Testing:
Each time a new form is added to the project the whole project is tested
thoroughly to rectify any side effects. That might have occurred due to the
addition of the new form. Thus regression testing has been performed.

5. White-Box testing:
White-box testing (also known as clear box testing, glass box testing, transparent
box testing and structural testing) tests internal structures or workings of a
program, as opposed to the functionality exposed to the end-user. In white-box
testing an internal perspective of the system, as well as programming skills, are
used to design test cases. The tester chooses inputs to exercise paths through the
code and determine the appropriate outputs. This is analogous to testing nodes in
a circuit, e.g. in-circuit testing (ICT).

6. Black-box testing:

17
Black-box testing treats the software as a "black box", examining functionality
without any knowledge of internal implementation. The tester is only aware of
what the software is supposed to do, not how it does it. Black-box testing
methods include: equivalence partitioning, boundary value analysis, all-pairs
testing, state transition tables, decision table testing, fuzz testing, model-based
testing, use case testing, exploratory testing and specification-based testing.

7. Alpha Testing:
Alpha testing is simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site. Alpha testing
is often employed for off-the-shelf software as a form of internal acceptance
testing, before the software goes to beta testing.

8. Beta Testing:
Beta testing comes after alpha testing and can be considered a form of external
user acceptance testing. Versions of the software, known as beta versions, are
released to a limited audience outside of the programming team. The software is
released to groups of people so that further testing can ensure the product has few
faults or bugs. Sometimes, beta versions are made available to the open public to
increase the feedback field to a maximal number of future users.

18
 CHAPTER 6
LIMITATIONS & FUTURE PERSPECTIVE

1. Data redundancy:
It means that same data fields appear in many different files and often in different
formats. In manual system, it poses quite a big problem because the data has to
be maintained in large volumes but in our system, this problem can be overcome
by providing the condition that if the data entered is duplicate, it will not be
entered, otherwise, updating will take place.

2. Difficulty in accessing the data:

In manual system, searching information is time consuming but in our system,
any information can be accessed by providing the primary key.

3. Unsatisfactory security measures:

In manual system, no security measures were provided but in this system,
password security has been provided. The person can access the system by
providing the correct password otherwise he is denied the access.

19
 FUTURE PERSPECTIVE

A software package should always have enough accommodation to meet the

demand for future aspects. Thus system should be flexible enough to
accommodate changes. This system can be more users friendly by introducing
mouse facility in it. Employee information and pay slip form can be further
improved by introducing some more facilities in them. Printing facilities can be
added in report section also.
Some more ways of query can be added according to the need.
As the objective of the project work was to enhance the computerized SHARE
TRADING, in order to access the records easily and to obtain the smooth and
error share management. This can be achieved by this software to some extent.

20
 BIBLIOGRAPHY

1000PROJECTS. Retrieved from http://1000projects.org/share-management-system-vb-net-project.html

creately.com. Retrieved from

https://creately.com/diagram/example/hu0t3h4m/Share%20Marketing%20Management%20System

enggroom. Retrieved from http://www.enggroom.com/VBNet.aspx

GURU99.Retrieved from https://www.guru99.com/software-development-life-cycle-tutorial.html

K.K. AGGARWAL, Y. S. (2014). SOFTWARE ENGINEERING. NEW DELHI: NEW AGE INTERNATIONAL PUBLISHERS.

21