INTRODUCTION

INTRODUCTION
1
1. INTRODUTION
1.1 PROJECT PROFILE
Anganawadi Management System (AMS) mainly used to decrease the workload of

anganawadi workers. The system is followed at present, is not automated. In the existing
system each and every time reference should be manually. There are high possibilities to
commit errors and mistakes, which leads to produce wrong statements. The existing
system is fully manual that means the record are maintained and keep manually by
workers. An Anganawadi has mainly two workers. One is the main and another one is the
assistant .The main worker who maintains and controls the major records of Anganawadi
including child record, staff record and survey record etc.The main disadvantage of the
existing system is that it is very time consuming process and also very difficult to handle
the whole records. When the record contains any type of failure then we cannot backup the
record .It gives greater workload to the workers.
This system is helps to store the major records of anganawadies and also through this
system a new user can easily register the jobs in anganawadies
The users of the system are
 Admin
 Panchayath Officer
 Anganawadi Worker
 Applicant
2
ABOUT THE DEVELOPING TOOLS
3
2. ABOUT THE DEVELOPING TOOLS
2.1 INTRODUTION TO ASP.NET
ASP.NET is an open-sourceserver-side web application framework designed for web

development to produce dynamic web pages. It was developed by Microsoft to
allow programmers to build dynamic web sites, web applications and web services.
It was first released in January 2002 with version 1.0 of the .NET Framework, and is the
successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on
the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using
any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET
components to process SOAP messages.
ASP.NET's successor is ASP.NET Core. It is a re-implementation of ASP.NET as a

modular web framework, together with other frameworks like Entity Framework. The new
framework uses the new open-source .NET Compiler Platform (codename "Roslyn") and
is cross platform. ASP.NET MVC, ASP.NET Web API, and ASP.NET Web Pages (a platform
using only Razor pages) have merged into a unified MVC 6.
Advantages of ASP.NET
 Keep you Asp.net applications secured with the built-in Windows authentication
and per-application configuration.
 Asp.Net has reduced the long lines of code required to develop large applications.
 Asp.Net and Html together generate dynamic web pages smoothly.
 Being an ideal server-side scripting technology, Asp.Net code first runs on Windows
server before displaying on the web browser.
 Asp.Net framework is language independent, means you can choose any
programming language which best suited to you application.
 With the built-in configuration information, Asp.Net is easy to deploy.
 The windows web server thoroughly monitors the web pages, multiple components,
and applications running over it.
4
 The Dot Net Framework quickly gives an alert for memory leaks, unbounded loops,
and other wrong behaviors, immediately killing them and restart them over again.
 Asp.Net features like early binding, JIT compilation, caching services and native
optimization supports gives your application the high level of performance.
 All the Asp.Net applications are highly monitored and managed to help application
available to handle requests.
 The best part of Dot Net Framework is it has its own built-in caching features.
 The content and the program logic are separated in the .Net Framework, thus
reducing the program inconveniences.
2.2 SCRIPTING LANGUAGE:- C SHARP
C# is a simple, modern, general-purpose, object-oriented programming language

developed by Microsoft within its .NET initiative led by Anders Hejlsberg. This tutorial will
teach you basic C# programming and will also take you through various advanced concepts
related to C# programming language.
C# is designed for Common Language Infrastructure (CLI), which consists of the

executable code and runtime environment that allows use of various high-level languages
on different computer platforms and architectures.
The following reasons make C# a widely used professional language −
 It is a modern, general-purpose programming language
 It is object oriented.
 It is component oriented.
 It is easy to learn.
 It is a structured language.
 It produces efficient programs.
 It can be compiled on a variety of computer platforms.
 It is a part of .Net Framework.
5
2.3 SQL SERVER
SQL Server is software (A Relational Database Management System) developed by

Microsoft. It is also called MS SQL Server. It is implemented from the specification of
RDBMS. Microsoft SQL Server is a highly scalable product that can be run on anything from
a single laptop, to a network of high-powered cloud servers, and anything in between.
Features of MS SQL Server
 MS SQL Server is implemented from the specification of RDBMS.

 MS SQL Server is highly scalable.
 MS SQL Server is platform independent.
 MS SQL Server can be run on a single laptop or a network of cloud servers.
 MS SQL Server is both a GUI and command based software.
 MS SQL Server supports SQL (SEQUEL) language which is an IBM product, non-
procedural, common database and case insensitive language.
2.4 ADO.NET
ADO.NET is a data access technology from the Microsoft .NET Framework that provides
communication between relational and non-relational systems through a common set of
components. ADO.NET is a set of computer software components that programmers can
use to access data and data services from a database. It is a part of the base class
library that is included with the Microsoft .NET Framework. It is commonly used by
programmers to access and modify data stored in relational database systems, though it
can also access data in non-relational data sources. ADO.NET is sometimes considered an
evolution of ActiveX Data Objects (ADO) technology, but was changed so extensively that it
can be considered an entirely new product.
 Single Object-oriented API: ADO.NET provides a single object-oriented set of
classes. There are different data providers to work with different data sources but
the programming model for all these data providers work in the same way. You
6
should be aware of only one data provider. You just need to change class names and
connection strings.
 Managed Code: The ADO.NET classes are managed classes. CLR takes care of
language independency and automatic resource management.
 Deployment: Microsoft uses MDAC (Microsoft Data Access Component), which is
used as ActiveX component in .NET Framework (X is extensible component, when X
is written after a term means extensible). .NET components takes care of
deployment which was difficult previous technologies used in deployment.
 XML Support: ADO.NET data is cached and transferred in XML (EXtensible Markup
Language) format. XML provide fast access of data for desktop and distributed
applications. XML is plain text designed to transport and store data and is self-
descriptive.
 Visual Data Components:.NET offers ADO.NET components and data-bound
control to work in visual form. You can use these components without writing long
codes and can achieve result in no time.
 Performance and scalability: Performance and scalability are two major factors
when developing web-based application and services. Disconnected cached data in
XML help in performance and scalability.
2.5 GIT
Git is a version-control system for tracking changes in computer files and coordinating
work on those files among multiple people. It is primarily used for source-code
management in software development, but it can be used to keep track of changes in any
set of files. As a distributed revision-control system, it is aimed at speed data integrity, and
support for distributed, non-linear workflows.
Git was created by Linus Torvalds in 2005 for development of the Linux kernel, with other
kernel developers contributing to its initial development. Its current maintainer since 2005
is Junio Hamano.
As with most other distributed version-control systems, and unlike most client–
server systems, every Git directory on every computer is a full-fledged repository with
7
complete history and full version-tracking abilities, independent of network access or a
central server.
Git is free and open-source software distributed under the terms of the GNU General Public
License version 2.
8
SYSTEM ANALYSIS
9
3. SYSTEM ANALYSIS
3.1 INTRODUCTION TO SYSTEM ANALYSIS
The term analysis and synthesis come from Greek where they mean respectively “to take
apart and to put together”. These terms are used in scientific disciplines from mathematics
and logic to economic and psychology to denote similar investigation procedures. Analysis
is defined as the procedure by which we break down an intellectual or substantial whole
into parts. Synthesis is defined as the procedure by which we combine separate elements
or components in order to form a coherent whole.
A system is an orderly grouping of interdependent components linked together according

to a plan to achieve a specific objective. That is a system is a combination of resource
working together to convert inputs into useful outputs. The resources used by the system
include personal facilities and lateral equipment. System analysis is a general term that
refers to an orderly structured process for identifying and solving problems. We call that
system Analysis process, the life cycle methodology, since it relates to our significant
phases in the life cycle of all business information system.
The system is followed at present, is not automated. In the existing system each and every
time reference should be manually. There are high possibilities to commit errors and
mistakes, which leads to produce wrongstatements.
The objectives of the system analysis are:
 Identifying the need.
 Analyzing the existing and proposed system.
 Evaluating the feasibility study.
 Perform economic and technical analysis.
 Identifying the hardware and software requirements.
 Allocating functions to the hardware and software.
 Create a system definition
10
3.2 EXISTING SYSTEM
The existing system is fully manual that means the record are maintained and keeped
manually by workers. An Anganawadi has mainly two workers. One is the main and
another one is the assistant .The main worker who maintains and controls the major
records of Anganawadi. The main disadvantage of the existing system is that it is very time
consuming process and also very difficult to handle the whole records. When the record
contain any type of failure then we cannot backup the record .It gives greater workload to
the workers. “ANGANAWADI MANAGEMENT SYSTEM“has mainly two workers. One is the
main and another one is the assistant .The main worker who maintains and controls the
major records of Anganawadi including child record, staff record and survey record etc.
3.3 LIMITATIONS OF EXISTING SYSTEM
 Difficulty to handle the large information

 Cost consumption is high
 It gives greater workload to the workers
 The system is manual one so errors occurs may be high.
 There may be chances for losing the records
 No automated tool like computer is used the processing.
 Less security
 Data duplication
