general ledger systemgeneralledgersystem.weebly.com/uploads/2/4/1/7/2417… · web viewgeneral...

General Ledger System

CHAPTER III

3.0 Analysis and Design

3.1 Software Requirement specifications

3.1.1 Introduction

The influenced of information system has arose the eagerness of discovering more things

that will make everything easy for client in such different aspects. It only shows that

Information system is not only for business purposes, it can be for personal use or it

depends on the client. It might be different from one another however the objective is to

create a user friendly system example of this is local government unit. This institution has

a lot of transactions and has different departments. In every transaction there must be

supporting documents, where all data are encoded manually and compile the papers, all

department had their own process base on the system. Administrator’s task has becoming

more complex, there have been efforts to improve the effectiveness of the problem

solving and central to this are quantitative and electronic devices such as upgraded

computers and connection. In the field of education, researchers and theorist have

focused intensively in recent years on examining the concepts and use of information

systems to assist administrators and other users. Others have raised and discussed

fundamental issues and uses of general ledger system to facilitate judgment and decision

making in this institution. All the transaction will be systematically organized. The

traditional way of handling documents which is manual encoding and compiling will be

easier than before. Local Government Unit, like in any other organization used to manage

all sorts of data and information to ensure attainment of its goal and objectives. The

emerging needs in most departments under LGU for accurate, relevant data and reliable

information are strengthen the information System. As of today information system is

one of the tools to succeed in modern generation. General ledger system is the

summarization of transaction reports coming from different departments. All the report

being processed in GL is submitted to the audit department.

Local Government Unit 3 - 1


3.1.1.1 Goals and Objectives

This project aimed to create an automated general ledger system that can handle

the entire transaction reports for accounting department. Specific objectives are to

improve the progress of processing the reports on time, to diminish the volume of

paper works of the client, to produce quality system base on the combined

clientele preferences and group decision, to create a user friendly system that can

maximized all the process in to a smooth and systematical way.

3.1.1.2 Statement of scope

The proposed electronic general ledger system will covered the major process of

general ledger of accounting department namely:

Downloading of a supporting document for a specific transaction and extract

it in the system. This will act as a proof of verification and basis of the accuracy

of data inputted.

Transferring of journal entry the transaction data to general ledger system by

hard selections.

Saving to database and generate the ledger reports base on the transaction.

Enable organization to manage their financial process in an integrated manner

by allowing to control over the journal entry process.

Since one of the specific objectives of the proponents is to improve the progress

of processing reports the design system would allow three users accounts which

are the Accountant, Accounting Manager, Admin. Accountant would only access

the downloading of documents and importing files from the other subsystem and

save it while Accounting Manager user account is the one, who had the access on

the entire general ledger system. In addition AM is the one who can register new

user, can open database edit and update. On the other hand Administrator user

account can access every feature design of the proposed integrated system,

meaning admin can access the entire local government unit system which general

ledger is under.



3.1.1.3 Software context

In an organization especially local government accounting department is very

important. This department covered different facilities like accounting for general

funds and property, general journal and general ledger. All of the summary

reports of these facilities for revenue and disbursement will generate in general

ledger. From manual to computerize until January 1, 2002 came, a computerized

has changed into electronics NGAS which has the power to the entire process of

accounting department. One of the features of NGAS is general ledger, a last part

of accounting system where in all types of transaction must be recorded and

create a general report that will be submitted to COA. According to Ms. Gricele a

certified CPA and one of the user of NGAS in general ledger department,

“accounting system is not complete without GL because all of the computation

that have done from the first part which is from budget allotment to release of

funds to distribution of funds are recorded”. To achieve the accrual data being

input must be double check by users and approve before saving to the database.

3.1.1.4 Major Constraints

Things to consider in general ledger:

Completeness of supporting document that required in one transaction.

Computation must be balance.

All documents must be submitted original copy except the cheque and scan.



3.1.2 Usage Scenario

3.1.2.1 User Profiles

The following definitions describe the actors in the system.


Actors DefinitionAdministrator An administrator has the

responsibility for the upkeep, configuration, and reliable operation of computer systems; especially multi-user computers, such as servers.

The system administrator seeks to ensure the uptime, performance, resources, and security of the computers he or she manages meet the needs of the users, without exceeding the budget.

Accounting Manager An accounting manager has the responsibility for establishes financial status by developing and implementing systems for collecting, analyzing, verifying, and reporting financial information; managing staff, maintains financial security by establishing internal controls.

