3. System Features - Oregon State University

terrificbeepedMobile - Wireless

Dec 10, 2013 (3 years and 8 months ago)

91 views

Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.


Beaver Tracks

Software Requirements Specification


Version 1.0

Prepared by Kim Griggs

OSU Libraries

3/4/10
Software

Requirements Specification for <Project>


Page
ii


Table of Contents
1.

Introduction
................................
................................
................................
................................
.....
1

1.1

Purpose

................................
................................
................................
................................
..............

1

1.2

I
ntended Audience and Reading Suggestions

................................
................................
............

1

1.3

Project Scope

................................
................................
................................
................................
....

1

1.4

References

................................
................................
................................
................................
........

2

2.

Overall Description

................................
................................
................................
........................
2

2.1

Product Perspective

................................
................................
................................
.........................

2

2.2

Product Features

................................
................................
................................
..............................

2

2.3

User Classes and Characteristics

................................
................................
................................
..

3

2.4

Design and Implementation Constraints

................................
................................
.......................

3

2.5

User Documentation

................................
................................
................................
........................

4

2.6

Assumptions and Dependencies

................................
................................
................................
...

5

2.7

Operating Environment
................................
................................
................................
....................

5

3.

System Features

................................
................................
................................
...........................
5

3.1

Welcome Page

................................
................................
................................
................................
.....

5

3.2

List of N
earby Sites

................................
................................
................................
.............................

6

3.3

List of Historical Sites

................................
................................
................................
.........................

7

3.4

Map of Historical Sites

................................
................................
................................
........................

8

3.5

Historical Site Page

................................
................................
................................
.............................

8

3.6

Historical Image Detail Pag
e

................................
................................
................................
.............

10

3.7

Enlarged Image Page

................................
................................
................................
.........................

10

3.8

Search Sites

................................
................................
................................
................................
.......

11

3.9

Historical Site Tour Information Page

................................
................................
..............................

12

3.10 About Project Page

................................
................................
................................
.............................

12

4

External Interface Requirements

................................
................................
..............................
13

4.10

User Interfaces Requirements

................................
................................
................................
...

13

4.10.1

Style Guide

................................
................................
................................
................................

14

4.11

Hardware Interfaces

................................
................................
................................
....................

15

Device Support

................................
................................
................................
................................
.........

15

Browser Support

................................
................................
................................
................................
.......

15

4.12

Software Interfaces

................................
................................
................................
......................

16

5

Other Nonfunctional Requirements

................................
................................
..........................
16

5.10

Security Requirements

................................
................................
................................
................

17

5.11

Software Quality Attributes

................................
................................
................................
.........

17

6

Tests

................................
................................
................................
................................
..............
17



Revision History

Name

Date

Reason For Changes

Version

Kim

3/11/10

Went over with team and finalized some
decisi
ons.

1.1







Software

Requirements Specificati
on for BeaverTracks


Page
1


1.

Introduction

1.1

Purpose

The software described in this document is the BeaverTracks Living History Tour mobile
web application and supporting software,
http://tour.library.oregonstate.edu
/

and
http://tour.library.oregonstate.edu/admin, version 1, created spring of 2010.


BeaverTracks Living History Tour mobile application will enable current students, staff,
parents, alumni, and the local community to explore OSU’s campus history using a

location aware map
-
based interface on their smartphone mobile devices. The
BeaverTracks administration tool will enable admins to easily add historical sites to the
tour.

1.2

Intended Audience and Reading Suggestions

Primary readers of this document are the
designers, developers, team members and
stakeholders of this project. Secondary readers are administrators or people interested in
the project.


Contributors to this document are the members of the beaverTracks team.


The following document contains the f
unctional, user and design requirements for
BeaverTracks application and supporting software, as well as user manuals, project
information and planning.


Depending on familiarity with the project, all readers should start with section 1.4, skip to
section

2.1, 2.2, 2.3, skip to section 2.6.


