Software Requirements

Specifications
for

49er Express and Applications

Prepared by Group 4

(Andew Alexander, Anthony Rosas, Alejandro Rios, Jonathan Presson, & Troy McCall)

ITIS 3300 Section 001

4.08.2008
Software Requirements Specifications for 49er Express

Table of Contents
1.1 Purpose........................................................................................................................... ..................3
1.2 Document Conventions................................................................................................................... ..3
1.3 Intended Audience and Reading Suggestions................................................................................... .3
1.4 Project Scope.................................................................................................................... ................3
1.5 References................................................................................................................. .......................3
Overall Description........................................................................................................................3
1.6 Product Perspective............................................................................................... ...........................3
1.7 Product Features......................................................................................................... ......................3
1.8 User Classes and Characteristics.................................................................................................... ...4
Students: Currently enrolled undergrad and graduate, and post-bat students at UNC Charlotte of any
gender and ages............................................................................................................. .........................4
Faculty: UNC Charlotte professors, deans, assistance professors, and teacher assistants.......................4
1.9 Operating Environment................................................................................................................... ..4
1.10 Design and Implementation Constraints................................................................... ......................4
1.11 User Documentation............................................................................................... ........................5
1.12 Assumptions and Dependencies............................................................................................ ..........5
System Features............................................................................................................................. .........5
1.13 System Feature I......................................................................................................... ....................5
1.14 System Feature II................................................................................................................... ..........5
1.15 System Feature III................................................................................................. ..........................5
1.16 System Feature IV........................................................................................................................ ...6
External Interface Requirements.................................................................................................6
1.17 User Interfaces.................................................................................................................... ............6
1.18 Hardware Interfaces.............................................................................................................. ..........7
1.19 Software Interfaces...................................................................................................... ...................7
1.20 Communications Interfaces............................................................................................................. 7
Other Nonfunctional Requirements.............................................................................................8
1.21 Performance Requirements................................................................................................ .............8
1.22 Security Requirements........................................................................................................ ............8

Revision History
Name Date Reason For Changes Version
Template Draft 2.12.08 Original Template Draft 1.0
Template Draft 2 2.14.08 Template Draft Modified for our SRS 2.0
SRS V1 3.15.08 Added new requirements 3.0
SRS V2 3.18.08 Combined requirements from group members 4.0
SRS V3 4.15.08 Added more requirements 5.0
SRS Final 5.08.08 Combined all requirements 6.0
Software Requirements Specifications for 49er Express

Introduction

1Purpose
To build an all inclusive system that includes your email system, check class schedule and
displays it all on one page. To create a more usable portal that is in essence, one-stop-shopping.
Kind of like amazon.com effect where you can get it all with one click on the button.

2Document Conventions

High level priorities will be italicized

3Intended Audience and Reading Suggestions

UNC Charlotte students, staff, and faculty who use 49er Express.

4Project Scope
To make 49er Express more user friendly, simplify the navigation, and

5References
References are including existing systems and documentation

Overall Description
6Product Perspective

To combine existing 49er express applications into a simplified portal system in order to make
49 express more user friendly. The entire home page of 49er express will be customizable to
allow each student to incorporate relevant material to themselves.

7Product Features

Banner:

Banner will continue to perform its existing functions of registration, drop/add, financial aid, etc.

Blackboard:
Software Requirements Specifications for 49er Express

Class information, due dates (calendar), assignments, quizzes, tests, grades, chat, message
board. All information will be displayed on the calendar. Classes will be able to access each
class webpage individually but not have to provide an additional password to do so.

Email:

