Project Online Domestic Helper

Chapter-1
PROBLEM DEFINITION
1.1 Brief Description of the Organisation:- Gitarattan International Business School

(giBS) was established in the year 2004. giBS is affiliated to Guru Gobind Singh
Indraprastha University, Delhi and is approved by All India Council for Technical
Education (AICTE), Ministry of HRD, and Government of India. It is accredited
by National Assessment & Accreditation Council (NAAC) and is ISO 9001: 2008
certified. The institute is assessed as Category 'A' by Joint Assessment Committee
of Goverment of Delhi and Guru Gobind Singh Indraprastha University. The
Institute conducts postgraduate courses of MBA (First & Second Shift), MBA-
International Business, MCA and MCA(Dual degree)
1.2 General Description of the System under Study:- The existing system of Online
Domestic Service Provider is a well-functioning unit which help in providing the
domestic assistant such as cleaner, cook, baby sitter, elder care etc.
Its provide database of helpers form where the seeker can chose an select the
desired and required helper as per their need.
1.3 User Requirement:- Information System Project generates because of various

reason such as greater speed, better accuracy, improved consistency, faster
information retrieval, reduced cost and better security.
1.31 In the existing online domestic assistance provider system is an automated

system. But at some point it is found to be inefficient as per increasing demands as
follows-
a. It is really a time consuming process.

b. No proper feedback is provided to the seeker.
c. Verification of helper not done properly.
d. Duplication of data.
e. Increased spam mails.
1
1.4 Establish the need of the new system:- Existing system being a properly working
portal is not being able to meet certain areas of requirement as per the increasing
demand. The new system provides with new well advanced features for facilitating
and providing an ease in browsimg the desired results. Some new and advanced
facilities provided by new system are as follows.
a. Easy GUI interface easy for user to excess it.

b. Increased filter for seeking helper.
c. Proper police verification of the helpers provided.
d. Adhar card number for proper identification of helper.
e. Spam reporting.
f. No duplication of data.
1.5 Objectives of the Project:- The objective of Online Domestic Assistant Provider
System is to provide a system to the user which provides records of the housemaid,
cook, babysitter and elder care .The customer will get to know the required detailed
information about the helper available as per their need.
The system will maintain all the records of the customer ( like email id, phone no
etc.), details of the helpers (like address, verified documents, phone no etc.),purpose
of hiring helper, salary, hours of work etc. A database is required to save the records
and accordingly different types of reports will be generated from this software.
The system is easy to use and any normal user can understand the system by looking
through it also it provides quick and easy comparison of different helpers for the
customers/seekers.
1.6 Methodology:- In this project Classic SDLC methodology was used. The system
development life cycle (SDLC) or software development process is a process of
creating or altering information system, and the models and methodologies that
people use to develop these system. It aims to produce a high quality system that
meets or exceeds customer expectations, reaches completions within time and cost
estimates. Justification of using SDLC (software Development Lifecycle Model) in
this project:
2
a) Simple goal
b) Simple to understand and use
c) Clearly define stages
d) Well understood milestones
e) Easy to arrange tasks
f) Process and results are well documented
g) Easy to manage
h) Each phase has deliverable and a review
i) Work well for projects where requirements are well understood
j) Works well when quality is more important than schedule
k) Customers/End users already know about it
1.61 The stage it involves can be characterized and divided up in different ways,
including the following:
1.62 Requirement Analysis:- Requirement gathering and analysis is the first stage of
any SDLC model. This phase is basically the brainstorming phase and often consists
of sub-stages like Feasibility Analysis to check how much of the idea can be put into
action. If any particular software needs to be modified, the underlying problem of that
software is sorted out along with finding ways to solve it. If brand new software is
going to be developed, then every minute requirement regarding that software is
looked in to. This implies that this stage involves maximum research and inputs from
both the company that is developing the software and the client.
1.63 System and Software Design:-This is the second phase of SDLC where the entire
system is defined in detail. In fact, it this stage wherein a detailed blueprint of various
processes of the software is developed. If needed the system is divided into smaller
parts to make it easier more manageable for the developers, designers, testers, project
managers and other professionals who are going to work on the software. System
Design helps in specifying hardware and system requirements and also helps in
defining overall system architecture. The system design specifications serve as input
for the next phase of the model.
3
1.64 Implementation and testing:- On receiving system design documents, the work
is divided in modules/units and actual coding is started. The system is first
developed in small programs called units, which are integrated in the next phase.
Each unit is developed and tested for its functionality; this is referred to unit testing.
Unit testing mainly verifies if the module/units meet their specifications.
1.65 Integration and System testing:- As specified above, the system is first divided
into units which are developed and tested for their functions. These units are
integrated into a complete system during integration phase and tested to check if all
modules/units coordinate with each other and the system as a whole behaves as per
the specifications. After successfully testing software, it is delivered to the customer.
1.66 Operations and Maintenance:- This phase of the model is virtually a never
ending phase. Generally, problems with the system developed (which are not found
during the development lifecycle) come up after its practical use starts, so die issues
related to the system are solved after deployment of the system. Not all the problems
come into picture directly but they arise from time to time and need to be solved,
hence this process is referred to as maintenance.
1.7 Data required & Data Collection Method:- Data collection is the process
of gathering and measuring information on targeted variables in an established
systematic fashion, which then enables one to answer relevant questions and evaluate
outcomes. The data has been collected by gathering information by interviewing
experienced people, document analysis and internet. For developing information
system data is required in respect of input, output, storage and processing
requirements. There are two types of sources of data:
a) Primary Data: The data is collected through questionnaire, search and research
through places and people who have mostly used or worked upon system like this.
Also data is been collected from internet.
b) Secondary Data: The data is collected through magazines, newspapers, journals

and websites.
4
1.8 Project Planning:-Project planning is a discipline for stating how to complete a
project within a certain timeframe, usually with defined stages, and with designated
resources. At the beginning of the project, proper timeline is being set for the design
and implementation of the software and what language to be used in writing the
software. After thorough follow up we then develop a time-line for the project when
would be the first version for software will be releasing and the estimated time that
would be used for refactoring. Same follows up for the other versions of the software
and their estimating time. Deciding the project title is also done here only.
1.81 Gantt chart

Gantt chart is a type of a bar chart that is used for illustrating project schedules. Gantt
charts can be used in any projects that involve effort, resources, milestones and
deliveries. At present, Gantt charts have become the popular choice of project
managers in every field. Gantt charts allow project managers to track the progress of
the entire project. Through Gantt charts, the project manager can keep a track of the
individual tasks as well as of the overall project progression. In addition to tracking
the progression of the tasks, Gantt charts can also be used for tracking the utilization
of the resources in the project.
Figure no-1.1: Gantt chart
5
Chapter-2
SYSTEM REQUIREMENT SPECIFICATION
2.1 Introduction -Requirement analysis is usually the first phase of large-scale

software development project. Online Domestic Assistance Provider System is better
in faster searching, processing time and get more accurate data for user requests (i.e.
for finding domestic helper online). This system is designed in such a way that seeker
will get the most desired result of their query for helper according to their need, time
and budget as per the process of the system
2.2 Process Identification-Based on the requirement gathered we divide the system

into three modules and these are :
2.21 Administrator Module

a) Login: The Administrator enters the site through this module. This module
provided with to view, update, delete and add helper details in this system.
b) Add New Helper: The administrator enters the details of new helper. Each helper is
provided with a unique id (beside adhar card no.) checked and verified. If it was
correct then admin is able to login else rejected.
c) Helper details : The Administrator view and update any specific details of helper
and the administrator can enters the particular valid helper id to view the details of
the desired helper. Also can view all helpers which are registered
d) Seeker details: The Administrator can view all details of seekers who all have
registered for the helper query. By entering the particular valid seeker id the
Administrator can view the details of seeker.
2.22 Seekers module:

a) Login: The seekers enters the site through this module if you’re an existing user.
b) Signup: The seeker can signup. The information includes name, email-id, phone
number, location/city. The seeker is checked and verified. If it was correct then seeker
is able to signup otherwise rejected.
6
c) Requirement input: The seeker here enter the details according to their need of
helper. It includes type of helper needed by the seeker, time slot, gender, area, salary
budget, pin code of your area.
d) View helper: The seeker can view the helper according to their needs as mentioned
by them. Best filtered result according to needs of seeker like timeslot ,salary, type of
assistance needed, gender, age etc. will be provided, based on location/city in which
area they wants the helper.
2.3 Identify the inputs to and outputs of each Process-For all above module we
identify the processes which constitutes of requirement, input, processing and output.

