1.Functional Requirements

1.Functional Requirements

a.Security

i.Varied access levels
Roles assigned to user groups. User session receives roles based on group membership at log in. Application checks for roles before granting access to each feature.
Difficulty: Low
Time: 3 hrs

1.Admin/coordinator

a.Full control over the data/layout

b.Assigns users/permissions

2.Designers

a.Basic control over the layout

3.Members

a.Access to individual personal information

b.Interact with other members

c.No access to layout/statistics

4.Data collection

a.Access to the statistics data/none to the layout

ii.Password protected
Passwords associated with users. Check password on log in.
Difficulty: Low
Time: 2 hours

1.Log-in is assigned only by Admin

2.Unique login generation

iii.SSL encryption
Purchase SSL certificate. Put it in place.
Difficulty: Low
Time: 1 hour

iv.¿Personal info will be collect by reseracher/shared amongst users?

v.Database should be encrypted with ¿non-reversible? encryption

vi.Comply with IRB standards

vii.Server Security

1.Unique authorization (not shared admin)
Different user account per server admin
Difficulty: Low
Time: .1 hour

2.Automated patching
Contact host to verify.
Difficulty: Low
Time: .1 hour

3.Anti-virus
Contact host to verify.
Difficulty: Low
Time: .1 hour

4.Firewall
Contact host to verify.
Difficulty: Low
Time: .1 hour

5.Automated data backup
Contact host to verify.
Difficulty: Low
Time: .1 hour

a.Profiles
Difficulty: Medium
Time:

i.Will be...

1.viewable to everyone on the site

ii.Will have... (this must be modifiable by Admin)

1.a name (user-chosen)

2.a picture/avatar

a.RSS feeds
Display content in RSS format.
Difficulty: Low
Time: 4 hours

b.Communication requirements

i.Community wall

1.Public forums (as the wall, or like mini walls?)

a.Text/Links/Documents/Attachments/Pictures

ii.Private messaging
System has private messages that are associated with private conversations. Users create conversations and post messages.
Difficulty: Medium
Time: 2 days

iii.Real-time chat
Difficulty: High
Time: 1 week

1.like a “chatroom” rather than FB chat

iv.News feeds (manually posted by user)

v.Calendar

a.Data/Statistics requirements

i.Data
Admin can select and filter data. Data presented in report form with charts, graphs and tables. Data presented in excel form.
Difficulty: Medium
Time: 1 week

1.Posting counts

2.Calendar activity

3.Messaging counts

4.Time spent in the application

5.“Full analytics”

ii.Evaluated

1.Usage patterns

2.“Full analytics”

iii.Survey collection

1.“Robust” survey creation with “full” integration
AJAX/DHTML form creator.
Difficulty: Hard
Time: 2 weeks

a.Conditional survey options

b.Multiple survey question types

i.Text

ii.Paragraph

iii.Multiple Choice

iv.Checkboxes

v.List

vi.Scale

vii.Grid

2.Dissemination scheduling options
Present survey to user through private message and homepage notification based on certain criteria.
Difficulty: Medium
Time: 1 day

a.#days

b.#posts

c.#calendar activities

d.etc.

a.Accessibility Requirements

i.RSS feeds

ii.Data exporting (all member data “fully accessible” for researchers)

1.“Multiple” file formats

iii.Desktop Interface

1.Modifiable interface

a.Make it aesthetic to different group sets

b.Cross-platform independence

iv.Mobile/Phone Interface
Use CSS to modify website view for mobile browsing.
Difficulty: Low
Time: 1 day

1.Live chat

2.Maintain security standards

a.Support Features

i.Ask the experts
Implement a messaging system similar to private messaging.
Difficulty: Medium
Time: 2 days

1.Email integration

2.Question filtering/forwarding

2.Non-functional Requirements (UI, performance, security)

a.Data/Statistics requirements

i.Data

1.“Full analytics”

ii.Evaluated

1.“Full analytics”

iii.Survey collection

1.“Robust” survey creation with “full” integration

b.Accessibility Requirements

i.Data exporting (all member data “fully accessible” for researchers)

1.“Multiple” file formats

ii.Desktop Interface

1.“Standard”

2.“Easy to read”

3.“Easy to navigate”

4.“Modern”

5.“Dynamic”

a.Different groups will share a community (cops/nurses/etc) but will need to manage these groups concurrently.

iii.Mobile/Phone Interface

1.Maintain security standards

2.Operating environment and constraints

3.Security, Safety, IP, and Tech considerations

4.Market and literature (survey similar products and articulate the uniqueness of the proposed product/system)

a.This proposed project should be similar to current social networking sites (ie Facebook) with a few specific differences.

b.This is for a private group that is controlled via an administrator.

c.Research is a primary goal. We want to be able to track how user interaction with this site affects behavior.

d.There is a behavior that this network is currently based upon. Initially our project is designed for female police officers and cardiovascular health.