MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

VIVEKANAND EDUCATION SOCIETY POLYTECHNIC

MICRO PROJECT
Academic year: 2022-23

Study and analyze Analysis tools for trading System and draw
UML diagram and test cases

Program: Computer Engineering

Program code: CO-4I (B)
Course: Software Engineering (SEN)
Course code: 22413
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
Certificate
This is to certify that Mr./Miss. Leonhard Dsouza, Aaditi Inamdar, Soham
Jagtap Roll No. 45, 46, 47 of Forth Semester of Diploma in Computer
Engineering Of Institute, V.E.S. POLYTECHNIC (Code: 0004) has Completed
the Micro Project satisfactorily in Software Engineering (22413) for the
academic year 2022 - 2023 as prescribed in the curriculum.

Place: Mumbai Enrollment No: 2100040261-63

Date: ……/……/2023 Exam Seat No:

Subject Teacher Head of the Department Principal

Sangita Bhoyar

Seal of
Institution
 INDEX
Academic year: 2022-23 Name of the faculty: Mrs. Sangita Bhoyar
Program code: CO-4I Course & Course code: Software Engineering (SEN)

Roll No: 45, 46, 47 Enrollment No. 2100040261-263

Semester: 4th
Name of the Students: Leonhard Dsouza, Aaditi Inamdar, Soham Jagtap

SR.NO. CONTENT PAGE NO.

4
1 Brief Introduction
4
2 Aim of the Micro-Project
5
3 Action Plan and Resources Required
5
4 Brief Description
11
5 Implementation & Result
18
6 Skill Developed / learning out of this Micro-Project
19
7 Teacher Evaluation Sheet

Annexure-1

Micro Project Proposal

Study and analyse Analysis tools for trading System and draw UML
diagram and test cases
1.0 Aim of Micro Project:
The Aim of this micro project is to manage risk and to increase profitability in any
market environment and to draw UML diagrams and test cases.

2.0 Course Outcomes Addressed:

CO1: Select suitable software process model for software development.
CO2: Prepare software requirement specification.
CO3: Use software modelling to create data design.
CO4: Estimate size and cost of software product.

3.0 Proposed Methodology:

• Discussion about topic with guide and among group members

• Literature Survey
• Submission of project proposal
• Information collection
• Analysis of Data
• Compilation of the content
• Representation
• Editing and revising the content
• Report Preparation

4.0 Action Plan:

Name of
Planned Planned
Sr. No. Activity performed Responsible Team
Start date Finish date
Members
1 Discussion and finalization of All
06/02/2023 20/02/2023
topic
2 Preparation and submission All
20/02/2023 06/03/2023
of Abstract
3 Literature Review 06/03/2023 13/03/2023 All
 4 Collection of Data 13/03/2023 27/03/2023 All
5 Compilation of Report And All
27/03/2023 10/04/2023
Presentation
6 Actual Presentation & Final All
10/04/2023 24/04/2023
submission of Micro Project

5.0 Resources required:

Name of
Sr. No. Specifications Qty
Resource/material
1 Chrome Free open learning source 2
Microsoft word document
2 Laptop With internet facility
1

3 Printer Hp Laserjet 1

Group Details:
Sr. No. Roll No Name of Student
1 45 Leonhard Dsouza
2 46 Aaditi Inamdar
3 47 Soham Jagtap

Name of Guide: Mrs. Sangita Bhoyar

Annexure-II

Micro Project Report

Study and analyze Analysis tools for trading System and draw UML
diagram and test cases
1.0 Rationale:
Trading analysis software is a powerful tool that traders and investors use to analyze
market data and make informed trading decisions. In this software test case refers to the
actions required to verify a specific feature or functionality in software testing. The test
case details the steps, data, prerequisites, and post conditions necessary to verify a
feature and UML diagrams can be used as a way to visualize a project before it takes
place or as documentation for a project afterward..

2.0 Aim of Micro Project :

The Aim of this microproject is to manage risk and to increase profitability in any Market
environment and to draw UML diagrams and test cases.

3.0 Course Outcomes Addressed:

