TNPProjectReport(APril 19)

A Report on

TRAINING AND PLACEMENT PORTAL

Submitted for partial fulfillment of award of

BACHELOR OF TECHNOLOGY

Degree

In

Computer Science & Engineering

By

Himanshi Goel

(1103010068)

Under the guidance of

Dr Pooja Tripathi

MENTOR (Professor)

Mr. Devbrat Upadhyay

SUPERVISOR

(Software Engineer)

INDERPRASTHA ENGINEERING COLLEGE, GHAZIABAD

UPTU, LUCKNOW

April, 2015

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD i

Certificate

Certified that Himanshi Goel has carried out the project work

presented in this report entitled Training and Placement Portal for the

award of Bachelor of Technology from Inderprastha Engineering College,

Ghaziabad, under my supervision. The report embodies result of original

work and studies carried out by Student himself and the contents of the

report do not form the basis for the award of any other degree to the

candidate or to anybody else.

Mentor: Dr. Pooja Tripathi

(Professor)

Supervisor: Mr. Devbrat Upadhyay

(Software Engineer)

Date: April 11,2015

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD ii

Abstract

Training and Placement Portal aims at providing the facility to automate and simplify the process

of registration and list generation of eligible students for placement activities. This system

provide facility to the Training and Placement Officer to do all their work that deals with

Placements like Collecting and analyzing Student records, posting Job Posts for various

companies visiting campus and thereby filtering Students as per companys requirements. The Training and Placement Officer can also update details of students, if requested. TPO can

analyze the placements statistics, i.e. he/she can analyze number of placed and unplaced students

with respect to various criterions like batch wise, course wise, stream wise. TPO can also post

various notices related with jobs. The whole work is automated and is available on the Intranet.

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD iii

Acknowledgement

We take this opportunity to thank our teachers and friends who helped us

throughout the project.

First and foremost I would like to thank my guide for the project (Dr. Pooja

Tripathi, Professor, Computer Science Department and Mr. Devbrat

Upadhyay, Software Engineer) for her valuable advice and time during

development of project.

We would also like to thank (Prof. Ram Gopal, Computer Science Department)

for his constant support during the development of the project.

Name: Himanshi Goel

Roll No.: 1103010068

Signature:

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD iv

DECLARATION

I hereby declare that this submission is my own work and that, to the best of

my knowledge and belief, it contains no material previously published or

written by another person nor material which to a substantial extent has

been accepted for the award of any other degree or diploma of the university

or other institute of higher learning, except where due acknowledgment has

been made in the text.

Signature:

Name: Himanshi Goel

Roll No.: 1103010068

Date: April 11,2015

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD v

Table of Contents

ACKNOWLEDGEMENTS II

CERTIFICATE III

LIST OF FIGURES IV

TABLES OF CONTENT V

LIST OF FIGURES VIII

LIST OF TABLE IX

CHAPTER 1: SYSTEM STUDY AND ANALYSIS

1.1. PRODUCT INFORMATION

1.1.1. PRODUCT PERSPECTIVE 2

1.1.2. PRODUCT FEATURES 2

1.1.3. PERFORMANCE ATTRIBUTE 4

1.2. REQUIREMENT ANALYSIS

1.2.1. FUNCTIONAL REQUIREMENT 5

1.2.2. NON FUNCTIONAL REQUIREMENT 5

1.3. FEASIBILITY STUDY

1.3.1. TECHNICAL FEASIBILITY 6

1.3.2. ECONOMICAL FEASIBILITY 7

1.3.3. SCHEDULED FEASIBILITY 7

1.3.4. OPERATIONAL FEASIBILITY 7

CHAPTER 2: SOFTWARE REQUIREMENT SPECIFICATION

2.1. INTRODUCTION

2.1.1. PURPOSE 10

2.1.2. PROBLEM STATEMENT 10

2.1.3. PROJECT OBJECTIVE 11

2.1.4. PROJECT SCOPE 11

2.1.3. OPERATING ENVIRONMENT 11

2.1.4. METHODOLOGY 12

2.1.5. DESIGN & IMPLEMENTATION CONSTRAINTS 13

2.2. SOFTWARE DEVELOPMENT LIFE CYCLE

2.2.1. INTRODUCTION TO SDLC 14

2.2.2. STAGES OF SDLC 15

2.2.3. SDLC MODELS 16

2.2.4. PROCESS MODEL ADOPTED 23

2.2.5. SYSTEM FEATURES 25

2.3. EXTERNAL INTERFACE REQUIREMENTS

2.3.1. USER INTERFACES 26

2.3.2. HARDWARE INTERFACES 27

2.3.3. SOFTWARE INTERFACES 27

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD vi

CHAPTER 3: SYSTEM DESIGN

3.1. DATA FLOW DIAGRAM 30

3.2. CLASS DIAGRAM 33

3.3. SEQUENCE DIAGRAM 34

3.4. INPUT DESIGN 37

3.5. OUTPUT DESIGN 37

3.6. DATABASE DESIGN 38

3.7. TABLES 40

CHAPTER 4: THEORETICAL BACKGROUND

4.1. INTRODUCTION TO FRONT END

4.1.1. ABOUT THE PLATFORM (VISUAL C#) 47

4.1.2. DEVELOPING AN APPLICATION IN VISUAL C# 47

4.1.3. COMMON FEATURES 49

4.2. INTRODUCTION TO BACK END

4.2.1. INTRODUCTION TO DBMS 50

4.2.2. SQL SERVER 2000 DATABASE 52

4.2.3. DBMS ARCHITECTURE 53

CHAPTER 5: CODING

CHAPTER 6: SYSTEM MAINTENANCE

6.1. SOFTWARE MAINTENANCE 55

6.2. SYSTEM SECURITY

6.2.1. THREATS TO SYSTEM SECURITY 56

6.2.2. SYSTEM SECURITY MEASURES 56

6.3. SYSTEM TESTING

6.3.1. TESTING STAKEHOLDERS 57

6.4. TESTING STRATEGIES ADOPTED

6.4.1. UNIT TESTING 58

6.4.2. BLACK BOX TESTING 58

6.4.3. WHITE BOX TESTING 58

6.4.4. INTEGRATION TESTING 58

6.4.5. VALIDATION TESTING 59

6.4.6. OUTPUT TESTING 59

6.4.7. USER ACCEPTANCE TESTING 59

6.4.8. REGRESSION TESTING 59

CHAPTER 7: SNAPSHOTS AND RESULT

CHAPTER 8: CONCLUSION & FUTURE WORK

8.1. CONCLUSION & FUTURE WORK

CHAPTER 9: REFERENCES

9.1. REFERENCES

9.1.1. BOOKS REFRENCES

9.1.2. WEB REFRENCES

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD vii

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD viii

List of Figures

Figure 1 Graphical representation of the various stages of a typical SDLC

Figure 2 Prototype Model Phases

Figure 3 Diagrammatic representation of how Training and Placement Portal will work.

Figure 4 DFD Components

Figure 5 DFD (Level 0)

Figure 6 TPO DFD

Figure 7 Student DFD



Figure 10 ER Diagram

Figure 11 Login Sequence Diagram

Figure 12 Student Sequence Diagram

Figure 13 TPO Sequence Diagram

Figure 14 Users of DBMS

Figure 15 Cycle of requests and their associated responses

Figure 16 Three Tier Architecture of ASP.NET

Figure 17 Detailed diagram of Three Tier Architecture

Figure 18 Using multiple objects in the Data Access layer

Figure 19 A typical application with multiple "windows"

Figure 20 Each "window" has its own layers

Figure 21 Multiple Presentation layers sharing a single Business layer and Data Access

layer

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD ix

List of Tables

Table Name Page No

1. UIAccessRights Table 40

2. AccessControlGroups Table 40

3. User Table 40

4. StudentDetails Table 41

5. QualificationDetails Table 42

6. CompanyDetails Table 43

7. JobPosts Table 44

8. JobPostNotices Table 44

9. PlacementRecord Table 44

10. SkillSetMaster Table 45

11. SegmentMaster Table 45

12. StudentRequest Table 45

13. StudentSkills Table 45

TRAINING AND PLACEMENT PORTAL PROJECT REPORT, IPEC, GHAZIABAD 1

Chapter 1:

System Study and Analysis


1.1 Product Information 1.1.1. Product Perspective This project is mainly intended for automating this procedure that can help the people who

belong to the Training and Placement 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 posting job posts on the

intranet and 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. Training and Placement 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 details can also be viewed.

EXISTING SYSTEM AND ITS DRAWBACKS The earlier system is not computerized. All transactions in the system are done manually like

maintaining records. To make this laborious job simple the clients have to computerize the

system.

The management and all the departments that have been carrying out this job using manually

makes the job more complicated and tedious most of the times. So, the best way is computerize

computerization of the current environment.

For example, in the earlier system placement officer has to collect student details for placements.

Approving those student details takes lot of time. Placement officer and students have to consult

each other directly if any information is needed. If any new company come for placements,

placement officer and his staff has to search the student details and they have to find the eligible

candidates for that particular company placement.

Here searching for eligible candidates takes lots of time. And sometimes some candidates details

may be missed.

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).

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).

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.


