SDMS Presented by

Arnena Shekih-housseinYiying LeeChen Hui

Outline• SDMS Design

– System overview (Initial) – System detailed design using IDEF0– Activity class diagram (Partial)– Entity classes

• Non-functional requirements• Prototype sample

System Overview (initial)

System design (Top Level)

System design (Detailed)

Second level: Log In

Second level: Change Preferences

Second level: Schedule Meetings

Second level: Validate Meeting Request

Activity Class Diagram (Partial)

LoginUserNamePassword

getName()getPassword()register()resetPassword()

UserPreferenceNameAvailableDatePreferences

getName()getDates()getPreferences()

MeetingsDateScheduledAttendeesLocation

getMeetingDate()getLocation()getAttendees()cancelMeeting()reschedule()getMeetingRequest()getAttendeePreferences()updateAttendees()updateLocation()updateMeetingDate()viewMeetings()checkConflicts()getAttendeeName()

LocationsLocationEquipmentAvailibility

addLocation()addEquipment()getAvailability()

Entity Classes

Non-Functional Requirements

Non-Functional Requirements• C1: Meetings Control

– Reduces Overhead– Accommodates decentralized requests– Performance– Enforce Privacy Rules– Customizable– Extensible– Security– Reliability– Robustness

• C1A: Schedule Meetings– Nomadicity– User-friendly– Availability

Non-Functional Requirements• C1B: Reschedule Meetings

– Dynamic – Physical constraints should not be broken– Flexibility

• C3: Conflict Resolution– Flexibility

Prototype

Prototype

Thanks!