V - CARE

1. INTRODUCTION
V - CARE

INTRODUCTION

The entitled project “V-CARE” aims to develop a Web application for Caretaker
services. Its prime objective is to provide care services for children, adult & differently-abled
persons. This is a medium sized project for managing caretakers. This project includes the
details of the customers, caretakers, corporates etc. The project is under the administrator &
staff.

The main intention of introducing this system is to reduce the manual work of
agencies. Every sort of task is performed by the system, such as adding & manage caretakers,
adding & manage agencies, managing customer requests, managing caretaker transfer
requests etc. reducing much paper work and burden of file storage. There are a lot of benefits
to the actors by placing the system anywhere. This web application manages all processes of
care services in specified area. Main purpose of the application is to assign caretakers for
customer service requests and provide best method for tracking the caretakers by their
respective agencies. In the form of administration administrator has the overall control of the
application. Application staff have the control over other actors: agencies, caretakers &
customers.
V - CARE

2. SYSTEM STUDY AND ANALYSIS

V - CARE

2.1 SYSTEM STUDY

System study is a brief investigation of the system under consideration and gives a
clear picture of what actually the physical system is? The initial system study involves the
preparation of a System proposal which lists the Problem Definition, Expected benefits of the
new system, etc. in the light of the user requirements. The system proposal is prepared by the
System Analyst (who studies the system) and places it before the user management. The
management may accept the proposal and the can proceed to the next stage. The management
may also reject the proposal or request some modifications in the proposal.

2.1.1 EXISTING SYSTEM

In existing system can have many drawbacks occurred, they are

Problems in existing system:

