CHAPTER 1

INTRODUCTION

An intranet is a private computer network that uses Internet Protocols technologies to securely share any part of an organization's information or network operating systems within that organization. The term is used in contrast to internet, a network between organizations, and instead refers to a network within an organization. Sometimes the term refers only to the organization's internal website, but may be a more extensive part of the organization's information technology infrastructure. It may host multiple private websites and constitute an important component and focal point of internal communication and collaboration. An intranet can be understood as a private analog of the Internet, or as a private extension of the Internet confined to an organization. Intranets are being used to deliver tools and applications, e.g., collaboration. Intranets are also being used as corporate culture-change platforms. For example, large numbers of employees discussing key issues in an intranet forum application could lead to new ideas in management, productivity, quality, and other corporate issues.

Intranet Site MITS is specially for college Mahakal Institute of Technology and Science. It contains all the information related to the institute and can be accessed within the institute only. It contains information that is need to be informed to the faculties, students and staff of the institute. This site also contains the feature of mailing. Employees may link to relevant information at their convenienc.

This is an application that is being developed in ASP.net

1.1Aim

The aim of the project is to explore the technologies, which are at the helm of the computer science, and to get a better understanding of processes and project management practices.

This project attempts at a understanding of the technologies starting from analysis and design of the system using Object-oriented approach, then using them for documenting the findings of the system, after this, converting the design into the product using the C#

programming language with ASP.Net technology and developing the creative user interface with business logic.

1.2 Objectives

The requirements have been gathered from various personnel who manages the intranet site. They are also based on the requests recorded from various institutes and students.

The objectives of this project are as follows:

Main goal of making this site is to provide the institute with a simple site that can be accessed easily and fulfil the needs of the people related with the institute. This can also help users to locate and view information faster and use applications relevant to their roles and responsibilities, this helps to distribute the information

To systematically study the functionalities those are required while programming.

To record and analyze the requirements of data sharing and information needs

To bring out a detailed system requirement specification report.

Plan all resources required to develop the project.

Design logical model suitable for implementation.

Develop a friendly user interface to enable convenient user interaction.

Test the durability of the system and modify as suggested.

Scientifically manage the project development life cycle with mix model approach.

Present an easy to understand documentation and help resource.

1.3 Goals

Reusability:

Reusability is possible as and when we require in this application. We can update it in next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects.

Extensibility:

This software is developed in ways that its enhancers may not expect. The following principles enhance extensibility like Hide data structure, avoid traversing multiple links or methods, Avoid case statements on object type and distinguish public and private operations.

Robustness:

Its method is robust if it does not fail even if it receives improper parameters. There are some facilities like Protect against errors, Optimize after the program runs, validating arguments and Avoid predefined limits.

Understandability:

A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We have used the methods, which are small and coherently helps to accomplish this.

1.4 Existing System

It was clear that College must have complete and reliable evidence of its activities, and that student, College staff and Fellows must have the information they need, when they need it, to enable them to do their jobs effectively. The present system is very time consuming as well as redundant and inconvenient with respect to communication. Many problems are encountered while work is done in the present system.

Conventionally, campus recruitment phases have following activities:

The colleges negotiate with recruiting companies to conduct a campus placement drive in their places.

The TPOs of those colleges are informed about the drive who can participate in it.

Then, the TPOs shortlist their students as per the company’s criteria and inform them.

Later, the students appear in the drive and the companies select them.

This entire task is done manually and through telephonic conversation. There is no easy way to inform students. It is costly and time consuming for college.

The above mentioned points in itself make this process quite complicated and difficult for every student and even worse for colleges and companies.

1.4.1 Problem Definition

The main problem faced by the students is that sometimes the students are not informed on time about the campus drives, college activities also, the college staff member and faculty find it difficult to communicate. Some other problems are:-

Redundancy- The student information and staff member data is maintained on paper and there is redundancy of data at colleges end. Data gets redundant at various stages in manually handling the system.

Search Difficult-There are various records and information which need to be searched according to different criteria. It’s a mammoth task to search these records in the present system.

Scope for Manipulation and Error- In the present system there is a possibility of error. The storage of correct and updated information of student’s, staff member is a very crucial procedure in which even slightest mistake can not be accepted and there is very chance of an error in manual handling.

Time consuming and Inconsistent - Present system is manual, thus time consuming and inconsistent in nature. Long hours are spent by the college staff to communicate and maintaining their information. Student’s has to ask from the staff member regarding college activity. The arrangement thus generated is not always efficient and inconsistent.

In order to meet the challenge of overcoming the drawbacks of overall system, an online information system is proposed.

