CHAPTER THREE

METHODOLOGY

3.1 Introduction

This chapter provides a detailed analysis of the existing system, assessing its strengths,

weaknesses, and the challenges faced. A new system is proposed to address these limitations,

offering enhanced functionality to overcome the identified weaknesses and improve overall

efficiency. This chapter also describes the methodology employed in this research.

3.2 System Analysis

System analysis is the process of studying a procedure or business to identify its objectives and

purpose, with the aim of designing systems and procedures to achieve them efficiently. The

primary objective of the system analysis phase is to specify the functional requirements needed

to meet user demands. In the system design phase, these specifications are translated into a

structured hierarchy of diagrams that outline the necessary data, and the processes required. This

structured approach allows for the creation of comprehensive instructions that can be

implemented within a computer program. Many information systems today are developed using

generic software rather than custom-built programs.

3.3 Database-Related Concepts

3.3.1 Database

A database is a collection of related data organized for easy access, management, and updating.

Data consists of facts and figures that can be processed to produce meaningful information. For

instance, data elements such as a student’s name, age, gender, class, and subjects can serve as

records for various purposes. Data represents information that, when processed, yields insights

and actionable information. For example, analysing student scores allows one to identify top
performers and calculate average marks. A database management system (DBMS) stores and

organizes data, making it easier to retrieve, manipulate, and generate valuable insights.

3.4 Web Technology-Related Concepts

3.4.1 PHP: PHP is a widely used general-purpose, server-side scripting language primarily

designed for web development to create dynamic web pages. PHP code can be embedded within

HTML and is processed by a web server equipped with a PHP module. This setup enables the

generation of interactive and dynamic content for users. Standard PHP delimiters (e.g., <?php ...?

>) allow PHP code to be seamlessly integrated with HTML, maintaining a structured document

format that adheres to XML standards (Michele, 2006).

3.4.2 MySQL: MySQL is one of the most popular open-source database applications, commonly

paired with PHP for web development. It includes a database server for data storage, various

client applications for database interaction, and several utilities. MySQL employs SQL

(Structured Query Language) for querying and managing data, with syntax that is both easy to

learn and highly functional. MySQL can be used on various server setups, such as WAMP

(Windows, Apache, MySQL, PHP) for Windows or LAMP for Linux, allowing flexibility

depending on the operating system (Michele, 2006).

3.4.3 JavaScript: According to Learning JavaScript: Better Interactive Design and Web

Development with Simple JavaScript Techniques by Kevin Svedberg and Jonathan Chaffer,

JavaScript is a powerful tool for enhancing website interactivity. Created by John Resig,

JavaScript is an open-source project supported by a team of expert developers, offering features

that are intuitive to learn and apply. Its robust cross-platform compatibility and compact syntax

make it ideal for dynamic web applications.

3.5 Fact-Finding Techniques (Requirements Gathering)

Various methods are employed to gather data and information for research purposes. In this

system, Gantt charts are utilized for progress tracking, while data collection methods focus on

reviewing existing records and documents relevant to the Casual Wages at the Consultancy Unit

of University of Maiduguri, Department of Computer Science. Key focus areas include employee

payment procedures, overtime calculation, and deduction processes. Relevant documents

reviewed include employee overtime schedules, deduction records, payroll information, and

attendance records, which help identify inefficiencies in the current system.

3.6 Software Development Methodology

Several software development life cycle models are available, including Waterfall, Incremental,

Rapid Application Development (RAD), Spiral, Prototype, Object-Oriented, Fountain, and Code-

and-Fix models. This research adopts the Waterfall model.

3.6.1 Waterfall Model

The Waterfall model, introduced by Royce in 1970, is one of the earliest and most systematic

software development models. It organizes the software development process into a sequential

series of phases that cascade from one to the next, resembling a Gantt chart. Each phase is

completed and validated before moving to the subsequent phase, making it ideal for projects

where requirements are clearly defined and stable.

3.4.3 JavaScript: According to the book learning JS: Better interactive Design and Web

Development with Simple JavaScript Techniques by Kelvin Svedberg and Jonathan Chaffer.

JavaScript is a powerful JavaScript library that can enhance your websites regardless of your

background. Created by John Resign, Query is an open-source project with a dedicated core team

of top-notch JavaScript developers. It provides a wide range of features and easy to learn syntax,

and robust cross-platform compatibility in a single compact file.

3.5 Fact Finding Techniques (Requirement Gathering)

