Final Reviewed

Acknowledgment
Not everything that we received can be acknowledged with a few words, not
everything that we acknowledge will relieve us from our indebt ness to the givers.
Infect, not everybody whom we are indebted to can be mentioned here. But they
will all hold the foremost position in our achievement.
We are grateful to Mr. Mr. Milind Parikh for giving us the opportunity of working
in such an esteemed organization as openMalo and to Mrs. Tina Patel who
organized our training from very first day by putting us under the guidance of Mr.
Nehal Mehta.
We would also like to thank our training guide Mr. Nehal Mehta for making this
training a grand success for us. This training would have been impossible without
his unwavering encouragement and trust in our ideas. He was always available
for discussion whenever we struggled and almost always found a way to guide us
out of any situation when we found ourselves devoid of any idea of how to
proceed with the problem.
We are also thankful to the supporting Company staff of openMalo who helped
us during the course of the training.
We are grateful to Mr. K. R. Amin, Head of Computer Department. We would

also like to thank out internal guide Mr. H. V. Shah, who has always been a
source of inspiration to us. His guidance has always inculcated confidence in us.
The fortnightly reporting, the discussion about the training and the valuable
advices given by him helped to make this training complete. We are indebted to
him for the pristine and enlightening guidance given to us throughout our degree
program.
There remains some name unmentioned, but none remains unacknowledged.
Jay Patel
1
Viral Agrawal
Abstract
Social networking has added another dimension to ever-fascinating world of

Internet. “Connect.Us” is a social networking website that enables an extremely
high profile group of people to converge and discuss about some particular
issues. A content management system known as Drupal has been used to
develop this website. This website enables its user to create his/her profile, join a
group, have a look at events and discuss on some particular issue. With Drupal’s
extremely rich theming options and designing capabilities we have succeeded to
make it look like an RIA -reach internet application-.
Keywords : drupal , cms , ajax , XHTML , jquery, Web 2.0, Webtop
2
Index
1 Feasibility analysis
• Technical feasibility
• Operational feasibility
• Implementation feasibility
• Economic feasibility
2 Project Plan
• Overview
• Main navigation
• Utility navigation
3 Requirement Analysis
• Present system, what improvements desired.
• List of inputs and outputs (e.g. reports)
• Business rules including validation checks
• Use case diagrams
• Basic hardware and software required
4 System Design
• Design strategy, e.g. 2-tier, 3-tier, etc
• DFD (context level to maximum up to 3
levels) , software decomposition into
modules
• Class diagram
• List of tables, Table design, Data dictionary
• User interface (forms, report layout,
navigation) design
• Design of Algorithms, flow charts, etc
5 Implementation Details
• Detail explanation of steps carried out to
implement the project
• Program listing, sample input/output, etc.
6 User manual
• Installation steps
• Steps for using different functionalities of
the software.
7 Conclusion and Future work
3
8 Annexure
1. Feasibility analysis
• Technical Feasibility:
As this is a social networking portal it was needed to be made using some content
management system as it deals with huge content and various access levels. With Drupal
being openMalo’s USP it was clearly feasible to make this portal using Drupal. With
Drupal being a content management system based on php, good support in php/mysql
platform was needed as well. Initially we were total rookies at Drupal but after studying
ample amount of well-documented material for Drupal, we were confident enough to
make this portal working using Drupal.
• Operational Feasibility:
As this portal is intended for very high profile people it was needed to look exclusive. We
were supposed to try hard to make it look different and professional. In order to do that
we had to include some features of Ajax. Though it has some heavy controls in XHTML
server doesn’t need to bare much load as the number of users simultaneously using it,
will not be large.
• Implementation Feasibility:
Initially it seemed very tough to implement such portal with almost no knowledge of
Drupal. But with the help of very knowledgeable staff at openMalo it was really fun
working with Drupal. Drupal has tremendous customizable controls and modules to make
such social networks. The most tiresome and demanding task was to understand the
theming system of Drupal. With constant efforts and patience we have succeeded to make
the portal look like what it currently looks.
• Economic Feasibility:
4
Owner of openMalo is associated with an NGO in USA which works in order to make
global engagements of US better. As this project is to be done for a noble cause company
had decided to make it without charging a single penny. Though good performance at this
project was surely going to assure some other good and valuable projects in future, our
company was so keen to make this as the best pilot project so far.
5
2. Project Plan
Overview
Below is a site map for the new Connect US website. It is based on the approved Website
Redesign Site Definition and Engagement Plan. This site map will serve as a guide for
writing content,, and for designing the look and feel of site navigation. The labels used in
this site map are subject to change as content is written for the site.
Main Navigation
1. Issues
2. Advocacy
3. Events
4. Resources
5. Members (logged in only)
6. Groups (logged in only)
7. Join (Public Only)
password
Homepage Logged in only Members
Groups
Join Form
Issues
Advocacy
Events
Resources
Utility Navigation
1. Home (only on internal pages)
6
2. About Us
3. Grants
4. Contact Us
5. Login / Logout
6. My Profile (logged in only)
Full Site Structure

1. Homepage
 Issue & Advocacy Slideshow – Photos with text showing the issue
areas and advocacy skills Connect US works on.
 Blog – displays the title, date/time, author and first x characters of
the latest x blog postings (collected from all blog channels).
 Featured Member Spotlight – Picture, name, organization, issue,
and other info TBD. Rotates on page refresh.
 Flexible Promotion Area – Graphic and/or text area used to
promote an event, resource, or grant opportunity.
 Events – Latest x events added to the site (including date and title).
 Resources – Latest x resources added to the site (including date
added and title).
 Email List Sign-up – Allows site visitors to register to receive
Connect US's enewsletter.
2. Issues
 Main Page – Description of each of the 5 issue areas and why
Connect US works on those issues and the latest blog postings from the 5
issue channels.
 Individual issue pages – Latest blog postings, events, resources,
members (members only), and groups (members only) assigned to the
selected issue.
 Add blog posting (members only) – add posting to any issue blog
7
 Add blog comment (members only) – add comment to any issue
blog posting
3. Advocacy
 Main Page – Description of each of the 3 advocacy skills areas
(messaging, strategy, and tactics) and the latest blog postings from the
effective advocacy channel.
 Individual advocacy skills pages – Latest blog postings, events,
resources, members (members only), and groups (members only) assigned
to the selected advocacy skill.
 Add blog posting (members only) – add posting to effective
advocacy blog
 Add blog comment (members only) – add comment to any
effective advocacy blog posting
4. Events
 Main Page – Featured upcoming and recent events, upcoming
