A MICRO PROJECT

On

Mathematical Equation Solving Software

➢ Aims/Benefits of the microproject :

The aim of the course is to help the student to affiant following industry identify
compendancy through various teaching, learning experience.

➢ Course outcome addressed:

Developing a Mathematical equation solving software.

➢ Proposed methodology:

This program include ALP instructions to manage the flow of program for finding the
length of String

➢ Action Plan :
Sr. Plan start Plan finish Name of responsible
Detail of activity
No date date team member

1 Group discussion

Searching of real life

2
task

Selection of micro
3
project topic

4 Gathering of information

5 Group discussion
 Distribution of works to
6
be done

Preparing the overview

7
of project

8 Gathering the details

9 Testing the code

10 Implementing the code

11 Demonstration

12 Group discussion

13 Gathering the data

14 Giving different inputs

Testing the remaining

15
code

16 Preparing report

➢ Resources used

Sr. no. Name of resource material Specifications Quantity

1 PC - 1

2 Operating System - 1

3 Software for Diagrams Star UML 1

➢ Introduction :-

As an Engineering student we always need to deal with the mathematical

expressions and their solutions. Many times during solving the expressions our
solution gets wrong or we have quite confusion about our solution then we try to find
the solution of that expression using “google.com” but we can’t.

➢ Problem :-
 To find the solution of our mathematical expression we type our
expression in Google search box , we get many solutions of it but we don’t get the
perfect solution of the expression and get the related solutions. Due to this we are
not able to get the step- by – step procedure for solving the expression and due to
this our confirmation for our solution is not found.

➢ Solution :-

Hence, as we discussed about the problem for solution of mathematical

expression we need a software that provide step – by – step procedure for solving
mathematical expression in an easy way.

The software that is to be developed should provide the facility of typing as

well as scanning the expression and should provide the result accordingly. It should
not show only the single procedure to solve the expression but show all the possible
ways to solve it. So, it will become easy for us to understand step – by – step
procedure and the easy way to solve it. This software should provide description of
each step of solution which will help us to understand the procedure in detailed
format.

➢ Objectives :-

• The software should be simple to grasp and easy to use the usual arithmetic
functions and exponential.
• This software calculates math problems with the cameras quickly and
accurately.
• It can solve the problems such as exponential , integrations , logarithms ,
derivations and so on.
• It should also display the mathematical graphs based on
• the scanned equation.
• It should also save the calculation history, which makes easy for us to find
difficult math problems.

➢ Relevant process model :

➢ Spiral Model:-

It is an evolutionary process model, is a combination of waterfall model and

iterative process model. Each phase in spiral model begins with a design goal and
ends with a client receiving process .Spiral model was invented by Dr. Barry Boehm
in 1988.
 The development team in spiral model starts with a small set of requirements and
goes through each development phase for those set of requirements. The software
engineering team adds functionality for the additional requirements in every
increasing spiral until the application is ready for production phase. Risk analysis is
the most important criteria considered in spiral model.

➢ Phases in Spiral model:

1.Communication

It involves communication among customer and other stake holders encompasses

requirement gathering to establish effective communication between developer and
customer.

2.Planning

It includes estimating the cost, the schedule and resources for iteration. It also involves
understanding the system requirements for continuous communication between the
system analyst and the customer.

Risk analysis
Its task requires to access both technical and management risks. Identification of
potential risk is done while risk is done mitigation strategy is planned and finalize.

3.Engineering

Engineering tasks required to build one or more representations of the application. It

includes testing, coding and deploying software at the customer site.

4.Evaluation

Evaluation tasks required to obtain customer feedback based on evaluation of the

software representations created during the engineering stage and implemented
during the installation stage.

• Why we used Spiral model?

We used spiral model because:

• Changes in spiral model can be done at a later stage

• Spiral model accommodates life-cycle evaluation, growth and requirement
changes.
• It focuses on early error detection.
• It incorporates prototyping as a risk-reduction strategy.
• It incorporates software quality objectives into the product.
• In spiral model, cost estimation becomes easy as the prototyping building is
done in small fragments.
• In spiral model there is always a space for customer feedback.

➢ Requirements :-
➢ Functional Requirements:

A] Input Requirements-:

The software should not accept the wrong input when provided.

Either it should display the error box for the wrong equation.

The software should accept the scanned equation as well as the typed equation.

B] Output Requirements-:
a. The software should display the appropriate solution of the given equation.

b. It should display the solution by using step-by-step procedure and having

appropriate comment with each line.

c. It should also display the other related solutions for the given equation.

C] Error-:

a. The error in the software should occur when there is a wrong equation entered by
the user.

b. The error message displayed should be simple so that it can be understand by the
user.

➢ Non-Functional Requirements:

A] Performance Requirement-:

Software should work properly instead of the wrong equation is entered

and should not get closed automatically if there is a wrong input provided.

B] Security Requirements-:

Any equation that is to be solved in the software should get stored in the
history management block so if any expression is misplaced then it can be
recovered. And all the personal information entered while login through the user
should not be accessible to any other user.

C] Avability Requirement-:

The software should be available with all the types of equations that are to
be entered by the user, it should also support the mathematical graphs for the
entered equation.

➢ System Requirements:
 A] Hardware Requirements-:

1. Processor- Any Intel or AMD X 86-64 processor with four logical cores
and AV X2 instruction set.

2. Disk- 2.9GB of HDD space, 5-8 GB for a typical installation. A full

installation of a Mathway products may take up to 29MB of disk space.

3. RAM- Minimum 2GB and recommended 4-8GB

4. Monitor- with resolution 1366 X 768 at 60Hz viewable image area

46.9cm widescreen

➢ Software Requirements-:

