Changes between Version 4 and Version 5 of DocumentsPage


Ignore:
Timestamp:
09/04/2007 07:09:16 AM (17 years ago)
Author:
russell
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DocumentsPage

    v4 v5  
    1 C''''''S6361 FALL
    2 
    3  2006 Documents Page
    4 
    5 Josh's brain storming-----------------------------------------------------------------------------------------------------
    6 Why? There are many aspects in our lives that we need to deal with, scheduling classes and flights, room assignments at hospitals, scheduling domestic and international meetings and etc... Many softwares are provided for support, and yet, clarity in customer needs is a problem. As long as requirements are lucid, the cost of application and production will be held to a minimum.
    7 
    8 '''What do we need?'''
    9 
    10 1. A scheduler, which deals with all scheduling information.
    11         Goal: is to reduce communication costs and time costs
    12 2. Database: which saves the information of all possible users available.
    13         Data included: calendar, physical rooms data, virtual room data, user information, user preferences (dates they    can and can’t attend meetings), scheduled meetings,
    14 3. GUI, the interface that the user will interact with.
    15 
    16    
    17 
    18 
    19 '''How everything works,'''
    20 All the requirements and specifics will be manually inputted by the client and sent to the server side. The server will then deal with all the scheduling information.
    21 
    22 What the client needs to know:
    23 
    24 
    25 1. hardware requirements (i.e. explore 6.0, XP…)
    26 
    27 
    28 2. Information requirements (what information is needed to schedule a meeting)
    29 
    30 
    31 3. Our system is user-friend
    32 
    33 4. Please respond to the server messages of scheduled meeting ASAP
    34 
    35 
    36 
    37 '''Client side:'''
    38 
    39 
    40 Register New user:
    41 
    42 
    43 1. Login to www.oursystem.com the system website
    44 
    45 
    46 2. Create user, by adding all data stated above
    47 
    48 
    49 3. Wait a few days for the registration to be authorized by us.
    50 
    51 
    52 4. Registration granted/denied
    53 
    54 
    55 
    56 '''Reschedule/Schedule a meeting'''
    57 
    58 
    59 1. Login to website
    60 
    61 
    62 2. Replan/Request for a meeting (must be requested 7 days before the actual meeting time)
    63 
    64 
    65 3. Identify the preferred date/time/location/monitoring user.
    66 
    67 
    68 4. Scheduled meeting status
    69 
    70 
    71        -Granted (all set)
    72 
    73 
    74        -pending (still scheduling)
    75 
    76 
    77        -modification (modification of meeting data required)
    78 
    79 
    80        -rejected (can’t schedule meeting)
    81 ---------------------------------------------------------------------
    82 '''Server side''': (assuming all information is inputted and updated)
    83 
    84 '''Assumptions''':
    85 
    86 
    87 1. our server is secure, privacy is guaranteed, so I think we should run this under https???
    88 
    89 
    90 2. Our database information will not have any flaw.
    91 
    92 
    93 3. We assume that all users will respond ASAP (within 24 hours) to the meeting request
    94 
    95 
    96 
    97 '''Technical issues'''
    98 1. Concurrency issues, this is an implementation part, so I think we can deal with this later on. (meeting requests and in-meeting communication)
    99 
    100 Preprocess the information sent by the client (to rectify the information before the scheduler actually schedules the meeting)
    101 
    102 
    103 1. Receives the data from the client
    104 
    105 
    106 2. Checks if there are any conflicts in the information
    107 
    108 
    109 3. If there is, respond to the client for rectification, else, send information to the scheduler.
    110 
    111 
    112 
    113 Meeting setups
    114 
    115 
    116 1. collects all the information being sent from the client
    117 
    118 
    119 2. identify all users that are requested to be involved in the meeting
    120 
    121 
    122 3. we run the programs to determine if the meeting can be scheduled (I propose that we use the priority algorithms in operating systems. (I believe the rest of the information is implementation issues, so I’m not stating anything about it as of right now)
    123 
    124 
    125 4. if meeting is not scheduled, send the unscheduled meeting results to the user, if needed for further assistance, repeat from step 1. Else, send out an invitation to all users about the scheduled meeting. We are assuming that they will follow their preferences as given in the database.
    126 
    127 
    128 5. We book the meeting when finalized.
    129 
    130 
    131 
    132 '''The Database'''
    133 components
    134 1. Information for all users
    135 
    136 
    137     -Preferences for meeting time
    138 
    139 
    140     -Current location (real-time update?)
    141 
    142 
    143     -Personal information
    144 
    145 
    146 2. Physical rooms available
    147 
    148 
    149 3. Virtual rooms available
    150 
    151 
    152 4. Scheduled meeting information (there might be cases where rescheduling is being requested even before the server responds to the client, so we need to have information about this)
    153 
    154 
    155 
    156 
    157 
    158 This is it folks, feel free to critique.
    159 
    160 = Russell's Brainstorming =
    161 ----
    162 
    163 1) Go to the office where the sign up sheet is located.[[BR]]
    164 2) Pick several dates and times for a meeting.[[BR]]
    165 
    166  * Room size
    167  * Teleconference availability
    168 [[BR]]
    169 3) Email meeting participants to see who is available when, based on chosen dates and times.[[BR]]
    170 4) If all participants available at same date and time, go to step 5, if not repeat from step 1.[[BR]]
    171 5) Go back to sign up sheet, if chosen time and date is still available, then sign up and go to step 6, else go to step 1.[[BR]]
    172 6) Email all participants the date, time and location of meeting.[[BR]]
    173 7)  If not using email then visit/call each participant or send memo to tell each participant the date, time and location of meeting.[[BR]]