Project report

On
Center Automation System
Submitted By

Akhil Sood

Registration No-7050070141

Under the Guidance of

Miss. Chander Kiran Mr. Parminder Singh

Department Of CSE/IT
Lovely School of Technology and Sciences
Lovely Professional University, Phagwara
July – December 2010
 DECLARATION

I hereby declare that the project work entitled “Centre Automation System” is an
authentic record of my own work carried out at Chandigarh as requirements of
Industry Internship project for the award of degree of B.Tech(H), Lovely
Professional University, Phagwara, under the guidance of Mr.Perminder Sigh and
Miss. Chander Kiran during July to December 2010).

(Signature of student)
Akhil Sood
7050070141

Date:03-09-2010

Certified that the above statement made by the student is correct to the best of our
knowledge and belief.

Miss. Chander Kiran Mr.Perminder Singh(Trainer)

 ACKNOWLEDGEMENT

Nothing great can be achieved without inspiration & perspiration. I would like to
thank LOVELY PROFESSIONAL UNIVERSITY for taking this initiative. I have
put on great efforts to complete this “PROJECT”. I hope my work will be
appreciated.

First and foremost I would like to thank GOD ALMIGHTY who had been there
with me all the time during my work.

My next inspiration comes from my parents who were the most supportive during
my research on the project.

I whole heartedly express my gratitude to our External Supervisor Mr.Parminder

Singh and Mentor Miss. Chander Kiran who is always there for me with her
everlasting and inspiring knowledge.

In the end I would not forget my friends who supported me and help me with their
best efforts they can put on.

With Regards

Akhil Sood
 1) INTRODUCTION OF THE ORGNISTAION

SPIC (Society for Promotion of IT in Chandigarh)

The Society for Promotion of IT in Chandigarh (SPIC) has been set up under
the aegis of the Department of Information Technology, Chandigarh
Administration for implementing the various plans of the Administration to
promote the IT industry in Chandigarh. The Chairperson of the Society is the
Adviser to the Administrator.

The major objectives of this society are as under:-

a) To promote application of Information Technology in the Union Territory of

Chandigarh in accordance with the IT Policy of Chandigarh Administration.

b) To carry out all such activities that are commensurate with the IT vision of the
Chandigarh Administration as outlined in IT Policy.

c) To promote e-Governance, Software Exports, create IT Infrastructure, generate

jobs in IT as outlined in the IT Mission of the Chandigarh Administration.

d) To facilitate the establishment and functioning of data processing computer

centers.

e) To provides consultancy services and imparts training in various disciplines of

Information Technology.

f) To facilitate the development of software packages as well as related items and

undertake turnkey project and assignments in India and abroad in Information
Technology by public and private sector companies in the Union Territory of
Chandigarh in order to promote the application of Information Technology for the
benefit of citizens of Chandigarh .
 1) Profile of the Problem:-
Here, we are making a project for the organization. The main features of this
project are to automate the system such as Registration of students, enquiry or
help desk ,accounts details(like fee balance),faculty details etc .basically, this
project can use in institutes of computer education centre, coaching centre. We
are going to implement this automation system in the organization.

Problem:- In organization they need to store the data of various students pursuing
different courses, faculty details and other issues in simple excel sheet format
and when anybody have to know something about the courses , fee structure,
faculty, timing, courses etc. for this they handled it by seeing the excel sheet that
they have maintained. In this procedure a lot of time will be wasted for searching,
sorting as well as they faces the problem of finding the data where it stored. If that
person would absent any day in the company due to some reason then for another
person which will do his/her work faces the lot of problems because he/she don’t
know that where the last person stored the file or data then he/she will not able to
solve the problem accurately. When they are taking the fee from students then at
that time they don’t know that how many installments the student has given? For
this they ask from the students this is which number installment? According to that
they have given the slip to the student. When they want to see that how many
students have not given the installment and they have given a word sheet to each
trainer to fill the names of those students which have not given the installment.
Then each trainer of a organization will have to maintain the name of students who
have not submitted the installment. In this way they are storing the data of the
students which is not accurate.

