CHAPTER 4

4.1 ARCHITECTURAL DESIGN

The architecture should be developed in such a way that the application's many
components are separated from one another, and each component should focus on a single
purpose. The design must be scalable in order for the system to accommodate an increasing
number of users and data over time. This may entail configuring the system to run across
numerous servers or utilising cloud services that can scale up and down automatically as
needed. The architecture should be built with security in mind to safeguard user data from
unwanted access or alteration. This might include employing secure communication
protocols, encrypting critical data, and creating access controls to limit user access to certain
areas of the programme. The architecture should be built to be adaptable and flexible,
allowing for easy modification or extension as new features or needs are introduced to the
programme. This might include employing modular design concepts, employing design
patterns to make code more reusable, and minimising hard-coded dependencies between
components.

The architecture should be built with security in mind to safeguard user data from
unwanted access or alteration. This might include employing secure communication
protocols, protecting critical data, and creating access controls to limit user access to certain
areas of the programme. To ensure that the application can manage enormous levels of traffic
and data without slowing down or crashing, the design should be tuned for performance. This
might include implementing caching technologies to minimise the amount of database
searches, optimising database queries, and processing data with efficient algorithms.

4.2 DATA DESIGN

The system should protect and encrypt user data such as user IDs, usernames,
passwords, and email addresses. users utilise the complete control full performance to ensure
that hack of users everyday lives . Furthermore, the project dealing with the money app want
to be safe.

34
FIGURE:4.2 DATA FLOW

35
4.3 USER INTERFACE DESIGN

36
4.4 ELEMENTS OF ANALYSIS MODEL

4.4.1 USE CASE AND CASE DIAGRAM

Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do.

FIGURE: 4.4.1 USE CASE DIAGRAM

4.4.2 SEQUENCE DIAGRAM

Sequence diagram and collaboration diagram are called INTERACTION

DIAGRAMS. An interaction diagram shows an interaction, consisting of set of objects and
their relationship including the messages that may be dispatched among them.

A sequence diagram is an introduction that empathizes the time ordering of messages.

Graphically a sequence diagram is a table that shows objects arranged along the X-axis and
messages ordered in increasing time along the Y-axis.

37
 FIGURE: 4.4. 2 SEQUENCE DIAGRAM

4.4.3 ACITIVITY DIAGRAM

An activity diagram is a graphical representation of a workflow or process, showing

the sequence of activities and the flow of information between them. It is commonly used in
software development and system design to model complex processes and workflows.
Activity diagrams typically use flowchart symbols and arrows to represent the steps in the
process and the flow of data or control between them. Each activity or step in the process is
represented by a rectangular box, and the arrows show the flow of control from one activity
to the next. Activity diagrams can be used at various stages of software development, from
requirements gathering and analysis to system design and implementation. They can also be
used to model and improve existing processes in a wide range of domains, such as healthcare,
finance, and manufacturing.

38
 FIGURE: 4.4.3 ACITIVITY DIAGRAM

4.4.4 CLASS DIAGRAM

FIGURE: 4.4.4 CLASS DIAGRAM

39
4.4.5 E-R DIAGRAM

There is no standard for representing data objects in ER diagrams. Each modeling

methodology uses its own notation.

FIGURE: 4.4.5 E-R DIAGRAM

40