Tribhuvan University

Institute of Science and Technology

New Summit College

Old Baneshwor, Kathmandu Nepal

A Project Report
On
Tapaiko Share

Submitted by:
Nitesh Parajuli, 1504/068
Gaurav Tripathee, 1497/068
Samundra Sharma Pandit, 1521/068
Prakritee Tuladhar, 1506/068

In partial fulfillment for the award of the degree of

Bachelors of Science
In
Computer Science and Information Technology (BSc CSIT)

September, 2015
 ACKNOWLEDGEMENT

The success and final outcome of this assignment required a lot of guidance and assistance
from many people and we feel extremely fortunate to have got all this all along the completion
of our assignment work. Whatever we have done is only due to such guidance and assistance
and we would not forget to thank them. We take this opportunity to express our profound
gratitude and deep regards to our supervisor Mr. Arjun Sunwar for his exemplary guidance,
monitoring and constant encouragement throughout the course of this thesis. The blessing,
help and guidance given by him time to time shall carry me a long way in the journey of life
on which we were about to embark.

We could not have completed this project without help from our college “NEW SUMMIT
COLLEGE” which gave the supportive hands before us academically, also regarding other
activities related to Information Communication Technology as well as extra curriculum
activities that we got to participate in. It gave us family like environment.

We also take this opportunity to express a deep sense of gratitude to Mr. Romkant Pandey,
project guide, and Mr. Kumar Paudyal, coordinator, New Summit College, for his cordial
support, valuable information and guidance, which helped us in completing this task through
various stages.

Lastly, we thank almighty, our parents, brothers, sisters and friends for their constant
encouragement without which this assignment would not be possible.
 ABSTRACT

Stock market is one of the most unpredictable markets. The values of stock fluctuate every
passing minute. So for general public and for investor it is very much difficult to keep track of
their investment, their share prices, either they are in profit or they are in loss. The system we
have developed here is the solution of all these difficulties. Our system helps to keep track of
bought or sold shares. It also helps to keep track of buying selling date and other information
about shares. It also calculates the profit or loss of the investment on the basis of purchase
date, purchase price and current share price.

Our system is based on stock market of Nepal i.e. NEPSE.

During the development period of this project we have gone through various stages from
requirement collection, feasibility analysis, system design, development to testing and
maintenance. We have used PHP as programming language, MySQL as database for backend
whereas CSS, HTML, JavaScript and other scripting language at front end. We used our own
custom MVC. Unit testing and integrated testing has been done to test and verify the
effectiveness and reliability of the system. The system is completely web based and can be
used with any computers or mobile devices with the availability of internet.

Nepal stock portfolio tracker allows users to create their personal profile, add information
about their shares, and in return users can easily track the profit and loss, and other detailed
information about their shares. Users can also browse history and view the past performance
of respective banks and their shares.
 List of Figures
Figure 1 - Incremental Development Life Cycle...........................................................9
Figure 2 - Work Division Structure for Tapaiko Share................................................10
Figure 3 - Information Domain Value.........................................................................11
Figure 4 - Calculation of Functional Points.................................................................11
Figure 5 - Calculation of Line of Code........................................................................12
Figure 6 - Calculation of Effort and Duration..............................................................12
Figure 7 - GANTT Chart..............................................................................................13
Figure 8 - System Architecture Overview...................................................................14
Figure 9 - Use Case Diagram.......................................................................................15
Figure 10 - Use Case Diagram (Profile Update)..........................................................15
Figure 11 - Class Diagram...........................................................................................16
Figure 12 - Activity Diagram.......................................................................................17
Figure 13 - Sequence Diagram.....................................................................................18
Figure 14 - Sequence Diagram (Login).......................................................................18
Figure 15 - Sequence Diagram (Profile Update)..........................................................19
Figure 16 - Component Diagram.................................................................................20
Figure 17 - Deployment Diagram................................................................................21
Figure 18 - Database Schema Design..........................................................................22
Figure 19 - Integration Testing (Login).......................................................................28
Figure 20 - Integration Testing (Profile Update).........................................................29
 List of Tables