Suggested Reading Sequence per reader:


Designers: Sections 2.4, & 4

Developers: Sections 2.4, 3, 4, & 5

Project Team: Appendix C

Admins: Appendix A

Users: Appendix B

1.3

Project Scope

The scope of the BeaverTracks Living
History Tour (beaverTracks, BT) mobile web
application is to provide a location
-
based tour of OSU’s campus using OSU Archives’
historical images. This version of the project will feature the 22 sites from the Oregon
State University Walking Tour, developed

by Facilities Services.


The BeaverTracks application will enable users to find historical sites of interest on OSU’s
campus by searching for a site, viewing the sites on a map, or by browsing sites by name;
each site will have multiple historical images

sourced from OSU Archive’s digital
collections, historical information about the site and details about each image. Users will
Software

Requirements Specificati
on for BeaverTracks


Page
2


also be able to find sites near them or near another site, as well as follow a directions
-
based walking tour of the sites.


The
goal of beaverTracks is to showcase and bring attention to the Libraries’ digital
collections, as well as a new and innovative approach for connecting with current students,
staff, parents, alumni, and the local community. This project is an outreach effor
t in line
with the larger OSU move toward using social software to interact with the campus
community.


Benefits of the project should include:

1.

New access point to Archives’ digital collections.

2.

Historical information about OSU campus location

3.

Location ba
sed walking tour of OSU campus


The main audience of this version is users on a smartphone (iPhone, Android, Palm Pre)
or those on a device with a geo
-
aware browser (safari, FF 3.5+, Chrome)


1.4

References

MobileLib Project Requirements

OSU and OSUL Web Requi
rements

2.

Overall Description

2.1

Product Perspective

Inspired by the WolfWalk project at North Carolina State University, BeaverTracks is a
new self
-
contained OSU Libraries’ project. BeaverTacks interfaces with the MobileLib
project, and therefore shall adhere

to some of the MobileLib requirements, unless noted
differently in this document.

2.2

Product Features

Major Features




List of Historical Sites




Map of Historical Sites



Sites Nearby User

o

Nearby List

o

Nearby Map



Search Historical Sites

o

Search Results list



Hist
orical Site Page

o

Image Detail Page



Image Page

o

Tour Directions Page

o

Sites Nearby



Nearby List

Software

Requirements Specificati
on for BeaverTracks


Page
3




Nearby Map





Minor Features:



Home Page



Historical Tour Information Page


Admin Features




Edit Historical Sites



Add Historical Sites



Delete Historical Site




2.3

User C
lasses and Characteristics

There are four types of users: mobile, non
-
mobile, off
-
site, and administrators.


The project’s main audience is mobile users on OSU campus. These users are typically
current students, staff, parents, alumni, and the local commun
ity. These users will be able
to use all the features of the project.


Secondary users are non
-
mobile users. These users are on
-
campus but not on a mobile
device. They will be able to use all the features, but features such as the walking tour will
have l
ittle importance to these users as they are stationary.


The least important user, are those off
-
site, mobile or not. For these users most features
will either not work, such as the location
-
based features, or not make sense for their
context, such as the

walking tour.


Note: It is assumed, mobile users are on one of the supported devices, and non
-
mobile
users are on one of the supported browsers.


Admin users are typically on a non
-
mobile device and only interacting with the admin
interface.




2.4

Design a
nd Implementation Constraints

Implementation Constraints


Programming Languages: Ruby on Rails, AJAX, XHTML, CSS 3


Code



Code shall be valid XHML & CSS



Code shall follow OSU/OSUL standards and requirements



Code shall be re
-
usable, well commented, compati
ble and extendable.

Software

Requirements Specificati
on for BeaverTracks


Page
4



Database:


MySQL


Technical Constraints




Individual resource files must be less than 10 MB



JavaScript execution time is limited to 10 seconds



Avoid using Flash and Java



iPhone

blocks pop
-
up windows by default (user preference).



Geo Location supported browsers