1.5 Proposed System

Scope and Benefits of the Proposed System:

The soul of this project is devoted towards the development of software, which has a very interactive and user-friendly interface equipped with robust features to simplify the information needs of users, backed with an efficient and well-designed interface to solve the large administrative problems occurring. The following points will

give an overview of the proposed system and some broad advantages of it over the existing system will be brought forth: -

All information within a single application:The problem of information needs for different people is solved by providing all

possible information under one application. Users like Students get information about the upcoming campus drives and staff member can communicate through email.

Intuitive and self-explanatory interface:

The proposed system will have intuitive names of the menus as well as the command buttons, which will help the users understand the working of the system just by looking at it.

Efficient online help and Easy search tips:

We plan to provide all information online so that its users can access the system with in the institute.

Mailing system that speaks for itself:

Our aim is to provide email messages that are concise yet informative. The contents of news are also entered by the administrator very easily.

CHAPTER 2

THE ORGANIZATION

2.1 HCL Infosystem

HCL Infosystem,India’s premier information enabling and integration companyOffers its customers technology solutions across multiple platforms.it has partnerships with some leading global players like Intel, AMD, Toshiba, Microsoft, Nokia and Sun Microsystems among others.

HCL Infosystems has direct customer service centers across 300+ locations and Two ISO 9001 certified state-of-the-art manufacturing facilities.With a mission to provide world class information technology solutions and services to enable its customersTo serve their customers better,HCL Infosystem is forever setting new standards of IT in the country.For more information please visit www.hclinfosystems.in.

2.1 About HCL Enterprise

HCL is a leading global Technology and IT Enterprise with annual revenues of US$ 4.9 billion. The HCL Enterprise comprises two companies listed in India, HCL Technologies and HCL Infosystems.

The 3 decade old enterprise, founded in 1976, is one of India's original IT garage start ups. Its range of offerings span R&D and Technology Services, Enterprise and Applications Consulting, Remote Infrastructure Management, BPO services, IT Hardware, Systems Integration and Distribution of Technology and Telecom products in India. The HCL team comprises 55,000 professionals of diverse nationalities, operating across 18 countries including 360 points of presence in India.

HCL has global partnerships with several leading Fortune 1000,including several IT and Technology majors.

Along with the swiftly growing software technology industry, HCL, which was hitherto known as the pioneer in modern computing made the advent into software development.

HCL's R&D was spun off as HCL Technologies in 1997 to mark their advent into the software services arena.

Today, HCL sells more PCs in India than any other brand, runs Northern Ireland's largest BPO operation, and manages the network for Asia's largest stock exchange network apart from designing zero visibility landing systems to land the world's most popular airplane. And this it does across 18 countries and across 360 service locations in India.

2.2.1 Products & Services:

Product Engineering & Technology Development:-

The Engineering and R & D services department runs the largest outsourced engineering center outside the US which is a testimony to the 30 year product engineering experience. The company offers a comprehensive range of R&D and Engineering services to component vendors, OEMs, ODMs and ISVs across multiple industry segments and domains.

2.2.2 Infrastructure:

HCL Infrastructure Management Division is focused on addressing the growing demand for the cost-effective management of technology infrastructure across geographically dispersed locations. IT Infrastructure Management is in the HCL DNA, drawing resources from the 30 year pioneering heritage in the area of computing, in line with global giants

2.2.3 BPO:

Business Processing Outsourcing is heading towards a maturity level where a new form of BPO, called Transformational BPO, is evolving that constitutes Full Process Outsourcing and Multiple Process Outsourcing . The evolving trend is more focused towards compliance , time-to-market, focus on core process, and quality improvement rather than cost savings.

2.2.4 Applications:

Leveraging strong partnerships with platform / product companies, the team of applications professionals deliver unprecedented value to few of the largest players in the field of Financial Services, Retail and Healthcare.

2.2.5 IT Hardware:

HCL Infosystems portfolio of products covers the entire spectrum of the information technology needs of its customers. By virtue of the immense diversity of markets and customers that it address, HCL Infosystems products offerings include everything from high end enterprise level servers for mission critical applications to multimedia home computers.

2.2.6 Telecom and Imaging Products and Retail:

HCL Infinet covers a range of telecom and imaging products including enterprise networking. HCL tied up with Nokia in 1995 with the sale and services of Nokia mobile phones in India.

2.2.7 Networking and Network Integration:

Network Management involves Network Monitoring of Bandwidth Utilization, Network Errors / Collisions, Network Troubleshooting, Day-to-day Network Operations, Network performance monitoring, Tuning Network Operating System and advise action plan.

