; CSCI Resource Reservation Application
Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out
Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

CSCI Resource Reservation Application

VIEWS: 26 PAGES: 24

  • pg 1
									CSCI Resource Reservation Application




                           Binbin Zhang, Scott Beck,
                       Yumiko Togashi, & Kyle Bellair


                  Purdue School of Computer Science,
                          Computer Science Program
                                     CSCI Internship
                                         Bob Molnar
                                    December 4, 2003
                                 Table of Contents


Project Plan …………………………………………...…..…………………………..…..5
    This section includes:
           1. Overview
           2. Concepts and Methodology
           3. Assignment
           4. Deliverables
           5. Timing
           6. Resources

Requirements Document ………………………...……………………………....…..9
    This section includes:
           1. Introduction
           2. Interface Requirements
           3. Input Requirements
           4. Output Requirements
           5. Database Requirements
           6. Documentation Requirements
           7. Operational Requirements

HIPO Chart………………………...…………………………………………………....…..12
    This section includes:
           1. HIPO Chart: Main
           2. HIPO Chart: Input Users
           3. HIPO Chart: Input Administration
           4. HIPO Chart: Outputs

Test Plan……………………..…...……………………………………………………...…..17
    This section includes:
           1. Purpose of the Test Plan
           2. Problem Statement and Test Objectives
           3. User Profile
           4. Test Methodology
           5. Test Design
           5. Test Environment/Equipment
           7. Roles of the Team Members
           8. Evaluation Measures
           9. Report Contents and Preparation

Test Data log..………………….………..………………..………………..……………….24
    This section includes:
           1. Purpose
           2. Problem Statement
           3. Methodology and Test Settings
          4. Background Information




    Section 1 : Task Analysis Study…………………………..………………………..…..26
    This section includes:
           1. CIA Report
           2. Usability Research Documentation
           3. User Profile Questionnaire/ results
           4. Timing matrix
           5. Post Videotaping Interview of Users

    Section 2 :    Information Architecture Study………………….………….……...…...38
    This section includes:
           1. HIPO Chart
           2. Further Conclusions

    Section 3 :    Prototyping Study………………………………………………….….…...41
    This section includes:
           1. Prototype Site
           2. Findings and Recommendations

    Section 4 :    Post Design Study…………………………………………………..….….45
    This section includes:
           1. User Profile Summary
           2. Post-task Questionnaire
           3. User Found Problems
          4. Conclusions

    Section 5 :    Report Summary………………………………………………….…./...….50
    This section includes:
           1. Conclusions
           2. Recommendations
           3. Final Remarks

System Documents …….…...…………………………………………………..….…..52
    This section includes:
           1. Syste m Administration Guide
           2. Data Dictionary
           3. Application Algorithms

    Section 1 :    System Administration Guide………………….……………….…..…...53
    This section includes:
           1. Introduction
           2. Administration Applications
           3. Calendar Applications
           4. Code Comment
           5. Database Information
   Section 2 :    Data Dictionary…………………………………………………….…..….59
   This section includes:
          1. Program Modules

   Section 3 :    Application Algorithms……………………………..…………….…..….71
   This section includes:
          1. Calendar Reservations
          2. Administration Functions
          3. Calendar functions

Manuals…….…...……………….………………..…………………………….…..….…..88
   This section includes:
          1. Administration Manual
          2. User Manual



   Section 1 :   Administration Manual………………….…………..…………….…..….88



   Section 2 :   User Manual………………………………….………..…………….…..…119




Appendix …….…...…………………………………………………………………..….…141
   This section includes:
          1. Requirements Interview Document
          2. Signed Requirements Document
          3. User Profile Questionnaire
                  A. Clients
                  B. Users
          4. Timing Matrix
          5. Post Task Questionnaire
                  A. Clients
                  B. Users
          6. Post-Videotaping Interview Questionnaire
                  A. Clients
                  B. Users
          7. Authorization for Videotaping
          8. Task List
          9. Code-on CD
         10. CSCI Resource Reservation Application Documents CD
         11. Recorded Test Videotape
CSCI Resource Reservation Application




     Project Plan
Project Plan
I.     OVERVIEW

This Product will be built with a web based programming language. The application will be a
scheduling program to log and reserve equipment and rooms with in the CSCI department. The
application will begin with an email and login for people involved with in the CSCI department. It
will allow a user to define equipment and rooms that need to be reserved. Also, the application will
send email notifications to renter and owner about the specified item needed. The application will
create a log of all equipment/rooms that have been rented or used for future analysis and data
collecting.

