View with the images and charts

M E C H A N I S M O F A U T O M AT E D S T U D E N T I D E N T I T Y C A R D

INTRODUCTION
It is highly essential for an educational institute to provide ID card to each and every student of
it. ID card is generally considered to be the summary of a student’s information. According to
this circumstance one institute must produce and provide to the student.
The project “Design and Implementation of Automated Student ID Card Generation” is created
to reduce the human effort, which we are to introduce a fully automated solution that will
generate and maintain the student ID card.
1.1 ID Card
An identity document (also called a piece of identification or ID, or colloquially as one's
'"papers"') is any document which may be used to verify aspects of a person's personal identity. If
issued in the form of a small, mostly standard-sized card, it is usually called an identity card (IC)
[1].
A card giving identifying data about a person, as full name, address, age, and color of hair and
eyes, and often containing a photograph: for use as identification at a place of employment,
school, club, etc[2].So a student id card is the identification card that holds the above
characteristics about a certain student.
1.2 ID Card Generation
ID card generation refers to the process to generate, maintain and distribution of the ID Cards. In
the traditional process the administration has to take sufficient information about the student.
Then the authority authenticates the information and if it is true they provide the ID Card to its
owner. All these process are done manually and for this the process is too much time consuming.
Students are to wait for several days to have their ID Card.

1.3 Automated ID Card Generation

In our automated system the total process of card generation is done with the help of computer
through this software rather than manually. Student’s information are collected and stored in
database and at the same time the administration can provide the student ID Card. So the concept
of time wasting is totally eliminated in here. Moreover this process is highly compatible with
data storing and manipulating.

1.4 Feasibility study

An important outcome of the preliminary investigation is the determination that the system
requested is feasible. Feasibility study is carried out to select the best system that meats the
performance requirements.
1.4.1 Technical Feasibility
The technical feasibility issues usually raised during the feasibility stage of investigation
includes these. This software is running in Windows XP operating system, which can be easily
installed the hardware required is Pentium based server.
1.4.2 Operational feasibility
This feasibility test asks if the system will work when it is developed and installed. Operational
feasibilities that are involved in this project: the proposed system offers greater level of user
friendly behaviors. It produces best results and gives high performance. It can be implemented
easily. So this project is operationally feasible.
1.4.3 Economical Feasibility
The economical feasibility for this project are: the cost to conduct a full system investigation is
possible. There is no additional manpower needed. There is no additional cost involved to
maintain the proposed system.
1.5 Conclusion
Our project provides all kinds of facilities as required. From every point of view, this project is
feasible enough. The ID Card will provide all the information of the card holder correctly as
possible.

REQUIREMENTS ANALYSIS
Several software development approaches have been proposed and largely used in practice. All
processes resolve a paradox of requirements engineering, the need to formulate a clear vision of
a system in a world of constantly changing requirements. The fundamental principle underlying
requirements engineering is the assumption that a system should be clearly specified before its
design and implementation.
2.1 Physical Layout of the ID Card
A student ID Card generally deals with the following fields:

 Students Name
 Class Roll Number
 Registration Number
 Session
 Name of the department
 Hall name
We must ensure all the features to our automated ID Card as all these information must be hold
on the card.
2.2 Administrative requirements
To demonstrate the administrative requirements we need too meet the administration the
following parameters:

 Basic student information

 The feature Add / remove department name and hall name
 Take student snap from a real time video streaming
 Check the printable form
 Edit the total information
 Go to the print process
 Find student information from unique ID number.

2.3 Non Requirements

 System will not enforce any security .Anybody who access to the computer will be able
to access this software and perform the operation
 System will not maintain any inventory
 The data stored in database is editable. Anyone access in this system can edit data as
needed.

2.4 Conclusion
ID card generation refers to the process to generate, maintain and distribution of the ID Cards.
What requirement it needs, is provided correctly. At the same time we must be concern about the
non-requirement. Data must be secured and safe.
SYSTEM ANALYSIS
3.1 Systems Analysis
Systems analysis is the study of sets of interacting entities, including computer systems analysis.
This field is closely related to operations research. It is also an explicit formal inquiry carried out
to help someone identify a better course of action and make a better decision than he might
otherwise have made [3].
3.1.1 Systems Analysis in Computer Science

The development of a computer-based information system includes a systems analysis phase

which produces or enhances the data model which itself is a precursor to creating or enhancing a
database There are a number of different approaches to system analysis. When a computer-based
information system is developed, systems analysis would constitute the following steps:

 The development of a feasibility study, involving determining whether a project is

economically, socially, technologically and organizationally feasible.
 Conducting fact-finding measures, designed to ascertain the requirements of the system's
end-users. These typically span interviews, questionnaires, or visual observations of work
on the existing system.
  Gauging how the end-users would operate the system (in terms of general experience in
using computer hardware or software), what the system would be used for etc[4].

3.2 Analysis Phase of ID Card Generation

The systems analysis process is an iterative one that cycles repeatedly through the following
interrelated and somewhat indistinct phases:

