|
Windows-based timesheet software faces all of the potential problems above when deployed. Because the software touches most, if not all employees, the costs involved are typically quite large.
The solution to all of the above problems lies in using Web-based technologies and your intranet. With web-based solutions, each end user accesses the time keeping software through a web browser. Because all desktops now come standard with either Microsoft Internet Explorer or Netscape Navigator as browsers, each desktop already has the tools needed to access a variety of applications.
Web-based applications are traditionally split into multiple components. The user interface or front end component executes within the browser, either as HTML, Java, Active-X, or JavaScript. The server side applications can be developed and executed in a variety of ways, but Java, C++, Visual Basic along with an application server, servlet, and/or active server pages are the most common back-end solutions.
This approach has many advantages. The client component is typically a thin component. The front end handles only the data presentation and user interface. This thin-client model means that the desktop doesn't require any database software to be installed for proper execution. Typically, the only requirement is a compatible browser (with a compatible Java Virtual Machine installed if the client is a Java client).
The server side also has many advantages over a traditional two-tiered client/server system. Typically, the server side utilizes a multi-threaded design to maximize performance on a multi-processor server. The server side also uses an application server and database connection pooling to gain high availability and scalability required to support hundreds or thousands of users.
This multi-tiered web-based design is ideally suited for time and attendance software. Time and attendance software that is widely distributed throughout an organization needs to run on a variety of desktops. The timeheet software needs to support a very large user population. This is especially true in environments where a lot of employees may access the time keeping software in a short period of time (such as at the end of the week).
|