Email hosted by Google: Gmail will be available on the home page of 49er express. Google
provides email hosting under their “Google Apps Education Edition Agreement”.
(http://www.google.com/a/help/intl/en/admins/education_terms.html)

8User Classes and Characteristics

Students: Currently enrolled undergrad and graduate, and post-bat students at UNC Charlotte of
any gender and ages.

Faculty: UNC Charlotte professors, deans, assistance professors, and teacher assistants.

9Operating Environment

Anyone that falls in the categories listed in section 1.8 will have complete access to the system
from any computer, on or off campus. It will be the responsibility of the maintenance staff of the
system to assure that the system is in working order and that students won't be held accountable
for assignments due on the date that the system would be down. Weather on of off campus, it is
suggested that the individual using the system be in a location that is conducive to learning. For
example, the upper levels of the Atkins library or any lab with little or no external noise.

10Design and Implementation Constraints

• The final Express portal must be compatible with integrating the other systems

• The hardware that runs the new Express must be able to handle the load of accessing all
the systems.

• Funding will be required for new hardware to run Express and labor costs for making the
transition.

• If the single sign-on Express portal fails all applications will be unavailable.

• The interface of Express must not change too greatly as it would require more help for
users that are used to the current system.
Software Requirements Specifications for 49er Express

11User Documentation

The documentation for the Express portal will be based on the existing documentation for
NinerNet services which can be found at http://ninernet.uncc.edu/policy.php. The main changes
are in accessing the services.

Documentation for the new Calendar and Gmail will be based on existing Google App
documentation. See http://google.com/support/a/users/?hl=en

12Assumptions and Dependencies

If one uses 49er Express, you are currently enrolled or employed by UNCC. Users have
compatible browsers, and active internet connections.

System Features

13System Feature I
49er Express Portal
 Combines e-mail, blackboard, banner, and current express features into one portal
that can be accessed with one sign on. High Priority (9).
■ The portal will contain a specific template. Each application will have it’s
own “window” or “webpart”. (See definitions)

14System Feature II

RSS Reader

• This webpart will allow the user to subscribe to existing RSS feeds and place them on 
their homepage or any other tab. 

15  System Feature III

Gmail
 Migrate Microsoft Exchange Server to Gmail. High Priority (9).
■ See http://www.google.com/support/a/bin/topic.py?topic=9202
 Gmail will replace Outlook Web Access, this will allow greater
storage (6.7 gigabytes per user, (6.7 GB is the current storage
limit, but will continue to grow at 0.0001 GB per day)). OWA only
allowed 100 megabytes of storage.
Software Requirements Specifications for 49er Express

16  System Feature IV

Integrated Calendar
 Combined Calendar (Google)
■ Includes all blackboard and webassign due dates. The calendar will also include
assigned homework from each class (that was not on either blackboard or
webassign). The calendar will include all quiz and test dates for all classes that
the student is registered for. (This assumes that the user is a student, not UNCC
faculty or staff)
See http://www.google.com/support/a/bin/topic.py?topic=9201

External Interface Requirements

Software Requirements Specifications for 49er Express

17 User Interfaces

18 Hardware Interfaces

The Hardware Interface is server specific. There are currently multiple servers running multiple
environments. integration is still to be determined. Implementation needs to be tested.

The physical drives (number to be determined) will be in a RAID 5 array (combines three or
more discs in a way that protects data against loss of any one disc; the storage capacity of the
array is reduced by one disk.)
Each web server will be balanced a test-loaded to ensure maximum response time.
Software Requirements Specifications for 49er Express

Http traffic will routed through high-levels of load-balancing (still to be determined)

Current web-servers will be upgraded on CPU, RAM, and gigabit Ethernet cards. After those
resources are exhausted we will add more (mirrored) web-servers to the farm.

19Software Interfaces

All servers will be migrated to Windows Server 2008. There are multiple software implementations that
have to be determined and explored. Currently we have multiple systems, running multiple environments
that are not coordinated.

Current software includes:

BEA Weblogic, Oracle (Banner)

IIS 5.5, SQL Server 2005 (49er Express)
IIS 6.0 Microsoft Exchange Server (Email)

The new portal system will include Banner, and existing 49er express applications, Microsoft Exchange
will be replaced will Google Gmail.

20Communications Interfaces

Http: protocol port:80 for a web-based application.

IMAP,POP3, etc for Gmail (Email)

Other Nonfunctional Requirements

21Performance Requirements

Even during heavy load times such as when students register for classes, Express Portal should
load pages within standard times expected for respective connections.

22Security Requirements
All student and faculty information must be encrypted via SSL Encryption with valid certificates and can
only be accessed by authorized users.

Appendix A: Glossary
Webassign: webassign is a 3rd party application used by some teachers for homework assignments.
http://webassign.net

Webpart: (also know as a widget, or window) Web Parts are an integrated set of controls for creating
Web sites that enable end users to modify the content, appearance, and behavior of Web pages directly
Software Requirements Specifications for 49er Express

from a browser. The Web Parts control set is a group of components that work together to enable
developers to create Web pages where users can modify the user interface (UI) directly from a browser.
The UI controls all derive from the Part class, and they comprise the primary UI on a Web Parts page.

OWA: Stands for Outlook Web Access. This is the current email system that 49er Express has in
production.

RSS: (Really Simple Syndication). A web-format used to publish frequently updated content such as
blog entries, news headlines, and podcasts. An RSS document (which is called a "feed" or "web feed or
"channel") contains either a summary of content from an associated web site or the full text. RSS makes it
possible for people to keep up with web sites in an automated manner that can be piped into special
programs or filtered displays
Software Requirements Specifications for 49er Express

Appendix B: Analysis Models

Appendix C: Issues List

No “actual” testing has been done. This integration is hypothetical and there could be many unforeseen
issues.