Dentist Advertising Budget - DOC

Document Sample
Dentist Advertising Budget - DOC Powered By Docstoc
					                    FRED

     Software Requirements Specification




     2002 MSE-Carnegie Mellon University




i
                                Revision History
Date        Revi sion   Description                             Author
02/05/ 02   1.0         Initial Version                         Ed Neubecker
2/27/02     1.1         Updates from the S RS inspection of     Ed Neubecker/ Poornima
                        2/22/02                                 Bharathy
3/7/02      1.2         More updates to SRS                     Ed Neubecker/ Poornima
                                                                Bharathy
3/21/02     1.3         Final edit before delivery              Mike Lester
4/8/02      1.4         Made changes after walk-thru w/ Scott   M.L.




                                          Signatures
Date        Signature




                                               ii
                                                 Table of Contents

1       PURPOSE ........................................................................................................ 1
1.1     SCOPE ........................................................................................................................ 1
1.2     D EFINITIONS ................................................................................................................ 1
1.3     OVERVIEW ................................................................................................................... 1
2       GENERAL DES CRIPTION.......................................................................................... 2
2.1     PRODUCT P ERSPECTIVE ................................................................................................ 2
2.2     PRODUCT FUNCTIONALITY /FEATURES .............................................................................. 2
2.3     R EQUIREMENT GATHERING P ROCESS .............................................................................. 3
2.4     USER C HARACTERISTICS ............................................................................................... 3
2.5 CONSTRAINTS .............................................................................................................. 4
  2.5.1 Hardware Platform and Operating S ystem ............................................................ 4
  2.5.2 Budget Constraints ............................................................................................. 4
  2.5.3 Bandwidth Requirements .................................................................................... 4
  2.5.4 REDX server constraints ..................................................................................... 4
2.6 ASSUMPTIONS AND D EPENDENCIES ................................................................................. 4
    2.6.1       Advertisement Sources ....................................................................................... 4
3       FUNCTIONAL REQUIREMENTS ................................................................................ 5
3.1     TABLE T P C REQUIREMENTS .................................................................................... 5
    3.1.1       Necessary supporting soft ware pack ages............................................................. 5
    3.1.2       Patient privileges & restrictions ............................................................................ 5
    3.1.3       Administrative privileges ...................................................................................... 5
    3.1.4       Usability: Data entry, and navigation .................................................................... 5
    3.1.5       LOGI N information – (user profile) ....................................................................... 5
    3.1.6       GAMES .............................................................................................................. 7
3.2 REDX SERVE R RE QUIREMENTS .............................................................................. 7
  3.2.1 Server Cont ent ................................................................................................... 7
  3.2.2 Advertising - ....................................................................................................... 7
  3.2.3 Server Administration.......................................................................................... 8
3.3 EXTERNAL INTERFACE R EQUIREMENTS ............................................................................ 8
3.4 OTHER R EQUIREMENTS ................................................................................................. 8
4       NON-FUNCTIONAL REQUIREMENTS ...................................................................... 10
4.1     PERFORMANCE .......................................................................................................... 10
4.2     USEABILITY ................................................................................................................ 10
  4.2.1   Tablet Usability ................................................................................................. 10
4.3 R ELIABILITY ............................................................................................................... 10
  4.3.1   Reliability ......................................................................................................... 10
4.4 SCALABILITY .............................................................................................................. 10
  4.4.1 Capacity and Growt h ........................................................................................ 10




          iii
4.5 AVAILABILITY .............................................................................................................. 10
  4.5.1  Site Availability ................................................................................................. 10
4.6 MODIFIABILITY ............................................................................................................ 11
  4.6.1 Tablet modifiability ............................................................................................ 11
4.7 SECURITY AND PRIVACY REQUIREMENTS ........................................................................ 11
    4.7.1      Medical and personal information security .......................................................... 11
    4.7.2      Confidentialit y................................................................................................... 11
5       REQUIREMENTS QUESTIO N & ANSW ER S ESSIONS ............................................. 12
6       REQUIREMENTS TRACEABILITY ........................................................................... 15
6.1     U PWARD TRACEABILITY ............................................................................................... 15
6.2     DOWNWARD TRACEABILITY .......................................................................................... 15
6.3     R EFERENCES ............................................................................................................. 15




                                                                iv