CSS3 supported browsers



Android, Palm constraints…



Design Constraints




Maximum size for decoded GIF, PNG, and TIFF images is 2 megapixels



OSUL and MobileLib design requirements



Screen size: 320x480



Style Guide will be crea
ted & maintained


Software Dependencies




Flickr API




Google Maps API



Gems: GeoKit, YMYR/GM, Flickr
-
fu, …


Interfaces


OSU Libraries Mobile Website

Look and feel should follow mobileLib requirements and will be joined through links on
both systems


2.5

User Doc
umentation

See Appendix A & B: User and Admin Manual

Software

Requirements Specificati
on for BeaverTracks


Page
5


2.6

Assumptions and Dependencies

This project is dependant on the Google and Flickr API, the use of flickr to store Archive’s
images and the supporting staff to develop and maintain it.


It is assumed Flick
r and Google will continue supporting their free APIs, and OSU
Libraries will continue the upkeep of the API keys.


It is assumed OSU Libraries Archives will continue the use of Flickr to host historical
images.


It is assumed OSU Libraries Archives will
continue to support staff and resources needed
to maintain and build this project.


It is assumed OSU Libraries ETS staff and resources will continue to support development
and hosting of the project.


2.7

Operating Environment

BeaverTracks is an extensio
n of the OSU Libraries site e.g. osulibrary.oregonstate.edu. It
is hosted on a Unix platform with an Apache server.


The web application is intended for smartphone mobile devices.


The admin interface is a standard web application that will operate on any

of the major OS
and browsers.


3.

System Features

3.1

Welcome Page


3.1.1

Description and Priority


BeaverTracks historical tour home page

Med/Low Priority


P1: The page includes a search box, a link to browse sites, a link to see sites
on a map, a
nd a link to take the tour. The homepage initiates the geo
-
location
features of the site by setting the users current location. If location is found
home page includes link to sites nearby user


P2: Page includes logo and info about the site.


3.1.2

Stimul
us/Response Sequences


Software

Requirements Specificati
on for BeaverTracks


Page
6


1.

User visits BeaverTracks home page

2.

BeaverTracks asks the user if it can find the user’s location

3.

User confirms

4.

BeaverTracks stores the user location and finds the 3 nearest sites to
the user.

5.

BeaverTracks responds with updated home

page with link to sites
nearby



3.1.3

Functional Requirements

REQ
-
1:

Get User’s location.

Depends: geo
-
location feature to be able to find a user


1

Check for user, if user skip to 2.3

2

Ask User for permission, if no skip to 2.4.2

2.1

Create user

2.2

Use Geolocati
on scripts to locate user.

2.3


If user

2.3.1

check if user is within 1 mile of the campus. If yes

2.3.1.1

update location.

2.3.1.2

Update home page (req
-
2)

2.3.2

No? Respond: Can not set your location. Try again later

2.3.2.1

Return to home page

2.4

User can not be found

2.4.1

Respond: Can not set yo
ur location. Try again later

2.4.2

Return to home page


REQ
-
2 (optional): Update Page with link to sites nearby

Assumes: User is within 1 mile of a site so we can depend on there being sites

Requires: User to accept geolocation script


1.

Build Ajax Response to upd
ate home page with a link to nearby site based on user
location

3.2

List of Nearby Sites

3.2.1

Description and Priority

The historical sites nearby a user or a building, listed on a map and by name


Med Priority



3.2.2

Stimulus/Response Sequences



User clicks on lin
k to browse sites nearby

o

Can be on home page or on a Site Page



BT responds with a list of links to the 3 nearest sites by A
-
Z, sorted by name

Software

Requirements Specificati
on for BeaverTracks


Page
7




BT responds with a the sites placed on a map with markers that includes name,
description and link to site page.


3.2.3

Functional Requirements

REQ
-
1:

Get 3 nearby sites

Requires: user location or building location

Depends: distance calculations and geolocation information for user/site and nearby sites.

