3) Infant's Serum Tracker-1

INFANT'S SERUM TRACKER
ABSTRACT
Young children are at increased risk for infectious diseases because their
immune systems have not yet built up the necessary defenses to fight serious infections and
diseases. Making sure that children have access to proper healthcare and immunization against
diseases that can be prevented by vaccines, which is a huge challenge that is being faced by
developing countries like ours. This highlights the importance and need of having a better,
smarter system in place, to improve the situations. This application provides a system to
provide information, store records and help parents schedule vaccination appointments for
their children. Our ASP.NET based Infant's Serum Tracker helps parents book vaccination
appointments for their children with just a few clicks and then our web application provide a
separate module for the Newborn baby’s vaccination schedule and record maintenance.
Admin will manage the child and vaccination report and approval of the appointment.
Hospitals will update the status of the vaccination applied for the child.
1
1.INTRODUCTION
1.1 PROJECT DESCRIPTION

As we all know, “Health is a priceless wealth”. This application is
especially for the infant’s, who are the early buds of the nation are to be under cared for their
healthy growth. As the children are not enough to fight against the various infections and
diseases, they are advised to be vaccinated. But now-a -days, people are not aware of the
vaccine schedule, that the infants should be vaccinated as per the correct interval of periods.
In this module, our system enhances the parents to be aware of the
infant’s neediness and importance of vaccination. Also, this system approves only if the proper
registration (proofs are to be attached) is done in this website to proceed further. This
vaccination system has access to newborn babies and to children up to their fifth age. It
provides separate and specific details about the vaccination schedule for different aged
children at different stages, when to vaccine them.
Also, this application provides the information to vaccine the children
by tracking their vaccination schedule and intimates the parents, the time scheduled of
vaccination to their children by notifying them previously by mail. These notifications help to
vaccinate the infants at regular period interval, which ensures a healthy child. Thus, infant’s
serum tracker benefits in making a healthy infants and children.
2. SYSTEM ANALYSIS
2.1.EXISTING SYSTEM
In the existing system, Vaccines are provided for infants and children
under teenage by various aspects such as by attending school manually and there is a chance
that some of the children’s and infants may miss the opportunity of getting vaccinated due to
some mandatory reasons. Which leads to loss of life or gets affected by various diseases such
as polio...etc. This is a time delay process to wait for each and every one all over the places.
2
DISADVANTAGE
 Every system human work with is vulnerable to errors made by a distracted, fatigued,
or incompetent team member.
 Costs Add Up Over Time.
 Searches Take Longer and Are Less Efficient.
 More human power.
2.2.PROPOSED SYSTEM
We can change this manual system into Infant's Serum Tracker by
collecting the info of infants, registered under website so that those who didn’t took vaccination
can avail one more opportunity to save the life of their children. By this system a lot of man-
hours can be saved and it is efficient too. Parents can search and find the hospital and book
online too.
ADVANTAGE
 Easy to maintain the records

 Effective use of time
 Easy to get the Vaccination Details of infant taken
 Easy to get the vaccination camp details.
3
2.3.SYSTEM STUDY
2.3.1.FEASIBILITY ANALYSIS
Feasibility is the study of impact, which happens in the organization by
the development of a system. The impact can be either positive or negative. When the positives
nominate the negatives, then the system is considered feasible. Here the feasibility study can
be performed in two ways such as technical feasibility and Economical Feasibility.
Three key considerations involved in the feasibility analysis are
 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
2.3.2 TECHNICAL FEASIBILITY

Since there will not be much difficulty in getting required resources for
the development and maintaining the system as well. All the resources needed for the
development of the software as well as the maintenance of the same is available in the
organization here we are utilizing the resources which are available already.
2.3.3.ECONOMICAL FEASIBILITY
Development of this application is highly economically feasible. The
organization needed not spend much money for the development of the system already
available. The only thing is to be done is making an environment for the development with an
effective supervision. If we are doing so, we can attain the maximum usability of the
corresponding resources. Even after the development, the organization will not be in condition
to invest more in the organization. Therefore, the system is economically feasible.
4
3.SYSTEM SPECIFICATION
3.1 HARDWARE REQUIREMENTS
 Processor : Intel i7
 RAM : 4 GB
 Hard Disk : 500 GB
 Monitor : LG 23”
 Keyboard : 104 Keys.
 Mouse : 2 buttons
3.2. SOFTWARE REQUIREMENTS
 Operating System : Windows 8, Windows 10, Windows 11

 Front end : HTML, BOOSTRAP, CSS & JAVASCRIPT
 Back end : C# Programming Language, SQL SERVER 2012
 Framework : ASP.NET MVC
3.3.SOFTWARE DESCRIPTION
3.3.1 INTRODUCTION TO DOTNET

