REQUIREMENT

Document Sample
REQUIREMENT Powered By Docstoc
					REQUIREMENT
SPECIFICATIONS
     FOR
*Star Properties

              Tim Boyle
           Jessica Davis
                   Loc Ma
             Tyrell Nash
             Claud Sava
        Justin Sebastian
            Mark Wettou
                      Page | 1
  Table of Contents

Introduction ..................................................................................................................................................... 4

1. Objective ................................................................................................................................................... 4

Constraints/Risk Management ........................................................................................................................ 4

2. Constraints ................................................................................................................................................ 4

3. Risk Management ..................................................................................................................................... 4

Requirements .................................................................................................................................................. 5

4. Business Requirements ............................................................................................................................. 5

   4.1.1.        System Availability ........................................................................................................................ 5

   4.1.2.        System Performance and Maintenance........................................................................................ 5

   4.1.3.        Accessibility ................................................................................................................................... 5

   4.1.4.        Security ......................................................................................................................................... 5

   4.1.5.        Toolbars ........................................................................................................................................ 6

   4.1.6.        User Roles ..................................................................................................................................... 6

   4.1.7.        Training Manual ............................................................................................................................ 6

5. Functional Requirements .......................................................................................................................... 7

   5.1.1.        Homepage ..................................................................................................................................... 7

   5.1.2.        Property Module ........................................................................................................................... 7

   5.1.3.        Alerts Module ............................................................................................................................... 8

   5.1.4.        Tenants Module ............................................................................................................................ 8

   5.1.5.        Tickets Module .............................................................................................................................. 8
                                                                                                                                                        Page | 2
   5.1.6.        Administration Module ................................................................................................................. 9

   5.1.7.        Projects Module ............................................................................................................................ 9

   5.1.8.        Contacts Module ........................................................................................................................... 9

6. User Role Requirements ......................................................................................................................... 10

   6.1.1.        Manager ...................................................................................................................................... 10

   6.1.2.        Tenant ......................................................................................................................................... 10

   6.1.3.        Guest ........................................................................................................................................... 10

7. System Requirements ............................................................................................................................. 11

   7.1.1.        Server Requirements .................................................................................................................. 11

   7.1.2.        Client Requirements ................................................................................................................... 11

8. Usability Requirements ........................................................................................................................... 12

   8.1. Functional Requirements .................................................................................................................... 12

   8.2. Form Requirements ............................................................................................................................ 12

   8.3. User Scenario Based Requirements .................................................................................................... 13

Appendix ........................................................................................................................................................ 14

Usability Requirements Testing ..................................................................................................................... 14

   User Type Questionnaire ........................................................................................................................... 14

   User Satisfaction Survey ............................................................................................................................ 15




                                                                                                                                                        Page | 3
Introduction

1. Objective

Our program is called *Properties, it’s a client-server based environment for the administration
and management of rental properties. The system will allow building managers, maintenance,
tenants and potential tenants to access the system with appropriate permissions to view and
manage properties and associated actions.


Constraints/Risk Management

2. Constraints
   2.1. Valid Emails Address – Users must have a valid emails address and it must be confirmed
        upon account creation
   2.2. Web site Security/Privacy – Users must accept the security levels set by the web site
   2.3. Rental application and documentation are limited to the laws of the state in which the
        property is located
   2.4. *Star Properties in not responsible or liable for inaccuracies or lawsuits resulting from
        the use of our website



3. Risk Management
   3.1. Bandwidth – Ensure that servers have adequate bandwidth. Need to monitor and test
        on a regular basis. Reporting will be provided
   3.2. System Outages – Ensure redundancy is built to prevent and minimize outages.
        Monthly “Fail Over” tests including complete shutdown of primary site and restore of
        system data will be done on a bi-monthly basis
   3.3. Backup media will be stored off site on a daily basis. Off-site electronic backup will be
        completed on a weekly basis. Customers will have the ability to backup their data
   3.4. Any functionality not explicitly listed in this document can be implemented for an
        agreed upon development fee. Once complete, this functionality is available to all
        customers




                                                                                           Page | 4
Requirements