To meet these needs, a system administrator may acquire, install, or upgrade computer components and software; automate routine tasks; write computer programs; troubleshoot; train and/or supervise staff; and provide technical support.

Accountant An accountant has the responsibility for Provides financial information to management by researching and analyzing accounting data; preparing reports.

http://en.wikipedia.org/wiki/Technical_support

http://en.wikipedia.org/wiki/Troubleshoot


3.1.2.2 Use Cases

The following use-cases are the typical interactions between the external

environment and the internal software system. Each use-cases described in section

3.1.2.2.2

1. Log on to system

2. Download the supporting documents

3. View journal entry voucher

4. Select type of transaction and fund

5. Select template/accounting entries

6. Edit particular template for transaction

7. Validate/Saves JEV

8. Generate report

9. Update JEV

10. Add user

11. Deactivate user

12. Access integrated system



Figure 1 Use-case Diagram



3.1.2.2.1 Use Case Diagram

The use case in figure 1 has three actors. First is Accountant: this actor can log on

to system and download all the supporting documents for the proof of the

transaction really exist and extract it in the system. Also this actor can access the

table of other system for journal entry voucher. This actor is the one who transfer

the journal entry to general ledger, validate if the data is accurate and save in the

database. Second is Accounting Manager: this actor can log on to system and do

the task of accountant. However this actor has the access to the entire general

ledger system. The last is Administrator; this actor can log on to system and

administer the entire general ledger system.

3.1.2.2.2 Use Case Descriptions


Use-cases: Log on to system

Primary actor: Accountant

Goal in context: To access the system

Precondition: The accountant has a valid user name and password

Trigger: The accountant needs to access to the system to perform

their job.

Scenario: 1. The system prompts the accountant for log in

user name and password.

2. The accountant enters the user name and

password.

3. The system sends the user name to the web

server.

4. The web server sends back the password

registered to the user name.

5. The system verifies the password and sets the

authorization.

6. The accountant is given access to the system to

perform the job.

Exceptions: The user name and password cannot be verified.

Use-cases: Download


Goal in context: To get the required document of COA.

Precondition: The accountant has view the exact document and

downloads.

Trigger: The accountant needs get the supporting document of

specific transaction in journal entry.

Scenario: 1. The accountant will download the document

as pdf file.

2. The system will send back message to make

sure that the accountant downloading the

right document.

3. The accountant will confirm

4. The system will allow the user to download

the document.

Exceptions: The files cannot post in the table if the allotted time has

reached the limit.



Use-cases: View journal entry


Goal in context: To transfer the journal entry to general ledger

Precondition: The journal entry should be posted on time

Trigger: The accountant needs to get the journal entry on time

and submit to audit.

Scenario: 1. The accountant will transfer the journal entry to

general ledger.

2. Checking of entry base on supporting documents

being downloaded.

Exceptions: The document should be complete

Use-cases: Select type of transaction and fund


Goal in context: To sort the entry according to their chart of accounts

Precondition: The selection of transaction and funds should be




general ledger.

2. Checked if correct save but if return and double

check and save.


Use-cases: Select template


Goal in context: To sort the entry according to their chart of accounts

Precondition: The selection of transaction and funds should be




general ledger.

2. Checked if correct save but if return and double

check and save.




Use-cases: Edit particular template


Goal in context: To distinguished what type of transaction

Precondition: The editing of template needs to be related to chart of

accounts the transaction belong.

Trigger: The accountant needs to edit the template to be more

specific

Scenario: 1. The accountant will edit template

Exceptions: The editing template will not affect the accuracy of

journal entry.



Use-cases: Validate/Save JEV


Goal in context: To save the journal entry voucher

Precondition: The validation will determine if the journal entry

voucher is balance according to the data input and on

supporting documents.

Trigger: If the journal entry voucher is unable to save the

accountant needs to review the entry

Scenario: 1. The accountant will save the journal entry

voucher.

2. The system will send back message if the entry

has discrepancy and not balance, while if none

the system will send back save message.

Exceptions: The system will not accept if the entry is not balance



Use-cases: Generate report

Primary actor: Accounting Manager

Goal in context: To have a hard copy of journal entry.

Precondition: Generation of report is one of COA’s requirements.

Trigger: The accountant will generate report in the last part of

system.

Scenario: 1. The user will generate the report.

2. The system will allow the user.


journal entry.



Use-cases: Update journal entry voucher


Goal in context: To update the journal entry voucher.

Precondition: The Accounting manager only has the authorities to edit

