Embed Size (px)
Citation preview
Drexel University and Unisys Corporation
System Requirement Specifications UniConf – Winter 2012
Jedidiah Weller
MeiZhi Li Phil Trinh
Ross Bower Sajal Desai
UniConf 2/1/2012
2 |UniConf
Table of Contents
Revisions ................................................................................................................................................. 5
1. Introduction..................................................................................................................................... 6
1.1. Purpose ...................................................................................................................................... 7
1.2. Scope .......................................................................................................................................... 7
1.3. Priority Levels ............................................................................................................................. 7
2. Document Layout ............................................................................................................................ 7
2.1. Main Features ............................................................................................................................. 7
2.2. User Roles ................................................................................................................................... 8
3. GUI Layout ....................................................................................................................................... 8
3.1. Login View .................................................................................................................................. 8
3.2. Main View................................................................................................................................... 9
3.3. Presentation View ..................................................................................................................... 11
3.4. Documents View ....................................................................................................................... 12
................................................................................................................................................. 13
3.5. Chat View ................................................................................................................................. 14
3.6. Scheduling View ........................................................................................................................ 16
3.7. Event View ................................................................................................................................ 18
3.8. Notification View ...................................................................................................................... 18
................................................................................................................................................. 19
3.9. Administrative View .................................................................................................................. 20
3.10. User Controls View ................................................................................................................... 21
3.11. Device Settings View ................................................................................................................. 22
4. Presentations................................................................................................................................. 23
4.1. Presentations ............................................................................................................................ 23
4.2. Surveys ..................................................................................................................................... 23
4.3. Scheduling ................................................................................................................................ 23
4.4. Tablet view ............................................................................................................................... 24
4.5. Phone view ............................................................................................................................... 24
5. Document Sharing ......................................................................................................................... 24
3 |UniConf
5.1. Files .......................................................................................................................................... 24
6. Scheduling ..................................................................................................................................... 24
6.1. Reservations ............................................................................................................................. 24
6.2. Rooms ...................................................................................................................................... 25
6.3. Events ....................................................................................................................................... 25
7. Communication ............................................................................................................................. 25
7.1. Chat Features............................................................................................................................ 25
7.2. Settings Panel ........................................................................................................................... 25
7.3. Personal Messaging .................................................................................................................. 25
7.4. Notification Features ................................................................................................................ 26
8. Administrative Features ................................................................................................................. 26
8.1. General ..................................................................................................................................... 26
8.2. User accounts ........................................................................................................................... 26
8.3. Location .................................................................................................................................... 26
8.4. Alerts ........................................................................................................................................ 26
8.5. On/Off Features ........................................................................................................................ 26
8.6. Chat Logging ............................................................................................................................. 27
9. User Roles...................................................................................................................................... 27
9.1. Guest/Audience ........................................................................................................................ 27
9.2. Registered User ........................................................................................................................ 27
9.3. Door Account ............................................................................................................................ 27
9.4. Admin ....................................................................................................................................... 27
10. Supported Platforms .................................................................................................................. 28
11. Update Characteristics ............................................................................................................... 28
12. Installation Requirements .......................................................................................................... 28
12.1. Client ........................................................................................................................................ 28
12.2. Server ....................................................................................................................................... 29
13. Glossary ..................................................................................................................................... 29
14. Appendix A – User Permissions .................................................................................................. 31
15. Appendix B – Priority Tracking.................................................................................................... 32
15.1. High Priority Tasks .................................................................................................................... 32
15.2. Medium Priority Tasks .............................................................................................................. 33
4 |UniConf
15.3. Low Priority Tasks ..................................................................................................................... 33
5 |UniConf
Revisions
Revision Date Committed by Comments
1.0 01/31/2012 Phil Trinh,
Jedidiah Weller Initial SRS with Formatting and all parts present
1.1 2/2/2012 Jedidiah Weller Made revisions based upon advisor feedback
1.2 2/6/2012 Ross Bower Added GUI Diagrams
2.0 2/7/2012 Entire Team Completed documented. Made all consistency, GUI, and requirement changes as requested
2.1 2/21/2012 Entire Team Updated SRS functional requirements to match the features we are actually implementing in the design document
2.2 4/29/2012 Entire Team Updated SRS to match priority changes from start to finish. Updated SRS to match changes to the Design Document
6 |UniConf
1. Introduction
1.1.Overview The popularity of mobile devices has created a unique opportunity for collaboration at conferences and presentation settings. Powered by Unisys ePortal technology, UniConf provides a unified and user friendly interface to allow conference hosts to better communicate with their audiences. UniConf achieves this by targeting the core features shared across every conference structure: Presentations, Communication, and Information sharing. Inside of a conference setting, UniConf allows users to view presentations, share documents, communicate with the presenter and other audience members, and provide feedback to the presenter.
7 |UniConf
1.2. Purpose The purpose of this document is to provide a detailed specification and requirements list
for the “UniConf” application. This document describes in detail the functionality that
UniConf possesses as well as the context in which that functionality is presented.
1.3. Scope
The scope of this document is laying out all requirements for the beta version of UniConf
as well as guiding the team to produce the acceptance test plan which is mandatory to
make UniConf deliverable.
1.4. Priority Levels
High: High priority defines requirements that are necessary for the functional
completion of UniConf. High priority is the highest priority. All high priority requirements
are marked with (H)
Medium: Medium priority defines requirements that are desired for the completion of
UniConf, however will not prevent the release of UniConf. All medium priority
requirements are marked with (M)
Low: Low priority defines requirements that are suggested improvements, and are not
defined within the scope of the project due date. All low priority requirements are
marked with (L)
2. Document Layout
2.1. Main Features This Document is broken into 3 main parts. In the first part, the functional requirements of the
UniConf User Interface are listed. The second part contains the following main features:
GUI Layout
Presentation
Document Sharing
Scheduling
Communication
Administrative Services
The third part represents features that are more device and system specific, such as server requirements, installation, maintenance and operating system. In addition, the end of this document contains a glossary of terms and an appendix with traceability tables for both priorities and User Roles.
8 |UniConf
2.2. User Roles
At each functional requirement the reader will see in bold a priority level (H, M, L) and a user role. Identifiers have been given to each functional requirement to represent which user roles will by default be able to access that feature. The User Roles and their symbols are as follows:
Presenter : P
Guest/Audience: G
Registered User: RU
Door Account: D
System Admin: A
All users : ALL
Here are two examples of a functional requirement followed by a user role.
11.1.1 The system shall allow users to be able to upload presentations in the .pptx format
(H) [A, P]
11.1.8 The system shall allow users to view the presentation (H) [ALL]
Note: Not all functional requirements have user roles associated with them. If no user role is
present, it is implied that the feature is a system requirement and is not user specific.
3. GUI Layout UniConf is a combination of functionality and presentation. As a program designed to improve a
user’s experience, it is natural that the graphical user interface (GUI) be presented and described
within the context of this document.
3.1. Login View The system shall present two separate login URLs, one for non-registered and one for
registered users (H) The system shall allow users to enable and use remembered user sessions (auto login)
(M) [ALL]
The system present a custom logo at each login screen if enabled in Administrative Features (H) [A]
The system shall allow the admin to choose a logo for the login screen, or it will use the default UniConf logo. (H)
The system shall allow users to log in with an existing user name and password at the <server>/login.aspx page (H) [A, P, RU, D]
The system shall allow users to log in with a user name and no password (defined as a “guest” account) (H) [G, D]
The system shall allow users to add custom data entry fields to each login screen (M) [A, P]
The system shall allow users to sign up for a guest account (M) [G]
The system shall allow users to log in with social networking credentials (M) [A, P, RU, G]
The system shall allow users to select which social networking sites are available (M) [A]
9 |UniConf
The system shall allow users to collect information from supported social networking sites (Facebook, LinkedIn, Twitter) (L) [A, P]
The system shall (if social networking identification is enabled) present a notification to users informing them of the information collection and allowing them to accept or decline (M) [ALL]
The system shall allow users to provide custom terms and conditions and privacy policies to be accepted by the users of the system (M) [A,P]
The system shall allow users to select which event they wish to join [H] [ALL]
3.2. Main View The Main View shall serve as a "home screen", providing access to all other views.
The Main View shall consist of a Smartphone version and a Tablet version (H)
3.2..1. The Smartphone version shall be presented to users on smart phone devices(H)
3.2..1.1. The table view shall take up the entire screen (H)
3.2..1.2. Sub views shall replace table view (H)
3.2..1.3. Users shall be able to navigate back to Navigation Table via the user of a back
button (H)
3.2..2. The Tablet version shall be presented to users on tablet devices and personal
computers(H)
3.2..2.1. The table view shall occupy the left-hand side of the screen (H)
UniConf Logo
Join Session
Login via Facebook
Logo
Username Field
Password Field
Join Session (login)
button
Social Networking
login options
Login View Diagram
Username
Password
10 |UniConf
3.2..2.2. Sub views shall occupy the remainder of the screen (H)
The Main View shall present a navigation table (H)
3.2..1. The navigation table shall consist of the following entries (H)
3.2..1.1. "Documents" [A, P, RU, G]
3.2..1.2. "Presentation" [ALL]
3.2..1.3. "Device Settings" [ALL]
3.2..1.4. "Chat" [A, P, RU, G]
3.2..1.5. "Admin" [A]
3.2..1.6. "Notification" [ALL]
Each entry shall consist of a title and an image (H)
3.2..1. The title shall be centered (M)
3.2..2. The image shall be on the left of the title (M)
Selecting an entry shall present the corresponding view (H)
The Main View shall present a "placeholder" when a user first accesses the Main View
(H)
3.2..1. The placeholder shall consist of an admin defined logo image (H)
Documents
Presentation
Scheduling
Chat
Notifications
Settings
Admin
Placeholder Image
Navigation TableView Placeholder
(subviews appear here on
tablet)
Main View Diagram (Tablet)
Presentation
Scheduling
Chat
Notifications
Settings
Admin
Documents
Navigation Table
Main View Diagram (Smartphone)
11 |UniConf
3.3. Presentation View
The system shall present the presentation as a PDF file(H) [A]
3.3..1. The system shall convert any uploaded .pptx presentations into a series of images
for use in the presentation view (M) [A]
3.3..2. The presentation view shall present the presentation as the entire screen (M) [A]
3.3..3. The system shall present an uploaded PDF file as a downloadable document (H)
The system shall allow the slides to transition from left to right in presentation order (H)
[A]
Presentation View Diagram
Page #
12 |UniConf
3.4. Documents View The Documents View shall present a list of documents available to be viewed or
downloaded. The Documents View let the user scroll between pages. (H)
The Documents View shall consist of a list of entries representing documents (H)
3.4..1. Each entry shall consist of the following (H)
3.4..1.1. An image icon representing the document type, located on the left of the
entry (H)
3.4..1.2. A text label representing the document title, centered in the entry (H)
3.4..1.3. A disclosure arrow indicating that the entry can be touched, located at the
right of the entry (H)
3.4..2. Selecting an entry shall display the Document viewer (H)
3.4..2.1. The document viewer shall present the document full screen (L)
3.4..2.2. The document viewer shall present controls overlaid on the document (M)
3.4..2.2.1. The overlaid controls shall fade in/fade out when the user taps on the
document (M)
3.4..2.2.2. User can navigate between pages by swiping his finger on the screen. (H)
3.4..2.2.3. The overlaid controls shall consist of the following:
3.4..2.2.3.1. Download document (H) [ A, P, RU]
3.4..2.2.3.2. Add notes (L) [ A, P, RU]
3.4..2.2.3.3. Zoom in/out (H)
3.4..2.2.3.4. Add markup (draw on document) (L) [ A, P, RU]
3.4..2.2.3.5. Rename document (M) [ A, P]
3.4..2.2.3.6. Change document permissions (L) [ A, P]
3.4..2.2.3.7. Share document (H) [ A, P, RU]
3.4..2.2.3.8. Share via Email (L) [ A, P, RU]
3.4..2.2.3.9. Share via Twitter (L) [ A, P, RU]
3.4..2.2.3.10. Share via Facebook (L) [ A, P, RU]
3.4..2.2.4. The overlaid controls shall be presented/hidden based on user
permissions (L) [ALL]
13 |UniConf
Documents View Diagram
Document 2.pptx
Document 3.xlsx
Document 4.pdf
Document 5.tiff
Document 6.png
Document 7.jpg
Document 1.docx >
>
>
>
>
>
>
Document Title
Document Type Image
1.1. DocumentsView1.1.1. TheDocumentsViewshallpresentalistofdocuments
availabletobeviewedordownloaded(H)1.1.2. TheDocumentsViewshallconsistofalistofentries
represen ngdocuments(H)1.1.2.1. Eachentryshallconsistofthefollowing(H)1.1.2.1.1. Animageiconrepresen ngthedocument
type,locatedonthele oftheentry(H)1.1.2.1.2. Atextlabelrepresen ngthedocument
tle,centeredintheentry(H)1.1.2.1.3. Adisclosurearrowindica ngthattheentry
canbeclicked,locatedattherightoftheentry(H)1.1.2.2. Selec nganentryshalldisplaytheDocument
viewer(H)1.1.2.2.1. Thedocumentviewershallpresentthe
documentfullscreen(L)1.1.2.2.2. Thedocumentviewershallpresentcontrols
overlaidonthedocument(M)1.1.2.2.2.1. Theoverlaidcontrolsshallfadein/fadeout
whentheusertapsonthedocument(M)1.1.2.2.2.2. Theoverlaidcontrolsshallconsistofthe
following1.1.2.2.2.2.1. Downloaddocument(H)[A,P,RU]1.1.2.2.2.2.2. Addnotes(L)[A,P,RU]1.1.2.2.2.2.3. Addmarkup(drawondocument)
(L)[A,P,RU]1.1.2.2.2.2.4. Renamedocument(M)[A,P]1.1.2.2.2.2.5. Changedocumentpermissions(H)
[A,P]1.1.2.2.2.2.6. Sharedocument(H)[A,P,RU]1.1.2.2.2.2.7. ShareviaEmail(H)[A,P,RU]
Document Controls
Document Being Viewed
Document Viewer Diagram
14 |UniConf
3.5. Chat View
The Chat View shall present a chat room and allow users to type chat messages to other
participants in the same conference(H)
The Chat View shall contain a chat room box (H)
3.5..1. The chat room box shall be presented in the center of the page (H)
3.5..2. The chat room box shall be divided into two columns (H)
3.5..2.1. The left column shall present a list of all users currently in the session (H)
3.5..2.1.1. Each entry in this column shall consist of a username (H)
3.5..2.1.2. Selecting an entry in this column shall present the following list of options
in a pop-over (H)
3.5..2.1.2.1. Send private message (H)
3.5..2.1.2.2. View contact information (H)
3.5..2.1.2.3. Share file (H)
3.5..2.1.3. The right column shall present all chat messages that have been posted to
the chat room during the current session (H)
3.5..2.1.4. Each message shall be preceded by the username of the person sending
the message (H)
3.5..2.1.5. Each message shall also be preceded by the timestamp the message was
sent (H)
3.5..2.1.6. Touching a username shall present the following list of options in a small
pop-over menu (H)
3.5..2.1.6.1. Send private message (H)
3.5..2.1.6.2. View contact card (H)
3.5..2.1.6.3. Share file (H)
The Chat View shall also present a chat input box (H)
3.5..1. The chat input box shall consist of a single-row text field (H)
3.5..2. The chat input box shall be presented below the chat room box (H)
3.5..3. The chat input box shall expand to multiple lines as the user types (M)
3.5..4. The chat input box shall have one associated button (H)
3.5..4.1. Send Message (H)
3.5..4.1.1. This button shall post the current text in chat input box to the chat room
and clear the chat input box (H)
3.5..4.1.2. This button shall be presented to the right of the chat input box (H)
3.5..5. The chat input box and Send Message button combined shall be the same width
as the chat room box (H)
15 |UniConf
Chat View Diagram
[Person 1]: Sample message sample message[Person 2]: Sample message sample message [Person 3]: Sample message sample message[Person 1]: Sample message sample message
Send
Chat Window
Text Input Box Send Button
[Alice 12:34:56]: Hello World! [Bob 12:34:57]: Hello World! [Chris 12:34:58]: Hello World! [Dave 12:34:59]: Hello World!
16 |UniConf
3.6. Scheduling View
The Scheduling View shall consist of: (H)
3.6..1. A list of all events scheduled in the same room as the current session (H)
3.6..2. A custom query to view events by (L) [ALL]
3.6..2.1. Time (H)
3.6..2.2. Location (H)
3.6..2.3. Owner (H)
3.6..2.4. Date (H)
3.6..2.5. Category (M)
Each entry in the list of events shall consist of the following (H)
3.6..1. The event title, left-justified in bold on the top row (H)
3.6..2. The event time, right-justified below the title(H)
3.6..3. The event location, left-below the title (M)
Selecting an entry in this list shall present the event view (H)
The Scheduling View shall present a “Rooms” entry (M)
3.6..1. Selecting the “Rooms” entry shall present a list of all rooms (H)
3.6..2. Selecting a room from the “Rooms” entry will list all events scheduled for that
room (H)
User shall be able to join events by clicking a “Join Event” button (H)
17 |UniConf
Sample Event 1
12:34 PM Room D
Sample Event 2
12:34 PM Room D
Sample Event 3
12:34 PM Room D
Sample Event 4
12:34 PM Room D
Filter By
[filter type drop-down] [filter options drop-down]
< Rooms View Rooms
Choose Filter Type
Filter type options
Events
Rooms View Diagram
Sample Event 1
12:34 PM Room D
Sample Event 2
12:34 PM Room D
Sample Event 3
12:34 PM Room D
Sample Event 4
12:34 PM Room D
Create New Event
All Events >
Events in this room
View All Events
Create New Event Button
Scheduling View Diagram
Save
Title
Time
Location
Attendees
Notes
Attach Documents...
Discard
Text Entry Box
Attach Documents
Button
Discard Button Save Button
Event View Diagram
vRoomR
vRoomR
vRoomR
vRoomR
vRoomR
vRoomR
Room 1
Room 2
Room 3
Room 4
18 |UniConf
3.7. Event View 3.7..1. The event view shall consist of a list of all information pertaining to an event (B)
3.7..2. Each entry shall consist of left-justified text with a disclosure button on the right
(H)
3.7..2.1. Selecting the disclosure button will allow the user to edit the entry (H) [A, P,
RU]
3.7..3. The event view shall present the following entries (H)
3.7..3.1. Event title (H)
3.7..3.2. Event time (H)
3.7..3.3. Event location (H)
3.7..3.4. Event guests (H)
3.7..3.5. Event notes (H)
3.7..3.6. Attached documents (H)
3.7..4. The event view shall present a “Save” button at the bottom of each entry view (H)
3.7..5. The event view shall present a “Discard” button at the bottom of each entry view
(H)
3.8. Notification View
The Notification view shall present a list of notifications (H)
Each notification shall consist of two panels, split vertically (H)
3.8..1. The top half shall present the text of the notification (H)
3.8..2. The bottom half shall present a list of options (H)
3.8..2.1. Send notification (H)
3.8..2.1.1. Selecting this option shall present a text field and send button (H)
3.8..2.1.2. Tapping the send button shall send the contents of the field to the
presenter and shall clear and dismiss the text field (H)
3.8..2.2. Respond to notification (H)
3.8..2.2.1. Selecting this option shall present a text field and send button (H)
3.8..2.2.2. Tapping the send button shall send the contents of the field to the sender
of the notification and shall clear and dismiss the text field (H)
3.8..2.3. Delete notification(H)
3.8..2.3.1. Selecting this option shall remove the notification from the list (H)
3.8..2.4. View sender (H)
3.8..2.4.1. Selecting this option shall present the notification sender's contact card
(H)
19 |UniConf
3.9.
Send Notification
This is the text of a sample notification. This is the
text of a sample notification.
Respond View Sender Respond
This is the text of a sample notification. This is the
text of a sample notification.
Respond View Sender Respond
This is the text of a sample notification. This is the
text of a sample notification.
Respond View Sender Respond
Notifications
Respond Button
View Sender Button
Respond Button
Send Notification Button
Notification View Diagram
SendCancel
Notification
Text Entry Box
Cancel Button Save Button
New Notification Diagram
20 |UniConf
3.9. Administrative View
Administrative View controls shall be presented as entries in a table view (H)
All controls listed in this section shall conform to the following style unless otherwise
specified (H)
The control shall be an on/off switch with text on the left and the control switch on the
right (H)
The controls in this section will correspond only to the current session the user is logged
into (H)
3.9..1. Presentation Viewing (on/off) (H) [A, P]
3.9..1.1. Allow Presentation Download (on/off) (H) [A, P]
3.9..2. Chat (on/off) (H) [A, P]
3.9..2.1. Chat Logging (on/off) (H) [A, P]
3.9..3. Document Sharing (on/off) (H) [A, P]
3.9..4. Notifications (on/off) (H) [A, P]
3.9..5. Hidden Event (on/off) (H) [A, P]
3.9..6. Current Session (on/off) (H) [A, P]
The administrative view shall also present a list of users registered users as a list of user
names (H)
3.9..1. Selecting a user name shall open the User Controls View (H)
Presentation Viewing On/Off
Allow Presentation Download On/Off
Chat On/Off
Chat Logging On/Off
Document Sharing On/Off
Notifications On/Off
Hidden Event On/Off
Current Session On/Off
Users
User 1 >
User 2 >
User 3 >
User 4 >
Settings
On/Off Switch
Administrative View Diagram
21 |UniConf
3.10. User Controls View User Controls are controls which are applied individually to each user(H)
Access to User Controls shall be presented through a list of user names (H)
This list shall be presented in a separate table view group from standard controls (H)
3.10..1. The User Controls view shall contain the following controls (H)
3.10..1.1. "Allow File Viewing" [A, P]
3.10..1.2. "Allow File Downloads" [A, P]
3.10..1.3. "Allow File Uploads" [A, P]
3.10..1.4. "Allow Chat" [A, P]
3.10..1.5. "Allow Presentation Viewing" [A, P]
3.10..1.6. "Allow Schedule Viewing" [A, P]
3.10..1.7. "Allow Schedule Editing" [A, P]
Allow File Viewing On/Off
Allow File Downloads On/Off
Allow File Uploads On/Off
Allow Chat On/Off
Allow Presentation Viewing On/Off
Allow Schedule Viewing On/Off
Allow Schedule Editing On/Off
Settings
On/Off Switch
User Controls View Diagram
22 |UniConf
3.11. Device Settings View
The Device Settings View shall serve as a control panel encapsulating all Device Setting
functions. (H) [ALL]
Device Settings view controls shall be presented as entries in a table view (H)
All controls listed in this section shall conform to the following style unless otherwise
specified (H)
The control shall be an on/off switch with text on the left and the control switch on the
right (H)
3.11..1. The controls in this section will be displayed or hidden based on user account
permissions. (H)
3.11..2. The Device Settings view shall contain the following controls
3.11..2.1. Theater Mode (H)
3.11..2.2. Notifications (H)
3.11..2.3. Sounds (M)
4.
Theater Mode On/Off
Chat Notifications On/Off
Chat Sounds On/Off
Settings
On/Off Switch
Device Settings View Diagram
23 |UniConf
4. Presentations
4.1. Presentations
The system shall allow users to be able to upload presentations in the .pptx format (M)
[A, P]
The system shall allow users to be able to upload presentations in the .PDF format (H) [A,
P]
The system shall allow users to enable/disable presentation viewing for the Guest
accounts (M) [A, P]
The system shall allow users to enable/disable presentation viewing for registered users
(H) [A, P]
The system shall allow users to enable/disable .pptx downloading by registered users or
audience members (H) [A, P]
The system shall allow users to view the number of attendees in session (H) [ALL]
The system shall allow users to scroll through the presentation with a left-right "swipe"
motion (H) [ALL]
The system shall allow users to display a JPEG/PNG/PDF placeholder for the meeting in
session (H) [A, P]
The system shall allow users to view the presentation (H) [All]
4.2. Surveys The system shall allow users to create a survey (H) [A, P]
The system shall allow users to view the results of a survey from their UniConf display (H)
[A, P, RU]
The system shall allow users to append the results of a survey to the current
presentation (H) [A, P]
The system shall allow users to take a survey/poll (H) [A, P, RU, G]
The system shall present users a survey/poll notification during a session (M)
[A, P, RU, G]
The system shall allow users to participate only once in the notification/poll (M)
[A, P, RU, G]
The system shall allow Admins and Presenters to create survey questions (H) [A, P]
4.2..1. The system shall allow A and P to create (H) [A, P]
4.2..1.1. Multiple Choice questions
4.2..1.2. Boolean (true/false) questions
4.2..1.3. Essay Questions
4.2..1.4. Multiple choice (multiple select) questions
4.3. Scheduling The system shall be able to link event descriptions to Presentations (I.e., click and brings
up presentation if user is registered) (H)
24 |UniConf
4.4. Tablet view
The presentation shall scale to fit the space (minus the navigation bar) in a Tablet view
(H)
The presentation shall transition slides on a left-right finger swipe (H)
4.5. Phone view
The presentation shall scale to fit the entire screen of a phone view (H)
The presentation shall display the "back bar" on screen click (H)
The presentation shall transition slides on a left-right finger swipe (H)
5. Document Sharing
5.1. Files The system shall be able to upload non-executable documents and files (H) [ A, P, RU]
The system shall allow users to download listed files onto their mobile device (H) [ A, P,
RU]
The system shall allow users to remove items previously uploaded (H) [ A, P]
The system shall allow users to link documents from within a Chat, Notification, or Event
item. (M) [ A, P, RU, G]
The system shall allow users to remove any file they have delete permissions on. (H)
[ALL]
The system shall allow users to change file permissions for other user(s) or user groups
(L) [ A, P]
The system shall allow users to change the maximum file size for document upload (M)
[A, P, RU]
6. Scheduling
6.1. Reservations The system shall allow users to reserve rooms (H) [ A, P, RU]
The system shall allow users to delete reservations (H) [ A, P, RU]
The system shall allow users to modify reservations (H) [ A, P, RU]
The system shall allow users to view reservations based upon the following queries(H)
[ALL]
6.1..1. Time (H)
6.1..2. Location (H)
6.1..3. Owner (H)
6.1..4. Date (H)
6.1..5. Category (M)
The system shall allow users to hide reservations (H) [ A]
The system shall allow users to view reservation details (H) [ALL]
25 |UniConf
6.2. Rooms
The system shall allow users to view all rooms and their availability (H) [ A, P, RU, D]
The system shall allow users to view all rooms’ capacity, location, attributes and services
(H) [ A, P, RU, D]
6.3. Events
The system shall allow users to save and export a reservation into iCalendar formatted
file (L) [ A]
The system shall allow users to import a reservation from an iCalendar file(L) [ A, P]
The system shall allow users to link events for easy sharing with other users (L) [ A, P, RU,
G]
The system shall allow users to invite other users to an event (L) [ A, P, RU, G]
7. Communication
7.1. Chat Features
The system shall allow users to copy/paste the text inside chat window (H) [ALL]
The system shall allow users to see a list of available chat users (H) [ALL]
The system shall allow users to send a private chat message to another specified user (H)
[ALL]
The system shall allow users to send a private chat message to the presenter (H) [ALL]
The system shall allow users to send a public chat message to all the other users (H)
[ALL]
The system shall allow users to ban/restore a guest account from the chat room (H) [ A,
P]
The system shall allow users to link documents for easy sharing (H) [ALL]
7.2. Settings Panel The system shall allow users to turn on or off notification pop-ups for chat (H) [ALL]
The system shall allow users to turn on/off the sound (H) [ALL]
The system shall allow users to turn on/off the theater mode (H) [ALL]
7.3. Personal Messaging The system shall allow a user to select another user’s profile by clicking on their name in
chat (H) [ALL]
The system shall allow a user to search for another user (M) [ALL]
The system shall allow a user to view another users profile (H) [ALL]
The system shall allow a user to enter into a one on one conversation with another user
(H) [ALL]
The system shall allow a user to invite multiple users into a private chat room (L) [ALL]
26 |UniConf
The system shall allow a user to select which information to display on their profile (L)[
A, P, RU]
The system shall allow a user to store a contact in a buddy list (L) [ A, P, RU]
7.4. Notification Features The system shall allow all users to turn on or off notifications (M) [ALL]
The system shall allow users to send out/delete notifications (H) [ A, P]
The system shall allow automatic notifications to be scheduled (M) [ A]
8. Administrative Features
8.1. General The system shall allow an administrator to select a logo to be viewed by users (H) [A]
8.2. User accounts The system shall allow an administrator to add user accounts with a corresponding user
name, password, and permissions (H) [A]
The system shall allow an administrator to delete user accounts (H) [A]
The system shall allow an administrator to modify the username, password, and
permissions of a user account (H) [A]
The system shall allow user accounts to contain custom data fields such as an email
address, physical address, company, title, and a phone number (L) [ALL]
8.3. Location
The system shall allow an administrator to add locations that are available for
reservations(L)
The system shall allow an administrator to remove a location from list of available
locations(L)
The system shall allow an administrator to make a location temporarily unavailable(L)
8.4. Alerts
The system shall allow an administrator to send a pop-up notification to all users
currently logged into the system (M)
8.5. On/Off Features The system shall allow an administrator to disable/enable the scheduling system(H)
The system shall allow an administrator to disable/enable the website(H)
The system shall provide a maintenance page if the website is disabled(H)
The system shall allow an administrator to disable/enable document sharing (H)
8.5..1. The system shall provide a maintenance view for document sharing, presentations,
and user accounts if they are disabled or if there are internal errors(H)
27 |UniConf
The system shall allow an administrator to disable/enable chat functionality.
8.5..1. The system shall provide a maintenance view for chat if it is disabled (H)
8.6. Chat Logging
The system shall allow an administrator to enable/disable chat logging for one, more
than one, or all of events(H)
The system shall allow an administrator to enable/disable presenters ability to receive
copies of the chat logs (H)
9. User Roles Below we have defined the default user roles that UniConf provides as part of its package. Each
user role will utilize one or more features. In this section, the user roles are explained briefly in an
easy to understand synopsis.
9.1. Guest The guest account shall be able to interact with the presentation
The guest account shall be able to chat with the other users
The guest account shall be able to change his/her personal settings
The guest account shall be able to download the conference’s public documents
The guest account shall be able to see the schedule
9.2. Registered User
The registered user may have privileges additional to those provided by guest
The registered user shall be able to maintain permissions and preferences through
multiple sessions
9.3. Door Account The door account shall be able to see the schedule
The door account shall be able to view event details
The door account shall be able to send notifications to presenters who have reservations
in its mapped location
9.4. Admin The system admin shall have all normal permissions and capabilities
The admin shall be able to broadcast a message to all audience
The admin shall be able to modify user permissions
The admin shall have access to every feature and setting
9.5. Presenter
The registered user may have privileges additional to those provided by the Registered
User role
28 |UniConf
The Presenter shall be able to maintain permissions and preferences through multiple
sessions
The presenter shall be able to upload documents and presentations
The presenter shall be able to clear the chat window for a particular event
The presenter shall be able to send notifications to users logged onto an event.
10. Supported Platforms 10.1. Because UniConf is web application, it can be accessed on any modern web browser.
However, it is optimized to run on the following platforms:
Safari 5.1 (H)
10.2. Future platform support
Microsoft Windows Phone 7 (M)
BlackBerry OS (L)
Google Android 2.0 and later (H)
Firefox (L)
Internet explorer (L)
11. Update Characteristics Because UniConf is a web application, updates are handled seamlessly. Bug fix or other updates
that do not affect what users see are performed silently. Updates that change features or affect the
way the application appears to the user will include a notification on the login screen detailing the
changes.
12. Installation Requirements
12.1. Client Because UniConf is a web application, no installation is required. Below are the client
requirements to use UniConf from a web interface.
Mobile devices
12.1..1. Users should be able to load UniConf on any touch screen devices running iOS
4.0 and later or Android 2.0 and later (H) [ALL]
Personal computers
12.1..1. Operating Systems (H) [ALL]
12.1..1.1. Users should be able to load UniConf on Windows XP or later
12.1..1.2. Users should be able to load UniConf on MacOS 10.5 or later
12.1..2. Browsers (H) [ALL]
12.1..2.1. Users should be able to load UniConf on Apple Safari 4.0 or later (H)
12.1..2.2. Users should be able to load UniConf on Google Chrome 16.0 or later(H)
12.1..2.3. Users should be able to load UniConf on Mozilla Firefox 5.0 or later (L)
29 |UniConf
12.2. Server
Web server requirements
12.2..1. The server should be running Windows Server 2003 or later (H)
12.2..2. The server should deployed IIS 7.0 or later (H)
12.2..3. The server should have Internet connection with at least 10Mbps uplink (H)
13. Error Handling
13.1. Unsupported devices Due to the large number of devices on the market, UniConf must contain a way to
redirect users and inform users if they are not running on a supported device.
13.2. Unsupported browsers Due to the large number of browsers on the market, UniConf must contain a way to
redirect users and inform users if they are not running on a supported browser.
13.3. Manual Injection Administrators must have a way of remotely accessing the database separate from the
project itself, in the case of product downtime.
14. Glossary 14.1. Administrator: The administrator account represents that of a facility manager. The
Administrator account can have all permissions
14.2. Administrative View: shall serve as a control panel encapsulating all Device Setting
functions.
14.3. Device: In this context, device refers to any computer (handheld or otherwise) that is used
to successfully view and use UniConf. Note, only certain devices are supported.
14.4. Documents: Refers to any type of virtual document, such as PDF, Excel, Word, PowerPoint,
and text documents
14.5. Door: The door user is specifically tailored for companies to place a tablet PC outside of a
conference room. The door account is meant to allow users to view information about the
current event, the schedule, and optionally any presentation occurring inside it’s designated
room
14.6. Event: An event refers to a title, description, date, and time by which a conference can be
identified. See also “Reservation”
14.7. Guest: A guest is a non-static user that may log in to any event/presentation session
without using a stored username and password. Guest accounts may have any number of
features enabled, except those of an Administrator
30 |UniConf
14.8. iCal / iCalendar: This is a calendar application format designed by Apple Inc. that is
supported by many calendar applications. UniConf uses this as It’s calendar specification of
choice
14.9. Logo: An image used by a company, organization, or individual that is chosen to represent
said entity
14.10. Notification: A notification is a chat window that specifically shows when a user has any
important form of communication that they have not yet opened
14.11. Panel: A rectangular graphical user interface element that serves as a relative location
placeholder and may contain other graphic user interface elements
14.12. Popover: This is a computer science term relating to a view that appears on top of another
view, but does not create a new window (such as a popup)
14.13. Presenter: A presenter is any user expected to give presentations to an audience. The
presenter is able to upload Microsoft PowerPoint files or PDF files and has presentation and
audience specific options enabled
14.14. Registered User: The registered user is a persistent account maintains a list of custom
permissions and user information
14.15. Reservation: A reservation refers to an event that is scheduled to take place with a time,
location, date, owner, event title, and event description. A reservation secures a place for
an event to occur
14.16. Theater Mode: This mode inverts the color scheme of UniConf to allow users to more easily
see the presentation and application in a dark setting.
14.17. Touching: This refers to “clicking” or “selecting” with ones finger on a touch screen device
31 |UniConf
15. Appendix A – User Permissions
Admin Presenter Registered
User Guest Door Presentation Permissions
Upload a presentation X X
Allow a presentation to be publicly view by guests X X
Allow a presentation to be view by login members only X X Display a JPEG/PNG/PDF placeholder for the meeting X X
View the presentation X X X X X
Create a survey X X View the results of a survey X X X
Append the results of a survey X X
Take a survey X X X X Present a survey/poll notification X X X X
Participate only once in the notification/poll X X X X
Document Permissions Upload files X X X
Download files X X X
Remove items previously uploaded X X Remove any file they have delete permissions on X X X X X
Change file permissions for other user(s) or user groups X X
Chat Permissions
See a list of available chat users X X X X X
Send a private message to the other specified user/presenter X X X X X
Send a public chat message to all the other users X X X X X
Ban/restore a guest account from the chat room X X Scheduling Permissions
Reserve rooms X X X
Delete reservations X X X Modify reservations X X X
Hide reservations X
View all rooms X X X X Event Permissions
Imported from an iCalendar file X X
export a reservation into iCalendar formatted file X X X X X Invite other users to an event X X X X
Notification Permissions
Turn on or off notifications X X X X X
Send out/delete Notifications X X Administrative View Permissions
Provide an administrative menu X
Allow an administrator to select a logo to be viewed by users X Allow an administrator to add/delete user accounts X
allow an administrator to modify the username and password X
32 |UniConf
16. Appendix B – Priority Tracking
16.1. High Priority Tasks
Section Sub-section Location Done
GUI Layout
Login View 3.1
Main View 3.2
Document View 3.3
Chat View 3.4
Scheduling View 3.5
Notification View 3.6
Login View 3.7
Device Settings View 3.8
Presentations
Presentations 4.1
Surveys 4.2
Scheduling 4.3
Tablet View 4.4
Phone View 4.5
Document Sharing Files 5.1
Scheduling All 6
Communication
Chat Features 7.1
Settings Panel 7.2
Personal Messaging 7.3
Administrative Features All 8
User Roles
Presenter 9.1
Audience 9.2
Registered User 9.3
Door Account 9.4
System Admin 9.5
Control Panel Settings All 10
Supported Platforms Supported Platforms 11.1
Installation Requirements All 13
33 |UniConf
16.2. Medium Priority Tasks
Section Sub-section Location Done
GUI Layout
Login View 3.1
Main View 3.2
Documents View 3.4
Scheduling View 3.6
Document Sharing Files 5.1.4
Communication Personal Messaging 7.3.2
Notification Features 7.4.1, 7.4.3
Supported Platforms Future Platform Support 11.2.1
16.3. Low Priority Tasks
Section Sub-section Location Done
GUI Layout
Login View 3.1
Documents View 3.4
Administrative Features
User Accounts 8.2
Alerts 8.4
Communication Personal Messaging 7.3.5-7.3.7
Supported Platforms Future Platform Support 11.2.2
