10-06-2014, 04:04 PM
TRAINING AND PLACEMENT CELL
1370282886-99169140TrainingAndPlacement.docx (Size: 95.55 KB / Downloads: 11)
Introduction
1.1 Problem Statement:
This project is aimed at developing an online application for the Training and Placement Dept. of the college. 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 application for the TPO of the college to manage the student information with regards to placement. Students 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 Students.
1.2 Purpose:
For the purpose of training and placement of the student in colleges, TPO’s have to collect the information and CV’s of students and manages them manually and arranges them according to various streams.
If any modification is required that is to be also done manually. So, to reduce the job required to manage CV’s and the information of various recruiters, a new system is proposed which is processed through computers.
1.3 Document Conventions:
Font-Style : Times New Roman
Font-Size:
Main Headings: 16
Sub Headings: 14
Content: 12
Line Spacing: 1.5
1.4 Scope of Project:
The project covers a wide scope. The information of all the students can be stored. CV’s are categorized according to various streams. Various companies can access the information. Students can maintain their information and can update it. Notifications are sent to students about the companies. Students can access previous information about placement.
1. Student Registration facility
2. Student Login
3. View Student Profile
4. Company Page
5. Company Login
6. Company recruitment schedule Page
7. View Recruitment Schedule
8. View Selected List of Students
9. Administrator Control Panel
10. Updates by the Administrator
11. View Updates by the Students
SYSTEM STUDY AND ANALYSIS
2.1 Product Information:
2.1.1 Product Perspective:
This project is mainly intended for automating this procedure that can help the people who belong to the T&P cell by saving their time ,based on this basic operation actually their activity is under two steps the first one is, to maintain the list of students and their credit records and the second job is to maintain the company details and based on the company requirements, need to select the students and make the list of students branch wise, which is more complex task, and here informing is through notice boards , where as this is also a bit old fashioned task, which can be automated in our proposed system by sending mails to the respective candidates. This proposed system is far advantageous than the existing one in many cases such as retrieving the student details is easily maintained in a manner that with just one click we can easily attain the details of the company such as the responsible person contacts and company contact details such as address and phone numbers can be maintained
T&P cell mainly include the details of students. The percentage of the students must be appropriate and true. The notices can be generated, so that we notify all the departments the corresponding information about campus recruitment drives. The student detail can also be viewed.
EXISTING SYSTEM:
1. Filling of forms by students
Here a form is given to students in which he/she has to fill with some details such as his name, roll number, contact details, percentages(from first year to till date), Intermediate particulars(name of institution, place, year of pass, percentage), SSC particulars(name of institution, place, year of pass, percentage).
2. Collecting marks from green book
Marks of each student are collected from green book (a book containing marks and other details maintained by each department in college).
3. Preparing excel sheet
From the data collected through filled-forms and green book, excel sheets are prepared.
These excel sheets are used to prepare a list of students who full-fill the requirements of a company visiting the campus and these students are eligible to attend the campus placement
PROPOSED SYSTEM:
In the proposed system the user need not do all the hectic work. he will be provided with an interface with which he can easily get his work done.
The following are the facilities that are provided by the system to the user
1. Notice generation
Here user has to provide information to the system about company name, date and venue at which campus drive might take place. With this information the system will generate a notice which can be seen on students’ account to intimate students about placement drive.
2. Student list generation
Here the user has to provide information to the system about the requirements of the company (such as, cut off percentage, number of backlogs allowed etc.).
3. View student profile
Here the user is able to view a student’s profile of his interest by giving the student’s roll number as input.
4. Result analysis
Here the user is able to get the results which are released and store them for later usage.
5. Posts
Here the user is provided to post updates or any necessary details to students or others (for example-company officials) depending on his need.
2.1.2 PRODUCT FEATURES
1. Complete automation is possible in this sector, which is against the main disadvantage namely time consuming.
2. Can maintain student details who have been studying in the college.
3. Any kind of lists based on students profile can be retrieved with in less time.
4. Results are uploaded directly from net so that no errors exist in calculating percentages.
5. Effective and good means of communication can be facilitated as we have included mailing module in the proposed system
6. User can also register student and can view and delete there profile.
FEASIBILITY STUDY
A feasibility analysis usually involves a through assessment of the operational (need), financial and technical aspects of a proposal. Feasibility study is the test of the system proposal made to identify whether the user needs may be satisfied using the current software and hardware technologies, whether the system will be cost effective from a business point of view and whether it can be developed with the given budgetary constraints. A feasibility study should be relatively cheap and done at the earliest possible time. Depending on the study, the decision is made whether to go head with a more detailed analysis.
When a new project is proposed, it normally goes through feasibility assessment. Feasibility study is carried out to determine whether the proposed system is possible to develop with available resources and what should be the cost consideration. Facts considered in the feasibility analysis were
1. Technical Feasibility
2. Economic Feasibility
3. Operational Feasibility
Technical Feasibility
Technical feasibility includes whether the technology is available in the market for development and its availability. The assessment of technical feasibility must be based on an outline design of system requirements in terms of input, output, files, programs and procedures. This can be qualified in terms of volumes of data, trends, frequency of updating, cycles of activity etc, in order to give an introduction of technical system. Considering our project it is technical feasible. Training and Placement System, with its emphasis on a more strategic decision making process is fast gaining ground as a popular outsourced function
2 Economic Feasibility
This feasibility study present tangible and intangible benefits from the project by comparing the development and operational cost. The technique of cost benefit analysis is often used as a basis for assessing economic feasibility. This system needs some more initial investment than the existing system, but it can be justifiable that it will improve quality of service.
Thus feasibility study should center along the following points:
1. Improvement resulting over the existing method in terms of accuracy, timeliness.
2. Cost comparison
3. Estimate on the life expectancy of the hardware.
4. Overall objective.
Our project is economically feasible. It does not require much cost to be involved in the overall process. The overall objective is in easing out the recruitment processes.
3.3 Operational Feasibility
This analysis involves how it will work when it is installed and the assessment of managerial environment in which it is implemented. People are inherently resistant to change and computers have been known to facilitate change. The new proposed system is very much useful to the users and therefore it will accept broad audience from around the world.
TESTING
In general, software engineers distinguish software faults from software failures. In case of a failure, the software does not do what the user expects. A fault is a programming error that may or may not actually manifest as a failure. A fault can also be described as an error in the correctness of the semantic of a computer program. A fault will become a failure if the exact computation conditions are met, one of them being that the faulty portion of computer software executes on the CPU. A fault can also turn into a failure when the software is ported to a different hardware platform or a different compiler, or when the software gets extended. Software testing is the technical investigation of the product under test to provide stakeholders with quality related information
Software testing may be viewed as a sub-field of Software Quality Assurance but typically exists independently (and there may be no SQA areas in some companies). In SQA, software process specialists and auditors take a broader view on software and its development. They examine and change the software engineering process itself to reduce the amount of faults that end up in the code or deliver faster.
Regardless of the methods used or level of formality involved the desired result of testing is a level of confidence in the software so that the organization is confident that the software has an acceptable defect rate. What constitutes an acceptable defect rate depends on the nature of the software. An arcade video game designed to simulate flying an airplane would presumably have a much higher tolerance for defects than software used to control an actual airliner.
A problem with software testing is that the number of defects in a software product can be very large, and the number of configurations of the product larger still. Bugs that occur infrequently are difficult to find in testing. A rule of thumb is that a system that is expected to function without faults for a certain length of time must have already been tested for at least that length of time. This has severe consequences for projects to write long-lived reliable software
A common practice of software testing is that it is performed by an independent group of testers after the functionality is developed but before it is shipped to the customer. This practice often results in the testing phase being used as project buffer to compensate for project delays. Another practice is to start software testing at the same moment the project starts and it is a continuous process until the project finishes
Another common practice is for test suites to be developed during technical support escalation procedures. Such tests are then maintained in regression testing suites to ensure that future updates to the software don't repeat any of the known mistakes.