A Company want to develop generalized PAYROLL Software under suitable platform, which can fulfill all the needs of their Units as they are getting from their existing physical system.

The final Architecture of the System will be decided after the thorough discussion with the management of The Company.

PAYROLL Software is designed in such a way by considering the above-mentioned factors. Properly implementing PAYROLL will give one a competitive advantage and help the company to run its business more effectively, efficiently, and responsively.

The static and dynamic behaviors of the PAYROLL depict some common and generalized design aspects that can be included as part of the basic architecture of the system. The business rules for PAYROLL follow, to certain extent, the workflow model that involves technical complexity in terms of multi-user environment; online transaction maintenance and huge data transfer over the net everyday. The PAYROLL product needs to be highly scalable and must exhibit good performance. Hence, a well-defined system architecture, that considers all these issues together, has to be designed before proceeding for detailed design and development of the product.

PAYROLL System Requirements impose complexity on the following areas that need to be addressed while defining the system architecture:

Users

The PAYROLL system should support multiple concurrent user activities. The users from different locations will remain connected to the server via network throughout the day.

Scalability

The system must be highly scalable. Different modules will be included in the proposed PAYROLL application. The system must have the provisions for new application modules to be incorporated into the system with minimum changes to the existing application parts. Change in business rules, database structure or the user interfaces may be done affecting only the pertaining sections. Thus the system will be highly resilient and stable to future changes.

Performance

Performance is another major issue for the PAYROLL product. The user interfaces for the PAYROLL product will be rich in graphics content that makes it both user-friendly and network resource hungry thereby degrading the overall system performance. The PAYROLL architecture designed in a way so as to reduce this performance bottleneck as much as possible. The PAYROLL system will be deployed over the Internet/ Intranet and utmost care has to be taken to reduce network traffic and server hits.

Proper communication methodologies with the objective of minimizing simultaneous connection to the server and also minimizing the network traffic should be devised and optimized for performance.

Security

Application security is one of the most challenging aspects of network security. Application-level security will ensure that PAYROLL application interacts with end users only in ways that the administrator will intend to. Application-level security will focus on preventing the unauthorized use of resources and PAYROLL information. User can able to enter the system by Login the application through valid User name and Password.

Exception Handling

Different exceptions may arise in the system from time to time that need to be handled by the application and may need to be conveyed to the end-user as well. The exceptions may be generated by the system as an interrupt to change the general flow of the program or as errors. The errors may be generated in the User Interface Layer and the Data Layer. Exceptions and Error handling will be the major part of the proposed PAYROLL product.

Salient features

The user himself can define payroll formulas. There is user level security for each Entry interface as well as each Report. Very easy user friendly interfaces for Income Tax module.

Technologies applied

The application is completely Web based and can be run in Linux as well as Windows Platform.

The technologies applied for different environment are as follows:

Server End Development Environment

- JDK 5
- Netbeans 6.0 java development tool
- Sun java Glassfish Application Server V2
- Blaze DS 3.0 Libraries
- Spring framework 2.5
- iReport 2.5
- Jasper Report
- Mozilla Firefox 3.5 web browser
- Acrobat Reader 9
Database – PostgreSQL 8.2 / MySQL 5.1/Oracle
Linux / Windows operating system

GUI Development Environment

- Adobe Flex Builder 3.0
- Flash 9,10
- Mozilla Firefox 3.5 web browser
- Windows operating system
- Acrobat Reader 9.

Client End Requirement

- Mozilla Firefox 3.5 web browser
- Flash 9 / 10
- Windows / linux operating system
- Acrobat Reader 9

Other than Windows and Oracle all are Open Source Environment.