1. Problem statement,
2. Alternative designs
3. Mathematical formulation
4. Evaluation of alternatives
5. Selection and implementation of the most preferred solution [5].

3.3 System Analysis of Automated Student ID Card Generation

3.3.1 Problem statement

 The system is defined in terms of its environment, goals, objectives, constraints,

criteria, actors (decision makers, participants in the system, impacted constituency)
and other objects and their attributes; According to our project the environment is
Microsoft based operating system. The primary goals and objectives are to reduce the
human effort and produce the automated student ID Card. To ensure student
participation in the process, we conducted the true information about the student body
to assess the awareness level, security and privacy concerns. These are the constraints
of our project.

3.3.2 Alternative designs

 The solutions are identified. In our project the successful run of the parts of the
solution can be referred to as alternative designs.

3.3.3 Mathematical Formulation

 A mathematical description of the system is developed, tested, and validated; In our

project the mathematical formulations are done by database management system.

3.3.4 Evaluation of Alternatives

 The mathematical model is used to evaluate and rank the possible alternative designs
by means of the criteria. In ID Card Generation the mathematical model that is our
database management system is used to satisfy the tasks.
3.3.5 Selection and Implementation of the most Preferred Solution
  The process includes feedback loops in which the outcomes of each phase are
reconsidered based on the analyses and outcomes of the other phases. For example,
during the implementation phase, constraints may be uncovered that hinder the
solution's implementation and thus cause the mathematical model to be reformulated.
The analysis process continues until there is evidence that the mathematical structure
is suitable; that is, it has enough validity to yield answers that are of value to the
system designers or the decision maker. After the successful running we choose and
implement the most successful running solution as our project.

3.4 Conclusion
This phase is an important phase in software engineering. What will be provided, how the user
will handle the software, if any problem occurs how it will be recovered, all this section are
defined as clear as possible, in this project.

SYSTEM DESIGN

4.1 Definition of Software System Design

Software system design is a process of problem-solving and planning for a software solution.
After the purpose and specifications of software are determined, software developers will design
or employ designers to develop a plan for a solution. It includes low-level component and
algorithm implementation issues as well as the architectural view [6].

Designing software is an exercise in managing complexity. The complexity exists within the
software design itself. Software design is very similar to systems design. It can span multiple
technologies and often involves multiple sub-disciplines. Software specifications tend to be fluid,
and change rapidly and often, usually while the design process is still going on [7].

4.2 Design Concepts

The design concepts provide the software designer with a foundation from which more
sophisticated methods can be applied. A set of fundamental design concepts has evolved. They
are:

 Abstraction :- Abstraction is the process or result of generalization by reducing the

information content of a concept or an observable phenomenon, typically in order to
retain only information which is relevant for a particular purpose.
 Refinement :- It is the process of elaboration. A hierarchy is developed by decomposing
a macroscopic statement of function in a stepwise fashion until programming language
statements are reached. In each step, one or several instructions of a given program are
decomposed into more detailed instructions. Abstraction and Refinement are
complementary concepts.
 Modularity :- Software architecture is divided into components called modules.
  Software Architecture :- It refers to the overall structure of the software and the ways in
which that structure provides conceptual integrity for a system. A good software
architecture will yield a good return on investment with respect to the desired outcome of
the project, e.g. in terms of performance, quality, schedule and cost.

 Control Hierarchy :- A program structure that represent the organization of program

components and implies a hierarchy of control.

 Structural Partitioning :- The program structure can be divided both horizontally and
vertically. Horizontal partitions define separate branches of modular hierarchy for each
major program function. Vertical partitioning suggests that control and work should be
distributed top down in the program structure.

 Data Structure :- It is a representation of the logical relationship among individual

elements of data.

 Software Procedure - It focuses on the processing of each modules individually

 Information Hiding :- Modules should be specified and designed so that information

contained within a module is inaccessible to other modules that have no need for such
information [8].

4.3 Design Considerations

There are many aspects to consider in the design of a piece of software. The importance of each
should reflect the goals the software is trying to achieve. Some of these aspects are:

 Compatibility :- The software is able to operate with other products that are designed for
interoperability with another product. For example, a piece of software may be backward-
compatible with an older version of itself.
 Extensibility :- New capabilities can be added to the software without major changes to
the underlying architecture.
 Fault-tolerance :- The software is resistant to and able to recover from component
failure.

 Maintainability :- The software can be restored to a specified condition within a

specified period of time. For example, antivirus software may include the ability to
periodically receive virus definition updates in order to maintain the software's
effectiveness.

 Modularity :- the resulting software comprises well defined, independent components.

That leads to better maintainability. The components could be then implemented and
tested in isolation before being integrated to form a desired software system. This allows
division of work in a software development project.
 Packaging :- Printed material such as the box and manuals should match the style
designated for the target market and should enhance usability. All compatibility
 information should be visible on the outside of the package. All components required for
use should be included in the package or specified as a requirement on the outside of the
package.
 Reliability :- The software is able to perform a required function under stated conditions