Software Requirements Specification




1 Purpose
The purpose of this document is to communicate the requirements of the REDX system
being built for the MSE studio project.

1.1 Scope
This document will identify requirements and use cases for the system to be built, but
will not include requirements and specifications of external agencies such as server
hosting companies, providers of marketing data, or marketing consultants.

1.2 Definitions
General Advertisements - Internet advertisements with no criteria to determine the
targeted audience who will view the advertisements.

Targeted Advertisements - Internet advertisements with criteria to determine the
targeted audience who will view the advertisement.


1.3 Overview
RedX is a new high-tech startup company that promises to enhance the experience a
patient has while in the waiting room. Patients are generally asked to complete lengthy
medical forms before an appointment. RedX and FRED (MSE Studio Team, Carnegie
Mellon University) will develop a hand-held wireless solution that allows patients to
complete these forms on- line. The aim is to provide the patient with some entertainment
as well as to create a market for targeted advertising. For this purpose, it is essential to
identify the most important features, functions, and requirements.
                  .




  Software Requirement Specification                Date                    Rev        Page
                                                    11/22/2010 6:22:00 PM   1.2        1
Software Requirements Specification




2 General Description
2.1    Product Perspective



                                                             RedX Server
                                                             (Data store)



                                                     Office
                                                     Internet
                                                     Gateway




                     Figure 1: Dentist‟s office


2.2 Product Functionality/Features
This product has two principal functions:
   1. To attract users to watch Internet advertisements (providing revenue to RedX)
       while also providing an “info-tainment” service to the user.
   2. To replace paper insurance forms that need to be filled out or updated each time a
       patient enters a waiting room of a dentist or a doctor.

The „Tablet PC‟ will be the device that is used to interface with the patient in the waiting
room. The patient will first use a tablet to update personal information. Next, the user will
update medical/dental information. Finally, the user will be able to use the tablet as an
“infotainment” device to browse the internet, review information about their doctor, or
play games. While the user uses the tablet, it will display advertisements targeted
towards that particular user based on the user information they provided. The income
generated from advertisements will be shared with the doctor‟s office as incentive to
make the tablet system customary in the waiting room.

The Tablet PC(s) will connect to the internet via an on-site wireless router connected to
the dentist‟s Internet Service Provider. (A wireless network card will be installed in each
tablet.) RedX.com will be the default home page for the tablet‟s browser-based
application, which will allow the user to fill out dental/medical forms before showing the
site‟s main menu. RedX.com will also serve as the internet portal for the user.
  Software Requirement Specification               Date                     Rev       Page
                                                   11/22/2010 6:22:00 PM    1.2       2
Software Requirements Specification




                                                                         Conduct Interviews


   Conduct Overview
       Meeting                                                                                               Document
                                                           Conduct Interview
                                                                                                            Requirements
                                                                                       Identify
                                Identify Questions                                Requirements from
                                                                                      Answers
                                                                                                              Identify &
                                                                                                              Document
                                                          Document Answers
                                                                                                           Acceptance Test
                                                                                                                Cases




                                                                        Collect Use-Cases



                                                                        Conduct Use-Case
                                                                            Session

                                             Identify Use-Cases
                                                                                               Refine Use Cases


                                                                          Document Use
                                                                             Cases




                                           Figure 2: Requirement Elicitation Process

2.3 Requirement Gathering Process
During the primary elicitation sessions, requirements, questions and answers, and use
cases were entered directly into a database for tracking. Both structured interviews and
use-case analysis were employed, following the high- level process diagram shown in
Figure 1.

2.4    User Characteristics
               End users : Patients in the waiting room. The End user will have the
                 ability to fill out personal information, surf the Internet, or play games.

                         Secretaries: The secretary (or office professional) shall have more
                          flexibility with the table where the secretary will have the ability to
                          print out user information, or start a new session for a new user.

                         REDX System Administrators : The RedX server administrator will
                          have the ability to perform administrative task on the RedX server
                          such as adding, and removing the advertisements that will be displayed
                          to the end user.


  Software Requirement Specification                                             Date                                        Rev   Page
                                                                                 11/22/2010 6:22:00 PM                       1.2   3
