Development of a feature-rich, practical online intranet knowledge mgmt system for the college (KMS).


Title of the project


Development of a feature-rich, practical online intranet knowledge mgmt system for the college (KMS).


Abstract of the project


This project is aimed at developing an online intranet knowledge mgmt system that is of importance to either an organisation or a college. The system (KMS) is an Intranet based application that can be accessed throughout the organisation or a specified group/Dept. This system can be used as a knowledge/information mgmt system for the college. Students/Staff logging should be able to upload any kind of technical information. Students/staffs logging in may also access/search any information put up by others.KMS should facilitate knowledge sharing from the grass root level like project teams to the entire college.




Generic Technology keywords


Databases, Network and middleware, Programming


Specific Technology keywords


MS-SQL server, HTML, Active Server Pages. Servlets, JSPs


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. More functionality 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.


  1. A person should be able to


  • Access/ Search documents/information from the first page (only read access).


  • login to the system through the first page of the application


  • change the password after logging into the system
  • See/change his/her details (like how many reports/technical documents/submitted)


  • Upload/ withdraw reports/technical papers/documents to his account.


  • get help about the Knowledge mgmt system on how to use the different features of the system


  1. An admin login should be present who can read as well as remove any uploads.


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



The following steps will be helpful to start off the project.


  1. Study and be comfortable with technologies such as
    1. Active Server Pages/HTML and SQL server.
    2. UNIX commands, Shell programming, C Programming, Tools like AWK etc.

            Some links to these technologies are given in the ‘Guidelines and References’ 

            Section of this document


  1. Decide on types of uploads (i.e., the different types of documents for IT, Computers, Electronics, Electrical, Mechanical, Civil, etc) and define it formally.


  1. Make a database for storing the documents.


  1. Create the front-page of the system giving a brief description about the system and a login box


  1. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system


  1. You may create other sub-systems like automatic notification, screens for various events. Like some competitions, topper of the month/semester (person who submits maximum uploads).


  1. A role of approver can also be introduced. The student should not have direct access to upload any document. Only when he/she gets an online approval from his approver, the student can upload his document (Make appropriate assumptions).




Hardware requirements




Alternatives (If available)


PC with 2 GB hard-disk and 256 MB RAM






Software requirements




Alternatives (If available)


Windows 95/98/XP with MS-office

Not Applicable


MS-SQL server




Not Applicable


Oracle database system



Manpower requirements


2 to 3 students can complete this in 4 – 6 months if they work fulltime on it.


Milestones and Timelines



Milestone Name

Milestone Description





Week no. 

from the start

of the project





Requirements Specification

Complete specification of the system (with appropriate assumptions) including the framing of policy etc constitutes this milestone (a detailed functionality of the KM system). A document detailing the same should be written and a presentation on that be made.


Attempt should be made to add some more relevant functionality other than those that are listed in this document.


Technology familiarization

Understanding of the technology needed to implement the project.


The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.


Database creation

A database of atleast 100 documents belonging to different subjects (like OS, Networking etc) should be created to demonstrate the use of the system.


It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.


The documents can be downloaded from the Internet or can be submitted by the students themselves during the course of the project.


High-level and Detailed  Design

Listing down all possible scenarios (like upload request, approval, rejection, cancellation, etc) and then coming up with flow-charts or pseudo code to handle the scenario.


The scenarios should map to the requirement specification (i.e., for each requirement that is specified, a corresponding scenario should be there).


Implementation of the front-end of the system

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options (document upload form, document search form etc).


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.


Integrating the front-end with the database

The front-end developed in the earlier milestone will now be able to update the database. Other features like notification etc should be functional at this stage. In short, the system should be ready for integration testing.




Integration Testing

The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).


Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.


Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.


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)



Guidelines and References (ASP tutorial) (SQL-server tutorial) (Shell script introduction)

Tags :
Your rating: None