1. Business Requirements - Google Project Hosting

bossprettyingΔιαχείριση Δεδομένων

28 Νοε 2012 (πριν από 4 χρόνια και 9 μήνες)

209 εμφανίσεις

















Project Document



By Temple Team






Authors:














Version:



Date:





Andrea

Bainbridge

Cladine

Momongan

Colin

Weight

Karen

Mok










V0.3



11 November

2008

Project Documen
tation


Page
2

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

Executive Summary


The scope do
cument outlines ………

Project Documen
tation


Page
3

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

Table of Contents

1.

Business Requirements

________________________________
_________________

5

2.

User

________________________________
________________________________

6

2.1 Profile

________________________________
________________________________
__

6

2.2 Needs

________________________________
________________________________
___

6

2.3 Content d
escription

________________________________
_______________________

6

3.

Recommended Existing CMS system

________________________________
______

7

Description

________________________________
________________________________
_

7

Requirements

________________________________
_______________________________

7

Resources

________________________________
________________________________
___

7

4.

CMS Requirements

________________________________
____________________

8

Hardware

________________________________
________________________________
__

8

Software and operating system requirements

________________________________
_____

8

5.

CMS Enhancement

________________________________
____________________

9

Feature

________________________________
________________________________
_____

9

Layout

________________________________
________________________________
_____

9

Code

9

6.

CMS Site Design Principles

________________________________
____________

10

7.

New CMS Hierarchy Diagram

________________________________
__________

11

8.

Design

________________________________
_____________________________

12

Page design

________________________________
________________________________

12

Navigation design

________________________________
___________________________

12

User instructions

________________________________
____________________________

12

9.

Client Acceptance Testing

________________________________
_____________

13

CMS user interface testing

________________________________
___________________

13

CMS admin interface testing

________________________________
__________________

13

Project Documen
tation


Page
4

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

Introduction


…………………..













Project Documen
tation


Page
5

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

1.

Business Requirements

The Sri Vakrathunda Vinayagar Temple requires a new website that has information
regarding the day to day activities of the temple, including events, newsletters, a
photo
gallery function and information on deities as well as general information on the temple for
visitors to the website.


The purpose of the website is to attract new members and keep existing ones, and to spread
awareness of Hindu temples, different cu
ltures and communities across Melbourne.


Some of the main purposes of the site are to:



Highlight awareness of charitable deeds that the temple participates in



Promote the canteen and it’s uniqueness



Show a map of their location



Display opening times



Provi
de a place where members can download the quarterly news letter



Show photos of recent events


Also, it is important that:



The information on the website is accessible to all members and visitors to the temple



The site content can be maintained and managed
by members of the temple using a
CMS


The purpose of choosing to use CMS to produce the website is to allow the administrators to
update it as and when required. This does not require the administrator to have any
knowledge of HTML or programming. This i
s in contrast to the current site, which requires
the involvement of their web designer even to make small changes.


The temple also has a long
-
term goal of being able to manage members using an online
database and to allow new members to sign up. Content
would then be displayed based on
the users access rights. This is beyond the scope of this project, but these features should
be able to be implemented without much disruption to the new site.

Project Documen
tation


Page
6

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

2.

User


2.1 Profile

The end users of the site are most likely to

be Hindus who are members of the temple or
potential members

of the temple. We should also consider members of the general public who
are interested in Indian culture and the Hindu religion, and may like to attend some events of
visit the temple and it’s
canteen.


Intermediate User: The administrator of the site’s content. The person responsible for
updating the website is unlikely to have experience with HTML and/or programming, and so the
CMS must be simple enough for a non
-
technical user to be able to g
et around.



2.2 Needs


Members and non
-
members will need to access information on the temple such as events and
times, available services, background information on the religion and history of the temple itself.


Intermediate User: Will require a manual t
hat will show them how to update the website.



2.3 Content description

The main body of the content will be provided by the administrators under each of the headings
provided by the navigation pane. Eg: Events, Newsletter. The existing site is to be used
as a
guide for which pages we should create (
http://www.melbournevinayagar.org.au/
).


The overall aim of the content is to encourage people to attend the temple and find out more
information.









Project Documen
tation


Page
7

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

3.

Recommended Existing CMS system

Description


Pixie is an open source content management system written in PHP.


Websites created with Pixie separate the style of the site from the contents. The style of the site
is controlled by Cascading Style Sheet (
CSS). Custom themes can be created with the blank
theme template or by modifying existing themes. Each CSS file is heavily commented to
improve usability.


The site contents, including the site structure and information on individual web pages, are
stored

in a single MySQL database for each website.


Modules and plug
-
ins are extra components for adding functionalities to a basic website.
Examples include events, links, contacts and RSS plug
-
in.