Table 1 - Comparison between top online portfolio tracker sites..................................1
Table 2 - Unit Testing (Login module)........................................................................24
 Abbreviations

NEPSE Nepal Stock Exchange

AGM Annual General Meeting

ROI Return of Investment

SDLC System Development Life Cycle

RAD Rapid Application Development

JAD Joint Application Development

COCOMO Constructive Cost Model

DFD Data Flow Diagram

E-R Entity-Relationship

HTML Hypertext Markup Language

PHP Hypertext Preprocessor

PC Personal Computer

MS Microsoft
Table of Contents

ACKNOWLEDGEMENT..............................................................................................i

ABSTRACT...................................................................................................................ii

List of Figures...............................................................................................................iii

List of Tables................................................................................................................iv

Abbreviations.................................................................................................................v

Chapter I.........................................................................................................................1

1 Introduction........................................................................................................1

1.1 Background..................................................................................................1

1.2 Problem Statement.......................................................................................1

1.3 Objective......................................................................................................2

1.4 Scope and Limitations.................................................................................2

1.4.1 Scope....................................................................................................2

1.4.2 Limitations............................................................................................2

Chapter II.......................................................................................................................3

2 Requirement Analysis...........................................................................................3

2.1 Study of Existing Systems...........................................................................3

2.2 Data Collection Methods.............................................................................5

2.2.1 Interviews.............................................................................................5

2.2.2 Web Surfing..........................................................................................5

2.2.3 Scenario Analysis.................................................................................5

2.3 Software Requirement Specifications..........................................................5

2.3.1 Functional Requirements......................................................................5

2.3.2 Non Functional Requirements..............................................................6

2.4 Feasibility Analysis......................................................................................6

 2.4.1 Technical Feasibility............................................................................6

2.4.2 Operational Feasibility.........................................................................6

2.4.3 Economic Feasibility............................................................................6

Chapter III......................................................................................................................8

3 System Planning.....................................................................................................8

3.1 Software Development Model.....................................................................8

3.1.1 Main activities of the development process.........................................9

3.2 Work Division Structure............................................................................10

3.3 Resource Requirement (COST Estimation)...............................................11

3.4 Time Schedule...........................................................................................13

Chapter IV....................................................................................................................14

4 Design..............................................................................................................14

4.1 System Architecture or Overview..............................................................14

4.2 Use Case Diagram.....................................................................................15

4.3 Class Diagram............................................................................................16

4.4 Activity Diagram.......................................................................................17

4.5 Sequence Diagram.....................................................................................18

4.6 Component Diagram..................................................................................20

4.7 Deployment Diagram.................................................................................21

4.8 Database Schema Design...........................................................................22

4.9 Algorithm (Prediction)...............................................................................23

Chapter V.....................................................................................................................24

5 System Development and Testing....................................................................24

5.1 Tools Used.................................................................................................24

5.1.1 Front End............................................................................................24

 5.1.2 Back End............................................................................................24

5.2 Testing.......................................................................................................25

5.2.1 Unit Testing........................................................................................25

5.2.2 Integration Testing..............................................................................28

5.2.3 System Testing...................................................................................29

Chapter VI....................................................................................................................30

6 Implementation and Maintenance....................................................................30

6.1 Implementation Plan..................................................................................30

6.2 Maintenance...............................................................................................30

6.2.1 Correction...........................................................................................30

6.2.2 Adaptive.............................................................................................30

6.2.3 Perfective............................................................................................31

Chapter VII...................................................................................................................32

7 Future Plan and Conclusion.............................................................................32

Annex I (Snapshots).....................................................................................................33

Annex II (Code)...........................................................................................................34

Bibliography.................................................................................................................35
 Chapter I

1 Introduction

1.1 Background