Microsoft .NET is a set of Microsoft software technologies for rapidly
building and integrating XML Web services, Microsoft Windows-based applications, and Web
solutions. The .NET Framework is a language-neutral platform for writing programs that can
easily and securely interoperate. There’s no language barrier with .NET: there are numerous
languages available to the developer including Managed C++, C#, Visual Basic and Java Script.
The .NET framework provides the foundation for components to interact seamlessly, whether
locally or remotely on different platforms. It standardizes common data types and
communications protocols so that components created in different languages can easily
interoperate. “.NET” is also the collective name given to various software components built
upon the .NET platform. These will be both products (Visual Studio.NET and Windows.NET
Server, for instance) and services (like Passport, .NET My Services, and so on).
5
3.3.2 ASP.NET MVC FRAMEWORK
The Model-View-Controller (MVC) framework is an architectural
pattern that separates an application into three main logical components Model, View, and
Controller. Hence the abbreviation MVC.
Each architecture component is built to handle specific development
aspect of an application. MVC separates the business logic and presentation layer from each
other. It was traditionally used for desktop graphical user interfaces (GUIs). Nowadays, MVC
architecture has become popular for designing web applications as well as mobile apps.
MVC ARCHITECTURE
6
3.3.3 INTRODUCTION TO SQL
DATABASE
A database management, or DBMS, gives the user access to their data
and helps them transform the data into information. Such database management systems
include dBase, paradox, IMS, SQL Server and SQL Server.
These systems allow users to create, update and extract information from
their database. A database is a structured collection of data. Data refers to the characteristics of
people, things and events. SQL Server stores each data item in its own fields.
In SQL Server, the fields relating to a particular person, thing or event
are bundled together to form a single complete unit of data, called a record (it can also be
referred to as raw or an occurrence). Each record is made up of a number of fields. No two
fields in a record can have the same field name.
SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different
tables are created for the various groups of information. Related tables are grouped together to
form a database.
PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that
uniquely identifies each record in the table. The Unique identifier is called the Primary Key, or
simply the Key. The primary key provides the means to distinguish one record from all other
in a table. It allows the user and the database system to identify, locate and refer to one particular
record in the database.
RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be
stored in one table. SQL Server makes it very easy to link the data in multiple tables. Matching
an employee to the department in which they work is one example. This is what makes SQL
Server a relational database management system, or RDBMS. It stores data in two or more
tables and enables you to define relationships between the table and enables you to define
relationships between the tables.
7
FOREIGN KEY
When a field is one table matches the primary key of another field is
referred to as a foreign key. A foreign key is a field or a group of fields in one table whose
values match those of the primary key of another table.
REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also
maintains consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.
ADVANTAGES OF RDBMS
 Redundancy can be avoided

 Inconsistency can be eliminated
 Data can be Shared
 Standards can be enforced
 Security restrictions ca be applied
 Integrity can be maintained
 Conflicting requirements can be balanced
 Data independence can be achieved
DISADVANTAGES OF DBMS
A significant disadvantage of the DBMS system is cost. In addition to
the cost of purchasing of developing the software, the hardware has to be upgraded to allow for
the extensive programs and the workspace required for their execution and storage. While
centralization reduces duplication, the lack of duplication requires that the database be
adequately backed up so that in case of failure the data can be recovered.
FEATURES OF SQL SERVER(RDBMS)

SQL SERVER is one of the leading database management systems
(DBMS) because it is the only Database that meets the uncompromising requirements of
today’s most demanding information systems. From complex decision support systems (DSS)
8
to the most rigorous online transaction processing (OLTP) application, even application that
require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the
industry in both performance and capability.
SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched
performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially
designed for online transactions processing and for handling large database application.
SQL SERVER with transactions processing option offers two features which contribute
to very high level of transaction processing throughput, which are: The row level lock manager
1.ENTERPRISE-WIDE DATA SHARING

The unrivaled portability and connectivity of the SQL SERVER DBMS
enables all the systems in the organization to be linked into a singular, integrated computing
resource.
2.PORTABILITY
SQL SERVER is fully portable to more than 80 distinct hardware and
operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of
proprietary platforms. This portability gives complete freedom to choose the database server
platform that meets the system requirements.
3.OPEN SYSTEMS
SQL SERVER offers a leading implementation of industry –standard
SQL. SQL Server’s open architecture integrates SQL SERVER and non –SQL SERVER
DBMS with industry’s most comprehensive collection of tools, application, and third-party
software products SQL Server’s Open architecture provides transparent access to data from
another relational database and even non-relational database.
4.DISTRIBUTED DATA SHARING

SQL Server’s networking and distributed database capabilities to access
data stored on remote server with the same ease as if the information was stored on a single
local computer. A single SQL statement can access data at multiple sites. You can store data
where system requirements such as performance, security, or availability dictate.
9
5.UNMATCHED PERFORMANCE
The most advanced architecture in the industry allows the SQL SERVER
DBMS to deliver unmatched performance.
4. SYSTEM DESIGN
4.1 MODULE DESCRIPTION
1. ADMIN PHASE
a. Admin login
b. Dashboard
c. Parent’s details
d. Add child’s details
e. Account approval
f. Schedule vaccination table
g. View vaccination plan
h. Review feed back
i. Add vaccine report details
j. logout
2. PARENT PHASE
a. Login
b. Sign up
c. Dashboard
d. Register children’s details
e. Children’s report
f. Vaccine schedule list
g. Feed back
h. Logout
10
3. ABOUT US
4. CONTACT US
1. ADMIN PHASE
The functionality of admin is controlling the complete website. The
admin phase has many sub modules such as parent details, account approval, schedule
vaccination table, review feedback of the parent. The admin has rights to view the parent details
of the register on this website, then the admin can view the newly registered parent details on
the website and also approve the account after verify the details of the parent. Schedule
vaccination table is sub module where the vaccination date chart is added and update then also
deleted. The admin can view the parent feedback and reply them.
2. PARENT PHASE
The parent phase has many sub modules such as login , user account
Register children’s details, children report, vaccine schedule list, feedback and logout. The
parent has to first create an account through filling their basic details on the user account
creation module. Once the account is created the admin will approve the user after that parent
as to register the children details on the form after that the parent view the vaccination list chart
based on the children age and month wise vaccination details. Then parent can also view the
children report on the their dashboard page and the parent can fill their feedback about the
service through the feedback functionality represent in the parent phase . The parent phase has
a logout functionality to close their session and return to the home page of the website.
3. ABOUT US
The about us module has a functionality used to display the details about
website and vaccination history.
4. CONTACT US
The Contact us module has a functionality to contact the admin through this module
and clarify their doubts.
11
4.2 ARCHITECTURE DESIGN
INFANT'S SERUM TRACKER
ADMIN PARENT
Login Login
Dashboard
Signup
Parent’s details
Dashboard
Add children details
Register children’s
details
Account approval
Children’s report
Schedule vaccination table
View vaccination plan Vaccine schedule