This application will list in detail all items and rooms available for use so the user may specifically
choose the exact item needed. The application will send an email to the user that a reservation has
been completed and also an email to the owner as a reminder to make sure the item or room will be
ready on time of pick up. The administrator receives an email every 24 hours to get the list of
reservations for the current day.

The application will be direct to the point and easily understood by the user. A very basic output so
there will be no question to the user on what he/she needs to be reserved.

This application will alleviate the need for the traditional pen & paper method of logging and keeping
track of equipment and rooms that need to be used.

II.    CONCEPTS AND METHODOLOGY

Interview clients and requirements gathering
Requirements review from clients
Determination of tools used (server, programming languages)
Coding and debugging
Testing
Reviewing system from clients
Developing
Documentation
Release


III.   ASSIGNMENT

The steps and descriptions of the system development are flexible to change
in order to satisfy the client’s demand. Basically, all of us will analyze and
develop the system to be consistent with the client’s needs.

All of us will be responsible in determining how we will design the system and
use web-building technologies such as HTML, JavaScript, and DHTML. BinBin and Scott will be
responsible in structuring server-side coding including PHP. Also, BinBin and Scott will be
responsible in database development and architecture by using MySQL. Kyle and Yumiko will be
responsible in test planning. Test plans will help us identify what need to be tested, what has
already been tested, how a test was performed, and the progress of the overall
testing before showing the system to clients, so testers will be all of us and
others in order to find any problems without prejudice. All of us will be
responsible in producing necessary documentations including user’s manual to
find problems and solutions for the system development.

IV.   DELIVERABLES

The product to be delivered by this team is to be a software solution for use by the Computer Science
Department to aid in the process of scheduling equipment and rooms for use by faculty, staff and
students of that department. The interface will be web based and accessible through simple password
protection. The data will be maintained in a relational database with the ability for the administrator of
the system to access for general maintenance. Full documentation for the system will also be provided.

V.    TIMING

      Beta Version Release – 11/06/2003
      Code Freeze – 11/13/2003
      Final Version Release – 11/24/2003




VI.   RESOURCES

This project will require an account to be set up on the Shelob server at IUPUI for access by this team.
Working on Shelob dictates that our database development is done with PHP. As a team, we bring
experience in a variety of programming languages and web development tools including PHP,
JavaScript, Java, HTML and DHTML from which we can draw in the development of this software
package. We also have at our collective disposal access to a variety of digital imaging equipment and
software.

       Human Resources:

               Cindy Lester – CSCI Secretary
               Scott Orr – CSCI System Administrator
               David Tauriainen – CSCI Assistant
               Bob Molnar - Advisor



       Book Resources:

               Asp.net and VB.net Web Programming. Matt J. Crouch.
               Cascading Style Sheets The Definitive Guide. Eric A. Meyer.
Core PHP Programming. Leon Atkinson
Database Management Systems. Ramakrishnan Gehrke.
Designing with JavaScript. Heinle & Pena.
JavaScript Programming for the Absolute Beginner. Andy Harris.
JavaScript The Definitive Guide. David Flangagan.
MySQL and Perl for the Web. Paul DuBois.
Perl and CGI for the World Wide Web. Elizabeth Castro.
PHP / MySQL for the Absolute Beginner. Andy Harris
Programming and Problem Solving with Java. Nell Dale, Chip Weems,
                                             Mark Headington.
Sams Teach Yourself Java 2 in 21 Days. Rogers Cadenhead & Laura Lemay.
Sams Teach Yourself MySQL in 24 Hours. Julie C. Meloni.
The Engineering of Software. Dick Hamlet & Joe Maybee.
Web Design in a Nutshell. Jennifer Niederst.
CSCI Resource Reservation Application




   Requirements
    Document
Requirements Document
Introduction:
The Scheduling Software Project Team recently conducted an interview with our primary customers to
find out what they felt was important to be included in a software solution for scheduling rooms and
equipment for use by faculty, staff and students of the CSCI department at IUPUI. The purpose of this
document is to identify the requirements of that software to meet the needs as identified in these
interviews.

The requirements identified for this project can be broken down into several categories including
interface, inputs, outputs, database, documentation and operational.

Inte rface Require ments:
The application is to be an Internet based application with an easy to understand and easy to use user
interface. The interface is to contain an area where the requester can input their personal information
and the needs for rooms and/or equipment. The interface will also require an administrative area for
database manipulation and management, calendar retrieval and if time permits in the design phase,
report generation. Report generation was deemed to be a "nice to have if time permits." The interface
should make use of menus; pull down lists, check boxes, radio buttons or other form selection
techniques that make the process as easy as possible for the user.

