Chapter four

System analysis and design

4. introduction
Designing an online tax management system requires a thorough analysis of the requirements and
needs of the system's stakeholders. The system should be designed in a way that is user-friendly, secure,
and able to handle large volumes of data efficiently.

the system's requirements are analyzed to identify any potential problems and develop solutions.

This includes determining the system's architecture, the types of databases that will be used, and the
types of interfaces that will be required.

the system is designed to meet the stakeholders' requirements. This includes designing the user
interface, the system's database structure, and the different modules that will be required.

4.1 these are the following functions of Systems Analysis and design:

• identifying the users of the system, their roles, and the tasks they need to perform.

• defining the system's components, interfaces, and data flows.

• security measures to ensure the protection of sensitive tax information.

• coding the software, integrating different components, and testing the system to ensure it functions as
intended.

Major futures of the system

Our system allows taxpayers to register themselves and provide their personal and financial
information.

Our system allows users to electronically file their tax returns with the appropriate government
agencies. This eliminates the need for paper forms and saves time and money

Our system can provide a mechanism for taxpayers to pay their taxes online. This could include support
for various payment options such as credit/debit card, online banking, and e-wallets.

Our system able to calculate taxes automatically based on the taxpayer's income, expenses, and other
relevant factors.

Our system can provide automatic notifications to taxpayers regarding upcoming tax deadlines, tax
payments, and other relevant information.
4.2 Figures of online tax management system
4.3 UML diagrams

UML stands for Unified Modeling Language; The UML is the standard language for visualizing,

specifying, constructing, and documenting the artifacts of a software- intensive system. It

can be used with all processes, throughout the development life cycle, and across different
implementation technologies

4.3.1Modeling

Unified Modeling Language (UML) Models represent systems at different levels of detail.

Some models describe a system from a higher, more abstract level, while other models provide

greater detail.

UML models contain model elements, such as actors, use cases, classes, and packages, and

one or more diagrams that show a specific perspective of a system. A model can also contain

other, more detailed models.

4.3.2 Diagrams

UML has many Types of Diagrams which are divided into two categories:

• Structure Diagrams

o Class Diagram

o Deployment Diagram

• Behavioral Diagrams

o Use Case Diagram

o Activity Diagram

o Sequence Diagram

4.4 Use case diagram

A use case diagram shows a set of use cases and actors (a special kind of class) and their

relationships
4.5 Activity Diagram

Activity diagram are graphical representations of workflows of stepwise activities and actions

with support for choice, iteration and concurrency.

In the Unified Modeling Language, activity diagrams are intended to model both computational

and organizational processes.

4.6 class diagram

A UML class diagram is a type of diagram that depicts the structure of a system by showing the classes
of objects within it, their attributes and operations, and the relationships between them.
4.7 sequence diagram

A sequence diagram is a type of UML (Unified Modeling Language) diagram that shows interactions
between objects or components in a system in a specific time sequence. It is used to illustrate the flow
of messages between objects and to visualize the order of the interactions.

This is a sequence diagram for an Online Tax Management System. The diagram depicts the interactions
between the user, the web server, and the database during the process of logging in, filing tax returns,
and logging out.

The sequence starts with the user sending a request to login to the web server. The web server queries
the database to retrieve the user's credentials and returns the user data to the web server. The web
server then sends the login page to the user.

The user enters their login credentials, and the web server verifies the credentials by querying the
database. The database returns the verification result to the web server, and the web server sends the
dashboard page to the user.

The user then requests to file their tax return, and the web server retrieves the user's tax data from the
database. The database returns the tax data to the web server, and the web server sends the tax filing
form to the user.

The user submits the tax filing form, and the web server stores the tax filing data in the database. The
database returns the status of the filing to the web server, and the web server sends the filing status to
the user.

Finally, the user logs out, and the web server ends the user session by querying the database. The
database confirms the session has ended, and the web server sends the logout page to the user.
 4.8 state diagram

A state diagram, also

known as a state
machine diagram, is a
type of behavioral
diagram in software
engineering and
computer science that
depicts the various
states that an object,
system, or process can
go through and the
transitions between
them.

This diagram has five

states: Login,
Dashboard, View Tax,
Edit Tax, and logout,
which is the initial
state. The arrows
represent the
transitions between
states, and the labels
on the arrows describe
the events that trigger
the transitions

4.9 deployment
diagram

A deployment diagram
is a type of UML (Unified Modeling Language) diagram that shows how software components are
deployed or distributed across hardware nodes and networks. It is used to model the physical
deployment of software components in a system.
In a deployment diagram, nodes represent hardware devices or software environments, while
components represent the software elements that are deployed on the nodes. Connections between
nodes indicate the communication paths between the different elements of the system.

.
4.10 Database design
4.11 Entity Relationship Diagram

Entity Relationship Diagram (ERD) is a type of diagram that lets you see how different entities ( people,
customers, or other objects) relate to each other in an application or a database.

They are created when a new system is being designed so that the development team can understand
how to structure the database. They can also be created on an existing system to help the team
understand how the system works and to find and resolve any issues.

Entity Relationship Diagrams use a specific set of symbols, such as shapes and arrows, to depict the
system and database.

Erd symbols

Entity: An entity is a distinct object or concept in the real world that is represented in the database

Attribute: An attribute is a characteristic or property of an entity. It describes the data that can be
stored for an entity.

Relationship: A relationship represents an association or connection between two or more entities. It

describes how the entities are related to each other. Relationships can be one-to-one, one-to-many, or
many-to-many.