2.2.8 Awards

India's Most Preferred Personal Computer Brand by CNBC AWAAZ Consumer Award 2007.

India's 'No. 1 PC Vendor' consecutively for six years.

HCL among the Top 3 IT companies for the last 3 years, DQ & IDC,Best Employer Survey, 'Best employer 2005' with Five Star Ratings.

Top 50 Fastest Growing Technology Companies in India & 'Top 500 Fastest Growing Technology Companies in Asia Pacific' by 'Deloitte & Touche'.

Vineet Nayar appointed to the Board of Directors at HCL Technologies.

Noida, Aug 1, 2008 : HCL Technologies, India’s leading Global Technology and IT Services company, announced that Vineet Nayar, CEO, HCL Technologies, has been appointed to the Board of HCL Technologies as a Wholetime Director with effect from August 1, 2008.

Shiv Nadar, Founder - HCL and Chairman & Chief Strategy Officer, HCL Technologies said - “Vineet’s appointment to the Board reflects HCL’s commitment to nurturing talent, positioning it in key areas of leadership and building lasting institutions of excellence. Vineet joined HCL - his first and only job, as Senior Management Trainee in 1985. He created HCL Comnet, and positioned HCL as a pioneer and industry leader globally in the Remote Infrastructure Management space. He has led HCL’s transformation strategy, now a Harvard Business School case study. Vineet will now continue to bring his leadership skills to bear on HCL’s future but in a larger context - in developing its vision, governance and strategy beyond the confines of HCL’s business. “

Vineet Nayar, now CEO and Whole time Director, HCL Technologies, said, “I am honoured by the Board’s decision, and look forward to being part of the future growth of HCL in all its larger dimensions as a global and responsible corporate citizen. In my 23 year association with HCL, this is another opportunity for me to share and shape the larger transformation journey with Shiv Nadar, the board, and my team members across the HCL Enterprise.”

2.3 Our Purpose:

To conduct educational programs whose purpose is to foster a community-wide effort to ensure high quality leadership to meet the present and future challenges that face the citizens of Huntington County.

Such educational programs shall seek the active involvement of informed and dedicated citizens in order to:

Identify, motivate and develop potential community leaders;

Expand the potential of the participants through: Informational programs designed to broaden their knowledge of Huntigton County and critical issues affecting the county and its communities; exposure to the existing leadership and civic organizations ; in-depth exchange of relevant issues;

Improve communication among community leaders;

Provide a channel to become involved in challenges facing the community through participation in various organizations and/or porojects;

Develop leadership skills;

Foster a commitment to a life of community service.

Contact Information :

Corporate Office:

HCL InfoSystems Ltd.

E-4,5,6 Sector Xi

NOIDA - 201301

(Uttar Pradesh)

India

Phones (Office): +91-2526518/19 / 2520977

Fax: 2550923

Prefix from Delhi: 95120

STD Code: 0120, ISD Code: 120

Email: webhost@hcl.in

CHAPTER 3

PROJECT ANALYSIS

3.1 Analysis

‘Placement Cell’ is a Local area network project. Projects can be categorized in two

ways:-

1. Local area network projects

2. Distributed area network projects

Local area Network projects are those projects where application has to be in

cooperated in the Local area network of the client i.e. with in its premises only. In LAN

cases, server is not remotely located and client access this application through this

network. Here the question of platform independence does not arise and we use

technologies like: Visual Basic, Fox pro, D2K or C, C++.

But Distributed projects are those projects where application is remotely situated. In

these kind of projects application is remotely situated on to the remote server from where

client machine connects to the remote server and application is downloaded on to client

machine. Here the question of platform independence arises and we use technologies

like .NET.

3.2 Feasibility Study

A feasibility study is conducted top select the best system that meets performance

requirement. The key consideration in feasibility analysis is:

1. Economic Feasibility

2. Technical Feasibility

3. Operational Feasibility

3.2.1 Economic Feasibility:

Meaning: Are there sufficient benefits in creating the system to make the costs

acceptable? Or Are the costs of not creating the system so great that it is advisable to

undertake the project.

This will include three major costs as described below:-

Cost of Hardware and Software

Cost of software to be acquired to build and run the product is a one time cost.

Buying a back end database is the major part of hardware and software cost.

Comparison between the Oracle database high cost and better features with the SQL

server low cost and better support for the same vendor operating system make this

decision need oriented.

Benefits in reduced cost, error and Savings will be made by reduction of present

system expenses, time saving and increased accuracy.