There are many methods of gathering data with respect to acquiring information about a research

work. In this system the techniques that will be employed is Gantt Chart for figuring the Progress

Report and Steps to achieve on the system and for Data Collections. For this ‘research work’, the

techniques relied upon in this research is the reviewing of the existing records and documents,

but still some other techniques are considered.

3.5.1 Review of Existing Documents

Relevant documents were reviewed and details pertaining to the various activities of the Casual

Wages at Consultancy Unit of University of Maiduguri, Department of Computer Science with

special attention to the payment of the Casual Staffs, Overtime and deduction were obtained.

Such activities include working condition, work force, bottlenecks, and gridlocks. Documents

reviewed include the Overtime, Schedule of the Staff, Deduction of Salary, Cash Advance,

Employee List and Attendance of the Employee which clearly shows the problem of the existing

format being used.

3.6 Software Development Methodology

Some examples of software development life cycle models are Waterfall, Incremental, Rapid

Application Development (RAD), Spiral, Prototype, Object Oriented, Fountain, and Code-and-

Fix Models. This research follows the Waterfall model.

3.6.1 Waterfall Model

This is the oldest model among the software development models introduced by Royce in 1970

and by mere observation it works like a Gantt Chart. It is a classic life cycle model that describes

a systematic sequence of activities in a software life cycle. It is called waterfall model because of

the cascade from one phase to another. Each of the activities in the waterfall model provides
feedback to developer responsible for earlier activities. The waterfall is applied because the user

requirement and their implementation as well defined and understood and are reasonably stable.
 Figure 3.1: Waterfall Model

3.6.2 Logical Modelling using UML

UML Class diagrams illustrate the system's classes, their interrelationships, operations, and

attributes. Use Case diagrams serve a wide range of purposes, including conceptual or domain

modeling as well as detailed design modeling, with an important consideration being the

appropriate level of detail. Arguably, the Class diagram is the most frequently used UML

diagram. Its purpose is to define the structural composition of the system, including class

relationships, attributes, and behaviors associated with each class. To effectively use Class

diagrams as communication tools, developers must share a consistent understanding of how the

elements displayed in a Class diagram translate into an object-oriented programming language

such as PHP."
3.6.3 Unified Modelling Language (UML) Diagram of the System

Figure 3.1: Showing the UML Diagram of the System

Administrator Activities: The administrator performs various activities as illustrated in the

diagram above. These include logging in, registering casual workers, and displaying the list of

registered staff. The administrator can also apply a flat overtime charge to each worker's wages,

make deductions for lateness or other reasons, and add cash advances as needed. Additionally,

the administrator can enter the position of casual staff members, set up working hour schedules,

and generate reports such as payslips, wages, and lists of casual staff. Lastly, the administrator

can receive SMS or email notifications once casual worker signed in for the day.

Casual Workers Activities: In this module the casual staff can only clock-in/clocked-out for

that day and show him notification of signing out.

3.6.4 Entity Relational Diagram

Figure 3.1: Entity Relational Diagram.

3.6.5 Flowchart of the System

 Figure 3.1: Showing the Flowchart of the System

3.7 Study of the Current System

Presently, the system in use is manual method, using a hand cash give. Any Casual Workers of

University of Maiduguri, Department of Computer Science must be charge manually including

their Wages Salary, Deduction, Overtime or even their work time are schedule manually because

of manual means used at the organization. The necessary fees and builds within some period,

certain amount as shares and savings respectively. The organization operates both the monthly

salary and Wages salary especially the consultancy unit, specialized on the Wages Payment to

their Casual Workers to which it results to a lot of stress, wages payment are made available

through the units in charge of the disbursement of the Wages to their Casual Workers. There are

difference mode in the wages payment to casual workers to which depends on how many hours

the casual staff works will be paid, this means that the payment of this fund depends on your

arrival time and closing time which the system will now figure out the numbers of hours of

which you work for, if the casual staff arrived late there is charges the system deduct from the

wages to be paid and if the casual workers works with overtime there is flat charges added to

his/her payment. The system generates report of each Wages to be paid for each labourer and

fixed a gross-rate, and Net-pay to the amount with the taxes. All correspondences and records are

kept on paper in files and folder and/or through the computer files system.

3.7.1 Problems with the Existing System

The current Cooperative management system has the following weakness:

i. Report generation seems to be very difficult.

 ii. Bias and selfish interest play role in loan disbursement.

