Title of the project Development of a feature-rich, practical Resource Management System (RMS) Abstract of the project This project is aimed at developing an online Resource Management System that is of importance to the various Independent Business Units (IBU) of an organization. The Resource Management System (RMS) is an Intranet based application that can be accessed throughout the organization or a specified group/Dept. This system can be used to add or modify employee details and help the management while organization in allocating resources to various Projects. Keywords Generic Technlogy keywords Databases, Network and middleware, Programming Specific Technology keywords MS-SQL server, HTML, Active Server Pages Unix, Shell, C, Oracle Project type keywords Analysis, Design, Implementation, Testing, User Interface Functional components of the project Following is a list of functionalities of the system. Any more functionalities that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed. There shall be two types of users in the system. One would be the super users, eg project managers, Unit Heads, etc. who would have the authority to allocate resources to various projects. The other type shall be Normal users who would be able to update their personal and official details, but wouldn’t be able to allocate themselves any other IBU’s or projects. 1. A normal user should be able to ? ? Login to the system through the first page of the application. Change the password after logging into the system
? ?
Incorrect entry of the password three consecutive times should lock the user out of the application until the super user resets his password. see his/her personal and official details. Details to be available are: 1. Employee Name. 2. Employee Number. 3. Project Code. 4. Current Location 5. Current IBU 6. Permanent Address 7. Local Address 8. Passport Information (Passport No, Issue date, Expiry date, Issuing Office) 9. Telephone numbers. 10. Educational Qualifications. 11. Technical skills and certifications. 12. No of Years of Experience. 13. Information about previous jobs held. (These should include Name of the organization, Duration of employment, Designation, Brief Description of work done).
2. The normal user should not be able to change certain fields like name, employee no, project code, location and the IBU’s. Only the super users should change these. 3. The normal user should not be able to view the records of any other employee. 4. If the normal user changes any records then a mail should be sent to the concerned user at his e-mail id confirming about the changes made. 5. The power user should be able to view the employee records of all the employees. 6. He should be able to search for employees on the basis of any of the employee fields. 7. He should be able to edit the Current Location, Current IBU and the Project code of any employee. 7. A summary report of the allocation details all employees in an IBU should be sent to the IBU Head periodically
Steps to start-off the project
There are couple of alternatives to implement such a system. A. Microsoft platform: The system is developed using Active Server Pages as the front end and SQL Server as the back end. B. Unix-based platform: HTML or even Shell scripting, C programming, any relational database (eg Postgress or Oracle or even flat files) , and tools in Unix The following steps will be helpful to start off the project. 1. Study and be comfortable with technologies such as a. Active Server Pages/HTML and SQL server. b. Unix commands, Shell programming, C Programming. Some links to these technologies are given in the ‘Guidelines and References’ section of this document 2. Make a database of people at different levels with their roles and form a hirearchy of them, like which role reports to which particular role. Decide on the various details of the people and their roles that would be stored in the database (like employee/registeration-number, name, grade, location, system-login, password in cryptic form, etc) 3. Assign a mail-admin who will create mail-ids for the people in the intranet of your lab or in the internet. These mail-ids will be used for sending automatic notifications and reports. The mail-admin will also take care of assigning the logins to the users of the leave system 4. Create the front-page of the leave system giving a brief description about the system and a login box 5. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system Requirements Hardware requirements Number Description Alternatives (If available) 1 PC with 2 GB hard-disk Not-Applicable and 256 MB RAM 2 Software requirements
Number Description 1 Windows 95/98/XP with MS-office 2 MS-SQL server 3 Linux 4 Oracle database system Manpower requirements
Alternatives (If available) Not Applicable MS-Access Not Applicable POSTgres
2 to 3 students can complete this in 4 – 6 months if they work fulltime on it. Milestones and Timelines Number Milestone Name Milestone Description Timeline Remarks
1
Requirements Specification
2
Technology familiarization
3
Database creation
Week no. from the start of the project Complete 2-3 Attempt should be made to specification of the add some more relevant system (with functionalities other than appropriate those that are listed in this assumptions) document. constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the 4-5 The presentation should be technology needed to from the point of view of implement the project. being able to apply it to the project, rather than from a theoretical perspective. A database of atleast 5-7 It is important to finalize on 100 entries of the database at this stage employees of all itself so that development grades should be and testing can proceed with created. The number the actual database itself. of mail-ids to be created need not be 100. It can be around 10 to 20.
4
5
High-level and Listing down all 7-9 Detailed possible scenarios and Design then coming up with flow-charts or pseudocode to handle the scenario. Implementation Implementation of the 10-12 of the front-end main screen giving the of the system login, screen that follows the login giving various options, screens for each of the options Integrating the The front-end 12-13 front-end with developed in the the database earlier milestone will now be able to update the employee database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing. Integration The system should be 14-15 Testing thoroughly tested by running all the testcases written for the system (from milestone 5). Final Review Issues found during 16-18 the previous milestone are fixed and the system is ready for the final review.
The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there). During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6
7
Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)
8
Guidelines and References http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnasp/html/asptutorial.asp (ASP tutorial)
http://www.functionx.com/sqlserver/ (SQL-server tutorial) http://heather.cs.ucdavis.edu/~matloff/UnixAndC/Unix/CShellII.html introduction) (Shell script
doc_285918735.docx
? ?
Incorrect entry of the password three consecutive times should lock the user out of the application until the super user resets his password. see his/her personal and official details. Details to be available are: 1. Employee Name. 2. Employee Number. 3. Project Code. 4. Current Location 5. Current IBU 6. Permanent Address 7. Local Address 8. Passport Information (Passport No, Issue date, Expiry date, Issuing Office) 9. Telephone numbers. 10. Educational Qualifications. 11. Technical skills and certifications. 12. No of Years of Experience. 13. Information about previous jobs held. (These should include Name of the organization, Duration of employment, Designation, Brief Description of work done).
2. The normal user should not be able to change certain fields like name, employee no, project code, location and the IBU’s. Only the super users should change these. 3. The normal user should not be able to view the records of any other employee. 4. If the normal user changes any records then a mail should be sent to the concerned user at his e-mail id confirming about the changes made. 5. The power user should be able to view the employee records of all the employees. 6. He should be able to search for employees on the basis of any of the employee fields. 7. He should be able to edit the Current Location, Current IBU and the Project code of any employee. 7. A summary report of the allocation details all employees in an IBU should be sent to the IBU Head periodically
Steps to start-off the project
There are couple of alternatives to implement such a system. A. Microsoft platform: The system is developed using Active Server Pages as the front end and SQL Server as the back end. B. Unix-based platform: HTML or even Shell scripting, C programming, any relational database (eg Postgress or Oracle or even flat files) , and tools in Unix The following steps will be helpful to start off the project. 1. Study and be comfortable with technologies such as a. Active Server Pages/HTML and SQL server. b. Unix commands, Shell programming, C Programming. Some links to these technologies are given in the ‘Guidelines and References’ section of this document 2. Make a database of people at different levels with their roles and form a hirearchy of them, like which role reports to which particular role. Decide on the various details of the people and their roles that would be stored in the database (like employee/registeration-number, name, grade, location, system-login, password in cryptic form, etc) 3. Assign a mail-admin who will create mail-ids for the people in the intranet of your lab or in the internet. These mail-ids will be used for sending automatic notifications and reports. The mail-admin will also take care of assigning the logins to the users of the leave system 4. Create the front-page of the leave system giving a brief description about the system and a login box 5. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system Requirements Hardware requirements Number Description Alternatives (If available) 1 PC with 2 GB hard-disk Not-Applicable and 256 MB RAM 2 Software requirements
Number Description 1 Windows 95/98/XP with MS-office 2 MS-SQL server 3 Linux 4 Oracle database system Manpower requirements
Alternatives (If available) Not Applicable MS-Access Not Applicable POSTgres
2 to 3 students can complete this in 4 – 6 months if they work fulltime on it. Milestones and Timelines Number Milestone Name Milestone Description Timeline Remarks
1
Requirements Specification
2
Technology familiarization
3
Database creation
Week no. from the start of the project Complete 2-3 Attempt should be made to specification of the add some more relevant system (with functionalities other than appropriate those that are listed in this assumptions) document. constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the 4-5 The presentation should be technology needed to from the point of view of implement the project. being able to apply it to the project, rather than from a theoretical perspective. A database of atleast 5-7 It is important to finalize on 100 entries of the database at this stage employees of all itself so that development grades should be and testing can proceed with created. The number the actual database itself. of mail-ids to be created need not be 100. It can be around 10 to 20.
4
5
High-level and Listing down all 7-9 Detailed possible scenarios and Design then coming up with flow-charts or pseudocode to handle the scenario. Implementation Implementation of the 10-12 of the front-end main screen giving the of the system login, screen that follows the login giving various options, screens for each of the options Integrating the The front-end 12-13 front-end with developed in the the database earlier milestone will now be able to update the employee database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing. Integration The system should be 14-15 Testing thoroughly tested by running all the testcases written for the system (from milestone 5). Final Review Issues found during 16-18 the previous milestone are fixed and the system is ready for the final review.
The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there). During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6
7
Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)
8
Guidelines and References http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnasp/html/asptutorial.asp (ASP tutorial)
http://www.functionx.com/sqlserver/ (SQL-server tutorial) http://heather.cs.ucdavis.edu/~matloff/UnixAndC/Unix/CShellII.html introduction) (Shell script
doc_285918735.docx