3.4 FEASIBILITY STUDY
A feasibility study is an analysis used in measuring the ability and likelihood to complete
a project successfully including all relevant factors. It must account for factors that affect it
such as economic, technological, legal and scheduling factors. Project managers use
feasibility studies to determine potential positive and negative outcomes of a project
before investing a considerable amount of time and money into it.
11
Feasibility analysis involves 8 steps:
 Form a project team and appoint a project leader

 Prepare system flow charts.
 Enumerate potential candidate system.
 Describe and identifying characteristics of candidate systems.
 Determine and evaluate performance and cost effectiveness of each candidate
system.
 Weight system performance and cost data.
 Select the best candidate system.
 Prepare and report final project directive to management.
Three key considerations involved in the feasibility study are:
 Economic feasibility
 Technical feasibility
 Behavioral feasibility
 3.4.1 Economic feasibility
Economic feasibility is the most frequently used method for evaluating the effectiveness
of the candidate system, more commonly known as cost/benefit analysis. The procedure
is to determine the benefit and saving that are accepted from a candidate system and
compare them with costs. If benefits and outweigh costs, then decision is made to design
and implements the system. Otherwise further justification or alternative in the proposed
system will have to be made if it is to have a chance of being approved.
The proposed system is cost effective because of its compatibility and effort saving
nature. The system reduces unnecessary expenses and waste of man hours in searching
12
and understanding the bulky leader reports. It benefits the user in getting hands on
experience.
 3.4.2 Technical feasibility
Technical feasibility centers on the existing systems and to what extent it supports the
proposed system. This involves financial consideration to accommodate technical
enhancements. If the budget is a serious constraint, then the project is judged not
feasible. Minimum requirement of the proposed system is a printer, which will not add
additional expenses in implementing the system.
 3.4.3 Behavioral feasibility
People are inherently resent to change and computers have been known to facilitate. An
estimate should be made of how strong a reaction the user staff is likely to have towards
the development of a computerized system. It is a common knowledge that computer
installations have something to do with turnovers, and changes in employee job status.
Therefore it is understandable that the introduction of a candidate system requires
special ways of conduct.
3.5 FACT FINDING TECHNIQUES
The success of any project depends upon the accuracy of available data. Accurate
information can be collected with the help of certain methods/techniques. These specific
methods for finding information of the system are termed as fact finding techniques.
Interview, Questionnaire, Record View and Observations are the different fact finding
techniques used in this project.
 Interview:
This method is used to collect the information from groups or individuals. We

select the people who are related with the system for the interview. In this method, we sit
face to face with people and record their responses.
 Record View:
13
The information related to the system is available in the source like companies,
documents, websites and other records. This record review helped me to get valuable
information about the system.
 Onsite Observation:
Unlike the other fact finding technique, in this method we visit the organization
and observe and understand the working of the existing system, flow of the system, the
users of the system etc.
3.6 PROPOSED SYSTEM
Due to the above mentioned disadvantage in the existing system if has been proposed for
the new system, which will overcome these difficulties. So the new system is developed
with the help of the ASP.NET and SQL Server.
ADVANTAGES
The overall system is under the control of administrator hence the system is centralized
one.
 High speed and accuracy.

 Provide high security.
 Good user interface.
 Easy edit
 User friendly.
 Reliable
 Efficiency.
 Less effort
14
SYSTEM SPECIFICATION
15
4. SYSTEM SPECIFICATION
4.1 HARDWARE SPECIFICATION
This phase of the software development process deals with a brief study of different
hardware used in the computerized system. There is a list of hardware materials used
during the making and also during the use of the proposed system. As the new system to be
made into a computerized functional system, requirement of a computer is must. All the
hardware needed here are generally the basic configuration of a typical office computer.A
list of the hardware requirement used in the system given below:
Processor : Intel core i3
System Bus : 64bits
Memory : 4GB RAM or Higher
Hard Disk : 320GB or Higher
Keyboard : 104 Keys
4.2 SOFTWARE SPECIFICATION
Software configuration:
1. Operating System :Microsoft Windows 7
2. IDE : Visual Studio 2010
3. Front End : Asp.Net
4. Back End : SQL Server 2008
16
 Asp.Net
Microsoft .NET technology you will have access to a new generation of advanced software
joining the best of computing and communications in a revolutionary new way. The effect
will be to totally transform the Web and every other aspect of the computing experience.
.NET enables developers, businesses, and consumers to harness technology on their terms.
.NET will allow the creation of truly distributed Web services that will integrate and
collaborate with a range of complementary services to help customers in ways that today’s
dotcoms can only dream of. The fundamental idea behind .NET is that the focus is shifting
from individual Web sites or devices connected to the Internet to constellations of
computers, devices, and services that work together to deliver broader, richer solutions.
People will have control over how, when, and what information is delivered to them.
Computers, devices and services will be able to collaborate with each other to provide rich
services, instead of being isolated islands where the user provides the only integration.
Businesses will be able to offer their products and services in a way that lets customers
seamlessly embed them in their own electronic fabric. Microsoft .NET will make computing
and communicating simpler and easier than ever. It will spawn a new generation of
Internet services, and enable tens of thousands of software developers to create
revolutionary online services and businesses. It will put you back in control, and enable
greater control of your privacy, digital identity, and data. And software is what makes it all
possible. However, Microsoft’s .NET technology will only succeed if others adopt this new
standard.
 The ASP.NET worker process is a distinct worker process, aspnet_wp.exe, separate

from inetinfo.exe (IIS process), and the process model in ASP.NET is unrelated to
process isolation settings in IIS.
 ASP.NET could be run on non-Microsoft Platforms also.
 We are no longer constrained to the two scripting languages available in traditional
ASP: Any fully compliant .NET language can now be used with ASP.NET, including
C# and VB.NET
 In contrast, ASP.NET pages are always compiled into .NET classes housed within
assemblies. This class includes all of the server-side code and the static HTML, so
17
once a page is accessed for the first time (or any page within a particular directory is
accessed), subsequent rendering of that page is serviced by executing compiled
code. This eliminates all the inefficiencies of the scripting model of traditional ASP.
There is no longer any performance difference between compiled components and
server-side code embedded within a page they are now both compiled components.
There is also no performance difference between interspersing server-side code
blocks among static HTML elements, and writing large blocks of server-side code
and using Response .Write() for static HTML content. Also, because the .aspx file is
parsed into a single code file and compiled, it is not possible to use multiple server-
side languages within a single .aspx file.
 But in ASP.NET In addition to improved performance over the interpreted model,
pages that are compiled into classes can be debugged using the same debugging
tools available to desktop applications or component developers. Errors with pages
are generated as compiler errors, and there is a good chance that most errors will be
found at compilation time instead of runtime, because VB.NET and C# are both
strongly typed languages. Plus, all the tools available to the .NET developer are
applicable to the .aspx developer
 In ASP.NET it is no longer possible to include executable code outside the scope of a
function within a script block marked as runat=server, and conversely, it is no
longer possible to define a function within a pair of server-side script tags. 7) But in
ASP.NET, you are now required to place the Language directive with a Page
directive, as follows: You can have as many lines of directives as you need.
Directives may be located anywhere in your .apsx file but standard practice is to
place them at the beginning of the file. Several new directives have been added in
ASP.NET
 SQL Server 2008
Microsoft SQL Server is a relational database management system developed

by Microsoft. As a database server, it is a software product with the primary function of
storing and retrieving data as requested by other software applications—which may run
18
either on the same computer or on another computer across a network (including the
Internet).
Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed at
different audiences and for workloads ranging from small single-machine applications to
large Internet-facing applications with many concurrent users.
The main mode of retrieving data from a SQL Server database is querying for it. The query
is expressed using a variant of SQL called T-SQL, a dialect Microsoft SQL Server shares
with Sybase SQL Server due to its legacy. The query declaratively specifies what is to be
retrieved. It is processed by the query processor, which figures out the sequence of steps
that will be necessary to retrieve the requested data. The sequence of actions necessary to
execute a query is called a query plan. There might be multiple ways to process the same
query. For example, for a query that contains a join statement and a select statement,
executing join on both the tables and then executing select on the results would give the
same result as selecting from each table and then executing the join, but result in different
execution plans. In such case, SQL Server chooses the plan that is expected to yield the
results in the shortest possible time. This is called query optimization and is performed by
the query processor itself.
 Windows 7