a) R1: Login
Input: Login ID, Password.
Process: click on the login link. If administrator enters ID and password correct it
goes to the admin services otherwise displays the same page with an error massage.
Output: Displays the admin services page.
b) R2: Add/Update New Helper:
Input: Name, Id, Adhar card No, Phone number, Gender, Age, Specialization, Area of
work, experience.
Process: A new helper can be added or updated into the system by admin only and can
be updated by admin only.
Output: The Helper will be added in the system.
c) R3: View Helper details.
Input: Adhar card no. , name
Process: The admin can view the details of already existing helper’s record.
Output: Helper details will be viewed from the database .
d) R4: Seeker details:
Input: Name, email id
Process: Administrator can view a particular seeker detail. This can be done only if
the seeker details are already present in the database.
Output: seeker details will be displayed on the screen.
7
2.32 Seeker Module
a)R1:Login
Input: ID, Password.
Process: click on the login link. If seeker enters ID and password correct it goes to
other page otherwise displays the same page with an error massage.
Output: Displays the information to be viewed by the seeker.
b) R2: Sign up
Input: Name, email id, Password, Address, City, pincode
Process: It will create a login id for the new seeker on the website. It will be carried to
another page is the details are being verified, else error will be displayed.
Output: Displays the information viewed by the seeker
d) R3: Requirement form
Input: Type of helper, salary, timeslot , gender, age, area (pin-code),
Process: The Seeker can add information what is required by the him/her for getting
the required helper.
Output: The seeker will get the list of helpers as per their requirement.
2.4) Identify the data elements(fields) in each Input & Output.
2.41) Administrator module

2.411) Login
a) Login ID
b) Password
2.412) Add/Update new Helper
a) Name,
b) Adhar card No
c) Phone number
d)Gender
e) Age
f) Specialization
g) Area
2.413) View seeker
a) Email Id
8
b) Name
2.414) View Helper
a) Adhar No.
b) Name
2.42) Seeker Module

2.421) Login
a) Email Id
b) Password
2.422) Sign Up
a) Name
b) Email id
c) Password
d) Phone no.
e) Area
2.423) Requirement Form
a) Specification
b) Timeslot
d) Gender
e) Area
f) Comment
2.5 Identify the Procedures/Rules/Mathematical Relationships used for converting

Input into output.
a) Login: To use the system, the admin has to login into the system. An email is asked
to the existing admin to access all the admin rights of the given application.
b) Add/Update New Helper: The new helper can be added to this system only by the
admin by entering the: Name, Id, Adhar card No, Phone number, Gender, Age,
Specialization, Area of work, experience etc. If anyone wants to login and see the
avail helpers, they have to register.
c) Helper Details: The admin panel can view and update the details of each Helper by
maintaining the their information like Id, Name etc.
9
d) Seeker Details: The admin panel can view the details of each seeker by maintaining
the information like Id name etc and responding to their query.
2.52 Seeker Module
a) Login: To use the system, the seeker has to login into the system. An email is asked
from the already existing seeker for further accessing the application.
b) Sign Up: If the seeker is first time visitor on your application the he/she must sign
up by giving details such as name, email, password, address, city etc for further
accessing the application.
c) Requirement Form: The seeker after successful login/signup now fill the
requirement form as per their need of the helper. This include Timeslot, for what
purpose helper is required, area etc.
2.6 Identity the controls (for I/O & Access).Security Need, validation Rules and Code
used for Data Element
The Controls used in the development of the input/output interface and data accessing
interface for Online Domestic Assistance Provider System are:
Labels Controls used Buttons

Admin Login
Login Email Textbox Login in
Password Password
Add New Helper
Name, Textbox Submit
Adhar card No Textbox Cancel
Phone number Textbox
Gender Radio Button
Age Dropdown list
Specialization Dropdown list
Area TextBox
Seeker Login
Email Textbox Search
Password Textbox
Seeker Signup
Name, Textbox Submit
email id Textbox Cancel
Password, Textbox
Phone no. Textbox
Area Drop Down List
10
Requirement Form
Specification Drop Down List Submit
Timeslot Drop Down List Cancel
Gender Radio Button
Area Textbox
Comment TextBox
View seeker
email id Textbox Save
Password Textbox View
Edit/Update
Submit
Table no-2.1 Control Used In Online Domestic Assistance Provider
2.61 Security Requirement and Validation Rules

2.611 Security requirements
a) When any user attempting into the system by using id and password the
system first check for validation of id and password , if valid then allow
further processing otherwise display a warning message.
b) Every user(admin or seeker) can use the services according to the privileges.
2.62 Validation Rules:- JavaScript provides the following validation Rules:

a) Required Field Validator: The Required Field Validator control ensures that the
required field is not empty. It is generally tied to a text box to force input into the text
box. For eg- if Area is left undone by seeker then it will be difficult to allocate the
helper for him/her near them. So validation is put there.
b) Range Validator: The Range Validator control verifies that the input value falls
within a predetermined range
Properties Description
Type Define types of the data like date,
double, integer, string
Minimum It specifies minimum of the range
Maximum It specifies maximum of the range
Table no-2.2 Range Validator
11
c) Compare Validator: The Compare Validator control compares a value in one
control with a fixed value or a value in another control. It has the following
specific properties:
d)
Properties Description
Type Define types of the data like
date,double,integer,string
Control to It specifies the value of the input
Compare control to compare with
Value to It specifies the constant value.
Compare
Table no-2.3 Compare Validator
12
Chapter-3
SYSTEM DESIGN
3.1 System Design:-The design document that we will develop during this phase is the
blueprint of the software. It describes how the solution to the customer problem is to
be built. This is true for software design as well. The design strategy, design method,
or design language must be flexible and must easily accommodate changes due to
iterations in the design.The design should be traceable to the analysis model because a
single element of the design model often traces to multiple requirements, it is
necessary to have a means for ttracking how requirements have been satisfied by the
design model. Systems are constructed using a set of design patterns, many of which
have likely been encountered before. These patterns should always be chosen as an
alternative to reinvention.Systems design is the process or art of defining the
architecture, components, modules, interfaces, and data for a system to satisfy
specified requirements. There is some overlap with the disciplines of systems
analysis, systems architecture and systems engineering.Object-oriented analysis and
design (OOAD) methods are becoming the most widely used methods for computer
system design. The UML has become the standard language used in Object-oriented
analysis and design. It is widely used for modeling software systems and is
increasingly used for high designing non-software systems and organizations. The
design for this project work has been divided into following major parts which are:
a) External Design
b) Logical Design
c) Physical Design
3.2 Levels of Design
3.21 External Design:- External design consists of conceiving, planning out and
specifying the externally observable characteristics of the software product. These
characteristics include user displays or user interface forms and the report formats,
external data sources and the functional characteristics, performance requirements etc.
External design begins during the analysis phase and continues into the design phase.
13
3.22 Logic Design:- The logical design of a system pertains to an abstract
representation inputs and outputs of the system. This is often conducted via modeling,
which involves asimplistic (and sometimes graphical) representation of an actual
system. In the context ofsystem design, modeling can undertake the following forms,
including:
a) Data Flow Diagrams

b) Entity Relationship Diagrams
3.23Physical Design:-The physical design relates to the actual input and output
processer. 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 output. 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 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.
3.3 Data Flow Diagram (DFD) (Physical Design) :- The dataflow diagram is used for
classifying system requirement to major transformation. That will become programs
in system design.This is the starting point of the design phase That functionally
decomposes the required specification down to the lower level of Details. Data can
trigger events and can be processed to useful information. System Analysis recognizes
the central goal of data in organisaton.
3.31 Notation used in data flow diagram :- The logic data flow diagram can be drawn
only four simple notations i.e special symbols and annotations that associates them
with specific system. We use three symbols for YOURDON notation
14
Figure No-3.1 Symbols of Data Flow Diagram
3.32 Description
a) Process: It describes how input data is converted to output data.
b) Data Store: It describes the repositories of data in a system.
c) Data Flow: It describes the data flowing between process, data stores and external
entities.
d) Sources: An external entity causing the origin of data.
e) Sink: An external entity, which consumes the data.
3.4 DFD’s (Physical Design)
15
3.41 Context Level DFD (Zero Level)
Figure No-3.2: Zero Level DFD
3.42 1ST Level (Admin)
login
logout
Figure No-3.3: First Level DFD (admin)
16
3.43 1st level (seeker)
LOGIN LOGOUT
DETAILS
ADDED
Figure No-3.4: First Level DFD (seeker)
3.44 2ND level (admin)
LOGIN LOGOUT
Figure No-3.5: Second Level DFD(admin)
17
3.45 2ND level (seeker)
LOGIN LOGOUT
Figure No-3.6: Second Level DFD (seeker)
3.46) DFD of Online Domestic Assistance Provider
Figure No-3.7: DFD for Online Domestic Assistance Provider
18
3.5) Entity Relationship Diagrams (ER-Diagrams): An entity-relationship (ER)
diagram is a specialized graphic that illustrates the interrelationships between entities
in a database. ER diagrams often use symbols to represent three different types of
information. Boxes are commonly used to represent entities. Diamonds are normally
used to represent relationships and ovals are used to represent attributes. An entity-
relationship model (ERM) in software engineering is an abstract and conceptual
representation of data. Entity-relationship modeling is a relational schema database
modeling method, used to produce a type of conceptual schema or semantic data
model of a system, often a relational database, and its requirements in a top-down
fashion.
3.51) Symbols used in this E-R Diagram:
a) Entity: Entity is a “thing” in the real world with an independent existence. An
entity may be an object with a physical existence such as person, car or employee.
Entity symbol is as follows
Figure No-3.8: Entity (Rectangle)
b) Attribute: Attribute is a particular property that describes the entity. Attribute