The proposed system is economically feasible because the cost involved in

purchasing that hardware and the software are within approachable.

The personal cost like salaries of employees hired are also nominal, because

working in this system need not required a highly qualified professional .The

operating –environment costs are marginal .The less time involved also helped in its

economical feasibility.

Cost Avoidance: Future cost reduction in form of reduction in the number of

administrative staff needed and manual records maintains in organization. Rise in cost

will be avoided.

3.2.2 Technical Feasibility:

Meaning: Can the work for the project be done with current equipment existing

software technology and available personnel? If new technology is needed, what is the

likelihood that it can be developed?

Reply: In this project the work cannot be done by the current system because currently

all the records, filling, transactions, entries, are done by manuals. It is really time

consuming and margin of error is more.

Yes, the current available personnel can develop this system but special training

should be given to those personnel to improve their skills. Yes new technology or

software, which is currently working in the market, is to be needed to develop this

system.

It can be developed easily with this software and for a long term it is working

effectively and margin of error is less.

To run this product the following technological consideration has to be kept in

mind by the Company.

SQL server as back-end is a good DBMS software with long-standing track

record in industry for the good technical aspect, extensibility, concurrency and support

needed for this purpose.

SQL server2005 and Windows NT operating system are used while making this

product. Language such as .NET is also used while making this project.

SQL server can run on the different windows operating systems from Windows

95 , Win NT, and Win xp and Win 7.

Hardware’s used in this project are –Pentium Dual 1.8 GHz, 1GB RAM, 10 GB

hard disk. These hardwares were already available on the existing computer system.

The software like MS-ACCESS, MS-WORD and operating system used were already

installed on the existing. So no additional hardware and software were required to

purchase and it is technically feasible.

3.2.3 Operational Feasibility:

Meaning: The system will be used if it is developed well then be resistance from users

that undetermined the possible application benefits.

Administrative Support: Administrative support for present system is there to add new

plans in the current system as well as managing details of TPO and students. No major

training and new skills are required as it is based on DBMS model.

It will help in the time saving and fast processing and dispersal of customer

request and applications for purchasing of plans available and to dynamically change

the discount percentage to display.

New product will provide all the benefits of present system with better

performance suchlike Improved information, better management and collection of the

reports.

Employer Support: Employer involvement in the building of present system is sought

to keep in mind the employer specific requirement and needs.

Faster and systematic processing of employer requirements will save employer’s

time from cumbersome process of Searching and Buying services.

3.3 Approach to be used:

WATERFALL MODEL:

The waterfall model is a sequential software development process, in which

progress is seen as flowing steadily downwards (like a waterfall) through the phases of

Conception, Initiation, Analysis, Design (validation), Construction, Testing and

maintenance.

Progress flows from the top to the bottom, like a waterfall. The waterfall

development model has its origins in the manufacturing and construction industries;

highly structured physical environments in which after-the-fact changes are prohibitively

costly, if not impossible. Since no formal software development methodologies existed at

the time, this hardware-oriented model was simply adapted for software development.

1. In the requirements analysis phase:

The problem is specified along with the desired service objectives (goals)

The constraints are identified

2. In the specification phase:

The system specification is produced from the detailed definitions of (a) and

(b) above. This document should clearly define the product function. Note that in

some text, the requirements analysis and specifications phases are combined

and represented as a single phase.

3. In the system and software design phase:

The system specifications are translated into a software representation.

The software engineer at this stage is concerned with:

Data structure

Software architecture

Algorithmic detail and

Interface representations

The hardware requirements are also determined at this stage along with a

picture of the overall system architecture. By the end of this stage the software

engineer should be able to identify the relationship between the hardware,

software and the associated interfaces. Any faults in the specification should

ideally not be passed ‘down stream’.

4. In the implementation and testing phase:

Stage the designs are translated into the software domain

Detailed documentation from the design phase can significantly reduce the coding

effort.

Testing at this stage focuses on making sure that any errors are identified and that

the software meets its required specification.

5. In the integration and system testing phase:

All the program units are integrated and tested to ensure that the complete

system meets the software requirements. After this stage the software is delivered to

the customer [Deliverable – The software product is delivered to the client for

acceptance testing.]

6. The maintenance phase:

The usually the longest stage of the software. In this phase the software is updated

to:

Meet the changing customer needs.

Adapted to accommodate changes in the external environment

Correct errors and oversights previously undetected in the testing phases.

Enhancing the efficiency of the software.

REASON FOR USING THIS MODEL:-

Testing is inherent to every phase of the waterfall model

It is an enforced disciplined approach