Windows 7 is a personal computer operating system that was produced by Microsoft as

part of the Windows NT family of operating systems. It was released to manufacturing on
July 22, 2009 and became generally available on October 22, 2009, [7] less than three years
after the release of its predecessor, Windows Vista. Windows
7's server counterpart, Windows Server 2008 R2, was released at the same time.
Windows 7 was primarily intended to be an incremental upgrade to Microsoft Windows,

intended to address Windows Vista's poor critical reception while maintaining hardware
and software compatibility. Windows 7 continued improvements on Windows
Aero (the user interfaceintroduced in Windows Vista) with the addition of a
redesigned taskbar that allows applications to be "pinned" to it, and new window
management features. Other new features were added to the operating system, including
19
libraries, the new file sharing system HomeGroup, and support for multitouch input. A new
"Action Center" interface was also added to provide an overview of system security and
maintenance information, and tweaks were made to the User Account Control system to
make it less intrusive. Windows 7 also shipped with updated versions of several stock
applications, including Internet Explorer 8, Windows Media Player, and Windows Media
Center.
20
SYSTEM DESIGN
21
5. SYSTEM DESIGN
5.1 INTRODUCTION TOSYSTEM DESIGN
The system design is the most creative and challenging phase of system development life
cycle. It is an approach for the creation of proposed system, in which the logic and details
structure of the proposed system is designed, which will help the system coding. The most
creative and challenging phase of the system development process is design phase it is a
solution, a how to approach to the creation of the proposed system. Design is the first step
in the development of the engineered product is initiated only after a clear exposition of
expected product is available. System design is vital for efficient database management. It
provides the understanding of procedural detailnecessary for implementing the system.A
number of sub-system is to be identified which constitutes the whole system.
From a project management point of view, software design is conducted in two steps.
Preliminary design is concerned with the information of requirements into data and
software architecture. Details design focuses on refinement to the architectural
representation.Design starts with the system requirement specification and converts it to a
physical reliability, response time, throughput of the system, maintainability, expandability
should be taken into account.
The database tables are designed by using the entire necessary field in a compact and
correct manner. Care has been taken to be avoiding redundant and duplicated field. The
important of software design can be started with word quality .Design is place where
quality is fostered in software development. Designs are the only way where requirements
are actually translated in to a finished software product or system
Logical design
The logical design of a system pertains to an abstract representation of the data flows,
inputs and outputs of the system. This is often conducted via modeling, using an over-
abstract (and sometimes graphical) model of the actual system. In the context of systems
design are included. Logical design includes ER Diagrams i.e. Entity Relationship Diagrams.
22
Physical design
The physical design relates to the actual input and output processes of the system. This is
laid down in terms of how data is input into a system, how it is verified/authenticated, how
it is processed, and how it is displayed as In Physical design, following requirements about
the system are decided.
1. Input requirement.
2. Output requirements.
3. Storage requirements.
4. Processing Requirements.
System control and backup or recovery. Put another way, the physical portion of systems
design can generally be broken down into three sub-tasks:
1. User Interface Design
2. Data Design
3. Process Design
User Interface Design is concerned with how users add information to the system and with
how the system presents information back to them. Data Design is concerned with how the
data is represented and stored within the system. Finally, Process Design is concerned with
how data moves through the system, and with how and where it is validated, secured
and/or transformed as it flows into, through and out of the system. At the end of the
systems design phase, documentation describing the three sub-tasks is produced and made
available for use in the next phase.
Physical design, in this context, does not refer to the tangible physical design of an
information system. To use an analogy, a personal computer's physical design involves
input via a keyboard, processing within the CPU, and output via a monitor, printer, etc. It
23
would not concern the actual layout of the tangible hardware, which for a PC would be a
monitor, CPU, motherboard, hard drive, modems, video/graphics cards, USB slots, etc. It
involves a detailed design of a user and a product database structure processor and a
control processor. The H/S personal specification is developed for the proposed system.
5.2 INPUT DESIGN
User interface design is very important for any application .The interface design describes
how the software communicates within itself, to system the interpreted with in andwith
humans who use it .The input design process is the process of converting the user –
oriented inputs into thecomputer based format.
Input facilities the entry of data into the computer system. Input design involves the
selection of the best strategy for getting data into the computer system at the right time
and as accurately as possible. Thus is because the most difficult aspect of input designs in
accuracy. The use of well-defined can encourage users to record data accurately without
confusion. In“Anganawadi Management System (AMS)” input is designed in such a way
that users of the system can easily enter the data without errors. Error correction is also
done us inputs such as phone number is validated while entering. The input is designed by
considering the following objectives.
Input Design Objectives
 Develop the efficient input procedure.

 Make it easy to do the right thing and had to the wrong things.
 Reduce input volume.
 Reduce input errors
5.3OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of
processing to uses. They are also used to provide a permanent copy of the results for later
consultation. Intelligent output designs will improve systems relationships with the users
and help much in decision-making. Various reports in proposed software are temporary
and permanent purchase bill, sales bill etc… Various onscreen messages are also displayed
for effective communication with the user. The output design is simple and easy to
24
understand. The significant points that have to be considered for the output design are as
follows.
 Determine what information to be present.

 Decide whether to display, print or voice the information and select the medium of
output.
 Arrange the presentation information in an acceptable format.
 Decide how to describe the output to intended represents.
5.4 DATA BASE DESIGN
A database is a collection of interrelated data stored with minimum redundancy to serve

many users quickly and efficiently. The general objective is to make information access
easy, quick, inexpensive and flexible for the users. The general theme behind a database is
to integrate all information. Database design is recognized as a standard of management
information system and is available virtually for every computer system. In database
design several specific objectives are considered:
 Ease of learning and use
 Controlled redundancy
 Data independence
 More information at low cost
 Accuracy and integrity
 Recovery from failure
 Privacy and security
 Performance
A database is an integrated collection of data and provides centralized access to the data.
Usually the centralized data managing the software is called RDBMS. The main significant
difference between RDBMS and other DBMS is the separation of data as seen by the
program and data has in direct access to stores device. This is the difference between
logical and physical data.
25
Design Consideration
The system is analyzed to the requirements and possible tables and fields are
identified.
Identifying Keys
Once we have drawn up the lists of possible tables and fields, the next step in there
logic database is to identify and foreign keys for each tables
1. Primary Keys
A primary key (pk) consist of a field or set of fields that uniquely identify each record
in that table. The “primary” field defines the primary key.
2. Foreign Keys
A foreign key (fk) comprises a field, or multiple field that to the primary key of
another table. For any database application data is stored in tables. So table designing is a
most important part of backend designing. Steps are taken to avoid unnecessary replication
of data and to achieve maximum data consistency and integrity. The appropriate data type
is chosen for the effective storage and manipulation of information. Another important
matter about table designing is the field width. Each field has enough rooms to
accommodate the data from domain, which has maximum width.
5.5 FORM DESIGN
The process of designing forms involves clarifying the specific needs of your application,
identifying the information you want to work with, and then devising a design that best
meets your needs. This section briefly describes the process.
Goal of form design
The goal of form design is to display and obtain the information you need in an accessible,
efficient manner. The form should encapsulate data so that it may be run without affecting
other forms that use the same data. dbase Plus makes this simple.
It’s important for your design to provide users with the information they need and clearly
tell them what they need to do to successfully complete a task. A well-designed form has
26
visual appeal that motivates users to use your application. In addition, it should use limited
screen space efficiently.
5.6 ARCHITECTURAL DESIGN
Architectural design of a computing system is the structure of the system, which comprises
software element, the externally visible properties of those elements, and the relationship
among them. Architectural design defines the relationship between major structural
elements of the program. Large system can be decomposed into subsystems that provide
some related set of services.
Architectural design is the process of identifying these subsystems and establishing a frame
work for the subsystem controls and communication. The primary objective is to develop a
modular program structure and represent the control relationship between modules. In
addition architectural design modules program structure and data flow through the
program. Architectural design is aimed at trying to refine the conceptual view of the
software product. It permits a system’s quality attributes such as performance or
reliability.
Architectural design is the back born for building successful software intensive system. A
good software structure design results in the development of a project working system. For
the development of the software, modules were identified .This software was developed
into separate named and addressable components that are integrated to satisfy the
problem requirements.
The modular design reduces the complexity, facilitates change and results in easier
implementation by encouraging parallel development of different part of the system. The
procedural design transforms structural elements of program architecture into a
procedural description of software components. The architectural design considers
architecture as the most important functional requirements. The system is based on three -
tier architecture. The first level is the user interface (presentation Logic), which displays
controls, and receives and validates user inputs .All the event handlers in the web form are
in the first level. The second level is the business layer (Business Logic) where the
27
application-specific logic takes place. The third level is the data layer where the application
information is stored in files or database. It contains logic about to retrieve and update
data. The important feature about three –tier design is that information only travels from
one level to an adjacent level.
5.7 SYSTEM MODULES
System Modules (originally known as System Building Blocks; the name was changed
around 1961) are a DEC modular digital logic family which preceded the later FLIP
CHIPs They connect to the units they are plugged into via a set of 22 gold-plated discrete
pins along one edge. They use transistor inverter circuits, with the transistors operating
saturated, to avoid dependence on tight tolerances; they use -3V and 0V as logic levels.
Intended for prototyping as well as production, they include design features intended to
avoid damage. They are provided with design advice which includes loading rules and
wiring instructions. In this system we use 4 modules
1. Administration Module:-In the administration level the admin add the district,
panchayath offices details. The administration can see all the details of anganawadi
2. Panchayath level:-after the admin add the panchayath office the officer can enter the
to site using the username password. Thepanchayath officer is a person who handle the
job vacancies. The officer receive the application from the user and process it.
3. Anganawadi level:-In this level the anganawadi worker add all the details of the
anganawadi like senses details, kids details etc.
4. New applicant:-When the applicant see the job vacancy she can apply for the job.
28
UML
29
5.8 UML
The Unified Modeling Language (UML) is a general-purpose, developmental, modeling

