Rational Unified Process (RUP) Methodology

The Rational Unified Process attempts to capture many of modern software development's best practices in a form suitable for a wide range of projects and organizations. This process recognizes that the traditional waterfall approach can be inefficient because it idles key team members for extended periods of time. Many feel that the waterfall approach also introduces a lot of risk because it defers testing and integration until the end of the project lifecycle. Problems found at this stage are very expense to fix.

By contrast, RUP represents an iterative approach that is superior for a number of reasons:

It lets you take into account changing requirements which despite the best efforts of all project managers are still a reality on just about every project.
Integration is not one "big bang" at the end; instead, elements are integrated progressively.
Risks are usually discovered or addressed during integration. With the iterative approach, you can mitigate risks earlier.
Iterative development provides management with a means of making tactical changes to the product. It allows you to release a product early with reduced functionality to counter a move by a competitor, or to adopt another vendor for a given technology.
Iteration facilitates reuse; it is easier to identify common parts as they are partially designed or implemented than to recognize them during planning.
When you can correct errors over several iterations, the result is a more robust architecture. Performance bottlenecks are discovered at a time when they can still be addressed, instead of creating panic on the eve of delivery.
Developers can learn along the way, and their various abilities and specialties are more fully employed during the entire lifecycle. Testers start testing early, technical writers begin writing early, and so on.
The development process itself can be improved and refined along the way. The assessment at the end of an iteration not only looks at the status of the project from a product or schedule perspective,
but also analyzes what should be changed in the organization and in the process to make it perform better in the next iteration.

Methodology

the analysis of the principles of methods, rules, and postulates employed by a discipline, the systematic study of methods that are, can be, or have been applied within a discipline
, a particular procedure or set of procedures.