It is documentation driven, that is, documentation is produced at every stage.

3.4 FUNCTIONAL COMPONENTS

To facilitate easy maintenance of records of various students.

To check details of students for campus.

To facilitate preparation of records in the mechanized process and thereby producing accurate documents/data’s for recording details.

Quick access of all records.

Reduce manual work.

Quickly informing all the students by sending mails.

Prevent and reduce human error.

3.5 HARDWARE REQUIREMENTS

Processor - Pentium 4

RAM - 1 GB

Hard Disk - 10 GB

Monitor - VGA/CGA

Keyboard - Multimedia Keyboard

Mouse - PS/2

3.6 SOFTWARE REQUIREMENTS

Operating System - Windows XP

Front End - Microsoft Visual Studio 2008

(Version 3.5)

Back End - Microsoft SQL Server 2005

Browser - Internet Explorer

CHAPTER 4

PROJECT DESIGN

This design document contains various diagrams to show the flow and working of

the system. Let us understand the ‘campusinfo.com’ by:

Data Flow Diagram

Flow Charts

Entity Relationship Diagram

Database Diagram

4.1 Data Flow Diagram:

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data

through an information system. DFDs can also be used for the visualization of data

processing (structured design). On a DFD, data items flow from an external data source

or an internal data store to an internal data store or an external data sink, via an internal

process.

A Data Flow Diagram or DFD is prepared to clarify system requirements and to

identify major transformation that will become programs in system design. Also known

as ‘Bubble Chart’, it is the first step in structured analysis part of designing. Hence, it is

the starting point of the designing phase that functionally decomposes the requirements

specification down to the lowest level of detail.

DFD consists of a series of bubbles and other symbols joined by arrows and lines.

However, it should be noted that a DFD describes “What is the logical data flow?” rather

than “How the data are processed?” So, it does not depend on hardware, software, data

structure or file organization. A DFD only shows the major transformations and flow of

data in the whole software system.

It is common practice to draw a context-level data flow diagram first, which

shows the interaction between the system and external agents which act as data sources

and data sinks. On the context diagram (also known as the Level 0 DFD) the system's

interactions with the outside world are modeled purely in terms of data flows across the

system boundary. The context diagram shows the entire system as a single process, and

gives no clues as to its internal organization.

This context-level DFD is next "exploded", to produce a Level 1 DFD that shows

some of the detail of the system being modeled. The Level 1 DFD shows how the system

is divided into sub-systems (processes), each of which deals with one or more of the data

flows to or from an external agent, and which together provide all of the functionality of

the system as a whole. It also identifies internal data stores that must be present in order

for the system to do its job, and shows the flow of data between the various parts of the

system.

There are numerous symbols that are being used in making a Data Flow

Diagram. But, amongst them, only few common ones are used. These are shown as

follows along with their use.

DFD Symbols:

Rectangle. It defines a source or destination of system data.

Circle. It represents a process that transforms incoming data flow into outgoing data flow.

Oval Bubble. Same as Circle.

Pipe. It shows a data store – data at rest or a temporary repository of data.

Open Rectangle. Same as pipe.

Arrows. They identify data flow i.e. data in motion.

Report. It is used to show a report submission.

0 LEVEL DFD:

Training And Placement

System

User Home Page

Description of 0-Level DFD:-

1. User request to open Online Campus Recruitment Information System (campusinfo.com).

2. Web Server responds to the request.

3. Web Server finds the website and gets all the DLLs.

4. User receives the Home Page.

1 LEVEL DFD:

User

Training And Placement Cell

Home

Administrator

Login

Mailing

TPO List

Information

Admin_Login

Inbox

Draft

Mail

TPO

Camp_Info

TPO

Login

Mailing

Student List

Add College

TPO_Login

Inbox1

Draft1

Mail1

Student_Reg

College_Info

Student

Login

Registration

Student_log

Student_Reg

Other Information

Description of 1-Level DFD:-

1. User request to open Online Campus Recruitment Information System (campusinfo.com) which is responded by Server.

2. From Home page the user can either go to Admin section only if he has provided the admin URL in the address bar.

3. Other user like Colleges can get registered.

4. Another user i.e. the TPOs can access the TPO section after successful login.

5. Finally, the Students can view Students section and Information section.

2 LEVEL DFD:

For Admin Section:

AdminSection

Login AndPassword

VerificationAdmin

EmailSection

TPOSection

Information Section

Campus_InfoTPOTables

Description of 2-Level DFD for Admin:-

1. After passing Admin URL the user has to give Login details on Login page. If Login is successful, the Admin’s account is opened.