language in the field of software engineering that is intended to provide a standard way to
visualize the design of a system.
The creation of UML was originally motivated by the desire to standardize the disparate
notational systems and approaches to software design. It was developed by Grady
Booch, Ivar Jacobson and James Rumbaugh at Rational Software in 1994–1995, with
further development led by them through 1996.
In 1997 UML was adopted as a standard by the Object Management Group (OMG), and has
been managed by this organization ever since. In 2005 UML was also published by
the International Organization for Standardization (ISO) as an approved ISO
standard. Since then the standard has been periodically revised to cover the latest revision
of UML.
30
UML FOR ADMINISTRATOR
31
UML FOR PANCHAYATH OFFICER
32
UML FOR TEACHER
33
UML FOR APPLICANT
DATA FLOW DIAGRAMS
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system. A data flow diagram can also be used for the visualization of data
processing .It is common practice for a designer to draw a context-level Data flow diagram
first which shows the interaction between the system and outside entities.
The DFD is designed to show how a system is divided into smaller portions and to highlight
the flow of data between those parts. This context-level Data flow diagram is then
"exploded" to show more detail of the system being modeled. Data flow diagrams were
invented by Larry Constantine, the original developer of structured design, based on Martin
and Estrin's "data flow graph" model of computation.
34
A Data Flow Diagram is a network that describes the flow of data and processes that
change, or transform, data throughout the system. This network is constructed by using a
set of symbols that do not imply a physical implementation. It is a graphical tool for
structured analysis of the system requirements. DFD models a system by using external
entities from which data flows to a process, which transforms the data and creates, output-
data-flows which go to other processes or external entities or files. Data in files may also
flow to processes as inputs.
There are various symbols used in a DFD. Bubbles represent the processes. Named arrows
indicate the data flow. External entities are represented by rectangles and are outside the
system such as venders or customers with whom the system interacts. They either supply
or consume data. Entities supplying data are known as sources and those that consume
data are called sinks. Data are stored in a data store by a process in the system. Each
component in a DFD is labeled with a descriptive name. Process names are further
identified with a number.
DFDs can be hierarchically organized, which help in partitioning and analyzing large
systems. As a first step, one Data Flow Diagram can depict an entire system, which gives the
system overview. It is called Context Diagram of level 0 DFD. The Context Diagram can be
further expanded.
Thus successive expansion of a DFD from the Context Diagram to those giving more details
is known as leveling of DFD. Thus a top down approach is used, starting with an overview
and then working out the details.
The Data Flow Diagram shows the logical flow of a system and defines the boundaries of
the system. For a candidate system, it describes the inputs (source), outputs (destination),
database (files) and procedures (data flow), all in a format that meet the user’s
requirements. The main merit of DFD is that it can provide an overview of system
requirements, what data a system would process, what transformations of data are done,
what files are used, and where the results flow.
35
Rules for constructing a Data Flow Diagram
1. Arrows should not cross each other
2. Squares, circles and files must bear names.
3. Decomposed data flow squares and circles can have same name.
4. Choose meaningful names for data flow
5. Draw all data flows around the outside of the diagram
SYMBOLS DESCRIPTION
A data flow is a route, which enables

packets of data to travel from one point to
another. Data may flow from a source to a
process and from data store or process. An
arrow line depicts the flow, with arrow head
pointing in the direction of the flow.
Circles stands for process that converts

datainto Information. Aprocess
representstransformation where incoming
data flows are changed into outgoing data
flows.
Sink enter or receives information from the
system, but is considered to be outside the
contest of data flow model
36
Content of store and does not alter it, the
arrowhead goes only from the store to the
process. If a process alters the details in the
store then a double headed arrow is used.
LEVEL 0 DFD
37
LEVEL 1 DFD FOR ADMIN
38
LEVEL 1 DFD FOR PANCHAYATH OFFICER
39
LEVEL 1 DFD FOR TEACHER
40
LEVEL 1 DFD APPLICANT
41
TABLES
42
1. Table Name: tbl_login
Field Data Type Constraints

Userid Int Primary Key
Uname varchar
Paswrd varchar
2. Table Name: tbl_dis

dist_id int Primary key
dist_name varchar
3. Table Name: tbl_office

panch_id int Primary key
dis_id int Foreign key
ofcr_name varchar
Phon varchar
Email varchar
Uname varchar
Paswd varchar
Cnfrm varchar
security varchar
Ans varchar
4. Table Name: tbl_anganawadi
43
anganawadi_id int Primary key
dist_id int Foreign Key
panch_id int Foreign Key
ward_id int
Email varchar
Phone varchar
username varchar
passwd varchar
cnfmpass varchar
security varchar
Ans varchar
5. Table Name: tbl_notification

not_id int Primary Key
dis_id int Foreign Key
panch-id int Foreign Key
ward_id int
Design varchar
Pdate varchar
Ldate varchar
6. Table Name: tbl_newuser
44
User_id int Primary Key
Fname varchar
Lname varchar
Hname varchar
Dis_id int Foreign Key
Panch_id int Foreign Key
Ward_id int
Phone varchar
Adhar varchar
Dob varchar
Email varchar
Quail varchar
Design varchar
Photo varcha
Docu varchar
Username varchar
Paswd varchar
Cnfrm varchar
Security varchar
Ans varchar
7. Table Name: tbl_addstaff

staff_id int Primary Key
Fname varchar
Lname varchar
ward_id int
Design varchar
Doj varchar
Dol varchar
8. Table Name: tbl_kid
45
kid_id int Primary Key
f_name varchar
l_name varchar
Gender varchar
h_name varchar
dist_id int Foreign Key
Ward int
gu_name varchar
gu_phn varchar
adhar_no varchar
Joinig varchar
passout varchar
9. Table Name: tbl_senses

anganawadi_id int Foreign Key
senses_id int Primary Key
first_name varchar
last_name varchar
house_name varchar
ward_id int
Gender varchar
Dob varchar
qualification varchar
adhar_no varchar
phn_no varchar
category varchar
10. Table Name: tbl_child
46
child_id int Primary Key
first_name varchar Foreign Key
last_name varchar Foreign Key
weight_birth varchar
weight_status varchar
dpt1 varchar
dpt2 varchar
dpt3 varchar
opv1 varchar
opv2 varchar
opv3 varcha
h1 varchar
h2 varchar
h3 varchar
v1 varchar
v2 varchar
v3 varchar
v4 varch
v5 varchar
11. Table Name: tbl_pregnant