and update the journal entry voucher that already saved.

Trigger: The Accounting manager has the access on the database.

Scenario: 1. The Accounting Manager will log onto the

system.

2. The system will send the log in information to the

web server.

3. The web server will send back the confirmation.

4. The system will allow the accounting manager

update the journal entry in database.

Exceptions: The accounting manager can only access the general

ledger system.



Use-cases: Add users


Goal in context: To add another user

Precondition: The system can allow many user

Trigger: The Accounting manager has the authority of adding

another user in courtesy of new employee in the

department.

Scenario: 1. The accounting manager will send request to the

web server to a add user.

2. The server will send back message of

confirmation.


journal entry.


1.1.2.3 Special Usage Consideration

The supporting document cannot be change.

The document should contain signature of the accountant.

The journal entry must be balance.

1.1.2.4 Activity Diagram


Use-cases: Access in entire integrated system

Primary actor: Administrator

Goal in context: To manage the integrated LGU system

Precondition: The administrator must have the access to all subsystem.

Trigger: The administrator needs to manage the integrated system

to maintain the right order.

Scenario: 1. The administrator can log onto system.

2. The system will allow the user.

3. Access granted.

Exceptions: The integrated system needs t have one administrator.


The following activity diagram below show that occur during a particular use-

case. Figure no. 2 shows the steps taken of accountant logs on to the system. The

access is only granted if the correct user ID and password combination is entered

within the first 3 attempts. After the third attempt the user ID will be locked out

and the system will turned into shutdown. The user that cause of shutting down of

system will no longer access the system on succeeding log on, the administrator

needs to log on to reboot the system.

In figure no 3 are steps taken in downloading of supporting documents. The

accountant can only download document only if it is already posted in the journal

form.


Prompt for user ID and password

Enter the user ID/password

Verify password

Access granted

Check of bad entry

Locked user and system will shutdown

[Correct]

[Incorrect]

[3xattempts]

Figure 2 Activity diagram of logging on to system

Log on to system activity diagram

Accountant will download the posted document of each

department


Figure 4 shows the steps taken in viewing of JEV. The document posted of the

journal form will extract to general ledger.


System will automatically save the documents as bad entry

Extraction of downloaded document

Preview of documents for analyzation

Save document to database

Downloading of supporting document of JEV

Figure 3 activity diagram of downloading supporting document

View posted JEV

Bad entry table


Figure no. 5 shows the steps taken in selection of template that exactly match to

the specific transaction of journal entry voucher and the validation of journal

entry. A selection of template is responsibility of accountant and this will occur if

the JEV is extracted to the general ledger. If the entry is incorrect the system will

prompt the user and data will not save.


Compare the supporting document to the JEV

Transfer JEV to general ledger by hard selection

Select of transaction General funds/others

Viewing of JEV/Selection of transaction

Figure 4 Activity diagram of viewing JEV and selection of transaction

Select transaction between general funds/others

Check bad entry

Save to other table

[Incorrect]


Figure 6 show the generation of reports. A general ledger reports coming from

JEV.


Choose from chart of accounts

Edit particular template

Validate the journal entry

Save to database

[Correct]

[Incorrect]

Selecting template and Validate JEV

Figure 5 Activity diagram of selecting template and validate JEV

Saving JEV to database


1.1.3 Data Model Descriptions

3.1.3.1 Data Objects

Bookkeeper Data Object


View general ledger sample form

Analyzed general ledger

Generate Report

Generate general ledger report

Figure 6 Activity diagram of generating general ledger report


Bookkeeper ID: a unique id number given to employee to identify what

department.

Bookkeeper Name: a JEV must have the name of encoder for the record of the

system.

Transaction Data Object

Transaction Name: every transaction has named to help the accountant identify

the documents.

Type of transaction: to identify if general fund or others

Date of transaction: to identify what date posted.

Time of posted

Reports Data Object

Balance sheet: summary of financial balances of departments. Annual generation

of reports

Income Statement: summary of income statement of department, annual

generation of reports.

General Ledger: summary of daily transaction.

Accounting Staff Data Object

Employee ID: a unique identifier given to accountant to access system.

Employee Name: to locate the accountant who validate the JEV of different

department and for the record of the system

Employee Information: for the record of other department.

Accounting Manager Data Object



Employee ID: a unique identifier given to accounting manager to access the

system.

Employee Name: for the record of the system

Employee information: address and contact number for the record of system

3.1.3.2 Relationships

In order to start transaction there should a journal entry to be process. This part

