CST8151 – Software Analysis and Design – Fall 2009

ohiofulvousSoftware and s/w Development

Aug 15, 2012 (4 years and 8 months ago)

350 views



Code Orange






Electronic Whiteboard System


Statement of Scope

for






































November 6, 2009


Prepared For:


Mr. Frederick Dixon, Blindside Networks


Prepared By:

Derrick Krishn, Project
Leader

Tristan Bali

Nouh El
-
Masri

Wei Warren Hoang

Carl Johnson

Adam Wiacek

Blindside Networks

Statement of Scope

Team: Code Orange


Page
2

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


Project Authorization Sign
-
Off Sheet


I
,

Fred Dixon

of

Blindside Networks
,

certify that this
statement of
scope meets the project requirements. I have read and
reviewed this document as prepared by
Code Orange

and I approve the project for completion by the deliverable date of

March 15, 2010
.


I understand that the Computer Studies Department of Algonquin Coll
ege is not a software development company, and as
such cannot be regarded as being under contract to deliver a finished product.


I also understand that this project may be cancelled at any time by the Computer Studies Department of Algonquin College
sho
uld the project group not meet the academic standards of
CST8151 Software Design, Testing, and Quality Assurance
or
CST8160 Project.










_________________________________




_________________

Mr.
Fred Dixon







Date

Blindside Networks














______________________________




_________________

Derrick Krishn







Date

Code Orange

Project Leader




Blindside Networks

Statement of Scope

Team: Code Orange


Page
3

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


Table of Contents


List of Figures

Figure 1: Electronic Whiteboard System Context Diagram

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

7


List of Report Sections

PROJECT INTIALIZATIO
N

1.

I
NTRODUCTION

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

5

2.

P
URPOSE OF THE
P
ROJECT
................................
................................
................................
................................
.............

5

3.

U
SERS OF THE
P
RODUCT

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

5

APPLICATION AND DEVE
LOPMENT ENVIRONMENTS

4.

A
PPLICATION
E
NVIRONMENT OF THE
P
ROPOSED
S
YSTEM

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

5

a.

Hardware
Requirements

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

5

b.

Software Requirements

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

5

c.

Data Requirements

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

5

5.

D
EVELOPMENT
E
NVIRONMENT OF THE
P
ROPOSED
S
YSTEM

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

6

a.

Hardware Requirements

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

6

b.

Software Requirements

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

6

c.

Data Requirements

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

6

d.

Research Requirements

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

6

FUNCTIONAL REQUIREME
NTS

6.

T
HE
P
ROPOSED
S
YSTEM

S
C
ONTEXT
D
IAGRAM

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

7

7.

F
UNCTIONS
P
ROVIDED BY THE
P
R
OJECT

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

8

a.

Hardware Requirements

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

8

b.

Software Requirements

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

8

Essential Requirements

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

8

Useful Requirements

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

9

Desirable Requirements

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

9

NON
-
FUNCTIONAL REQUIREME
NTS

8.

M
ANDATED
C
ONSTRAINTS

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

9

9.

L
OOK AND
F
EEL
R
EQUIREMENTS

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

9

10.

U
SABILITY
R
EQUIREMENTS

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

9

11.

P
ERSONALIZATION AND I
NTERNATIONALIZATION
R
EQUIREMENTS

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

9

12.

E
ASE OF
L
EARNING

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

9

DELIVERABLES

13.

P
ROJECT
D
ELIVERABLES
................................
................................
................................
................................
.............

10

14.

C
OURSE
D
ELIVERABLES

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

10


Appendices

Appendix A


Project Gantt Chart



Blindside Networks

Statement of Scope

Team: Code Orange


Page
4

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


Contact Information




Client




Mr.
Frederick
Dixon






Blindside Networks



246 Queen Street, Suite 200



Ottawa, Ontario



K1M 1P6




(613) 695
-
0264



ffdixon@blindsidenetworks.com




Project Group Members





Derrick Krishn, Project Leader




derrick.krishn@gmail.com





Tristan Bali




bali.tristan@gmail.com





Nouh El
-
Masri