Assumes: A user’s or building location is passed in.

Assumes
: we can always find 3 nearby sites


1.

No site or user location

1.1


Create user and get location. See 3.1 REQ 1, except return to nearby sites page

2.

If user?

2.1

Check and update location

3.

Else if site?

3.1

Update user location with site location

4.

Find three closest site
s based on distance to the user’s location

4.1

Store site ids in session


REQ
-
2: Build Page


1.

Build markers for sites

2.


Build marker of the current location


styled differently

3.

Build map for sites

4.

Return map and markers

5.

Build URL to site’s page

6.

Display links

3.3

Li
st of Historical Sites

3.3.1

Description and Priority

The historical sites listed by name, A
-
Z


High Priority



3.3.2

Stimulus/Response Sequences



User clicks on link to browse sites from home page



BT responds with a list of links to all the sites by A
-
Z, s
orted on site name

3.3.3

Functional Requirements

REQ
-
1:

A
-
Z list

Depends: Sites added correctly


1.1

Collect list of all sites sorted by name

1.2

Build URL to each site’s page

1.3

Display links

Software

Requirements Specificati
on for BeaverTracks


Page
8




3.4

Map of Historical Sites

3.4.1

Description and Priority

The historical si
tes placed on a map with markers that include name, description
and link to site page.


High Priority


3.4.2

Stimulus/Response Sequences



User clicks on link to map sites from the home page



BT responds with a campus map with all the historical sites place
d on it



BT responds with a marker for each site placed on map that include the name,
shorten description, and link to the site page.

3.4.3

Functional Requirements

REQ
-
1:

Get Sites

Depends: Sites added correctly


3.5

Collect list of all sites

3.6

Build marker info
rmation for each site

3.6.1

Includes title, description, and link to site page

3.6.1.1

Build site page url



REQ
-
2:

Build Map

Requires: Campus bounding location and zoom point

Requires: Google Map API and key

7.

Build Map

7.1

Place markers on map

7.2

Return map


REQ
-
3: Build Page

1.

Add Map with markers

2.

Add List of links to site

2.1

Add link back to home


3.5.0

Historical Site Page

3.5.1

Description and Priority

P1: The site’s page contains an image, the name and description of the site and
thumbnails of the site’s historical images.


P2: Link

to nearby page

Software

Requirements Specificati
on for BeaverTracks


Page
9





P3: Link to walking directions on tour



P1: High Priority

P2: Medium

P3: Low


3.5.2

Stimulus/Response Sequences



User clicks on link to site page

o

Could be from list of sites, map of sites, or nearby list or map



BT responds with
a page of the site’s image, title and description



BT responds with a list of thumbnail images for the site, listed from oldest to
newest by year.



BT responds with a link to nearby sites to the site



BT responds with a link to the tour’s walking directions


3.5.3

Functional Requirements

REQ
-
1:P1

Get Site

Depends: Sites added correctly


1.

Get site

2.

Return site image, title, truncated description, year,


REQ
-
2:P1

Get Site images

Requires: Site’s flickr tag

Requires: Flickr Map API and key

Depends: Images added co
rrectly to flickr


1.

Get site tag

2.

Search archive’s flickr account for images tagged with site tag

3.

If images

3.1

Return list of images

3.1.1

For each image, store medium and large image url and description

4.

No image

4.1

Return no image flag


REQ
-
3:P1 Build Page


1.

Display si
te information and image

1.1.

Link image to image page

2.

Display thumbnail images

2.1.

Link thumbnail images to image detail page

2.1.1.

Build Ajax response to update site information with image details

3.

Add link back to home

Software

Requirements Specificati
on for BeaverTracks


Page
10




REQ1:P2 Build Nearby Link

Requires: Site locati
on

1.1

See 3.12 REQ1 and REQ2

1.2

Add link to Page


REQ1:P3 Build Walking Directions

Depends: Tour directions

Requires: Starting site and next site



3.6