• It was limited to a single system.
• It was less user-friendly.
• It have lots of manual work (Manual system does not mean that we are working
with pen and paper, it also includes working on spread sheets and other similar
software's).
• It won’t get suitable caretakers.
• It was time consuming process.
• The present system was very less professional.
• It is unable to get different kinds of caretaker.

To avoid all these limitations and make the working more accurately the system
needs to be computerized.

2.1.2 PROPOSED SYSTEM

The aim of proposed system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the existing system. The
system provides proper security and reduces the manual work. The proposed system
helps the user to work user friendly and he can easily do his jobs without time lagging.
V - CARE

Advantages

 Fast access to database

 Less error
 More Storage Capacity
 Provides Search facility

 Details of any caretakers, customers, and agencies can be founded within a short span
of time.
 The proposed system includes tracking and transfer of caretaker within a short period.
 The system allows the customers to view the details very easily.

2.2 FEASIBILITY STUDY:

Feasibility study is the study carried out about the project before starting of the
project to check whether the development of this particular project is useful in every aspect.
There is no use in developing a project which is of no use to anyone. Hence different types
of feasibility study must be carried out before beginning any project. An aspect the
developer has to keep in mind during the development is that all the functionalities that
exist in the present has to be there in the new system, and also has to overcome the demerits
existing one has. A feasibility study on this project was carried out and it was found to be
feasible in every respect.

This project is feasible and cost effective because it requires a smaller number of
man-hours and the resources needed are very less. The different types of feasibility studies
that were carried out are:

1. Economic Feasibility
2. Performance Feasibility
3. Operational Feasibility
4. Technical Feasibility
V - CARE

2.2.1 Economic Feasibility:

Analysis of a project's costs and revenues in an effort to determine whether or not
it is logical and possible to complete. In this following, issues are considered.
 Is the cost conduct a full system investigation feasible?
 Is the cost of hardware and software for the class application being considered?
The Economic aspect of the project reveals the following:
 The cost of the project is very less compared to other application projects.
 The total man-hours required to develop is hundred hours
 Single developer can undergo this project.

2.2.2 Performance Feasibility:

It is mainly related to human organizational and political aspects. The points to be

considered are
 What changes will be brought with the system?
 What organizational structures are disturbed?

Generally, project will not be rejected simply because of operational infeasibility but
such considerations are likely to critically affect the nature and scope of the eventual
recommendations. This feasibility study is carried out by a small group of people who are
familiar with information system techniques, who understand the parts of the business that
are relevant to the project and are skilled in system analysis and design process.

The Performance of the system should be high because:

 The system should function in the network environment; the packet should not be
lost.
 Each command transferred should reach the destination
 The speed of the process should be high.

2.2.3 Operational Feasibility:

V - CARE

Proposed project would be beneficial only if it can be turned into information system
that will meet the organization's operational requirements. One of the main problems faced
during development of new system is getting acceptance from user. Even if a system is
technically and economically feasible but the user of the system are resistant to use it then
there is no use. In this stage the following issues are considered.

 Is the proposed system user-friendly?

 Is there sufficient support for the project from the management and users?
 Will the proposed system cause harm?
 Will it produce poorer result in any area?
 Will loss of control result in any area?

2.2.4 Technical Feasibility:

Technical feasibility focuses on the possibility of doing the project with current
equipment, existing software technology and available personnel recourses. The technical
needs were taken into consideration to see if the project is feasible with the current resources
available. In this stage the following issues are considered.

 Does the required technology exist to do what is suggested?

 Does the proposed equipment have the technical capacity to hold the data?
 Will the proposed system provide adequate response to inquire?
 Can the system be expanded if needed?

The Technical Feasibility issue raised during the feasibility stage of investigation of this
project includes:
 The existence of the necessary technology to do what is suggested.
 Adequate technical capacity to hold the data required for the system.
 Guaranteed technical reliability, accuracy, eases of access and data security.
V - CARE

2.3 SYSTEM ANALYSIS

System Analysis is a process of collecting factual data, understand the processes
involved, identifying problems and recommending feasible suggestions for improving the
system functioning. This involves studying the business processes, gathering operational
data, understand the information flow, finding out bottlenecks and evolving solutions for
overcoming the weaknesses of the system so as to achieve the organizational goals. System
Analysis also includes subdividing of complex process involving the entire system,
identification of data store and manual processes.
The major objectives of systems analysis are to find answers for each business
process: What is being done? How is it being done? Who is doing it? When is he doing it?
Why is it being done? and how can it be improved? It is more of a thinking process and
involves the creative skills of the System Analyst. It attempts to give birth to a new efficient
system that satisfies the current needs of the user and has scope for future growth within the
organizational constraints. The result of this process is a logical system design. Systems
analysis is an iterative process that continues until a preferred and acceptable solution
emerges.

2.3.1 Method for Analysis

System Analysis is the first and foremost step in the development of a project. It can
be defined as the process of gathering information and facts, diagnosing problems. It also
includes understanding of the existing system. System analysis specifies what the system
should do. In spite of the relevance of technology, the human efforts will play an important
role in the organizational work. The interaction with the end user leads to the identification
of all the problems of the present system. Once the drawbacks, shortcomings and problems
of the existing system are known, the next step ‘System Design’ is easy.

The various fact-finding techniques that were part of the system analysis are:

 Observation
 Document reference
 Discussion
V - CARE

Observation:
An observation was made through working of existing system to know how the data are
processed and caretaker was assigned.

Document Reference: For preparation of information of caretakers, the details are hard
coded in the file. Currently the updating of the information and the addition of new
caretakers are done manually and the data is updated in the file.

Discussions:
To understand the system better, discussions were held with the caretakers, agencies and
also with the end users. This leads to the better design of the system.
V - CARE

3. SYSTEM SPECIFICATION
V - CARE
V - CARE

3.1 SYSTEM ENVIRONMENT

Here shows the target environment (hardware and software) for which the software is being
developed.

HARDWARE REQUIREMENTS:
 PROCESSOR: INTEL 3 CORE
 RAM: 128mb RAM
 HDD: 20 GB Hard Disk Space and Above
 KEYBOARD: STANDARD 102 KEYS
 MOUSE: 3 BUTTONS

SOFTWARE REQUIREMENTS:
 OPERATING SYSTEM: Windows 10
 ENVIRONMENT: Visual Studio .NET 2019
 .NET FRAMEWORK: Version 3.5
 LANGUAGE: C# ASP.NET
 BACKEND: SQL SERVER 2020

3.2 TECHNOLOGY USED:

.NET technology

The technology followed here is Microsoft’s .Net technology. An integral

component of the Microsoft Windows Operating System , the Microsoft .Net framework is
for building and running the next generation of applications and XML based Web Services.
The .Net Framework represents a unified, object oriented set of services and libraries that
embrace the hanging role of new network centric and network aware software. The .Net
Framework is the first platform designed from the ground up with the Internet in mind. It
provides a highly productive, standards based, enterprise ready, Multilanguage environment
that simplifies application development, enables developers to take advantage of their
existing skill set, facilitates integration with existing software, and eases the challenges of
deploying and operating Internet Scale applications.
V - CARE

Benefits of .Net Framework

A consistent programming model.
O The .Net Framework has a consistent programming model.
Direct support for security.
O The .Net Framework enables both developers and system administrators to specify
method level security.
Simplified development efforts.
O The efforts for development of applications are simplified in .Net technology.
Easy application deployment and maintenance.
The .Net Framework makes it possible to install applications that use some or all
of the components (Web pages, Windows form based components, Web services,
Components based in DLLs), without having to register DLLs or to create Registration
Database entries. The .Net Framework makes it easy to deploy applications using zero impact
installation. This is possible because the .Net framework handles the details of locating and
loading components of an application needs.

Elements of the .Net Framework

The .Net Framework consists of two key elements:
 Common Language Runtime
The CLR is an object-oriented platform for windows and web developers that
all the languages share. The CLR simplifies an application’s design and reduces the amount
of code developers need to write because it provides a variety of execution services that
include memory management, thread management, component life time management, and
default error handling. The benefit of CLR is that it transparently provides these execution
services to all applications, regardless of what programming language they are written in. It is
also responsible for compiling code just before it executes.
 . Net Class Library
The .Net class library contains hundreds of classes that model the system and
services it provides. The benefits of using .Net Class library includes a consistent set of
services available to all .Net languages and simplify deployment, because the .Net Class
library is available on all implementations of the .Net Framework.
V - CARE

FRONT END:
 Over view of software
In the project Software project monitoring system .NET Framework is used
as front-end tool. .NET is one of the most beautiful and recently more popular front-end
tools. C#.NET and ASP.NET are used in this project. An interface for users is build-using
ASP.NET. SQL Server 2020 is used as the back-end tool. Additional technologies used are
Internet Information Services (IIS) and ADO.NET. Then it comes the turn of the Operating
System. Any .NET framework compatible software platform can be used.

Introduction To .Net

C#.NET is the next generation of the Visual Basic language from Microsoft.
With C# you can build .NET applications quickly and easily. Applications made with C# are
built on the services of the common language runtime and take advantage of the .NET
Framework.
C# has many new and improved features such as inheritance, interfaces, and
overloading that make it a powerful object-oriented programming language. Other new
language features include free threading and structured exception handling. C# fully
integrates the .NET Framework and the common language runtime, which together provide
language interoperability, garbage collection, enhanced security, and improved versioning
support. C# supports single inheritance and create Microsoft intermediate language (MSIL)
as input to native code compilers.

C# is comparatively easy to learn and use, and has become the programming
language of choice for thousands of developers over the past decade. An understanding of C#
can be leveraged in a variety of ways, such as writing macros in Visual Studio and providing
programmability in applications such as Microsoft Excel, Access and Word.

C#.NET, the next generation of the C# language, is a fast and easy way to create .NET based
applications.
V - CARE

BACK END

 SQL Server 2008:

Microsoft SQL Server is a relational model database server produced by
Microsoft. Its primary query languages are T-SQL and ANSI SQL. Microsoft SQL Server
2008 is a full-featured relational database management system (RDBMS) that offers a variety
of administrative tools to ease the burdens of database development, maintenance and
administration. In this article, we'll cover five of the more frequently used tools: Enterprise
Manager, Query Analyzer, SQL Profiler, Service Manager and Data Transformation
Services. Let's take a brief look at each:

 Enterprise Manager
Enterprise Manager is the main administrative console for SQL Server installations.
It provides you with a graphical "birds-eye" view of all of the SQL Server installations on
your network. You can perform high-level administrative functions that affect one or more
servers, schedule common maintenance tasks or create and modify the structure of individual
databases.

 Query Analyzer
Query analyzer offers a quick and dirty method for performing queries against any
of your SQL Server databases. It's a great way to quickly pull information out of a database
in response to a user request, test queries before implementing them in other applications,
create/ modify stored procedures and execute administrative tasks.

 SQL Profiler
SQL profiler provides a window into the inner workings of your database. You
can monitor many different event types and observe database performance in real time. SQL
Profiler allows you to capture and replay system "traces" that log various activities. It's a
great tool for optimizing databases with performance issues or troubleshooting particular
problems.
V - CARE

 Service Manager
Service manager is used to control the MSSQL Server (the main SQL Server
process), MSDTC (Microsoft Distributed Transaction Coordinator) and SQL Server Agent
processes. An icon for this service normally resides in the system tray of machines running
SQL Server. You can use Service Manager to start, stop or pause any one of these services.

 Data Transformation Services (DTS)

DTS provide an extremely flexible method for importing and exporting data
between a Microsoft SQL Server installation and a large variety of other formats. The most
commonly used DTS application is the "Import and Export Data" wizard found in the SQL
Server program group.

SQL server 2008 Advantages

 Transparent Data Encryption: The ability to encrypt an entire database.
 Backup Encryption: Executed at backup time to prevent tampering.
 External Key Management: Storing Keys separate from the data.
 Auditing: Monitoring of data access
 Data Compression: Fact Table size reduction and improved performance.
 Resource Governor: Restrict users or groups from consuming high levels or resources.
 Hot Plug CPU: Add CPUs on the fly.
 Performance Studio: Collection of performance monitoring tools.
 Installation improvements: Disk images and service pack uninstall options.
 Dynamic Development: New ADO and Visual Studio options as well as Dot Net 3.
 Entity Data Services: Line Of Business (LOB) framework and Entity Query Language
(eSQL)
 LINQ: Development query language for access multiple types of data such as SQL and
XML.
 Data Synchronizing: Development of frequently disconnected applications.
V - CARE

 Large UDT: No size restriction on UDT.

 Dates and Times: New data types; Date, Time, Date Time Offset.
 File Stream: New data type VarBinary(Max) File Stream for managing binary data.
 Table Value Parameters: The ability to pass an entire table to a stored procedure.
 Spatial Data: Data type for storing Latitude, Longitude, and GPS entries.
 Full Text Search: Native Indexes, thesaurus as metadata, and backup ability.
 SQL Server Integration Service: Improved multiprocessor support and faster lookups.
 MERGE: TSQL command combining Insert, Update, and Delete.
 SQL Server Analysis Server: Stack improvements, faster block computations.
 SQL Server Reporting Server: Improved memory management and better rendering.
 Microsoft Office 2007. Use OFFICE as an SSRS template. SSRS to WORD.
 SQL 2000 Support Ends. Mainstream Support for SQL 2000 is coming to an end.
V - CARE

4.SYSTEM DESIGN
V - CARE

4.1 SYSTEM DESIGN

Designing is the most important phase of software development. It requires a

careful planning and thinking on the part of the system designer. Designing software means
to plan how the various parts of the software are going to achieve the desired goal. It should
be done with utmost care because if the phase contains any error then that will affect the
performance of the system, as a result it may take more processing time, more response time,
extra coding workload etc. Software design sits at the technical kernel of the software
engineering process and is applied regardless of the software process model that is used.
After the software requirements have been analyzed and specified, software design is the first
of the three technical activities Designing, Coding and Testing that are required to build and
verify the software. Each activity transforms information in such a manner that ultimately
results in validated computer software.

 Design goals
The following goals were kept in mind while designing the system:
 Make system user-friendly: This was necessary so that system could be used
efficiently and system could act as catalyst in achieving objectives.
 Make system compatible: It should fit in the total integrated system. Future
maintenance and enhancement must be less.
 Make the system reliable: understandable and cost-effective

4.2 NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the
following modules
 Administrator
 Staff
V - CARE

 Agency
 Caretaker
 Customer
 Transfer
 Customer Application

MODULE DESCRIPTION

The system after careful analysis has been identified to be presented with the
following modules:

1. Administration:

Administrator has an authentication to monitoring the complete system. This module

deals with operations that are applicable to administrator. It includes
 Add/view/edit/delete staff
 Add/view/edit/delete agency
 Add country
 Add state
 Add district
 Add area

2. Staff:

Staff is a person who manages customer and caretaker. It includes

 View/edit/delete caretaker
 View/edit/delete customer

3. Agency:

Agency is an actor that works under the . That are

 View caretaker
 Approve caretaker
V - CARE

 Manage caretaker category

 View/edit/delete customer applications
 Assign caretaker for customer applications
 View/edit/delete transfer
 Manage transfer
 Edit/delete transfer status

4. Caretaker

Caretaker is a person who works under the agency that has includes
 View/select agency
 View/Accept customer application
 Edit/delete application status
 Apply transfer
 View transfer status

5. Customer:

Customer is the module which choose the caretaker.

 View/select caretaker
 Add/edit application
 View application status

6. Transfer:

This module is used to generate transfer requests.

 Prepare transfer request
 Caretaker details can be recorded
 View/select agency

7. Applications:

This module is used to generate customer applications

 Prepare customer applications
 Customer details can be recorded
 Caretaker details can be recorded
V - CARE

4.3 LOGICAL DESIGN

DATA FLOW DIAGRAMS

A data flow diagram is a graphical representation that depicts information flow and
transforms that are applied as data move from input to output. A data flow diagram may be
used to represent a system or software at any level of abstraction. DFDs can be partitioned
into levels that represent increasing information flow and functions details.
A level 0 DFD, also called a fundamental system model or a context model,
represents the entire software element as a single bubble with input and output data indicated

by incoming and outgoing arrows, respectively. Each of the process represented at level 1 is
a sub function of the overall system depicted in the context model.
In the normal convention, logical DFD can be completed using only four notations

Represents source or destination of data

Represents data flow

Represents a process that transforms

Incoming data into outgoing flow.

Represents the data store

The DFD at the simplest level is referred to as the ‘CONTEXT ANALYSIS

DIAGRAM’. These are expanded by level, each explaining its process in detail. Processes are
numbered for easy identification and normally labeled in block letters. Each data flow is
labeled for easy understanding.
V - CARE

DFD LEVEL 0:

DFD LEVEL 1:
V - CARE

DFD LEVEL 1.1 ADMIN PROCESS:

DFD LEVEL 1.2 STAFF PROCESS:

V - CARE

DFD LEVEL 1.3 AGENCY PROCESS:

DFD LEVEL 1.4 CUSTOMER PROCESS:

V - CARE

DFD LEVEL 1.5 CARETAKER PROCESS:

 V - CARE

4.4 INTERFACE DESIGN

The interface design describes how the software communicates within itself with
system that operates with it and with users who use it. The user interface is the link between
user and the capabilities of our software. A well-designed user interface makes it very easy for
the audience to learn software. Through frequent consultation and reviews by the client we
could develop a template for the interface, based on which other interfaces were constructed,
as needed for specific requirements of the system. User Interface design is the design of the
computer appliances and software applications with the focus of the user’s experience and
interaction. The User Interface shall make the object or application physically active. The goal
of the physical Interface is to make the user’s Interaction as intuitive as possible. Graphical
User Interface or GUI make it easier for the people with little computer skills to work with and
use of computer software. It is visual front to a piece of software that links to the internal
workings of a computer, or a piece of software. The user interface design process encompasses
four distinct framework activities

1. User, Task, and Environment Analysis and Modeling

2. Interface Design
3. Interface Construction
4. Interface Validation
V - CARE

4.5 PHYSICAL DESIGN

Physical modeling involves the actual design of a database according to the

Requirements that were established during logical modeling

4.5.1InputDesign

The input design is the process of converting the user-oriented inputs in to the
computer based format. The goal of designing input data is to make the automation as easand
as possible. For providing a good input design for the application easy data input and
selection features are adopted.

The input design requirements such as user friendliness, consistent format and
Interactive Dialogue for giving the right message and help for the user at right time are also
considered for the development of the project.

Input facilitates 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. This is because the most difficult aspect of input design in
accuracy .The use of well-defined documents can encourage users to record data accurately
without omission.

Input design must capture all the data that the system needs, without introducing any
errors. Input errors can be greatly reduced when inputting directly by using appropriate forms
for data capture and well designed computer screen layout.

4.5.2 Output Design

Output are the most important and direct source of information to the user and to the
management. Computer system is required to users or for some other system. .

In any system, the results were communicated to the users and to other systems through
output. Even the best design input is of no use if the inputs do not meet the user‘s requirements.
V - CARE

The design of the system is usually processed from output to input. The screen itself should be
simple and helpful with meaningful prompts. So efforts at taken to make output screen as much
user-friendly as possible.

4.6 DATABASE 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 key
easy, quick, inexpensive and flexible for the user. Database is designed, built and populated
with the data for the specific purpose. It has an intended group of users and some preconceived
applications on which the users are interested.

In database environment, common data are available in which several users can use. The
concept behind a database is an integrate collection of data and provides a centralized access to
the data from the program. It makes possible to treat data as a separate resources.

Data types and its description:

Fields in database table have a data type used in database table are explained below.

1. Integer: One optional sign character (+or-) followed by at least one digit (0-
9).Leading and trailing blanks are ignored . No other character is allowed.
2. Varchar: It is used to store alpha alpha numeric characters.In this data type we can
set the maximum number of characters upto 8000 ranges by defaults SQL server will
set the size to 50 characters range.
3. Date time: Date time data types is used for representing date or time.
V - CARE

4.6 TABLE DESIGN

1. LOGIN TABLE

Field Datatype Description

User id Int Primary key
Username Varchar(20) For storing user name for
login
Password Varchar(20) For storing password for
login
Status Int For storing status of user

Type Int For storing type of user

2. CUSTOMER REGISTRATION TABLE

Field Datatype Description

Custid Int Primary key

Firstname Varchar(20) For storing First name for

registration
Lastname Varchar(20) For storing Last name for
registration
Mobno Varchar(10) For storing Mobile no. for
registration
Email Varchar(20) For storing Email for registration

Username Varchar(20) For storing Username for

registration
V - CARE

Password Varchar(20) For storing Password for

registration

3. CARETAKER REGISTRATION TABLE

Field Datatype Description

Careid Int Primary key

Fullname Varchar(20) For storing Full name for

registration
Mobno Varchar(10) For storing Mobile no. for
registration
Email Varchar(20) For storing Email for
registration
Username Varchar(20) For storing Username for
registration
Password Varchar(20) For storing Password for
registration

4. AGENCY REGISTRATION TABLE

Field Datatype Description

Agencyid Int Primary key

Agencyname Varchar(20) For storing Agency name for

registration
Cntno Varchar(10) For storing Contact no. for
registration
Email Varchar(20) For storing Email for
registration
Username Varchar(20) For storing Username for
V - CARE

registration
Password Varchar(20) For storing Password for
registration

5. CUSTOMER APPLICATION TABLE

Field Datatype Description

Appid int Primary key

Agencyid int Foreign key

Careid int Foreign key

Cid Int Country id , Foreign key
Sid Int State id , Foreign key

Did Int District id , Foreign key

Aid Int Area id , Foreign key

6. TRANSFER REQUEST TABLE

Field Datatype Description

TRid int Primary key

Careid int Foreign key

CurAgenid int Agencyid, Foreign key

ReqAgenid int Agencyid, Foreign key
Cid Int Country id , Foreign key
Sid Int State id , Foreign key
V - CARE

Did Int District id , Foreign key

Aid Int Area id , Foreign key

FrmDate Datetime For storing from date

ToDate Datetime For storing to date

7. CARETAKER JOIN APPLICATION TABLE

Field Datatype Description

CTAppid int Primary key

Agencid int Agencyid, Foreign key

Cid int Countryid, Foreign key

Sid int Stateid, Foreign key

Did int Districtid, Foreign key

Aid int Areaid, Foreign key

8. CARETAKER CATEGORY MANAGE TABLE

Field Datatype Description

Careid int Caretakerid, Foreign key

Categoryid int Caretaker categoryid,

foreign key

9. TRANSFER MANAGE TABLE

V - CARE

Field Datatype Description

TRmanid int Primary key

TRid int Transfer requestid, foreign

key
TrStatid int Transfer statusid, foreign
key

10. CUSTOMER APPLICATION MANAGE TABLE

Field Datatype Description

Appmanid Int Primary key

Appid Int Customer Applicationid,
foreign key
AppStatid Int Application statusid, foreign
key

11. TRANSFER STATUS TABLE

Field Datatype Description

TrStatid Int Primary key

Statusname Varchar(20) For storing status name

12. APPLICATION STATUS TABLE

Field Datatype Description

AppStatid Int Primary key

Statusname Varchar(20) For storing status name

V - CARE

13. COUNTRY TABLE

Field Datatype Description

Countryid Int Primary key

Countryname Varchar(20) For storing country name

14. STATE TABLE

Field Datatype Description

Stateid Int Primary key

Countryid Int Foreign key

Statename Varchar(20) For storing state name

15. DISTRICT TABLE

Field Datatype Description

Districtid Int Primary key

Countryid Int Foreign key

Stateid Int Foreign key

Districtname Varchar(20) For storing district name

16. AREA TABLE

Field Datatype Description

V - CARE

Areaid Int Primary key

Countryid Int Foreign key

Stateid Int Foreign key

Districtid Int Foreign key

Areaname Varchar(20) For storing Area name

17.CUSTOMER PROFILE

Field Datatype Description

CustProid Int Primary key

Custid Int Foreign key

Firstname Varchar(20) For storing First name for

profile
Lastname Varchar(20) For storing Last name for
profile
Dob Datetime For storing date of birth for
profile
Gender Varchar(20) For storing gender for
profile
Cid Int Country id , Foreign key

Sid Int State id , Foreign key

Did Int District id , Foreign key

Aid Int Area id , Foreign key

StreetAddr Varchar(20) For storing street address for

profile

18. CARETAKER PROFILE

Field Datatype Description

CareProid Int Primary key
V - CARE

Careid Int Foreign key

Firstname Varchar(20) For storing First name for

profile
Lastname Varchar(20) For storing Last name for
profile
Fathername Varchar(20) For storing Father’s name
for profile
Mothername Varchar(20) For storing Mother’s name
for profile
Dob Datetime For storing date of birth for
profile
Gender Varchar(20) For storing gender for
profile
Cid Int Country id , Foreign key

Sid Int State id , Foreign key

Did Int District id , Foreign key

Aid Int Area id , Foreign key

StreetAddr Varchar(20) For storing street address for

profile
Photo Varchar(20) For storing photo for profile

19. AGENCY PROFILE

Field Datatype Description

AgencyProid Int Primary key

Agencyid Int Foreign key

YearEst Datetime For storing year established

for profile
Cid Int Country id , Foreign key

Sid Int State id , Foreign key

Did Int District id , Foreign key

Aid Int Area id , Foreign key

StreetAddr Varchar(20) For storing street address for

profile
Logo Varchar(20) For storing logo for profile

LicNo Varchar(20) For storing license no. for

V - CARE

profile

20. AGENCY CATEGORY MANAGE

Field Datatype Description

Agencyid int Agency id, Foreign key

AgenCategoryid int Agency categoryid, foreign

key

5. SYSTEM DEVELOPMENT


V - CARE

5.1 CODING STRUCTURE

System development is a series of operations performed to manipulate data to

produce output from a computer system. This is highly dependent on the programming
language used. The principle activities performed during the development phase can be
divided into two major related sequences.

They are:

1) External system development