nouh.elmasri@gmail.com





We
i Warren Hoang




wei.warren.hoang@gmail.com





Carl Johnson




johnson.h.carl@gmail.com





Adam Wiacek




adam.wiacek2@gmail.com




Project Professor




Mel
Sanschagrin, Professor



Algonquin College


Woodroffe Campus



1385 Woodroffe Avenue



Ottawa, Ontario



K2G 1V8




(613) 727
-
4723 Extension 7299



sanschm@algonquincollege.com




Project Advisor




Mel
Sanschagrin, Professor



Algonquin College


Woodroffe Campus



1385 Woodroffe Avenue



Ottawa, Ontario



K2G 1V8




(613) 727
-
4723 Extension 7299



sanschm@algonquincollege.com

Blindside Networks

Statement of Scope

Team: Code Orange


Page
5

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


PROJECT IN
I
TIALIZATION

The initialization of the project and the understanding of the driving forces behind the client’s request for a product are
important to understand at the very onset of the project.

1.

Introduction

This is a Statement
of Scope prepared by
Code Orange

for t
he
Electronic Whiteboard System
sponsored by Mr.
Fred Dixon
,
Blindside Networks
. The project group leader is
Derrick Krishn
, and the project team members are
Tristan Bali
,
Nouh El
-
Masri
,
Wei Warren Hoang, Carl Johnson,

and

Adam Wiacek
.

The project will proceed according to the project plan
annotated in
the
Appendix A Gantt charts, and have a completion date of

March 15, 2010
.


2.


Purpose of the Project

Code Orange will address the business requirements of Blindside
Networks

by designing and implementing t
he Electronic
Whiteboard System (EWS) to be migrated into BigBlueButton. Hybrid classes have become a more common means of
teaching and allowing
distance

students’ access to lectures. This creates an opportunity for
distance

students to participate in
live lectures through BigBlueButton. BigBlueButton is an expanding project focused on making a more interactive
environment for teachers and students. The EWS will be incorporated to this project to further enhance to in
teractivity of the
BigBlueButton.


3.

Users of the Product


The users of this system will include all
students, and professors, who use BigBlueButton software. Students vary in
expertise of computing knowledge; however basic internet surfing skills are required to use BigBlueButton and the
Electronic Whiteboard System.


APPLICATION AND DEVELOPMENT ENVIRONMENTS

This section addresses the hardware and software requirements for the development and implementation of the project.

4.

Application Environment of the Proposed System

This section identifies b
oth the hardware and the software that must be in place in the operational (non
-
testing)
environments and configuration details.



a.

Hardware Requirements

The client agrees to reimburse C
ode
O
range 100% of all hardware costs relevant to setup, deployment, an
d testing
of the Electronic Whiteboard System within the BigBlueButton environment. This reimbursement does not cover
any cost associated with notebooks/netbooks, or network infrastructure
.


b.

Software Requirements

BigBlueButton is an open source project wh
ich requires no additional software to be mandated. BigBlueButton
software is already in place, and its current iteration has no limitations or requirements that need to be fulfilled.



c.

Data Requirements

The client must ensure that the shared object that
resides wi
thin BBB
-
apps remains available and
accessible; Non
-
compliance with this data requirement will
pose a high risk situation for design analysis and a medium risk
situation which could jeopardize the acceptance testing schedule for the remote commun
ications aspects of the
project.



Blindside Networks

Statement of Scope

Team: Code Orange


Page
6

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


5.


Development Environment of the Proposed System

The Linear Sequential Software Engineering paradigm, coupled with prototyping has been chosen for this project because
the client’s requirements are well known; however, not

all of the Human
-
Computer Interfaces have been defined.



a.

Hardware

Requirements

The
client will supply the following
hardware development system
to the project group within
one week
1

of the
signing of the Statement of Scope:




Two Nintendo Wii R
emotes



O
ne
Bluetooth adapter



b.

Software

Requirements

The system will be developed using the current versions of
Microsoft
Visual
Studio
,

Adobe C
reative
S
uite
,