symbol is
Figure No-3.9: Attribute (oval)
c) Relationship: Relationship will be several implicit relationships among various

entity types whenever an attribute of one entity refers to another entity type some
relationship exits. Relationship symbol is:
Figure No-3.10: Relationship (diamond)
19
d) Key attributes: An entity type usually has an attribute whose values are distinct for
each individual entity in the collection. Such an attribute is called key attribute. Key
attribute symbol is as follows
Figure No-3.11: Key Attribute
e) Connecting lines: Solid lines that connect attributes to show the relationships of
entities in the diagram.
f) Cardinality: Cardinality specifies how many instances of an entity relate to one
instance of another entity. Cardinality specifies the maximum number of relationships
and ordinarily absolute minimum no. of relationships.
Figure No-3.12: Cardinality ratio
g) ER Diagram for Online Domestic Assistance Provider –Here is the ER diagram for
the Online Domestic Assistance System Provider
20
Figure No-3.13: ER Diagram For Online Domestic Assistance Provider
21
3.6 Interface Design
3.61 Input Design
a) Login Screen – Here the user will be asked whether he/she wants to login as an
admin or as a seeker. Admin will have rights of website whereas seeker just goes for
the requirement of the helper as needed.
Figure No-3.14: Ask login
22
b) Admin login- Here the admin login with valid login and password. Validation has
been performed here.
Figure No-3.15: Admin login
23
c) Admin menu –In this admin is asked to perform the desired task
Figure No-3.16: Admin Menu
24
d) Add/update Helper Details-Add/Update helper details by admin which is been set
into database. Proper validation has been performed here.
Figure No-3.17: Add/Update Helper
25
e) View Helper-In this admin enter the valid adhar no. and name of the helper to
display the details of that helper
Figure No-3.18: View Helper
26
f) View Seeker- In this admin enter the valid email id and name of the helper to
display the details of that seeker
Figure No-3.19: View seeker
27
g) Seeker login- If seeker has a signup in past the he/she just login using email id and
password. Proper validation has been performed.
Figure No-3.20: Seeker login
28
h) Seeker signup- if seeker is new to website then allow him/her to sign up with new
account.
Figure No-3.21: Seeker signup
29
i)Requirement Form-In this seeker put up the desired input as asked as per their
requirement of required helper.
Figure No-3.22: Requirement Form
30
3.62 Output Design
a) Home page- this is the welcome page of the website. It includes about us, how it
works, Contact us and Login option.
Figure No-3.23: Welcome page(login page)
31
Figure No-3.24: About Us
Figure No-3.25 How it works
32
Figure No-3.26: Contact us
b) View helper- It views the detail of the desired helper by admin
Figure No-3.27: View helper
33
c)View Seeker- It views the detail of the desired seeker by admin
Figure No-3.28: View Seeker
34
d) Add/Update helper view screen-It displays that database has been successfully
updated
Figure No-3.29: Successful Update
35
e) Required Helper details-It displays the details of helper as asked by the seeker in
the requirement form.
Figure No-3.30: Required Helper Details
36
f) Log out page-It displays on loging out from admin or seeker.
Figure No-3.31: Log Out
3.7 Database Design
a) Table Name-Helper
S.No Field Name Datatype Size Constraint Description

1 Name Varchar2 30 Name of the helper
2 Adhar no. Number 20 Primary Key Adhar Card no. of
helper
3 Phone Number 10 Contact no. of
helper
4 Gender Varchar2 10 Female/Male
5 Age Number 5 Age
6 Specification Varchar2 15 The area in which
the helper is
specified
7 Area Varchar2 8 Place of work
37
Table no-3.1: Helper Details
b) Table Name-Seeker
S.No Field Name Datatype Size Constraint Description

1 Name Varchar2 30 Name of the seeker
2 Email Id Number 15 Primary Key Email id of seeker
3 Password Varchar2 30 Password
4 Telephone Number 30 Contact no. of
seeker
5 Area Varchar2 10 Residential
location
Table no-3.2: Seeker Details
c) Table helper –Database
Figure No-3.32: Helper Database
38
d)Table Seeker-Database
Figure No-3.33: Seeker Database
39
Chapter-4
SYSTEM DEVELOPMENT
4.1 Introduction:- System development is the development of any application. This

term is used to refer to the activity of computer programming which is the process of
implem enting, debugging, testing and validating the source code, but in broader
sense of the term it includes all that is involved between the conception of the desired
software through to the final manifestation of the software, ideally in a planned and
structured process, In this chapter we are going to include the screen shots of our
system which is designed by writing the source code. We are also perform the testing
activity on the designed system and also applied some validations on the Online
Domestic Assistance Provider.
4.2 Program Development:-Program development is the process in which we are

going to write the actual code which will be needed for developing Online Domestic
Assistance Provider System. The Front End used in HTML, CSS, Java Script . The
Back End used is Oracle Database.
4.3 Front-End
4.31 HTML:- Hyper Text mark-up language, commonly referred to as HTML, is the
standards mark-up language used to create web pages and other information that can
be displayed in a web browser. It is written in the form of HTML elements consisting
of tags enclosed in angle brackets (like <HTML>), within the web page content.
HTML tags most commonly come in pairs like <h1> and </h1> although some tags
represent empty elements The first tag in a pair is the start tag, and the second tag is
the end tag. In between these tags web designers can add text, tags, comments and
other types of text based contents. The purpose of the web browser is to read the
HTML document compose them into visible and audible web pages. The browser
does not display the HTML tags and scripts but use them to interpret the content of
the page. HTML elements form the building blocks of all the websites. HTML allows
images and objects to be embedded and can be used to create the interactive forms. It
can embed scripts written in languages such as Java Script which affect the behavior
of HTML web pages. Web browser can also refer to Cascading Style Sheets (CSS) to
40
define the look and layout of text and other material. The World Wide Web
Consortium (W3C), maintainer of both the HTML and the CSS standards, encourages
the use of CSS over explicit presentational HTML.
4.32 Cascading Style Sheet (CSS) :- It is a style sheet language used for describing
the presentation semantics of a document written in a markup language. It’s most
common application is to style of web pages and uses interfaces written in HTML and
XHTML, but the language can be applied to any kind of XML document, including
plain XML,SVG and XUL. CSS is designed primarily to enable the separation of
document content from document presentation , including elements such as the
layout, colours and fonts.
4.321 This separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple pages to
share formatting and reduce complexity by specifying the relevant CSS in a separate
.css file , and reduce complexity and repetition in the structural content, such as
semantically insignificant table that were widely used to format pages before
consistent CSS rendering was tables that were widely used to format pages before
consistent CSS rendering was available in all major browsers. For each matching
HTML element , it provides a list of available in all major browsers . For each
matching HTML element , it provides a list of formatting instructions . This
separation of formatting and content makes it possible to present the markup page in
different styles for different rendering methods, such as on-screen, in print, by voice
and on Braille-based, tactile devices. It can also be used to display the web page
differently depending on the screen size or device on which it is being viewed.
4.322 While the author of a web page typically links to a CSS file within the markup
file, render can specify a different style sheet, such as a CSS file stored on their own
computer, to override the one the author has specified. If the author or the reader did
not link the document to a style sheet, the default style of the browser will be applied.
Another advantage of CSS is that aesthetic changes to the graphic design of a
document can be applied quickly and easily, by editing a few lines in one file, rather
than by a laborious process of crawling over every document line by line, changing
markup.
41
4.33 JavaScript:- JavaScript is a high-level, dynamic, untyped, and interpreted
programming language .It has been standardized in the ECMAScipt language
specification It is an interpreted computer programming language. It was Originally
implemented as a part of Web Browser so that client-side scripts could interact with
the user, control the browser, communicate asynchronously, and alter the document
content that is displayed. It is also used in server-side network programming with
runtime environments such as game development and the creation of desktop and
mobile applications. JavaScript is almost entirely object-based. In JavaScript, an
object is an associative array, augmented with a prototype (see below); each string
key provides the name for an object property. JavaScript supports much of the
structured programming syntax from C (e.g., if statements, while loops, switch
statements, do while loops, etc.). One partial exception is scoping: JavaScript
originally had only function scoping with var. ECMAScript 2015 added a let keyword
for block scoping, meaning JavaScript now has both function and block scoping.
JavaScript typically relies on a run-time environment (e.g., a Web browser) to provide
objects and methods by which scripts can interact with the environment (e.g., a
webpage DOM). It also relies on the run-time environment to provide the ability to
include/import scripts (e.g., HTML <script> elements). This is not a language feature
per se, but it is common in most JavaScript implementations.
4.4 Back-End
4.45 Oracle Database : Oracle Database (commonly referred to as Oracle RDBMS or

simply as Oracle) is an object-relational database management system produced and
marketed by Oracle Corporation.
4.451 Larry Ellison and his two friends and former co-workers, Bob Miner and Ed
Oates, started a consultancy called Software Development Laboratories (SDL) in
1977. SDL developed the original version of the Oracle software. The
name Oracle comes from the code-name of a CIA-funded project Ellison had worked
on while formerly employed by Ampex.
4.452 An Oracle database system—identified by an alphanumeric system identifier or