iii. The system is not efficient and wastes valuable resources.

iv. It cannot deliver accurate, and prompt required information.

v. Its financial calculations are prone to errors as such leads to problems from the deductions

made.

vi. The system is not secured enough because records can be tempered with easily.

vii. There is no organized database, as such; there is data redundancy, data inconsistency,

lengthy development time and no backup and recovery.

3.8 User Requirement

From the analysis carried out, the following were identified as the user requirement for the system.

1. The new system should be able to calculate the numbers of hours the labour/casual

workers work for per day.

2. The system should be able to deduct from the amount of the casual staff if arrived at the

workplace late

3. The system should be able to show bar-chart of the monthly report, show the numbers of

attendance clock-in/clocked-out, numbers of late attendees, and take the percentage of the

total attendance on the system.

4. The user should be able to choose the schedule of his/her working time, show the wages,

5. The user should be able to clock-in/clocked-out the working hour on the user page

6. The system should be able to delete and edit the attendees account and prevent

unnecessaries modification to the account for security purpose.

7. The system should calculate the Gross, Net-Pay add deduction or overtime to the selected

user and generate transaction report.

8. The administrator should be able to update his/her profile.

 9. The new system should be able to limit errors in the financial computations.

10. The system should provide a high-level security for all transactions.

3.8.1 Functional Requirements for the Proposed System

Out of the user requirements identified, the following were synthesized as the functional

requirements.

1. System admin should be able to edit/delete attendees’ details.

2. The system should be able to search for casual workers.

3. New user should be able to Clock in/out for a workday

4. Staff should be able to process make Overtime and deduction for staff.

5. The System should be able to decline Attendance of staff and make update

6. The System Should be able to make Cash Update

7. Admin should be able to SMS/Email to the any Casual Staff

8. Admin should be able to Update Profile and Change Password

9. Admin should be able to print the Report for the Gross, Deduction, Cash Advance and

necessary report need by the user.

3.8.2 Functionalities of the System

• Casual Workers and Administrative side

• Add, Edit, Remove and View Casual Workers

• Manage Casual Workers Attendance

• Overtime Works, Advance Cash and Manage Schedules

• Deductions, Position and Titles

• Wages on Date Range and Payslip on Date Range

3.8.3 System Design

The design tools used in this study include the following:

i. UML (Unified modelling Language)

ii. Use Case Diagram

iii. Gant Chart Diagram

iv. Network Diagram

3.8.3 Hardware Requirements

For efficiency the computer system on which the software is installed should have

i. A Fast-Central Processing Unit (with clock cycle 2GHZ)

ii. A minimum amount of RAM (2GB is desirable)

iii. Enough hard disk storage (5000GB)

iv. Recommended processor speed of at least 900MHZ, Intel Pentium or Intel Celeron

v. Monitor size 14 inch and above

vi. If Desktop is to be used (An Uninterruptible Power Supply (UPS)) for desktop PC

3.9 Review of Research Objectives in Relation to Web-Based System Applications

The research objective acted the major guideline to the design, development and validation of the

Web-based application. The first objective was to design a system that handles the casual

Workers’ Wages Attendees with the access from the administration to clock in the casual

workers. The study explained the various forms of employment focusing on casual employment.

It explained the nature of casual employment as labour brokers hence the challenges in casual

labor management and payment. Using requirement system analysis of the data collected from

both primary and secondary sources of information the research indicated the key element in

coordination and payment of casual laborers. The study discovered that most of casual
information must be collected in the field hence issue of portability and bulkiness were factors to

be considered. The data collected needed to be group based on projects and tasks.

The second objective was to review research gaps with the existing casual workers management

and Wages payment. The study identified some applications that exist currently and could be

used for casual labour management. However, most of these applications were found lacking or

limited versus the client expectations. The applications either could manage casual labourer but

had no integrated payment options while others were financial oriented system or had no aspects

of casual labour management or project management. Other applications were personal computer

applications which were not portable hence could not be used in the field.

The third objective was to design, develop and test a working prototype that can be used in data

management and payment of casual labourer. The application designed had to allow real time

data from the field as well as be integrated to external application programming interfaces to

enable communication via messages and mobile money payments to the casual laborers. Service

oriented architecture was found best suited. A web and mobile integrated solution were

developed based on design diagrams and user functional requirements stated by respondents. The

web application used Hypertext Preprocessor (PHP) framework while the mobile application

used the android operating system. The database used is MySQL database.