Académique Documents
Professionnel Documents
Culture Documents
By Soumyadeep Ghosh
Table of Contents
Important note....................................................................................................................................................3 1.0 Introduction ..................................................................................................................................................4 1.1 purpose .............................................................................................................................................4 1.2 scope..................................................................................................................................................4 2.0 Environmental characteristics 2.1 Hardware requirements.....................................................................................................................5 2.2 Software requirements .....................................................................................................................5 3.0 Goals of implementation.................................................................................................................................6 4.0 Functional requirements..................................................................................................................................6 5.0 Non Functional requirements..........................................................................................................................7
IMPORTANT NOTE
This document is being prepared before the commencement of the software design and coding phases. Thus many of the software
3
requirements might not be clear at this point of time. As and when additional requirements evolve it will be added to this document, as in most software development practices all the software requirements might not be clear at the beginning.
1.0. Introduction
1.1. Purpose The purpose of this document is to present a detailed description of the mobile based employee management system. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system. However additional requirements may come up during the development of the project and will be added to this document as and when needed.
employees and other executives at different hierarchies. The system also contains a relational database containing all the information about the employees such as payroll, attendance management and leave accounting.
At least 128KB of non-volatile memory is necessary to run Mobile information Device (MID) 8KB of non-volatile memory is needed for storage of persistent volatile data. Minimum 32KB of volatile memory must be available. The device must provide two way network connectivity Some additional non-volatile memory (about 20MB) is required for storage of the employee database
2.2 SOFTWARE REQUIREMENTS The native operating system must implement exception handling, process interrupts , be able to run the JVM and provide schedule capabilities. All user input to the operating system must be forwarded to the JVM otherwise the device cannot run a J2ME application
The native operating system must be able to write and read persistent data(data retained when the device is powered down), to non-volatile memory.
GOALS OF IMPLEMENTATION
This system might be revised in the future so as to run on windows mobiles and android supported Smartphone. It is desirable for the system to be user friendly and support internet connectivity.
6
The code must be documented enough and must be so written so that it can be run on mobiles with very low memory resources.
FUNCTIONAL REQUIREMENTS
1. ENTER DATA DESCRIPTION-it adds new employee data to to database. Input: Employee name, employee id, employee category, employee paygrade, employee status etc. Output: Whether employee data has been correctly entered. 2. SEARCH EMPLOYEE DESCRIPTION: Input: Employee name or employee Output: Employee data. 3. UPDATE DATA DESCRIPTION: Updates already existing employee data. Input: Employee credentials. Output: Whether data has been correctly updated.
4. ENTER LEAVE DETAILS DESCRIPTION: enters the metadata used for leave management. Input: employee details and leave details. Output: whether data has been correctly entered.
Scalability The system is designed to test many different scenarios. Through the use of abstract classes and properties and generally well maintained object oriented techniques, the project should be easily adjusted to meet scenarios outside of its initial implementation. Look and Feel This software should look simple to use. Even amateur users should be able to use it. Performance This software shall provide dynamic sharing of information to the managers. Maintainability This software shall be readily portable to any operating system running Java Virtual Machine(JVM) . The source code will available for future changes or enhancements.