Existing System: - Currently organization- administration are using Microsoft

office packages and maintaining their records in MS-Word and MS-Excel sheets.
Introduction:- As we already discussed that in organization –administration they
are using the MS office packages. In MS-office software it is easy to maintain the
data but the data is not so much consistent and it is problematic to find the data of
any required entity in the list of hundred and thousand records .and there is no
duplicity checks on data can be done during the data entry .in this type of data
storage data can be mismatch

For e.g.:- If the user enter the data in excel sheet then they may be enter the
wrong field instead of filling the correct field such as they can enter the user name
in the field of its serial no.

Existing Software:-

1) MS-WORD

2) MS-EXCEL and obsolete data entry system.

Data Flow Diagram:-

DFD

The data flow diagram (DFD) serves two purposes:-

1) To provide an indication of how data are transformed as they move through
the system and
2) To depict the functions (and sub functions) that transform the data flow.
The DFD provides additional information that is used during the analysis of
the information domain and serves as a basis for the modeling of function.

As information moves through software, it is modified by a series of

transformations. A data flow diagram is a graphical representation that depicts
information flow and the transforms that are applied as data move from input to
output. The basic form of a data flow diagram, also known as a data flow graph.

The data flow diagram may be used to represent a system or software at any
level of abstraction. In fact, DFDs may be partitioned into levels that represent
increasing information flow and functional detail. Therefore, the DFD provides a
mechanism for functional modeling as well as information flow modeling. In so
doing, it satisfies the second operational analysis principle (i.e., creating a
functional model)

DFD, also called a fundamental system model or a context model, represents

the entire software element as a single bubble with input and output data indicated
by incoming and outgoing arrows, respectively.

The basic notation used to develop a DFD is not in itself sufficient to

describe requirements for software. For example, an arrow shown in a DFD
represents a data object that is input to or output from a process. A data store
represents some organized collection of data. But what is the content of the data
implied by the arrow or depicted by the store? If the arrow (or the store) represents
a collection of objects, what are they? These questions are answered by applying
another component of the basic notation for structured analysis—the data
dictionary.

The data flow diagram enables the software engineer to develop models of
the information domain and functional domain at the same time. As the DFD is
refined into greater levels of detail, the analyst performs an implicit functional
decomposition of the system, thereby accomplishing the fourth operational
analysis principle for function. At the same time, the DFD refinement results in a
corresponding refinement of data as it moves through the processes that embody
the application.

A few simple guidelines can aid immeasurably during derivation of a data flow
diagram:-
1) The level 0 data flow diagram should depict the software/system as a single
bubble
2) Primary input and output should be carefully noted
3) Refinement should begin by isolating candidate processes, data objects, and
stores to be represented at the next level
4) All arrows and bubbles should be labeled with meaningful names
5) Information flow continuity must be maintained from level to level, and
6) One bubble at a time should be refined. There is a natural tendency to
overcomplicate the data flow diagram. This occurs when the analyst attempts to
show too much detail too early or represents procedural aspects of the software in
lieu of information flow.

What’s new in the system to be developed:-

In CENTER AUTOMATION SYSTEM we use separate database for storing

the information of all the students, faculties. In front end or in presentation layer
we just entering the data in our graphics interface and in back end the data is
maintained separately.

In this type of data storage system it is easy to retrieve data from thousand of the
entries and we can also validate the data so data that to avoid the mistakes. For fee
receipt system we can use the crystal reports to print the all information for the
convenience of user.

The main features of the Center Automation System are:-

1) To maintain the records: - it will maintain the records of visitors in an

organization and also the various records of the students like their
registration no, their domain, name of the project, trainer for their project
etc.

2) Enquiry or help desk:-in this section anybody who wants to know the
company policies, fee, and affiliations and to sort out their queries they can
sign in for this section.

3) Accounts Section:- This section will store the records of the students like
fee, balance, no of installments played etc

This project will solve the problem of an organization to keep the information
in one single database in spite of keeping records in various lists and so that
records can be fetched easily.
 Project Snapshots