Stocks are the capital raised by a company or corporation through the issue and
subscription of shares.

A stock exchange lists and helps trading of shares by bringing buyers and sellers
together. Every general people nowadays own shares of various organizations so that
they are always in need of proper system that can track their investments in shares,
their transactions, profits, and about the business analytics of the organization they
have invested on.

Stock market is a place where shares are bought and sold. Stock market is very
sensitive where price fluctuation may occur in minutes. So keeping track of past
performance, present performance and analyzing it to make future investment could
be very much beneficial to any investor. Also keeping track of the investment is
essential with the help of Portfolio Tracker. The initial investment, the loss or profit,
and every other transaction can be kept into record.

This helps users or the investors to keep track of their investment with ease in
systematic, scientific and digital way.

1.2 Problem Statement

Stock market is one of the most unpredictable markets. The values of stock fluctuate
as the minute passes by. So, for general public and for investor it is very much
difficult to keep track of their investment, their share prices, either they are in profit or
loss. Also, what if there is some system that can accumulate these data and auto-
analyze the price for tomorrow’s market? We came across a thought of building a
system that will help user to keep track of their shares and somehow auto-analyze the
approximate value of tomorrows share price. So, why did we choose Tapaiko Share?

 Unpredictability of share market and daily market fluctuations.

 Difficulty for general public to evaluate the share market.
 No existing system that provides user specific data.
Tapaiko Share will be a great platform for the share investors to find an easy access to
their listed shares and also for the naïve investors to get thorough information on what
share market is and how it works.

1.3 Objective

Proposed software have following objectives:

 To Hhelp users to keep track of their investments

 To provides Auto-analysis of Share Market and market values
 To provides Facilitate auto-calculation of user’s profits and losses
 To Provide support for making investment related decisions

1.4 Scope and Limitations

1.4.1 Scope

 Keeping track of user investments and information in accordance with the

latest market values.
 Help user to make the right investments and strategies.

1.4.2 Limitations

 High risk of market fluctuations.

 Unpredictability of Share Market.
 Chapter II

2 Requirement Analysis

As required by our system, we adopted various methodologies to collect the required

and reliable data, specifically centralized on Stock Market of Nepal.

2.1 Study of Existing Systems

Nepal Stock Exchange Pvt. Ltd. (NEPSE)

NEPSE is the only stock exchange company of Nepal that provides the basic
information about the Stock Market and the basic Stock Market scenarios. Users can
access the stock market values of all the listed companies, banks, and/or organizations
but not that of their relative organizations. These data are hard for naïve users and
general public to understand. Also, auto-analysis and calculation of the user profit or
losses is not provided.

There are some other systems/services such as sharesansar.com,

Nepalsharemarket.com, etc. that provides information about the Stock Exchange
provided by NEPSE. They too cannot provide automatic data analysis and user
specific information.

These systems are the primary source of data retrieval for Tapaiko Share.
Comparison between top online portfolio trackers

We studied three online portfolio tracking sites: Morningstar, SmartMoney, and Wikinvest. On studying them, we obtained the following
information:

Table 1 - Comparison between top online portfolio tracker sites

Website Name Morningstar.com SmartMoney.com Wikinvest

Company Morningstar, Inc. SmartMoney Magazine Wikinvest
Web Address www.morningstar.com www.smartmoney.com www.wikinvest.com
Subscription Price free to $21.95/mo. free; $5.95/mo. or $58/yr. free
automatic (delayed quotes),
Portfolio Updates (Frequency of Updates) automatic (delayed quotes) automatic (delayed quotes)
real-time $58/yr.
Desktop Software Compatibility Money, Quicken, Excel Money, Quicken , Excel  
Brokerage Services none None 55
Bloomberg, Businessweek, CNN
Financial Times, Dow Jones Barrons Online, Dow Jones
Money, Forbes, MarketWatch,
Newswires, MarketWatch, Newswires, MarketWatch,
Newswire Services New York Times, PR Newswire,
Morningstar, PR Newswire, Motley Fool, SmartMoney,
RealMoney, Reuters,
Reuters, Seeking Alpha WSJ.com  
TheStreet.com, WSJ.com
Email Alerts (News/Price
yes (news/dividends/splits) yes (price targets) yes (news)
Targets/Dividends/Splits)
Email Reports (Security Values/Market
yes (security values) yes (security values) yes (security values)
Summary)
Additional Stock Screening/Mutual Fund yes Yes  
Analysis Tools Screening
 Financial Planning yes Yes  