RECOGNITION OF NEED For the purpose of training and placement of the student in colleges, TPOs have to collect all the information of students and manages them manually and thus arranges the data according to

various streams.

If any modification is required that is to be also done manually. So, to reduce the job required to

manage students data manually and the information of various recruiters, a new system is proposed which is processed through computers.

BOTTLENECKS OF PRESENT WORKING SYSTEM The Job of TPO is a unique task that involves taking into considerations many details. Existing

system has some bottlenecks looked upon by TPOs and students of colleges. They are: i)It takes so much time for a placement officer to collect students details and approving the details provided by them.

ii) Poor communication between students and placement officer, so intimating about new

placements is a hard task.

iii) Students may not know about company details. Here also poor communication provides a

problem.

iv) Candidate may not get required information regarding companies visiting campus and

information about the job(profile) the company is offering.

v) It is a time consuming activity of managing, updating and informing specific student for

specific company requirements.

PROPOSED SOLUTIONS: In the proposed system the TPO 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.

i) Notice generation: Here TPO has to provide information about company name, date and venue

at which campus drive might take place. With this information the portal will generate a notice

which can be seen on students account to intimate students about placement drive. ii) Student list generation: Here the TPO has to provide information about the requirements of

the company (such as, cut off percentage, whether backlogs allowed or not etc.).

iii) View student profile: Here the TPO is able to view a students profile of his interest by giving the students roll number as input. iv) Result analysis: Here the TPO is able to get the results which are released and store them for

later usage.

v) Posts: Here the TPO is provided to post updates or any necessary details to students depending

on his need.

vi) Reduce the paperwork and storage area.

vii) Improve the output of operators.

viii) Improve accuracy in result.

ix) Allow easy navigation through company information.

x) Manage the man and machine resources efficiently.

xi) It has user friendly interface having quick authenticated access to documents.

xii) Secured check in, check out & updates.

xiii) Easily scalable to grow with changing system requirement.


1.1.2 Product Features i) Complete automation is possible in this sector, which is against the main disadvantage namely

time consuming.

ii) Can maintain student details who have been studying in the college.

iii) Any kind of lists based on students profile can be retrieved with in less time.

iv) Results are uploaded directly from the system so that no errors exist in calculating

percentages.

v) Effective and good means of communication can be facilitated mailing module is included in

the proposed system.

vi) TPO can view students profile and also update it as per requirement.

1.1.3. Performance Requirements: i) The completely separate business logic at server side from the student interface ensures good

performance.

ii) The system exhibits high performance because it is well optimized. The business logic is

clearly separate from the User Interface.

iii) The response to the user is within seconds, providing all the information at a glance.


1.2 Requirement Analysis We are overcoming the difficulty of student details which were manual in the current system and

here we generate detailed information about the students which will save our time to inform each

and every batch and section and student profile is maintained.

1.2.1. Functional Requirements Students should be able to login to the system through the first page of the application, by

mentioning their required username and they should be able to view their details and request to

update the same. TPO can login into his account and he/she will update the student information.

It can filter students on the basis of certain criterion. Students as well as companies information

is maintained.

1.2.2. Non Functional Requirements i) Performance requirements

The accountability is a vital feature and this could only be assured if the system is working in full

capability. So uninterrupted power supply is needed.

ii) Safety requirements

The data handled is very vital. The data are saved to the database at consecutive intervals. Power

is a significant feature and the power supply should be always taken care of. An Uninterrupted

Power Supply is always recommended.

iii) Software quality attributes

The source code can be easily modified and the system can be updated easily. This system is

flexible. Necessary changes can be done when needed.

iv) Usability

This section includes all of those requirements that effect usability. We get the response within

seconds. The software must have a simple, user-friendly interface so customers can save time

and confusion.

v) Reliability

The system is more reliable because of the qualities that are inherited from the chosen platform

dot NET. The code built by using dot NET is more reliable.

vi) Supportability

The system is designed to be the cross platform supportable. The system is supported on a wide

range of hardware and any software platform. This application is being developed using Visual

C#, hence it is extremely portable.

vii) Implementation

The system is implemented in web environment. The IIS is used as the web server and windows

XP/vista/7/8/10 is used as the platform.

viii) Interface

The user interface is based on the web browser. The application is developed using Visual C#

and .The Interface design is aimed at a flexible front-end communication to provide the user with

clear information in navigating a user-friendly interface is planned.


1.3. Feasibility Study A feasibility analysis usually involves a thorough 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 economical 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:

i) Technical Feasibility

ii) Economic Feasibility

iii) Scheduled Feasibility

iv) Operational Feasibility

Once you define a problem you have to analyze whether this is feasible or not, because all

possible solutions are not feasible and feasible one is not always possible. The detailed studies

carried out to check the work ability of proposed system. A feasibility study is a test of system

proposal regarding to its work ability, impact on the organization ability to meet user needs an

effective use of resources. Thus when a new application is proposed it normally goes through a

feasibility study before it is approved for deployment.

Thus during feasibility analysis for this project, following primary areas of interest are to be

considered. Investigating the existing system in the area under investigation and generating ideas

about a new system does this.

1.3.1. 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 technically

feasible. Training and Placement System, with its emphasis on a more strategic decision making

process is fast gaining ground as a popular outsourced function.

The study of resource availability that may affect the ability to achieve an acceptable system.

This evaluation determines whether the technology needed for the proposed system is available

or not.

i) It will avoid multiple file handling

ii) Report generation is very easy

iii) The new system provides full security of confidential data