1) Login Form
2) Master Form
3) College From
4) City & state form
Problem Analysis:-In “organization” they are generally using the MS-Word
and MS-Excel sheets to store the data of their employees, trainers and trainees. So
as we know that in Ms-word and excel sheet our data in not secure. So we are
going to implement this project in our organization so that they can store their data
in a single database and fetch the various records easily.

So various advantages of databases over flat file system are: as under -

Data redundancy and inconsistency:- Since different programmers create the

files and application programs over a long period, the various files are likely to
have different formats and the programs may be written in several programming
languages. Moreover, the same information may be duplicated in several places
(files).

For example: - The address and telephone number of a particular customer may
appear in a file that consists of savings-account records and in a file that consists of
checking-account records. This redundancy leads to higher storage and access cost.
In addition, it may lead to data inconsistency,

That is, the various copies of the same data may no longer agree.

Difficulty in accessing data: - Suppose that if we want to find out the names of
all students who joined the .NET course. So it is very difficult for the person to
check each and every record from the excel file. So by using SQL SERVER in our
project we can overcome this problem.

Data isolation:-Because data are scattered in various files, and files may be in
different formats, writing new application programs to retrieve the appropriate data
is difficult.

Integrity problems:-when data values stored in the database must satisfy certain
types of constraints. For example, if we want to store the registration number of
any student then it can only accept numeric values, if someone tries to add
character value then it throws some exception. But these facilities are not available
in Ms-excel and text files.

Concurrent-access anomalies: - For the sake of overall performance of the

system and faster response, many systems allow multiple users to update the data
simultaneously. In such an environment, interaction of concurrent updates may
result in inconsistent data.

Security problems:- Not every user of the database system should be able to
access all the data. For example:-if we want to maintain privacy of our code that
we are going to use in our project. So by using the stored procedures we can also
maintain the security by giving the different access writes to different users.

Such as the administrator having all the rights to read, write and makes changes in
database and employees of the organization having rights to read and write the
data.

Product definition:-

Product definition is a critical starting point in the development of any new

product. In our product definitions we are just start developing the fundamental
requirements of the project. Yet for its importance, there are a number of common
shortcomings to the process of product definition in many companies:-
a) In this part there is no defined product strategy or product plan

b) There is a shortage of formal requirements as a basis for initiating product

development

c) Product requirements developed without true customer input and with the help
of making their E-R Diagrams

d) A marketing requirement specification that is completed late - after

development is underway

e) Engineering having little or no involvement in development of MRS, thereby

lacking a true understanding of requirements.

f) An incomplete, ambiguous, or overly ambitious MRS.

g) Creeping elegance or a constantly evolving specification that requires

increasing development scope and redesign iteration

A company doesn't blindly respond to customer needs and opportunities. A

business strategy which defines customers and markets to be served, competitors,
and competitive strengths provides a framework from which to evaluate potential
opportunities. The result of this evaluation of opportunities is expressed in a
product plan. In this phase of designing there is proper interaction between
developer and owner or customer so that the product will be less prone to failures.

Feasibility Analysis:-

The various fields where we can implement our project:-

1) Career development centers.

2) Small organizations.
 3) Educational institutes.

4) Schools and colleges

A feasibility Analysis is an evaluation of a proposal designed to determine the

difficulty in carrying out a designated task. Generally, a feasibility study precedes
technical development and project implementation. In other words, a feasibility
Analysis is an evaluation of the potential impact of a proposed project.

As, we know that in every business plan or project plan for a new organization
or venture, we have to do a Feasibility Analysis before we start doing a project
plan. Because we need to verify that the enterprise is viable before you spend the
time and money into doing a full-blown Project plan.
In feasibility analysis any information we gather and the time we spend on the
Feasibility Analysis will be directly useful in developing the Project plan.

The purpose of the Feasibility Analysis is to make sure that our project is on
the right track or not two basic questions need to be answered with the analysis:
1) Is there sufficient demand for the product or service:-this process signifies that
the project which we undertaken are on sufficient demand or not.
2) Can the product or service be provided on a profitable basis?

5) Software Requirement Analysis:-

Introduction:- Various software that we are going to use in our project are:-