Interactive Charting yes Yes yes
25/140 (free), 25/280
Maximum Portfolios/Securities per Portfolio 50/50 unlimited/unlimited
(premium)
Maximum Securities 3,500 (free), 7,000 (premium) 2,500 unlimited
Cash/Stocks/Mutual
yes Yes yes
Funds/ETFs
Bonds
yes    
Securities/Assets (Fixed/Variable/Zero/PIK)
Handled Annuities      
Options/Futures/Warrants   yes (options) yes (options)
Real Estate/Partnerships      
User-Defined      
Identification
yes (name/ticker) yes (name/ticker) yes (name/ticker)
(Name/Ticker/CUSIP)
Account
Security     yes
Number/Management Firm
Classification
Asset Class (Predefined/User-
yes (predefined) yes (predefined) yes (predefined)
Defined)
Industry yes Yes yes
Transactions Deposit/Withdrawal; Buy/Sell yes Yes yes
Handled Short/Cover   Yes yes
Margin     yes
Dividends yes Yes yes
(Cash/Stock/Splits/Reinvest)
 Receive/Deliver Security      
Interest Income yes    
Treatment of
yes Yes yes
Fees/Commissions
Security Lot Assignments (Avg.
  yes (average cost) yes (FIFO)
Cost/FIFO/Specific Lot)
Current Holdings yes Yes yes
Holdings by Lots      
Cash Portfolio Status yes Yes yes
Tax Schedules
Reports
(Interest/Dividends/Capital      
Gains)
Projected Cash Flows      
Customized Reports/Views yes Yes yes
Security/Industry/Asset yes (security/industry/asset
yes (security) yes (security/asset class)
Class/Investment Style class)
Portfolio (Single/Multiple) yes (single) Yes yes
Holding Period/Between
Performance yes Yes yes (holding period)
Period Returns
Reports
Value-Weighted IRR/Time-
yes yes (time-weighted) yes (time-weighted)
Weighted Returns
Tax-Adjusted Returns      
Benchmark Comparison yes Yes yes
Import/Export Data yes Yes yes
2.2 Data Collection Methods

2.2.1 Interviews

We took interviews with some users, Stock Market Personnel, investors, and
shareholders regarding the Stock Market and Market fluctuations. The subject of the
interview were those that were directly involved in day to day stock exchange
scenarios, and have great deal of knowledge on Share Market. The thus-obtained
information provided us a more detailed knowledge on the working of Stock Market.

2.2.2 Web Surfing

We researched some important topics over the Internet that would help with our
project. We surfed the Internet to obtain the basics on Stock Market. We also studied
the existing systems, and their features through the Internet. We studied some
algorithms which would help us in analyzing the share market.

2.2.3 Scenario Analysis

We analyzed the present market scenarios, other existing systems, what they have
implemented and achieved till date. We also studied about the stock exchange of other
countries.

2.3 Software Requirement Specifications

2.3.1 Functional Requirements

 Registration and Login

The users must register before accessing Tapaiko Share. Once they
register, they should login to access the data.
 Personal profiling interface
The users should be provided with a personal profile in which they can add
and update their personal information. They should be provided with the
facility of keeping track of their shares and add or remove their share data.
 Auto-analysis of share market
The system should auto-analyze the past records and provide information
to the users about the market trends.
 News about listed companies
 The system should provide news such as AGMs, book closures and