2) Internal system development

The major external system development activities are:

 Planning
 Equipment Acquisition
 Installation
 Implementation

The major internal system development activities are:

 Coding Structure
 Computer program development
 Performance testing

Coding translates a detailed representation of software into programming language

realization. For this project C# is used for coding. Code design has been implemented giving
priority to understandability, simplicity and clarity. Coding style has been chosen in such a
way that it provide execution speed and minimum memory requirement.
V - CARE

Programming language used for coding has greater influence over the final output.
This project is coded using C#.NET . It is a high level programming language with the
following important characteristics:

5.2 SYSTEM SECURITY MEASURES

Various measures of security are laid down by the system. This provides
facility for validating the identification code and password to make the system as reliable
and interactive as possible, necessary validation have been provided in filling input data for
any operation to be performed a user has to fill certain mandatory fields. If user leaves out
any of them, a warning is provided in the form of dialogue boxes to ensure proper and
correct input.
V - CARE

6.SYSTEM TESTING AND

IMPLEMENTATION
V - CARE

6.1 SYSTEM 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 perform allocated
functions.

Testing is the final verification and validation activity within the organization itself.
Testing is done 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 major
activities are concentrated on the examination and modification of the source code.

TESTING METHODOLOGIES ADOPTED:

 Unit Testing

 Integration Testing

 Validation Testing

 Output Testing