Input Require ments:
The interface will provide an opportunity for the user to enter all necessary information pertaining to
the request including but not limited to the following items:
-*Email address of requester
-*Equipment needs – For equip reservation
-*Room needs – For room reservation
-*Date and time for pick up
-*Date and time for return – Needed for program functionality
        If request is for longer than 1 week, send instruction to call for reservation
-Special needs
-*Platform requirements – For room reservation
-*Size of group – For room reservation
-Cancel request (or instructions) – Only allow cancellation by confirmation number
For Admin
-Deny request automatically if conflict occurs
-Deny request if equipment / room becomes unavailable after requested
-Update capabilities for database

* denotes items that are required input for a request

Output Requirements:
The application will process the information input by the user and provide the following outputs:

-Notification to user that request has been processed and verified by email
-Notification if a conflict occurs
-Email confirmation to the requester that their request has been processed
-Email to the owner of the room or equipment letting them know about the request.
 -Instructions for pickup
-Email reminder to the owner on the day that the equipment is to be picked up.
-Email response to user if Admin denies request
-Calendar output

Database Require ments:
This application is to use a relational database, which will contain the following information:
-Contact information (phone, *email)
-Users and passwords
-Equipment descriptions
-Rooms and capacity and platform information
-Owner information – Include instructions for pick-up
-Reservation log – Store confirmation number with log entry
-Any other information, not yet identified that is necessary for the functionality of the software.

Documentation Requirements:
The project team is also responsible for delivering documentation containing a detailed description of
the software code and instructions for how to use the software.

Ope rational Requirements:
In general, this application will provide an interface that will be accessed via the Internet. A user will
enter their email address then choose from the various room and equipment options depending on their
needs. They will then be required to enter the date that they need the reservation for and when the plan
to return equipment if applicable. There will also be the ability for the user to identify special needs.
Finally the user will click on a button or link to process their reservation request at which time they
will receive a message informing them either that their request was successfully processed or that there
was a conflict with their request. Also for reservation needs that exceed one week (or some agreed
upon length of time) the user will be informed that they need to contact Scott Orr’s office directly to
make long-term arrangements.

Once the request has been processed, the system will email the requester with a confirmation number,
which will be used for cancellation of the request if needed, and instruction on pick-up of equipment.
The system will also email the owner of the requested item to let them know of the request. It is also
planned at this time that an email reminder will be sent to the owner on the day of pickup as well.

There will be a database table used to record reservation information. This table will be accessed by a
calendar function that will output some sort of graphical monthly output to show the administrative
users when there are reservations that need to be fulfilled. Additionally, there will be an administrative
interface to allow additions, removal and modifications to the database tables. This functionality will
be password protected.




Accepted:_________________________                    Date:_______________
CSCI Resource Reservation Application




      HIPO Chart
CSCI Resource Reservation Application




        Test Plan
Test Plan
       The purpose of the scheduling application test is to collect information about how users use this
web-based scheduling application and whether they experience any difficulties with this application, so
the improvements can be made.

       This test plan describes:
        The problems to be tested and our strategies for addressing them
        The participants
        Our test methods
        The tasks to be tested
        The task environment
        The roles of our team members
        The evaluation measure we will use
        The materials and other deliverables we plan to provide with the final report des cribing the
          usability test results.

       The purpose of testing was to determine:
        Whether or not this application easily and quickly provides graduate students in Computer
          Science Department
        User’s overall knowledge and perception of the application before and after reviewing the
          application



Proble m State ment and Test Objectives

        We will do this scheduling application test in order to gain data addressing user’s concerns
about the application’s usability. We will test difficulties of the following tasks:

<For room or equipment requesters>
        Logging in and out of the application
        Reserving rooms and equipments
        Putting date and time for pick up and return
        View calendar to make sure whether the reservation was made
        Check availability for equipment
        Modify reservation (time for pick up) by confirmation number

<For administers>
        Logging in and out of the application
        Update information of owners / users
        Adding a new user and delete the user
        Check particular date’s reservation
        Check availability for equipment / room
       To know user’s perception about the application, we should also focus on users’ perceptions.
These include:
        How users actually uses the application
        How users feel to interface design (color, layout, etc.)
        How users feel to navigation
        The level of effort required to use this application
           (How easy and difficult it is for users to use the application)
        Satisfaction with the application
        Perceived reliability of the application
        Perceived speed of using the application

       The focus of the research will be task oriented and directed toward how the user subjectively
responds to the issues listed above. Tests will be held with test team (Advising team) to test usability
and these issues.

       The test will be designed to allow us to gain verifiable data about usability. Participants will be