SID—comprises at least one instance of the application, along with data storage. An
instance—identified persistently by an instantiation number (or activation id:
42
SYS.V_$DATABASE.ACTIVATION#)—comprises a set of operating-
system processes and memory-structures that interact with the storage. Typical
processes include PMON (the process monitor) and SMON (the system monitor).
Oracle documentation can refer to an active database instance as a "shared memory
realm".
4.453 Users of Oracle databases refer to the server-side memory-structure as the SGA
(System Global Area). The SGA typically holds cache information such as data-
buffers, SQL commands, and user information. In addition to storage, the database
consists of online redo logs (or logs), which hold transactional history. Processes can
in turn archive the online redo logs into archive logs (offline redo logs), which
provide the basis for data recovery and for the physical-standby forms of data
replication using Oracle Data Guard.
4.454 The Oracle RAC (Real Application Clusters) option uses multiple instances
attached to a central storage array. In version 10g, grid computing introduced shared
resources where an instance can use CPU resources from another node in the grid.
The advantage of Oracle RAC is that the resources on both nodes are used by the
database, and each node uses its own memory and CPU. Information is shared
between nodes through the interconnect—the virtual private network.
The Oracle DBMS can store and execute stored procedures and functions within itself
. PL/SQL (Oracle Corporation's proprietary procedural extension to SQL), or the
object-oriented language Java can invoke such code objects and/or provide the
programming structures for writing them.
4.5 Testing and Debugging
4.51Software Testing:- Software Testing is the process of evaluation of a software

item to detect differences between given input and expected output. Testing assesses
the quality of the product. Software testing is a process that should be done during the
development process. In other words, software testing is a validation and verification
process. Verification is the process to make sure the product satisfies the conditions
imposed at the start of the development phase. In other words to make sure the
product behaves the way we want it to. Validation is the process to make sure the
43
product satisfies the specified requirements at the end of the development phase. In
other words, to make sure the product is build as per the customer’s requirements.
Software testing is an investigation conducted to provide stakeholders with
information about the quality of product or service under test. Testing is performed
for finding out the errors and bugs in the system.
a) Testing Principles
i. To discover as yet undiscovered errors.
ii. All tests should be traceable to customer’s requirements.
iii. Tests should be planned long before the testing actually begins.
iv. Testing should begin “in the small” and progress towards “testing in the
large”.
v. Exhaustive Testing is not possible.
vi. To be most effective training should be conducted by an independent third
party.
b) Cause of Errors :-The most common cause of errors in the software system are
i. Communication Gap between the Developer and the Business Decision

Maker:- A communication gap between the developer and the business decision
maker is normally due to subtle differences between them. The differences can be
classified into five areas : Thought process, Background and Experience, Interest,
Priorities, Language.
ii. Time provided to a developer to complete the project:- A common source of

errors in projects comes from time constraints in delivering a product. To keep the
features, the schedule can be slipped. Failing to adjust the feature set or schedule
when problems are discovered can lead to rushed work and flawed systems.
iii. Over Commitment by the developer :- High enthusiasm can lead to over
commitment by the developer. In these situations, developers are usually unable to
adhere to deadlines or quality due to lack of resources or required skills on the team.
44
iv. Insufficient Testing and Quality Control:- Insufficient testing is also a major
source of breakdown of e-commerce systems during operations, as testing must be
done during all phases of development.
v. Inadequate Requirements Gathering:- Short time to market results in

developers starting work on the website development without truly understanding the
business and technical requirements. Also, developers may create client-side scripts
using language that may not work on some client bowsers.
vi. Keeping pace with the First Changing Technology:- New technologies are
constantly introduced. There may not be adequate time to develop expertise in the
new technologies. This is a problem for two reasons. First, the technology may not be
properly implemented. Second, the technology may not integrate well with the
existing environment.
c) Levels of Testing
i. Unit Testing :- The most ‘micro ’ scale of testing , to test particular functions
and code modules. Typically done by the programmer and not by the testers, as it
requires detailed knowledge of internal program design and code. Not always easily
done unless the application has a well designed architecture with a tight code; may
require developing test drive modules or test harnesses.
ii. Integration Testing :- Testing of combined parts of an application to determine

whether they function together correctly. The ‘parts’ can be code modules, individual
applications, client and server applications on a number, etc. This type of testing is
especially relevant to client/server distributed systems.
iii. System Testing :- System Testing is the testing to ensure that by putting the
software in different environments (e.g. Operating Systems) it still works. System
Testing is done with full system implementation and environment. It falls under the
class of black box testing.
45
iv. Functional Testing:- Black-box type testing geared to functional of an
application, tester should do this type of testing. This doesn’t means that the
programmers shouldn’t check their codes before releasing it.
v. Regression Testing:- Re-testing after fixes or modifications of the software or

its environment. It is difficult to determine how much re-testing is needed, especially
near the end of the development cycle. Automated testing tools can be especially
useful for this type of testing.
vi. Acceptance Testing:- Final Testing based on the specifications of the end user
or customer or based on use by end-users / customers over some limited period of
time
vii. User Acceptance Testing:- Determining if the software is satisfactory to an

end user customer.
4.52 Debugging:- Debugging is the routine process of locating and removing

computer program bugs, errors or abnormalities, which is methodically handled by
software programmers via debugging tools. Debugging checks, detects and corrects
the errors or bugs to allow proper program operation according to set specifications.
The code to be examined might alternatively be running on an instruction set
simulator (ISS), a technique that allow great power in its ability to halt when specific
conditions are encountered but which will typically be somewhat slower than
executing the code directly on the appropriate (or the same) processor. Some
debuggers offers two modes of operations – full or partial simulation – to limit this
impact. A trap occurs when the program cannot normally continue because of a
programming bug or invalid data. When the program traps or reaches a preset
condition, the debugger typically show the location in the original code if it is a
source-level debugger or symbolic debugger, commonly now seen in integrated
development environments. If it is a low-level debugger or a machine level debugger
it shows the line in the disassembly.
46
i. Module Testing:- Module testing is the testing of complete code as objects as
produced by the compiler when built from source. A library may be composed of a
single compiled object or several compiled objects. There is only a slight difference
between unit testing and module testing. Modules are fully formed chunks of coherent
source.
i. Unit Testing:- Unit testing is a software testing method by which individual
units of source code, sets of one or more computer program modules together with
associated control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use.
ii. Integration Testing: Integration testing is any type of software testing that
seeks to verify the interfaces between components against a software design. Software
components may be integrated in an iterative way or all together ("big bang").
Normally the former is considered a better practice since it allows interface issues to
be located more quickly and fixed.
4.6 Test Cases: A test case is a set of conditions or variables under which a tester will
determine whether a system under test satisfies requirements or works correctly.The
process of developing test cases can also help find problems in the requirements or
design of an application.
4.61 System Testing (Test Cases)
Test Test Description Expected Expected Actual Actual Result