2. The Admin can send and receive mails.

3. In the account the Admin can go to College section where addition, updating, removal and listing of all colleges can be done through College table.

4. Same operations along with mailing functionality are provided in TPO section.

5. Admin can also maintain Student table.

6. Finally, the Admin can manage Campus_Info table as per requirements.

For TPO Section:

TPOSection

Login AndPassword

VerificationTPO

MailingSection

StudentSection

CollegeSection

College_InfoStudentTables

Description of 2-Level DFD for TPO:-

1. After clicking on TPO button on Home Page TPO login is opened where Login is required.

2. Once logged in, a TPO can send and receive mails from Admin and other TPOs.

3. The TPO can also lists the students of his / her college as per various criteria.

4. Finally, the TPO can see the various campus recruitment information.

4.2 Flow Charts:

Every system has certain flow in which the information passes between various

sub-systems. A Flow Chart is used to depict this flow in graphical form. It is a designing

tool that is used by most designers to show the actual flow of information, before the

system is developed. A Flow Chart is a modeling technique introduced in 1940s and

popularized for structured development in 1970s by Gane and Sarson.

A Flow Chart is prepared to clarify the information flow among various levels of

a system. There are basically three types of Flow Charts in use. These are:-

System Flow Chart

Used by System Analyst for analyzing and designing systems, they graphically

illustrate the elements and characteristics of a system and express its structure and

relationships in terms of symbols.

Modular Program Flow Chart

Also known as ‘Block Diagram’, these are designed primarily to illustrate

algorithms for developing and writing specific computer programs. Specific details on

how a program is processed are not given in them.

Detail Program Flow Chart

These are most comprehensive and elemental charts used by Programmers. Each

symbol represents an executable step suitable for coding as an instruction in a computer.

These may vary slightly when coding in different languages.

Flow Chart Symbols

Rectangle. It represents the process being carried out.

Rhombus. It shows the input and output data for a process.

Diamond. This symbol is used to show decision making for

branching of information.

Oval. It acts as a terminator i.e. shows start and stop of a

flow chart.

Small Circle. It is a connector between different parts of a

flow chart.

Arrows. They identify the flow i.e. movement of

information in a flow chart.

Flow Charts are essentially a working map of your final product. The Flow Chart

is not created in stone. It will probably change as one work through all of the details of

the final product.

Flow Chart for Home Page:

START

HOME PAGE

ADMIN TPOs STUDENT CAMPUS INFORMATION

A B C D

Flow Charts for Home Page:

1. Administrator Tab

A

If Admin’s URL is passed with website’s URL

Show Admin Login Page.

Ask for Username and Password.

Verify Admin Login from Admin Table.

Yes

Redirect to Home Page with message of unknown user

No

Yes

Admin’s Acccount Page

If Admin’s Login is correct

If Log Out

Yes

2. TPO Tab

B

If TPO Button is pressed on Home Page

Show TPO Login Page.

Ask for Username and Password.

Verify TPO Login from TPOTable.

Yes

Redirect to Home Page with message of unknown TPO

No

Yes

TPO’s Account Page

If TPO Login is correct

If Log Out

Yes

3. Student Tab

C

If Student Button is

pressed on Home Page

Show Student’s Home Page.

Allow new Student to get registered.

Allow registered Students to update their information.

Yes

4. Information Tab

D

If Information Button is

pressed on Home Page

Show Information Page.

Get Campus Interview tips and papers.

Get latest updates and display them on the page.

Yes

4.3 E-R Diagram:

In software engineering, an Entity-Relationship Model (ERM) is an abstract and

conceptual representation of data. Entity-relationship modeling is a database modeling

method, used to produce a type of conceptual schema or semantic data model of a

system, often a relational database, and its requirements in a top-down fashion.

Diagrams created using this process are called entity-relationship diagrams, or ER

diagrams or ERDs for short.

The Entity Relationship Diagram, or ER Diagram, provides a graphical notation

for representing data models that are typically used in the first stage of information

system design. They are used to describe information needs and the type of the

information that is to be stored in the database during the phase of requirement analysis.

Today all computer software use Data Base Management Systems for information

storage and retrieval along with its manipulation. In such a scenario, ER Diagram

symbolizes the design of an information system that is based on a database. The

conceptual data model is at a later stage of designing mapped to a logical data model such

as the relational model. This in turn is mapped to a physical model during physical

design. Therefore, ER Diagram is a data model or data diagram for high level

descriptions of conceptual data models.

The ER Model consists of entities, their attributes, relationships, etc. that are

being revealed with the help of various symbols. These symbols along with their use are