1. Operating System- Windows 7, Windows 10 or Linux operating system.

2. Language used- JAVA Advanced

3. Front End Language- JAVA script.

➢ Data Flow Diagram :

A Data Flow Diagram is a graphical representation of the flow of data

through an information system.DFD describes the processes that are involved in a
system to transfer data from the input to the file storage and reports generation.

DFD uses defined symbols like rectangles , circles and arrows to show
data inputs , outputs, storage points and the routes between each of the destination.
A DFD is also known as a bubble chart or work flow diagram.

➢ Mathematical Graphs
➢ Solution
➢ Level 1 DFD:
➢ Level 2 DFD:
 ➢ Use case Diagram:

A use case diagram is a dynamic or behavior diagram in UML. Use case

diagrams model the functionality of a system using actors and use cases. Use cases
are set of actions, services and functions that the system needs to perform.

In this context, a “system” is something being developed or operator, such

as a website. The “actors” are people or entities operating under defined roles within
the system. Actors can be a human user, some internal applications or may be some
external applications. Use case diagrams are drawn to capture the functional
requirements of a system.

➢ Decision Table:
 It is a graphical method for explaining the logic of making decision in a
tabular format. It is a matrix representation of logic of decisions which specify the
possible conditions for decision and resulting actions.

It is defined as, “a tabular representations used to describe and analyze

decision situations , where the state of a number of conditions determines the

Conditions Rule 1 Rule 2 Rule 3 Rule 4

Username
T F T F
(T/F)

Password (T/F) T F F T

Login Login Login Login

Output
successful unsuccessful unsuccessful unsuccessful
execution of a set of actions”

➢ Test Cases :

Test cases involves a set of steps, conditions, and inputs that can be used
while performing testing tasks. The main intent of this activity is to ensure whether a
software passes or fails in terms of its functionality and other aspects.

Conditions Rule 1 Rule 2 Rule 3 Rule 4

Username
T T F F
(T/F)

Password
T F T F
(T/F)

Scanned equation Scanned equation Select the proper

Equation
Output does not match to the does not match to the type and scan the
Result
type selected type selected equation
IEEE defines test cases as,” a set of input values , execution preconditions
and expected outcomes developed for a particular objects.
 Expected Actual
C_ID TC_Name Steps Input Data Status
Result Result

Enter
Username in It should It accepted
TC_1 Username alphanumeric “math123” accept the the PASS
alphabets A-Z username username
numbers 0-9

Enter
Password in It should It accepted
Password
Password alphanumeric “system001” accept the the PASS
(T/F)
alphabets A-Z password password
numbers 0-9

After valid
username and It should go It is going
TC_3 Submit password click to the next to the next PASS
on submit page page
button

It should
It shows
remain in
Click on the login page
TC_4 Cancel login page PASS
cancel button with blank
with blank
fields
fields

It should
select the It selects
Equation Click on the Click the clicked the
TC_5 selection particular type appropriate equation equation PASS
box of equation type type and go and go to
to next next page
page

➢ ER Diagram:

An entity relationship diagram shows the relationships of entity sets stored in

the database. An entity in this context is an object, a component of data. An entity
set is the collection of similar entities. These entities can have attributes that define
its properties.
 By defining the entities, their attributes, and showing the relationships between
them, an ER diagram illustrates the logical structure of databases.

An entity relationship diagram is a high level conceptual data model diagram.

ER modeling helps us to analyze data requirements systematically to produce a well
defined database. This diagram represents real-world entities and the relationships
between them.

ER diagram include many specialized symbols, and its meaning makes this
model unique. The purpose of ER diagram is to represent the entity framework
infrastructure. The components used in the ER diagram are entity, entity set,
relationships, attributes, cardinality, ER notations, etc.

Following diagram shows Entity Relationship Diagram of mathematical

equation solving software:

➢ Class Diagram:

A class diagram is a Unified Modeling Language (UML) is a type of static

structure diagram that describes the structure of a system classes, their attributes,
operations , methods and the relationships among objects.
A class diagram gives us an overview of a system by showing its classes and the
relationships among them. It display what interacts but not what happens when they
do interact.

➢ Activity Diagram :

Activity diagram is used to illustrate the flow of control in a system and refer
to the steps involved in the execution of use case. We can model sequentially and
concurrent activities using the activity diagram. So , basically depicts workflow
visually using an activity diagram.

It focuses on the condition of flow and the sequence in which it happens. It

is also known as the behavior diagram as it depicts the behavior of the system.
➢ Sequence Diagram:

A sequence diagram shows object interactions arranged in time sequence.

It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of
the scenario.
 Sequence diagrams are typically associated with use cases realizations in
the logical view of the system under development. This allows the specifications of
simple runtime scenarios in a graphical manner.

➢ State-Transition Diagram:

State-Transition diagram describes all of the states that an object can have,
the events under which an object can have, the states, the conditions that must be
fulfilled before the transition will occur and the activities undertaken during the life of
an object.

These diagrams shows all the possible states of the object and the
transitions that cause a change in the state.
 ➢ Collaboration Diagram:

A collaboration diagram is also known as a communication diagram, is an

illustration of the relationships and interactions among the software objects in the
UML.

This diagram identify the structural elements required to carry out the
functionality of an interaction. A model is the built using the relationships between
those elements. The four major components of collaboration diagram are objects,
actors, links and messages.
 ➢ Conclusion:

Hence, from this project I successfully learn to draw different types of

diagrams like Data Flow Diagrams, Use case Diagrams, Activity Diagrams,
Collaboration Diagrams , Sequence Diagram, State-Transition Diagram, etc and also
learn to classify different requirements based on the software development along
with this I learn to draw the Decision Table and Test Case related to the software.

Thank You