6.1.1 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of Software design that is
the module. Unit testing exercises specific paths in a module’s control structure to ensure
complete coverage and maximum error detection. This test focuses on each module
individually, ensuring that it functions properly as a unit. Hence, the naming is Unit Testing.
V - CARE

6.1.2 INTEGRATION TESTING

Integration testing addresses the issues associated with the dual problems of
verification and program construction. After the software has been integrated a set of high
order tests are

conducted. The main objective in this testing process is to take unit tested modules and builds
a program structure that has been dictated by design.

The following are the types of Integration Testing:

1. Top-down Integration

This method is an incremental approach to the construction of program structure.

Modules are integrated by moving downward through the control hierarchy, beginning with
the main program module. The module subordinates to the main program module are
incorporated into the structure in either a depth first or breathe first manner.

2. Bottom-up Integration

This method begins the construction and testing with the modules at the lowest level
in the program structure. Since the modules are integrated from the bottom up, processing
required for modules subordinate to a given level is always available and the need for stubs is
eliminated. The bottom-up integration strategy may be implemented with the following steps:

 The low-level modules are combined into clusters that perform a specific Software sub-
function

 A driver (i.e.) the control program for testing is written to coordinate test case input and
output

 The cluster is tested

 Drivers are removed and clusters are combined moving upward in the program structure