dividend.
 Access to broker information
The system should provide information about the brokers.

2.3.2 Non Functional Requirements

 User friendly
The system is easy and convenient for users to use. The user interface is
easy to understand and use.
 Responsive
We have used responsive.css stylesheet to make the website responsive.
 Availability
The system would be easily available once hosted over the internet.

2.4 Feasibility Analysis

2.4.1 Technical Feasibility

The application runs on your browser with the access of the Internet. No extra
hardware or software are required to run the system. The application is
technologically supportable, viable, and is a state of art in technology.

2.4.2 Operational Feasibility

This system is operationally feasible. Operational feasibility of any system is the

measure of how well the system can solve the problems, and how well it can take
advantage of the opportunities identified during scope definition and how it satisfies
the requirements identified in the requirement analysis phase of system development.
This system can solve the problems efficiently and can satisfy the needs specified by
users and investors.

2.4.3 Economic Feasibility

The use of open source codes such as PHP and MySQL allowed the project to
complete in low cost. The availability of Internet in cheap price makes the application
economically feasible. Due to availability of electronic systems and technologies, the
cost of paperwork is reduced.
Also, after the calculation of ROI (Return of Investment), we can say that the system
is economically worthwhile.

Calculation of the cost benefit analysis, this system is viable based on return of
investment method, net present value and payback method.
 Chapter III

3 System Planning

System planning is the phase in software development where we make plans on how
to develop the system based on the collected requirements.

3.1 Software Development Model

Software Development work is divided into many distinct phases with an intent of
better planning and management and is called a software model. Each phases are a
part of the SDLC. Some of the most known software development models are
Waterfall model, Spiral model, RAD, JAD, etc.

Among the many development models that are available, we found that Incremental
development model was the best choice for this project. The Incremental development
model combines the elements of waterfall model which are then applied iteratively. It
basically delivers a series of releases called increments which provide progressively
more functionality at each delivery of the increments. This process continues till the
complete system is achieved.

The advantages of using Incremental development model are:

 Generates working software quickly and early during the software life
cycle.
 This model is more flexible, less costly to change scope and requirements.
 It is easier to test and debug during a smaller iteration.
 In this model customer can respond to each built.
 Lowers initial delivery cost
 Easier to manage risk because risky pieces are identified and handled
during each iteration.

The reason for choosing this model is because the major requirements of the system
were clearly known and were fixed. Also, this model generates a working software
quickly and early during the SDLC. This model is more flexible and less costly.
 Figure 1 - Incremental Development Life Cycle

3.1.1 Main activities of the development process

The steps of SDLC can be broken down as follows:

a. Requirement Analysis
Before developing the system essential requirements were collected.
Determining the requirement, work plan was developed to meet the
requirement objectives. After that analyzing the system concept and function
further processes began.
b. Design and Development
Determining concept of proposed system, the framework of system was
developed and introduced. In this period, the overall system design and
database designs were created. After the designs were made, coding began.
c. Testing
Each modules were tested, integrated and again tested. Error checking and
debugging were done simultaneously.
d. Implementation
After the development of the system, we plan to host it over the internet.

3.2 Work Division Structure

Tapaiko Share

Requirement
Design Coding Testing
Collection
 Background Layout Form Validation Errors

Database
Interviews Main Activity Debug
Connection
3.3 Resource Requirement (COST Estimation)

We used the Basic Constructive Cost Model (COCOMO) for cost estimation.
Background
Analysis Database
Datadeveloped
COCOMO is an algorithmic software constitutional model Pulling by Barry W.
Boehm. The model uses a basic regression formula with parameters that are derived
from historical project data and current project characteristics.
Session
Documentation
Management

Calculations

User
Information

Figure 3 - Information Domain Value

Figure 4 - Calculation of Functional Points

 Figure 5 - Calculation of Line of Code