1.3.2. Economical 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:

i) Improvement resulting over the existing method in terms of accuracy, timeliness.

ii) Cost comparison

iii) Estimate on the life expectancy of the hardware.

iv) 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. The system will be

developed and operated in the existing hardware and software infrastructure. So there is no need

for procuring additional hardware and software for the system. The proposed system will replace

the hectic cost and man power involved in the existing system. The employees will be trained in

using and operating the system, thus eliminating the need for recruiting employees. Thus the

project is economically feasible for the development of the company.

1.3.3. Scheduled Feasibility An evaluation of the time, which is to be taken in the development of the project. The time

scheduled for the development of the project is very important since more development time

affects machine time, cost and cause delay in the development of other systems, so the project

should be completed within a fixed scheduled time as the company is concerned. Besides this,

the project is assigned to the student as an academic exercise to complete within a fixed schedule

of time.

1.3.4. 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.


Chapter 2:

Software Requirement Specification (SRS)


2.1. Introduction Software Requirements Specification is a complete description of the behavior of the system to

be developed. It includes asset of use cases that describe all the interactions the users will have

with the software. Use cases are also known as functional requirements. In addition to use cases,

the SRS also contains non-functional (or supplementary) requirements. Non-functional

requirements are requirements which impose constraints on the designer implementation (such as

performance engineering requirements, quality standards, or design constraints)

Training & Placement Portal aims at providing the Facility to automate and simplify the process

of registration and list generation of eligible students for placement. This system provide facility

to TPO to do all their Work Regarding Placement like Collecting Student Records, Registering

the Suitable Students, to check the number and percentage of placed & unplaced students, and

important announcements to other departments. The whole work is automated as well as on

Intranet.

2.1.1. Purpose Computer based information system are designed to improve existing system. Whatever the

information, TPO has to pass to the student and he or she can inform online. Improve accuracy in

result. It has user friendly interface having quick authenticated access to documents. It provides

the facility of maintaining the details of the students. It will reduce the paper work and utilize the

maximum capabilities of the Setup and organization as well as it will save time and money

which are spending in making reports and collecting data. It can be accessed throughout the

organization and outside as well with proper login provided. This system can be used as an

application for college to manage the student information with regards to placement.

2.1.2. Problem Statement This project is aimed at developing an online application for the Training and Placement

Department of the college. The system is an online application that can be accessed throughout

the organization 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 view various job posts posted by TPO.

At present the new entries of company, college and candidates and technical problem are

managed manually. It is time consuming and much paper work is needed, also there are

possibilities of human error, as the transactions are done manually. Fake entries can be there.

System is more error-prone and time consuming. Difficulty in managing huge amount of data of

students. Large piles of records are to be maintained. TPOs have to collect the information of various companies who want to recruit students and notify students time to time about them. It is

a time consuming activity of managing, updating and informing students for specific company

requirements.


2.1.3. Project Objective The aim of the Training & Placement Office is to computerize all the work related with training and its placement. It includes information about TPO and detail of each student. As the

technology is growing at a faster rate, the usage of manual system is reduced. We have planned

to develop automation for Training Placement Cell, this automation is developed based on web

application so the training and placement cell works are processed within the organization with

authorized people. In placement cell, the records are maintained in paper formats, thus it is a

tedious work to short list the students according to the companys requirements. To overcome this problem, records of the students are updated by the authorized TPOr electronically rather

than manually. There will be unique user name and password for the TPOr.

The student only view the details of the records and can ask for updation of some personal

information like his/her contact number, email id. Only the authorized TPOr should have the

rights to insert, delete and update information into the database, thereby filtering candidate for

particular company.

The system proposed by us is beneficial to overcome the problem sited in the Placement. In the

manual, time is taken to prepare the records and the information of all Company and also

difficult to retrieve the information about the particular candidates, hence the computer section is

necessary to achieve perfect goal. Furthermore the human errors occur in the manual system can

be avoided by using the computerized system. The use of database management system is

appropriate in the environmental condition of Training & Placement Office.

2.1.4. Project Scope Project has a big scope to do. We Students can maintain their information and can update it.

Notifications are sent to students about the companies. Students can access previous information

about placement. This system has scope of improvement amendments. In future, sector can

communicate with each other online. All currently active enquires can also be added in the

website to view if online. This application can be modified from time to time as per the changing

requirement of the user with lesser cost. Also the backend of the application can be changed as

per the storage requirement of the application and to provide more security level features.

2.1.5. Operating Environment Operating System : Windows XP Prof. or above.

Processor : Pentium 4, 1.2 GHz or above.

Hard Disk : 40 GB or above.

RAM : 512 MB or above.


2.1.6. Methodology PHASES: i) Initiation Phase

The initiation of a system (or project) begins when a business need or opportunity is identified. A

Project Manager should be appointed to manage the project. This business need is documented in

a Concept Proposal. After the Concept Proposal is approved, the System Concept Development

Phase begins.

ii) System Concept Development Phase

Once a business need is approved, the approaches for accomplishing the concept are reviewed

for feasibility and appropriateness. The Systems Boundary Document identifies the scope of the

system and requires Senior Official approval and funding before beginning the Planning Phase.

iii) Planning Phase

The concept is further developed to describe how the business will operate once the approved

system is implemented, and to assess how the system will impact employee and customer

privacy. To ensure the products and /or services provide the required capability on-time and

within budget, project resources, activities, schedules, tools, and reviews are defined.

Additionally, security certification and accreditation activities begin with the identification of

system security requirements and the completion of a high level vulnerability assessment.

iv) Requirement Analysis Phase

Functional user requirements are formally defined and delineate the requirements in terms of

data, system performance, security, and maintainability requirements for the system. All

requirements are defined to a level of detail sufficient for systems design to proceed. All

requirements need to be measurable and testable and relate to the business need or opportunity

identified in the Initiation Phase.

v) Design Phase

The physical characteristics of the system are designed during this phase. The operating

environment is established, major subsystems and their inputs and outputs are defined, and

processes are allocated to resources. Everything requiring user input or approval must be

documented and reviewed by the user. The physical characteristics of the system are specified

and a detailed design is prepared. Subsystems identified during design are used to create a

detailed structure of the system. Each subsystem is partitioned into one or more design units or

modules. Detailed logic specifications are prepared for each software module.

vi) Development Phase

The detailed specifications produced during the design phase are translated into hardware,

communications, and executable software. Software shall be unit tested, integrated, and retested

in a systematic manner. Hardware is assembled and tested.


vii) Integration and Test Phase

The various components of the system are integrated and systematically tested. The user tests the

system to ensure that the functional requirements, as defined in the functional requirements

document, are satisfied by the developed or modified system. Prior to installing and operating the

system in a production environment, the system must undergo certification and accreditation

activities.

viii) Implementation Phase

The system or system modifications are installed and made operational in a production

environment. The phase is initiated after the system has been tested and accepted by the user.

This phase continues until the system is operating in production in accordance with the defined

user requirements.

i.i) Operations and Maintenance Phase

The system operation is ongoing. The system is monitored for continued performance in

accordance with user requirements, and needed system modifications are incorporated. The

operational system is periodically assessed through In-Process Reviews to determine how the

system can be made more efficient and effective. Operations continue as long as the system can

be effectively adapted to respond to an organizations needs. When modifications or changes are identified as necessary, the system may reenter the planning phase.