Historical Image Detail Page

3.6.1

Description and Priority

The details of a site’s image which contains the
description and link to enlarged

image.


High Priority


3.6.2

Stimulus/Response Sequences



User clicks on a thumbnail image from the site’s page



BT replaces the site’s image with the medium sized clicked on image



BT replaces the site’s description with th
e clicked on image description

3.6.3

Functional Requirements


REQ
-
1:

Get Image

Depends: Images retrieved from flickr

Requires: Image urls and description


1.

Ajax request returns link to small and large image url and image description


REQ
-
2:

Update Site page

Requires: image information

Requires: Javascript support

Depends: Prototype API


1.

Replace site image and description with image and image description

1.1

Build link to enlarged image view

1.2

Add link to image


3.7

Enlarged Image Page

3.7.1

Description and Priority

Software

Requirements Specificati
on for BeaverTracks


Page
11



A

site’s enlarged image


Low Priority


3.7.2

Stimulus/Response Sequences



User clicks on the main image on the site’s page



BT responds with a an enlarged version of the image



BT responds with a link back to site page

3.7.3

Functional Requirements

REQ
-
1:

Get

Image

Depends: Images retrieved from flickr

Requires: Image url


1.

Display enlarged image with zoom set to true.

2.

Display link back to site page



3.8

Search Sites

3.8.1

Description and Priority


Search for a site by building name, description


Med Priority


3.8
.2

Stimulus/Response Sequences



User enters a search term into the search box from the home page



BT responds with suggestions after 3 characters



User submits query



BT responds with a list of links to sites that match user’s query

3.8.3

Functional Requireme
nts

REQ
-
1:

Build Search Engine

Depends: Sites added correctly

Requires: Search form added to home page

Assumes: JQuery support


1.0

Search by site name, description

2.

build auto
-
suggest


REQ
-
2:

Return Search Results

Requires: Search engine

Software

Requirements Specificati
on for BeaverTracks


Page
12


1.

If results

1.1

Return lis
t of links to sites

2.

No Results?

2.1

Return No Results message

3.

Add link back to home



3.9

Historical Site Tour Information Page

3.9.1

Description and Priority

Information page about the walkng tour, including how to and a link to the campus

map


Low Priority


3.9.2

Stimulus/
Response Sequences



User clicks on link to Walking Tour



BT responds with walking tour page

3.9.3

Functional Requirements

REQ
-
1:

Build Walking tour page

Depends: Walking directions added to sites

Requires: About Content


3.10

Add about content

3.11

Add how to content

3.12

Add li
nk to campus map

3.13

Add link back to home


3.10 About Project Page

3.10.1

Description and Priority

Information page about the beaverTracks project


Low Priority


3.10.2

Stimulus/Response Sequences



User clicks on link to About



BT responds with about page

3.10.3

Functional Requirem
ents

REQ
-
1:

Build about page

Requires: About Content

Software

Requirements Specificati
on for BeaverTracks


Page
13



3.11

Add about content

3.12

Add link back to home


4

External Interface Requirements

4.10

User Interfaces Requirements



Device Guidelines


Opera Guidelines:


http:/
/dev.opera.com/articles/mobile/


iPhone Human Interface guidelines:

http://developer.apple.com/iphone/library/docume
ntation/UserExperience/Conceptual/Mob
ileHIG/Introduction/Introduction.html


Palm Pre Guidelines:

http://developer.palm.com/index.php?option=com_content&view=article&id=1606


Webkit Guidelines:


http://developer.apple.com/safari/articles/cssrecipes.html

http://developer.apple.com/
safari/library/documentation/AppleApplications/Reference/Safa
riCSSRef/Articles/OtherStandardCSS3Features.html


CSS 2.1 specifications:

http://www.w3.org/TR/CSS21/


Template Requirements





Each template shall in
clude a style optimization for the iPhone, Android, Palm and
Opera



Each template shall include:

o

Header

o

Footer

o

Link Back