Figure 6 - Calculation of Effort and Duration

 3.4 Time Schedule

The time schedule of the project is shown by the

following GANTT Chart:

Figure 7 - GANTT Chart

 Chapter IV

4 Design

4.1 System Architecture or Overview

The main component of the system architecture are Internet, web server and database
and end users. The system is fully web-based. The system architecture can be
depicted through the diagram shown below:

Figure 8 - System Architecture Overview

4.2 Use Case Diagram

Figure 9 - Use Case Diagram

Figure 10 - Use Case Diagram (Profile Update)

4.3 Class Diagram

Figure 11 - Class Diagram

4.4 Activity Diagram

Figure 12 - Activity Diagram

4.5 Sequence Diagram

Figure 13 - Sequence Diagram

Figure 14 - Sequence Diagram (Login)

Figure 15 - Sequence Diagram (Profile Update)
4.6 Component Diagram

Figure 16 - Component Diagram

4.7 Deployment Diagram

Figure 17 - Deployment Diagram

4.8 Database Schema Design

Figure 18 - Database Schema Design

4.9 Algorithm (Prediction)

Step 1: Start

Step 2: Read from database 50 previous data of a Listed Company and store in an
array.

Step 3: Find the average of the data and set it as a variable avg.

Step 4: Group the data comparing to the average.

If the data is greater than the average

Make it a separate group and store in an array

Find the average of this group

If the data is smaller than the average

Make it a separate group and store in an array

Find the average of this group

Step 5: Add the average to the latest value of the data. Store it as D1.

Step 6: Find the difference between each data in the grouped data

Step 7: Find the average of the differences.

Step 8: Add the average to the latest value of the data. Store it as D2.

Step 9: Find the average of D1 and D2. Store it as D.

Step 10: Print D.

Step 11: Stop

 Chapter V

5 System Development and Testing

System development and testing is the most important in SDLC. This stage consists of
two most important parts, i.e. coding tools used and testing strategies.

5.1 Tools Used

5.1.1 Front End

 Sublime Text version 2.2

Sublime Text is the text editor used for coding purpose.
 Web Browser
Web browser is used to access Tapaiko share.
 Photoshop CS6
Photoshop is used to design the logo of Tapaiko Share.
 HTML
HTML is used to define how the webpage looks like.
 CSS
CSS is used to add styling to the webpage.
 PHP version 5.4.12
We have defined custom MVC in PHP to design the overall working of
Tapaiko Share.
 MS Word 2013
MS Word is used for the purpose of documentation.
 MS Visio Professional 2013
MS Visio is used for making different diagrams.

5.1.2 Back End

 MY-SQL version 5.0.10

We used MySQL database to store data.

5.2 Testing

Testing is the process of determining whether the developed system meets our
objectives or not. It is one of the most important phases of SDLC. This phase
consumes 40-50% of development efforts and consumes more effort for systems that
require higher levels of reliability. As the amount of maintenance and upgrade of
existing systems grow, significant amount of testing will also be needed to verify
systems after changes are made. Despite advances in formal methods and verification
techniques, a system still needs to be tested before it is used. Testing remains the truly
effective means to assure the quality of a software system of nontrivial complexity, as
well as one of the most intricate and least understood areas in software engineering.
Testing, an important research area within computer science is likely to become even
more important in the future.

The various testing techniques used in Tapaiko Share

Testing is involved in every stage of SDLC, but the testing done at each level of
software development is different in nature and has different objectives.

5.2.1 Unit Testing

The basic unit of software that is testable is known as a module or unit. After the
coding of modules, they were tested, made error free and debugged. In this way we
carried out the unit test.
Unit testing for Login module

Table 2 - Unit Testing (Login module)

Test case Expected Observed Pass/Fai