p_id int Primary Key
47
first_name int Foreign Key
last_name int Foreign Key
p_hus varchar
p_reg varchar
p_first int
p_second int
p_third int
p_forth int
p_fifth int
p_deliv varchar
p_child varchar
48
SYSTEM TESTING
49
6. SYSTEM TESTING
6.1 INTRODUCTION TOSYSTEM TESTING
No program or system design is perfect; communication between the user and the
designer is not always complete or clear, and time is usually short. The result is errors and
more errors. The number and nature of errors in a new design depend on several factors,
1. Communications between the user and the designer.
2. The programmer’s ability to generate a code that reflects exactly the system
specifications.
3. The time frame for the design.
Software testing is a critical element of software quality assurance and represents the
ultimate reviews of specification, design and coding. Testing presents an interesting
anomaly for the software. Testing is vital to the success of the system. Errors can be
injected at any stage during development. System testing makes a logical assumption that if
all the parts of the system are correct, the goal will be successfully achieved. During testing,
the program to be tested is executed with set of test data and the output of the program for
the test data is evaluated to determine if the program is performing as expected. A series of
testing are performed for the proposed system before the system is ready for user
acceptance testing. System testing is actually a series of different tests whose primary
purpose is to fully exercise the computer-based system. Although each test has a different
purpose, all work to verify that all system elements have been properly integrated and
performed allocated functions. During testing we tried make sure that the product does
exactly what is supposed to do.
Testing is the final verification and validation activity within the organization itself. In the
testing stage, we try to achieve the following goals; to affirm the quality of the product, to
find and eliminate any residual errors from previous stages, to validate the software as a
solution to the original problem, to demonstrate the presence of all specified functionality
in the product, to estimate the operational reliability of the system. During testing the
50
major activities are concentrated on the examination and modification of the source code.
The rules that are serve as well as testing objectives are,
 Testing is a process of executing a program intend with the finding of an error.
 A good test case is one that has a high probability of finding an as yet undiscovered
error.
 A successful test is one that uncovers an as yet undiscovered error.
The test principles are:
 All tests should be traceable to customer requirements
 Tests should be planned long before testing begins.
 Exhaustive testing is not possible.
 To be most effective testing should be conducted by an independent third party.
The basic types of tests are,
 Unit testing
 Integration testing
 Validation testing
 Output testing
 User acceptance testing
Here we are used the following tests
 Programming portion: For optimization the speed of execution, the unwanted

portion of the code are removed
 The structure of each and every web page of the system
The main testing strategies:
6.2 UNIT TESTING
This is the first level of testing. Unit testing focuses verification effort on the smallest unit of
the software design, the module this is known as module testing. Since the proposed
51
system has modules the testing is individually performed on each module. Using the details
description as a guide, important control paths are tested to uncover errors within the
boundary of the modules. This testing was carried out during programming stage itself. In
this testing step each module is found to be working satisfactorily as regards to the
expected output from the module.
6.3 INTEGRATION TESTING
Data can be test across an interface; one module can have adverse effect on another, sub
function when combined may not produce the desired function. Integration testing is a
systematic technique for constructing the program structure while at the same time
conducting test to uncover errors associated within the interface. The objective is to take
unit tested modules and built a program structure that has been dictated by design. All
modules are combined in this testing step. The entire program is tested as whole.
Correction is difficult at this stage because the isolation of causes is complicated by the vast
expense of the program.
6.4 VALIDATION TESTING
At the culmination of integration testing, software is completely assembled as a package.

Interfacing errors have been uncovered corrected and a final series of software validation
testing begins.
Validation testing can be defined in many ways, but a simple definition is that validation
succeeds when the software function in manner that is reasonably expected by the user.
Software validation is achieved through a series of tests that demonstrate conformity with
requirement. After validation test has been conducted, one of two conditions exists.
 The function or performance characteristics confirm to specifications and are

accepted.
 A validation from specifications is uncovered and a deficiency created
Deviation or error discovered at this step in this project is corrected prior to

completion of the project with the help of the user. Thus the proposed system under
52
consideration has been tested by using validation testing and found to be working
satisfactorily
53
SYSTEM IMPLEMENTATION
54
7. SYSTEM IMPLEMENTATION
7.1 INTRODUCTION TO SYSTEM IMPLEMENTATION
As the system is tested, it starts to move into the implementation phase. Ideally the system
should be completed and fully tested implementation gets under way but unless a package
is being installed this seldom happens. Normally what happens is that parts of the system
which are required for file set-up are completed first and this process gets under way.
Conversions program may also have to be available which allow data from another system
to be used in setting up the files. Once this data is set-up, it must keep up-to-date and thus
the first use is made of the new system. This may be followed by a period of parallel
running and then a decision is made to drop the old system.
As soon as the first phase pf implementation, file set-up starts, all system documentation
should be available, viz., user manuals and procedure manuals, computer operating
instructions and security procedures. The system then passes from the development staff
to the computer operations personnel and once the system is alive, strict procedures
should be enforced governing programmers access to programs and files. Procedures
should be established to control all requests for system and program changes, from the
request by the user to the implementation by the programmer.
Installation Procedure
Equipments vendors can provide the specific for equipment installation. They usually work
with the projects equipment installation team in planning for adequate space, power and
light and a suitable environment. After a suitable site has been completed the computer
equipment can be installed. Although equipment is normally installed by the manufacture,
the implementation team should advice and assist.
Implementation Plan
Implementation is the stage in the project where the theoretical design is turned into a
working system and is giving confidence on the new system for the users that it will work
efficiently and effectively. It involves careful planning, investigation of the current system
55
and it’s constraints on implementation, design of methods to achieve the change over an
evaluation, of change over methods.
Implementation is the final and important phase. The most critical stage in achieving a
successful new system and in giving the users confidence that the new system will work
and be effective. The system can be implemented only after thorough testing is done and if
it found to working according to the specification. This method also offers the greatest
security since the old system can take over if the errors are found or inability to handle
certain types of transactions while using the new system.
At the beginning of the development phase a preliminary implementation plan is created to

schedule and manage the many different activities must be integrated into plan. The
implementation plan is updated throughout the development phase, culminating in a
changeover plan for the operation phase. The major elements of implementation plan are
test plan, training plan, equipment installation plan and a conversion plan.
Implementation involves placing the completed and tested system of hardware and
software into the actual work environment of the users. There are both technical and
people-oriented activities during this stage. Examples of technical activities include
converting date files.
There are three types of implementation.
 Implementation of a computer system to replace a manual system.
 Implementation of a new computer system to replace the existing system.
 Implementation of a modified application to replace an existing one, using the same

computer.
7.2 Training
The purpose of the training is to ensure that all the personnel who are to be associated
with the computer based business system possess the necessary knowledge skills.
Operating, programming and user personnel are trained using performance manuals as
training aids.
56
Programmer Training:-Programmers are assigned to the computer-based business
system project at the beginning of the development phase. The programmer’s reference
manual helps an experienced programmer, unfamiliar with the system, about all of the
aspects of the computer program. The manual should enable this person to,
1. Understand existing program components
2. Modify existing program components
3. write new program components
Operator Training:-If new equipment is to be installed operator training is completed in

conjunction with its installation and check-out. If new equipment is not required for the
computer-based system, operators still must become familiar with the operational
requirements of the new system. Different kinds of personnel may be involved in the
operation of the system, such as computer operators, console operators and data entry
operators. Training programs for operations are scheduled to coincide with the needs of
the computer based system as it is developed tested and approaches operational status.
Users, analysts and programmers may participate in the training of operators.
User Training: After the system is implemented successfully, training of the users is the
one of the most important subtasks of the developer. Even well designed and technically
elegant systems can succeed or fail, because of the way they are operated and used. For this
purpose, user manuals are prepared and handled over to the user to operate the developed
system. Both the hardware and software securities are made to run the developed system
successfully in future.
In order to put new application systems in to use, the following activities were taken care
of:
 Preparing of user and system documentation.
 Conducting user training with demo and hands on
 Test run for some period to ensure smooth switching over the system.