Software Requirements Specification



2.5    Constraints

2.5.1 Hardware Platform and Operating System
All components of the system will run under the Windows 98SE, 2000 or XP operating
systems except hand-helds, which will either run Windows CE or Windows XP.

2.5.2 Budget Constraints
Should not exceed $5000 for each office. This includes a package of three hand- held
clients, networking hardware, server (if required), software and installation charges.

2.5.3 Bandwidth Requirements
System bandwidth limitations will be restricted by xDSL or comparable speed broadband
Internet connection. The connection shall be capable of download rates of at least
500Kbps. This assumes streaming video takes 200Kbps of the bandwidth, and each office
is capable of supporting 3 tablets.

2.5.4 REDX server constraints
            The RedX server will run a web application server that meets J2EE
              specifications, such as IBM‟s Web-Sphere.
            System will run a RDBMS accessible by type 4 JDBC drivers.
              (Initially Oracle 9i will be supported, though the system will be written
              with RDBMS independent calls.)
            Streaming video server will reside on the RedX server


2.6    Assumptions and Dependencies

2.6.1 Advertisement Sources
     Advertisements will be created external to this project.
     Backup and typical system administrative information is outside the scope of this
      document.
     Software will not interface with the third party dental software such as Dentrix,
      and Softdent, though this will be kept in mind as a possible future expansion.




  Software Requirement Specification              Date                    Rev       Page
                                                  11/22/2010 6:22:00 PM   1.2       4
Software Requirements Specification




3 Functional Requirements
3.1 TABLET PC REQUIREMENTS
This section describes requirements of the TabletPC software.


3.1.1 Necessary supporting software packages
The Tablet PC must run the following software packages:
               Microsoft Media Player- for streaming videos
               Macromedia Flash
               Internet Web browser capable of displaying applets

3.1.2 Patient privileges & restrictions
             The patient (end user) must be restricted from starting new processes,
            and also exiting the application and operating system.
             The patient will only be able to access, enter, and modify information
            that is specific to them.


3.1.3 Administrative privileges
The tablet must be able to distinguish between a local administrator using the system, and
a patient using the system. The secretary would have as a „local‟ administrator privileges
such as:
                 Printing patient information to a printer
                 Ability to maneuver around in the operating system
                 Sign in new patients


3.1.4 Usability: Data entry, and navigation
All data entry, and navigation on the tablet PC must be designed to be performed without
a mouse or keyboard. The design will be optimized to use the pen provided with the
tablet as the main source of user interaction. The design may allow for a keyboard, or
mouse as an input, but it shall not be the main method to interact with the user.

3.1.5 LOGIN information – (user profile)
The Tablet PC system must be able to accept user information, both medical and general.
This information may or may not be tracked beyond the login session, depending on user
preference. If the option “Save Medical Information on Server” is checked, the
information will then be saved, and stored on the RedX server. Once the tablet is returned
to the receptionist, the Information will no longer be available for a patient to see without


  Software Requirement Specification               Date                     Rev       Page
                                                   11/22/2010 6:22:00 PM    1.2       5
 Software Requirements Specification



re-entering the User ID and password. This takes place only after the receptionist prints
out the information.

Data that will be tracked in the system follows.

3.1.5.1    MEDICAL/ DENTAL DATA FIELDS
Insurance company name
…

3.1.5.2    General personal Information.
Table 1, Personal Information, shows the data elements to be captured along with the
following characteristics of the data.

Field Name: The name that will appear to the user on the information gathering web
page. This is not an attribute; rather it is the field containing the information.

Mandatory: This is an attribute of the Field Name element. If yes, the information must
be entered before the user can proceed.

Type/Format: This is an attribute of the Field Name element. This describes the type of
information that is expected for each Field Name element. Examples are numbers,
strings, checkbox etc.

Advertising Demographics: This is an attribute of the Field Name element. It will identify
the field name elements to be used for identifying the users targeted for advertisements.
A “Yes” in this box means that this field will be used as one of the selection criteria for
selecting an advertisement targeted for the user.