Test case Preconditions Input test data Steps to be executed
ID result result l
1 Test if user login User must be Correct a. Enter correct User must be User logged in Pass
succeeds with correct already username, username and correct able to login successfully
username and correct registered correct password in successfully
password password respective fields
b. Click Login
button
2 Test if unregistered User must be Incorrect a. Enter incorrect User must be User could not Pass
user is denied unregistered username, username and denied login
successful login incorrect incorrect password in successful
password respective fields login
b. Click Login
button
3 Test if login is denied User must be Correct a. Enter correct User must be User could not Pass
when username is registered username username in denied login
correct and password respective field successful
filed is empty b. Click Login login
button
4 Test if login is denied User must be Correct a. Enter correct User must be User could not Pass
when username field registered password password in denied login
is empty and respective field successful
password is correct b. Click Login login
button
5 Test if login is denied Incorrect a. Enter incorrect User must be User could not Pass
when both username username, username and denied access login
 and password is incorrect incorrect password in
incorrect password respective fields
b. Click Login
button
6 Test if login is denied a. Click login button Access must be Access was Pass
when username and denied denied
password fields are
empty
5.2.2 Integration Testing

It is performed when two or more tested units are combined into a larger structure.
The test is often done on both the interfaces between the components and the larger
structure being constructed, if its quality property cannot be assessed from its
components. After integrating the requirements we tested, it was fine and satisfactory.

Figure 19 - Integration Testing (Login)

 Figure 20 - Integration Testing (Profile Update)

5.2.3 System Testing

System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system’s compliance with its specified requirements. After the
working modules were integrated to form a complete system, it was tested again. The
completed system fulfilled the specified requirements and works as per desired.
 Chapter VI

6 Implementation and Maintenance

6.1 Implementation Plan

During implementation process we should consider various factors like risk, expected
benefits, performance of system, and maintenance process in long run. Our system is
completely web based so, to implement it we will buy some domain name. Our
system will be accessible in that domain name via internet. User can get all the
services provided by system through it.

6.2 Maintenance

Maintenance is the process of modifying software product after its delivery to correct
fault and improve performance. We cannot make a perfect and reliable system at once
so maintenance plays a very important role in the SDLC. We need an accurate and
effective maintenance plan.

Software maintenance is a very broad activity that includes error correction,

enhancements of capabilities, deletion of obsolete capabilities, and optimization.
Because change is inevitable, mechanisms must be developed for evaluation,
controlling and making modifications. Regarding these aspects we have planned
following maintenance techniques:

6.2.1 Correction

A system is made by integrating simpler and easy components. If any bug is found,
instantly it can be debugged. Coding standard or coding pattern is simpler so that it is
easy to find out logical errors. Also, it can be checked and maintained. If the system
does not meet its requirement objectives, requirement errors can be solved and
reintegration or remake of system can be done. In this way, system bugs, logical
errors, and requirement errors can be corrected.

6.2.2 Adaptive

Adaptive maintenance is modifying the system to cope with changes in the software
environment. System is made considering present software and hardware trend. It is
supported by almost every machine with internet browsers. It will be compatible with
further upgrades in those browsers.

6.2.3 Perfective

Perfective maintenance means implementing new or changed user requirements

which concern functional enhancements to the software. The system is developed in
such a way that it can be upgraded and more features could be added in future. This
makes it easier to perfect our system every time maintenance is done.
 Chapter VII

7 Future Plan and Conclusion

The whole financial system of any country or even of the world is completely
dependent upon the slight fluctuation of the stock price and its market. Our system
has to deal with the users share prices depending upon stock fluctuation and change in
the stock market. The future project plan is to improve the analytical efficiency of
Tapaiko Share so that it can provide an even more efficient decision support to its
users. Also, keeping track of user needs is necessary in order to make any needed
changes to the system.

We have planned to gradually upgrade our system and provide more service related to
stock market which could help stock brokers, buyers, sellers in every possible way.
Annex I (Snapshots)
Annex II (Code)
 Bibliography
Add bibliography

Add Annex for supporting document

Add major source code in ANNEX

Add some Snapshots