class input output input output
id
1 Admin When one Username, Admin admin, Admin Pass
login having password menu admin@123 menu
admin Page Page
rights want
to access
the website
Table no.-4.1: Test Case for login(Admin)
47
Test Test Descriptio Expected Expected Actua Actual Resul
clas n input output l input output t
s id
2 Add When one Details of Message Fields Message Pass
/Updat having helper such page of page
e admin as name, indicating helper indicating
Helper rights want specification successfu details successfu
to , gender etc l l
add/update Database Database
helper to update update
the website followed followed
by home by home
page. page.
Table no-4.2: Test case for Add/update helper
Test Test Descriptio Expecte Expected Actual input Actual Resul

clas n d input output output t
s id
3 View When one Null Empty Null Empty Fail
Helpe having Field field
r admin Adhar Say Pass
rights no. , Page 66665555666 Page
want to Name of displayin 6 , Rakesh displayin
see the helper g g
helper Detail of Detail of
details that that
helper helper
\
Table no-4.3: Test case to view helper

s id
4 View When one Adhar Page Say Page Pass
Seeke having no. , displayin Yau1@yaho displayin
r admin Name of g o. com g
rights helper Detail of Yashu Detail of
want to that that
see the Seeker seeker
seeker
48
details
Table no-4.4: Test case to view seeker

s id
5 Seeke When the Null Empty field Null Empty Fail
r seeker Field
login already Email id Requirnme Say Pass
having a passwor nt form 6666555566 Page
login id d 66 , Rakesh displayin
then the g
login from Detail of
here that
helper
\
Table no-4.5: Test case for Seeker Login
Test Test Descriptio Expected Expected Actual Actual Resul

clas n input output input output t
s id
6 Signu When Details Page Require Page Pass
p seeker such as displaying d details displaying
Seeke new to name Requirnme as per Requirnme
r website emailed nt form nt form.
then need password form
to signup. Telephon
e no etc
Table no-4.6: Test case for SignUp seeker
Tes Test Descripti Expected Expected Actual Actual Resu

t on input output input output lt
cla
ss
id
7 Requirem When Required Page Requirem Page Pass
ent form seeker details displaying ent details displaying
signin such as Detail of in the Detail of
the timeslot, the helper form the helper
he/she specificati as per as per
49
specifies on, requirenm requirenm
need/ Gender , net net
requirem area etc.
ent of the
helper by
filling a
form
Table no-4.7: Test case to view helper as per requirement
4.6.2 Unit Testing (Test Cases)
Test Case Id 1
Test Case Name Admin Login
Item/Feature being tested Whether admin is able to login or not
Sample input Username password
Expected Output Admin login menu open
Actual Output Admin login performed properly
Remarks Done properly
Table no-4.8: Test case for admin login
Test Case Id 2
Test Case Name Update Helper
Item/Feature being tested Whether admin is able to add helper
Sample input Details of helper
Expected Output Database updated properly
Actual Output Database updated properly
Table no-4.9: Test case for Updating Helper
Test Case Id 3
Test Case Name Requirement form by seeker
Item/Feature being tested Whether seeker able to view helper as per
need
Sample input Details of helper needed
Expected Output Data shown accordingly
Actual Output Data shown accordingly
Table no-4.10: Test case for Requirement Form
50
4.7 Program Coding:- Code is the seemingly complex series of numbers, letters and
symbols that is used to run our computer browsers, apps, operating systems and
websites. Knowing how to put these parts together in the correct order is necessary in
order to end up with the desired results. The code that is written is actually a language
that is translated into a set of instructions that are understood by the computer.
4.7.1 HTML coding:-

a)Home page:-
<html>
<head>
<link rel="stylesheet" type="text/css" href="style.css"></link>
<title>Online Domestic Assistance Provider</title>
</head>
<body>
<div id="home">
<header>
<img class="i1" src="C:\Users\RADHIKA\Desktop\pkg\SYM.jpg"/>
<ul>
<li><a href="#contact">Contact Us</a></li>
<li><a href="#hiw">How It Work</a></li>
<li><a href="#about">About</a></li>
<li><a class="active" href="#home">Home</a></li>
</ul>
</header>
<h1>ONLINE DOMESTIC ASSISTANCE PROVIDER</h1>
<marquee hspace=5px behavior=alernate bgcolor="pink" class="mq">ASSURED
VERIFIED DOMESTIC HELPER AT YOUR END!!</marquee>
<img class="fi2" src="C:\Users\RADHIKA\Desktop\pkg\frontimage2.png"
usemap="#helpermap"/>
<map name="helpermap">
<area shape="rect" coords="30,30,800,800" alt="login" href="ask_login.html">
</map>
<img class="sh1" src="C:\Users\RADHIKA\Desktop\pkg\start-here-arrow.png"/>
51
<img class="maid1" src="C:\Users\RADHIKA\Desktop\pkg\maid_model.png"/>
</div>
<div id="about" class="di1">
<!—About Us division coding-->
<h2>ABOUT US</h2>
<p align="justify">
This website is aimed to transform the landscape of domestic household work and
make its system professional. <br>It is an effort for formalized and well-
organized domestic maid provider. It identifies potential domestic workers;
provide professional training, up skilling and place them.
Along with that it is beneficial in following ways :-<br>
• It will provide fitness certificate of maid<br>
• It will provide police verification of the offered maid<br>
• Customer can personally negotiate with maid<br>
• Economical<br>
• Trustworthy platform<br>
• Instant feedback<br>
It provides a two-way benefit both for customer and the helper. It offers
comprehensive access to domestic help solutions to households. This is an online
search portal based on a large database of trained and verified household
help.<br>
</p>***********<img class="p3" src="C:\Users\RADHIKA\Desktop\pkg\ab1.jpg"
align="middle"/>************
<form action="service.html">
<center><input type="submit" value="BACK TO HOME"/></center>
</form>
</div>
<!—How it works division coding-->
<div id="hiw" class="di2">
<h2>HOW IT WORKS</h2>
<img class="p3" src="C:\Users\RADHIKA\Desktop\pkg\how1.jpg" align="middle"/>
</form>
52
</div>
<!—Contact Us division coding-->
<div id="contact" class="di1">
<h2>CONTACT US</h2>
<p align="justify">
For any futher query write us on our email or contach on the given toll free no.
Also feel free to provide us with your valuable feedback.Your any query or
suggestion will be taken into consideration with prompt reply.
</p>*************<img class="p3" src="C:\Users\RADHIKA\Desktop\pkg\cs.jpg"
align="middle"/>*************
<br>
</form>
</div>
</body>
</html>
b)Ask-Login
Once the user login he/she will be provided with two options as in how he/she wants
to login. These two options include Admin Login and Seeker Login. Html code of
this page is as below.
<html>
<head>
<title>
ODAP-LOGIN PAGE
</title>
</head>
<body>
<div >
<header>
<ul>
53
<li><a href="service.html">Home</a></li>
</ul>
</header>
<center><h2>LOGIN AS:</h2></center>
<form action>
<div class="img1">
<img src="C:\Users\RADHIKA\Desktop\pkg\admin-icon.png">
           &nbs
p;          &nbsp
;


<img src="C:\Users\RADHIKA\Desktop\pkg\user-icon.png">
</div>
<div class="di3">

<button type="button" class="but1" onClick="window.location='admin_login.html';"
name="Admin" value="Admin">Admin</button>
           &nbs
p;          &nbsp
;


           &nbs
p;          &nbsp
;
<button type="button" class="but1" onclick="window.location='seeker_login.html';"
name="Seeker" value="Seeker">Seeker</button>
</div>
</form>
</body>
</html>
c)Admin-login
54
If admin login is being performed then the user will be asked for admin name and
password. As admin have the major rights of the portal therefore verification has
been included using the JavaScript coding within the script tag. Admin login page
coding is as follows.
<html>
<head>
<title>
ODAP-ADMIN LOGIN PAGE
</title>
<script>
function show()
{
return validate();
}
function validate()
{
var isValid=true;
if(document.getElementById('name').value=="")
{
isValid=false;
alert("please enter name");
}
if(document.getElementById('paswrd').value!="admin@123")
{
isValid=false;
alert("Incorrect Password");
}
return isValid;
}
</script>
<body>
<div >
<header>
55
<ul>
</ul>
</header>
<center><h2>ADMIN LOGIN</h2></center>
<img align="middle" src="C:\Users\RADHIKA\Desktop\pkg\admin-icon.png"
class="img2">
<div class="form_1">
<form name="form1" action="add_uph.html" onsubmit="return show()">
NAME          :
<input type='text' id='name' />
<br>
PASSWORD:
<input type='password' id='paswrd' >
<br>
<br>
<br>
<center><input type='submit' value='LOGIN' /> </center>
</form>
</div>
</body>
</html>
d)Menu for admin-