4. Business Requirements



     4.1.1. System Availability
        4.1.1.1. The system must be available 24/7, 365 days a year
        4.1.1.2. The system must achieve a 99% uptime ratio, Tested by calculating total
        uptime over operational hours
        4.1.1.3. The system must have a site replication in case of outages
        4.1.1.4. The system must have robust backups for potential data lose and fast
        restoration of records
        4.1.1.5. The system application can be backed up for restoration in another site
        or the same after a disaster
        4.1.1.6. Test: Run redundant server and backups tests bi-monthly. ensure the
               backups are operational by restoring the data and running on backup
     4.1.2. System Performance and Maintenance
        4.1.2.1. Must be able to track system performance such as processor usage, site
        traffic From administrator console, view directly or link to web site statistics
        4.1.2.2. There must be a maintenance window of .5 hours/day. The application
        can be shut down for various upgrades and changes for .5 hours per night
        4.1.2.3. The application must take less than 7 hours of maintenance per week.
        The total time an operator will need for backups and operational support of the
        application will take less than 7 hours per week. Operational Support involves all
        work not related to business functions such as, but not limited to; Backups,
        Upgrades, Scheduled Jobs, Log Verification
        4.1.2.4. Test: ensure maintenance is scheduled on off hours and that site is being
        monitored and tracking is enabled with the site tools
     4.1.3. Accessibility
        4.1.3.1. The system must be accessible over the Internet and easy to use.
            4.1.3.1.1.  Tests will be done timing specific functionality
        4.1.3.2. The system must be accessible in the English Language
        4.1.3.3. The system must be accessible over IE and Firefox
        4.1.3.4. Test: ensure the site has usability testing and that all browsers are tested
     4.1.4. Security
        4.1.4.1. The system must use encryptions across any page that is transmitting any
        sensitive login/password, personal information or payment information
        4.1.4.2. The applications hardware would be stored in a secure environment.
        Secured environment refers to a location with a dual authentication, temperature
        controlled room, 24/7 security, 24/7 onsite support. This location will have power


                                                                                      Page | 5
   feeds from multiple suppliers entering the building from different directions. Power
   to the control room will also be supplemented with generated power.
   4.1.4.3. T he system must contain a logout button on every page
   4.1.4.4. The system must require a valid email address be used a the login
       4.1.4.4.1.     Validity will be determined by sending a users password to that
                email
   4.1.4.5. A complex password of numbers and characters must be required.
       4.1.4.5.1.     Complex is defined as containing one number and one non alpha-
                numeric character. The password will be a minimum of 6 characters
                long
   4.1.4.6. Test: Ensure the site has SSL encryption, and that every page is protected
   and ensure the server room is locked and monitored for entry access
4.1.5. Toolbars
   4.1.5.1. The Main Toolbar should contain the following links: Login/out, Home,
   Contacts, Search Properties, and Documents. When clicked, these links will redirect
   the browser to the associated site
   4.1.5.2. Test: ensure the toolbar is consistent across the all pages
4.1.6. User Roles
   4.1.6.1. The System must have three distinct access roles, Manager, Tenant and
   Guest. Each role must have security a configurable setup for proper module access.
   4.1.6.2. Test: ensure the roles are defined and documented. Login with different
   roles and test accessibility and functionality with each role.
4.1.7. Training Manual
   4.1.7.1. A training manual will be provided that includes examples of common
   task, operation processes, and a troubleshooting guide. Collateral will be reviewed
   by executive committee.
   4.1.7.2. Test: ensure the training manual is reviewed with usability testing




                                                                                Page | 6
5. Functional Requirements