Each template shall adhere to style guide lines


Information Template



Welcome Page



Walking Tour Page



About Project Page


The information

template is a mixture of text areas and navigation links.


o

Large Header

o

Text areas shall be in a rounded box

Software

Requirements Specificati
on for BeaverTracks


Page
14


o

Links shall use an edge to edge design



General Template



Campus Map



Enlarged Image Page


The general template is for large images and maps


o

Small

header

o

Page Title

o

Image (max width 80% of screen)



Site Template



Site Page



Detail Page


The site template is a mixture of images, text and image links

o

Small header

o

Page Title

o

Rounded Box




Small Image (max width 50% of screen)



Wrapping Text (surrounds sma
ll image)



Link To Nearby Sites

o

Edge to edge



Poliroid image links



Image title and year



No curser


List Template



Search Results



Site List Page


The List Template is a list of links

o

Edge to edge design



Nearby Template



Nearby Page


The Nearby Template is
a mixture of an map and navigation links

o

Small header

o

Medium image



Max width 80%



Max height 50%

o

Links



Edge to edge

4.10.1

Style Guide

Colors Schema:

#333

Software

Requirements Specificati
on for BeaverTracks


Page
15


#fff

#E55302

#
EE9944

#000

# D9D9D9


H1: #000, 20px

H2: #333, 18px

H3: #000, 17px



Links:

Active: #E55302

Vis
ited: #
EE9944



Rounded box

Background: #333

Box: #fff

Border: #E55302


Font

Helvetica

#000, 17px

Normal


Edge to Edge


Font: 20px, #333


Border:
# D9D9D9


Background: #000




4.11

Hardware Interfaces

Device Support



iPhone, iTouch, iPad



Android phones



Palm Pre



Opera Phones (blackberry, )

Browser Support

Web Browser

Geolocation API support

Mozilla Firefox

supported in
Firefox 3.5

and later versions.

Chrome

Supports thru
Google Gears Geolocation API

Opera

Supported in nightly builds


download from this page

Safari

Support includes the IPhone’s Safari browser 3.0+.

Software

Requirements Specificati
on for BeaverTracks


Page
16


In
ternet Explorer

An experimental support available from IE8.


4.12

Software Interfaces


Google Maps API

http://code.google.com/apis/maps/


Key
:

See /config/gmaps_api_key.yml


Google Maps is accessed through the

YM4R/GM library, version 0.4.1.
The library
requires a Google API key to be passed in. The Library

facilitates the use of
Google

Maps
to build maps and markers of the historical sites within the application.


YM4R/GM library
:

http://ym4r.rubyforge.org/ym4r_gm
-
doc/


Geo
-
location API

http://dev.w3.org/geo/api/spec
-
source.html


The geo
-
location API is used to find a user’s location. The user’s
location is used to
display nearby sites.


Flickr API

http://www.flickr.com/services/api/


Key and secret
:
See /config/flickr.yml

Archives User ID:
27497198@N08


The Flickr API is accessed through the
F
lickr_fu gem
. The gem requires an API key and
secret to be passed in. The gem uses Flickr’s REST API for searching and finding images.
The search call requires Archives user id to be passed in.


Flickr_fu: http://github.com/commonthread/flickr_fu


Archive
s Flickr Account

http://www.flickr.com/photos/osuarchives/


The Archive’s Flickr account hosts all the images used in the application.


Database

MySQl Cluster: tour_prod, tour_test, tour_dev


The
database schema manages the sites, the user’s location, and admin accounts



5

Other Nonfunctional Requirements


Software

Requirements Specificati
on for BeaverTracks


Page
17


5.10

Security Requirements

No personal data about a user is stored. User location information is deleted nightly via a
cron job.


Project admins will

need to be authorized before they can use the admin interface to
manage the sites in the project.


Standard web security measure shall be implemented.

5.11

Software Quality Attributes