57
The users are trained to use the newly developed functions. User manuals
describing the procedures for using the functions listed on menu and circulated to all the
users. It is confirmed that the system is implemented up to users need and expectations.
7.3 Conversion
Conversion is the process of preparing all of the operations that result directly in the
turnover of the new system to the user. Conversion has two parts: The creation of a
conversion plan at the start of the development phase and the implementation of this plan
throughout the development phase.
The creation of a system changeover plan at the end of the development phase and
the implementation of the plan at the beginning of the operation phase.
Conversion activities
A conversion plan is prepare at the start of the development phase. Its principal elements
concern procedures, program and file conversion.
Procedure conversion
Often a new system will incorporate many of the old systems forms and procedures, but
some of these may require modification to fit into the new system. The new system may
interface to the network of other system; too may cause some modification of procedures.
The procedure that requires change must be identified, and the change explained during
training of the personnel.
Program conversion
The new computer based system may include some computer program that is part of
existing system. A conversion problem may arise if new equipments are installed, if the
inputs and outputs of the existing programs change, or if the existing programs are not
efficient in their new environment. Re programming should be considered when programs
are documented, heavily patched, or not efficient enough. For instance, many small
programs might be replaced by a single program that performances a repetitive function
more efficiently.
File conversion
58
File conversion can be thus most time consuming and expensive step in the entire project.
The magnitude of this task is underestimated. Duplicate files must be consolidated and
errors corrected before changeover to the new system start. Otherwise a series of data
errors may plug users of the new system for considerable time after its implementation.
7.4 Post implementation review
After the system is implemented and conversion is complete, a review of system is usually
conducted by users and analyst alike. Not only is this a normal practice, but it should be
formal process to determine how well the system is working, how it has been accepted, and
whether adjustments are needed. The review is also important to gather information for
maintains of the system. Since no system is really ever complete, it will be maintained as
changes are required because of internal developments, such as new users or business
activities, and externals developments, such as new legal requirements, industry standards,
or competition. The post implementation review provides the first source of information
for maintains requirements, Review questions The most fundamental concern during post
implementation review is determining whether the system has met its objective: that is,
analyst want to know if the performance level of users has improved and if the system is
producing the result intended. If neither is happening, one way question whether the
system can be considered successful. The system’s output quality merits special attention.
The concerns raise during analysis and design about the accuracy of information, the
timeliness of presentation, completeness, and the appropriateness of format continue to
indicate systems quality. Reports that are awkward to use or that do not contain sufficient
information to be useful may need redesign. Or the review may reveal that information
previously thought unnecessary must be provided after all. This issue may in turn affect
input requirements. Ease of use and tendency towards errors in input are fundamental
questions for all analysts to address during this review. Is the system easy to use? Are there
adequate safeguards to prevent errors in input and to detect, report, and correct them if
they occur?
If the answered to the questions are not favorable, the reliability and quality of the entire
system may be suspect. User confidence is a generally also an indicator of system quality.
The confidence that user’s, managers, and operators have in the system is sure to affect its
59
longevity and use. Can an analyst realistically expect users who are not confidence of the
system’s reliability to draw on it in reaching critical decisions? It is unlikely. But if
evaluators find that confidence levels are not adequate, they must also determine why. The
questions of an accuracy, completeness timeliness, and usability continue to be central to
the review. Ease of use and benefits of use balance each other. It is generally found that
systems that are easy to use and that provide distinct benefits are accepted and well
received by people. However, even when using a system provides better performance, if
the system itself is awkward to use, it is not common to find that use of the system will be
avoided. Thus, ease of use is as important an attribute as reliability.
In some case, unsuitable systems components may be found during post implementation
review. For example, that a system requires excessive throughput time can be traced to the
amount of time required to print out. Changing printers may eliminate the problem. Data
preparation bottlenecks can be traced to insufficient terminals or data entry stations.
Issue to consider in the evaluation of information systems:
1. How have information systems the cost of operation?
2. How have information systems changed the way in which operations are
performed?
3. How have information systems changed the accuracy of information that users
receive?
4. How have information systems changed the timeliness of information and reports
users receive?
5. How has information systems brought about organization changes? Are these
changes for the better for the worse?
6. How have information systems changed the completeness of the information?
7. How have information systems changed control or centralization? What is the effect
of such changes?
8. How have information systems changed the attitude of systems users or persons
affected by the system?
60
9. How have information systems changed the number of users?
10. How have information systems changed the interactions between members of the
organization?
11. How have information systems changed productivity?
12. How have information systems changed the efforts that must be expended to
receive information for decision making?
Review methods
In general, the data collection methods of questionnaire, interview, observation, sampling,

and record inspection are most useful for collecting details above the new systems. In
addition, supplemental methods will reveal additional information to evaluators. For
example, event logging requires users to record unusual or unexpected events that impact
the system. These events may reflect incidents that system cannot handle because of
incomplete design or activities that are not occurring in the prescribed manner. For
example, when an order entry system is installed, users may find that they are not able to
override the product prices retrieved by the system. The frequency of the incidents reveals
its importance to the organization. However, it may also reveal either that users are
attempting to discount prices to certain customers or that, when quality purchases are
made, there must be made known to analysts evaluating the implemented system. Impact
evaluation determines how systems affect or changed the areas of the organization in
which they are installed. If new systems are proposed and developed on the basis of
increased speed, or improved productivity, systems should be evaluated against these
expectations. Sampling records for errors, assessing the quantity of throughput, or
observing users will provide concrete statistics of the effects of the system.
The impact of the system could also be compared with financial costs and benefits. Even if
greater productivity is achieved with a new system, management will to known whether
the changes produce the intended financial, service, or competitive advantage. During the
system is reviewed to compare the actual costs and benefits with the expectation.
61
How users and other persons do affected by new system, such as customers, suppliers, or
internal mangers, fell about the new system? This simple question reveals much about the
future usefulness of the system. Whether through questionnaires or personnel interviews,
attitude surveys reveal the people side of the system, pertinent questions probe individuals
feeling about the changes in the amount of work they perform, quality of their efforts,
quality of the service to customer or patients, ease of use, or acceptance of the system by
co-workers.
These review methods emphasize the importance of collecting both quantitative

and subjective data to determine the suitability of the system. There is no substitute for
effective review. Introspective and supposition have no place systems development, even
after the system is implemented.
7.5 SYSTEM MAINTENANCE
System maintenance is a set of software engineering activities that occur after software has
been delivered for the customer and put into operation. The success of the software and
project rely on the maintenance procedure performed. Maintenance was done after the
success implementation. Maintenance is continued till the product is reengineered or
deployed to another platform. System maintenance is actually the implementation of post-
implementation review plan. The maintenance can be classified as corrective, adoption or
perfective.
Corrective maintenance means repairing processing or performance failures or making

alternation because of previously ill-defined problems. Adoption maintenance means
changing the program function. Enhancing the performance or modifying the programs
62
according to users additional or changing means are include in perfective maintenance. The
greatest amount of maintenance work is for user enhancement and improved
documentation of the system for better efficiency.
Maintenance covers a wide range of activities including correcting coding and design
errors, updating documentation and test data and upgrading user support.
The keys to reduce the need for maintenance while making it possible to carry on with
essential task more efficiently are as follows:
 More accurately defining user’s requirements during system development.

 Preparation of system documentation in a better way
 Using more effective ways for designing processing logic and communicating it to
project team members.
 Making better use of existing tools and techniques
 Managing the systems engineering process effectively.
63
SYSTEM EVALUATION
64
8. SYSTEM EVALUATION
System evaluation is the process of assessing the performance of a complete system to

discover how it is likely to perform in live market conditions.
There are several steps to evaluation:
 Defining personal trading goals.

 Risk resonance.
 Parameter selection.
 Step testing.
 Calibration and final testing.
