Synergy Distributed Meeting Scheduler (SDMS)

1.

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

2.

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

3.

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

4.

Informal requirement Description
4

5.

Use Case Diagram (Package)
Maintenance
Administrator
User
Scheduler
Meeting
Database
Timer
5

6.

Use Case Diagram (Maintenance)
ManageMeetingRecord
Administrator
ManageResource use
case probably initiates the
ScheduleMeeting use
case when some meeting
resources are changed.
ManageResource
ManageAccount
Database
Login
User
Logout
ModifyAccount
6

7.

Use Case Diagram (Scheduler)
as
ReserveMeeting
MeetingInitiato
r
Timer
ModifyMeetingInfo
User
Database
InputAttendeeInfo
PotentialAtten
dee
ScheduleMeeting
<<include>>
<<include>>
<<include>>
ImportantPartic
ipant
ActiveParticip
ant
NotifyParticipant
All use cases in this
package need to
access the actor
Database.
HandleConflict
7

8.

Use Case Diagram (Meeting)
PotentialAtten
dee
Attendee
HoldMeeting
Timer
MeetingInitiato
r
MonitorMeeting
Database
8

9.

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

10.

Activity Class Diagram
ManageMeetingRecord
ManageResource
ManageAccount
HoldMeeting
MonitorMeeting
Login
AdmUI
Logout
UserUI
(from BoundaryClass)
ModifyAccount
ModifyMeetingInfo
InputAttendeeInfo
(from BoundaryClass)
ScheduleMeeting
HandleConflict
NotifyParticipant
All activity classes are
subclasses of an
abstract base class
called as FlowControl,
which is not depicted
in this diagram.
(from BoundaryClass)
ReserveMeeting
TimerHandling
10

11.

Entity Class Diagram
11

12.

Terminate System
Initiate System
Ready
Shut down
Wait Input
Event
[ Timer event for scheduling meeting ]
Meeting ends
Logout
[ Timer event for starting meeting ]
Logout
[ Administrator Login ]
[ User Login ]
Maintain Database
Main User Interface
do/ Show adm menu
do/ Show user menu
[ Select Record ]
Hold Meeting
do/ HoldMeeting
do/ MonitorMeeting
[ Select Attendee ]
[ Select Modify ]
[ Select Initiator ]
Statechart
Diagram
ManageMeet
ingRecord
ModifyAc
count
Initiator User Interface
Attendee User Interface
do/ Show initiator menu
do/ Show attendee menu
[ Select Account ]
[ Select Reserve ]
Manage
Account
[ Select Modify ]
[ Select Resource ]
Reserve
Meeting
Input Attendee
Information
Modify Meeting
Information
ManageRe
source
[Others]
[Using-Resource changed]
Show
Result
Schedule Meeting
Handle
Conflict
[Conflict occurs]
Schedule
Meeting
[ Need Info ]
Need New Info
Notify Participant
[Time out]
[Success]
Schedule
Complete
Cancel
Meeting
Save Meetinf
Record
[ Unlogined ]
[ Logined ]
Upper Menu
12

13.

Non Functional Requirements
C1
C2
C3
Availability
Reliability
User ID
Perform
SDMS System
Password
Robustness
Well performance
User friendly
Maintainability
Portability
Security
Extensible
Customizable
Flexible
A0
Participant
Database
Administrator Computer
13

14.

Prototype
14

15.

Prototype
15

16.

Prototype
16

17.

Thanks !
17