Property managers will be able to login to the website and select the buildings they manage,
and view units and tenants. It will also allow guests to search available units on the site.
Managers and tenants will have a secure login enabling them to select/perform appropriate
tasks and functions based on their access level. Only managers will be able to add, delete, and
change the content of the system. Below is a detailed layout of the different system functions


       5.1.1. Homepage
           5.1.1.1. The system must have a login/password boxes
           5.1.1.2. The system must have a password reminder link
           5.1.1.3. The system must display the main links toolbar across the top
           5.1.1.4. The system must display corporate logo in all pages and be located in a
           consistent place across all pages
           5.1.1.5. Test: ensure that all pages are accurate and consistent. Must present a
           previously agreed upon uniform look/design

       5.1.2. Property Module
           5.1.2.1. The system must allow this module to be available to guests. No Login
           required to view page
           5.1.2.2. The system must allow users to login in order to define their user roles
           for proper access
           5.1.2.3. The system must allow searching, view of all building, units and parking
           for all roles
           5.1.2.4. Test: ensure each user role has adequate access and that user roles are
           setup with only applicable permissions.
           5.1.2.5. The system must allow only managers to post forms
           5.1.2.6. The system must allow only managers to post available building, units
           and parking information
           5.1.2.7. The system must allow only managers to post picture data in jpg format
           on all buildings, units and parking
           5.1.2.8. The system must allow managers to post contact information on
           buildings, units and parking that is posted.
           5.1.2.9. Test: Ensure only managers can post forms, picture data and contact info
           5.1.2.10. The system must allow tenants to view available building, units, parking
           information and pictures
           5.1.2.11. The system must allow tenants to post forms
           5.1.2.12. The system must allow tenants to contact management via contact links


                                                                                        Page | 7
   5.1.2.13. The system must allow tenants to view available building, units, parking
   information and pictures via a query
   5.1.2.14. The system must allow tenants to post forms
   5.1.2.15. The system must allow tenants to contact management via contact links
   5.1.2.16. Test: ensure that tenants can post forms, view contact info and review
   units and building information
5.1.3. Alerts Module
   5.1.3.1. The system must allow this module to be available to logged in users only
   5.1.3.2. The system must allow users to login in order to define their user roles
   for proper access
   5.1.3.3. The system must allow managers to post, view and respond to alerts via
   email and/or PDA
   5.1.3.4. The system must allow tenants to view and respond to alerts via email
   and/or PDA
   5.1.3.5. The system will send email or text notification to the submitter of a ticket
   or application and to all subscribed managers
   5.1.3.6. Test: ensure that all alerts are posted and can be received via email and
   SMS alerts. Ensure that managers can review and respond.
5.1.4. Tenants Module
   5.1.4.1. The system must allow this module to be available to logged in users only
   5.1.4.2. The system must allow users to login in order to define their user roles
   for proper access
   5.1.4.3. The system must allow tenants to update personal information
   5.1.4.4. The system must allow tenants to make payments and track status
   5.1.4.5. The system must allow tenants to complete forms and applications
   5.1.4.6. The system must allow managers to post and view completed forms and
   applications
   5.1.4.7. The system must allow managers to view and update tenants personal
   information
   5.1.4.8. The system must allow managers to view and post payments
   5.1.4.9. Test: ensure that all tenants can update information, post and track
   payments and that managers can view the information and post payment status
5.1.5. Tickets Module
   5.1.5.1. The system must allow this module to be available to logged in users only
   5.1.5.2. The system must allow users to login in order to define their user roles
   for proper access
   5.1.5.3. The system must allow tenants to create, modify and track tickets
   5.1.5.4. The system must allow managers to create, modify, track and close
   tickets
   5.1.5.5. Test: Ensure that tenants and managers can create tickets. Test that
   managers can respond and close tickets. Test that guests do not have access to the
   Tickets Module

                                                                                Page | 8
5.1.6. Administration Module
  5.1.6.1. The system must allow this module to be available to managers only
  5.1.6.2. The system must allow users to login in order to define their user roles
  for proper access
  5.1.6.3. The system must allow managers to create and define user roles
  5.1.6.4. The system must allow managers to access software support
  5.1.6.5. Test: Ensure that managers have full access to the module and can create
  and define roles, have access to support. Ensure Tenants and Guests do not have
  access to this module
5.1.7. Projects Module
  5.1.7.1. The system must allow this module to be available to managers only
  5.1.7.2. The system must allow users to login in order to define their user roles
  for proper access
  5.1.7.3. The system will allow managers to create and manage large projects
  5.1.7.4. The system must allow managers to create sub task for projects
  5.1.7.5. The system must allow linking of contacts
  5.1.7.6. Test: Ensure managers can create project pages and create sub task.
  Ensure the link is enabled for contacts access.