ix) Disposition Phase

The disposition activities ensure the orderly termination of the system and preserve the vital

information about the system so that some or all of the information may be reactivated in the

future if necessary. Particular emphasis is given to proper preservation of the data processed by

the system, so that the data is effectively migrated to another system or archived in accordance

with applicable records management regulations and policies, for potential future access.

2.1.7. Design & Implementation Constraints User friendliness is provided in the application with various controls.

The system makes the overall project management much easier and flexible.

It can be accessed over Intranet.

Secured check in, check out & updates.

There is no risk of data mismanagement at any level while the project development is under process.


2.2. Software Development Life Cycle 2.2.1. Introduction to Software Development Life Cycle SDLC, Software Development Life Cycle is a process used by software industry to design,

develop and test high quality software. The SDLC aims to produce a high quality software that

meets or exceeds customer expectations, reaches completion within times and cost estimates. It

is also called as Software development process. The software development life cycle (SDLC) is a

framework defining tasks performed at each step in the software development process.

ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to be the

standard that defines all the tasks required for developing and maintaining software.

SDLC is a process followed for a software project, within a software organization. It consists of

a detailed plan describing how to develop, maintain, replace and alter or enhance specific

software. The life cycle defines a methodology for improving the quality of software and the

overall development process.

Figure 1 Graphical representation of the various stages of a typical SDLC


2.2.2. Stages of Software Development Life Cycle A typical Software Development life cycle consists of the following stages:

Stage 1: Planning and Requirement Analysis Requirement analysis is the most important and fundamental stage in SDLC. It is performed by

the senior members of the team with inputs from the customer, the sales department, market

surveys and domain experts in the industry. This information is then used to plan the basic

project approach and to conduct product feasibility study in the economical, operational, and

technical areas.

Planning for the quality assurance requirements and identification of the risks associated with the

project is also done in the planning stage. The outcome of the technical feasibility study is to

define the various technical approaches that can be followed to implement the project

successfully with minimum risks.

Stage 2: Defining Requirements Once the requirement analysis is done the next step is to clearly define and document the product

requirements and get them approved from the customer or the market analysts. This is done

through .SRS. . Software Requirement Specification document which consists of all the product

requirements to be designed and developed during the project life cycle.

Stage 3: Designing the product architecture SRS is the reference for product architects to come out with the best architecture for the product

to be developed. Based on the requirements specified in SRS, usually more than one design

approach for the product architecture is proposed and documented in a DDS - Design Document

Specification.

This DDS is reviewed by all the important stakeholders and based on various parameters as risk

assessment, product robustness, design modularity , budget and time constraints , the best design

approach is selected for the product.

A design approach clearly defines all the architectural modules of the product along with its

communication and data flow representation with the external and third party modules (if any).

The internal design of all the modules of the proposed architecture should be clearly defined with

the minute details in DDS.

Stage 4: Building or Developing the Product In this stage of SDLC the actual development starts and the product is built. The programming

code is generated as per DDS during this stage. If the design is performed in a detailed and

organized manner, code generation can be accomplished without much hassle.

Developers have to follow the coding guidelines defined by their organization and programming

tools like compilers, interpreters, debuggers etc are used to generate the code. Different high

level programming languages such as C, C++, Pascal, Java, and PHP are used for coding. The

programming language is chosen with respect to the type of software being developed.

Stage 5: Testing the Product This stage is usually a subset of all the stages as in the modern SDLC models, the testing

activities are mostly involved in all the stages of SDLC. However this stage refers to the testing

only stage of the product where products defects are reported, tracked, fixed and retested, until

the product reaches the quality standards defined in the SRS.


Stage 6: Deployment in the Market and Maintenance Once the product is tested and ready to be deployed it is released formally in the appropriate

market. Sometime product deployment happens in stages as per the organizations. business

strategy. The product may first be released in a limited segment and tested in the real business

environment (UAT- User acceptance testing).

Then based on the feedback, the product may be released as it is or with suggested enhancements

in the targeting market segment. After the product is released in the market, its maintenance is

done for the existing customer base.

2.2.3. Software Development Life Cycle Models There are various software development life cycle models defined and designed which are

followed during software development process. These models are also referred as "Software

Development Process Models". Each process model follows a Series of steps unique to its type,

in order to ensure success in process of software development.

Following are the most important and popular SDLC models followed in the industry:

i) Build and Fix Model

ii) Waterfall Model

iii) Iterative Model

iv) Spiral Model

v) Prototype Model

The other related methodologies are Agile Model, RAD Model, Rapid Application Development

and Prototyping Models.


2.2.4. Process Model Adopted The model that we used in implementation of TRAINING and PLACEMENT PORTAL is

Software Prototype Model. This model is explained as below.

The Software Prototyping refers to building software application prototypes which display the

functionality of the product under development but may not actually hold the exact logic of the

original software.

Software prototyping is becoming very popular as a software development model, as it enables

to understand customer requirements at an early stage of development. It helps get valuable

feedback from the customer and helps software designers and developers understand about what

exactly is expected from the product under development.

Prototyping is used to allow the users evaluate developer proposals and try them out before

implementation. It also helps understand the requirements which are user specific and may not

have been considered by the developer during product design.

Figure 2 Prototype Model Phases

Requirements Gathering

Quick Design

Refine requirements

incorporating

customer satisfaction

Build Prototype

Customer Evaluation

Design

Implementation and Unit Testing

Integration and System Testing

Operation and Maintenance


Following is the stepwise approach to design a software prototype:

i) Basic Requirement Identification: This step involves understanding the very basics product

requirements especially in terms of user interface. The more intricate details of the internal

design and external aspects like performance and security can be ignored at this stage.

ii) Developing the Initial Prototype: The initial Prototype is developed in this stage, where the

very basic requirements are showcased and user interfaces are provided. These features may not

exactly work in the same manner internally in the actual software developed and the

workarounds are used to give the same look and feel to the customer in the prototype developed.

iii) Review of the Prototype: The prototype developed is then presented to the customer and the

other important stakeholders in the project. The feedback is collected in an organized manner

and used for further enhancements in the product under development.

iv) Revise and enhance the Prototype: The feedback and the review comments are discussed

during this stage and some negotiations happen with the customer based on factors like , time

and budget constraints and technical feasibility of actual implementation. The changes accepted

are again incorporated in the new Prototype developed and the cycle repeats until customer

expectations are met.

Prototypes can have horizontal or vertical dimensions. Horizontal prototype displays the user

interface for the product and gives a broader view of the entire system, without concentrating on

internal functions. A vertical prototype on the other side is a detailed elaboration of a specific

function or a sub system in the product.

The purpose of both horizontal and vertical prototype is different. Horizontal prototypes are used

to get more information on the user interface level and the business requirements. It can even be

presented in the sales demos to get business in the market. Vertical prototypes are technical in

nature and are used to get details of the exact functioning of the sub systems. For example,

database requirements, interaction and data processing loads in a given sub system.

Software Prototyping Types: There are different types of software prototypes used in the industry. Following are the major

software prototyping types used widely:

i) Throwaway/Rapid Prototyping: Throwaway prototyping is also called as rapid or close

ended prototyping. This type of prototyping uses very little efforts with minimum requirement

analysis to build a prototype. Once the actual requirements are understood, the prototype is

discarded and the actual system is developed with a much clear understanding of user

requirements.