Validation Criteria: This is not an attribute of the Field Name element. This is a
description of how the mandatory fields will be validated.

 Field Name           Mandatory Type/Format Advertising  Validation Criteria
                                            demographics
 Store on             Yes       checkbox
 Server?
 First Name           Yes              String        No               Exist
 Last Name            Yes              String        No               Exist
 Gender               Yes              Pulldown      Yes              „M‟ or „F‟ one is selected
 Date of Birth        No               Date          Yes              NA
 Home Address         Yes              String        No               Exist
 City                 Yes              String        Yes              Exist
 State                Yes              Pulldown      Yes              a state is selected
 Zip Code             Yes              Number        Yes              Exist
 Phone Number         Yes              number with   Yes              exist
  Software Requirement Specification                   Date                     Rev        Page
                                                       11/22/2010 6:22:00 PM    1.2        6
 Software Requirements Specification



                                       proper
                                       format
                                       boxes
 Email Address        No               string     Yes              Prompt if empty, but
                                                                   allow user to continue if
                                                                   empty
 Income               No               Pulldown   Yes
Table 1, Personal Informati on



3.1.6 GAMES
The system must allow JAVA Servlet based games.


3.2     REDX SERVER REQUIREMENTS

3.2.1 Server Content
The RedX.com site will contain the following.
             Advertisements
             Links to sites to order medical products and subscription drugs online,
                 support groups, medical information, etc.
             Survey groups
             Directory of dentists
             Directory of advertisers w/ search capability
             Area to request medical records, which will send e- mail to the dentist
                 office

3.2.1.1    Personal information updates
Users may not update dental office records such as address from a home PC via the
Internet. (They must request updates from a TabletPC in the dentist office.)


3.2.2 Advertising -
The system will provide the flexibility for sending both targeted and general
advertisements to users.

3.2.2.1    Adverti sement Matching algorithm
Each advertisement on RedX com will be categorized according to target groups
(profiles) it appeals to. For each ad, any number of the following categories can be
selected to be used by the targeting algorthim.

3.2.2.1.1 Age


  Software Requirement Specification                Date                     Rev        Page
                                                    11/22/2010 6:22:00 PM    1.2        7
 Software Requirements Specification



3.2.2.1.2 Gender

3.2.2.1.3 Zip code

3.2.2.1.4 Area code

3.2.2.1.5 Income

3.2.2.1.6 Targeted
Some ads are meant for all audiences (instead of targeted ads.) The system must provide
a way to distinguish between the two types of ads.

After the user logs in and updates his personal information, the personal information will
be compared against the advertisement profiles to find the advertisement(s) of most likely
match. If no exact matches are found, ads are selected from the pool of general- targeted
ads.


3.2.2.2    Adverti sement Formats
The system shall be able to accommodate the following advertisement formats:
               Banner ads
               Streaming video advertisements
               Multi- media Flash
(A good reference for this type of information is located at www.iab.net)


3.2.2.3    Adverti sing - Billing
The system will track the number of "click-throughs" on advertisements, as well as
minutes of airtime given to multi- media advertisements, in 1-second increments.


3.2.3 Server Administration
The RedX system administrator will have the responsibility to place the advertisements
into the database used by the system.



3.3    External Interface Requirements
The system may interact with other mark eting systems such as Double-Click. External inteface
requirements are to be determined.



3.4    Other Requirements



  Software Requirement Specification               Date                    Rev        Page
                                                   11/22/2010 6:22:00 PM   1.2        8
Software Requirements Specification



Use cases defined for this project will reside in the Rational Rose model. The filename is
“FredRoseModel.mdl”. The controlled copy is archived in Visual source safe, along with
all the other requirements documents. The use MSWORD document that accompanies
this rose model is also stored in VSS, and is “FredRoseModel.doc”.




  Software Requirement Specification              Date                    Rev       Page
                                                  11/22/2010 6:22:00 PM   1.2       9
Software Requirements Specification




4 Non-Functional Requirements
4.1 Performance
Internet bandwidth, tablet, and server capacity must be sufficient to support a
refresh/redraw time of less than 6 seconds per web page.

4.2     Useability