5.1.8. Contacts Module
  5.1.8.1. The system must allow this module to be available to logged in users only
  5.1.8.2. The system must allow users to login in order to define their user roles
  for proper access
  5.1.8.3. The system will allow logged in tenants to modify their info only
  5.1.8.4. The system will allow managers to add, delete, or modify any contact
  5.1.8.5. The system will allow managers to print one, some, or all contacts
  5.1.8.6. Test: Ensure tenants and managers have access. Test that tenants can
  only create and modify their own. Test that managers can modify all contacts in the
  system. Verify printing format matches a pre agreed upon format.




                                                                              Page | 9
6. User Role Requirements



     6.1.1. Manager
        6.1.1.1. The system will allow a logged in manager to access all modules of the
        site.
        6.1.1.2. The system will allow a logged in manager to add, delete, or modify
        Contact and Property information. Information is descried as the attributes of
        Contacts and buildings.
        6.1.1.3. Test: Ensure Managers access to all listed modules. Ensure managers
               have the ability to add, modify, and delete data
     6.1.2. Tenant
        6.1.2.1. The system will allow a logged in tenant to access the Property, Alerts,
        Contacts and Tickets modules.
        6.1.2.2. The system will allow logged in tenants to add and modify information
        that was created from their account.
        6.1.2.3. Test: Ensure Tenants access to Property, Alerts, Contacts and Tickets
               modules.
     6.1.3. Guest
        6.1.3.1. The system will allow a guest to contact via email *Properties.
        6.1.3.2. The system will allow a guest to search for available rental units
        6.1.3.3. The system will allow the guest to submit an application
        6.1.3.4. Test: Ensure Guests access to view properties, apply for properties and
               send an email requesting information




                                                                                   Page | 10
7. System Requirements



     7.1.1. Server Requirements
        7.1.1.1. Server application must run in a Microsoft server 2003 environment with
        IIS 6.0 or later, running ASP.NET 3.5
        7.1.1.2. Server application must be coded in C#
        7.1.1.3. Server rendered code must be w3c compliant
        7.1.1.4. Test: Applications run in stated environment and the coding is compliant
        with the listed requirements.
     7.1.2. Client Requirements
        7.1.2.1. Client application must be platform agonistic
        7.1.2.2. Test: connect to server from Firefox, IE 6, 7, Links, Safari, on Windows XP,
        Vista, OSX, Ubuntu, Gento
        7.1.2.3. Client application must not rely on client side scripting.
        7.1.2.4. Test: Disable client-side scripting in Browsers and ensure web
        functionality persists




                                                                                    Page | 11
8. Usability Requirements



  8.1. Functional Requirements
     8.1.1. Ease of Learning
         8.1.1.1. System must be easy to learn for both novices and expert users
             8.1.1.1.1.     Test: This will be measured by meeting the user scenario based
             requirements below
     8.1.2. Task Efficiency
             8.1.2.1.1.     System must be efficient for the frequent user
         8.1.2.2. Test: Requirement will not pass until during user testing of expert users
         measure the system efficient, by a 90% confidence interval. Testing form is included
         in appendix
     8.1.3. Ease of Remembering
             8.1.3.1.1.     System must be easy to remember for the causal user
             8.1.3.1.2.     Test: Requirement will not pass until during user testing focus groups of
             novice users measure the system easy to remember, by a 90% confidence interval.
             Testing form is included in appendix
     8.1.4. Understandability
            8.1.4.1.1.      User must understand what the system does
            8.1.4.1.2.      Test: Requirement will not pass until there is an 85% confidence
            interval that all users tested during focus groups rate the system
            understandable. Understandability testing form included in appendix
     8.1.5. Subjective Satisfaction
            8.1.5.1.1.      User must feel satisfied with the system
            8.1.5.1.2.      Test: Requirement will not pass until there is an 85% confidence
            interval that all users tested during focus groups feel satisfied with the system.
            Satisfaction testing form included in appendix




  8.2.Form Requirements
     8.2.1. User must be able to quickly enter information into form fields
     8.2.2. System must have intelligent data entering capabilities that remember
     previously stored data.
     8.2.3. System must have the ability to automatically save data that has been entered to
     prevent data loss. System will automatically save data on a periodical basis such as every
     30 seconds
                                                                                           Page | 12
  8.2.4. If user’s connection to *properties is temporally disconnected for any reason,
  the system must save all data entered.
  8.2.5. If the user accidentally hits a button that navigates elsewhere the system must
  have saved all data entered.
  8.2.6. If user closes out of the internet browser the system must have saved all data
  entered.
  8.2.7. Test: Requirement will not pass until a tester is able to enter in data that has
  previously been entered and have it successfully recognize the word from the first 3
  letters typed
  8.2.8. Test: Requirement will not pass until a tester can verify that when text was
  entered into a data field without being saved. Tester must exit program, then re-open
  program and verify unsaved data was automatically saved by system.