ii) Evolutionary Prototyping: Evolutionary prototyping also called as breadboard prototyping is

based on building actual functional prototypes with minimal functionality in the beginning. The

prototype developed forms the heart of the future prototypes on top of which the entire system is

built. Using evolutionary prototyping only well understood requirements are included in the

prototype and the requirements are added as and when they are understood.

iii) Incremental Prototyping: Incremental prototyping refers to building multiple functional

prototypes of the various sub systems and then integrating all the available prototypes to form a

complete system.


iv) Extreme Prototyping: Extreme prototyping is used in the web development domain. It

consists of three sequential phases. First, a basic prototype with all the existing pages is

presented in the html format. Then the data processing is simulated using a prototype services

layer. Finally the services are implemented and integrated to the final prototype. This process is

called Extreme Prototyping used to draw attention to the second phase of the process, where a

fully functional UI is developed with very little regard to the actual services.

Software Prototyping Application

Software Prototyping is most useful in development of systems having high level of user

interactions such as online systems. Systems which need users to fill out forms or go through

various screens before data is processed can use prototyping very effectively to give the exact

look and feel even before the actual software is developed.

Software that involves too much of data processing and most of the functionality is internal with

very little user interface does not usually benefit from prototyping. Prototype development could

be an extra overhead in such projects and may need lot of extra efforts.

Advantages of Prototype model i) Users are actively involved in the development

ii) Since in this methodology a working model of the system is provided, the users get a better

understanding of the system being developed.

iii) Errors can be detected much earlier.

iv) Quicker user feedback is available leading to better solutions.

v) Missing functionality can be identified easily

vi) Confusing or difficult functions can be identified

vii) Requirements validation, Quick implementation of, incomplete, but

functional, application.

Disadvantages of Prototype model i) Leads to implementing and then repairing way of building systems.

ii) Practically, this methodology may increase the complexity of the system as scope of the

system may expand beyond original plans.

iii) Incomplete application may cause application not to be used as the

full system was designed

iv) Incomplete or inadequate problem analysis.

When to use Prototype model Prototype model should be used when the desired system needs to have a lot of interaction with

the end users.

Typically, online systems, web interfaces have a very high amount of interaction with end users,

are best suited for Prototype model. It might take a while for a system to be built that allows ease

of use and needs minimal training for the end user.

Prototyping ensures that the end users constantly work with the system and provide a feedback

which is incorporated in the prototype to result in a useable system. They are excellent for

designing good human computer interface systems.


2.2.5. System Features i) Simplicity Although it may seem old-fashioned, the aphorism all things in moderation applies to web apps. There is tendency among some designers to provide the end-user with too much-exhaustive content, extreme visuals, intrusive animation, enormous web pages.

ii) Consistency This design goal applies to virtually every element of the design model. Content should be

constructed consistently. Graphic design should present a consistent look across all parts of the

web app. Architectural Design should establish templates that led to consistent hypermedia

structures.

iii) Identity The aesthetic, interface, and navigational design of a web app must be consistent with the

application domain for which it is to be built. The web app architecture will be entirely different

interfaces will be constructed to accommodate different categories of users; navigation will be

organized to accomplish different objectives.

iv) Robustness Based on the identity that has been established, a web app often makes an implicit promise to a user. The user expects robust content and functions that are relevant to the users need.

v) Compatibility A web app will be used in a variety of environment (e.g. different hardware, operating

System) and must be designed to be compatible with each.


2.3. External Interface Requirements 2.3.1. User Interfaces TPO: This module contains all the information about the TPO. He can add all the students as

well as company that is going to visit campus for the recruitment. TPO can post jobs. Allow TPO

to verify the details of the student, and to approve the same if their request is correct. TPO can

also filter the students on the basis of criterion led down by the company and can communicate

with those students via emails or messages. Allow TPO to insert/update statistics like no. of

students placed. Allow TPO to add/insert an events. Also allow TPO to upload materials (like

notices related with job posts).

Student: This module contains all the information related to the students. Students are the

registered person who will edit their personal details like their contact numbers, email ids. They can also request for updation of their particular details like their marks. They can also see the list

of companies visiting the campus.

Company: This module contains all the information related to various companies visiting the

campus.

Guest: The guests can be Directors, HODs of various departments, or the faculties, they can view the statistics of placements till date. Statistics can be viewed to them in various perspectives

like batch wise, branch wise, percentage wise.

Figure 3: Diagrammatic representation of how Training and Placement Portal work.


2.3.2. Hardware Interfaces Processor -------- Pentium 4, 1.2 GHz or above.

Hard Disk: -------- 40 GB or above.

RAM: -------- 1GB or above.

2.3.3. Software Interfaces Operating System: Windows 2007/xp/2010

Backend: SQL Server 2012

Frontend: Visual Studio 2010

Server: IIS

Scripting Languages: JavaScript

Server Side Scripting: Asp.net

Markup Languages: HTML, XML

(To be discussed)


Chapter 3:

SYSTEM DESIGNING


System design Software analysis and design includes all activities, which help the transformation of

requirement specification into implementation. Requirement specifications specify all functional

and non-functional expectations from the software. These requirement specifications come in the

shape of human readable and understandable documents, to which a computer has nothing to do.

Software analysis and design is the intermediate stage, which helps human-readable

requirements to be transformed into actual code.

The design data structure, software architecture, software architecture, software representation

and procedure detail is specified. The design process translate requirement into a representation

if the software. The suggested system is Establishment. Design is the process of applying the various techniques and principles for the purpose of defining a device, a process or a system in

sufficient detail to permit its physical realization.

The system design is carried out in two phases:-

i) The architecture design (High Level Design)

ii) The detailed design (Low Level Design)

High Level Design:- The high level design, describes the actual processes of the system, i.e. the information flow of

the system. In this phase we identified all the entities or in other words we can say external

source. That is, in this phase we represent flow graphically, this is known as DFD (Data Flow

Diagram).

Low Level Design:- In the low level design, first we collect all the data in the form of tables. The name of entity is

taken as the name of tables. The process is known as Fast Patch Table. The next important step

after the designing of tables is actual coding of the program. The code of program is written and

tested separately.


3.1. DATA FLOW DIAGRAMS Data flow diagram is graphical representation of flow of data in an information system. It is

capable of depicting incoming data flow, outgoing data flow and stored data. The DFD does not

mention anything about how data flows through the system.

It is a graphic tool used to describe and analyze the moment of data through a system manualor automated including the processes, stores of data, and delays in the system. Data flow diagrams are the central tools and the basis from which other components are developed.

The transformation of data from input to output, through processes, may be described logically

and independently of the physical components associated with the system.

Data Flow Diagram is a means of representing a system at any level of detail with a graphic

network of symbols showing data flows, data stores, data processes and data sources.

The purpose of data flow diagram is to provide a semantic bridge between users and system

developers. The diagram is the basis of structured system analysis. A DFD describes what data

flows rather than how they are processed, so it does not depend on hardware, software, data

structure or file organization.

There is a prominent difference between DFD and Flowchart. The flowchart depicts flow of

control in program modules. DFDs depict flow of data in the system at various levels. DFD does

not contain any control or branch elements.

Types of DFD .i) Logical DFD - This type of DFD concentrates on the system process, and flow of data in the

system. For example in a Banking software system, how data is moved between different

entities.