Once the admin has successfully logged in he/she will be provided with tasks which
admin can perform. These tasks include Adding/Updating helper details from the
portal, view helper details and view seeker details. On this page Logout facility is
also being provided whose code will be seen later. The code of this page is as
follows.
<html>
<head>
56
<title>
ODAP-ADMIN
</title>
</head>
<body>
<div >
<header>
<ul>
<li><a href="lg2.html">Logout</a></li>
</ul>
</header>
<center><h2>Select The Desired Option</h2></center>
<form action>
<div >
<img src="C:\Users\RADHIKA\Desktop\pkg\add.png" class="img3">
<img src="C:\Users\RADHIKA\Desktop\pkg\u1.png"class="img3" >
<img src="C:\Users\RADHIKA\Desktop\pkg\group.png"class="img3">
</div>
<div class="di4">
<button type="button" class="but2" onClick="window.location='add_help.html';"
name="addhelper" value="ADD HELPER">ADD/UPDATE HELPER</button>
           &nbs
p;          &nbsp
;


<button type="button" class="but2" onclick="window.location='view_helper.html';"
name="VIEW helper" value="VIEW HELPER">VIEW HELPER</button>
           &nbs
p;          &nbsp
;
57


<button type="button" class="but2" onclick="window.location='view_seeker.html';"
name="VIEWSEEKER" value="VIEW SEEKER">VIEW SEEKER</button>
</div>
</form>
</body>
</html>
e)Add/update-helper
Admin can add the helper or update the helper by feeling in the details as required in
the form. On this page javascript has been used for performing validations.
<html>
<head>
<title>
ODAP-ADD/UPDATE HELPER
</title>
<script>
function show()
{
return validate();
}
function validate()
{
var isValid=true;
var isValid=false;
alert("UNATTENDED FIELD (NAME OR AGE)")
ann=document.getElementById('an').value
if(isNaN(ann) || ann.length!=12 || ann=="")

58
var isValid=false;
alert("wrong adhar no")
num=document.getElementById('phone').value
if(isNaN(num) || num.length!=10 || num=="")
var isValid=false;
alert("wrong telephone no")
if(document.form1.gender[0].checked==false &&
document.form1.gender[1].checked==false)
var isValid=false;
alert("Select a Gender")
if(document.form1.spec[0].checked==false &&
document.form1.spec[1].checked==false)
var isValid=false;
alert("Select Specification")
dropdown=document.getElementById('area').value
if(dropdown=="-1")
var isValid=false;
alert("select area")
}
</script>
</head>
<body>
<div >
<header>
<ul>
59
</ul>
</header>

<h2>ADD/UPDATE HELPER DETAILS</h2>
<img class="ser1" src="C:\Users\RADHIKA\Desktop\pkg\serv.png"/>

<form name="form1" action="add_uph_data.html" onsubmit="return show()">
NAME:          &nb
sp;
<br>
<br>
ADHAR NO.:        <input
type='text' id='an'>
<br>
<br>
TELEPHONE NO.<input type='text' id='phone' >

<br>
<br>
GENDER:
<br>
<br>
60
           &nbs
p;          &nbsp
;
FEMALE<input type='radio' name='gender' id='genf' value='female' >
<br>
<br>
           &nbs
p;          &nbsp
;
MALE<input type='radio' name='gender' id='genm' value='male'>

<br>
<br>
AGE:
           &nbs
p;
<input type='text' id='name' /><BR>
<br>
<br>
SPECIFICATION <br>
<br>
           &nbs
p;          &nbsp
;
CLEANING<input type='checkbox' name='spec' id='s1' value='clean'>

<br>
           &nbs
p;          &nbsp
;
COOKING<input type='checkbox' name='spec' id='s1' value='cook'>

61
<br>
           &nbs
p;          &nbsp
;
BABY SITTER<input type='checkbox' name='spec' id='s1' value='bs'><br>

           &nbs
p;          &nbsp
;
ELDER CARE<input type='checkbox' name='spec' id='s1' value='ER'>

<br>
<br>
AREA


<select name='area' id='area'>
<option value="-1" id='drop'>--select--</option>
<option value=del>Delhi</option>
<option value=ncr>NCR</option>
</select>
<br>
<br>

<input type='submit' value='ADD'
onclick='validate()'>        &n
bsp;
<input type='submit' value='UPDATE'>
</form>
</div>
</body>
</html>
62
f)View-helper
Admin can view helper details using helper’s adhar no. and name.
<html>
<head>
<title>
ODAP-VIEW HELPER
</title>
<script>
function validate()
{
{
alert("incorrect adhar no.");
}
if(document.getElementById('paswrd').value=="")
{
alert("Incorrect Name");
}
}
</script>
<body>
<div >
<header>
<ul>
</ul>
</header>
<center><h2>VIEW HELPER</h2></center>
<img align="middle" src="C:\Users\RADHIKA\Desktop\pkg\u1.png" class="img2">
63
<form name="form1" >
ADHAR NO:
<br>
NAME:          &nb
sp;
<input type='text' id='paswrd' >
<br>
<br>
<br>
<center><input type='submit' value='VIEW' onClick='validate()' /> </center>
</form>
</div>
</body>
</html>
g)View-seeker
Admin can view seeker details using seeker’s email id. and name.
<html>
<head>
<title>
ODAP-VIEW SEEKER
</title>
<script>
function validate()
{
{
alert("incorrect adhar no.");
}
{
alert("Incorrect Name");
64
}
}
</script>
<body>
<div >
<header>
<ul>
</ul>
</header>

<center><h2>VIEW SEEKER</h2></center>
<img align="middle" src="C:\Users\RADHIKA\Desktop\pkg\group.png"
class="img2">
<form name="form1" >
EMAIL ID:
<br>
NAME:
<input type='text' id='paswrd' >
<br>
<br>
<br>
<center><input type='submit' value='VIEW' onClick='validate()' /> </center>
</form>
</div>
</body>
</html>
h)Seeker-login
65
If seeker login is being performed then the user will be asked for seeker email id and
password. Coding is as follows.
<html>
<head>
<title>
ODAP-SEEKER LOGIN PAGE
</title>
<script>
function show()
{
return validate();
}
function validate()
{
var isValid=true;
{
isValid=false;
alert("please enter name");
}
{
isValid=false;
alert("Incorrect Password");
}
return isValid;
}
</script>
<body>
<div >
<header>
<ul>
66
</ul>
</header>
<center><h2>SEEKER LOGIN</h2></center>
<img align="middle" src="C:\Users\RADHIKA\Desktop\pkg\seeker.png"
class="img2">
<form name="form1" action="require.html" onsubmit="return show()">
EMAIL ID          :
<br>
PASSWORD:
<br>
<br>
<center><input type='submit' value='LOGIN' />
<h4><a href="form.html">Doesn't have a login id? Signup!!
</h4></center></a>
</form>
</div>
</body>
</html>
i)Seeker-signup
If the seeker is new to the portal provide him/her with a platform to create an account.
<html>
<head>
<title>
ODAP- SEEKER SIGNUP PAGE
</title>
<script>
function show()
67
{
return validate();
}
function validate()
{
var isValid=true;
{isValid=false;
alert("Enter Name");}
email=document.getElementById('email').value
at=email.indexOf("@")
dott=email.indexOf(".")
if(at<1 || (dott-at)<2 || email=="")

{isValid=false;
alert("incorrect email")}
{isValid=false;
alert("Enter Password");}
num=document.getElementById('phone').value
if(isNaN(num) || num.length!=10 || num=="")

{isValid=false;
alert("wrong telephone no")
}
if(dropdown=="-1")
{
68
isValid=false;
alert("select area")
}
return isValid;
}
</script>
</head>
<body>
<div >
<header>
<ul>
</ul>
</header>
<h2>SEEKER SIGNUP</h2>
<body>
<img class="ser1" src="C:\Users\RADHIKA\Desktop\pkg\full.png"/>
<form name="form1" action="require.html" onsubmit="return show()"
action="lg2.html">
NAME:          &nb
sp;          &nbs
p;
<br>
<br>
EMAIL ID:

<input type='text' id='email'>
<br>
<br>
69
PASSWORD:         &nbs
p;
<br>
<br>
TELEPHONE NO:
<input type='text' id='phone' >
<br>
<br>
AREA
           &nbs
p;          &nbsp
;
</select>
<br>
<br>