This project should be easily extendable, maintainable and able to be releas
ed as an
open
-
source project. Future thought should go into enabling project to be extending
beyond the campus context.


Features to fulfill these requirements include:




An admin interface to easily add sites



Training documents to easily add images



A RE
ST
-
ful code base to enable an API



A MVC code base to enable maintainability



A templating system to enable a non
-
mobile interface



Automated Tests to ensure correctness



Manual Tests to ensure standards



User tests to ensure usability


6

Tests

6.10


Functionality and

Standards

Standards


CSS Standards Tests: Must pass tests for CSS 2

XHTML Standards Tests: Must pass test for XHTML transitional

MobileOK Test: Must score a 4

Mobile Readiness Test: Must score a 90


Functionality


Unit tests must pass for every action

Fun
ctional Tests must pass for every class

Manual Tests must pass for every case

Software

Requirements Specificati
on for BeaverTracks


Page
18


6.11


User Tests


Heuristics Examination

Evaluation performed by Usability Experts


User Testing

Usability testing with users

Software

Requirements Specificati
on for BeaverTracks


Page
19


Appendix A: User Manual

Appendix B: Admin Manual

Historic
al Site Creation

Site Requirements



Name:

The name of the site. This information comes from the historical walking tour
pamphlet.



Description:

A description of the site. This information comes from the historical
walking tour pamphlet.



Flickr URL:

The URL
to the flickr address for the main image of the site. See
instructions below. This is the same image from the pamphlet.



Flickr Tag:

A unique tag that will be used to tag flickr images for this site. The tag
shall be a combination of the site name (all one
word with dashes) and the word Tour
(example: Site name is Benton Hall. Tag with: Benton
-
Hall
-
Tour)



Latitude:

The latitude of the site. See instructions below



Longitude:

The longitude of the site. See instructions below

Get Flickr URL

1

Navigate to the image

on Flickr (example:
http://www.flickr.com/photos/osuarchives/4362164297/
)

2

Click on ‘All Sizes’ link above image

3

Click on the Small Size

4

Right Click on Image

5

Select ‘Copy Image Location


6

Paste into Flick URL box

Software

Requirements Specificati
on for BeaverTracks


Page
20


Get Latitude & Longitude

1.

Go to:
http://m.oregonstate.edu/buildings

2.

Find Site and click on link

3.

Right Click on Orange Marker

4.

Select Properties

5.

Under Address, find value ‘center=’

6.

Copy first number into Latitude and second number into Longitude

Example:

Building Benton Hall: http://m.oregonstate.edu/building/12

Address=
http://m.oregonstate.edu/map?cent
er=44.566216721,
-
123.274284785

center=44.566216721,
-
123.274284785

Latitude = 44.566216721

Longitude =
-
123.274284785

How
-
to Add Sites

1.

Login to:
http://tour
-
dev.library.oregonstate.edu/admin

2.

Cl
ick on Buildings Tab

3.

Click On ‘New Building’ Link

4.

Enter Site Requirements

5.

Click on Create Building

How
-
To Edit/Delete Sites

Software

Requirements Specificati
on for BeaverTracks


Page
21


1.

Click on Site Name

2.

Click on Edit Building Link

3.

To Edit, change information and Save

4.

To Delete, click on Delete Building Button


Fli
ckr Instructions

Image requirements



Image must be uploaded to Archive’s Flickr account



Image must be set to Public



Image title shall be building name and year (Example: Benton Hall, 1905,
Administration Hall, 1889)



Image description shall describe the imag
e and not repeat the site description.
(Description shall not include links and shall not be empty).



Image shall be tagged with site tag



Image shall have date taken set to be the building year

How to mange Site Images

Images are linked to a site via the

site’s unique tag.



To add images to a site you must include the site’s tag to the flickr image’s tags.



To remove an image from a site, remove the tag from the flickr image or from the
Archive’s flickr account.

Appendix C: Project Plan


Software

Requirements Specificati
on for BeaverTracks


Page
22