1) C#.Net(Window Applications)

2) SQL Server 2005

3) Crystal Reports
4) XML sheets

5) Customized Control

General Description:-

1) C#.Net(Window Applications):-

C# a multi-paradigm programming language encompassing imperative,

declarative, functional, generic, object-oriented (class-based), and component-
oriented programming disciplines.

C# language is intended to be a simple, modern, general-purpose, object-oriented

programming language.

The language, and implementations thereof, should provide support for software
engineering principles such as strong type checking, array bounds checking,
detection of attempts to use uninitialized variables, and automatic garbage
collection. Software robustness, durability, and programmer productivity are
important.

The language is intended for use in developing software components suitable for
deployment in distributed environments.

Source code portability is very important, as is programmer portability, especially

for those programmers already familiar with C and C++.

Support for internationalization is very important.

C# is intended to be suitable for writing applications for both hosted and embedded
systems, ranging from the very large that use sophisticated operating systems,
down to the very small having dedicated functions.
Although C# applications are intended to be economical with regard to memory
and processing power requirements, the language was not intended to compete
directly on performance and size with C or assembly language.

SQL Server 2005:-

SQL Server 2005 (codenamed Yukon), released in October 2005, is the successor
to SQL Server 2000. It included native support for managing XML data, in
addition to relational data. For this purpose, it defined an xml data type that could
be used either as a data type in database columns or as literals in queries. XML
columns can be associated with XSD schemas; XML data being stored is verified
against the schema. XML is converted to an internal binary data type before being
stored in the database. Specialized indexing methods were made available for
XML data. XML data is queried using Query; Common Language Runtime (CLR)
integration was a main features with this edition, enabling one to write SQL code
as Managed Code by the CLR. SQL Server 2005 added some extensions to the T-
SQL language to allow embedding Query queries in T-SQL. In addition, it also
defines a new extension to Query, called XML DML, which allows query-based
modifications to XML data. SQL Server 2005 also allows a database server to be
exposed over web services using TDS packets encapsulated within SOAP
(protocol) requests. When the data is accessed over web services, results are
returned as XML.

For relational data, T-SQL has been augmented with error handling features
(try/catch) and support for recursive queries with CTEs (Common Table
Expressions). SQL Server 2005 has also been enhanced with new indexing
algorithms, syntax and better error recovery systems. Data pages are check
summed for better error resiliency, and optimistic concurrency support has been
added for better performance. Permissions and access control have been made
more granular and the query processor handles concurrent execution of queries in a
more efficient way. Partitions on tables and indexes are supported natively, so
scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL
Server 2005 to let it integrate with the .NET Framework.

SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of
allowing usage of database connections for multiple purposes.

SQL Server 2005 introduced DMVs (Dynamic Management Views), which are
specialized views and functions that return server state information that can be
used to monitor the health of a server instance, diagnose problems, and tune
performance.

SQL Server 2005 introduced Database Mirroring, but it was not fully supported
until the first Service Pack release (SP1). In the initial release (RTM) of SQL
Server 2005, database mirroring was available, but unsupported. In order to
implement database mirroring in the RTM version, you had to apply trace flag
1400 at startup. Database mirroring is a high availability option that provides
redundancy and failover capabilities at the database level. Failover can be
performed manually or can be configured for automatic failover. Automatic
failover requires a witness partner and an operating mode of synchronous (also
known as high-safety or full safety).
Database Designs:-
College & Qualification Tables
System Design:-

Design:-Software design is actually a multistep process that focuses on four

distinct attributes of a program: data structure, software architecture, interface
representations, and procedural (algorithmic) detail. The design process translates
requirements into a representation of the software that can be assessed for quality
before coding begins. Like requirements, the design is documented and becomes
part of the software configuration.

Software engineers design computer based systems, but the skills required at
each level of design work are different. At the data and architectural level, design
focuses on patterns as they apply to the application to be built. At the interface
level, human ergonomics often dictate our design approach. At the component
level, a “programming approach” leads us to effective data and procedural designs.

Why is it important: - You wouldn’t attempt to build a house without a