Methodology refers to more than a simple set of methods;[citation needed] rather it refers to the rationale and the philosophical assumptions that underlie a particular study relative to the scientific method. This is why scholarly literature often includes a section on the methodology of the researchers. This section does more than outline the researchers’ methods (as in, We conducted a survey of 50 people over a two-week period and subjected the results to statistical analysis; it might explain what the researchers’ ontological or epistemological views are.

Another key (though arguably imprecise) usage for methodology does not refer to research or to the specific analysis techniques. This often refers to anything and everything that can be encapsulated for a discipline or a series of processes, activities and tasks. Examples of this are found in software development, project management and business process fields. This use of the term is typified by the outline who, what, where, when, and why. In the documentation of the processes that make up the discipline, that is being supported by "this" methodology, that is where we would find the "methods" or processes.

PHASES OF SDLC

Initiation/planning

To generate a high-level view of the intended project and determine the goals of the project. The feasibility study is sometimes used to present the project to upper management in an attempt to gain funding. Projects are typically evaluated in three areas of feasibility: economical, operational, and technical. Furthermore, it is also used as a reference to keep the project on track and to evaluate the progress of the MIS team.The MIS is also a complement of those phases. This phase is also called the analysis phase.

Requirements gathering and analysis

The goal of systems analysis is to determine where the problem is in an attempt to fix the system. This step involves breaking down the system in different pieces and drawing diagrams to analyze the situation. Analyze project goals, break down functions that need to be created, and attempt to engage users so that definite requirements can be defined. Requirement Gathering sometimes require individual/team from client as well as service provider side to get a detailed and accurate requirements.

Design

In systems design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. The output of this stage will describe the new system as a collection of modules or subsystems.

The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input.

Build or coding

Modular and subsystem programming code will be accomplished during this stage. Unit testing and module testing are done in this stage by the developers. This stage is intermingled with the next in that individual modules will need testing before integration to the main project.code will be test in every sections.

Testing

The code is tested at various levels in software testing. Unit, system and user acceptance testing are often performed. This is a grey area as many different opinions exist as to what the stages of testing are and how much if any iteration occurs. Iteration is not generally part of the waterfall model, but usually some occurs at this stage.

Types of testing:

Data set testing.
Unit testing
System testing
Integration testing
Black box testing
White box testing
Module testing
Regression testing
Automation testing
User acceptance testing
Performance testing
Operations and maintenance

The deployment of the system includes changes and enhancements before the decommissioning or sunset of the system. Maintaining the system is an important aspect of SDLC. As key personnel change positions in the organization, new changes will be implemented, which will require system updates.

SYSTEM DEVELOPMENT LIFE CYCLE

Software Development Life Cycle in systems engineering and software engineering, is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. The concept generally refers to computer or information systems.

In software engineering the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information systeM: the software development process.

Systems Development Life Cycle (SDLC) is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.

Computer systems have become more complex and often (especially with the advent of Service-Oriented Architecture) link multiple traditional systems potentially supplied by different software vendors. To manage this level of complexity, a number of system development life cycle (SDLC) models have been created: "waterfall," "fountain," "spiral," "build and fix," "rapid prototyping," "incremental," and "synchronize and stabilize."

SDLC models can be described along a spectrum of agile to iterative to sequential. Agile methodologies, such as XP and Scrum, focus on light-weight processes which allow for rapid changes along the development cycle. Iterative methodologies, such as Rational Unified Process and Dynamic Systems Development Method, focus on limited project scopes and expanding or improving products by multiple iterations. Sequential or big-design-upfront (BDUF) models, such as Waterfall, focus on complete and correct planning to guide large projects and risks to successful and predictable results.

Some agile and iterative proponents confuse the term SDLC with sequential or "more traditional" processes; however, SDLC is an umbrella term for all methodologies for the design, implementation, and release of software.

In project management a project has both a life cycle and a "systems development life cycle," during which a number of typical activities occur. The project life cycle (PLC) encompasses all the activities of the project, while the systems development life cycle focuses on realizing the product requirements.

What is Computer?

a machine that manipulates data according to a set of instructions.

Although mechanical examples of computers have existed through much of recorded human history, the first electronic computers were developed in the mid-20th century (1940–1945). These were the size of a large room, consuming as much power as several hundred modern personal computers (PCs).[1] Modern computers based on integrated circuits are millions to billions of times more capable than the early machines, and occupy a fraction of the space.[2] Simple computers are small enough to fit into a wristwatch, and can be powered by a watch battery. Personal computers in their various forms are icons of the Information Age and are what most people think of as "computers". The embedded computers found in many devices from MP3 players to fighter aircraft and from toys to industrial robots are however the most numerous.

Network Topology

is the physical interconnections of the elements (links, nodes, etc.) of a computer network. A local area network (LAN) is one example of a network that exhibits both a physical topology and a logical topology. Any given node in the LAN has one or more links to one or more other nodes in the network and the mapping of these links and nodes in a graph results in a geometrical shape that may be used to describe the physical topology of the network. Likewise, the mapping of the data flows between the nodes in the network determines the logical topology of the network. The physical and logical topologies may or may not be identical in any particular network.

Rapid Application Development (RAD)

Refers to a type of software development methodology which uses minimal planning in favor of rapid prototyping. The "planning" of software developed using RAD is interleaved with writing the software itself. The lack of extensive pre-planning generally allows software to be written much faster, and makes it easier to change requirements.

Rapid Application Development is a software development methodology, which involves iterative development and the construction of prototypes. It is a merger of various structured techniques, especially data driven Information Engineering with prototyping techniques to accelerate software systems development.[1]

RAD calls for the interactive use of structured techniques and prototyping to define user's requirements and design the final system. Using structured techniques, the developer first builds preliminary data models and business process models of the business requirements. Prototyping then helps the analyst and users to verify those requirements and to formally refine the data and process models. The cycle of models, then prototypes, then models, then prototypes and so forth on, ultimately results in a combined business requirements and technical design statement to be used for constructing new systems.

CHAPTER 5

Chapter V
SUMMARY, CONCLUSION and RECOMMENDATION

Summary

Capiz Electric Cooperative is the most source of Electricity in Roxas City. Due to the increasing numbers of people whose using electricity every year, the cooperative requires some support. This increasing of number of people who used electricity means more task and transaction to be processed, record to be stored and the increase of task for the employees and the personnel of the said cooperative. With the help of the modern technology and by the use of internet, the proponents learned more about the importance of a computerized payroll system. With the help of the proposed computerized payroll system, the proponents can help the respondents to lessen the problem encountered in the payroll process in terms of generating reports of each employee. This system will provides fast, reliable and efficient computerized payroll transaction. By this study, the Capiz Electric Cooperative will be given significant contribution especially for the improvement of their payroll transaction.

Conclusion

The Capiz Electric Cooperative renders inevitable standards of high quality of services for their employees. The Accounting Department of CAPELCO still uses manual method in doing their payroll tasks, because it takes lots of time and efforts and also focuses in recording, calculating, and generating reports. It is a pressure for the Payroll Maker to do the task to avoid committing errors and revisions.
Through the Computerized Payroll System, the Capiz Electric Cooperative will be able to generate accurate records and reports since it is stored in database. The system also provides security where it is only accessible to the authorized user or the person in charge using its own password.

Recommendation

The Proponent developed a Computerized Payroll System for Capiz Electric Cooperative (CAPELCO) to know the needs and the problem encountered of the Accounting Department, especially the Payroll Maker when it comes to security, the date efficiency of generating necessary reports. The proponents highly recommended the online payroll site for Capiz Electric Cooperative. The employees can search online about their payroll slip and other reports. The proponents recommended also to CAPELCO to implement the system using Local Area Network (LAN). The proponents recommend networking connection to the proposed system to connect and shared data from one Computer to another.

CHAPTER 4

Chapter 4

THEORETICAL FRAMEWORK

Capiz Electric Cooperative is still using their manual system. Payroll system is a computerized payroll system that is designed to give a better service. This is to make sure that their works accurate and it is to less time and effort of the personnel. Computerized payroll system would be a great help to maximize the use of computer and give services to any companies as well as to the capiz electric cooperative.

1. System Security

It is important to any kind of system for an information system, which is design for multi-user environment wherein lot of people can access data. System security can be improved through good security mechanics and can undermine through faulty design or implementation. This theory helped the proponents in developing a system that is secure from the interaction of unauthorized user.

2. Reliability

In computer software, reliability is generally measured how often the product breakdown or requires major services. Reliability can be defined as the probability that an item will continue to perform its intended function without failure for a specified period of time under stated condition. This theory gives the proponents the idea how to implement an effective system by making sure of its reliability.

3. Integrity

Is an attribute that measures the system ability to withstand with the attack its security. It is achieved by preventing accidental or deliberate but unauthorized insertion, modification or destruction of data in the database.

4. Correctness

It is one of the important capabilities of the software to the user is its correctness. Correctness is a great help for the accomplishment of the study by making sure that the software performs its required function. The proponents would expect that correctness of all aspects of such software, including the user interface would be strenuously pursued.

5. Database Design

The process of producing a detailed data model of a database. This logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a Data Definition Language, which can then be used to create a database.
A fully attributed data model contains detailed attributes for each entity. Database theory encapsulates a broad range of topics related to the study and research of the theoretical realm of database and database management system.

6. System Design

Is process or art of defining the architecture, components, modules, interface and data for a system to satisfy specified requirement. One could see it as the application of system theory to product development. It is the application of systems theory to product development. There is some overlap with the disciplines of systems analysis, systems architecture and systems engineering. It helps the proponents to satisfy the requirements specified by the user in order to implement the system correctly.

CHAPTER 3

Chapter III

METHODOLOGY OF THE STUDY

The continuous growth of the world is also the continuous change of all it has. Proponents believed that “There is nothing in this world that is constant but change”. It is due to the unsatisfied craving and¬ human consciousness to discover and search thing to support and satisfy human needs and wants. That is through developing man-made machine, devices and application in order to expressing their ideas and principles.

Among the four methodologies (the System Development Life Cycle (SDLC), Rapid Application Development (RAD), Joint Application Development (JAD), the proponents used the Fourth Generation Technique (4GT) because of its powerful tools in implementation. It is flexible nature in terms of accessing database and its user-friendliness.

Fourth Generation Technique (4GT) best suits the system developed. It has a characteristic that makes the system methodical and systematic. Fourth generation techniques (4GT) encompasses a broad array of software tools that have one thing in common each enables the software engineer to specify some characteristic of software at a high level. The tool then automatically generates source code based on the developer's specification. There is little debate that the higher the level at which software can be specified to a machine, the faster a program can be built. The 4GT paradigm for software engineering focuses on the ability to specify software using specialized language forms or a graphic notation that describes the problem to be solved in terms that the customer can understand.

Technique (4GT) involve different phase such as Requirements Gathering, Design Strategy, Implementation using Fourth Generation Languages and Testing.
Requirements Gathering.

The first phase of 4GT is the Requirements Gathering. This is the phase where the definition of requirements necessary in building software is defined. This is where the gathered data is translated into operational prototype, which is necessary in developing a design strategy for the system. This phase could be best done by interviewing the respondent and other people who have extensive knowledge in developing a specified system.

Design Strategy

In this phase where the gathered data is translated into a set of presentation that describes data structures, architecture, algorithmic procedures and interface characteristic. This is the phase where the proponents defined how the system is to be developed. The use of 4GT without design for large project will cause difficulties such as poor quality, poor maintenance ability, and poor customer acceptance that are often encountered when developing software using conventional approaches. All this necessary in order to proceed to the next phase called

Implementation using Fourth Generation Languages (4GL)

This the third phase of 4GT wherein the design presentation is translated to an artificial language that result in instruction that could be executed by the computer. The gathered requirements and design are put into a machine executable form using the newest programming language the Microsoft Visual Basic 2008 as a tool.

Testing

The last phase is testing, in computer hardware and software development is used at key checkpoints in the overall process to determine whether objectives are being met. This is required to ensure the system quality and that it will not create errors during run time, especially when it is being used.

CHAPTER 2

Chapter II

REVIEW OF RELATED LITERATURE

The development of Computerized Payroll System for Capiz Electric Cooperative is difficult task. The proponents gathered some information that is related in the Proposed Computerized Payroll System to have a guide and background in developing a system.


CONCEPTUAL LITERATURE

Payroll System is a flexible compensation administration solution. It is designed to help human resource professionals as well as finance and accounting personnel to manage employee compensation, deductions, allowances, and benefits in an organization. The system is integrated with the Employee Information System, offers efficient features and functionality to manage company's expenses. (www.blastasia.com)

Payroll is an application that lends itself well to the computer because of its repetitive procedures and calculation. A Computerized payroll system can perform the same basic function as those performed manually by payroll clerk. The important differences are the computer’s speed, accuracy, reliability, and ability to easily generate reports. In a computerized payroll system, the computer stores data such as an employee’s name, address, social security number, marital status, number of withholding allowances, pay rate and voluntary deductions. At the end of each pay period, the operator enters all payroll transaction data, such as regular and overtime hours for each employee and deduction into the computer. The computer calculates all withholding taxes and other deductions and accumulates and updates the earnings and withholdings. (Www.wadsworth.com)

FOREIGN STUDIES

Titus Information Payroll System

A Payroll System designed to produce payroll checks with appropriate withholdings, benefits, allowances, and deductions for employees in multiple companies, departments, and/or sub-departments. It has been designed to handle up to 1,000,000 employees in 100 companies, 1,000 departments in each company, and 36 sub-departments in each department.

Some of the features and benefits of the Payroll System are multiple cost centers for payroll reporting, will handle special non-taxable benefits for ministers, flexible withholding capability, ability to split payroll expense between different cost centers, complete governmental reporting; FICA, FUTA, SUTA, Workman's Compensation, W-2's, and 1099's, Payroll check reversal, One check capability, Salaried, hourly, and contract employees in the same payroll run, Combined processing for weekly, bi-weekly, semi-monthly, or monthly, Taxable and non-taxable benefits and deductions, Multiple hourly rates for each employee, General ledger interface, Check list UFD file for check reconciliation, Extensive personnel information for each employee, Accrual of sick, vacation, and holiday hours, Flexible federal, state, and local taxation, Multiple company, department, and sub-department capability, Flexible benefit and deduction capability, Easy federal, state, and local tax table maintenance, Split income over multiple companies, departments, sub-departments, Payroll accrual/reversal capabilities, Time card data entry function, Special message function for printing on check stubs. (Www.titusinformationsystems.com)

Canadian Payroll System

Sage Accpac Canadian Payroll is a flexible module that gives you complete control over employee earnings and benefits, special payroll situations and government reporting, ensuring that your company's payroll requirements and personnel policies are accurate to the penny. You can enter or import timecards, enter after-the-fact paycheques, run automatic calculations or even combine all three methods to get your pay data into the system and your paycheques deployed on time. Payroll handles all pay frequencies; multiple work states; unlimited earnings, deductions, benefits and taxes; and other pay factors such as expense reimbursements, accruals and advances. (www.2020software.com)

LOCAL STUDIES

Cagayan de Oro City Hall Computerized Payroll System

The City Accounting Department has introduced an upgraded computerized payroll system for permanent employees in a bid to improve its services and maximize resources. "This project, which was conceived two years ago, basically aims to improve our services particularly in the processing of payrolls for permanent employees," City Accountant Wilma Polley-Rugay told payroll in-charge of the different departments and offices at City Hall during a briefing and orientation on the concept of the one-month payroll system held Friday last week at the City Council session hall in Cagayan de Oro City. With the added features of the new computerized payroll system, Rugay said the preparation, processing and payment of payroll system to permanent employees would be hastened and fast-tracked.

Adopting of the one-month payroll system is also beneficial, not only to the City Accounting Department, but also to the payroll-in-charge as it would save time, energy and resources. “Employees who handle payroll preparation and processing can now attend to other office needs and concerns as the new payroll system will lessen their workload," she added.

Under the new payroll system, preparation and processing of payroll, which reflects the accrued, amount payable every 15th and 30th day of the month, done only once. Unlike the time-consuming old payroll system, preparation and processing of payroll is done twice a month covering the first half and second half of the month. (www.sunstar.com.ph)

Computerized Payroll System of Department of Health (DOH)

The Computerized Payroll System is a window based program especially designed to facilitate and simplify the monthly preparation of general payroll and related reports such as Standard computerized payroll system for use in all DOH offices, Allows faster and more accurate computation of monthly gross income, deductions and net salary, Faster and less-resource-consuming generation of General Payroll and other payroll related reports, Security and integrity of payroll data and information. The Features of computerized payroll system of DOH are Graphical User Interface, Interactive and menu-driven program, Systematic maintenance and retrieval of employee records, Flexible as it provides options to include additional fields for other compensation and deductions unique to an office or unit, Automatic computation of monthly net income, GSIS, PAG-IBIG, Withholding Tax and other deductions, Y2K compliant, Fast and easy generation of the General Payroll and all other payroll related reports which include Monthly reports like GSIS and PAG-IBIG remittances, Denominations Report and Leave Credits Report and annual Year-end Tax Reports, Password security to ensure the integrity of data. General payroll reports such as Payroll Summary sheet, Pay slip, Leave Credits Report, Withholding Tax Statement (W-2), BIR Remittance Reports, GSIS Remittance Reports, PAG-IBIG Remittance Reports, Other User-defined Reports (PERA, ACA, PNB, etc..). (www2.doh.gov.ph)

The proponents learned from this study that the Cagayan de oro and Department of Health has its own database for their employees. They stored the information of the employees to the database that represent each employee’s records as a separate persistent object.

Computerized Payroll System of Capiz Electric Cooperative THESIS 1

Chapter 1

INTRODUCTION

Background of the Study

Nowadays all establishment are becoming modernized, they use modern technologies to make their transaction fast, easy, and accurate in order to avoid waste of time and for the sake of safety and security. It also helps human to solve and understand complex problem and analysis such us the computational need of humans. Especially to business establishment or corporation processing enormous data and complex transaction. Payroll is an example of a complex transaction because it is a critical business operation dealing with numerous accounts and produce plenty and confidential files. Payroll is encompasses every employee of a company who receives a regular wages or other compensation due to each.

Applying manual procedure on a Payroll transaction involving the vast beat answer in that problem would be computer because computers can simulate enormous data and can process complex transaction in a fast and efficient way. It can generate numerous accounts and data accurately.

A Computerized Payroll System will not only provide accurate calculation and fast process of Payroll transaction but it will secure data through security implementation and accordingly arrange files provided by a well designed database that will produce a paperless environment.

Capiz Electric Cooperative is Government regulated by ERC. Capiz Electric Cooperative is headed and managed by a General Manager from National Electrification Administration (NEA).

Capiz Electric Cooperative if formed by the National Electrification Administration last June 07,1971 and registered with NEA last June 16, 1971.Several projects were proposed and granted by NEA and the cooperative rapidly expanded. February 16, 1978, National Electrification Commission (NEC) certificate of franchise NO. 004 issued to Capiz Electric Cooperative the license to operate electric light and power for 50 years in area comprising Roxas City and the sixteen town of Capiz namely Panay, Panitan. Pontevedra, Maayon, President Roxas and Pilar, Ivisan, Sapian, Jamindan, Mambusao, Sigma, Dao, Cuartero, Dumarao, Dumalag Tapaz and the City of Roxas. Capiz Electric Cooperative has six Area Offices: Roxas City, President Roxas, Mambusao, Dao, Dumalag and the main office is in Timpas, Panitan.

Presently, Capiz Electric Cooperative (CAPELCO) is practicing the manual process on their Payroll System. It has separate manual process for the Regular Employees and J.O (Job-Order) employees. The total number of employees in Capiz Electric Cooperative is 339 – 299 regular employees and 40 job-order employees.

Statement of the Problems

1. Time consuming process of payroll preparation

The Capiz Electric Cooperative still using the manual method of payroll process. A lot of jobs are assigned to the payroll maker and accounting clerk, with cause’s inconvenience to their services. In this method, it will need more time and manpower to complete the payroll of each employee.

2. Laborious payroll process

Nobody could admit the inescapable fact that what makes the manual procedure take a long time to finish the task is due to the many steps and processes to undergo. There is the collection of data such as DTR, REMITTANCES, and individual manual calculation of payroll. Individual data is transferred through sheets, encoding and double checking after calculating. All this process requires labor and effort to complete the task.

3. Misposting and understating of employee’s data

The logical process of manual procedure result to too much time consumption. It often times result in misposting and understating of each employees data of plenty of files that is hard to accommodate.

Objectives of the Study

This study is intended to design and develop a Computerized Payroll System for Capiz Electric Cooperative for calendar year 2010.

Specifically, this study aims:

1• To minimize the effort of the bookkeeper in processing the Payroll Slip and Payroll Form.

2• To make an efficient and accurate computation of Payroll.

3. To create a well-arranged database and to implement strong security of the system for data security.

Significance of the Study

To Accounting Department and Payroll Maker of Capiz Electric Cooperative

The proposed system will help the accounting section of Capiz Electric Cooperative especially the Payroll maker/bookkeeper and the Finance Officer. It will help to lessen the time and effort of the payroll maker/bookkeeper preparing payments of employees. The System develop can accommodate changing figures and produce a paperless environment through well design database.

To Proponents

This study will help the proponents to enhance the ability on how to create an understandable computerized system in an easy way. This will serve to the proponents as a challenge to do a better system.

To the other Researcher

This study gives knowledge to the researcher on how to create a Computerized System in understandable way. This will serve as a fresh ground for the researcher whose study will be related in the field of Information Technology.

Scope and Limitation

Scope

This study is designed to develop a Computerized Payroll System for Capiz Electric Cooperative. It covers the process of preparing the Pay slip of each employee, the regular and job order employee, keeping of records safety and computing the exact wages of each employee. Including the stored report list of employee such as Monthly Salary, Basic salary, overtime, Gross payment, Net pay, and Deduction such as withholding tax, SSS, and Medicare, SSS loan, Advances, Multi-purpose loan, PAG-IBIG Contribution, CAPELCO loan, Cash Advance, Bond, Energy Sales, Motorcycle, Canteen, under time, Cigna, WELCA, union loan, Lot/housing loan, health Care and AR.

The proposed Payroll System for Capiz Electric Cooperative is expected to generate Pay Slip of Employees, Report list of employees, Remittances for respective agencies, Payroll register of regular and job-order employees, and Payroll form for every pay period.

Limitation

The proposed Computerized Payroll System for Capiz Electric Cooperative does not support network topology implementation and online program or online transaction.

Joint Application Design (JAD)

is a process used in the Systems Development Life Cycle (SDLC) to collect business requirements while developing new information systems for a company. "The JAD process also includes approaches for enhancing user participation, expediting development, and improving the quality of specifications." It consists of a workshop where “knowledge workers and IT specialists meet, sometimes for several days, to define and review the business requirements for the system.” The attendees include high level management officials who will ensure the product provides the needed reports and information at the end. This acts as “a management process which allows Corporate Information Services (IS) departments to work more effectively with users in a shorter time frame.

“Joint Application Design (JAD) was developed by Chuck Morris of IBM Raleigh and Tony Crawford of IBM Toronto in the late 1970’s. In 1980 Crawford and Morris taught JAD in Toronto and Crawford led several workshops to prove the concept. The results were encouraging and JAD became a well accepted approach in many companies. In time, JAD developed and gained general approval in the data processing industry.