Synergy Distributed Meeting

Scheduler (SDMS)
Project Presentation

Students: Arnena Sheihk-Houssein

Hui Chen
Yiying Lee
CS6361 Requirement Engineering
Prof. Lawrence Chung
Computer Science Department
University of Texas at Dallas
Fall 2005

1
 Contents

• Project Overview
• Requirement Description
• Use Case Diagrams
• System Level Class Diagram
• Activity Class Diagram
• Entity Class Diagram
• Prototype
2
 Project Overview

SDMS is a system simply refers to on-line scheduling

between businesses personals as opposed to the
more familiar way by calling and scheduling a
meeting between businesses SDMS systems are a
way of bringing business partners together in one
location or across countries at the same time.

3
Informal requirement Description

4
Use Case Diagram (Package)

Maintenance

Administrator Scheduler Database

User Meeting
Timer

5
Use Case Diagram (Maintenance)

ManageResource use
case probably initiates the
ManageMeetingRecord ScheduleMeeting use
case when some meeting
resources are changed.

Administrator ManageResource

ManageAccount

Database
Login

User Logout

ModifyAccount

6
 Use Case Diagram (Scheduler)
as

MeetingInitiato ReserveMeeting
r
ModifyMeetingInfo Timer

User

Database
InputAttendeeInfo ScheduleMeeting

PotentialAtten
<<include>> <<include>>
dee
All use cases in this
package need to
<<include>> access the actor
Database.
NotifyParticipant HandleConflict
ActiveParticip
ImportantPartic
ant
ipant

7
 Use Case Diagram (Meeting)

PotentialAtten Attendee HoldMeeting Timer

dee

MeetingInitiato MonitorMeeting Database

r

8
 Class Diagram (System level)
For each entity class which can be InputForm <<use>>
input with using UserInterface, there (from BoundaryClass)
is a corresponding subclass of
InputForm which is used for UserIO
prompting user to input necessary (from BoundaryClass)
...)
information and then creating it. <<create>> <<use>>
<<realize>>

TimerHandling <<initiate>> FlowControl <<initiate>> UserInterface

(from BoundaryClass) (from ActivityClass) (from BoundaryClass)

<<use>> <<use>>

DBHandling Notifier AdmUI UserUI

(from BoundaryClass) (from BoundaryClass) (from BoundaryClass) (from BoundaryClass)

9
 Activity Class Diagram
ManageMeetingRecord
Login Logout

AdmUI UserUI
ManageResource (from BoundaryClass) ModifyAccount
(from BoundaryClass)

ManageAccount ReserveMeeting ModifyMeetingInfo InputAttendeeInfo

TimerHandling
HoldMeeting (from BoundaryClass) ScheduleMeeting All activity classes are
subclasses of an
abstract base class
called as FlowControl,
which is not depicted
MonitorMeeting HandleConflict NotifyParticipant in this diagram.

10
Entity Class Diagram

11
 Initiate System Terminate System
Ready Shut down

[ Timer event for scheduling meeting ] Wait Input

Event

Logout Meeting ends

Logout [ Timer event for starting meeting ]

[ Administrator Login ]
[ User Login ]

Maintain Database Main User Interface Hold Meeting

do/ Show adm menu do/ Show user menu do/ HoldMeeting
do/ MonitorMeeting

[ Select Record ] [ Select Modify ] [ Select Attendee ]

[ Select Initiator ]

Statechart
ManageMeet Initiator User Interface Attendee User Interface
ingRecord ModifyAc
count
do/ Show initiator menu do/ Show attendee menu
[ Select Account ]

Diagram
Manage [ Select Reserve ]
Account [ Select Modify ]

[ Select Resource ] Reserve Modify Meeting Input Attendee

Meeting Information Information
ManageRe
source
[Others]
[Using-Resource changed]
Show Schedule Meeting
Result
Handle
Conflict
Need New Info
[Conflict occurs]
Schedule [ Need Info ] Notify Participant
Meeting
[Time out]
[Success]
Cancel [ Unlogined ]
Schedule Meeting
Complete

Save Meetinf [ Logined ]

Record Upper Menu
12
Non Functional Requirements

C1 C2 C3

Availability
Reliability
Robustness
Well performance
User ID
User friendly
Perform
Maintainability
SDMS System Portability
Password
Security
Extensible
Customizable
Flexible
A0

Participant Database Administrator Computer

13
Prototype

14
Prototype

15
Prototype

16
Thanks !

17