Installation instructions are available on the Pixie website
. A user guide (pdf format) is also
available which describes how to use Pixie.


Requirements



PHP version 4.3.0 and above



MySQL version 4.0 and above



JavaScript enabled brower



Linux/Unix webserver for full functionality (Windows platform may not support

all features)



FTP for file transfer


Resources

Pixie can be download from:
http://www.getpixie.co.uk/

Google Group:
http://groups.google.com/group/pixie
-
cm
s








Project Documen
tation


Page
8

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

4.

CMS Requirements


Hardware

The website is to be hosted on the Swinburne cit3 server. The specifications of the server are as
follows:


Processor

Intel(R) Pentium(R) 4 CPU 1.60GH

Memory

1Gb RAM

Hard disks

/dev/sda 500Gb

/dev/sdb 80Gb



Software
and operating system requirements

Operating system

Linux

Distribution

Fedora Core 7

Linux kernel version

2.6.23.17
-
88

Processor

Intel(R) Pentium(R) 4 CPU 1.60GH

Memory

1Gb RAM

Hard disks

/dev/sda 500Gb

/dev/sdb 80Gb

PHP version

5.2.6

PHP Modules in
stalled

php
-
pear
-
1.5.0
-
3

php
-
bcmath
-
5.2.6
-
2.fc7

php
-
pdo
-
5.2.6
-
2.fc7

php
-
mysql
-
5.2.6
-
2.fc7

php
-
xml
-
5.2.6
-
2.fc7

php
-
debuginfo
-
5.0.5
-
2.1

php
-
pear
-
ole
-
0.5
-
2.2.fc4

php
-
mcrypt
-
5.0.5
-
1

php
-
imap
-
5.2.6
-
2.fc7

php
-
devel
-
5.2.6
-
2.fc7

php
-
gd
-
5.2.6
-
2.fc7

php
-
5.2.6
-
2.fc7

php
-
pear
-
excel
-
0.8
-
1.2.fc4

php
-
mbstring
-
5.2.6
-
2.fc7

php
-
ldap
-
5.2.6
-
2.fc7

php
-
common
-
5.2.6
-
2.fc7

php
-
cli
-
5.2.6
-
2.fc7

Web servers

Apache, lighttpd

Apache version

2.2.8

Databases

MySQL, postgresql

MySQL version

5.0.45
-
6








Project Documen
tation


Page
9

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here


5.

CMS Enhancement


Feature

We have decided to add the functionality for users to create and maintain a photo gallery within
Pixie, as this is currently not catered for and is a highly desired function for the website.


Layout

We will add a new module called galleries_module.php. Thi
s controls the administration and the
viewing of the galleries.


Code

When the administrator adds a new photo gallery using the Pixie admin mode, they will specify a
source folder, which contains an images folder and a thumbs folder. The objective is to get

the
user to upload the main images via FTP to the source folder, and for the CMS to create the
thumbs the first time the gallery is viewed.

When the user clicks on Photo Galleries, the code will loop through all available gallery ids in the
mySQL database
, and then display links to the galleries on the page, with a short description.
When the user clicks on the link, the code will examine the relevant thumbs folder. It will






Project Documen
tation


Page
10

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

6.

CMS Site Design Principles

(approx 1/2 page max)


Summary of the sites desi
gn principles








Project Documen
tation


Page
11

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

7.

New CMS Hierarchy Diagram

(approx 1 page max)











Project Documen
tation


Page
12

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

8.

Design

(approx 1 page max)


Page design





Navigation design






User instructions



Project Documen
tation


Page
13

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

9.

Client Acceptance Testing


CMS user interface testing

Brief instructions using screen shot
s and text







CMS admin interface testing

Brief instructions using screen shots and text



Project Documen
tation


Page
14

of
14


bossprettying_d6c3a098
-
dc21
-
4c83
-
9004
-
d1fc852244b2.doc


Put logo here

Contributions Declaration


The signatures below certify that the project, based upon the requirements identified for ……….
has been completed and the following te
am members contributed as specified



Team Leader

-

………..


Signature ………………………… Date ……/……/….. % contribution to Project ……….




Signature Required


Team Member

-

………



Signature ………………………… Date ……/……/….. % contribution to Project ……….




Sig
nature Required


Team Member

-

………



Signature ………………………… Date ……/……/….. % contribution to Project ……….




Signature Required


Team Member

-

………



Signature ………………………… Date ……/……/….. % contribution to Project ……….




Signature Required


Team
Member

-

………



Signature ………………………… Date ……/……/….. % contribution to Project ……….




Signature Required


Team Member

-

………



Signature ………………………… Date ……/……/….. % contribution to Project ……….




Signature Required