All of these steps form part of the trader’s method and are carried out routinely for any
system rules he wishes to review. Systems traders spend a proportion of their trading time
trying to improve their existing systems and looking for new and different ideas. This is
interesting work when you have the essential tools to carry it out.
65
CONCLUSION
66
9. CONCLUSION
The existing system is fully manual that means the record are maintained and keeped
manually by workers. An Anganawadi has mainly two workers. One is the main and
another one is the assistant .The main worker who maintains and controls the major
records of Anganawadi. The main disadvantage of the existing system is that it is very time
consuming process and also very difficult to handle the whole records. When the record
contain any type of failure then we cannot Backup the record .It gives greater workload to
the workers. “ANGANAWADI MANAGEMENT SYSTEM“overcomes tis disadvantages using
ASP.NET and SQL Server.
9.1FUTURE ENHANCEMENT
The application has the capability for easy integrating with other system. New modules can
be added to this system with less effort. Reusability is possible as and when required in this
application. There is flexible in all the modules .We can easily add modules to the system.
Now we are implemented only the registration, senses details, in future we can add stock
details of anganawadies and manage the attendance using face recognition.
67
APPENDIX
68
10.1APPENDIX A
Sample code
<%@PageLanguage="C#"AutoEventWireup="true"CodeFile="adlogin.aspx.cs"Inherits="adl
ogin"%>
<!DOCTYPEhtmlPUBLIC"-//W3C//DTD XHTML 1.0

Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<htmlxmlns="http://www.w3.org/1999/xhtml">
<headrunat="server">
<title></title>
<styletype="text/css">
.style1
{
}
.style2
{
height: 23px;
}
.style3
{
width: 779px;
}
.style4
{
text-align: center;
}
.style6
{
font-size: x-large;
}
.style7
{
height: 26px;
}
.style8
{
width: 779px;
height: 26px;
}
69
.style9
{
text-align: center;
width: 205px;
}
.style10
{
width: 205px;
}
.style11
{
height: 26px;
width: 205px;
}
.style12
{
height: 23px;
width: 205px;
}
.style13
{
height: 27px;
}
.style14
{
height: 27px;
}
.style15
{
width: 779px;
height: 27px;
}
.style16
{
width: 714px;
height: 27px;
}
.style17
{
width: 714px;
}
.style18
{
width: 714px;
height: 26px;
}
70
</style>
</head>
<body>
<formid="form1"runat="server">
<div>
<tablestyle="width: 87%;">
<tr>
<tdclass="style9">
</td>
<tdclass="style4"colspan="2">
<strong><spanclass="style6">LOGIN HERE...</span></strong></td>
<tdclass="style4">
</td>
</tr>
<tr>
<asp:RadioButtonID="rdb_admin"runat="server"Text="ADMIN"/>
<asp:RadioButtonID="rdb_officer"runat="server"Text="OFFICER"/>
<asp:RadioButtonID="rdb_anganawadi"runat="server"Text="ANGANAWADI"/>
<asp:RadioButtonID="rdb_applicant"runat="server"Text="APPLICANT"/>
</td>
</tr>
<tr>
<tdclass="style10">
</td>
<tdclass="style1">
Username</td>
<tdclass="style17">
<asp:TextBoxID="txt_uname"runat="server"></asp:TextBox>
<asp:RequiredFieldValidatorID="RequiredFieldValidator1"runat="server"
ControlToValidate="txt_uname"ErrorMessage="Enter
Username"></asp:RequiredFieldValidator>
</td>
<tdclass="style3">
</td>
</tr>
<tr>
<tdclass="style11">
</td>
<tdclass="style7">
Password</td>
<tdclass="style18">
<asp:TextBoxID="txt_pass"runat="server"style="height: 22px"
TextMode="Password"></asp:TextBox>
<asp:RequiredFieldValidatorID="RequiredFieldValidator2"runat="server"
71
ControlToValidate="txt_pass"ErrorMessage="Enter
Password"></asp:RequiredFieldValidator>
</td>
<tdclass="style8">
</td>
</tr>
<tr>
<tdclass="style10">
</td>
            &nbs
p;            &n
bsp;            &
nbsp;
<asp:ButtonID="btn_login"runat="server"Text="LOGIN"Width="68px"
onclick="btn_login_Click"/>

<asp:ButtonID="btn_cancel"runat="server"Text="CANCEL"/>