ii) Physical DFD - This type of DFD shows how the data flow is actually implemented in the

system. It is more specific and close to the implementation.

DFD Components DFD can represent Source, destination, storage and flow of data using the following set of

components -

Figure 4 DFD Components

Entities - Entities are source and destination of information data. Entities are represented

by a rectangle with their respective names.

Process - Activities and action taken on the data are represented by Circle or Round-

edged rectangles.

Data Storage - There are two variants of data storage - it can either be represented as a

rectangle with absence of both smaller sides or as an open-sided rectangle with only one

side missing.

Data Flow - Movement of data is shown by pointed arrows. Data movement is shown

from the base of arrow as its source towards head of the arrow as destination.



Figure 6 TPO DFD

Figure 7 Student DFD


3.2. Entity Relationship Diagram An entity-relationship diagram (ERD) is a data modeling technique that graphically illustrates an

information systems entities and the relationships between those entities. An ERD is a conceptual and representational model of data used to represent the entity framework

infrastructure.

The elements of an ERD are: Entities, Relationships, Attributes.


3.3. Sequence Diagrams: A sequence diagram is an interaction diagram. From the name it is clear that the diagram deals

with some sequences, which are the sequence of messages flowing from one object to another.

Interaction among the components of a system is very important from implementation and

execution perspective.

So Sequence diagram is used to visualize the sequence of calls in a system to perform a specific

functionality.

UML sequence diagrams are used to show how objects interact in a given situation. An

important characteristic of a sequence diagram is that time passes from top to bottom: the

interaction starts near the top of the diagram and ends at the bottom (i.e. Lower equals Later).

A popular use for them is to document the dynamics in an object-oriented system. For each key

collaboration, diagrams are created that show how objects interact in various representative

scenarios for that collaboration.

Login Sequence Diagram

Figure 11 Login Sequence Diagram


Student Sequence Diagram:

Figure 12 Student Sequence Diagram


TPO Sequence Diagram

Figure 13 TPO Sequence Diagram


3.4. DATABASE DESIGN Data base is designed to manage large bodies of information. The management of data involves

both the definitions of structures for the storage of information. In addition the data base system

must provide for the safety of the information solved, despite system crashes or due to attempts

at unauthorized access. For developing an efficient database we have to fulfill certain conditions

such as controlled redundancy.

i) Defining the data

ii) Inputting the data

iii) Locating the data

iv) Accessing the data

v) Communicating the data

vi) Revising the data

Objectives of Data base design

In this data base design several objectives are designed such as :

i) Ease of use

ii) Control of data integrity

iii) Control of redundancy

iv) Control of security

v) Data independence (logical & physical)

vi) Data storage protection

vii) System performance

viii) System functions

ix) System compatibility

For achieving the abovementioned criterias we have to make use of various features that are available with the RDBMS by enforcing integrity constrains, we can ensure data integrity and

reduce data inconsistency to a great extend.

DATA DICTIONARY A data dictionary is a catalogue a repository of the elements in a system. As the name suggests, these elements center on data the way they are structured to meet user requirements and

organization needs. In a data dictionary you will find a list of all the elements composing the data

flow through a system.


3.7. Tables

AccessControlGroups Table

Fields Data Type Size Description Constraints

AccessControlGroupId int Access Control Group Id Primary Key

Name varchar 100 Name

Description varchar 200 Description

ModTs

UIAccessRights Table


AccessControlGroupId int Access Control Group Id

SecurityProfileId int Security Profile Id

CollegeId int College Id NOT NULL

[view] bit view NOT NULL

Edit bit Edit NOT NULL

ModTs

User Table


UniqueId uniqueidentifier Unique Id Primary Key

CollegeId int College Id NOT NULL

UserId varchar 15 User Id NOT NULL

Name varchar 50 Name NOT NULL

SecurityProfileId int Security Profile Id NOT NULL

Salt varchar 50 Salt NOT NULL

SaltedHashed varchar MAX Salted Hashed NOT NULL

IsActive bit Is Active

ModTs


StudentDetails Table

Fields Data Types Size Description Constraints

StudentId int Student Id Primary Key

FullName nvarchar 20 Full Name

ActualName nvarchar 50 Actual Name

FirstName nvarchar 15 First Name

MiddleName nvarchar 15 Middle Name

LastName nvarchar 15 Last Name

FatherName nvarchar 50 Father Name

Dob datetime Dob

Sex varchar 6 Sex

AddressCorrespondence nvarchar 250 Address Correspondence

ContactNo nvarchar 100 Contact No

PermanentAdd nvarchar 250 Permanent Address

PermanentContact nvarchar 100 Permanent Contact

MobileNum nvarchar 20 Mobile Number

EmailId nvarchar 50 Email Id

StudentPinNo varchar 12 Student Pin No

RollNo char 15 Roll No

EnrollmentNo char 15 Enrollment No

AdmissionNum nvarchar 50 Admission Number

AdmissionSessionId int Admission Session Id

StatusId int Status Id NOT NULL

SessionId int Session Id NOT NULL

CourseId int Course Id NOT NULL

SemesterId int Semester Id NOT NULL

YearId int Year Id NOT NULL

ModTs ModTs


QualificationDetails Table


IdQualification int Qualification Id Primary Key

StudentId int Student Id

TenthBoard nvarchar 100 Tenth Board

TenthMedium nvarchar 10 Tenth Medium

TenthPassingYear nvarchar 10 Tenth Passing Year

TenthPercentageGrade nvarchar 25 Tenth Percentage Grade

TwelthBoard nvarchar 100 Twelfth Board

TwelthMedium nvarchar 10 Twelfth Medium

TwelthPassingYear nvarchar 10 Twelfth Passing Year

TwelthPercentageGrade nvarchar 25 Twelfth Percentage Grade

GraduationUniversity nvarchar 100 Graduation University

GraduationMedium nvarchar 10 Graduation Medium

GraduationPassingYear nvarchar 10 Graduation Passing Year

GraduationPercentGrade nvarchar 25 Graduation Percent Grade

PostGradUniv nvarchar 100 Post Graduation University

PostGradMedium nvarchar 10 Post Graduation Medium

PostGradPassingYear nvarchar 10 Post Graduation Passing Year

PostGradPercentGrade nvarchar 25 Post Graduation Percent Grade

DiplomaUniversity nvarchar 100 Diploma University

DiplomaMedium nvarchar 10 Diploma Medium

DiplomaPassingYear nvarchar 10 Diploma Passing Year

DiplomaPercentGrade nvarchar 25 Diploma Percent Grade

DiplomaMarksheet bit Diploma Marksheet

GraduationMarksheet bit Graduation Marksheet

GapCertificate bit Gap Certificate

TenthMarksheet bit Tenth Marksheet

TenthCertificate bit Tenth Certificate

TwelthMarksheet bit Twelfth Marksheet

TwelthCertificate bit Twelfth Certificate

DegreeCertificate bit Degree Certificate

DiplomaCertificate bit Diploma Certificate

Per_ten decimal(18,2) ****Percentage

ModTs ModTs


CompanyDetailsTable


CompanyId uniqueidentifier Company Id Primary Key

CompanyName varchar 200 Company Name NOT NULL

CompanyLogo image Company Logo

CompanyWebsite varchar 100 Company Website

CompanyHeadquarter varchar 20 Company Headquarter

PhoneNo varchar 20 Phone Number