6.1.3 VALIDATION TESTING:

In validation testing the requirements established as part of the requirement analysis

are validated against the software that has been constructed. Validation testing provides
V - CARE

final assurance that software meets all functional, behavioral, and performance
requirements. Black-box testing techniques are used exclusively during validation

6.1.4 OUTPUT TESTING

After performing the validation testing, the next step is output testing of the proposed
system, since no system could be useful if it does not produce the required output in the
specified format. The outputs generated or displayed by the system under consideration are
tested by asking the users about the format required by them. Hence the output format is
considered in 2 ways – one is on screen and another in printed format.

6.2 SYSTEM IMPLEMENTATION

Implementation is the stage of the project where the theoretical design is turned into
a working system. At this stage the main work load, the greatest upheaval and the major
impact on the existing system shifts to the user department. If the implementation is not
carefully planned and controlled, it can cause chaos and confusion.

Implementation includes all those activities that take place to convert from the old
system to the new one. The new system may be totally new, replacing an existing manual or
automated system or it may be a major modification to an existing system. Proper
implementation is essential to provide a reliable system to meet the organization
requirements. Successful implementation may not guarantee improvement in the
organization using the new system, but improper installation will prevent it.

The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old
system to the new system. The system can be implemented only after thorough testing is
done and if it is found to be working according to the specifications. The system personnel
check the feasibility of the system.