<center><input type='submit' value='LOGIN' ></center>
</form>
</body>
</html>
j)Requirement form
After seeker successful login, seeker will be asked to fill the given requirement form
which ask the seeker about the required details for the kind of domestic helper
they are looking for such as specification, area etc.
<html>
<head>
<title>
70
ODAP-REQUIRNMENT FORM
</title>
<script>
function validate()
{
dropdown=document.getElementById('spec').value
if(dropdown=="-1")
alert("Select Specification")
dropdown=document.getElementById('ts').value
if(dropdown=="-1")
alert("Select Time Slot")
if(document.form1.gender[0].checked==false &&
document.form1.gender[1].checked==false)
alert("Select a Gender")
if(dropdown=="-1")
alert("Select area")
}
</script>
</head>
<body>
<header>
<ul>
71
</ul>
</header>

<h2>REQUIRNMENT FORM</h2>
<img class="ser1" src="C:\Users\RADHIKA\Desktop\pkg\full.png"/>

<form name="form1">
SPECIFICATION:

<select name='spec' id=spec>
<option value=del>CLEANING</option>
<option value=ncr>COOKING</option>
<option value=ncr>BABY SITTER</option>
<option value=ncr>ELDER CARE</option>
</select>
<br>
<br>
TIMESLOT:
           &nbs
p;
<select name='time slot' id='ts'>
<option value=del>6AM-8AM</option>
<option value=ncr>10AM-12AM</option>
<option value=ncr>10AM-12AM</option>
<option value=ncr>12AM-2PM</option>
72
<option value=ncr>2PM-4PM</option>
<option value=ncr>4PM-6PM</option>
</select>
<br>
<br>
GENDER:
<br>
<br>
           &nbs
p;          &nbsp
;

FEMALE<input type='radio' name='gender' id='genf' value='female' >
<br>
           &nbs
p;          &nbsp
;

MALE<input type='radio' name='gender' id='genm' value='male'>

<br>
<br>
AREA



</select>
<br>
73
<br>
COMMENT:
           &nbs
p;
<input type='textarea' id='name' />
<br>
<br>

