Java-Based ERP System: Architecture, Interface, and Class Design

Verified

Added on  2025/04/28

|17
|2049
|445
AI Summary
Desklib provides past papers and solved assignments for students. This project details the design and development of an ERP system.
Document Page
ENTERPRISE RESOURCE PLANNING
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Table of Contents
Introduction......................................................................................................................................3
System architecture..........................................................................................................................4
Interface screen................................................................................................................................5
Java classes....................................................................................................................................11
Classes.......................................................................................................................................11
Conclusion.....................................................................................................................................13
References......................................................................................................................................14
List of Figures
Figure 1: ERP system architecture..................................................................................................4
Figure 2: Welcome page..................................................................................................................5
Figure 3: Welcome administrator....................................................................................................6
Figure 4: Sign up page.....................................................................................................................6
Figure 5: Login page........................................................................................................................7
Figure 6: Forgot password page......................................................................................................7
Figure 7: Login using OTP..............................................................................................................8
Figure 8: Admin profile page..........................................................................................................8
Figure 9: User profile page..............................................................................................................9
Figure 10: ERP hierarchy structure...............................................................................................12
Document Page
Introduction
In this progress report, we will discuss and determine various ways and methods to develop an
efficient ERP system. Firstly, we will discuss and determine a system architecture for our ERP
system. Later we will analyze the significance of the system architecture. To perfectly discuss
the need and functions of this ERP system we will build a hierarchy structure so that we can see
how the software application will work.
Document Page
System architecture
A system architecture is a graphical representation of any system. A system can be of any type
like booking system, hospital management system, scheduling system. The system architecture
gives the user an overview of the respective system. It contains various entities like
administrator, user, server, database, etc. when these entities are combined together in a
structural format then it describes a system architecture (Crawley, 2015).
In this section, I have designed a system architecture for an ERP system. ERP stands for
Enterprise Resource Planning, which is used in organizations like schools and colleges where
there are several tasks and schedules to be managed and various actors are also involved in the
system. If we look at the overall concept of ERP system and integrate it with system architecture,
we can see that, for a basic ERP system there has to be only a three-tier architecture and those
three layers are as follows: Client layer, server layer, and presentation layer. The client layer is
considered to be responsible for entities like admin or administrator, student or faculties (in case
of any educational institute), etc. there is also another layer called view layer which helps in
designing and determining the GUI part of any software-based application. The view layer has
components like Buttons, Text fields, Labels, radio button, etc.
Figure 1: ERP system architecture
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Interface screen
The interface is the connection between the user and the software. Interface plays a very vital
role in case of proper software management development. The interface is the creative section of
the software that provides a face to all the functionality of the software. There are many classes
in ERP management, so the best way to build interactive software that is easy to use is by
creating a user-friendly interface.
For this ERP system we have the following:
Login page
Sign up page
Welcome page
User profile page
Administrator profile page
Change password
Admin welcome page
Login using OTP or One Time Password
Generating OTP or One Time Password
The first page is the Welcome page, which will ask the user their type of account which means
whether they are an admin or general user. This page has to be created so that the type of user
account can be differentiated. There are various attributes used in this page like the label , radio
button and buttons for proceeding and EXIT.
Figure 2: Welcome page
If the user chooses admin type account then that will take him or her to welcome admin page
which will ask him how they want to proceed. At this page there will be two options first is to
sign up for a new account and second is for logging into an existing one (Jackson, 2016).
Document Page
Figure 3: Welcome administrator
If the user chooses to sign up option then this page will redirect it to the sign-up page which will
contain a form that has all the required field for any new admin account. For this page, there are
attributes like label, button, text field, account type as a combo box. , etc.
Figure 4: Sign up page
Document Page
If the user has already had an existing admin or general user account then they will redirect to the
login page. The login page will ask the user for their email id and password so that they can get
logged into their account. This page has attributes like a label for showing position of email and
password and for entering the value of this field I have provided text field attribute. We also have
to consider the case where the user no longer remembers their password. In that case, there is a
dedicated button called forgot password which will take the user to a separate page.
Figure 5: Login page
Now we have the forgot password page. In general term, we have this page in case the user
forgets his or her password. This page will ask the user their registered mail id and contact no.
and will send them an OTP or also known as One Time Password which they can use later on to
login into their account (Noguchi, 2017).
Figure 6: Forgot password page
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
After sending the user OTP the page will automatically redirect to a page where the user can the
generated OTP to login to their account.
Figure 7: Login using OTP
After the user has successfully logged into their account, they will be shown a profile page.
Depending on their account type there will be two different types of profile page, one is for an
admin profile page and other is for the general user profile page. This page contains attribute
label, table, text field and button for change password (Savitch, 2017).
Figure 8: Admin profile page
Document Page
Figure 9: User profile page
There is also an option to change password, it will redirect the user to a page where they can
change their password (Madanhire, 2016).
Document Page
This page will help the user to change their password if they want.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Java classes
Classes
This ERP system has many functions and classes which can be used by the user to make the
software more interactive and easier to use for the user. A very important part of OOP’s is the
use of class for various functionalities. Classes have objects and methods, and in any Java-based
program, we have to create an object of the class to call any method of the respective class.
In this Java-based ERP system we have many classes which are as follows:
Login page
Sign up page
Welcome page
User profile page
Administrator profile page
Change password
Admin welcome page
Login using OTP or One Time Password
Generating OTP or One Time Password
In order for these classes to be functional, methods have to be declared so that we can determine
what class can perform which function. In object-oriented programming, functions are called as
methods which are no different other than their name (Altamony, 2016). There are two main and
common method of any Java application which are run() and components().
Classes Field
Login page Label, text field, button
Sign up page Label, text field, combo box, button
Welcome page Label, button, radio button
User profile page Label, combo box, table, text field, button
Administrator profile page Label, combo box, table, text field, button
Change password Label, text field, button
Admin Welcome page Label, button
Login using OTP Label, text field, button
Generating OTP Label, button, text field
Document Page
Figure 10: ERP hierarchy structure
The above is a hierarchy structure of this ERP management system. This describes the
relationship between any and every page in our ERP system. There are many relationships like
one to one, one to many, many to one and many to many (Seethamraju, 2015).
chevron_up_icon
1 out of 17
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]