CO1: Select suitable software process model for software development.
CO2: Prepare software requirement specification.
CO3: Use software modelling to create data design.
CO4: Estimate size and cost of software product.

4.0 Literature Review:

Analysis tools for trading System:-
The impact of algorithmic trading on market liquidity by L. Menkveld (2013): This study
analyzes the impact of algorithmic trading on market liquidity, and how it affects the ability
of traders to buy and sell securities. The author finds that algorithmic trading can improve
liquidity in some situations, but can also create negative feedback loops that exacerbate
market volatility.
Use Cases:-
A use case diagram is the primary form of system/software requirements for a new software
program underdeveloped. Use cases specify the expected behaviour (what), and not the exact
method of making it happen (how). Use cases once specified can be denoted both textual and
visual representation (i.e. use case diagram). A key concept of use case modelling is that it helps
us design a system from the end user's perspective. It is an effective technique for communicating
system behaviour in the user's terms by specifying all externally visible system behaviour.
As said, a use case diagram should be simple and contains only a few shapes. If yours contains
more than 20 use cases, you are probably misusing use case diagrams.
The figure below shows the UML diagram hierarchy and the positioning of the UML Use Case
Diagram. As you can see, use case diagrams belong to the family of behavioural diagrams.

Notations that are used in Use Case Diagram:-

DFD(Data Flow Diagram):-

A data flow diagram (DFD) maps out the flow of information for any process or system. It uses
defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs,
outputs, storage points and the routes between each destination. Data flowcharts can range from
simple, even hand-drawn process overviews, to in-depth, multi-level DFDs that dig progressively
deeper into how the data is handled. They can be used to analyze an existing system or model a new
one. Like all the best diagrams and charts, a DFD can often visually “say” things that would be hard
to explain in words, and they work for both technical and nontechnical audiences, from developer to
CEO. That’s why DFDs remain so popular after all these years. While they work well for data flow
software and systems, they are less applicable nowadays to visualizing interactive, real-time or
database-oriented software or systems.
ER Diagram:-
An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities” such as
people, objects or concepts relate to each other within a system. ER Diagrams are most often used to
design or debug relational databases in the fields of software engineering, business information
systems, education and research. Also known as ERDs or ER Models, they use a defined set of
symbols such as rectangles, diamonds, ovals and connecting lines to depict the interconnectedness
of entities, relationships and their attributes. They mirror grammatical structure, with entities as
nouns and relationships as verbs.
Activity Diagram:-
Activity diagram is basically a flowchart to represent the flow from one activity to another activity.
The activity can be described as an operation of the system. The control flow is drawn from one
operation to another. This flow can be sequential, branched, or concurrent.

State Diagram:-
A state diagram is a type of diagram used in computer science and related fields to describe the
behaviour of systems. State diagrams require that the system described is composed of a finite
number of states; sometimes, this is indeed the case, while at other times this is a reasonable
abstraction.
Test Cases:-
The test case is defined as a group of conditions under which a tester determines whether a
software application is working as per the customer's requirements or not. Test case
designing includes preconditions, case name, input conditions, and expected result. A test
case is a first level action and derived from test scenarios.

The primary purpose of writing a test case is to achieve the efficiency of the application.

TEST CASE TEMPLATE

Overall, these studies and articles highlight the importance of trading analysis software in the
financial industry, and how it can be used to improve trading performance, risk management,
and decision-making. They also emphasize the need for careful analysis and testing of trading
strategies to ensure their effectiveness and reliability.

5.0 Actual Methodology Followed:

• Discussion about topic with guide and among group members
• Literature Survey
• Submission of project proposal
• Information collection
• Analysis of Data
• Compilation of the content
• Representation
• Editing and revising the content
• Report Preparation

6.0 Actual Resources Used:

Sr. Name of
Specifications Qty Remarks
No. Resource/material
Free open learning
1 Chrome source
2