Fax varchar 20 Fax No

Email varchar 50 Email Address NOT NULL

CompanyProfile text Company Profile

ModTs datetime

JobPosts Table


JobPostId uniqueidentifier Job Post Id Primary Key

CompanyId uniqueidentifier Company Id FK(CompanyDetails)

SegmentId int Segment Id

Designation varchar 50 Designation

AnnualSalary varchar MAX Annual Salary

JoiningLocation varchar 50 Joining Location

JobDetails text Job Details

EventVenue varchar 100 Event Venue

EventDate date Event Date

ValidUpto date Valid Upto

JobPostDate date Job Post Date NOT NULL

PlacementType varchar 50 Placement Type NOT NULL

BondPeriod varchar 50 Bond Period

TrainingPeriod varchar 50 Training Period

EventTime varchar 10 Event Time

ValidUptoTime varchar 10 Valid Upto Time

ModTs


JobPostNotices Table


JobPostNoticeId uniqueidentifier Job Post Notice Id Primary Key

JobPostId uniqueidentifier Job Post Id FK(JobPosts)

Description varchar MAX Job Description NOT NULL

Link varchar 80 Apply Link NOT NULL

JobPostNoticeDate date Job Post Notice Date NOT NULL

ModTs

PlacementRecord Table


StudentId int Student Id

JobPostId uniqueidentifier Job Post Id

PostedOn date Job Posted Date NOT NULL

PlacementTrackId varchar 5 Placement Track Id NOT NULL

ModTs NOT NULL

SkillSetMaster Table


SkillSetId varchar 5 Skill Set Id Primary Key

SkillDetails varchar 50 Skill Details NOT NULL

ModTs


SegmentMaster Table

Fields Data Type Size Description Fields

SegmentId int Segment Id Primary Key

SegmentName char(100) 100 Segment Name NOT NULL

ModTs

StudentRequest Table


RequestId uniqueidentifier RequestId Primary Key

StudentId int StudentId FK(StudentDetails)

UpdateField varchar 50 UpdateField NOT NULL

UpdateValue varchar 100 UpdateValue NOT NULL

ModTs

StudentSkills Table


StudentSkillId uniqueidentifier Student Skill Id Primary Key

StudentId int Student Id FK(StudentDetails)

SkillSetId varchar 5 Skill Set Id

Experience int Experience

ModTs


CHAPTER 4:

THEORETICAL BACKGROUND


4.1. Introduction to Front End 4.1.1. About the Platform (Visual C#): C# (pronounced "C-sharp") is an object-oriented programming language from Microsoft that

aims to combine the computing power of C++ with the programming ease of Visual Basic. C# is

based on C++ and contains features similar to those of Java.

C# is designed to work with Microsoft's .Net platform. Microsoft's aim is to facilitate the

exchange of information and services over the Web, and to enable developers to build

highly portable applications. C# simplifies programming through its use of Extensible Markup

Language (XML) and Simple Object Access Protocol (SOAP) which allow access to a

programming object or method without requiring the programmer to write additional code for

each step. Because programmers can build on existing code, rather than repeatedly duplicating it,

C# is expected to make it faster and less expensive to get new products and services to market.

Microsoft is collaborating with ECMA, the international standards body, to create a standard for

C#. International Standards Organization (ISO) recognition for C# would encourage other

companies to develop their own versions of the language. Companies that are already using C#

include Apex Software, Bunka Orient, Component Source, devSoft, Far Point Technologies,

LEAD Technologies, Proto View, and Seagate Software.

4.1.2. Developing an application in Visual C# It takes only few minutes to build an application in Visual C# application you create the user

interface by drawing the controls on the form. For example: text boxes, command buttons, check

boxes etc. Next you set the properties for the form and the controls on your form. You can

specify the multiple values such as caption (name for any control to be displayed) color and size.

Finally, you have written some code and your application is ready to run you can run it and test it

before final use of .exe file.

Event Driven Programming Visual C# is object based language which means it works around the objects created by the user

or those which are pre-defined and it is event driven which all the activities in a program is

triggered on the occurrence of a particular event. Each object has its own properties determining

its position, size, color and the type of text its takes fonts etc. Each object has its own event

handling procedure. The Visual C# system knows all about these already. It knows that this is a

button and how it works. It also knows how to handle the images and all the menus, dialog

boxes, drives and directories and all the stuff which is included within the package. We just have

to tell it through the programming that what to do and when to do it i.e. what command it has to

execute at which event. For instance - a widow closes on the click event of exit button. We dont have to write anything about these events the Visual C# knows how much events can be

performed on any object; a programmers job is to just write the action to be performed on that event. The process of program design reflects the nature of the system. In the Visual C# we have

saved in the form of project a project can have multiple forms, modules & so on.


Forms Control menus: The first step to creating an application with Visual C# is to create with interface. The visual part

of the application with which user will interact. Forms & controls are the basic building blocks

used to create an interface. These are the object that we will work with to build our application.

By setting the properties, of the forms and writing the visual code to respond to its events, you

customize the objects to meet the requirements of your application.

Controls are objects that are contained within the forms object. Each type of control has its own

set of properties, methods and events that make it suitable for entering or displaying the text.

Other controls let you access other applications and process data as if the remote application was

part of your code. To create an application with visual C#, you work with projects. A project is

the collection of all the files that you use to build an application.

When you create an application, you will usually create new forms. You might also reuse of

modify of forms that were created for previous projects. The same is true for objects from other

applications can also be shared between the projects.+

After all of the basic building blocks of visual C# application, the actual windows with which a

user interacts when they run the application. Forms have their own properties, events & methods

with which you can control their appearance & behavior.

Microsoft Visual Studio is an Integrated Development Environment (IDE) from Microsoft. It can

be used to develop console and graphical user interface applications along with Windows

Forms applications, web sites, web applications, and web services in both native code together

with managed code for all platforms supported by Microsoft Windows, Window Mobile,

Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silverlight. Visual

Basic 9.0 was released together with the Microsoft .NET Framework 3.5 on 19 November 2007.

ASP.NET is a set of Web development tools offered by Microsoft. Programs like Visual Studio

.NET and Visual Web Developer allow Web developers to create dynamic websites using a

visual interface. ASP.NET also supports Visual Basic .NET, Jscript, .NET and open-source

languages like Python and Perl. .NET provides a visual interface for developers to create their

applications, which makes .NET a reasonable choice for designing Web-based interfaces as well.

SQL Server is a relational database developed and sold by Microsoft. Originally bought from

Sybase, Microsoft have released versions 6, 6.5, 7, 2000 and 2005. The Express Edition of SQL

Server 2005 is used in the C++ and C#.


4.1.3. Common Features Microsoft added many features including:

i) Debugging the .NET source code

VS2008 has integrated debugging support so that you can step into the framework libraries.

Visual Studio will automatically download the source file from Microsofts server and you will get full watch and breakpoint support.

ii) Visual Studio Split View

It is becoming increasingly more common to have multiple monitors on developers desks.

Building on the split window feature of VS 2005, Visual Studio 2008 now allows you to tile the window horizontally or vertically so you can split your design and code view across monitors

iii) C# 3.0 support

Things like automatic properties, lambda expressions (which reduce your typing for anonymous

delegates), partial methods, anonymous types and extension methods will radically change how

you can build applications. They will cut down your typing and provide for some really cool

