You are on page 1of 5

Development of a feature-rich Web Based Search Portal 1. Title of the project: Carrier Path 2.

Project Architecture : N-Tire Architecture 3. Abstract of the project: This project is aimed at developing an online search Portal for the Placement Details for job seekers. The system is an online application that can be accessed throughout the organization and outside as well with proper login provided. This system can be used as an Online Job Portal for job seekers. Job Seekers logging should be able to upload their information in the form of a CV. Visitors/Company representatives logging in may also access/search any information put up by Job aspirants . 4. Existing System: The existing system is a manual system. Here the employees needs to save the information in the form of excel sheets or Disk Drives. There is no sharing is possible if the data is in the form of paper or Disk drives. The manual system gives us very less security for saving data; some data may be lost due to mismanagement. Its a limited system and fewer users friendly. Searching of particular information is very critical it takes lot of time. It is very critical to maintain manually call records of customers, because call center receives huge no of calls per a day. It is a tedious job to maintain different customers are asking different service details, normally solve these queries are not possible. Automated system is needed. Every employee having different rosters, different shift timings, manually handle these roster is tough work. Search an employee roster in call center system is a tedious job. 5. Proposed System: The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach. User Friendliness is provided in the application with various controls provided by system Rich User Interface.

The system makes the overall project management much easier and flexible. It can be accessed over the Intranet. The user information can be stored in centralized database which can be maintained by the system. This can give the good security for user information because data is not in client machine. Authentication is provided for this application only registered Users can access. There is no risk of data management at any level while the project development is under process. The automated system will provide to the customers for reliable services. The speed and accuracy of this system will improve more and more.

6. Modules: Admin Job Seeker Job Provider Notification Search Report Authentication . 7.Functional components of the project: 1. A person should be able to Access/ Search CVs/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 Upload his/her CV. See/change his/her details. Get help about the application on how to use the different features of the system. 2. An admin login should be present who can read as well as remove any uploads.

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

9. Environment: Servers: 10. Requirements: Hardware requirements: Number 1 Description PC with 2 GB hard-disk and 256 MB RAM 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

Software requirements: Number 1 2. 3. 4.

Description Windows 2000/ XP/ or Higher with MS-office MS-SQL server2000/2005 Ms-Visual Studio .Net 2005 Ms-Internet Explorer

Manpower requirements: 3 to 4 Developers can complete this in 3-4 months. 11. Milestones: No. Milestone Name Milestone Description Remarks

Requirements Specification

Technology familiarization

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project. A database of at least 10 entries of users with at least 1 should application admin.

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

Database creation

High-level and Listing down all possible Detailed scenarios and then coming up Design with flow-charts or pseudo code to handle the scenario. Development Implementation of the main of front end screen giving the login, screen functionalities. that follows the login giving various options, screens for each of the options

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. 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 scenarios should map to the requirement specification

During this milestone period, it would be a good idea for the team to start working on a testplan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. 8 Final Review Issues found during the During the final review of the previous milestone are fixed project, it should be checked that and the system is ready for the all the requirements specified final review. during milestone number 1 are fulfilled 12. 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.

Integrating the The front-end developed in the front-end with earlier milestone will now be the database able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. Integration The system should be Testing thoroughly tested by running all the test cases written for the system (from milestone 5).

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.

You might also like