Microsoft word
2 Laptop document 1
With internet facility
3 Printer Hp Laserjet 1
7.0 Outputs of micro-projects
ER DIAGRAM FOR TRADING ANALYSIS SOFTWARE
 TEST TEST CASE TEST CASE STEPS EXPECTED RESULT ACTUAL RESULT STATUS
CASE_ID DESCRIPTION

TC 01 Verify valid username and Enter username and password Software should display main Displayed Main window Successful
password & click on login window
button

TC02 Verify valid username and Enter username and password Display “Invalid password “ Displayed error of invalid Successful
invalid password & click on password
login button

TC 03 Verify invalid username and Enter username and password Display “Invalid credentials” Displayed invalid Successful
invalid password & click on credentials
login button

TC 04 Signing up for account Enter personal and account Enter account and personal Account created successful
information information successfully

TC 05 Forgot password Click Forgot password and Generate OPT through login OPT send and password Successful
Enter Login Gmail account Gmail to change password changed

TC 06 Verify Bank account Field by Enter Account Credentials Display “Valid Account Invalid Account number Unsuccessful
entering the valid account Credentials”
number and PIN

TC 07 Verify the user knowledge Select your Type from given Diplay Displayed “1.Rookie, Successful
towards trading options “1.Rookie, 2. Intermediate, 2.Intermediate, 3.Expert”
3. Expert” and “Choose one that
suits your knowledge”

TC 08 Search company Enter name of company in Display trading Information Displayed (“About the Successful
search bar and about company company and Trades of
company”)

TC 09 Verify current valuation of Click on company current Display company current Displayed current Successful
company valuation valuation valuation of the company

TC 10 Reminder for end of stock Allow notification from our Remind end of stock market Reminded exactly half n Successful
market time period (Closing software hour i.e 3.00 AM before
Bell) closing bell

TC 11 Check working of ‘StopLoss’ Set buy and sell triggers while Software should maintain buy Software is accurately Successful
trading and sell position according to working according to
StopLoss StopLoss

TC 12 Check working of Bar charts,
graphs and candlestick charts
provided for company
Click on ‘view analytics’ of
that particular company
Display Bar chart, Graphs ,
candlestick charts, tick chart,
etc
Displayed analytics of Successful
particular company like
graphs and charts on
basis of current market
valuations

TC 13 Digital wallet Click on ‘Digital Wallet’ on Software should display Displayed profit, loss and Successful
Top right corner Transaction window transactions

TC 14 Get Help Click on “Get Help? “ Software should help the user Displayed solution of Successful
if faced any difficulty generally occurring
problems in software

TC 15 Log Out Click on “ LOGOUT ” Software should open login Login page opens Successful
page again
TEST CASES FOR TRADING ANALYSIS SOFTWARE
 8.0 Skill Developed / learning out of this Micro-Project
The following skills were developed-
1 Designing: Designing of micro project with minimum required resources and
at low cost.
2 Teamwork: Learned to work in a team and boost individual confidence.
3 Time Management: Timely completion of micro project as scheduled.
4 Data Analysis: Interpretation of data: drawing and analysis of graphs,
laboratory calculations, etc.
5 Problem-solving: Develop good problem-solving habits.
6 Technical writing: Preparing a report of the proposed plan and final report.
7 Presentation: Giving working model presentation of the micro project.

9.0 Applications of this Micro – Project.

• It is commonly used for technical analysis, which involves studying

historical market data to identify patterns and trends.
• It can also be used for fundamental analysis, which involves analyzing a
company's financial statements, economic indicators, and other relevant information to
determine its intrinsic value.
• It is often used for algorithmic trading, which involves using computer
programs to execute trades based on pre-defined rules and algorithms.
• This project will help all end users as a user friendly system

References:

https://youtu.be/9mSFYWMjZuo

https://www.investopedia.com/articles/active-trading/121014/best-technical-
analysis-trading-software.asp

Sign of the faculty

Mrs. Sangita Bhoyar

 Annexure-III
Suggested Rubric for Assessment of Micro-Project