events (# TBD)
 Recent Connect US events – summary, recordings, transcripts, and
resources of past Connect US hosted events.
 Upcoming events list – all, by issue, by tag, display name, date(s),
time, location, and summary
 Event details pages – fields TBD, members can add tags and
comments to any event
 Event registration available for Connect US hosted events.
 Add an event (members only) – available from any page where
events are listed and event details pages.
 Download ical format file for any event
 Add event to selected group (if user is a member of a group)
8
5. Resources
 Main Page – Featured and recently added resources (# TBD),
favorite resources, resource browse and search options (TBD)
 Resource browse and search results pages – display title, type, date
submitted, submitter name, description, web or file download link, link to
comments if they exists (members only), and the issues, advocacy skills,
and tags associated with resources, members can add tags and comments
and mark any resource as a favorite.
 Add a resource (members only) – available from any page where
resources are listed.
 Add resource to selected group (if user is a member of a group)
 Main Page – Benefits of membership, how to join, featured
member spotlight (rotates), link to member application.
 Membership Application – fields and approval/communication
workflow TBD
7. Directory (Members Only)
 Main Page – Featured and new members (# TBD), directory
browse and search options (TBD) (only available to members who have
filled out their own profile (threshold TBD), My Profile summary with
link to update profile and list of members in the user's network.
 Directory browse and search results pages – includes name, title,
organization, city, state and the issues and groups associated with member,
members can add tags and comments and mark members as belonging to
their network (add to favorites).
 Member Profile – fields TBD, list of all user's content added to the
site.
 Add member to selected group (if user is a member of a group)
8. Groups (Members Only)
9
 Main Page – Description of groups and how to start one, featured
and recent groups (name, issue, summary) (list all groups until list is too
long), links to groups by issue.
 Group pages – Group blog postings and events, resources, and
members assigned to the group by group members.
9. About Us
 Main Page – Description, staff (link to full bios), Council members
 Mission and Vision
 Strategies and Activities - Brief descriptions of direct grants,
network approach, and relevant operational activities Network Advisory
Team
 History
 Contact US – basic contact info and instructions or links for
specific types of contact options (ex. grant request)
10. Grants
 Main Page – Description of direct grant programs, featured grantee
spotlight (rotates), links to specific grant opportunities
 Grantmaking process
 Grant Opportunity Descriptions
 Rapid Response Grant Application – fields and communication
workflow TBD
 Grantee list by year, type, issue
11. Contact Us (link to Contact Us page in About Us section)
12. My Profile (Members Only)
10
 Main Page – fields TBD, groups to which the user is assigned,
favorite resources, members in users network.
3. Requirement Analysis
1. Overview
This Site Definition and Engagement Plan will serve as the guiding document for creating
and operating a new website for Connect US, including, look and feel design, content,
technical development, testing, and training. The plan is divided into ten sections
addressing the audiences, goals, messages, performance indicators, functionality, content
management, staffing, architecture, and future plans for the new Connect US website. All
decisions regarding the development and maintenance of the website should factor in
these elements.
2. Target Audiences
Connect US's new website will be designed to attract anyone interested in promoting and
reflecting responsible U.S. global engagement. Specifically, the site will have the
following target audiences:
Primary Audience
Below are the definition and needs of audiences that must be successfully engaged for
this website to be successful.
1. US Foreign Policy Advocates:

Communication, policy, & management staff at foreign policy advocacy
organizations whose behavior Connect US seeks to influence.
 Find and connect with other advocates interested in promoting and reflecting
responsible U.S. global engagement
 Find resources to help them be more effective in advocacy strategy, planning and
evaluation; messaging; network-building and other aspects of their work.
 Find tools to help them collaborate with other advocates and influencers, and
influence key U.S. foreign policy makers.
11
 Share information about activities and find out what other advocates are doing.
 Get tips & lessons learned through strategy discussions.
 Discover relevant upcoming events and activities.
 Find information about Connect US grant-making and apply for grants.
2. US Foreign Policy Influencers:

Academics, think tank fellows, and research assistants working on US foreign policy.
This audience is expected to visit the site in connection with specific activities
Connect US sponsors, not as a regular resource for basic information.
 Read opinion pieces by thought leaders
 Download policy papers
 Read about results of meetings
 Discover relevant upcoming events and activities
Secondary Audience
Below are the definitions and needs of additional audiences that Connect US wants to
engage through its website.
1. US Foreign Policymakers: Congressional, Executive and Presidential campaign

staff and elected officials responsible for making or advising on US foreign
policy. This audience is expected to visit the site in connection with specific
activities Connect US sponsors, not as a regular resource for basic information.
• Opinion pieces by thought leaders
• Download policy papers
• Read about results of meetings
2. Connect US Funders: Members of the Connect US Council and their staff.
• Determine what issues Connect US community members are discussing
• Download policy papers
• Discover relevant upcoming events and activities
3. Media: Reporters & Bloggers working the foreign policy beat.
12
• Find contacts for stories.
• Determine which issues are hot
• Discover relevant upcoming events and activities
3. Goals
These website goals will be used to set priorities for all aspects of the redesign, including
content development, site architecture and functionality, technology selection, resource
allocation, and graphic design.
Goal 1: Develop and promote the vision(s) for what responsible U.S. global engagement
would
look like on a policy level. The website will achieve this goal by:
o Disseminating information and analysis on critical policy issues, particularly in
relation to the challenges that will be faced by the next President during the
transition and first years.
o Solicit and promote opinion pieces by thought-leaders about these policy
challenges
Goal 2: Foster stronger collaborations among NGOs working for a more responsible U.S.
global engagement across different foreign policy issue areas. The website will achieve
this goal by:
o Allowing individuals and organizations that join Connect US (and provide
complete profile information) to find one another through a searchable database of
network members’ contact information.
o Providing information on activities of members, particularly in relation to their
efforts to raise issues of cooperative global engagement in the context of the
campaign and transition. Directing visitors to opportunities for collaboration
through conference calls, online chats, and documents that may be edited by site
users.
13
o Allowing users to post resources and information about their activities (before
through calendar and afterwards on the blog)
o Providing members a forum for posting links to fact sheets, press releases, reports
and other materials that they have developed.
Goal 3: Enhance the effectiveness of the collective advocacy efforts of NGOs working
for more responsible U.S. global engagement. The website will achieve this goal by:
o Providing and linking to “How-To” materials on advocacy, including advice on
advocacy planning and evaluation, media outreach, tools (online conferencing,
wiki, e-advocacy), templates (fact sheets, press releases), strategic
communications, engagement with campaigns and transition teams, constituency
building and grassroots advocacy.
o Soliciting and linking to analyses of advocacy campaigns that demonstrate best
practices and highlight conditions for success.
o Share information about key decision-makers involved in the policy debates on
the priority issues (including members of congress, presidential candidates and
their staff, transition team members, etc.)
Goal 4: Develop greater coherence and effectiveness among organizations working in

specific issue areas, i.e., climate change/energy, nuclear weapons; human
rights/counterterrorism, civil-military relations and international trade and development.
The website will achieve this goal by:
o Provide messaging advice and online forums for the development of common
messages
o Providing opportunities for online discussion about strategy and policy challenges
in target issue areas.
4. Key Messages
These are the messages Connect US will use on its website to attract, educate, and inspire
visitors to join and participate in the Connect US community:
14
1. Connect US wants to actively engage in conversations with policy advocates and
policymakers on promoting and reflecting responsible U.S. global engagement. However
this engagement does not necessarily lead to funding of any specific project or effort.
2. Connect US is making a difference in U.S. foreign policy through its innovative
approach to grantmaking. focus on bringing advocates and policy makers together, and
advancement of policy proposals.
3. Connect US supports the efforts of advocates of responsible U.S. global engagement in
the nonprofit and policymaking worlds through both funding and operational activities,
including meetings, trainings and the website.
Key Performance Indicators

These KPI's are tied to the goals listed above. They will be used by Connect US to
measure the success of the website in achieving these goals.
KPI 1: Number of views of key pages and downloads.
KPI 2: Number and frequency of directory searches.
KPI 3: Number of profiles meeting a defined threshold of completeness.
KPI 4: Number and frequency of each type of user post.
KPI 5: The number of posts and comments made to Connect US sponsored blogs and
discussion boards.
KPI 6: Number of advocates who join the community.
KPI 7: The percentage of community members with at least one post per month.
KPI 8: Number of unique posters
KPI 9: Number of members who report that the Connect US website helps them connect
to at least one/three other member of the community.
KPI 10: Number of members who report that the Connect US website helped enhance
their effectiveness as an advocate.
Other Performance Indicators

These OPI's are indirectly tied to the goals listed above. They will be used by Connect US
to better understand what visitors to the website are interested in.
OPI 1: Number of visitors to site.
OPI 2: Length of time visitors spend on site.
15
OPI 3: Referring and exiting sites and pages (where visitors to the site come from and go
to)
OPI 4: General feedback from site visitors
5. User Groups and Access
Access to the new website will be controlled through a user authentication system. The
site will have seven (7) user groups that will be granted different levels of access to site
features and management tools. Each user requiring access to secure areas of the site will
have an individual username and password. The user groups are:
1. Public – This user group will have access to areas of the site that do not require a
username and password. These areas will be referred to as public. All visitors to the site
will be considered to be part of this user group until they successfully login as a member
of one of the other user groups.
2. Registered - This user group is designed for people signing up Connect US newsletters
and email blasts. Users in this group will have permission to view and update their own
user profile. (specific profile field permissions TBD). Applicants for membership will be
considered members of this group until they are approved as members.
3. Members – This user group will have permission to view content and perform
functions designated for members, create user generated content (see “User Generated
Content” below) and will be able to update their own user profile. This group may be
subdivided based on audience type (specific profile field permissions TBD).
4. Council - This user group will have permission to view content and perform functions
designated for Connect US Council members and will be able to update their own user
profile.
5. Content Author – This user group will have permission to submit non-user generated
types of content or the site. Submissions will be placed in a holding bin for a Site
Administrator or Site Editor to publish them
16
6. Site Editor – This user group will have permission to edit and publish content and may
have access to other site administration tools as defined by users in the Site Administrator
user group.
7. Site Administrator – This user group will have access to all administration and content
management tools available for the site. Site Administrators are responsible for overall
maintenance of the site as well as user management. Users can be assigned to more than
one user group. Users will be granted access based on the assigned user role that grants
them the greatest amount of access for a particular permission.
17
6. Content Management Requirements
Requirement Notes
Site administrative access: Web-based access to
Allows site administrators to update content from
content administrative tools adding, editing, and
any place that has an Internet connection.
deleting content.
User friendly tools: Simple and easy to use Site administrators and content authors do not have
interface for managing content. to read dozens of pages of documentation in order
to perform basic management and authoring tasks.
Non-technical content authoring. Content Staff can generally add content to the website
authors don’t need any web development or special without assistance from technical staff or
technical knowledge to create and edit site content. consultants.
WYSIWYG editor/HTML Source: non-technical Flexible tool that adapts to the technical knowhow
staff and site members can easily enter and maintain of the author.
site content using a What-You-See-Is-What-You-Get
(WYSIWYG) editor that enables bold, italics,
underline, images, bullets, and hotlinks. HTML tags
can be used by more experienced content authors.
Flexible site structure and navigation Site administrators may change the site structure
and navigation from time to time to adjust to
organizational needs without seeking technical
support.
On-demand Publishing: Non-technical staff and No need to wait for changes to be made. Upload and
site members can easily upload and publish web publish any document on the website within
pages and documents without assistance from minutes based on user permissions.
technical staff.
Scheduled Publishing: Selected content can be Post new or edited content, such as press releases,
scheduled for publishing and expiration at a on pre-scheduled dates and times. No need for you
specified date and time. to be available or online at the time that it goes
online.
Cross Posting: Content can be published in
Makes it quick and easy to post and maintain
multiple places on the site based on attributes
content for multiple purposes on the same site.
assigned to the content.
Archiving: Ability to archive pages in any section. Ability to prioritize available content.
Page Template Engine: Page layout and look and Allows for both the enforcement of page consistency
feel are separated from content through the use of and the ability to apply changes look and feel and
templates that can be assigned to specific types of layout throughout the site without changing
pages. individual pages.
Photo Galleries: The ability to create event photo Module for easily setting up photo galleries.
galleries as needed.
Video and audio streaming: The site will be able Linking to external video and audio streams is also
to stream flash based audio and video files. expected to be popular..
File downloads: Site administrators will be able to Makes it easy for site visitors to download files by
associate file attachments with any standard web simply clicking on a link to the file.
page. Expected file types include PDF, Word, Excel,
PowerPoint, and plain text.
Custom Databases – The ability to create custom ex. rapid response applications.
databases for specialized information
Page titles. All pages can have their own unique Make it easy for users to find what they’re looking
title bar to improve site navigation and searchability for and improves page searchability.
by search engines. This can be easily added by the
site administrator.
Printer Friendly – The ability to display and print a
Makes it easier for site visitors who need to read
version of any content page that is optimized for
website content offline.
printing.
18
Requirement Notes
Pop-up Navigation. The CMS will include
functionality to create menus associated with the
main site navigation that allow visitors to access
internal content with one click.
Calendar: Create and manage event content and
display based on event date.
Directory: Create searchable user directories and Depends on user management capabilities.
restrict access to those directories based on user
access permissions.
Blogs: create multiple blogs with administrative
control over which users can post entries and
comments.
RSS: Administrators can create rss feeds based on
content attributes.
User Management: Create and manage user Must have the ability to import users and create
groups with specific access permissions and allow custom user profile fields
site visitors to register through the website. Also
track users relationship with the Connect US,
including event participation and official status (e.g.
grantee, member)
Search: Robust internal search engine capability
Includes indexing of all text based file attachments
with the ability to restrict results based on user
(PDF, Word, Excel, etc).
permissions.
Tagging: Registered users can tag content with self Ideally administrators would be able to report non
identified labels and save those associations to the personal data on which tags are being associated
users profile. with which content.
Forms: Administrators can create forms for
Used for Rapid Response grant applications and
collecting data from visitors to the site and save the
event RSVPs.
data to a database.
Non administrative content creation – All non Publishing capabilities can be restricted.
administrative users to post and publish content to
the site.
7. Staffing Requirements
The above roles will be needed to manage the new Connect US website. Multiple people
Role Description
Site Administrator Responsible for overall maintenance of the website including final editorial
decisions, vendor relationships,
Blog Manager Responsible for recruiting guest bloggers, responding to complaints about blog
and comment postings, and encouraging active use of all site blogs. There may
be a different blog manager for each blog.
User/Member Manager Responsible for approving memberships, managing member accounts, and overall
maintenance of user records including CRM functionality.
Strategic Planner Responsible for managing the strategic direction of the site and working with
stakeholders to ensure that the site meets the goals set forth in this plan.
Responsible for tracking site stats.
can be assigned to some roles and one person may have multiple roles.
19
8. Technology used in portal
In This website we use content management software drupal.
• What is CMS?
CMS is a software package that enables content to be managed on one or more
websites. A content management system allows one or more authors to prepare and
publish information online, without needing to prepare HTML code. Modern systems
allow information and resources (images, scripts, etc.) to be stored in a database for
re-use, automatic indexing and searching, and for workflow management
(authorisation, publication, retirement, archiving).
Normally, CMSs have their own structure, such as blogs (blogging software), forums
(forum software) and general content management systems, such as Joomla, etc.
However, there are other systems that let you create your own site structure and
layout, such as Drupal.
Before we go into picking the system, you need to define what you need before doing
anything.
• What is Druapl?
Drupal is a set of scripts written in PHP that provide the framework and basic
functionalityfor building feature-rich and dynamic web sites. It is a content
management system (CMS), because it greatly simplifies the process of authoring,
managing, and publishing content—such as text, images, files, and audio—to the
Web. It is a forum, a blogging tool, and an organizer of information. It is an
extensible platform on which you can build custom modules, and it is a set of
programming APIs that allows web developers to create custom web applications
very rapidly and efficiently. Drupal is also a vibrant online community with
thousands of enthusiastic people from around the world. This community spans the
Drupal.org site, several mailing lists, user groups in various countries, a number of
nonprofit organizations, some small companies, and a growing army of freelancers
who earn their living partially or completely from using or developing Drupal. The
community has events, often coinciding with major conferences, and is an excellent
example of massively distributed cooperation.
20
• Who Should Use Drupal?
Drupal is for anyone who wants to have a web site that is well suited for (but not
limited to) multiuser communities. Drupal is for bloggers who want more than just a
blog, groups who need to cooperate online, activists who want to spread a message,
educators who want to provide online learning tools, artists who want to share media
online, businesses or individuals who want to sell goods online, and programmers
who want to work with a platform that is extensible, clean, efficient, and well
architected. Developers find Drupal very easy to customize and extend. Drupal
departs from some of the conventions and techniques of the past, and is therefore for
anyone who is eager to learn or who is investigating modern best practices for web
application building. Drupal is for anyone who is investing their efforts for the long-
term payoff and has the patience to cope with a system that is sometimes admittedly
complex. Drupal is not for those who want a blog, want it now, and don’t need any
other features. Those people should choose a free online service like Blogger.
• Technology Stack
Drupal’s design goals include both being able to run well on inexpensive web
hosting accountsand being able to scale up to massive distributed sites. The former
goal means using the mostpopular technology, and the latter means careful, tight
coding. Drupal’s technology stack is illustrated in Figure
Figure: Drupal’s technology stack
21
The operating system is at such a low level in the stack that Drupal does not care
much about it. Drupal runs successfully on any operating system that supports PHP.
The web server most widely used with Drupal is Apache, though other web servers
(including Microsoft IIS) may be used. Because of Drupal’s long history with
Apache, Drupal ships with. htaccess files in its root that secure the Drupal
installation (if you’re using a web server other than Apache, be sure to convert the
.htaccess rules to the syntax understood by your system).Clean URLs—that is, those
devoid of question marks, ampersands, or other strange characters—are achieved
using Apache’s mod_rewrite component. This is particularly important because hen
migrating from another content management system or from static files, the URLs of
The content need not change, and unchanging URIs are cool, according to Tim
Berners-Lee (http://www.w3.org/Provider/Style/URI).Drupal interfaces with the next
layer of the stack (the database) through a lightweight database abstraction layer.
This layer handles sanitation of SQL queries and makes it possible to use different
vendors’ databases without refactoring your code. The most widely tested databases
are MySQL and PostgreSQL. Drupal is written in PHP. PHP has gotten a bad
reputation, because it is easy to learn so much PHP code is written by beginners.
Like many programming languages, PHP is often abused or used to quickly hack
systems together. However, PHP can also be used to write solid code. All core
Drupal code adheres to strict coding standards.
• Advantages of drupal
 The greatest advantage of Drupal is that you have the power to determine site
structure
 Also, it is quite very human friendly (thanks to response via suggestions forums
and special usability studies)
 Moreover, it is quite search engine friendly (URLs are crawlable, the text is
automatically and semantically correct formatted)
22
 You can have literally anything: publish articles, have a blog, a forum, a shop, a
classifieds section or anything you want: you can create your own page type and
system with the right modules
 There's a great handbook, a forum and lots of contributed modules (may as well
apply to a couple of other platforms, though)
 Drupal is very performance-oriented: it works slightly better than Joomla, has a
special "Throttle" module to stay through the heavy traffic and is well optimized
internally
 You can run multiple websites from one installation (and with one or many
databases)
 One can migrate from any other platform: WordPress, phpBB, etc
 All site sections, including a blog and a forum, will be integrated and shown with
the same layout
 You can search through all the site with search (which won't work, if you are
using a 3d party forum platform)
9. Use case diagrams
23
Add
View
Modify
Administr
ator
Delete
Search
Text Description
U1: Add: Using this use case the administrator can add details to maintain the site.
Scenario1: Mainline Sequence

1. Administrator: Select “add details” option.
2. System: Various option to add the details will be displayed like add poll
question, add Security questions, upload books, upload software and
Various other details.
3. Administrator: Administrator will select the option and will add the details.
4. System: Displays the message that details have been added successfully.
Scenario2: At step 4 of the mainline sequence

4. System: Displays the message that the details have been already added.

4. System: Displays the message that some input information has not been entered.
The system displays a prompt to enter missing values.
24
U2: View: Using this use case the administrator can view details to maintain the site.

1. Administrator: Select “view details” option.
2. System: Various option to view the details will be displayed like view poll
question, view security questions, view books, view softwares and
various other details.
3. Administrator: Administrator will select the option and will view the details.
4. System: Displays the details that the administrator has selected to view.
U3: Search: Using this use case the administrator can search the details of the site.

1. Administrator: Select “search details” option.
2. System: Various options to search the details will be displayed like search
registered members of the site, search uploaded softwares, uploaded
books and various other details.
3. Administrator: Administrator will select the option and will give the keyword he
wants to search for.
4. System: Displays the details of the given keyword if found.

4. System: Displays the message if the details of the given keyword are not found.

U4: Modify: Using this use case the administrator can modify details to maintain the site.
25
1. Administrator: Select “modify details” option.
2. System: Various options to modify the details will be displayed like modify poll
question, modify security questions and various other details.
3. Administrator: Administrator will select the option and will modify the details.
4. System: Displays the message that details have been modified successfully.

4. System: Displays the message that the details have been already modified.

.
U5: Delete: Using this use case the administrator can delete details to maintain the site.

1. Administrator: Select “delete details” option.
2. System: Various options to delete the details will be displayed like delete poll
question, delete security questions and various other details.
3. Administrator: Administrator will select the option and will delete the details.
4. System: Displays the message that details have been deleted successfully.

4. System: Displays the message that the details have been already deleted.

26
27
login
Public
View info
Text Description
U1: registration: Using this use case the guest can register himself by providing
necessary details.

1. Guest: Select registration option.
2. System: Registration form will be displayed.
3. Guest: Guest will fill the form.
4. System: System will respond to the given input by user and generate email with
credentials of user.

4. System: Displays the message that the guest has already registered.

1. System: Displays the message that some input information has not been entered. The
system displays a prompt to enter missing values.

1. System: Displays the message that given Email address is not valid or have already
been used by some user. It can also respond in adverse way if the math
challenge question hasn’t been answered properly.
28
U2: View of static info: Using this use case the guest can view all information that is
featured on the home page.

1. Guest: Select any of the issue from carousel from the main page.
2. System: Carousel will change the image and display brief about the issue.

1. Guest: Select “view blog entries” option.
2. System: System will provide the show the entries of blog.
29
Login
Myprofile
Issues
Blog
Registere
d user
Resources
Events
Text Description
U1: Login: Using this use case the user can login.

1. User: Select login option.
2. System: System will ask for the username and password.
3. User: User will enter the username and details.
4. System: System redirects to the my profile page if the entered username and
password is correct.

3 System: Displays the message “invalid login” if the entered username and password
are incorrect.
30
system displays the message regarding insufficient credentials.
U2: Blog: Using this use case the user can access blog.

1. User: Select blog option.
2. System: System will display two options to “insert blog category” and to “post blog”.
3. User: User will select the option.
4. System: System redirects to the page as per the selected option.

4. User: If the user selects “insert blog category” option.
5. System: Displays the form where the user can insert the category along with its
description.

4. User: If the user selects “post blog” option.
5. System: System displays the form in which the user can select the category of the
article and post the article.
6. User: User fills the form and posts the article.
7. System: System displays the message of successful posting of article.
Scenario4: At step 7 of Scenario3

4. User: If the user wants to view the blog and comments for his blog.
5. System: System displays the categories of the user’s blog through which the user can
View the articles posted by him earlier in the selected category
6. User: User clicks on the category.
7. System: System displays all the articles of the selected category.
31
system displays a prompt to enter missing values.
U3: Events: Using this use case the user can view the upcoming, current and past events.

1. User: Select events option.
2. System: System will take user to events page with the side block containing options.
This page will be showing one featured event which is nearest in
chronological order or currently going on.
3. User: User can select any of the option from the sidebar consisting of Upcoming
events, recent events, Add event.
Scenario 2: At step 3 of the mainline sequence.

1. User: User clicks on upcoming events.
2. System: System gives the user list of upcoming events from the current date and
display teasers of event.

1. User: User clicks on recent events.
2. System: System displays the list of events which have been completed recently. User
can view any of these events by clicking on the teaser of event.

1. User. User clicks on add an event.
2 System: System will respond with add event page where user needs to enter the title of
event as well details about the event.
32
U4: Directory: Using this use case the user can view his profile with various options.

1. User: Select directory option.
2. System: System will take user to his profile page.
3. User: User will perform desired operations with his profile.

1. User: If the user selects “Campaign” tab.
2. System: Displays the tab where his campaign related information has been stored.

1. User: If the user selects “Transition” option.
2. System: Displays the tab with user’s transition related details.

1. User : If the user selects “View all contributions”.
2. System: Displays the page which contains user’s all contributions to the community.
U5: Resources: Using this use case the user can see the resources.

1. User: Select resource options.
2. System: System will display the resources page. This is a static page.
U6: Issues: Using this use case the user can have a look at the issues of community.
33
1. User: Select “issues” option.
2. System: System will display the current featured issue. The issue page will be having
blog entries regarding the issue.
3. User: User can read any of the blog entries from the page.
Scenario 2: At step 3 of mainline sequence.
1. User : User selects any of the blog entry to read.
2. System : System responds with the content of that particular blog entry.
3. User : User clicks on add comment link.
4. System : System will display the collapsed block of add comment.
5. User : User can post the comment if he/she has sufficient credentials.
Scenario 3 : At step3 of scenario 2.

1. User : User clicks on add comment.
2. System : System will open the collapsed block.
3. User : After feeling up the fields user submits the comment.
4. System : System doesn’t let the user add comment and responds with insufficient
credentials message.
Scenario 4 : At step 3 of mainline sequence.

1. User : User clicks on Add blog entry.
2. System : System responds with the page to submit new blog entry if user has enough
credentials.
34
4. System Design
1. Architecture
There are two types of architecture available.

1) Two tier architecture
2) Three tier architecture
In two tire architecture business logic and database are stored on the same server. Two
tiers of business logic and database are combined in one tier. While in three tier
architecture business logic and database are stored in different servers.
Here, in connect us we have decided to implement the system using ‘two tier
architecture.’ There will not be large number of users accessing this portal
simultaneously. The server is capable enough of entertaining limited number of users.
Database and the application logics are stored at one server only. So the client’s machine
makes the one tier and the server machine containing database and business logic makes
the other tier.
35
2. Data flow diagrams.
Data Flow Diagram is a pictorial representation, which shows how the data passes from
various stages one by one during the processing.
Thus, after understanding data flow diagram we can create general overview about the
current system processing. The standard symbols used here as per the UML standards.
DFD up to 2 levels have defined here. The 2 levels described are enough for the
explanation of the content.
Symbols used in DFD:
Most DFDs use four types of symbols, which represent system components such 3S:
External Entities, Processes, Data Flows and Data Stores.
Notations:
1. Process: Here flow of data is transformed.
2. External Entity: A source or destination of data which

is external to the system.
3. Data Flow: It is a packet of data. It may be in the form

of a document, letter, telephone call etc.
4. Data Store: Any stored data but with no storing.
36
Registered User
po ns e
Res
Administrator Ma va
na r
ge Re ious
S it
e qu pa
es rts
tt
o of s
ac
ns e ce ite
po s s
Re Connect.US
Re
sp
on
se
er
i st
reg
o
tt
es
qu
Re Guest
Data Flow Diagram: Context Level Diagram- (LEVEL 0)
37
tion
Valida
Check
Give acess level

Authentication Registered user
according there type
0.1.1 database
0.1.2 ght
ri
t
ive
righ
ser
trat
u
red
gis te
ins
re
G ive
adm
e
Giv
Registered user Administrator
Data Flow Diagram: Level – 1
38
tion
Valida
Check
Give acess level

Authentication Registered user
according there type
0.1.1 database
0.1.2
ght
ri
t
ive
righ
ser
trat
u
red
gis te
ins
re
G ive
adm
e
Giv
Registered user Administrator
39
General
Information
0.3
Issues Events Blog
Featured
0.4
Blog My profile Event issues Groups
40
Enter username &
password
Registration Login
Registered user
0.2 0.1
Check validation
& give
conformation
d
tion
atio r
rovie
reg ues t fo
n
rm a
ss p
is tr
fo
q
Con
Re
A c ce
Storag
Normal user
Featured Req
0.4 ues
t forU
p dat
ion
e
onc
ues t
resp
Req
Gran Administrator
ted
Give
General
information
0.3
Data Flow Diagram: Level -2
41
Generate
mail
0.2.3
Check
Get
username &
e
information
id
al
password
ov
0.2.1
mail
pr
0.2.2
ap
ive
Give
G
us c ded
e rna hec oc ee
es t pr
me k u Requ
& ni qu Temp data store
pa e
ss In s
wo ert
rd valu
e in
da t
a ba
se
Database
Updation
Data Flow Diagram: Level-3
42
3. Class diagram.
Connect US class diagram.
43
4. Data Dictionary
access
Field Type Null Default Comments
aid int(11) No
mask varchar(255) No
type varchar(255) No
status tinyint(4) No 0
authmap
aid int(10) No
uid int(11) No 0
authname varchar(128) No
module varchar(128) No
blocks
delta varchar(32) No 0
theme varchar(255) No
weight tinyint(4) No 0
region varchar(64) No left
custom tinyint(4) No 0
throttle tinyint(4) No 0
visibility tinyint(4) No 0
pages text No
title varchar(64) No
44
blocks_roles
delta varchar(32) No
rid int(10) No
boxes
bid int(11) No
body longtext Yes NULL
info varchar(128) No
format int(11) No 0
cache
cid varchar(255) No
data longblob Yes NULL
expire int(11) No 0
created int(11) No 0
headers text Yes NULL
cache_content
cid varchar(255) No
expire int(11) No 0
cache_filter
cid varchar(255) No
45
expire int(11) No 0
cache_menu
cid varchar(255) No
expire int(11) No 0
cache_page
cid varchar(255) No
expire int(11) No 0
cache_views
cid varchar(255) No
expire int(11) No 0
captcha_points
form_id varchar(128) No
module varchar(64) Yes NULL
46
type varchar(64) Yes NULL
cck_address_countries
country_code varchar(2) No
country_name varchar(64) No
cck_address_states
state_id int(10) No
state_name varchar(64) No
state_abbrv varchar(5) No
country_code varchar(2) No
comments
cid int(11) No
pid int(11) No 0
nid int(11) No 0
uid int(11) No 0
subject varchar(64) No
comment longtext No
hostname varchar(128) No
timestamp int(11) No 0
score mediumint(9) No 0
format int(11) No 0
thread varchar(255) No
users longtext Yes NULL
name varchar(60) Yes NULL
mail varchar(64) Yes NULL
homepage varchar(255) Yes NULL
contact
47
cid int(10) No
category varchar(255) No
recipients longtext No
reply longtext No
selected tinyint(4) No 0
contemplate
type varchar(32) No
teaser text No
body text No
rss text No
enclosure varchar(128) No
flags int(8) No 7
contemplate_files
site varchar(255) No
data longblob No
content_field_election_related_activiti
Table comments: InnoDB free: 11264 kB

vid int(10) No 0
delta int(10) No 0
nid int(10) No 0
field_election_related_activiti_value longtext Yes NULL
48
content_field_level_of_engagement_durin

vid int(10) No 0
delta int(10) No 0
nid int(10) No 0
field_level_of_engagement_durin_value longtext Yes NULL
content_field_primaryissues

vid int(10) No 0
delta int(10) No 0
nid int(10) No 0
field_primaryissues_value longtext Yes NULL
content_field_primaryjobfunction

vid int(10) No 0
delta int(10) No 0
nid int(10) No 0
field_primaryjobfunction_value longtext Yes NULL
content_field_regionalfocus
49

vid int(10) No 0
delta int(10) No 0
nid int(10) No 0
field_regionalfocus_value longtext Yes NULL
content_field_transition_related_activi

vid int(10) No 0
delta int(10) No 0
nid int(10) No 0
field_transition_related_activi_value longtext Yes NULL
content_type_page
vid int(10) No 0
nid int(10) No 0
content_type_story
vid int(10) No 0
nid int(10) No 0
content_type_usernode
vid int(10) No 0
nid int(10) No 0
content_type_userprofile
50
vid int(10) No 0
nid int(10) No 0
field_address_street1 longtext Yes NULL
field_address_street2 longtext Yes NULL
field_address_apt varchar(15) Yes NULL
field_address_city longtext Yes NULL
field_address_state varchar(100) No
field_address_zip varchar(15) No
field_address_country varchar(2) No
field_address_other longtext Yes NULL
field_firstname_value longtext Yes NULL
field_mobilephone_value varchar(255) No
field_organisationwebsite_url varchar(255) No
field_organisationwebsite_title varchar(255) No
field_organisationwebsite_attributes mediumtext Yes NULL
field_middleintial_value varchar(1) No
field_organisationdescription_value longtext Yes NULL
field_lastname_value longtext Yes NULL
field_organisationname_value longtext Yes NULL
field_projectdescription_value longtext Yes NULL
field_title_value longtext Yes NULL
field_workphone_value varchar(255) No
field_otherjobfunction_value longtext Yes NULL
field_volunteeraffiliations_value longtext Yes NULL
field_languagesspoken_value longtext Yes NULL
field_otherissues_value longtext Yes NULL
field_consultant_value longtext Yes NULL
file_revisions
fid int(10) No 0
vid int(10) No 0
description varchar(255) No
list tinyint(3) No 0
files
51
fid int(10) No 0
nid int(10) No 0
filename varchar(255) No
filepath varchar(255) No
filemime varchar(255) No
filesize int(10) No 0
filter_formats
format int(11) No
name varchar(255) No
roles varchar(255) No
cache tinyint(4) No 0
filters
format int(11) No 0
delta tinyint(4) No 0
flood
event varchar(64) No
history
uid int(11) No 0
nid int(11) No 0
52
menu
mid int(10) No 0
pid int(10) No 0
path varchar(255) No
type int(10) No 0
menu_per_role
mid int(10) No 0
rid int(10) No 0
node
nid int(10) No
vid int(10) No 0
type varchar(32) No
uid int(11) No 0
status int(11) No 1
changed int(11) No 0
comment int(11) No 0
promote int(11) No 0
moderate int(11) No 0
sticky int(11) No 0
node_access
53
nid int(10) No 0
gid int(10) No 0
realm varchar(255) No
grant_view tinyint(3) No 0
grant_update tinyint(3) No 0
grant_delete tinyint(3) No 0
node_comment_statistics
nid int(10) No
last_comment_timestamp int(11) No 0
last_comment_name varchar(60) Yes NULL
last_comment_uid int(11) No 0
comment_count int(10) No 0
node_counter
nid int(11) No 0
totalcount bigint(20) No 0
daycount mediumint(8) No 0
node_field
field_name varchar(32) No
global_settings mediumtext No
required int(11) No 0
multiple int(11) No 0
db_storage int(11) No 0
54
node_field_instance
type_name varchar(32) No
weight int(11) No 0
label varchar(255) No
widget_type varchar(32) No
widget_settings mediumtext No
display_settings mediumtext No
description mediumtext No
node_group
group_name varchar(32) No
label varchar(255) No
settings mediumtext No
weight tinyint(4) No
node_group_fields
group_name varchar(32) No
node_revisions
nid int(10) No
vid int(10) No
uid int(11) No 0
body longtext No
teaser longtext No
log longtext No
55
format int(11) No 0
node_type
type varchar(32) No
description mediumtext No
help mediumtext No
has_title tinyint(3) No
title_label varchar(255) No
has_body tinyint(3) No
body_label varchar(255) No
min_word_count smallint(5) No
custom tinyint(4) No 0
modified tinyint(4) No 0
locked tinyint(4) No 0
orig_type varchar(255) No
nodefamily
parent_nid int(10) No
child_nid int(10) No
permission
rid int(10) No 0
perm longtext Yes NULL
tid int(10) No 0
56
role
rid int(10) No
name varchar(64) No
search_dataset
sid int(10) No 0
data longtext No
search_index
word varchar(50) No
sid int(10) No 0
fromsid int(10) No 0
fromtype varchar(16) Yes NULL
score float Yes NULL
search_total
word varchar(50) No
count float Yes NULL
57
sequences
id int(10) No 0
sessions
uid int(10) No
sid varchar(64) No
cache int(11) No 0
session longtext Yes NULL
system
filename varchar(255) No
status int(11) No 0
throttle tinyint(4) No 0
bootstrap int(11) No 0
schema_version smallint(6) No -1
weight int(11) No 0
term_data
tid int(10) No
vid int(10) No 0
description longtext Yes NULL
58
term_hierarchy
tid int(10) No 0
parent int(10) No 0
term_node
nid int(10) No 0
tid int(10) No 0
term_relation
tid1 int(10) No 0
tid2 int(10) No 0
term_synonym
tid int(10) No 0
url_alias
pid int(10) No
src varchar(128) No
dst varchar(128) No
59
usernode
nid int(10) No
uid int(10) No
users
uid int(10) No 0
name varchar(60) No
pass varchar(32) No
mail varchar(64) Yes
mode tinyint(4) No 0
sort tinyint(4) Yes 0
threshold tinyint(4) Yes 0
theme varchar(255) No
signature varchar(255) No
access int(11) No 0
login int(11) No 0
timezone varchar(8) Yes NULL
language varchar(12) No
picture varchar(255) No
init varchar(64) Yes
data longtext Yes NULL
users_roles
uid int(10) No 0
rid int(10) No 0
60
variable
name varchar(48) No
value longtext No
view_argument
vid int(10) No 0
argdefault varchar(255) Yes NULL
title varchar(255) Yes NULL
options varchar(255) Yes NULL
position int(2) Yes NULL
wildcard varchar(32) Yes NULL
wildcard_substitution varchar(32) Yes NULL
view_exposed_filter
vid int(10) No 0
field varchar(255) Yes NULL
label varchar(255) Yes NULL
optional int(1) Yes NULL
is_default int(1) Yes NULL
operator int(1) Yes NULL
single int(1) Yes NULL
view_filter
61
vid int(10) No 0
tablename varchar(255) Yes NULL
value longtext Yes NULL
operator varchar(20) Yes NULL
view_sort
vid int(10) No 0
sortorder varchar(5) Yes NULL
view_tablefield
vid int(10) No 0
label varchar(255) Yes NULL
handler varchar(255) Yes NULL
sortable int(1) Yes NULL
defaultsort varchar(5) Yes NULL
view_view
vid int(10) No 0
name varchar(32) No
description varchar(255) Yes NULL
62
access varchar(255) Yes NULL
page int(1) Yes NULL
page_title varchar(255) Yes NULL
page_header longtext Yes NULL
page_header_format int(4) No
page_empty longtext Yes NULL
page_empty_format int(4) No
page_footer longtext Yes NULL
page_footer_format int(4) No
page_type varchar(20) Yes NULL
use_pager int(1) Yes NULL
nodes_per_page int(5) Yes NULL
url varchar(255) Yes NULL
menu int(1) Yes NULL
menu_tab int(1) Yes NULL
menu_tab_weight int(4) Yes NULL
menu_title varchar(255) Yes NULL
menu_tab_default int(1) Yes NULL
menu_tab_default_parent_type varchar(10) Yes NULL
menu_parent_title varchar(255) Yes NULL
menu_parent_tab_weight int(4) Yes NULL
block int(1) Yes NULL
block_title varchar(255) Yes NULL
block_use_page_header int(1) Yes NULL
block_header longtext Yes NULL
block_header_format int(4) No
block_use_page_footer int(1) Yes NULL
block_footer longtext Yes NULL
block_footer_format int(4) No
block_use_page_empty int(1) Yes NULL
block_empty longtext Yes NULL
block_empty_format int(4) No
block_type varchar(20) Yes NULL
nodes_per_block int(5) Yes NULL
block_more int(1) Yes NULL
breadcrumb_no_home int(1) Yes NULL
changed int(11) Yes NULL
view_args_php longtext Yes NULL
is_cacheable int(1) Yes NULL
63
vocabulary
vid int(10) No
description longtext Yes NULL
help varchar(255) No
relations tinyint(3) No 0
hierarchy tinyint(3) No 0
multiple tinyint(3) No 0
required tinyint(3) No 0
tags tinyint(3) No 0
vocabulary_node_types
vid int(10) No 0
type varchar(32) No
watchdog
wid int(11) No
uid int(11) No 0
type varchar(16) No
message longtext No
severity tinyint(3) No 0
link varchar(255) No
location text No
referer varchar(128) No
64
5. User Interface Design.
Screenshots
This is homepage of Connect US. This page displays issues in the main carousel.
Carousel is JQuery based control which lets you to move between the images in various
ways. It also automatically changes the images at some predetermined time interval. It
also displays events, blog entries and resources at the lower part of the page. Welcome to
65
connect US block is replaced by login block and search bar is removed when the guest is
visiting the home page.
This is the page where the user is directed when he/she logs in. This page contains users’
basic information and links to user’s contributions to the community.
66
This is drupal’s basic admin panel with connect US theme.
67
This is events page. Here, user can view the most recent or current event by default. He
can choose the different options from the side block as well. User can create his own
event as well.
68
This page displays the main concern issues for community. By default it will display
some featured issue. It will display the blog and enable the users to post in the blog,
create a new entry and comment on the blog.
69
Connect US provides grant to many organizations that work in order to make this world a
better place. So, any organization, looking for some grant, can have a look at this page
and apply for grant.
70
5. Implementation Details.
Steps carried out in order to implement the project.
This Connect US is a web portal intended for advocates and policy makers to enable them
to analyze the situation in a better way to make global engagements of United States of
America better. This project was led by consultant of NGO Connect US that is led by
Heather Hamilton.
All the requirements of the projects had not been given at first place. We had decided to
move forward step by step. Our project leader needed to talk to the consultant for
deciding the things. They sent us a detailed document saying what’s the project all about
and what was it intended to do. From the document we were supposed to design the pages
and wait for consultant’s approval.
From the detailed requirements of the client we decided to modularize the project. After
studying the requirements we reached to the conclusion that this whole thing revolves
around issues. So, our primary and main module had to be issues. Most of the other little
modules revolve around these issues.
We modularized the project in 5 different modules,
1) Profile
2) Events
3) Grants
4) Issues
5) Homepage
1) Profile: As this portal was supposed to be a social network, profile had to be the vital
part. Profile is the page where the user is redirected immediately after he logs in There is
no profile listing type of thing. A user can search for a particular profile from the home
page search bar. This profile is not your typical social network profiles which list the
71
hobbies and favorite singers. This profile is used to display user’s volunteer affiliations,
his areas of social work and his concerned issues.
2) Events : Connect US frequently organizes lectures or meet ups of like minded people
in order to discuss on some issue. This module enables the registered user to have a look
at the events. Implementing events was made really easy by Drupal’s powerful event
module. We had to hack some of the codes of event module to make it work in our way.
3) Grants : Connect US generously donates to NGOs around the globe. All we needed to
do is enlist all the available grants and randomly display any of the two grants. A person
can certainly have a look at all the available grants. By clicking on apply now he can
apply for the grant by providing necessary details.
4) Issues is the most complicated part to be implemented. All the events, blogs and
resources move around the issues. People gather over social networks to have an
elaborated discussion over the issues. We had to provide a blog on issue page. Blog posts
are not monitored. Issue page also displays events related to this issue. Issue page
displays resources for issue as well.
5) Home page: Designing the home page was the most tedious part. Playing with Drupal
theme engine is the most complicated thing to do. Homepage also has a carousel. Drupal
is not capable enough to have JCarousel directly. We had to make it working by writing a
complicated code in Javascript using Jquery library. Drupal has a little hook jquery_add
which adds your jquery based file to your Drupal website.
72
6. User Manual
Installation Steps
Installing Drupal:
This document outlines the standard installation process.
1. Requirements
2. Server Configuration
3. Optional Components
4. Installation
5. Drupal Administration
6. Customizing Your Theme(S)
7. Upgrading
8. More Information
REQUIREMENTS
1. Drupal requires a web server, PHP4 (http://www.php.net/) and either

MySQL, PostgreSQL or a database server supported by the PHP PEAR API
(http://pear.php.net/).
2. To Install you will need an FTP program to upload files to the server, or shell access
if you wish to install using the commands listed below; access to run database scripts
directly or a tool such as PHPMyAdmin to manage a database; knowledge of how to
use either FTP programs or shell access to set permissions on directories, and how to
run database scripts.
3. NOTE: The Apache web server and MySQL database are strongly recommended;
other web server and database combinations such as IIS and PostgreSQL
are possible but tested to a lesser extent.
SERVER CONFIGURATION
Your PHP must have the following settings:
73
session.save_handler user
In addition, we recommend the following settings:
session.cache_limiter none
These values are set in php.ini and can be overwritten in a .htaccess file; you can print out
your local PHP settings with PHP's phpinfo() function.
OPTIONAL COMPONENTS
* To use XML-based services such as the Blogger API, Jabber, RSS

syndication, you will need PHP's XML extension. This extension is
enabled by default in standard PHP4 installations.
* If you want support for clean URLs, you'll need mod_rewrite and
the ability to use local .htaccess files. (More information can
be found in the Drupal handbook on drupal.org.)
INSTALLATION
1. DOWNLOAD DRUPAL
You can obtain the latest Drupal release from http://drupal.org/.

Download the current tar.gz format and extract the files:
$ wget http://drupal.org/files/project/drupal-x.x.x.tgz
$ tar -zxvf drupal-x.x.x.tgz
This will create a new directory drupal-x.x.x/ containing all Drupal files and directories.
Move the contents of that directory into a directory within your web server's document
root or your public HTML directory:
$ mv drupal-x.x.x/* drupal-x.x.x/.htaccess /var/www/html

2. CREATE THE DRUPAL DATABASE
74
These instructions are for MySQL. If you are using another database, check the database
documentation. In the following examples, "dba_user" is an example MySQL user which
has the CREATE and GRANT privileges. You will need to use the appropriate user name
for your system.
First, you must create a new database for your Drupal site:
$ mysqladmin -u dba_user -p create drupal
MySQL will prompt for the dba_user database password and then create the initial
database files. Next you must login and set the access database rights:
$ mysql -u dba_user -p
Again, you will be asked for the dba_user database password. At the MySQL prompt,
enter following command:
GRANT ALL PRIVILEGES ON drupal.*

TO nobody@localhost IDENTIFIED BY 'password';
where
* 'drupal' is the name of your database

* 'nobody@localhost' is the userid of your webserver MySQL account
* 'password' is the password required to log in as the MySQL user
If successful, MySQL will reply with Query OK, 0 rows affected to activate the new
permissions you must enter the command flush privileges; and then enter '\q' to exit
MySQL.
3. LOAD THE DRUPAL DATABASE SCHEME
75
Once you have a database, you must load the required tables:
$ mysql -u nobody -p drupal < database/database.mysql
4. CONNECTING DRUPAL
The default configuration can be found in the 'sites/default/settings.php' file within your
Drupal installation. Before you can run Drupal, you must set the database URL and the
base URL to the web site. Open the configuration file and edit the $db_url line to match
the database defined in the previous steps:
$db_url = "mysql://username:password@localhost/drupal";
Set $base_url to match the address to your web site:
$base_url = "http://www.example.com";
In addition, a single Drupal installation can host several Drupal-powered sites, each with
its own individual configuration.
If you don't need to run multiple Drupal sites, you can skip to the next section.
Additional site configurations are created in subdirectories within the 'sites' directory.
Each site subdirectory must have a 'settings.php' file which specifies the configuration
settings. The
easiest way to create additional sites is to copy the 'default' directory and modify the
'settings.php' file as appropriate. The new
directory name is constructed from the site's URL. The configuration for
www.example.com could be in
'sites/example.com/settings.php' (note that 'www.' should be omitted if users can access
your site at http://example.com/).
76
Sites do not each have to have a different domain. You can use subdomains and
subdirectories for Drupal sites also. For example, example.com, sub.example.com, and
sub.example.com/site3 can all be
defined as independent Drupal sites. The setup for a configuration such as this would
look like the following:
sites/default/settings.php
sites/example.com/settings.php
sites/sub.example.com/settings.php
sites/sub.example.com.site3/settings.php
When searching for a site configuration (for example www.sub.example.com/site3),
Drupal will search for configuration files in the following order, using the first
configuration file it finds:
sites/www.sub.example.com.site3/settings.php
sites/sub.example.com.site3/settings.php
sites/example.com.site3/settings.php
sites/www.sub.example.com/settings.php
sites/sub.example.com/settings.php
sites/example.com/settings.php
sites/default/settings.php
Each site configuration can have its own site-specific modules and themes that will be
made available in addition to those installed in the standard 'modules' and 'themes'
directories. To usesite-specific modules or themes, simply create a 'modules' or 'themes'
directory within the site configuration directory. For example, if sub.example.dom has a
custom theme and a custom module
that should not be accessible to other sites, the setup would look like this:
sites/sub.example.com/:
settings.php
themes/:
custom_theme
77
modules/:
custom_module
NOTE: for more information about multiple virtual hosts or the configuration settings,
consult the Drupal handbook at drupal.org.
5. CONFIGURE DRUPAL
You can now launch your browser and point it to your Drupal site.
Create an account and login. The first account will automatically become the main
administrator account.
6. CRON TASKS
Many Drupal modules have periodic tasks that must be triggered by a cron job. To
activate these tasks, you must call the cron page;
this will pass control to the modules and the modules will decide if and what they must
do.
The following example crontab line will activate the cron script on the hour:
0 * * * * wget -O - -q http://HOSTNAME/cron.php
Installing Commect US
1) Place the connect US folder in htdocs/www folder.
2) Try to open the site in any browser.
3) If you are running the site and haven’t installed the database, drupal’s error engine will
give the error.
78
4) Create the database ConnectUS.
5) Import connectus.sql file to ConnectUS database.
6) open \site\default\settings.php and give the database name and mysql id and password
appropriately.
Steps for using different features of portal.
Site Map for Connect US Website
Overview
Below is a site map for the new Connect US website. It is based on the approved Website
Redesign Site Definition and Engagement Plan. This site map will serve as a guide for
writing content,, and for designing the look and feel of site navigation. The labels used in
this site map are subject to change as content is written for the site.
Main Navigation
1. Issues
2. Advocacy
3. Events
4. Resources
Utility Navigation
1. Home (only on internal pages)

2. About Us
3. Grants
Full Site Structure
79
Homepage
 Issue & Advocacy Slideshow – Photos with text showing the

issue areas and advocacy skills Connect US works on.
 Blog – displays the title, date/time, author and first x characters of
the latest x blog postings (collected from all blog channels).
 Featured Member Spotlight – Picture, name, organization, issue,
and other info TBD. Rotates on page refresh.
 Flexible Promotion Area – Graphic and/or text area used to
promote an event, resource, or grant opportunity.
 Events – Latest x events added to the site (including date and title).
 Resources – Latest x resources added to the site (including date
added and title).
 Email List Sign-up – Allows site visitors to register to receive
Connect US's enewsletter.
Issues
 Main Page – Description of each of the 5 issue areas and why
Connect US works on those issues and the latest blog postings from the 5
issue channels.
 Individual issue pages – Latest blog postings, events, resources,
members (members only), and groups (members only) assigned to the
selected issue.
 Add blog posting (members only) – add posting to any issue blog
 Add blog comment (members only) – add comment to any issue
blog posting
Advocacy
 Main Page – Description of each of the 3 advocacy skills areas

(messaging, strategy, and tactics) and the latest blog postings from the
effective advocacy channel.
 Individual advocacy skills pages – Latest blog postings, events,
80
resources, members (members only), and groups (members only) assigned
to the selected advocacy skill.
 Add blog posting (members only) – add posting to effective
advocacy blog
 Add blog comment (members only) – add comment to any
effective advocacy blog posting
Events
 Main Page – Featured upcoming and recent events, upcoming

events (# TBD)
 Recent Connect US events – summary, recordings, transcripts, and
resources of past Connect US hosted events.
 Upcoming events list – all, by issue, by tag, display name, date(s),
time, location, and summary
 Event details pages – fields TBD, members can add tags and
comments to any event
 Event registration available for Connect US hosted events.
 Add an event (members only) – available from any page where
events are listed and event details pages.
 Download ical format file for any event
 Add event to selected group (if user is a member of a group)
Resources
 Main Page – Featured and recently added resources (# TBD),

favorite resources, resource browse and search options (TBD)
 Resource browse and search results pages – display title, type, date
submitted, submitter name, description, web or file download link, link to
comments if they exists (members only), and the issues, advocacy skills,
and tags associated with resources, members can add tags and comments
and mark any resource as a favorite.
81
 Add a resource (members only) – available from any page where
resources are listed.
 Add resource to selected group (if user is a member of a group)
Join (Public Only)
 Main Page – Benefits of membership, how to join, featured

member spotlight (rotates), link to member application.
 Membership Application – fields and approval/communication
workflow TBD
Directory (Members Only)
 Main Page – Featured and new members (# TBD), directory

browse and search options (TBD) (only available to members who have
filled out their own profile (threshold TBD), My Profile summary with
link to update profile and list of members in the user's network.
 Directory browse and search results pages – includes name, title,
organization, city, state and the issues and groups associated with member,
members can add tags and comments and mark members as belonging to
their network (add to favorites).
 Member Profile – fields TBD, list of all user's content added to the
site.
 Add member to selected group (if user is a member of a group)
About Us
 Main Page – Description, staff (link to full bios), Council members
 Mission and Vision
 Strategies and Activities - Brief descriptions of direct grants,
network approach, and relevant operational activities
 Network Advisory Team
 History
82
 Contact US – basic contact info and instructions or links for
specific types of contact options (ex. grant request)
Grants
 Main Page – Description of direct grant programs, featured grantee

spotlight (rotates), links to specific grant opportunities
 Grantmaking process
 Grant Opportunity Descriptions
 Rapid Response Grant Application – fields and communication
workflow TBD
83
7. Further Enhancements
Groups
Community members will be able to request the formation of adhoc groups. These groups
will have a group blog and group index page that will collect and provide members with
direct access to all site content associated with the group, including members assigned to
the group. Any member, even if they are not associated with the group can view group
index pages, but only members assigned to the group can associate content with that
group. Any member can request to be assigned to a group. The public will not have
access to any group pages.
Tagging
Registered users will be able to apply their own tags to any resource, directory, and
blogging content for easy retrieval. Tagging will give members a greater sense of
ownership of the content and allow them to save content they find useful in a way that's
meaningful to them. Using tagging reports, Connect US can look for patterns in how
content is being grouped.
Syndication/RSS
Members of the community will be able to receive RSS feeds for all or a specific type of
content. RSS feeds will increase the reach of the website and ensure allow members to
push the specific types of content they are interested in tracking, ensuring a greater
likelihood that the content will be read.
Share Content
Each content page on the website will have multiple options for sharing the page. In
addition to emailing the page, visitors will have access to links that will post entries for
84
any page on the site to major social bookmarking sites (specific sites TBD). Making it
easy to share connect will increase page views and therefore search engine rankings.
3rd Party Collaboration and Community Tools

A prominent links will be included to 3rd party tools used to support the Connect US
community. Best of breed 3rd party tools will provide Connect US with expanded
capabilities without the time and expense f modifying equivalent but less featured
collaboration and community tools provided with many
Reports
Some reports based on KPI – key performance indicator and OPI –other performance
indicators should be generated in order to help connect US to analyze the situation.
Wiki editing
Future functionality being considered for the website includes wiki editing and access to
web conferencing tools through account paid for by Connect US.
85
8. Annexure
1. Glossary of terms and abbreviations.
drupal An extremely powerful content management system

Ajax Asynchronous JavaScript and XML
Jquery A new way to implement Ajax instead of conventional DOM based Ajax
CMS Content management system
Php An open source server side scripting language
Webtop A web application that is very close to a desktop application
LAMP Acronym for Linux, Apache, MySql, php.
Hook Drupal’s customizable functions are known as hooks
Breadcrumb Drupal’s in-built system which monitors workflow
Carousel Rotating image system
86
2. Bibliography
“There is no site that is so small, that it is not important to someone.”

-Steven Penn
Websites:
www.drupal.org All about Drupal, total documentation,
modules, theme templates, handbooks
www.php.net An awesome site which has complete manual
for php
Books
Dries Buytart “Drupal theming- A handbook”, Dries Publications
Roger Pressman “Software Engineering”
David mercer “Drupal- Creating blogs, forums, portal and community websites.” ,
Pungeon Publications, cost - 990 INR.
Dries Buytart “Drupa – A complete handbook”, Dries Publications
87
3. About openMalo
We are the leading provider of open source solutions for small and medium businesses
around the world. Our engagements range from complete system implementations on a
LAMP stack including post-production support through state-of-the-art monitoring
centers to performance tuning of a PostgreSQL database.
Through scores of business engagements, we know that a business (your business) can
significantly reduce the total cost of ownership by embracing open source. In several
engagements, open source is really the bridge from nothingness to everything. Simply
put, openMalo is like the ignition key for your car. It jump starts your open source work.
How do we conduct business

openMalo's business philosophy is simple. openMalo exists because our customers trust
us. openMalo prides itself in being more than just a system implementer. We think of
ourselves as your business partners. While this may sound as a cliché, it is, truly, at the
core of what we are, what we do and how we do it. We make sure that you (our customer)
understand the value proposition of any implementation; the hidden costs, the "obvious"
got has and the secret benefits. Customer loyalty is fiercely important to any openMalor.
Every openMalor knows that the majority of the business comes from repeat orders and
recommendations from our customers.
Our engagement model

Our project engagement model is designed to develop a symbiotic relationship with our
customers. We have complete transparency in the engagement model; so that there are
relatively few surprises. This enables us to develop a smooth frictionless relationship; but
more importantly helps us concentrate our energies (and your synergies) in developing a
winning solution for you.
Our MVPs
88
Our most valued assets are our people. We have implicit trust; developed through keen
training and deep insights; in our people. We ensure that openMalo is a fun place to work
and enable openMalor's develop relationships that last a lifetime. We never have "job
openings". However we constantly hire people. People think a hundred times before
leaving openMalo. Invariably, when they leave, they leave thinking “What a great place
to work!".
Our contributions to the open source community

We are very cognizant that our business would not be possible without the tireless effort
of countless developers who pour their heart and soul into developing the best possible
open source software. We use their work to produce a winning solution for our
customers. We give back to the open source community by providing top-of-the-line
content on the usage of their software; absolutely and always free.
Mission Statement
openMalo provides high end technical consulting services for small and
medium business around the world. We provide innovative solutions based on
open source software to our customer. We provide such solutions by
developing a deep and keen understanding of the customer's business.
WE have projects including post-production support through state-of-the-art monitoring
centers to performance tuning of a PostgreSQL database. We focus on delivering quality
solutions.
Services
Our services revolve around building solutions for our customer. We utilize, almost
exclusively, all open source software for building solutions. Our core expertise is in
building solutions. However there are times when we must patch the core open source
software. We contribute these patches back in to the open source community.
Our services are multi-faceted in nature. But all of our services have commonalities. They
are based on a fundamental premise that they deliver significant value for the customer.
89
There are three components in delivering this value: quality, timeliness and budget. We
deliver on all components.
Our services are of two types: (a) time and material and (b) fixed price. We deliver
services on a fixed price basis only when we understand the requirements completely and
when we have done similar work before. Fixed price services can be extremely
productive in certain segments/areas. In certain other areas, they can be detrimental to
delivering value.
We offer several services in various areas. Please feel free to browse through the service
catalog. In different sections. The service catalog is structured to be more meaningful if
you know what you want. If you are looking at technology and technology enablement,
please browse through the technology sections
Domains in which we have expertise
• Drupal
• ZK
• openLaszlo
• Asterisk
• Al fresco
Books
openMalo focuses a lot of energy on producing quality books that are always
free to use. We believe that this symbiotic relationship is a win-win
situation for openMalo and the community at large. OpenMalo instantly
becomes recognized as a de-facto leader in the particular subject and the
community benefits greatly from a free book. The lack of documentation that is easy to
read and use is often overlooked in open source projects. Such lack of documentation
often prevents faster adoption of the particular open source technology. On the other
hand, companies, like openMalo, may have several war-wounds from implementing open
source technologies. The books in openMalo are reflective of the real implementation
90
scenarios and are example driven. .
"Plumbing in Drupal" is openMalo’s first book. It covers Drupal (v5.1), an

open source web based content management product, in depth. Its 350 odd
pages take the reader through various topics in Drupal such as
installation, configuration and advanced development and deployment in
Drupal.
Clients
openMalo has several clients around the world. P3SI is a leading provider of contractors
for Oracle Applications. P3SI had commissioned openMalo to provide an custom
implementation of dotProject and Drupal that works with P3SI needs. openMalo has
provided P3SI with a successful implementation of dotProject and is now coming up with
the integration of dotProject and Drupal.
Foundry Networks®, Inc. is a leading provider of high-performance enterprise and

service provider switching, routing, security, and application traffic management
solutions including edge and backbone Ethernet switches, Web and content-aware
application switches, network-wide security solutions, wireless LAN and access points,
wide area access routers and internet provider edge and service provider core MPLS
routers. We are working with Foundry networks to upgrade and integrate their entire
service and support offering. This will enable Foundry networks to provide better
integrated and timely services with their offerings.
openMalo currently works for an NGO called “CONNECT US”. This NGO works in
order to improve global engagements of US. Connect US is headed by Heather Hamilton
who had worked as secretary of U N President Cofi Annan.
91
4. About UVPCE
Mission :
"It shall be the constant endeavor of the Mehsana District Education Foundation to meet
the educational needs of the youth in the area of professional studies and provide state-of-
the-art learning opportunities along with inculcation of values of professional
commitment and uprightness."
Vision:
“Seek, Search and offer programs those lead to symbiotic emergence of ‘academic
excellence’ and ‘industrial relevance’ in education and research in the field Engineering
and Technology.”
Aim:
Our spirituous efforts are directed towards leading our student community to such an
acme of technical excellence that can satisfy the requisition of the industry, the nation and
the globe at large. The generation of an entirely different community of students aiming
at attaining technical expertise and utilizing the technical know-how in the service of
mankind is at the root of our efforts. We have the following aims before us.
• To offer guidance, motivation and inspiration for full growth of hidden traits
• To impart technical and need-based education by conducting elaborated training
programs.
• To shape and mould the personality of future generation
• To construct fertile ground for resting dire challenges
• To cultivate the feeling of belongingness amongst the faction of engineers
92
Establishment
U.V. Patel College of engineering (UVPCE) situated in Ganpat vidyanagar campus was
established in septmber-1997 under the aegis of Mehsana District Education Foundation
with a view of educating and training young talented students of Gujarat at the field of
engineering and technology to meet the needs of industries in Gujarat and beyond for the
growth of the industries.
The College is named after Shri Ugarchandbhai Varanasibhai Patel, a leading industrialist
of Gujarat, for his generous donation of Rs. 1.25 crores. It is a self-financed institute
approved by All India Council for Technical Education (AICTE), New Delhi, the
Government of Gujarat and North Gujarat University, Patan.
The College is spread over 25 acres of land and is a part of Ganpat vidyanagar Campus. It
has two ultra modern buildings of architectural splendor measuring 6100 sqm. and 2700
sqm., for housing class rooms, tutorial rooms, seminar hall, offices, drawing hall,
workshop, library, well equipped different departmental laboratories, several computer
labs with internet connectivity through 1 Mbps wireless link, satellite link education
center with two-way audio and one-way video link with Gandhinagar etc.
93

Final Reviewed

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Final Reviewed

Hochgeladen von

Copyright:

Verfügbare Formate

Acknowledgment

We are grateful to Mr. K. R. Amin, Head of Computer Department. We would

There remains some name unmentioned, but none remains unacknowledged.

Social networking has added another dimension to ever-fascinating world of

Keywords : drupal , cms , ajax , XHTML , jquery, Web 2.0, Webtop

7 Conclusion and Future work

1. Home (only on internal pages)

Full Site Structure

8. Groups (Members Only)

11. Contact Us (link to Contact Us page in About Us section)

12. My Profile (Members Only)

1. US Foreign Policy Advocates:

2. US Foreign Policy Influencers:

1. US Foreign Policymakers: Congressional, Executive and Presidential campaign

Goal 4: Develop greater coherence and effectiveness among organizations working in

Key Performance Indicators

Other Performance Indicators

5. User Groups and Access

Figure: Drupal’s technology stack

9. Use case diagrams

Scenario1: Mainline Sequence

Scenario2: At step 4 of the mainline sequence

Scenario3: At step 4 of the mainline sequence

Scenario1: Mainline Sequence

Scenario1: Mainline Sequence

Scenario2: At step 4 of the mainline sequence

Scenario3: At step 4 of the mainline sequence

Scenario2: At step 4 of the mainline sequence

Scenario3: At step 4 of the mainline sequence

Scenario1: Mainline Sequence

Scenario2: At step 4 of the mainline sequence

Scenario3: At step 4 of the mainline sequence

Scenario1: Mainline Sequence

Scenario2: At step 4 of the mainline sequence

Scenario3: At step 4 of the mainline sequence

Scenario4: At step 4 of the mainline sequence

Scenario1: Mainline Sequence

Scenario2: At step 1 of the mainline sequence

Scenario1: Mainline Sequence

Scenario2: At step 4 of the mainline sequence

Scenario1: Mainline Sequence

Scenario2: At step 4 of the mainline sequence

Scenario3: At step 4 of the mainline sequence

Scenario4: At step 7 of Scenario3

Scenario1: Mainline Sequence

Scenario 2: At step 3 of the mainline sequence.

Scenario 3: At step 3 of the mainline sequence.

Scenario 4: At step 3 of the mainline sequence.

Scenario1: Mainline Sequence

Scenario2: At step 3 of the mainline sequence

Scenario3: At step 3 of the mainline sequence

Scenario4: At step 3 of the mainline sequence

Scenario1: Mainline Sequence

Scenario 3 : At step3 of scenario 2.

Scenario 4 : At step 3 of mainline sequence.

There are two types of architecture available.

Symbols used in DFD:

1. Process: Here flow of data is transformed.

2. External Entity: A source or destination of data which

3. Data Flow: It is a packet of data. It may be in the form

4. Data Store: Any stored data but with no storing.

Data Flow Diagram: Context Level Diagram- (LEVEL 0)

Give acess level