will discuss the relationships of data object to one another.

A Bookkeeper is a borrowed entity from other department, in every Bookkeeper

there are many transaction. The relation between bookkeepers is many is to many.

In department there is one accounting manager the relationship between

accounting manager is one to many.

All transaction needs to be noted this must have transaction name, transaction

type, date and sets of document that general ledger required to submit. In every

transaction there is one accountant, the relationship between accountant and

transaction is one is to many.

A report is the summary of balance sheet and income statement that will come

from general ledger. In every transaction there should be report, the relationship

between transaction and report is one is to one.

An accountant is the one who act the process of general ledger, In every

transaction there is one accountant, the relationship between transaction and

accountant is one is to many. The relationship between accounting manager and

accountant is one is to many.

1.1.3.3 Complete Data Model

The relationships between the data objects describe in 3.1.3.2 shown in figure 7




Figure 7 Relationship diagram of Automated General Ledger System


Figure 8 Entity Relationship Diagram of Automated General Ledger System

3.1.4 Functional Model Description



3.1.4.1 Class Diagram

The transaction between the different classes are shown below in figure 8 the

action to get a set of private data attributes have been eliminated.

Figure 9

Class Diagram of Automated General Ledger System


General Ledger System Class Diagram


3.1.4.2 Software Interface Description

3.1.4.2.1 External Machine Interfaces

The system will be connected to printer for the printing of supporting

documents and others. In addition to this system has cable connector such

as: UTP cable from modem to the server computer and other units.

3.1.4.2.2 External System Interfaces

General ledger is a summary of all report such as: Balance sheet, Income

statement and Ledger this report are coming from different departments.

Therefore the general ledger system will be connected to the other

department system to download the supporting document and extract

posted entry of bookkeepers.

3.1.4.2.3 Human Interface

The system will allow the user to complete navigation using keyboard and

mouse.

3.1.4.2.4 Reports

General Ledger Reports

Supporting Document Reports

Balance sheet through excel files.

Income Statement

Statement of cash flow

Owner’s Equity



3.1.5 Behavioral Model Description

3.1.5.1 Description for Software Behavior

3.1.5.1.1 Events

Accountant Class Events

Accountant will log on to system

Open the JEV posted of other department

Download supporting document

Bookkeeper Class Event

Bookkeeper will post JEV entry

Bookkeeper will post name and ID

Identify if Disbursement/Revenue

View JEV Class Events

Accountant will view JEV posted

Analyze the posted JEV

Compare with supporting document

Extract to general ledger

Select Template Events

Account will choose between general funds/other funds

Choose from chart of accounts

Edit the template which is exactly right for transaction



Validate JEV

Accountant will analyze JEV

Save the JEV to general ledger

If incorrect return to view JEV

Analyzed again and save

3.1.5.1.2 States

Bookkeeper Description

Posting: Department will post the daily transaction

Department Info: Department ID number and name must be included

in posting

Type of transaction: Disbursement/Revenue

Accountant State Description

Log on: The accountant will log onto the system

View files: The accountant will view the posted document

Download: Download the posted supported documents

Extract files: Extract the documents

View JEV Description

Data: Journal entry voucher

Journal Info: JEV number, JEV transaction name

Type of funds: General funds/Others



Selection template Description

Transaction Type: Choose from chart of accounts

Edit: Edit Template to make it more detailed

Validate JEV Description

Requirements: Needs to meet all the requirements

Journal entry: Needs to be balance.

Save GL: Save general ledger if requirements is complete and

balance.

Generate Report Description

Report: Generate general ledger report and supporting

document.

Accounting Manager Description

Log onto system: Accounting manager needs to log onto system.

Manage GL: Manage general ledger system.

Add user: Accounting manager can add user.



3.1.5.2 Statechart Diagram



Figure 10 State chart Diagram of Automated General Ledger System

3.1.6 Restriction, Limitation and Constraints

The system is unable to delete accounts/transaction.

The system is in capable of saving bad entries posted of other departments.

Not balance JEV is not accepted in general ledger system. The system is programmed

to generate ledger report all computation should take over by each department.

The system shall integrate within the other department such as sharing of database

management systems.



System Rules

1. Boundary rules

1.1 Entity rule: distinguish clearly what concerns the firm and what does not. Do

not mix up transactions which engage the firm as its ownership over things.

1.2 Periodicity rule: prepare the final documents on a regular basis, posting

journal entry before deadline and in generating reports monthly, quarterly and

annually.