The most crucial stage is achieving a new successful system and giving confidence on
the new system for the user that it will work efficiently and effectively. It involves careful
planning, investigation of the current system and its constraints on implementation, design of
methods to achieve the changeover. The more complex the system being implemented, the
more involved will be the system analysis and the design effort required just for
V - CARE

implementation. The system implementation has three main aspects. They are education and
training, system testing and changeover.

The implementation stage involves following tasks.

 Careful planning.

 Investigation of system and constraints.

 Design of methods to achieve the changeover.

 Training of the staff in the changeover phase.

 Evaluation of the changeover method.

FUTURE ENHANCEMENT
V - CARE

FUTURE ENHANCEMENT

Every application has its own merits and demerits. The project has covered almost
all the requirements. Further requirements and improvements can easily be done since the
coding is mainly structured or modular in nature. Changing the existing module or adding
new module can append improvements.

1. Updates based on client requirements.

2. Increment in caretaker Category.

These modules are kept as future enhancement for implementation

New modules can be added to the existing system with less effort. The software can
be given a new looking and new features can be added thereby improving the efficiency
of the entire system.
V - CARE

CONCLUSION
V - CARE

CONCLUSION

This project “V-CARE” has been completed successfully and marks the
expectation of those who have guided us through this project. The constraints are met and
overcame successfully. The system is designed as like it was decided in the design phase.
The software was developed in a .NET platform with Visual Studio 2019.It is expected to
live up to the objective for which it was designed. In the proposed system it is sure that it
must reduce the workload and time duration.
In primary stage of the system that the caretaker management on manual method
which is a time taking process and there are chances of lose data.
The developed system is flexible and modification is easy whenever necessary.
Only authorized persons can run the system. The system automatically saves time and man
power and lot of money. This phase gives me a good idea on developing full-fledged
software satisfying the user requirements. With the successful completion of this project, I
believe that it would be of great help to my career. This system has been tested with real data
and the results are found to be satisfactory.
V - CARE