shown as follows:

ER Diagram Symbols

Rectangle. It represents the entities, the things about which we seek information.

Week Entity. It depends on another entity to exist.

Ellipse. It shows attributes that are properties of the entity.

Primary Key / Attribute. It is the unique, distinguishing property of the entity.

Multivalued Attribute. It can have more than one value.

Derived Attribute. It is based on another attribute to exist.

Diamond. It shows relationships that provide the structure which draws information from multiple entities.

Weak Relationship. It is used to connect a weak entity to another.

Arrows. They identify the flow i.e. movement of information in a flow chart.

ER Diagram:

Inbox

outdate subjectfrom1

userid

mailid

outtime

message1

Received

Adminsaved mailsDraft

u bcc

u ccu to

u from

draft id

subject

body drftdate

drfttime

sent mails Mail

mailid

to1 cc bcc

from1

mtype

outtime outdate

message1

Manages

auname apaswd

Camp Info

ciid

colgname

compny

cidate

colgaddbranch criteria

TPO

tpoid

tponame

tpocolgname

emailid

tpomobnotpousernametpopswd

Has

Student College

clgid

clgname

clgaddr

cname

BE

MEMCA

stid

stname

stcolststreamstbranch

styear

stsem

st10marks

st12marks

stgradstpg stemail stmob

stuser

subject

MBA

stpass

CHAPTER 5

SCREEN SHOTS

TPO Login :

TPO Registration :

Add College :

Student Registration :

Student Login:

Student Update Information:

Student List :

Admin Login :

TPO List:

Campus Information :

Admin Inbox:

Admin Mail Compose:

Admin Sent Mail:

Admin Read Mail:

Other Information :

CHAPTER 6

TESTING

6.1 Software Testing:

Software Testing is an empirical investigation conducted to provide stakeholders

with information about the quality of the product or service under test, with respect to the

context in which it is intended to operate. Software Testing also provides an objective,

independent view of the software to allow the business to appreciate and understand the

risks at implementation of the software. Test techniques include, but are not limited to,

the process of executing a program or application with the intent of finding software

bugs. It can also be stated as the process of validating and verifying that a software

program/application/product meets the business and technical requirements that guided

its design and development, so that it works as expected and can be implemented with the

same characteristics.

Software Testing, depending on the testing method employed, can be

implemented at any time in the development process, however the most test effort is

employed after the requirements have been defined and coding process has been

completed.

6.2 Software testing topics

6.2.1 Scope

A primary purpose for testing is to detect software failures so that defects may be

uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a

product functions properly under all conditions but can only establish that it does not

function properly under specific conditions. The scope of software testing often includes

examination of code as well as execution of that code in various environments and

conditions as well as examining the aspects of code: does it do what it is supposed to do

and do what it needs to do. In the current culture of software development, a testing

organization may be separate from the development team. There are various roles for

testing team members. Information derived from software testing may be used to correct

the process by which software is developed.

6.2.2 Defects and failures

Not all software defects are caused by coding errors. One common source of

expensive defects is caused by requirements gaps, e.g., unrecognized requirements,

which result in errors of omission by the program designer. A common source of

requirements gaps is non-functional requirements such as testability, scalability,

maintainability, usability, performance, and security.

Software faults occur through the following processes. A programmer makes an

error (mistake), which results in a defect (fault, bug) in the software source code. If this

defect is executed, in certain situations the system will produce wrong results, causing a

failure. Not all defects will necessarily result in failures. For example, defects in dead

code will never result in failures. A defect can turn into a failure when the environment is

changed. Examples of these changes in environment include the software being run on a

new hardware platform, alterations in source data or interacting with different software.

A single defect may result in a wide range of failure symptoms.

6.3 Testing methods

Software testing methods are traditionally divided into black box testing and

white box testing. These two approaches are used to describe the point of view that a test

engineer takes when designing test cases.

6.3.1 Black box testing

Black box testing treats the software as a "black box," without any knowledge of

internal implementation. Black box testing methods include: equivalence partitioning,

boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability

matrix, exploratory testing and specification-based testing.

Specification-based testing

Specification-based testing aims to test the functionality of software according to the

applicable requirements. Thus, the tester inputs data into, and only sees the output from,

the test object. This level of testing usually requires thorough test cases to be provided to

the tester, who then can simply verify that for a given input, the output value (or

behavior), either "is" or "is not" the same as the expected value specified in the test case.

Specification-based testing is necessary, but it is insufficient to guard against certain

risks.

Advantages and disadvantages