8.3.User Scenario Based Requirements
     8.3.1.1. User must be able to create and setup their account within 10 minutes
     8.3.1.2. User must be able to login on the first try after creating account 98% of
     the time.
     8.3.1.3. User must be able to access help files at every single stage of each
     process
     8.3.1.4. Help files must contain screen shots of the relevant process and module
     in question
     8.3.1.5. Software must have two interfaces one for simple mode and one for
     advance mode
     8.3.1.6. Simple mode must have all basic functions
     8.3.1.7. Advance mode must all users to further customize their experience by
     offering a multitude of features. This includes analysis features, database backup,
     website development, reporting.
     8.3.1.8. User must be able to customize the user interface, including buttons and
     layouts
     8.3.1.9. User must be able to add additional features and templates from our
     website
     8.3.1.10. User must be able to add additional features from outside sources
     including open source and 3rd party software
     8.3.1.11. User must have the ability to make their own tools and features
     8.3.1.12. Test: This will be tested by conducting user testing. Specifically by taking
     a sample of probable users who will receive instructions on how to sign up an
     account. Participant will then be asked to setup an account. The amount of time it
     takes will be recorded. This requirement will not pass until there is a 98% confidence
     interval



                                                                                  Page | 13
Appendix

Usability Requirements Testing

User Type Questionnaire

PART 1

Name: ___________________________________________________ Contact #: _________

Email: ___________________________________________________

Your current position: ________________________________________________
Number of years in this position: ___

PART 2

How much experience have you had with the following types of computers and computer devices?
Mac                      ___ Years      ___ Months
PC or Compatible ___ Years       ___ Months
Laptop                   ___ Years      ___ Months

About how many hours a week do you use a computer?
At home: _____________          At work: _____________

What type of computer do you use?
At home: _____________           At work: _____________

Do you use Microsoft Windows?             Yes ___          No ___

Do you use Microsoft Office               Yes___                    No___

What Windows applications have you used?:
Product name:
1.                                      ___ Years          ___ Months
2.                                      ___ Years          ___ Months
3.                                      ___ Years          ___ Months

What do you typically use your computer for?

___      Games and Pleasure               ___       Graphics
___      Accounting/Finance               ___       Data storage (i.e., data bases)
___      Word Processing                  ___       Other ___________________________
___      Decision Support                 ___       Other ___________________________




                                                                                               Page | 14
User Satisfaction Survey




                                         Usability


Would you recommend this software to other people?                                       0 Yes 0 No

If you answered Yes, please complete the following section.

                                                          Far                               Far
Please indicate your level of satisfaction                                                    Exc
                                                                                              eed
                                                         Below      Below   Meets Exceeds       s      N/A
                                                                                              Exp
                                                                                              ecta
                                                        Expecta-
                                                                                                -
                                                            tions
                                                                                              tion
                                                                                                s
     The overall satisfaction of the system                0         0       0       0      0           0
     Did system meet your expectations                     0         0       0       0      0           0
     How satisfied were you the with help files            0         0       0       0      0           0
     How satisfied were you with the features offered      0         0       0       0      0           0
     Did system meet your expectations of ease of use      0         0       0       0      0           0


What specifically about the system were you satisfied with? What specifically about the
  system were you dissatisfied with?
  ______________________________________________________________________
    _________________________________________________________________
    _________________________________________________________________
    _________________________________________________________________
    _________________________________________________________________
    ________________




                                                                                                     Page | 15

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:16
posted:3/7/2012
language:Latin
pages:15