4.2.1  Tablet Usability
The system will conform to Windows GUI guidelines, using design elements such as
combo boxes, frames, and short-cut keys to make the system easy to use for novice users.
TEST CASE:
HCI study will be performed on the prototype for feedback regarding ease-of-use

4.3     Reliability

4.3.1    Reliability
Failure Intensity: For a six day work week, the maximum acceptable software failure
rate for a Tablet PC is 1 per week, or 52 failures/ 260 business days = .2 probab ility of
failure.


4.4     Scalability

4.4.1    Capacity and Growth
Initially, 200 dentists will beta the product (prior to full scale launch.) An average
dentist has 2000 patients.

By the end of 1st year, 44,000 dentists are expected to use RedX. The RedX.com s ite
must scale to this growth while maintaining performance specified.

TEST CASE:
When the system's first architecture is prototyped, the system will be load tested using a
tool such as Mercury's LoadRunner to insure that it will scale as expected.

4.5     Availability

4.5.1 Site Availability
The RedX.com site will be available 18 hours x 6 days.




  Software Requirement Specification               Date                     Rev          Page
                                                   11/22/2010 6:22:00 PM    1.2          10
Software Requirements Specification



4.6     Modifiability

4.6.1 Tablet modifiability
New advertisements, content, and most functionality changes must not require software
to be re- loaded on the TabletPC

The architecture needs to be flexible to accommodate new items for profiling (like
profession, name….).

(on scale of 1 – 3) Client indicated 2.
1 -Can add new categories without code modifications
2- Minor code modifications (turn around in a couple of weeks)
3- Takes a programmer a month to add new category


4.7     Security and Privacy Requirements

4.7.1 Medical and personal information security
Medical information entered through the TabletPC must not be exploited/intercepted.
If information is transmitted via a wireless network, data stream must utilize 128-bit
strong encryption.

4.7.2   Confidentiality
A Privacy Policy shall be included on site that discusses what RedX will do with the data
collected.




  Software Requirement Specification              Date                    Rev        Page
                                                  11/22/2010 6:22:00 PM   1.2        11
Software Requirements Specification




5 Requirements Question & Answer sessions
        Functional Requirements Questions
        Dentist System - Soft Dent Status: Answered
        149     Q:     What are top dental systems that should be interfaced with?
                A:     SoftDent (by far) and Dentrex
         148 Q:        Can we modify SoftDent or Dentrex? Can we add tables to their
                       database, etc?
               A:      - Need to ask suppliers about their APIs and whether or not tables
                       can be added.
        Infrastructure Status: Answered
         141 Q:        "Must the DentistOffice components run on existing PCs? Is it
                       reasonable to expect dentist
                       offices to purchase a non-dedicated server PC to run the system?
                       (Office employees might use the system in a limited fashion.)"
                A:     Are hoping to provide Dentist w/ 3 tablets installed for under
                       $5000 Budget includes:
                       - Server, if needed
                       - Network Components
                       - 3 Tablets for the office
                       - Installation
                       RedX.com         Status: Answered
        150     Q:     Can information (birth day, etc) be modified?
                A:     No, must go back to dr's office for updates. READ-ONLY.
                       146 Q:           What information needs to be generated to allow
                       RedX to bill advertisers?
                       - # click-throughs?
                       - # of users who view the add? ("airtime?")
                A:     - Air time, per user
        145     Q:     What medical information can be requested?
                       X-Ray images?
                       Office visits? (What data elements are available?)
                       Billing information?
                       Insurance information?
               A:      - Xrays could be available for those with digital equipment. Those
                       without could digitize the film.
                       - Date of visits could be tracked for purposes of tickler system. E-
                       mail could be sent out as a reminder of when to come in for
                       yearly visit.
                       - Insurance/Billing: local system only
         144 Q:        Medical information that can be viewed on the Internet poses some
                       security and technical challenges. Instead of "instant viewing"
                       online, would a delayed scenario be acceptable? For example, the
 Software Requirement Specification               Date                    Rev        Page
                                                  11/22/2010 6:22:00 PM   1.2        12