S. Characteristic to be Poor ( Marks Average Good ( Marks Excellent

No. assessed 1-3) ( Marks 4 - 5 ) 6-8) ( Marks 9- 10 )
Relevance to the course Relate to very few Related to some LOs Take care of at-least one Take care of more than
1
LOs CO one CO
Not more than two
sources At-least 5 relevant
Literature Survey (primary and At –least 7 relevant About 10 relevant
2 sources, at least 2
/information collection secondary), very old latest sources, most latest sources, most latest
reference
Completion of the
Completed less than Completed more than 80
3 Target as per project Completed 50 to 60% Completed 60 to 80%
50% %
proposal
Enough data collected
Sufficient and
Sufficient and appropriate by sufficient and
appropriate
Sample Size small, sample, enough data appropriate sample size.
sample, enough
data neither Proper
Analysis of Data and data generated but generated
4 organized inferences drawn by
representation not organized and which is organized and
nor presented well organising and
not presented well. presented well but poor presenting data
No or poor inferences drawn through tables, charts
inferences drawn
and graphs.
Just Well
assembled/fabricated Well assembled/fabricated
and parts are not assembled/fabricated
with proper
functioning with proper functioning
parts. In proper shape, functioning parts. In
Quality of Incomplete well. Not in proper proper shape, within
5 Prototype/Model shape, dimensions within tolerance
tolerance dimensions
fabrication/assembly. beyond tolerance dimensions and good
and good
limit. finish/appearance. But
finish/appearance.
Appearance/finish is no creativity in design and
Creativity in design
shabby. use of material
and use of material
Nearly sufficient
Very short, poor and correct details
quality sketches, about methods, Very detailed, correct,
Detailed, correct and clear
Details about material, clear description of
description of methods, materials,
methods, precautions and methods, materials,
6 Report Preparation material, conclusion. but precautions and
precautions and
precaution and clarity is not there in conclusions. Enough
Conclusions. Sufficient
conclusions presentation. tables, charts and
omitted, some details But not enough Graphic Description.
sketches
are wrong graphic description.

Major information is Includes major Includes major Well organized,

Presentation of Micro not included, information but information and well includes major
7 information is not not well organized organized but not presented information ,well
Project and not presented
well organized . well presented
well
Replied to
Could not reply to considerable Replied properly to
Replied most of the
8 Viva considerable of number of considerable number of
questions but not questions properly
question. question.
 very properly

Annexure – IV
Micro-Project Evaluation Sheet
Academic year: 2021-22 Name of the faculty: Mrs. Sangita Bhoyar
Program code: CO-4I (B) Course & Course code: Software Engineering (SEN)

Roll No: 45, 46, 47 Enrollment No: 2100040261-63

Semester: 4th Name of the Students: Leonhard Dsouza, Aaditi Inamdar, Soham Jagtap
Title of the Micro-Project: Study and analyze Analysis tools for trading System and draw
UML diagram and test cases Course Outcomes Achieved:

CO1: Select suitable software process model for software development.

CO2: Prepare software requirement specification.

CO3: Use software modelling to create data design.

CO4: Estimate size and cost of software product.

Evaluation as per Suggested Rubric for Assessment of Micro Project

Sr. Characteristic to be Poor Average Good Excellent Sub Total

No assessed Marks Marks Marks Marks 9-
. 1-3 4-5 6-8 10
(A)Process and product assessment Out Of 6
1 Relevance to the course
2 Literature Survey .
Information Collection
3 Completion of the Target
as per project proposal
4 Analysis of Data and
representation
5 Quality of
Prototype/Model/Content
6 Report Preparation
(B)Individual Presentation/Viva Out of 4
7 Presentation .
8 Viva
 Micro-Project Evaluation Sheet

Process and Product Individual Total

Roll
Name Assessment Presentation/Viva Marks
No.
(6 marks) (4 marks) 10

Leonhard Dsouza
45

Aaditi Inamdar
46

Soham jagtap
47

Comments/Suggestions about teamwork/leadership/interpersonal communication (if any)

……………………………………………………………………………………………..

……………………………………………………………………………………………..

Name and designation of the Faculty Member: Mrs SANGITA BHOYAR (Lecturer)

Signature________________