for a specified period of time.
 Reusability :- the software is able to add further features and modification with slight or
no modification.
 Robustness :- The software is able to operate under stress or tolerate unpredictable or
invalid input. For example, it can be designed with resilience to low memory conditions.
 Usability :- The software user interface must be usable for its target user/audience.
Default values for the parameters must be chosen so that they are a good choice for the
majority of the users.

4.4 The Use Case Diagram

 Fig 4.1: The Use Case Diagram of Automated Student Identity Card Generation.

4.5 Class Diagram

 Fig 4.2: The Class Diagram of Automated Student Identity Card Generation.

4.6 Conclusion

We have followed some designing criterion so that this software will be more user friendly. The
software is able to operate with other products that are designed for interoperability with another
product.

IMPLEMENTING the SYSTEM

During this phase as implementation, the system is either developed or purchased (in the case of
package software). This phase is usually the longest and most expensive part of process. The
phase has three steps.

5.1 System Construction

System Construction consists of all of the activities required to build and validate the new system
to the point at which it can be turned over for System Acceptance. Development efforts in this
phase are based on the technical solution created during System Design, which, in turn, was
based on the functional and operational requirements captured during System Requirements

Analysis, Included in this phase is the construction of all components of the system, including
utilities required to adequately prepare and load the data. In addition, System Construction
consists of a series of tests of the system components, with each set of tests being performed
against a progressively larger grouping of components until the operation of the system in its
entirety has been verified[9].

The system is built and tested to make sure it performs as designed.

Installation: Prepared to support the installed system. Microsoft Windows XP, Vista, Se7en and
all XP version are compatible for the installation of this software.

5.2 Support Plan

This phase consist of three major part. They are:

 Back-end implementation
 Front-end Implementation

 Combined implementation including the previous two type of implementation.

 A methodology is a formalized approach to implementing the SDLC. The methodology

will vary depending on whether the emphasis is on business processes or on the data that
supports the business. We have to study and analyze the information system properly.
Implementation is the main phase of developing a system. Gathered information and
knowledge about the proposed system will now have to be used efficiently to develop the
system.

 Among the three parts of implementation, back-end of a system mainly consists of the
data and related information which the users are not aware of. Users do not even have
any idea about how many tables are there in the database. A back-end database stores data
but does not include end-user application elements such as stored queries, forms, macros
or reports.

 Front-end of a system is the user interface that the users see when they interact with the
system usually there are different forms for the users to access the data. With front-end
users can read, modify, and enter data to the database without having any knowledge
about the database knowledge.

5.3 Software User Interface

In this section, we are introducing some user interfaces of this project:

5.3.1 Startup Screen

First of all the user have to run the executable file. After that the following interface will appear
first:

Fig 5.1: The Startup Screen of the Software.

5.3.2 The Student Information and Image Capturing Interface

After clicking the add button the following interface will appear where the author is to fill-up the
student information and capture the image from real time video streaming:
Fig 5.2: Student Information and Image Capturing.

5.3.3 Generate ID Demo and Save to Database

After providing all information, capturing image and generating the ID demo the following
interface will appear:
Fig 5.3: Generate ID Demo and Save to Database.

5.4 Conclusion

In the startup screen we see the data bank which will be extended in future. Here we can add
more options as student result system, teacher’s salary payment system and so on. Capturing the
photograph of the student by the webcam and providing the required information we will get the
final student identity card. After saving all this in database, we can see all this information in the
data bank.

CONCLUSION and FUTURE WORK

6.1 Conclusion

From a proper analysis of positive points and constraints on the component, it can be safely
included that the product is a highly efficient GUI based component. After we have completed
the project we are sure the problems of existing system would overcome. The “Automated
Student ID Card Generation” process made computerized to reduce human errors and to increase
the efficiency. The maintenance of the records is made efficient, as all the records are stored in
Microsoft SQL Server 2008 database, through which data can be retrieved and deleted easily.
The editing is also made simpler. The authority is just to provide the required information and to
print the Identity card with the student image which is captured in a real time video streaming.
The computerization of the Automated Student Identity Card Generation will not only improves
the efficiency but also reduces human stress thereby indirectly improving human recources.

6.2 Future Work

Our plan is to provide the student a plastic made identity card which is more familiar now-a-
days. A specific identity number will also be included as Social Security number. A digital
signature will be included through digital touch pad and digital pen. And the additional part of
this project is the Data Bank. We can add more software on this single project such as Teacher’s
salary payment system, student result system and so on.

References

[1] http://en.wikipedia.org/wiki/ID_Card

[2] http://dictionary.reference.com/browse/ID+card

[3] http://en.wikipedia.org/wiki/Systems_analysis

[4] Christopher J. Date "An Introduction to Database Systems".

[5] http://www.answers.com/topic/systems-analysis

[6] http://en.wikipedia.org/wiki/Software_design

[7] http://www.developerdotstar.com/mag/articles/reeves_design.html

[8] http://en.wikipedia.org/wiki/Software_design

[9] NYS Project Management Guidebook