<input type='submit' value='SEARCH' onclick='validate()'>
</form>
</div>
</body>
</html>
k) Log Out page
This page let the user wheather admin or seeker to successfully logout.
<html>
<head>
<title>
ODAP-LOGOUT
</title>
</head>
<body>
<div >
<header>
<ul>
</ul>
</header>
<img align="middle" class="ty1" src="C:\Users\RADHIKA\Desktop\pkg\ty.png"/>
74
<center><h3>_/\_ Thanks for visiting _/\_<br>You're successfully logged out!! <br>
Click on HOME </h3></center>
</body>
</html>
4.7.2 CSS coding:-
It includes the styling of all the pages of the given portal.
body {
background-image: url("bgg3.jpg");
background-repeat: repeat-x repeat-y;
}
h1
{
padding:0px;
font-family: "Times New Roman", Times, serif;
color:white;
background-color:maroon;
text-align:center;
}
h2
{
padding:10px;
font-family: "Times New Roman", Times, serif;
color:Black;
background-color:white;
text-align:center;
}
header {
position:relative;
display:block;
max-width:100%;
75
height:83px;
margin:0 auto;
padding:0px 30px;
background:#000000;
color:#000;
}
.i1 {
top-margin: 0;
display:inline;
float:left;
border-left=0px;
border: 1px solid #ddd;
border-radius: 4px;
padding-top: 0px;
height:80px;
width: 90px;
}
ul {
list-style: none;
display:inline;
margin-bottom: 0;
padding-left: 0;
overflow:hidden;
background-color:#000000;
ul li {
position:relative;
76
float:right; !important
display: inline-block;
color: white;
text-align: center;
padding: 20px 15px;
}
ul li > a {
position: relative;
display: block;
padding: 0px 15px;
text-decoration: none;
font-size: 24px;
color:white;
}
li a:hover:not(.active) {
background-color: #cccccc;
}
.active {
background-color: #4CAF50;
}
.fi2
{
display:block;
float:right;
height:440px;
width:700px;
padding:30px 15px;
77
}
.sh1
{
float:left;
height:90px;
width:330px;
padding:20px 120px;
display:block;
}
.maid1
{
display:block;
float:left;
height:320px;
width:250px;
padding:0px 120px;
}
.mq
{
padding:0px;
font-size:25px;
color:black;
}
.di1
{
background-image:url("bgg6.jpg");
padding:0px 100px;
font-size:20px;
color:white;
float:left;
}
.di2
78
{
background-image: url("bgg3.jpg");
padding:50px 280px;
font-size:20px;
color:white;
float:left;
}
.di3
{
padding:20px 340px;
}
.di4
{
padding:10px 110px;
}
.but1
{
background-color: #008CBA;
border: 2px solid #555555 ;
color: white;
padding: 30px 54px;
text-align: center;
font-size: 14px;
box-shadow: 0 8px 16px 0 rgba(0,0,0,0.2), 0 6px 20px 0 rgba(0,0,0,0.19);
}
.button1:hover {
background-color: #4CAF50;
color: white;
}
.img1
{
padding:10px 300px ;
79
}
.img2
{
padding:30px 570px;
height:200px;
width:200px;
//align:middle;
}
.img3
{
height:140px;
width:120px;
padding:40px 160px;
}
.but2
{
background-color: #008CBA;
border: 2px solid #555555 ;
color: white;
padding: 20px 50px;
text-align: center;
font-size: 14px;
box-shadow: 0 8px 16px 0 rgba(0,0,0,0.2), 0 6px 20px 0 rgba(0,0,0,0.19);
}
.form_1
{
font-size:18px;
text-align:center;
//padding:50px 100px ;
}
80
.form_2
{
font-size:16px;
float:right;
padding:20px 150px;
.ser1
{
float:left;
height:440px;
width: 180px
padding:0px ;
}
.ty1
{
padding:30px 430px;
height:200px;
width:530px;
//align:middle;
}
.p3
{
padding:30px;
height;850px;
width:800px;
}
4.7.3 JDBC connection:-
81
import javax.servlet.http.*;
import java.io.*;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import javax.servlet.*;
public class jdbc2 extends HttpServlet {

public void doGet(HttpServletRequest req,HttpServletResponse res)throws
ServletException,IOException
{
try
{
Connection con=null;
ResultSet rs;
int count=0;
PrintWriter out=res.getWriter();
String spec1=req.getParameter("spec");
String gen1=req.getParameter(“gender”);
String area1=req.getParameter("area");
Class.forName("oracle.jdbc.driver.OracleDriver");
con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","user2
","pwd");
if(con!=null)
{ out.println("success");
}
else
{
out.println("failure");
}
Statement stmt=con.createStatement();
82
rs=stmt.executeQuery("SELECT * FROM Student WHERE
area=area1,spec=spec1,gender=gen1);
while(rs.next())
{
count++;
out.println("record-”+count+<br>"+”Name-
”rs.getString(1)"<br>"+”Adhar no.-”+rs.getInt(2)+"<br>"+”Phoneno-
”+rs.getInt(3)+"<br>"+”Gender-”+rs.getString(4)+"<br>"+”age-
”+rs.getInt(5)+"<br>"+”Specification-”+rs.getString(6)+"<br>"+”Area-
”+rs.getString(7)+"<br>");
}
if (con!=null)
{
con.close();
}
}
catch(Exception ex)
{
}
}
83
Chapter-5
SYSTEM IMPLEMENTATION
5.1 Acquisition :- A corporate action in which a company buys most, if not all, of the
target company's ownership stakes in order to assume control of the target firm.
Acquisitions are often made as part of a company's growth strategy whereby it is
more beneficial to take over an existing firm's operations and niche compared to
expanding on its own. Acquisitions are often paid in cash, the acquiring company's
stock or a combination of both. Acquisition is given as example in Table 5.1
Memory Management 1GB

Disk Space For Programmers 50GB
For Databases 1GB
Hardware Requirement 1 CPU(Dual Core)
Software Requirement Internet Browser, Oracle Database, Net
Beans 7.2.1 or above
People resources Customer, Analyst, Designer,
Developer, Tester
Table No-5.1: Acquisition
5.2 Conversion:- Conversion is the activity that transforms the stored data in the
existing information system into the format required for use in the new or changed
information system. Other activities may also be done during conversion. Conversions
can be very simple or very complex. The final activity within design is implementing
the system, which involves installing and getting the users to use the new or changed
information system. There are three types of conversion methods:-
5.21 Direct: In this type of conversion, input from the old system is transferred to the
new system. When the transfer is completed, the organization switches over to using
the new system. One disadvantage is that there is no phasing-in period to test out the
new system Valuable accounting and cost information could be lost.
84
5.22 Parallel: In the parallel conversion method, the organization uses the old system
in parallel with the new system for a period of time until it becomes comfortable with
the new system. The organization then totally switches over to the new system and no
longer uses the old one.
5.23 Partial: It can allow you to implement the system at in stages or modules. In this
method implementation of each subsystem can done by using other three changeover
methods. The risk of failure is limited up to the implementation stage. It is a less
expensive than the parallel method. It is not possible if the system cannot be separated
easily into logical modules or segments. If the system contains large number of the
phases, phase operation cost is more than a pilot approach.
5.231 For our system, Partial method has been adopted. Existing system has large user
database. Partial conversion will help in easy migration from existing system to new
system. Also it will allow end user to understand the system and its benefits as
compared to existing system. The risk of failure is limited up to the implementation
stage. It is a less expensive than the parallel method.
5.3 Training needs :- The activity of training personnel and operators is a necessary
part of the implementation of the system. There are two types of training methods:-
5.31 Vendor and In-service Training: often the best source of training on equipment is
the vendor who supplies the equipment. Most vendors offer extensive educational
programs as part of their services.
5.32 In-House Training: the main advantage of in-house training is that instructions
can be tailored according to the requirements of the organization. Often the vendors
negotiate fees and charges that are more economical if organization involves more
personnel in the training program compared to the cost of travelling to the vendor’s
location.
5.33 Training of Personnel and Operators:- A well designed system can succeed or
fail because of the way they are operated and used. The quality of training received by
personnel involved with the system in various capacities help or hinders and may
85
even prevent the successful implementation of management information system.
Those who are directly or indirectly related with the system development work must
know in detail what their roles will be, how they can make efficient use of the system
and what the system will not do for them. Both systems operators and other staff need
training.
5.34 System Operators Training:- Running of the system successfully depends on the
personnel working in the computer centers. They are responsible for providing the
necessary support. Their training must ensure that they are able to handle all possible
operations, both routine and extra ordinary in nature.
5.35 User Training: - Users may be trained on the use of equipment, particularly in
the case where, for example, a micro-computer is in use and the individual involved is
both an operator and a user. In such cases, uses must be given training how to use the
system also. Questions that may be trivial to the analyst, such as how to turn on the
terminal, how to insert a diskette into a micro-computer ,or when is it safe to turn off
equipment without danger of data loss, are significant to the new users who are not
familiar with the computers.
5.4 Documentation
5.41 Operation Manual (Instruction for Running Programs) :- The operations manual
is the authoritative guidebook of how things are done in your business. It gives you an
effective way of communicating policy and procedures, and gives your employees the
independence and security they need to operate in their jobs for maximum results.
a. To run the project, go to URL type odap.com and to make any changes in the
website portal login with the credentials username and password.
b. Now you can see which requests are need to be activated or deactivated.
c. Login with your credentials.
86
d. If you login with admin credentials you have privileges to add, update helper
and can manage the whole Portal.
e. User can view their status by logging into their account by using userid and
password.
f. Don’t forget to logout your account after your all work is completed.
5.42 User Manual:- Provides instructions and procedures for end-users. The user
manual is created with the help of which the end users will be able to manage the
website. The user manual is simple and could be understandable by anyone who will
also later join the organization. The user manual will be added later.
87
Chapter-6
SUMMARY AND CONCLUSION
6.1 Summary
This project is aimed to transform the landscape of domestic household work and
make its system professional. It is an effort for formalized and well-organized
domestic maid provider. It identifies potential domestic workers; provide professional
training, up skilling and place them
The website provides the admin the control of the website. Admin can login and can
add/update helper, view seeker and helper. Seeker can login or signup and further fill
the details as per their requirement for the desired helper.
For designing part of the website various DFD models has been used. Two modules
are being used in this website i.e admin and seeker where admin handles the helper
details as well. Using these modules working of website is being designed. DFDs
have been made from zero-level to second-level for both modules. Also an overall
DFD has been designed. ER diagram holds and defines the entities used in the table.
Required screenshots are attached.
After designing coding part come. In this HTML, CSS, JavaScript and JSP have been
used. Login forms, home page etc are made using these designing tools and language.
Two modules has been used namely admin and seeker in the given website.
Login email, password, area, gender, specifications etc fields are being used in these
modules.
After coding testing part comes. In coding part various validations has been put up for
authentic input by the user. Testing is being performed after coding. System testing
and unit testing has been performed for confirming the desired output and siplay at the
user end
88
6.2 Conclusion
The objective of the project which where to provide an easy and effective way for the
seeker to view and get the desired filtered output for the required helper has been
fulfilled successfully. A portal with fast browsing, less processing time, easy to
understand interface has been provided. Also the helpers which are provided on
website are well trained and verified. It increases efficiency. It provides an easy way
for hiring a helper with ease and safety.
Future scope of website is that that it can provide with the documents of verification
on the website only. But this has to be done carefully by keeping in mind the privacy
of the helper.
89
References\Bibliography
Books
1. Thomas Powell, A.A (2010) HTML & CSS: The Complete Reference. Delhi:
McGraw Hill
2. Kevin Loney, A.A (2004) Oracle Database 10g : The Complete Reference.
Delhi: McGraw Hill
Website
1. Reference,https://www.reference.com/business-finance/write-project-
synopsis-b5a54e108fec1692 on February at 1pm
2. Get Domestic Help, http://www.getdomestichelp.com/index.html on February

at 2pm
3. Data flow diagram, https://www.visual-paradigm.com/tutorials/data-flow-

diagram-dfd.jsp on march at 1200pm
4. Html/Css , https://www.w3school.com on march at 10am
90

Project Online Domestic Helper

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Project Online Domestic Helper

Enviado por

Direitos autorais:

Formatos disponíveis

Chapter-1

1.1 Brief Description of the Organisation:- Gitarattan International Business School

1.3 User Requirement:- Information System Project generates because of various

1.31 In the existing online domestic assistance provider system is an automated

a. It is really a time consuming process.

a. Easy GUI interface easy for user to excess it.

b) Secondary Data: The data is collected through magazines, newspapers, journals

1.81 Gantt chart

Figure no-1.1: Gantt chart

2.1 Introduction -Requirement analysis is usually the first phase of large-scale

2.2 Process Identification-Based on the requirement gathered we divide the system

2.21 Administrator Module

2.22 Seekers module:

2.31 Administrator Module

2.4) Identify the data elements(fields) in each Input & Output.

2.41) Administrator module

2.42) Seeker Module

2.5 Identify the Procedures/Rules/Mathematical Relationships used for converting

Labels Controls used Buttons

2.61 Security Requirement and Validation Rules

2.62 Validation Rules:- JavaScript provides the following validation Rules:

Table no-2.2 Range Validator

Table no-2.3 Compare Validator

3.2 Levels of Design

a) Data Flow Diagrams

3.4 DFD’s (Physical Design)

Figure No-3.2: Zero Level DFD

3.42 1ST Level (Admin)

Figure No-3.3: First Level DFD (admin)

Figure No-3.4: First Level DFD (seeker)

3.44 2ND level (admin)

Figure No-3.5: Second Level DFD(admin)

Figure No-3.6: Second Level DFD (seeker)

3.46) DFD of Online Domestic Assistance Provider

Figure No-3.7: DFD for Online Domestic Assistance Provider

Figure No-3.8: Entity (Rectangle)

b) Attribute: Attribute is a particular property that describes the entity. Attribute

Figure No-3.9: Attribute (oval)

c) Relationship: Relationship will be several implicit relationships among various

Figure No-3.10: Relationship (diamond)

Figure No-3.11: Key Attribute

Figure No-3.12: Cardinality ratio

3.61 Input Design

Figure No-3.14: Ask login

Figure No-3.15: Admin login

Figure No-3.16: Admin Menu

Figure No-3.17: Add/Update Helper

Figure No-3.18: View Helper

Figure No-3.19: View seeker

Figure No-3.20: Seeker login

Figure No-3.21: Seeker signup

Figure No-3.22: Requirement Form

Figure No-3.23: Welcome page(login page)

Figure No-3.25 How it works

Figure No-3.27: View helper

Figure No-3.28: View Seeker

Figure No-3.29: Successful Update

Figure No-3.30: Required Helper Details

Figure No-3.31: Log Out

3.7 Database Design

S.No Field Name Datatype Size Constraint Description

S.No Field Name Datatype Size Constraint Description

c) Table helper –Database