The black box tester has no "bonds" with the code, and a tester's perception is very

simple: a code must have bugs. Using the principle, "Ask and you shall receive," black

box testers find bugs where programmers don't. But, on the other hand, black box testing

has been said to be "like a walk in a dark labyrinth without a flashlight," because the

tester doesn't know how the software being tested was actually constructed. That's why

there are situations when (1) a black box tester writes many test cases to check something

that can be tested by only one test case, and/or (2) some parts of the back end are not

tested at all.

Therefore, black box testing has the advantage of "an unaffiliated opinion," on the one

hand, and the disadvantage of "blind exploring," on the other.

6.3.2 White box testing

White box testing, by contrast to black box testing, is when the tester has access

to the internal data structures and algorithms (and the code that implement these)

Types of white box testing

The following types of white box testing exist:

API Testing - Testing of the application using Public and Private APIs.

Code Coverage - creating tests to satisfy some criteria of code coverage. For

example, the test designer can create tests to cause all statements in the program

to be executed at least once.

Fault Injection Methods.

Mutation Testing Methods.

Static Testing - White box testing includes all static testing.

Code Completeness Evaluation

White box testing methods can also be used to evaluate the completeness of a test suite

that was created with black box testing methods. This allows the software team to

examine parts of a system that are rarely tested and ensures that the most important

function points have been tested.

Two common forms of code coverage are:

Function coverage, which reports on functions executed

Statement coverage, which reports on the number of lines executed to complete

the test.

They both return coverage metric, measured as a percentage.

6.3.3 Grey Box Testing

In recent years the term grey box testing has come into common usage. This involves

having access to internal data structures and algorithms for purposes of designing the test

cases, but testing at the user, or black-box level. Manipulating input data and formatting

output do not qualify as "grey-box," because the input and output are clearly outside of

the "black-box" that we are calling "the software under test." (This distinction is

particularly important when conducting integration testing between two modules of code

written by two different developers, where only the interfaces are exposed for test.) Grey

box testing may also include reverse engineering to determine, for instance, boundary

values or error messages.

Testing can be done on the following levels:

Unit testing: Unit testing tests the minimal software component, or module. Each

unit (basic component) of the software is tested to verify that the detailed design

for the unit has been correctly implemented. In an object-oriented environment,

this is usually at the class level, and the minimal unit tests include the constructors

and destructors.

Integration testing: Integration testing exposes defects in the interfaces and

interaction between integrated components (modules). Progressively larger groups

of tested software components corresponding to elements of the architectural

design are integrated and tested until the software works as a system.

System testing : System testing tests a completely integrated system to verify that

it meets its requirements.

System integration testing: System integration testing verifies that a system is

integrated to any external or third party systems defined in the system

requirements.

Before shipping the final version of software, alpha and beta testing are often done

additionally:

Alpha testing : Alpha testing is simulated or actual operational testing by

potential users/customers or an independent test team at the developers' site.

Alpha testing is often employed for off-the-shelf software as a form of internal

acceptance testing, before the software goes to beta testing.

Beta testing : Beta testing comes after alpha testing. Versions of the software,

known as beta versions, are released to a limited audience outside of the

programming team. The software is released to groups of people so that further

testing can ensure the product has few faults or bugs. Sometimes, beta versions

are made available to the open public to increase the feedback field to a maximal

number of future users.

CHAPTER 7

CONCLUSION

7.1 Limitations of the system

Since, every system has some limitations so our proposed system is also not

untouchable in this regard.

Although it includes every kind of features but it can’t be used in a huge

organization where number of networks is very large, because the data base constraints

used in this system is an average one.

The main limitations of our system are:

There is no facility for sending messages to students’ mobile number.

The TPO can only send mails after login.

TPO cannot send mail to other TPO.

7.2 Future Enhancements

In future this project can be treated as product according to specification and

needs of any college. At present days every organization is using web technology for

their proper functioning, so this web based project is all in all important from market

aspects. Future enhancements related with this project are-

If this project will be uploaded, it can be used as campus recruitment information

system and any college can register itself on the site to carry out its recruitment

process using this site.

In future, message will be sent automatically to student’s mobile number

regarding campus information.

TPO can send mail to other TPO also.

7.3 REFERENCES AND BIBLIOGRAPHY

SITES REFERRED:

1. http://www.dotnetspider.com

2. http://www.docjax.com

3. http://www.placementpaper.com

BOOKS

1. ASP.NET Black Book - By Steven Holzner

2. The Complete Reference (ASP and C# .NET) - By Jeffrey R. Shapiro

3. Database System Concepts - By Henry Korth