1.3 Going concern: record all transactions with the assumption that the firm will

exist forever, and there always will be more transactions in the future.

1.4 Quantitative rule: record only quantifiable information in the accounting

system.

2. Measurement Rules

2.1 Monetary measurement: everything is recorded in monetary units, and the

same monetary unit.

2.2 Realization rule: it is an important rule which concerns the date of a

transaction, and therefore to which accounting period it belongs.

2.3 Matching rule: again, an important rule. All the transactions must be

balanced and declared accordingly. The explanation of every particular with

respect to the chart of accounts must be well organized.

2.4 Dual aspect: it simply says that a transaction involves two accounts, one will

be debited, and another one will be credited. It is the technical translation of the

fact that a transaction is made of two movements of value, most usually one

leaving the firm, and one entering the firm.



2.5 Materiality rule: we create different accounts to distinguish expenditures or

assets or liabilities of different nature, but we don't create new accounts for

insignificant things, we treat them as a lump quantity.

3. Ethical rules

3.1 Prudence rule: surprisingly enough there are transactions where we have the

choice of how to record them (this is the case, for instance, of passing provisions).

The rule says: when you have a choice between several recording methods,

choose the one that minimizes the profit. That way we are prudent.

3.2 Consistency rule: when we have adopted one accounting way to treat such

and such transaction, we should stick to the same way in the subsequent periods.

It is important, because one of the functions of the accounting system is to show

the evolution of the firm from one year to the next. If we change the accounting

procedures, we end up with figures which are not comparable.

3.3 Relevance rule: put only relevant information in the accounting documents

and their accompanying appendices.

3.1.7 Validation Criteria

Software validation may vary base on the end users command.

3.1.7.1 Classes of Test

User

Generation of reports

Normalization of database

Subsystem integrations



3.1.7.2 Expected Software Response

The system should response the appropriate error may occurred during testing.

In order to be familiarized the group although it is a small thing.

3.1.7.3 Performance Bounds

The system should accommodate the entire user in testing and may remain in

good performance until the given time.



1.2 Software Design Specification

3.2.1 Introduction

The influenced of information system has arose the eagerness of discovering more things

that will make everything easy for client in such different aspects. It only shows that

Information system is not only for business purposes, it can be for personal use or it

depends on the client. It might be different from one another however the objective is to

create a user friendly system example of this is local government unit. This institution has

a lot of transactions and has different departments. In every transaction there must be

supporting documents, where all data are encoded manually and compile the papers, all

department had their own process base on the system. Administrator’s task has becoming

more complex, there have been efforts to improve the effectiveness of the problem

solving and central to this are quantitative and electronic devices such as upgraded

computers and connection. In the field of education, researchers and theorist have

focused intensively in recent years on examining the concepts and use of information

systems to assist administrators and other users. Others have raised and discussed

fundamental issues and uses of general ledger system to facilitate judgment and decision

making in this institution. All the transaction will be systematically organized. The

traditional way of handling documents which is manual encoding and compiling will be

easier than before. Local Government Unit, like in any other organization used to manage

all sorts of data and information to ensure attainment of its goal and objectives. The

emerging needs in most departments under LGU for accurate, relevant data and reliable

information are strengthen the information System. As of today information system is

one of the tools to succeed in modern generation. General ledger system is the

summarization of transaction reports coming from different departments. All the report

being processed in GL is submitted to the audit department.



3.2.1.1 Goals and Objectives

This project aimed to create an automated general ledger system that can handle

the entire transaction reports for accounting department. Specific objectives are to

improve the progress of processing the reports on time, to diminish the volume of

paper works of the client, to produce quality system base on the combined

clientele preferences and group decision, to create a user friendly system that can

maximized all the process in to a smooth and systematical way. There are several

goals for which the software is developed such as:

Accurate

Efficient

Reduce complexity

3.2.1.2 Statement of Scope

The proposed electronic general ledger system will covered the major process of

general ledger of accounting department namely:

Downloading of a supporting document for a specific transaction and

extract it in the system. This will act as a proof of verification and basis of

the accuracy of data inputted.

Transferring of journal entry the transaction data to general ledger system

by hard selections.

Saving to database and generate the ledger reports base on the transaction.

Enable organization to manage their financial process in an integrated

manner by allowing to control over the journal entry process.

The system will borrow most of information needed to be generated such as:

Bookkeeper record

Journal entry record

Supporting documents in every journal entry record

Statement of cash flow

Local government’s equity

Balance sheet



Major inputs