BIBLIOGRAPHY
V - CARE

BIBLIOGRAPHY

 FOR DEPLOYMENT
http://www.codeproject.com/Articles/14249/populate-DataGridView-GridView
http://stackoverflow.com/questions/6907223
http://msdn.microsoft.com/en-us/library/aa287920%28v=vs.71%29.aspx
http://www.c-sharpcorner.com/CrystalReports/CrystalReportsIntroduction.aspx
http://csharp.net-informations.com

 FOR SQL

http://www.w3schools.com/sql/sql_join.asp
http://en.wikipedia.org/wiki/Join_%28SQL%29#Sample_tables
http://msdn.microsoft.com/en-us/library/ms203721%28v=sql.90%29.aspx
 Software Engineering (Roger‟s Pressman)
V - CARE

APPENDIX
V - CARE

LOGIN FORM

ADMIN FORM
V - CARE

CHIEF ACCOUNTANT FORM

ACCOUNTANT FORM
V - CARE

OFFICE STAFF FORM

V - CARE

STAFF DETAILS FORM

STAFF VIEW FORM

V - CARE

DEPARTMENT FORM

DEPARTMENT VIEW FORM

V - CARE

COURSE FORM

SEMESTER FORM
V - CARE

BATCH FORM
V - CARE

STUDENT FORM
V - CARE

STUDENT REPORT

FEES FORM
V - CARE

FEE PAYMENT FORMS

FEE PAYMENT VIEW & REPORT

V - CARE

FEE RECEIPT

SALARY FORM
V - CARE

SALARY VIEW

SALARY PAYMENT
V - CARE

LETTER FORM
V - CARE

LETTER VIEW

LETTER PRINT

EXPENCE HEAD
V - CARE

EXPENCE FORM
V - CARE

ACCOUNT VIEW FORM

V - CARE