list
Review feed back

Feed back
Add vaccine report details

Logout
Logout
12
4.3 DATA FLOW DIAGRAM
Administrator
parent
Infant’s
serum tracker
Venue of vaccination
Schedule vaccination table
OVERALL DATA FLOW DIAGRAM
13
4.4 DFD 0TH LEVEL
Parent Register
details children details
INFANT’S
ADMIN SERUM PARENT
TRACKER
Add View
children vaccine
schedule
Vaccine schedule plan
14
4.5 USECASE DIAGRAM
LOGOUT Parent’s details

LOGOUT
LOGIN
Account
approval
ADMIN
Schedule
vaccination table Children’s
report PARENT
Feedback
Register
children’s details.
Vaccine
schedule list
Feedback
15
4.6 DATABASE DESIGN
A table is a data structure that organizes information into rows and
columns. It can be used to both store and display data in a structured format. For example,
database store data in table so that information can be quickly accessed from specific rows.
Websites often use table to display multiple rows of data on page. Spreadsheets combine both
purpose of a table by storing and displaying data in structured format.
Databases often contain multiple tables, with each one designed for a
specific purpose. For example, a company database may contain separate table for employees,
clients and suppliers. Each table may include its own set field, based on what data the table
needs to store. In database tables, each field is considered a column, while each entry (or
record), is considered a row. A specific value can be accessed from the table by requesting data
from an individual column and row.
A) PARENT DETAILS
FIELDS DATA CONSTRAINS

TYPE
Id Int Primary Key
Father Name Varchar (25) Not Null
Mother Name Varchar (25) Not Null
Email Varchar (25) Not Null
Password Varchar (25) Not Null
Confirm Password Varchar (25) Not Null
Mobile Big int Not Null
16
B) CHILD DETAILS
FIELDS DATA CONSTRAINS

TYPE
Id Int Primary Key
Father’s name Varchar (25) Not Null
Mother’s name Varchar (25) Not Null
Child Name Varchar (25) Not Null
Age Int Not Null
Gender Varchar Not Null
D.O.B Varchar Not Null
Pre-vaccinated list Varchar (25) Not Null
C) VACCINE SCHEDULE LIST DETAILS
FIELDS DATA TYPE CONSTRAINS

Id Int Primary Key
Age Int Not Null
Gender Varchar (25) Not Null
Parent name Varchar (25) Not Null
Pre-vaccinated list Varchar (25) Not Null
Vaccine schedule list Varchar (25) Not Null
Venue of vaccination Varchar (25) Not Null
17
D) FEEDBACK DETAILS
FIELDS DATA TYPE CONSTRAINS

Id Int Primary Key
Parent Name Varchar (25) Not Null
Vaccinated details Varchar (25) Not Null
Email id Varchar (25) Not Null
Password Varchar Not Null
Mobile Bigint Not Null
Feedback Varchar (max) Not Null
5.SYSTEM TESTING AND IMPLEMENTATION
5.1 TESTING INTRODUCTION

System Testing includes testing of a fully integrated software system.
Generally, a computer system is made with the integration of software (any software is only a
single element of a computer system). The software is developed in units and then interfaced
with other software and hardware to create a complete computer system. In other words, a
computer system consists of a group of software to perform the various tasks, but only software
cannot perform the task; for that software must be interfaced with compatible hardware. System
testing is a series of different type of tests with the purpose to exercise and examine the full
working of an integrated software computer system against requirements.
18
5.2 TESTING METHODS
There are two major type of testing they are
1) White Box Testing.
2) Black Box Testing.
WHITE BOX TESTING

White Box Testing is a testing technique in which software’s internal
structure, design, and coding are tested to verify input-output flow and improve design,
usability, and security. In white box testing, code is visible to testers, so it is also called Clear
box testing, Open box testing, Transparent box testing, Code-based testing, and Glass box
testing.
BLACK BOX TESTING

Black box testing is a technique of software testing which examines the
functionality of software without peering into its internal structure or coding. The primary
source of black box testing is a specification of requirements that is stated by the customer.
5.3 UNIT TESTING

Unit Testing is a type of software testing where individual units or
components of a software are tested. The purpose is to validate that each unit of the software
code performs as expected. Unit Testing is done during the development (coding phase) of an
application by the developers. Unit Tests isolate a section of code and verify its correctness. A
unit may be an individual function, method, procedure, module, or object.
In SDLC, STLC, V Model, Unit testing is first level of testing done
before integration testing. Unit testing is a Whitebox testing technique that is usually performed
by the developer. Though, in a practical world due to time crunch or reluctance of developers
to tests, QA engineers also do unit testing.
.
5.4 INTEGRATION TESTING
Integration testing is the process of testing the interface between two
software units or modules. It focuses on determining the correctness of the interface. The
purpose of integration testing is to expose faults in the interaction between integrated units.
Once all the modules have been unit tested, integration testing is performed.
19
5.5 VALIDATION TESTING
Validation testing is the process of ensuring that the tested and
developed software satisfies the client /user’s needs. The business requirement logic or
scenarios have to be tested in detail. All the critical functionalities of an application must be
tested here.
As a tester, it is always important to know how to verify the business
logic or scenarios that are given to you. One such method that helps in detailed evaluation of
the functionalities is the Validation Process.
USER ACCEPTANCE TESTING