Bookkeepers name, ID number

Upload supporting documents

Post journal entry

Accountant name, ID number, Address, Contact number

Accounting Manager name, ID number, Address, Contact number

Transaction name, Type, Date, Time

Select transaction

Edit template

Validate journal entry

Save entry

Report name, Type, number / folio number

Processing Functionalities

Function Priority

Bookkeeper information entry Essential

Supporting document entry Essential

Journal entry Essential

Accountant information entry Essential

Accounting Manager information entry Essential

Transaction information entry Essential

Funds information entry Essential

Chart of account entry Essential

Template entry Desirable

Validate journal entry Essential



Bad entry Desirable

Good entry Essential

Generation of report entry Future requirements

3.2.1.3 Software Context

The automated general ledger system is awfully proficient one. These maintain

the normalization of database to avoid shuffle of data. In additional this system is

less expensive as well as complexity is reduced just the way the clientele

requested. In this system the group will use java netbeans and MySQL.

3.2.1.4 Major Constraints

The system should be accurately connected to the server to access database. The

must be good enough to perform all the actions fast for instance in generation of

monthly reports, in saving journal entry to database in an ample of time. To

completely experience advantages of this system the clientele should follow the

required unit of computer as well which is describe in subsequent section.

3.2.2 Data Design

As the application is being build in java, MySQL the overall design can be

categorized into three parts based on the above mentioned application developing

language.

a. Graphical User Interface

Java Netbeans is being used for the development of the front end GUI. The GUI

components provisionally stores the keyboard input by the users till it is being

used by the functional procedures. More explanation of the overall GUI and its

component is available in section 4 of the document.



b. Back End Data

The group decided to use MySQL for database management system at the back

end for storing all information in the form of tables. This table will entirely

available to all the internal procedure of LGU system. The DBMS system will

be locally available on the machine or server where the application is running.

c. Internal Function Procedures

Java Netbeans will be used to create the front end GUI and MySQL for the

database and MySQL connector 4.0 for the connection of GUI and database.

This will connect the JNB and database, a compatible version for both

languages to secure a fast and reliable connection.

3.2.2.1 Internal Software Data Structure

In this part the internal software data structure will start from posting of JEV

of other department to the AGLS, the data will be save straightly to database

as bad entry until the time it is not extracted to AGLS. The user of AGLS will

be use major selection and inputs as well for add edit and update of files. For

accessing and viewing of the table the data is being fetched directly from

DBMS to the java netbeans to display directly on the screen. For the reports

printing there are codes and variables have been defined and declare in the

procedures and then print the report after finished.

3.2.2.2 Global Data Structure

Database is the only kind of data structure that available on the entire system.

It stored in MySQL. After the MySQL connection any data stored can be

fetched, update.

3.2.2.3 Temporary Data Structure

The AGLS does not use any temporary files of its own. As data is being

posted in the system it is directly send to database as bad entry. This will

remain in the bad entry table until the command “edit” is being executed in

the SQL query by the application.



3.2.2.4 Database Description

Below are mentioned all tables, their corresponding attributes and description

of each.

Table Name: Accounting Staff

Attributes: Employee ID, Employee name, Employee contact no

Description: This table is borrowed from payroll system. It holds the general

information of all employees who worked in city hall.

Table Name: Accounting Manager

Attributes: Employee ID, Employee name, Employee contact no, Employee

address



Table Name: Bookkeeper

Attributes: Employee ID, Employee name, Department name



Table Name: Transaction

Attributes: Transaction name, Transaction type

Description: This table is the chart of accounts.

Table Name: Source Document

Attributes: Document name, Department name

Description: This table is the bad entry where in all the JEV posted in AGLS

will be automatically saved.



Table Name: Reports

Attributes: Report type, Report name

Description: This table is for all kinds of report that AGLS generated.

3.2.3 Architectural and Component Level Design

3.2.3.1Architectural Diagram

This diagram below shows the various actors are accounting manager,

accountant and admin who will use the system. The subordinates systems that

will be used by the software are the database (MySQL) and Java. Also MySQL

connector. Maintenance system is important, which needs the software for

testing and maintenance purpose.

Figure 11 Architectural Context Diagram


Architectural Context Diagram


Call and Return Architecture

These diagram below show the call and return architecture for the general ledger software

system.

Figure 12 Call and Return Architecture


Call and Return Architecture

general ledger systemgeneralledgersystem.weebly.com/uploads/2/4/1/7/2417… · web viewgeneral...

Documents