Timeline and
Methodology



Date

Mileston
e (MS)

Goal

Depends on

Req.
Resources/Peopl
e

Outcome

3/10

1

Development and Production
Infrastructure

ryan

Ryan

Dev and
production env
and code repos

3
/

2

Functionality and requirement list

Kim

Kim and BT team

This document


3

Add the 22 sites via the admin
interface

=
P⼱9
=
q楡i
=
q楡iⰠwa汫lng⁴ou爠
do捵men琬=
瑲t楮楮g=
do捵men琬⁡dm楮i
楮ie牦a捥
=
qhe⁳楴=猠sdded=
瑯⁴he⁤a瑡ba獥
=
=
4
=
Add‴
-
U⁩=age猠so⁦汩捫爠co爠ra捨=
獩瑥=

=
P⼲R
=
q楡iⰠjp″
=
q楡iⰠ業age猬s
瑲t楮楮g⁤o挬c
=
qhe⁩=age猠

ded⁴o⁦汩捫c
=
=
R
=
䥭p汥len琠䡩gh⁐物o物瑹=
牥ru楲emen瑳
=
h業
=
h業Ⱐ剥o=
do捵ment
=
ja楮i
牥ru楲emen瑳t
f楮楳ied
=
=
S
=
䥭p汥len琠jed⁐物o物瑹=
牥ru楲emen瑳
=
h業Ⱐjp‵
=
h業Ⱐ剥o=
do捵ment
=
jed極i=
剥ou楲emen瑳t
f楮楳ied
=
=
T
=
mo汩獨⁵獥爠rn瑥牦a捥⁦o爠rob楬e=
獩瑥⁡nd⁣牥a瑥⁳=
y汥lgu楤i汩nes
=
-
4⼵⼱M
=
h業
=
h業Ⱐ䝲dph楣i
de獩sne爬⁂q=
瑥amⰠ啳敲r
楮ie牦a捥=
牥ru楲emen瑳
=
啉⁤e獩sn†
f楮楳ied⸠p瑹汥l
gu楤i汩nes
=
=
U
=
䥭p汥len琠iow⁰物o物瑹=
牥ru楲emen瑳t
-
4⼱S
=
h業Ⱐjp‶
=
h業Ⱐ剥o=
do捵ment
=
A汬⁲=qu楲emen瑳t
f楮楳ied
=
=
9
=
Add⁣=n瑥n琠and⁰o汩獨=be
汳l
-
4⼱S
=
h業Ⱐjp‸
=
Bq⁴eamⰠ捯n瑥n琠
ou瑬楮t
=
啉⁦楮楳ied
=
=

=
qe獴sw楴i⁵獥牳†
-
4⼱9
=
h業ⱍ匠N
-
9
=
Bq⁴eamⰠr
-
qeamⰠu獥牳Ⱐr獥爠
瑥獴
=
App⁔e獴sd⁷楴i=
u獥牳
=
=

=
䙩x⁩獳=e猠snd⁩瑥牡瑥n⁍匠NM=

=
4⼳M
=
h業Ⱐjp‱M
=
h業Ⱐu獥爠瑥獴s
牥獵汴l
=
啳敲⁴e獴s楳獵i猠
f楸ed
=
=

=
Add楮欠瑯ob楬e⁳楴==

=
R⼳⼱M
=
h業Ⱐjp‱N
=
h業Ⱐg牡rh楣i
de獩sne爬⁩捯n
=
Bq楮步d⁦牯r=
mob楬e⁳楴=
=
=
N
P
=
m牥獳r牥汥a獥=

=
R⼳⼱M
=
iau物eⰠjp‱N
=
Bq⁴eamⰠp牥獳r
牥汥a獥
=
Bq⁡nnoun捥d⁴o=
捡mpu猠so爠
䡩獴s特on瑨
=
Software

Requirements Specificati
on for BeaverTracks


Page
23









Issues


MSMS

Responsible

Issues

New Date

1




2