This document outlines a proposal for developing a website called Merryincircle.com. It includes specifications for the frontend user interface, backend administrative area, and site design methodology. The frontend will allow users to register, view profiles, and see matches. The backend will enable administrators to manage users, content, and categories. The site aims to load quickly across browsers with an intuitive information structure and interactivity. It will have a professional look and feel to represent the company positively online.

1. Website Development Proposal
For
Merryincircle.com
Presented by
Arvind Saharkar

2. Arvind S. Page 2
Contents
Executive Summary........................................................................................................................................................3
Functional Specifications ...............................................................................................................................................4
Overview of the System .............................................................................................................................................4
User interface - FRONTEND ...................................................................................................................................5
User Section ...........................................................................................................................................................6
BACKEND - Administrative Area ............................................................................................................................7
Site Design Methodology...............................................................................................................................................8
Fast loading ...............................................................................................................................................................8
Browser compatibility................................................................................................................................................8
Look ...........................................................................................................................................................................8
Information Structure ................................................................................................................................................9
Interactivity................................................................................................................................................................9
Coding Standard ......................................................................................................................................................10
Component Interaction........................................................................................................................................10
Third Party Tool .......................................................................................................................................................11
Testing .....................................................................................................................................................................11
Text Content ............................................................................................................................................................11
Scope Change Control..............................................................................................................................................11
Budget Estimate ..........................................................................................................................................................12
Cost Structure ..............................................................................................................................................................13
Payment Distribution...........................................................................................................................................14

3. Arvind S. Page 3
Executive Summary
This document encompasses the scope of work necessary to construct version 1.0
of the application and make that system available on the Web for general use.

4. Arvind S. Page 4
Functional Specifications
The specifications listed below outline the scope of work to be completed as part
of version 1.0 of this website application. These specifications will form the blue print from
which construction will proceed. Alterations to the scope of work defined in this document
may result in altered timeframes for completion and altered costs.
Overview of the System
The objective of the system is to develop marryincircle.com portal. This is basically
on the perspective of matrimonial reference when somebody is suggested to person who
are in search of bride/groom. User will register to the site and search for the life partner.
Basically, this project has 3 sections:-
1. User Interface-FRONTEND This section is visible to all users. User can register
with free membership or standard membership; registered user can login to the
system (Facebook login or normal login) etc., from this section.
2. User section This section can be accessed by registered user only. User can
view upto 5 stages of friends
3. Backend – Website Administration This section is accessed by super admin
only. This section allows super admin to manage users, CMS, Caste categories
and subcategories.

5. Arvind S. Page 5
User interface - FRONTEND
All pages will have navigation to the items below.
1. Home Page (accessible by all user types) The Home Page will be the first page
viewed when accessing the System and the primary introduction for all actors
visiting the site, this page is also website also known as “Lead Capture page” or
“Lander”. The Home Page will have links to the following areas via its navigation,
which will be present on all pages thereafter: Home, Enquiry, FAQ (Frequently
Asked Questions), Contact Us, and Privacy Policy. User can register/login to site
from this page via fb login.
2. About US (accessible by all user types) This is the first place people look before
they start to take you seriously. This page contains general information.
3. FAQ Page (accessible by all user types) The FAQ page will provide a list of
Frequently Asked Questions to inform new and existing users of the System and its
benefits. The FAQ page’s contents will be editable on-the-fly by system
administrators to ensure the content is kept current.
4. Contact Us Page (accessible by all user types) The place where you have a last
ditch attempt at getting potential clients, users and fans to get in touch. This page
contains contact address
5. Privacy Policy Page (accessible by all user types) The Privacy Policy page will
contain the privacy policy for the System. The site will also use SSL for privacy
assurance.

6. Arvind S. Page 6
User Section
Only registered user can access to this section. This section will have following
navigations:-
1. Profile This section allow user to manage their profile details. On right side of
page user can see post of the friends which are on 5th
stage and who are using
this app.
2. Friends of friends From this section user can view their bride/groom list added
by friends upto 5 stage with their common friends.
3. Show interests On showing interest, user is able to see his/her profile.
4. Logout This link allow user to terminate their session.

7. Arvind S. Page 7
BACKEND - Administrative Area
Website administrators (Super admin) are in charge of keeping their website
information up-to-date and monitoring the activity of other users who use the
website.
1. Login Page The login page will be used by administrators to login to the system. All
logins will be logged in a database.
2. User Management Tool This tool allow user to manage users in the system. This
allow administrator to Active/Inactive a particular user, edit/view user details,
delete user and reset user password.
3. Content Management Tool This tool enable administrator to change content of
the static pages like about us.
4. Manage Caste Categories This page allow admin to manage Caste categories
and subcategories