and
Java Netbeans
. The project documentation will be developed using the current versions of Microsoft
Word,
Microsoft Project, and Microsoft Visio, which is a data
-
modelling tool. Since the project group has licensed copies
of all of this software

and is very familiar with its use
, the software development suite is considered low risk.


c.

Data Requirements

The client will supply documentation to inform Code Orange of any modifications made to the BBB
-
apps shared
object, at any given stage of development of the Electronic Whiteboard System.


d.

Research Requirements

The

project group will have to research the op
eration of
BigBlueButton

using the client
-
supplied
website
,

and
forums.

Research will also include device functionality with BigBlueButton server, and configuration details,
which pertain to web browsers talking to hardware devices.





1

Hardware may
be

provided
earlier
, but no later than
.

Blindside Networks

Statement of Scope

Team: Code Orange


Page
7

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


FUNCTIONAL REQUIREMENTS

Function
al
requirements are functions or features that must be included in the system to satisfy the project needs and be
acceptable to the client.

6.

The Proposed System’s Context Diagram

The
Electronic
Whiteboard System

context diagram
depicted in
Figure
1

contains all of the external entities that produce or
consume data and an external
entity that rep
resents inter system communication
. As such, the context diagram assists in
bounding the scope of the software requirements and also assists in determining the system interfaces.

0
-------
Electronic
Whiteboard
System
Professor
Session Information
New Whiteboard
Drawing Points
Pen Properties
Undo Drawing
Redo Drawing
Clear Canvas
Whiteboard
Updated Canvas
Updated Pen Properties
ITS
Technician
Write Calibration Coordinates
Validated Calibration Coordinates
BigBlueButton
Server
Query Drawing List
Drawing List
Context Diagram


Electronic Whiteboard System
(
EWS
)

Figure
1
: Electronic W
hiteboard System

Context Diagram

The
EWS

is the software system that will be developed to meet the requirements of the
EWS
SOS.


There are
three

external entities that all play an integral role in the operation of the
EWS
, briefly described as follows:




Pr
ofessor
:

Allows teachers to draw, create, undo, redo, and clear the Electronic Whiteboard.



ITS Technician
:
provides calibration techniques to validated user.



BigBlueButton Server
:
Sends and receives information from external system.


Blindside Networks

Statement of Scope

Team: Code Orange


Page
8

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


7.

Functions Provided by

the Project

This section explicitly identifies the hardware and software functionality for the project. Each hardware and software
requirement is prioritized as follows:




Essential:

T
hese requirement must be included in the system



Useful:

T
hese requireme
nts are those that would reduce system effectiveness if left out



Desirable:

T
hese requirements are those that are not part of the core, but make the system more attractive to
the users


In addition, each requirement will be identified using a unique identi
fier: the letters “HW” for hardware, “SW” for software,
followed by the priority category


“E” for Essential, “U” for Useful, or “D” for Desirable, and a number representing the
order of priority within the category. This notation will be used in other d
ocuments to cross
-
reference the requirements back
to this statement of scope.



a.

Hardware Requirements

The Electronic Whiteboard System has the following essential
hardware

requirements:


HWE
1

The Electronic Whiteboard System will use

two

Nintendo Wii Remo
tes.

HWE
2

The Electronic Whiteboard System will use

a host computer.

HWE
3

The Electronic Whiteboard System will use

a Bluetooth receiver.

HWE
4

The Electronic Whiteboard System
must have a projected surface.

HWE
5

The Electronic Whiteboard System must have a

calibrated infrared pen.

HWE
6

The Electronic Whiteboard System must have a Bluetooth receiver
to receive input from two

Nintendo
Wii R
emotes
, which will transmit to the host computer
.

HWE
7

The Bluetooth device, W
ii R
emotes, and infrared device will all be

in range of each other.

HWE
8

The Electronic Whiteboard System configuration file must be stored on the host computer
.

HWE
9

The Wii R
emotes will remain stationary.

HWE
10

The

Infrared pen will have an uninterrupted line of sight with the Wii
R
emotes.





b.

So
ftware Requirements

The
Electronic Whiteboard System

will provide
an

electronic drawing surface within

