Search This Blog

Sunday 15 January 2012

Easy Leave



1.  Title of the project: Easy Leave
2.  Domain: Open Industry
3.    Sub Domain: Management: HR Division
4.    Project Architecture: N-Tire Architecture
5.    SDLC methodologies: Waterfall model
6.    Abstract of the project:
This project is aimed at developing a web based Leave Management Tool, which is of importance to either an organization or a college.

The Easy Leave is an Intranet based application that can be accessed throughout the organization or a specified group/Dept. This system can be used to automate the workflow of leave applications and their approvals. The periodic crediting of leave is also automated. There are features like notifications, cancellation of leave, automatic approval of leave, report generators etc in this Tool.

Functional components of the project:
There are registered people in the system. Some are approvers. An approver can also be a requestor. In an organization, the hierarchy could be Engineers/Managers/Business Managers/Managing Director etc. In a college, it could be Lecturer/Professor/Head of the Department/Dean/Principal etc.

Following is a list of functionalities of the system:
  1. A person should be able to
    • login to the system through the first page of the application
    • change the password after logging into the system
    • see his/her eligibility details (like how many days of leave he/she is eligible for etc)
    • query the leave balance
    • see his/her leave history since the time he/she joined the company/college
    • apply for leave, specifying the from and to dates, reason for taking leave, address for communication while on leave and his/her superior’s email id
    • see his/her current leave applications and the leave applications that are submitted to him/her for approval or cancellation
    • approve/reject the leave applications that are submitted to him/her
    • withdraw his/her leave application (which has not been approved yet)
    • Cancel his/her leave (which has been already approved). This will need to be approved by his/her Superior
    • get help about the leave system on how to use the different features of the system
  2. As soon as a leave application /cancellation request /withdrawal /approval /rejection /password-change is made by the person, an automatic email should be sent to the person and his superior giving details about the action
  3. The number of days of leave (as per the assumed leave policy) should be automatically credited to everybody and a notification regarding the same be sent to them automatically
  4. An automatic leave-approval facility for leave applications which are older than 2 weeks should be there. Notification about the automatic leave approval should be sent to the person as well as his superior

7.    Keywords:
·         Generic Technology Keywords: Databases, User Interface, Programming
·         Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server
·         Project Type Keywords: Presentation, Business, Data Access Layers
·          SDLC Keywords: Analysis, Design, Implementation, Testing

8.    Environment:
·         Servers:
·                     Operating System Server: - Microsoft Windows 2000 or Higher
·                     Data Base Server: Microsoft SQL Server 2000/2005
·         Clients: Microsoft Internet Explorer,
·         Tools: Microsoft Visual Studio .Net
·         User Interface: ASP.NET with AJAX
·         Code Behind: VC#.NET
9.     Requirements:
·   Hardware requirements:

Number
Description
1
PC with 40 GB hard-disk
and 512 MB RAM

·   Software requirements:

Number
Description
1
Windows 2000/ XP/ or Higher with MS-office
2.
MS-SQL server2000/2005
3.
Ms-Visual Studio .Net 2008
4.
Ms-Internet Explorer

10.  The following steps will be helpful to start off the project:
  • Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server.
  • Gather some knowledge of product hierarchies and maintenance before starting the design.
  • Create a user database with different access levels.
  • Start with creating the login screen.
  • Create menus for navigation and group the functionalities as sub menus.
  • Create the help-pages of the application in the form of FAQ. This will helps user.

No comments:

Post a Comment