</td>
<tdclass="style1">
</td>
</tr>
<tr>
<tdclass="style12">
</td>
<asp:HyperLinkID="HyperLink1"runat="server"ForeColor="#3333CC">Forgot
Password?</asp:HyperLink>
</td>
<tdclass="style2">
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
72
usingSystem.Configuration;
usingSystem.Data;
usingSystem.Data.SqlClient;
publicpartialclassadlogin : System.Web.UI.Page
{
protectedvoidPage_Load(object sender, EventArgs e)
{
}
protectedvoidbtn_login_Click(object sender, EventArgs e)
{
SqlConnection con =
newSqlConnection(ConfigurationManager.ConnectionStrings["str"].ConnectionString);
con.Open();
SqlCommandcmd = newSqlCommand("select * from tbl_login where uname ='" +
txt_uname.Text + "' and paswrd='" + txt_pass.Text + "'",con);
SqlDataAdaptersda = newSqlDataAdapter(cmd);
DataTabledt = newDataTable();
sda.Fill(dt);
if (dt.Rows.Count == 0)
{
Response.Write("<script>alert('Invalid login');</script>");
else
{
Session["userid"] = dt.Rows[0][0].ToString();
Response.Redirect("district.aspx");
}
SqlCommand cmd1 = newSqlCommand("select * from tbl_anganawadi where usrname ='" +
txt_uname.Text + "' and passwd='" + txt_pass.Text + "'", con);
SqlDataAdapter sda1 = newSqlDataAdapter(cmd1);

DataTable dt1 = newDataTable();
sda1.Fill(dt1);
if (dt1.Rows.Count == 0)
{
73
else
{
Session["anganawadi_id"] = dt1.Rows[0][0].ToString();
}
SqlCommand cmd2 = newSqlCommand("select * from tbl_office where uname ='" +
txt_uname.Text + "' and paswd='" + txt_pass.Text + "'", con);

sda2.Fill(dt2);
{
else
{
Session["panch_id"] = dt2.Rows[0][1].ToString();
}
SqlCommand cmd3 = newSqlCommand("select * from tbl_newuser where username ='" +
txt_uname.Text + "' and paswd='" + txt_pass.Text+ "'", con);

sda3.Fill(dt3);
{
else
{
74
Session["user_id"] = dt3.Rows[0][0].ToString();
}
con.Close();
}
}
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="anganawadi.aspx.cs"

Inherits="anganawadi" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
<style type="text/css">
.style1
width: 226px;
.style2
width: 226px;
height: 30px;
.style3
height: 30px;
75
</style>
</head>
<body>
<form id="form1" runat="server">
<div>
<table style="width:100%;">
<tr>
<td class="style1">
District</td>
<td>
<asp:DropDownList ID="ddl_dist" runat="server" DataSourceID="SqlDataSource3"
DataTextField="dist_name" DataValueField="dist_id">
</asp:DropDownList>
<asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server"
ControlToValidate="ddl_dist" ErrorMessage="Select
district"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td class="style1">
Panchayath Name</td>
<td>
<asp:DropDownList ID="ddn_panch" runat="server" DataSourceID="SqlDataSource1"
DataTextField="panch_name" DataValueField="panch_id">
76
</asp:DropDownList>
ControlToValidate="ddn_panch" ErrorMessage="Select
Panchayath"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td class="style1">
Ward Number</td>
<td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td class="style2">
Email</td>
<td class="style3">
<asp:TextBox ID="txt_email" runat="server"></asp:TextBox>
<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"
ControlToValidate="txt_email" ErrorMessage="Enter valid E-mail "
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-
.]\w+)*"></asp:RegularExpressionValidator>
</td>
</tr>
<tr>
77
<td class="style1">
Phone Number</td>
<td>
<asp:TextBox ID="txt_phnoe" runat="server"></asp:TextBox>
</td>
</tr>
<tr>
<td class="style1">
Username</td>
<td>
<asp:TextBox ID="txt_uname" runat="server"></asp:TextBox>
ControlToValidate="txt_uname" ErrorMessage="Enter
Username"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td class="style1">
Password</td>
<td>
<asp:TextBox ID="txt_pass" runat="server"></asp:TextBox>
ControlToValidate="txt_pass" ErrorMessage="Enter
password"></asp:RequiredFieldValidator>
</td>
78
</tr>
<tr>
<td class="style2">
Confirm Password</td>
<td class="style3">
<asp:TextBox ID="txt_confirm" runat="server" TextMode="Password"></asp:TextBox>
<asp:CompareValidator ID="CompareValidator1" runat="server"
ControlToCompare="txt_pass" ControlToValidate="txt_confirm"
ErrorMessage="Wrong password"></asp:CompareValidator>
</td>
</tr>
<tr>
<td class="style1">
Security Question</td>
<td>
<asp:DropDownList ID="ddl_question" runat="server">
<asp:ListItem>--Select--</asp:ListItem>
<asp:ListItem>What is your birth date?</asp:ListItem>
<asp:ListItem>What is your mobile number?</asp:ListItem>
<asp:ListItem>What is your childhood nickname?</asp:ListItem>
<asp:ListItem>What is your pets name?</asp:ListItem>
<asp:ListItem>What is your favorite color?</asp:ListItem>
</asp:DropDownList>
79
ControlToValidate="ddl_question" ErrorMessage="Select security
question"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td class="style1">
Answer</td>
<td>
<asp:TextBox ID="txt_ans" runat="server"></asp:TextBox>
ControlToValidate="txt_ans" ErrorMessage="Enter
answer"></asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td class="style1">
<asp:Button ID="btn_ok" runat="server" Text="OK" onclick="btn_ok_Click" />
</td>
<td>
<asp:Button ID="btn_cancel" runat="server" Text="CANCEL" />
</td>
</tr>
<tr>
<td class="style1">
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
80
ConnectionString="<%$ ConnectionStrings:str %>"
SelectCommand="SELECT * FROM [tbl_office]"></asp:SqlDataSource>
</td>
<td>
</td>
</tr>
</table>
</div>
SelectCommand="SELECT * FROM [tbl_dis]"></asp:SqlDataSource>
DeleteCommand="delete from tbl_anganawadi where anganawadi_id=@anganawadi_id"
SelectCommand="select
w.anganawadi_id,b.dist_name,p.panch_name,w.ward_id,w.email,w.phone from
tbl_disb,tbl_officep,tbl_anganawadi w where p.dis_id=w.dist_id and b.dist_id=p.dis_id and
p.panch_id=w.panch_id"
UpdateCommand="update tbl_anganawadi set

ward_id=@ward_id,email=@email,phone=@phone where
anganawadi_id=@anganawadi_id">
<DeleteParameters>
<asp:Parameter Name="anganawadi_id" />
</DeleteParameters>
<UpdateParameters>
<asp:Parameter Name="ward_id" />
81
<asp:Parameter Name="email" />
<asp:Parameter Name="phone" />
<asp:Parameter Name="anganawadi_id" />
</UpdateParameters>
</asp:SqlDataSource>
<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False"
DataKeyNames="anganawadi_id" DataSourceID="SqlDataSource4">
<Columns>
<asp:BoundFieldDataField="anganawadi_id" HeaderText="anganawadi_id"
InsertVisible="False" ReadOnly="True" SortExpression="anganawadi_id" />
<asp:BoundFieldDataField="dist_name" HeaderText="dist_name" ReadOnly="True"
SortExpression="dist_name" />
<asp:BoundFieldDataField="panch_name" HeaderText="panch_name" ReadOnly="True"
SortExpression="panch_name" />
<asp:BoundFieldDataField="ward_id" HeaderText="ward_id"
SortExpression="ward_id" />
<asp:BoundFieldDataField="email" HeaderText="email" SortExpression="email" />
<asp:BoundFieldDataField="phone" HeaderText="phone" SortExpression="phone" />
<asp:CommandFieldShowDeleteButton="True" />
<asp:CommandFieldShowEditButton="True" />
</Columns>
</asp:GridView>
</form>
</body>
</html>
82
using System;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Data;
public partial class panchayath : System.Web.UI.Page
protected void Page_Load(object sender, EventArgs e)
protected void btn_ok_Click(object sender, EventArgs e)
SqlConnection con = new

SqlConnection(ConfigurationManager.ConnectionStrings["str"].ConnectionString);
con.Open();
string str="insert into tbl_office values(" + ddn_dis.SelectedItem.Value +

",'"+txt_panch.Text+"','"+txt_officer.Text+"','"+txt_phn.Text+"','"+txt_email.Text+"','"+txt_un
ame.Text+"','"+txt_pass.Text+"','"+txt_confirm.Text+"','"+ddl_security.SelectedItem.Text+"','
"+txt_ans.Text+"')";
SqlCommandcmd = new SqlCommand(str, con);
83
cmd.ExecuteNonQuery();
con.Close();
GridView1.DataBind();
protected void SqlDataSource2_Selecting(object sender, SqlDataSourceSelectingEventArgs

e)
Newuser code
using System;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
84
usingSystem.Data;
public partial class newuser : System.Web.UI.Page
protected void Page_Load(object sender, EventArgs e)
protected void btn_sub_Click(object sender, EventArgs e)
SqlConnectioncon=newSqlConnection(ConfigurationManager.ConnectionStrings["str"].Con
nectionString);
con.Open();
string str="insert into tbl_newuser values('" + txt_fname.Text + "','" + txt_lname.Text +

"','" + txt_hname.Text + "'," + ddl_dis.SelectedItem.Value + "," +
ddl_panch.SelectedItem.Value + "," + txt_ward.Text+ ",'" + txt_ph.Text + "','" + txt_adhar.Text
+ "','" + txt_calender.Text + "','" + txt_email.Text + "','" + txt_quali.Text + "','" +
ddl_designation.SelectedItem.Text + "','" + FileUpload1ph.FileName + "','" +
FileUpload2do.FileName + "','" + txt_uname.Text + "','" + txt_pass.Text + "','" +
txt_cnfrm.Text + "','" + ddl_security.SelectedItem.Text + "','" + txt_ans.Text + "')";
SqlCommandcmd = new SqlCommand(str, con);
cmd.ExecuteNonQuery();
con.Close();
GridView1.DataBind();
85
}
protected void btn_can_Click(object sender, EventArgs e)
txt_fname.Text = "";
txt_lname.Text = "";
txt_hname.Text = "";
ddl_dis.SelectedItem.Text = "";
ddl_panch.SelectedItem.Text="";
txt_ward.Text = "";
txt_ph.Text = "";
txt_adhar.Text = "";
txt_calender.Text = "";
txt_email.Text = "";
txt_quali.Text = "";
86
10.2 APPENDIX B
SCREEN SHOTS
1.Login Page
2.District
87
3.Panchayath Office
4.Anaganawadi
88
5. Senses
89
10.3 APPENDIX C
BIBLIOGRAPĤY
1. https://en.wikipedia.org/wiki/ASP.NET
2. https://www.w3schools.com/asp/
3.https://en.wikipedia.org/wiki/Anganwadi
90

INTRODUCTION

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

INTRODUCTION

Uploaded by

Copyright:

Available Formats

INTRODUCTION

1.1 PROJECT PROFILE

Anganawadi Management System (AMS) mainly used to decrease the workload of

The users of the system are

ASP.NET is an open-sourceserver-side web application framework designed for web

ASP.NET's successor is ASP.NET Core. It is a re-implementation of ASP.NET as a

2.2 SCRIPTING LANGUAGE:- C SHARP

C# is a simple, modern, general-purpose, object-oriented programming language

C# is designed for Common Language Infrastructure (CLI), which consists of the

The following reasons make C# a widely used professional language −

 It is a modern, general-purpose programming language

 It produces efficient programs.

 It can be compiled on a variety of computer platforms.

 It is a part of .Net Framework.

SQL Server is software (A Relational Database Management System) developed by

Features of MS SQL Server

 MS SQL Server is implemented from the specification of RDBMS.

3.1 INTRODUCTION TO SYSTEM ANALYSIS

A system is an orderly grouping of interdependent components linked together according

The objectives of the system analysis are:

 Identifying the need.

 Analyzing the existing and proposed system.

 Evaluating the feasibility study.

 Perform economic and technical analysis.

 Identifying the hardware and software requirements.

 Allocating functions to the hardware and software.

 Create a system definition

3.3 LIMITATIONS OF EXISTING SYSTEM

 Difficulty to handle the large information

3.4 FEASIBILITY STUDY

 Form a project team and appoint a project leader

Three key considerations involved in the feasibility study are:

 3.4.1 Economic feasibility

 3.4.2 Technical feasibility

 3.4.3 Behavioral feasibility

3.5 FACT FINDING TECHNIQUES

This method is used to collect the information from groups or individuals. We

3.6 PROPOSED SYSTEM

 High speed and accuracy.

4.1 HARDWARE SPECIFICATION

Processor : Intel core i3

System Bus : 64bits

Memory : 4GB RAM or Higher

Hard Disk : 320GB or Higher

Keyboard : 104 Keys

4.2 SOFTWARE SPECIFICATION

1. Operating System :Microsoft Windows 7

2. IDE : Visual Studio 2010

3. Front End : Asp.Net

4. Back End : SQL Server 2008

 The ASP.NET worker process is a distinct worker process, aspnet_wp.exe, separate

Microsoft SQL Server is a relational database management system developed

Windows 7 is a personal computer operating system that was produced by Microsoft as

Windows 7 was primarily intended to be an incremental upgrade to Microsoft Windows,

5.1 INTRODUCTION TOSYSTEM DESIGN

1. User Interface Design

5.2 INPUT DESIGN

Input Design Objectives

 Develop the efficient input procedure.

 Determine what information to be present.

5.4 DATA BASE DESIGN

A database is a collection of interrelated data stored with minimum redundancy to serve