blueprint, would you? You’d risk confusion, errors, a floor plan that didn’t make
sense, windows and doors in the wrong place a mess. Computer software is
considerably more complex than a house; hence, we need a blueprint— the design.

What are the steps: - Design begins with the requirements model. We work to
transform this model into four levels of design detail: the data structure, the system
architecture, the interface representation, and the component level detail. During
each design activity, we apply basic concepts and principles that lead to high
quality.

What is the work product: - Ultimately, a Design Specification is produced.

The specification is composed of the design models that describe data, architecture,
interfaces, and components. Each is a work product of the design process. How do
I ensure that I’ve done it right? At each stage, software design work products are
reviewed for clarity, correctness, completeness, and consistency with the
requirements and with one another.

System Design

There are five ways to design the system:-

System design develops the architectural detail required to build a system or

product. The system design process encompasses the following activities:

1) Decomposability:-the facility with which a design method helps the

designer to decompose a large problem into sub problems that are easier to
solve.

2) Composability:-the degree to which a design method ensures that program

components (modules), once designed and built, can be reused to create
other systems.

3) Understandability:-the ease with which a program component can be

understood without reference to other information or other modules.
 4) Continuity:-the ability to make small changes in a program and have these
changes manifest themselves with corresponding changes in just one or a
very few modules.

5) Protection:-an architectural characteristic that will reduce the propagation

of
Side effects if an error does occur in a given module.

Detailed Design

The interface design describes how the software communicates within itself, with
systems that interoperate with it, and with humans who use it. An interface implies
a flow of information (e.g., data and/or control) and a specific type of behavior.
Therefore, data and control flow diagrams provide much of the information
required for interface design.

The component-level design transforms structural elements of the software

architecture into a procedural description of software components. Information
obtained from the serves as the basis for component design. During design we
make decisions that will ultimately affect the success of software construction and,
as important, the ease with which software can be maintained.

Importance of Software Design:-

The importance of software design can be stated with a single word quality. Design
is the place where quality is fostered in software engineering. Design provides us
with representations of software that can be assessed for quality. Design is the only
way that we can accurately translate a customer's requirements into a finished
software product or system. Software design serves as the foundation for all the
software engineering and software support steps that follow. Without design, we
risk building an unstable system one that will fail when small changes are made;
one that may be difficult to test, one whose quality cannot be assessed until late in
the software process, when time is short and many dollars have already been spent.

The Design Process

Software design is an iterative process through which requirements are translated

into a “blueprint” for constructing the software. Initially, the blueprint depicts a
holistic view of software. That is, the design is represented at a high level of
abstraction a level that can be directly traced to the specific system objective and
more detailed data, functional, and behavioral requirements. As design iterations
occur, subsequent refinement leads to design representations at much lower levels
of abstraction. These can still be traced to requirements, but the connection is more
subtle.

Design and Software Quality:-Throughout the design process, the quality of

the evolving design is assessed with a Series of formal technical reviews or design
walkthroughs.
There are three characteristics that serve as a guide for the evaluation of a good
design:-
1) The design must implement all of the explicit requirements contained in the
analysis model, and it must accommodate all of the implicit requirements
desired by the customer.
 2) The design must be a readable, understandable guide for those who generate
code and for those who test and subsequently support the software.
3) The design should provide a complete picture of the software, addressing
the data, functional, and behavioral domains from an implementation
perspective.

In order to evaluate the quality of a design representation, we must establish

technical criteria for good design. Now, we discuss design quality criteria
in some detail. For the time being, we present the following guidelines:-

1) A design should be modular; that is, the software should be logically

partitioned
Into elements that perform specific functions and sub functions.

2) A design should contain distinct representations of data, architecture,

interfaces
and components (modules).

3) A design should lead to data structures that are appropriate for the objects to

be implemented and are drawn from recognizable data patterns.

4) A design should lead to components that exhibit independent functional

characteristics.

5) A design should lead to interfaces that reduce the complexity of connections

between modules and with the external environment.

6) A design should be derived using a repeatable method that is driven by

information obtained during software requirements analysis.