8. Arvind S. Page 8
Site Design Methodology
As a part of our dynamic development methodology, we identify the following
ingredients that make a successful website. These characteristics can be incorporated
into the site, to fulfill and enhance the objectives.
Fast loading
The biggest single reason visitors do not stay at a website is that it takes too long to
load – that is the time it takes for the page to appear on the computer screen. The site
needs to be designed around the premise of 'loading' as quickly as possible.
Browser compatibility
The site needs to be compatible for viewing across a wide range of user platforms
and browser software along with mobile browser. We will test the site with many different
browsers like ie9, ie10, FF23+, chrome to ensure that the vast majority of visitors can see
the site quickly and easily.
The site will be designed to confirm to a 1024x768 screen resolution. This will entail
an actual available window size somewhat smaller than 1024x768 to accommodate the
presence of system windows on the user’s desktop.
Look
An Internet site today represents the first contact point for many prospective clients.
It is, in a nutshell, showing how professional a company is, and what kind of attitude they
have in selling themselves. In full consultation with you, we will discuss the interface and
layout of the site with you, to ensure the site is attractive, appealing and reflects the
appropriate image.
We utilize extensive usability survey to ensure the site is simple to navigate to
encourage usage.

9. Arvind S. Page 9
Information Structure
A clear, crisp view of the information on the site is paramount in relation to finding
specific information on a site. At this early stage, we would anticipate the use of databases
to store articles and information of interest. To provide major benefit to the business, the
site should have significant amounts of information available to the user. This information
must be easily found and presented in such a way as to encourage use. Information on
the site must be able to be quickly and easily update, by (client company name) staff.
Interactivity
Without interactivity, a Website is purely a book online. Interactive sites capture
user details online and monitor what users do inside the system. The more visitors can
interact and 'do things' on the site, the more likely they are to revisit.

10. Arvind S. Page 10
Coding Standard
For Coding we use the well-known MVC methodology i.e., Model–view–controller.
MVC is a software architecture pattern which separates the representation of information
from the user's interaction with it. The model consists of application data, business rules,
logic, and functions. A view can be any output representation of data, such as a chart or a
diagram. Multiple views of the same data are possible, such as a bar chart for
management and a tabular view for accountants. The controller mediates input,
converting it to commands for the model or view. The central ideas behind MVC are code
reusability and separation of concerns.
Component Interaction
In addition to dividing the application into three kinds of components, the MVC design
defines the interactions between them.
 A controller can send commands to its associated view to change the view's
presentation of the model (e.g., by scrolling through a document). It can also send
commands to the model to update the model's state (e.g., editing a document).
 A model notifies its associated views and controllers when there has been a change
in its state. This notification allows the views to produce updated output, and the
controllers to change the available set of commands. A passive implementation of
MVC omits these notifications, because the application does not require them or the
software platform does not support them.[6]

11. Arvind S. Page 11
 A view requests from the model the information that it needs to generate an output
representation to the user.
Third Party Tool
Paid third party tool need to be purchase by the client.
Testing
Completing unit testing tasks in a thorough and timely manner is critical to the
overall success of this initiative. Accurate and timely testing of the application, prior to
making it available for user testing, is critical to the success of this project.
Completing user testing tasks in a thorough and timely manner is critical to the
overall success of this initiative. Completing user acceptance testing for all functional
elements within the plan timeline is the responsibility of you.
Text Content
Text for the home page, Terms of use agreement, Privacy Policy, and other page
content will be the responsibility of client.
Scope Change Control
It is the responsibility of you to adhere to the scope of work defined in this
document. It is understood by all parties that changes often occur during the course of
development. It should further be understood that those changes may result in altering the
stated project timeline and budget. It is in the best interests of both parties that scope
changes during the course of the project be minimized.
Any new work that was not in scope will be considered as Change Request (CR)
and it will charge.

12. Arvind S. Page 12
Budget Estimate
The project estimate section of this document describes the total hours required to
complete module.
# Items Hours
Analysis and Design 48
1 Understanding of the Project 4
2 Data model creation and ER diagram 8
3 Homepage mockup designing 8
4 Homepage xhtml 4
5 Inner page mockup 16
6 Inner page HTML 8
Frontend 61
User Interface – FRONTEND 8
1 Home page and CMS Integration 8
User Section 53
1 Facebook Login, Logout 8
Session Management 2
Get Friends list upto 5 stages (Friends who are using this app.) 24
2 User Profile 6
Display post from friends of the friends 3
3 Friends of the friend in popup with their common friends 8
Show interest 2

13. Arvind S. Page 13
Backend 40
1 Login, forgot password, Logout 8
Session Management
2 Dashboard 6
3 User management 10
-Add/Edit/Delete
-Active/Inactive
4 Content Management 8
-Add/Edit/Publish Content
Integrate WYSIWYG editor
5 Manage Categories and subcategories 8
-Add/Edit/Delete
-Active/Inactive
Total required man hour 149
Cost Structure
Total required man hour 149
Cost per hour (In USD) $6
Total $894

14. Arvind S. Page 14
Payment Distribution
The below payment distribution is given for fixed project. For per hour project, it will
adjust for all milestones. Milestone will delivered on Sunday of every week.
Payment Distribution
Advance Payment 30%
Milestone 1 40%
Go-Live 30%