a web conferencing
application.

A
ny user with sufficient privileges will have access to this whiteboard
.

The Electronic
W
hiteboard
system will broadcast to users connected the information
that is currently drawn on the E
lectronic
W
hiteboard.


Software requirements for this projected are prioritized in the following paragraphs.


Essential Requirements


The
Electronic Whiteboa
rd
System has the following essential software requirements:


SWE
1

The ITS Technician must calibrate the host computer, used by a Professor, before a
n

Electronic
Whiteboard System can

be

initialize
d

with the BigBlueButton web application.

SWE
2

To start a
new whiteboard module, the professor must login to the BigBlueButton server, provide a session
ID number, and the associated password. Once validated, the professor will have access to functionality
applicable to their terms of usage.

SWE
3

Professor must b
e able to draw on the whiteboard and change the drawing properties of the pen used in the
lecture. Drawing properties in this case means color and thickness of the pen.

SWE
4

Professor must be able to clear the current whiteboard.

SWE
5

Professor must be able to undo and redo information on the whiteboard.

SWE
6

The Electronic Whiteboard must be pre
-
configured in such a way that the controls are simplistic when a
Professor chooses to use it. (
1
5
-
30

minute
s

of

training)

SWE7

The Electroni
c Whiteboard must be able to transmit coordinates of the current session to the
BigBlueButton Server. This data is transmitted to all clients connected with the same session ID #.


Blindside Networks

Statement of Scope

Team: Code Orange


Page
9

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


Useful Requirements


The

Electronic Whiteboard

System has
no useful softwar
e requirements.



Desirable Requirements


The
Electronic Whiteboard System
has
no useful software requirements.



NON
-
FUNCTIONAL REQUIREMENTS

Non
-
function
al

requirements describe the features, characteristics, and attributes of the sys
tem

as well as any constraints that
may limit the boundaries of the proposed system and the eventual design of the product.

8.

Mandated Constraints

This section describes constrain
ts on the requirements and the eventual design of the product.


Deadline

The deadline for this project is
March 15, 2010
.


Solution Constraints

The system must be easy to use.

The product
will use the user
-
supplied Wii R
emotes (2), Bluetooth receiver, and

host computer.

The host computer must have internet capability, and must be
F
lash capable, to connect to a BigBlueButton server.


9.


Look and Feel Requirements


The Interface

The product must comply wi
th corporate branding standards, and will be configure
d

within the BigBlueButton
configuration file.


10.

Usability Requirements


Ease of use

The product must be user friendly, such that controls are simple and easy to understand.

The product must be able to communicate with the BigBlueButton server, on a real tim
e basis.


11.

Personalization and internationalization
R
equirements


Language

The Electronic Whiteboard System will be part of BigBlueButton server, and such that the configuration of the Electronic
Whiteboard System is dependant of BigBlueButton.
The default
region

language English will be use
d.


12.

Ease of Learning


Training

Since the
product
will be used by
e
ducational institutes
,

students, and professors alike, minimal amounts of training will
be required to use this product. ITS technicians will be setting up and configuring all hardware components local to
educational institute.

After receiving
15


30 minutes
of training,
a pro
fessor or student must be able to use the Electronic
Whiteboard System with minimal effort
.

Blindside Networks

Statement of Scope

Team: Code Orange


Page
10

of
10

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx


DELIVERABLES

At a minimum, the following constitute the deliverables of your project.

13.

Project Deliverables

The following list constitutes the project deliverables:



Analysis Document set



Design Document set



Documented Source Code



Test Plan and Test Results



Supporting Manuals
-

User manuals, Installation manuals



Tested Software in
modular

format


14.

Course
Deliverables

The following list constitutes the course deliverables:



Project Group and Individual Time Logs



Project Presentation











Appendix A:



Blindside Networks

Statement of Scope

Team: Code Orange


A
-
3

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx



Blindside Networks

Statement of Scope

Team: Code Orange


A
-
3

©2009 Algonquin College

Team Code Orange

ohiofulvous_b09f65fc
-
b9c5
-
4c24
-
ab77
-
056e6417db14.docx