User Acceptance Testing (UAT), or application testing, is the final stage
of any software development or change request lifecycle before go-live. UAT meaning the final
stage of any development process to determine that the software does what it was designed to
do in real-world situations. Actual users test the software to determine if it does what it was
designed to do in real-world situations, validating changes made and assessing adherence to
their organization’s business requirements. The main purpose of acceptance testing is to
validate end-to-end business flow.
5.6 TEST CASES

ACTUAL
INPUT EXPECTED TEST ACTION
NO OUTPUT
GIVEN OUTPUT PASS TAKEN
OCCURED
Admin Admin Home Admin Home
1 YES -
Admin123 Page Page
Muthu Staff Home Staff Home
2 YES -
Muthu123 Page Page
The
Admin, Admin Home Invalid
3 NO password is
145 Page Password
Wrong
20
5.7 SYSTEM IMPLEMENTATION
5.7.1 INTRODUCTION
Implementation is the stage in the project where the theoretical design is
turned into a working system. The implementation phase constructs, installs, and operates the
new system. The most crucial stage in achieving a new successful system is that it will work
efficiently and effectively.
There are several activities involved while implementing a new project. They are
 End user training
 End user Education
 Training on the application software
 System Design
 Parallel Run and To New System
 Post implementation Review
END USER TRAINING

End User Implementation means only those specific portions of End
User Products, developed through the use of a Company Toolkit, that (a) implement and are
compliant with all or part of the required portions of Structured Storage for the sole purpose of
implementing and being compliant with such required portions of the AAF Specification; and
(b) are branded with a trademark owned or controlled by End User.
END USER EDUCATION

End-user education is building awareness among employees by
equipping them with the necessary tools and skills required to protect themselves and the
company data from loss or attack.
21
TRAINING OF APPLICATION SOFTWARE
software development is part of every business not just for software
companies themselves, but for every company which relies on software to deliver on their core
business. Thus, understanding the key tenets of Successful Software Implementation and
Delivery is valuable in any organization.
SYSTEM DESIGN
System design is the phase that bridges the gap between problem
domain and the existing system in a manageable way.
POST IMPLEMENTATION VIEW
PIER is a tool or standard approach for evaluating the outcome of the

project and determine whether the project is producing the expected benefits to the processes,
products or services. It enables the user to verify that the project or system has achieved its
desired outcome within specified time period and planned cost.
6. CONCLUSION AND FUTURE ENHANCEMENT
6.1 CONCLUSION
Infant’s serum tracker for any viable vaccines for infants (up to age of
5) is and state-of-art reliable platform to serve the infants and their ignorant clientele.
In the parent’s phase, until the infant reaches the age of five or even more, due to negligence
or undue influence or coercion these information’s were hidden, by using this application an
awareness of the usage of these vaccines and their availability could be found out. The clientele
parent or caretaker could follow the schedule systematically and achieve his/her task without
hurry or fuss.
In the administrator phase, all the details with regard to details such as
basic information to advanced information viz. place of vaccine if not other venues, etc. are all
collected by the admin and disseminated to the client.Ultimately, the ignorant client would
become enlightened, and the administrator would have peace of mind.
22
6.2. FUTURE ENHANCEMENTS
 In time ahead, we can use this application that the vaccines are inserted to the infants
and children at the place where do they live. Also, we can include that the children at
emergency case can contact the pediatricians and first aid the children through online
mode until the physician reaches the children’s location, also the medicines for them
are brought to home directly by the pharmacist with the consultation of the pediatrician.
 Infant issues and their treatment using naturopathy, Unnani medicines , siddha
medicines to find cure for the infants because the allopathy does not cause complete
cure.
 The app which consist of the things used in home such as pepper, cinnamon , cardamon
, etc. to find simple cure for the infants.
 A separate app to predict the disease through the symptoms therefore prevention is