given some questionnaires designed to extract detailed and specific feedbacks about features of this
application, and post-test surveys to rate the usability of this application overall.

       Here is a table of test’s participants and task to be tested:

                    Tasks                           Users-Requester        Administrator
                                                    (Advising Team)          (Faculty)
Log in and out of the application                          √                     √
Reserve rooms and equipments                               √
Put date and time for pick up and return                   √
View calendar                                              √
Check availability for equips / rooms                      √                      √
Modify reservation with confirmation                       √
number
Update information of owners / users                                              √
Add a new user and delete the user                                                √
Check particular date’s reservation                                               √
User Profile

       Users of this application consist of requesters and administrators. Requesters consist of
graduate students majoring Computer Science. Administrators consist of faculty and staff in CSCI
department.

        Participants of this test will come from the following groups: students and clients. All
participants will have at least a High School education and will ideally be either pursuing or have
completed an advanced degree. Students are from Advising Application team. They are going to have
testing as users (requester). Clients are faculty and staffs in CSCI department. They are going to have
testing as administrators. Participants are expected to have at least minimal computer skills requested
to use this application.


   Test Methodology

       The test will consist of a performance test made of four sections:

        1.      User Profile Questionnaire & Authorization for video-recording
        The participants will be asked to fill out a short pre-study questionnaire, which gathers
background information. We will also ask the participants for authorization for video recording. If we
get authorization, we will ask them to sign a sheet.

       2.    Testing Instruction
       We will briefly explain testing instruction for this application.

        3.      Performance Test
        We will ask the participants to do five tasks. We will tell each question after the participant
finishes each task. We will count time of each task. During testing, we will record and observe the
participants.

       4.      Post-Test Questionnaire
       The participants will be asked to fill out a short port-test questionnaire, which gathers
information of usability of this application.

       5.     Short Intervie w
       The participants will be asked some questions about overall of this application.
The questions will be:
    Participant’s overall agreement with this application.
    Participant’s comments and recommendations regarding navigation and interface design.
    Participant’s responses about specific errors or problems that occurred during the test.
Test Design

        We will provide the participants with descriptions of each task. However, we will not provide
specific detailed instruction on how to accomplish the designated task in order to see usability of this
application. We will provide scenario lists below.

       For users (requester)

       Task 1:
           Log in
        Reserve equipment / room with specific day and time for pick up and return

       Task 2:
                      View calendar to see previous reservation

       Task 3:
        Check availability for equipments

       Task 4:
        Modify availability for equipments with confirmation number


     For administrators

     Task 1:
       Log in
       Update information of administrator

     Task 2:
       Add a new user
       Delete the user

     Task 3:
       Check reservation at particular date

     Task 4:
       Check availability for equipment / room
   Test Environme nt / Equipme nt

       The testing room is furnished with the following equipment:
        Video cameras, allowing filming of participants from various perspectives and angles
        A desk on which computer equipment can be set up to simulate a work environment
        A Pentium computer running Windows 98/2003/XP with Netscape Communicator or
          Internet Explorer software
        Internet connection



   Roles of the Team

       Our team consists of four members. We will perform specific tasks, however, it is also
necessary to perform varied duties as required.

      Briefer: We have assigned a briefer who will explain the test activities to the participants and
who will administer the questionnaires.

       Camera Ope rator: One team member will operate all of the cameras.

       Recorder / Observer: Observer will make observations about test event and ask interview.

       Test Administrator: One team member will be responsible for overall coordination and
troubleshooting duties.



   Evaluation Measures

       The evaluation measures will be a combination of quantitative meas urements and subjective
observations. The quantitative and qualitative data measures are listed below:

       Quantitative Data
        Time to completion of each task
        Number of participants completing tasks within allocated time
        Number of problems encountered
        Number of errors (includes unsuccessful tries)
        More than three errors per task indicated a potential usability problem
        Number of local problems

       Qualitative Data
        Facial expressions
        Verbal comments when they think
        Spontaneous verbal expressions (comments)
        Interviews before the test
         Interviews after the test
         Miscellaneous activities (stretching, wanting breaks, etc.)


Report Contents and Preparation

      The report will be presented in a formal report format with the following sections:
          Cover letter
          Title page
          Executive summary
          Contents
          Discussion of the background of the project
          User profile
          Description of the planning phase with estimated and actual work hours
          Description of the test (methods and tasks)
          Collected data (both quantitative and qualitative)
          Analysis of the collected data
          Recommendations on the basis of analyzed data
          Appendices (questionnaires etc.)

								
To top