Software Requirements Specification



                           user might request medical information which could be prepared
                           after 30 minutes to an hour. E-mail could be used to notify the
                           user when the information is ready. For example, the e- mail might
                           say, "Your dental records are available for the next 24 hours at the
                           following secure link:
                           https://www.RedX.com/xxxxxid=123456789. All records will be
                           deleted on mm/dd/yyyy at hh:mm:ss."

                           Would a semi-automated / manual system be acceptable, where
                           the user request simply generates e-mail to dentist office staff?
                           For example, "Patient John Doe has requested medical
                           information to be sent. Click here to view details of request:
                           https://www.RedX.com/requests/xxxxxxxxxx"
               A:          Doctor's access to his local data must be instant. User might be
                           willing to wait for a while, but the preferred route is just to go to
                           RedX.
                           With proper security measures, it may be acceptable for RedX.com
                           to store medical information. For users who do not wish to store
                           information on-site, a polling mechanism could also be used to
                           push medical info to RedX.com as requested with a delay.
        143 Q:             The Internet site will be hosted by an "app service provider" to be
                           chosen. What are the site's online availability requirements?
                            24hrs x 7 days per week? Business hours only?
              A:           24 x 7 for all features.

        142 Q:        Some patients may not want even general info to be used for
                      marketing information. Is it necessary to give the patient an
                      option "do not send general information?"
                      Should a disclaimer stating that "general information may be used
               for marketing…"?
            A:        Dentist (or secretary) can go over this with the patient, but
                      disclaimer is needed. A Privacy Policy needs to included on site.
        140 Q:        How many dentists could be expected to use the site in the 1st
                      year?
                      2nd year?
            A:        Initially, 200 dentists start w/ "free" Dente (prior to launch.)
                      Number of patients: dentists see 78 per week, 5 are emergencies.

        Functional Requirements Questions
        139    Q:    What kinds of content are to be on RedX.com?
                     Some ideas:
                     - Directory of dentists?
                     - Directory of advertisers?
               A:    - Same Advertisements.
 Software Requirement Specification                    Date                    Rev       Page
                                                       11/22/2010 6:22:00 PM   1.2       13
Software Requirements Specification



                           - order medical products online? Drugs?
                           - Links to support groups
                           - Links to research about Medical Information
                           - survey groups
                           - Directory of dentists?
                           - Directory of advertisers w/ search
                           - Area to request personal dental/medical information
                           TabletPC        Status: NEW



         138     Q:        How desirable would it be for the site to support different
                           resolutions? (For example, small CE hand- held devices)
               A:
       Please rank the importance of the following scenario: (1 to 3)
         User wishes to support any screen resolution with no more than 120 man hours
of development time.

         137     Q:        What is the screen resolution we will develop to? 800 x 600? 640
                           x 480?
                 A:

         136     Q:        Tablets based upon Window CE are much less expensive than
                           those based upon Window 98 or XP. What Operating Systems
                           will the TabletPC run? (Some technologies such as Flash may not
                           be available in CE.) Could there be a requirement to run on
                           Linux or other alternative operating systems?
                 A:

       Other Information / Requirements Questions
       TabletPC         Status: Answered
133    Q:     Is it a requirement for the system to work in a limited fashion w/o an
              Internet Connection?
       A:               It would be "nice to have" this capability for dentists to just use
                        form- filling features.




 Software Requirement Specification                    Date                    Rev       Page
                                                       11/22/2010 6:22:00 PM   1.2       14
Software Requirements Specification




6 Requirements Traceability
6.1   Upward Traceability
                 Traceability from each requirement in this specification to the system or
                 subsystem requirements it addresses. (pls clarify 6.1 and 6.2)

6.2   Downward Traceability
                 Traceability from each system or subsystem requirement to the requirements
                 contained in this specification

6.3 References
FRED Statement of Work
FRED Software Project Management Plan
FRED Wireless Connectivity Report
FRED Requirements Tracking Database, \\dogbert\TabletPC\FREDRequirements.mdb.
:FRED Rational Rose Model , -see VSS




 Software Requirement Specification                Date                    Rev      Page
                                                   11/22/2010 6:22:00 PM   1.2      15

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:29
posted:11/23/2010
language:English
pages:19
Description: Dentist Advertising Budget document sample