ways to enhance and evolve your projects.

iv) Refactoring enhancements

The refactoring support was a welcome addition to VS 2005 - and Microsoft has enhanced the

support in 2008 to support C# 3.0 features and allow you to refactor anonymous types, extension

methods and lambda expressions.

v) Organize your "using" statements

Visual Studio now has the ability to organize your using statements. As a project evolves, you

often end up with a ton of using statements at the top of each file which are not really being used

- either because the project template added it, or because you originally did use something from

that namespace which was then removed later. Now you can right click on your using statements

and sort and/or remove unused namespaces.

vi) Better IntelliSense support

Visual Studio now has IntelliSense and code completion support! Its smart enough to look at the underlying type currently assigned and correctly infer the methods which are available. Visual

Studio will also look at the comments applied to your methods- just like in C# and VB.NET, it

will pull descriptions out of XML based comments on your JavaScript methods and display

descriptions as tooltips when you are navigating the IntelliSense dropdown. Now if you press a

letter and start typing, it will begin to restrict your choices displayed, not just scroll to that

section. This filters the output and makes it easier to find what you are looking for.

vii) Multi-framework targeting

This release of Visual Studio has a much-needed feature that I wish had been there before - the

ability to target multiple versions of .NET. Specifically, you can select your target framework

(2.0 SP1, 3.0 or 3.5) and the project types, toolbox, references, IntelliSense and features will be

appropriately set to that version. This selection can occur during project creation - in the project

templates dialog or on the project properties dialog. Be aware that selecting .NET Framework

2.0 actually means 2.0 SP1 and not the original .NET 2.0 framework released with Visual Studio

2005.


4.2. INTRODUCTION TO BACK END 4.2.1. Introduction to Database Management System Database is a collection of related data and data is a collection of facts and figures that can be

processed to produce information.

Mostly data represents recordable facts. Data aids in producing information, which is based on

facts. For example, if we have data about marks obtained by all students, we can then conclude

about toppers and average marks.

A Database Management System stores data in such a way that it becomes easier to retrieve,

manipulate, and produce information.

To build up any application or any software, which is to be implemented, the database performs

very important role. We should know about database how to make database, how to establish the

relation between database & how to implement these functions for making good and efficient

software. For the project of Training & Placement Portal, as it is a System Software, so we have

taken SQL Server 2000 database for building application database. Thus it is necessary to talk

about this database system. It is also important to think what is the purpose of creating database.

Here are some key features like tables, fields and expression of SQL Server which is being taken

by us as a back end.

Characteristics Traditionally, data was organized in file formats. DBMS was a new concept then, and all the

research was done to make it overcome the deficiencies in traditional style of data management.

A modern DBMS has the following characteristics i) Real-world entity A modern DBMS is more realistic and uses real-world entities to design its architecture. It uses the behavior and attributes too. For example, a school database may use

students as an entity and their age as an attribute.

ii) Relation-based tables DBMS allows entities and relations among them to form tables. A user can understand the architecture of a database just by looking at the table names.

iii) Isolation of data and application A database system is entirely different than its data. A database is an active entity, whereas data is said to be passive, on which the database works and

organizes. DBMS also stores metadata, which is data about data, to ease its own process.

iv) Less redundancy DBMS follows the rules of normalization, which splits a relation when any of its attributes is having redundancy in values. Normalization is a mathematically rich and

scientific process that reduces data redundancy.

v) Consistency Consistency is a state where every relation in a database remains consistent. There exist methods and techniques, which can detect attempt of leaving database in inconsistent

state. A DBMS can provide greater consistency as compared to earlier forms of data storing

applications like file-processing systems.

vi) Query Language DBMS is equipped with query language, which makes it more efficient to retrieve and manipulate data. A user can apply as many and as different filtering options as

required to retrieve a set of data. Traditionally it was not possible where file-processing system

was used.

vii) ACID Properties DBMS follows the concepts of Atomicity, Consistency, Isolation, and Durability (normally shortened as ACID). These concepts are applied on transactions, which

manipulate data in a database. ACID properties help the database stay healthy in multi-

transactional environments and in case of failure.


viii) Multiuser and Concurrent Access DBMS supports multi-user environment and allows them to access and manipulate data in parallel. Though there are restrictions on transactions

when users attempt to handle the same data item, but users are always unaware of them.

ix) Multiple views DBMS offers multiple views for different users. A user who is in the Sales department will have a different view of database than a person working in the Production

department. This feature enables the users to have a concentrate view of the database according

to their requirements.

x) Security Features like multiple views offer security to some extent where users are unable to access data of other users and departments. DBMS offers methods to impose constraints while

entering data into the database and retrieving the same at a later stage. DBMS offers many

different levels of security features, which enables multiple users to have different views with

different features. For example, a user in the Sales department cannot see the data that belongs to

the Purchase department. Additionally, it can also be managed how much data of the Sales

department should be displayed to the user. Since a DBMS is not saved on the disk as traditional

file systems, it is very hard for miscreants to break the code.

Users A typical DBMS has users with different rights and permissions who use it for different

purposes. Some users retrieve data and some back it up.

Figure 14: Users of DBMS

TPO TPO maintain the DBMS and are responsible for administrating the database. They are responsible to look after its usage and by whom it should be used. They create access profiles for

users and apply limitations to maintain isolation and force security. TPO also look after DBMS

resources like system license, required tools, and other software and hardware related

maintenance.

Designers Designers are the group of people who actually work on the designing part of the database. They keep a close watch on what data should be kept and in what format. They identify

and design the whole set of entities, relations, constraints, and views.

End Users End users are those who actually reap the benefits of having a DBMS. End users can range from simple viewers who pay attention to the logs or market rates to sophisticated

users such as business analysts.


4.2.2. SQL Server 2000 Database Microsoft SQL Server 2000 is a full-featured relational database management system (RDBMS)

that offers a variety of administrative tools to ease the burdens of database development,

maintenance and administration.

The six frequently used tools of SQL Server are as follows:-

i) Enterprise Manager:

Enterprise Manager is the main administrative console for SQL Server installations. It provides

you with a graphical "birds-eye" view of all of the SQL Server installations on your network.

You can perform high-level administrative functions that affect one or more servers, schedule

common maintenance tasks or create and modify the structure of individual databases.

ii) Query Analyzer:

Query Analyzer offers a quick and dirty method for performing queries against any of your SQL

Server databases. It's a great way to quickly pull information out of a database in response to a

user request, test queries before implementing them in other applications, create/modify stored

procedures and execute administrative tasks.

iii) SQL Profiler:

SQL Profiler provides a window into the inner workings of your database. You can monitor

many different event types and observe database performance in real time. SQL Profiler allows

you to capture and replay system "traces" that log various activities. It's a great tool for

optimizing databases with performance issues or troubleshooting particular problems.

iv) Service Manager:

Service Manager is used to control the MS-SQL Server (the main SQL Server process), MSDTC

(Microsoft Distributed Transaction Coordinator) and SQL Server Agent processes. An icon for

this service normally resides in the system tray of machines running SQL Server. You can use

Service Manager to start, stop or pause any one of these services.

v) Data Transformation Services:

Data Transformation Services (DTS) provide an extremely flexible method for importing and

exporting data between a Microsoft SQL Server installation and a large

TNPProjectReport(APril 19)

Documents

Transcript of TNPProjectReport(APril 19)