better than cure.
23
7. APPENDIX
7.1 SAMPLE SOURCE CODE
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using Infant.Models;
using System.Data.Entity;
namespace Infant.Controllers
{
public class DashController : Controller
{
Vaccination con = new Vaccination();
public ActionResult AdminDash()
{
return View();
}
public ActionResult ParentDash()
{
return View();
}
public ActionResult parlist()
{
return View(con.Parents.Where(m => m.status != null).ToList());
}
public ActionResult parlist1()
24
{
return View(con.Parents.Where(m => m.status == null).ToList());
}
public ActionResult svac()
{
return View();
}
[HttpPost]
public ActionResult svac(AddVaccine s)
{
con.AddVaccines.Add(s);
con.SaveChanges();
return RedirectToAction("svac1");
}
public ActionResult svac1()
{
return View(con.AddVaccines.ToList());
}
public ActionResult UserActive(int id)
{
var j = con.Parents.Find(id);
j.status = "Active";
con.SaveChanges();
return RedirectToAction("parlist1");
}
public ActionResult parentprofile()
{
int j = Convert.ToInt32(TempData["Pro"].ToString());
TempData.Keep();
return View(con.Parents.Find(j));
}
[HttpPost]
public ActionResult parentprofile(Parent s)
{
25
int j = Convert.ToInt32(TempData["Pro"].ToString());
s.status = "Active";
con.Entry(s).State = EntityState.Modified;
con.SaveChanges();
return RedirectToAction("parentprofile");
}
public ActionResult ChildrenProfile()
{
string k = TempData["Baby"].ToString();
TempData.Keep();
var d = con.Childrens.Where(m => m.CN.Equals(k)).FirstOrDefault();
return View(d);
}
public ActionResult AddChild()
{
return View();
}
[HttpPost]
public ActionResult AddChild(Children s, HttpPostedFileBase file)
{
string ImageName = System.IO.Path.GetFileName(file.FileName);
string physicalPath = Server.MapPath("~/Pro/" + ImageName);
// save image in folder
file.SaveAs(physicalPath);
//save new record in database
s.Image = ImageName;
con.Childrens.Add(s);
con.SaveChanges();
return RedirectToAction("AddChild");
}
public ActionResult vsl1()
{
26
return View(con.AddVaccines.ToList());
}
public ActionResult AVRD()
{
return View();
}
[HttpPost]
public ActionResult AVRD(vaccinedetail s)
{
con.vaccinedetails.Add(s);
con.SaveChanges();
return RedirectToAction("AdminDash");
}
public ActionResult CVR()
{
string k = TempData["Baby"].ToString();
TempData.Keep();
var d = con.vaccinedetails.Where(m => m.CN.Equals(k)).ToList();
return View(d);
}
}
}
using System;
using System.Linq;
using System.Web;
{
public class HomeController : Controller
{
// GET: Home
public ActionResult Index()
27
{
return View();
}
public ActionResult AboutUs()
{
return View();
}
public ActionResult ContactUs()
{
return View();
}
}
}
using Infant.Models;
using System;
using System.Linq;
using System.Web;
{
public class LoginController : Controller
{
Vaccination con = new Vaccination();
public ActionResult AdminLogin()
{
return View();
}
[HttpPost]
public ActionResult AdminLogin(Login s)
{
if (s.us == "Admin" && s.psd == "Admin123")
{
28
return RedirectToAction("AdminDash", "Dash");
}
else
{
return View();
}
}
public ActionResult ParentLogin()
{
return View();
}
[HttpPost]
public ActionResult ParentLogin(Login s)
{
int c = con.Parents.Where(m => m.us.Equals(s.us) && m.psd.Equals(s.psd) &&
m.status.Equals("Active")).Count();
if (c != 0)
{
TempData["Pro"] = con.Parents.Where(m => m.us.Equals(s.us) &&
m.psd.Equals(s.psd)).Select(m => m.Id).FirstOrDefault();
TempData["Baby"] = con.Parents.Where(m => m.us.Equals(s.us) &&
m.psd.Equals(s.psd)).Select(m => m.CN).FirstOrDefault();
return RedirectToAction("ParentDash", "Dash");
}
else
{
return View();
}
}
public ActionResult AddParent()
{
return View();
29
}
[HttpPost]
public ActionResult AddParent(Parent s)
{
int h = con.Parents.Where(m => m.us == s.us).Count();
if (h == 0)
{
con.Parents.Add(s);
con.SaveChanges();
return RedirectToAction("ParentLogin");
}
else
{
TempData["msg"] = "<script>alert('Already User Exist')</script>";
return View();
}
}
}
}
using System;
using System.Linq;
using System.Web;
using System.Data.Entity;
using System.ComponentModel.DataAnnotations;
namespace Infant.Models
{
public class Child
{
}
public class Login
{
30
[Display(Name = "UserName")]
public string us { get; set; }
[Display(Name = "Password")]
public string psd { get; set; }
}
public class Parent
{
[Key]
public int Id { get; set; }
[Display(Name = "Fathers Name"), Required]

public string FN { get; set; }
[Display(Name = "Mothers Name"), Required]

public string MN { get; set; }
[Display(Name = "Child Name"), Required]

public string CN { get; set; }
[Display(Name = "Gender"), Required]

public string Gender { get; set; }
[Display(Name = "UserName"), Required]

public string us { get; set; }
[Display(Name = "Password"), Required]

public string psd { get; set; }
[Display(Name = "Mobile"), Required]

public Int64 Mob { get; set; }
[Display(Name = "City"), Required]

public string City { get; set; }
31
public string status { get; set; }
}
public class AddVaccine
{
[Key]
public int id { get; set; }
[Required, Display(Name = "Vaccination Schedule Date")]

public string VacDt { get; set; }
[Required, Display(Name = "In Time")]

public string IT { get; set; }
[Required, Display(Name = "Out Time")]

public string OT { get; set; }
[Required, Display(Name = "Location")]

public string Loc { get; set; }
[Required, Display(Name = "Incharge")]

public string Inc { get; set; }
[Required, Display(Name = "Mobile Number")]

public string Mob { get; set; }
[Required, Display(Name = "Baby Age")]

public string BA { get; set; }
}
public class Children
{
[Key]
[Display(Name = "Children Name"), Required]

32
[Display(Name = "Fathers Name"), Required]

public string FN { get; set; }
[Display(Name = "Mothers Name"), Required]

public string MN { get; set; }

[Display(Name = "Age"), Required]

public string Age { get; set; }
public string Image { get; set; }

}
public class vaccinedetail
{
[Key]
[Display(Name = "Vaccination Date")]

public string VD { get; set; }
[Display(Name = "Children Name"), Required]


[Display(Name = "Age"), Required]

public string Age { get; set; }
[Display(Name = "Vaccine Name")]

33
public string VN { get; set; }
}
public class Vaccination : DbContext
{
public DbSet<Parent> Parents { get; set; }
public DbSet<AddVaccine> AddVaccines { get; set; }
public DbSet<Children> Childrens { get; set; }
public DbSet<vaccinedetail> vaccinedetails { get; set; }
}
}
@model Infant.Models.Children
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width" />
<link href="~/Content/bootstrap.min.css" rel="stylesheet" />
<title></title>
<style>
body {
box-sizing: border-box;
margin: 0px;
background: url('../../Image/Bg (1).jpg') no-repeat;
background-size: cover;
font-family: Georgia;
user-select: none;
}
h1 {
}
.w-15 {
width: 200px !important;
34
transition: transform 2s;
}
q{
color: brown;
display: inline-block;
}
.w-15:hover {
transform: translateY(-15px);
}
img {
height: 200px !important;
margin: 5px;
transition: 2s;
}
img:hover {
transform: scale(1.1,1.1);
}
</style>
</head>
<body>
<div class="container rounded bg-dark w-50 text-white bg-opacity-50 p-4 form mt-5">
<h1 class="text-center">Add Childerns Details</h1>
@Html.Raw(@TempData["msg"])
<br />
@using (@Html.BeginForm("AddChild", "Dash", FormMethod.Post, new { enctype =
"multipart/form-data" }))
{
<div class="row">
35
<div class="col-6">
@Html.DisplayNameFor(m => m.FN)
@Html.TextBoxFor(m => m.FN, new { @class = "form-control m-2",
@placeholder = "Fathers Name",@required="required" })
@Html.DisplayNameFor(m => m.MN)

@Html.TextBoxFor(m => m.MN, new { @class = "form-control m-2",
@placeholder = "Mothers Name", @required = "required" })
@Html.DisplayNameFor(m => m.CN)

@Html.TextBoxFor(m => m.CN, new { @class = "form-control m-2",
@placeholder = "Children Name", @required = "required" })
<button class="btn btn-warning m-2 w-100">Add Profile</button>
</div>
<div class="col-6">
@Html.DisplayNameFor(m => m.Gender)

@Html.TextBoxFor(m => m.Gender, new { @class = "form-control m-2",
@placeholder = "Gender", @required = "required" })
@Html.DisplayNameFor(m => m.Age)

@Html.TextBoxFor(m => m.Age, new { @class = "form-control m-2",
@placeholder = "Age", @required = "required" })
@Html.DisplayNameFor(m => m.Image)

<input type="file" name="file" class="form-control m-2" required />
@Html.ActionLink("Back", "AdminDash", "Dash", "", new { @class = "btn btn-
primary m-2 w-100" })
</div>
</div>
}
</div>
<br />
36
<div class="container text-center">
<img src="~/Image/pexels-anna-shvets-3771605.jpg" class="img-thumbnail" />
<img src="~/Image/pexels-hasan-albari-1130172.jpg" class="img-thumbnail" />
<img src="~/Image/pexels-kampus-production-7854086.jpg" class="img-thumbnail" />
</div>
</body>
</html>
<!DOCTYPE html>
<html>
<head>
<title>Admin Dash Board</title>
<style>
body {
margin: 0px;
user-select: none;
}
h1 {
}
.w-15 {
}
q{
color: brown;
37
}
.w-15:hover {
}
img {
margin: 5px;
transition: 2s;
}
img:hover {
}
</style>
</head>
<body>
<div class="text-center">
<h1 class="bg-info bg-opacity-75">
Infant's Serum Tracker
<br />
<br />
<q>Admin Dash Board</q>
</h1>
@Html.ActionLink("Parent Details", "parlist", "dash", "", new { @class = "btn btn-
success m-5 w-15" })
@Html.ActionLink("Add Children Details", "AddChild", "Dash", "", new { @class =
"btn btn-dark m-5 w-15" })
@Html.ActionLink("Account Approval", "parlist1", "dash", "", new { @class = "btn
btn-danger m-5 w-15" })
<br />
38
@Html.ActionLink("Schedule vaccination", "svac", "dash", "", new { @class = "btn btn-
warning m-5 w-15" })
@Html.ActionLink("View vaccination Plan", "svac1", "dash", "", new { @class = "btn
btn-info m-5 w-15" })
@Html.ActionLink("View FeedBack", "#", "#", "", new { @class = "btn btn-dark m-5
w-15" })
<br />
@Html.ActionLink("Add Vaccine Report Details", "AVRD", "Dash", "", new { @class
= "btn btn-dark m-5 w-15" })
@Html.ActionLink("Logout", "AdminLogin", "Login", "", new { @class = "btn btn-
</div>
</body>
</html>
@model Infant.Models.Children
<!DOCTYPE html>
<html>
<head>
<title></title>
<style>
body {
margin: 0px;
user-select: none;
}
39
h1 {
}
.w-15 {
}
q{
color: brown;
}
.w-15:hover {
}
img {
margin: 5px;
transition: 2s;
}
img:hover {
}
</style>
</head>
<body>
<div class="container rounded bg-dark w-50 text-white bg-opacity-50 p-4 form mt-5">
<h1 class="text-center">Profile Childerns Details</h1>
40
<br />
@using (@Html.BeginForm("AddChild", "Dash", FormMethod.Post, new { enctype =
"multipart/form-data" }))
{
<div class="row">
<div class="col-12">
@placeholder = "Children Name", @readonly = "readonly" })

@placeholder = "Gender", @readonly = "readonly" })
@Html.DisplayNameFor(m => m.Age)

@Html.TextBoxFor(m => m.Age, new { @class = "form-control m-2",
@placeholder = "Age", @readonly = "readonly" })
<center>
<img src="~/Pro/@Model.Image" class="img-thumbnail " />
</center>
<br />
@Html.ActionLink("Back", "ParentDash", "Dash", "", new { @class = "btn btn-
</div>
</div>
}
</div>
<br />
41
</div>
</body>
</html>
@model Infant.Models.Parent
<!DOCTYPE html>
<html>
<head>
<title></title>
<style>
body {
margin: 0px;
user-select: none;
}
h1 {
}
.w-15 {
}
q{
color: brown;
}
42
.w-15:hover {
}
img {
margin: 5px;
transition: 2s;
}
img:hover {
}
</style>
</head>
<body>
<div class="container rounded bg-dark w-50 text-white bg-opacity-50 p-4 form">

<h1 class="text-center">Parent Account Profile </h1>
<br />
@using (@Html.BeginForm())
{
@Html.HiddenFor(m=>m.Id)
<div class="row">
<div class="col-6">
@placeholder = "Father Name", @required = "required" })

@placeholder = "Mother Name", @required = "required" })
43
@Html.DisplayNameFor(m => m.us)

@Html.TextBoxFor(m => m.us, new { @class = "form-control m-2",
@placeholder = "User Name", @required = "required" })
</div>
<div class="col-6">
@Html.DisplayNameFor(m => m.psd)
@Html.TextBoxFor(m => m.psd, new { @class = "form-control m-2",
@placeholder = "Password", @required = "required" })

@Html.DisplayNameFor(m => m.Mob)

@Html.TextBoxFor(m => m.Mob, new { @class = "form-control m-2",
@placeholder = "Mobile Number", @required = "required" })
@Html.DisplayNameFor(m => m.City)

@Html.TextBoxFor(m => m.City, new { @class = "form-control m-2",
@placeholder = "City", @required = "required" })
</div>
</div>
<button class="btn btn-warning m-2 w-15">Update Profile</button>

@Html.ActionLink("Back", "ParentDash", "Dash", "", new { @class = "btn btn-
primary m-2 w-25 float-end" })
}
</div>
44
<br />
</div>
</body>
</html>
@model Infant.Models.AddVaccine
<!DOCTYPE html>
<html>
<head>
<title></title>
<style>
body {
margin: 0px;
user-select: none;
}
h1 {
}
.w-15 {
}
45
q{
color: brown;
}
.w-15:hover {
}
img {
margin: 5px;
transition: 2s;
}
img:hover {
}
</style>
</head>
<body>
<br />
<br />
<q>Roll up your sleeve for the vaccine</q>
</h1>
</div>
<h1 class="text-center">Creation Vaccination Chart </h1>
46
<br />
{
<div class="row">
<div class="col-6">
@Html.DisplayNameFor(m => m.VacDt)
@Html.TextBoxFor(m => m.VacDt, new { @class = "form-control m-2", @type
= "date" })
@Html.DisplayNameFor(m => m.IT)

@Html.TextBoxFor(m => m.IT, new { @class = "form-control m-2", @type =
"time" })
@Html.DisplayNameFor(m => m.OT)

@Html.TextBoxFor(m => m.OT, new { @class = "form-control m-2", @type =
"time" })
@Html.DisplayNameFor(m => m.Loc)

@Html.TextBoxFor(m => m.Loc, new { @class = "form-control m-2",
@placeholder = "Location" })
</div>
<div class="col-6">
@Html.DisplayNameFor(m => m.BA)
@Html.TextBoxFor(m => m.BA, new { @class = "form-control m-2",
@placeholder = "Baby Age" })
@Html.DisplayNameFor(m => m.Inc)

@Html.TextBoxFor(m => m.Inc, new { @class = "form-control m-2",
@placeholder = "Incharge Name" })

47
@placeholder = "Mobile Number" })
</div>
</div>
<button class="btn btn-warning m-2 w-15">Create Account</button>

@Html.ActionLink("Back", "AdminDash", "Dash", "", new { @class = "btn btn-
primary m-2 w-25 float-end" })
}
</div>
<br />
</div>
</body>
</html>
<!DOCTYPE html>
<html>
<head>
<title>Index</title>
<style>
body {
margin: 0px;
user-select: none;
48
}
h1 {
}
.w-15 {
}
q{
color: brown;
}
.w-15:hover {
}
img {
margin: 5px;
transition:2s;
}
img:hover {
}
</style>
</head>
<body>
49
<br />
<br />
</h1>
@Html.ActionLink("Admin", "AdminLogin", "Login", "", new { @class = "btn btn-info

m-5 w-15" })
@Html.ActionLink("Parent", "ParentLogin", "Login", "", new { @class = "btn btn-
@Html.ActionLink("About Us", "#", "#", new { @class = "btn btn-danger m-5 w-15" })
@Html.ActionLink("Contact Us", "#", "#", new { @class = "btn btn-warning m-5 w-15"
})
<br/>
<br/>
<img src="~/Image/pexels-nastia-ligrain-14476211.jpg" class="img-thumbnail" />
<img src="~/Image/pexels-pixabay-459957.jpg" class="img-thumbnail" />
<img src="~/Image/pexels-tuấn-kiệt-jr-2338051.jpg" class="img-thumbnail" />
</div>
</body>
</html>
@model Infant.Models.Parent
<!DOCTYPE html>
<html>
<head>
<title>Parent Account Creation </title>
<style>
body {
50
margin: 0px;
user-select: none;
}
h1 {
}
.w-15 {
}
q{
color: brown;
}
.w-15:hover {
}
img {
margin: 5px;
transition: 2s;
}
img:hover {
51
}
</style>
</head>
<body>
<br />
<br />
</h1>

m-5 w-15" })
})
</div>
<h1 class="text-center">Parent Account Creation </h1>
<br />
{
<div class="row">
<div class="col-6">
@placeholder = "Father Name", @required = "required" })

52
@placeholder = "Mother Name", @required = "required" })


@Html.TextBoxFor(m => m.us, new { @class = "form-control m-2",
@placeholder = "User Name", @required = "required" })
</div>
<div class="col-6">
@Html.PasswordFor(m => m.psd, new { @class = "form-control m-2",
@placeholder = "Password", @required = "required" })


@placeholder = "Mobile Number", @required = "required" })
@Html.DisplayNameFor(m => m.City)

@Html.TextBoxFor(m => m.City, new { @class = "form-control m-2",
@placeholder = "City", @required = "required" })
</div>
</div>
<button class="btn btn-warning m-2 w-15">Create Account</button>

@Html.ActionLink("Back To Login", "ParentLogin", "Login", "", new { @class =
"btn btn-primary m-2 w-25 float-end" })
53
}
</div>
<br />
</div>
</body>
</html>
@model Infant.Models.Login
<!DOCTYPE html>
<html>
<head>
<title>Parent Login</title>
<style>
body {
margin: 0px;
user-select: none;
}
h1 {
}
.w-15 {
54
}
q{
color: brown;
}
.w-15:hover {
}
img {
margin: 5px;
transition: 2s;
}
img:hover {
}
</style>
</head>
<body>
<br />
<br />
</h1>

m-5 w-15" })
55
})
</div>
<h1 class="text-center">Parent Login</h1>
<br />
{
@Html.TextBoxFor(m => m.us, new { @class = "form-control m-2", @placeholder =
"User Name", @required = "required" })
@Html.PasswordFor(m => m.psd, new { @class = "form-control m-2", @placeholder
= "Password", @required = "required" })
<button class="btn btn-warning m-2 w-25">Login Account</button>
@Html.ActionLink("Create Account", "AddParent", "Login", "", new { @class = "btn
btn-primary m-2 w-25 float-end" })
}
</div>
<br />
</div>
</body>
</html>
56
7.2 SAMPLE SCREEN SHOTS
57
58
59
60
7. BIBLIOGRAPHY
BOOK REFERENCE
1. http://en.wikipedia.org/wiki/Web Audit_automation_system
2. http://www.koha.org/about-koha/
3. http://www.kohadocs.org/usersguide/ch01.html
4. http://www.kohadocs.org/usersguide/ch01s01.html
WEBSITE REFERENCE
1. https://www.iconfinder.com/
2. www.studytonight.com
3. www.tutlane.com
4. www.jQuery.com
5. https://dotnet.microsoft.com/
6. https://procodeguide.com/
7. https://www.sensibledev.com/
8. https://www.c-sharpcorner.com/
9. https://www.javatpoint.com/
61
62

3) Infant's Serum Tracker-1

Uploaded by

Document Information

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

3) Infant's Serum Tracker-1

Uploaded by

Copyright:

Available Formats

INFANT'S SERUM TRACKER

1.1 PROJECT DESCRIPTION

 Easy to maintain the records

Three key considerations involved in the feasibility analysis are

2.3.2 TECHNICAL FEASIBILITY

3.1 HARDWARE REQUIREMENTS

3.2. SOFTWARE REQUIREMENTS

 Operating System : Windows 8, Windows 10, Windows 11

3.3.1 INTRODUCTION TO DOTNET

SQL SERVER TABLES

 Redundancy can be avoided

FEATURES OF SQL SERVER(RDBMS)

1.ENTERPRISE-WIDE DATA SHARING

4.DISTRIBUTED DATA SHARING

4.1 MODULE DESCRIPTION

INFANT'S SERUM TRACKER

View vaccination plan Vaccine schedule

Review feed back

Add vaccine report details

Schedule vaccination table

OVERALL DATA FLOW DIAGRAM

LOGOUT Parent’s details

FIELDS DATA CONSTRAINS

FIELDS DATA CONSTRAINS

C) VACCINE SCHEDULE LIST DETAILS

FIELDS DATA TYPE CONSTRAINS

FIELDS DATA TYPE CONSTRAINS

5.SYSTEM TESTING AND IMPLEMENTATION

5.1 TESTING INTRODUCTION

WHITE BOX TESTING

BLACK BOX TESTING

5.3 UNIT TESTING

USER ACCEPTANCE TESTING

5.6 TEST CASES

END USER TRAINING

END USER EDUCATION

POST IMPLEMENTATION VIEW

PIER is a tool or standard approach for evaluating the outcome of the

6. CONCLUSION AND FUTURE ENHANCEMENT

7.1 SAMPLE SOURCE CODE

public ActionResult parlist1()

[Display(Name = "Fathers Name"), Required]

[Display(Name = "Mothers Name"), Required]

[Display(Name = "Child Name"), Required]

[Display(Name = "Gender"), Required]

[Display(Name = "UserName"), Required]

[Display(Name = "Password"), Required]

[Display(Name = "Mobile"), Required]

[Display(Name = "City"), Required]

[Required, Display(Name = "Vaccination Schedule Date")]

[Required, Display(Name = "In Time")]

[Required, Display(Name = "Out Time")]

[Required, Display(Name = "Location")]

[Required, Display(Name = "Incharge")]

[Required, Display(Name = "Mobile Number")]

[Required, Display(Name = "Baby Age")]

[Display(Name = "Children Name"), Required]

[Display(Name = "Fathers Name"), Required]

[Display(Name = "Mothers Name"), Required]

[Display(Name = "Gender"), Required]

[Display(Name = "Age"), Required]

public string Image { get; set; }

[Display(Name = "Vaccination Date")]