TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009
description
Transcript of TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009
![Page 1: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/1.jpg)
TERASOFT DISTRIBUTEDMEETING SCHEDULER SYSTEM
PROJECT PHASE 2.2DECEMBER 3 , 2009 Presented by
Vinit PatwaPrasanna Kumar ThiagarajanShiva SangamAzharuddin Mohammed Ritesh Patel Tarun Chandra Samireddy Rutvij Desai Sirisha BalantrapuShubhada Deshmukh Preethi Varambally Swaroop Govindappa
![Page 2: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/2.jpg)
Secure, interactive and easy to use online meetings are waiting for you !!! • Communicate as if you
are "face-to-face" with people across town, or across the world
• Share documents, make presentations, demonstrate products and services, and collaborate like never before
• Start a secure web meeting from the comfort of your desktop instantly, with just a click of the mouse
The possibilities are infinite. And with Terasoft Distributed meeting Schedular System, there's no software to install and no hardware to purchase
![Page 3: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/3.jpg)
PRESENTATION SUMMARY
• New Requirements
• Process Specification
• Vision Document and SRS-Analysis Models
• Functional Prototype Demo
![Page 4: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/4.jpg)
NEW REQUIREMENTS!!!
![Page 5: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/5.jpg)
ENTERPRISE FUNCTIONAL REQUIREMENTS• Meetings can belong to a special category that can be held in chunks.
• Attendees of chunk meetings qualify for partial attendance. (i.e. they can participate in multiple meetings in the chunk partially).
• The meeting locations for the meetings that are held in chunks should be as convenient as possible for attendees who are involved in more than one meeting.
• The initiator can cancel a meeting request and delete it form the calendar. Then notify all the participants about the cancellation.
![Page 6: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/6.jpg)
SYSTEM FUNCTIONAL REQUIREMENTS
• System should provide functionality to organize meetings that are held at the same time as chunks.
• System should provide functionality that will allow partial attendance.
• The system should provide functionality to suggest convenient locations for meetings that are held in chunk.
• System should provide functionality to cancel or update a meeting.
• System should provide functionality to schedule recurring meetings.
![Page 7: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/7.jpg)
ISSUES Requirement - The meeting location should be as convenient as possible
for attendees who are involved in more than one meeting.
Description – This requirement is incomplete. It does not specify what convenient location means.
Option 1: Location at which maximum number of participants of meetings that are held as chunk can attend.
Option 2: Location at which 100% of participants who are attending more than one meeting of a chunk can attend.
Option 3: Location at which 100% of the participants who are attending more than one meeting of a chunk can attend and 70% of the single meeting participants can attend.
Decision and rationale:- Options 3 is a better one because people who are attending more than one meeting in a chunk can benefit. More over if a participant is attending more than one meeting he can be considered as an important attendee.
![Page 8: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/8.jpg)
ISSUES (CONTD) Requirement - Attendees of chunk meetings qualify for
partial attendance.
Description- This requirement is incomplete. There may be a situation where a person may be needed at two meetings at the same time.
Option 1: This requirement can be extended to mention which part of the meeting the partial attendee is going to attend.
Decision and rationale: - When accepting the meeting request the attendee with partial attendance has to mention which part of the meeting he/she is going to attend.
![Page 9: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/9.jpg)
PROCESS SPECIFICATION
![Page 10: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/10.jpg)
PROCESS MODEL
![Page 11: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/11.jpg)
SADT: TOP LEVEL DIAGRAM
Process Requirements
Preliminary Document
Requirements Engineer
Software Requirements Specification
A0
Requirements validation
Process Specification
UML Specifications
SADT Specifications
![Page 12: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/12.jpg)
SADT: MEETING SCHEDULAR!!!
Meeting Initiation
A1
Scheduling
Conflict Resolution
A2
A3
InputsData Range
Participants list
Location Preferences
ES, PS, Location Preferences
Date Range, Location
Initiator Participants
Admin
No Proposed Date
Final Proposed or Discussion
A0
Software System
![Page 13: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/13.jpg)
Decide on date Range, Participants and Location,
by Initiator
Send invites to participants
Date Range
Available Locations
Participants
Initiator Software System
A1
A11
A12A12
Participants List
Date range location
![Page 14: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/14.jpg)
Receive Responses
Date RangeLocation
Calculate Schedule
ES, PS , LocationEquipement
ES, PS, Location,Equipement
Participants Software System
A21
A2
A22
Proposed Schedule
No ProposedDate
![Page 15: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/15.jpg)
Inform about Conflicts and Get User Response
A3
Update ES and PS
Calculate Schedule
Resolve Manualy
SoftwareSystem
Participants Admin
Final Proposal
No ProposedDate
A3
A31
A32
A33
A34Not Resolved
![Page 16: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/16.jpg)
IDEF LEVEL0
![Page 17: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/17.jpg)
IDEF LEVEL1
![Page 18: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/18.jpg)
VISION DOCUMENT AND SRS-ANALYSIS MODELS
![Page 19: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/19.jpg)
THE VISION !!!
The problem ofscheduling meetings with minimal interactions and resolutionof conflicts regarding date and time
Affects employees of organizations
the impact of which is Delay and ultimately improper resource utilization
a successful solution would be
An accessible, cost-effective meeting scheduler which can beused by the employees to initiate and schedule meetings. Theproduct would also address issues related to conflict in datesand provide an efficient method to solve any such problems
![Page 20: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/20.jpg)
THE VISION!!
![Page 21: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/21.jpg)
THE VISION(CONTD)
![Page 22: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/22.jpg)
USE CASE DIAGRAM
![Page 23: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/23.jpg)
SEQUENCE DIAGRAM
![Page 24: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/24.jpg)
SEQUENCE DIAGRAM
![Page 25: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/25.jpg)
FISH-BONE DIAG
Attendees have already committed to other meetings
Attendees are in different places/ Geometric locations have different holidays Attendees are in
different time zones
Scheduling meetings is Difficult and Time Consuming
Availability of Attendees
Availability of Equipment
Availability of Free Timeslots
Attendees LocationDate
Unexpected change in meeting schedules / cancelation by attendees
Attendees are in different places/ Geometric locations
Attendees not available at a given date
Equipment malfunction
Equipment taken by other meetings
Attendees have work or assignments on a given meeting date
![Page 26: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/26.jpg)
ACTIVITY DIAGRAMReview Preliminary
Requirement Document
Identify Stakeholder
Start RE Process
Interview Users
Review Similar Software
Model Enterprise, Functional, Non-Functional Requirements
Identify Conflicts
Propose Solution
Validate Solution with user
Create initial dependency graph
Create improved Dependency graph
Convert Functional Dependency to UML
Convert NonFunctional dependency to SIG
Refine functional Requirements and identify Domain Class
Specify SRS
![Page 27: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/27.jpg)
CLASS DIAGRAM
![Page 28: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/28.jpg)
KAOSSchedule Chunk
MeetingsReduce the overhead in
organizing meetings
Choose convenient meeting locations
Allow partial attendance
Convenient for 70% of the single meeting
attendees
Convenient for 100% of the multiple
meeting attendees
Reduce the number of interactions
between attendees and the initiator
Maintain [Partial attendance
timing]Avoid
[Redundant interactions]
Maintain [Interactions for backtracking]
![Page 29: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/29.jpg)
SIG:SECURITY
Security [Meeting Info]
Security [Meeting Data]
Security [Participent Info]
User Login Administrator Login
+ +
++
Login [NSG2, NSG2]
+
"Password can be stollen"_
Database access Roles [data]
security [Institution Data]
+
Security [Authentication]
++
+
![Page 30: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/30.jpg)
SIG: PERFORMANCE
Performance
Capacity Responsiveness
Minimum overhead
manages Cocurrency
confirm loction
++ +
++
confirm participants Send reminder before meeting
++
responding through website
auto rescheduling +
+
Confirm meeting+
+
+
Reschedule meeting
+minimize interactions
+
![Page 31: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/31.jpg)
SIG:USABILITY
Convenience Convenient to use due to some convenience featuresUnderstandability Learning to use the system takes few hours. It is very easy to use as the system as the interface is user friendly.
Usability
ConvenienceUnderstandability
+
+
location time independent
++Easey reschedulingemail reminders
User friendly interface
Quick to learn
++++
++++
![Page 32: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/32.jpg)
SIG:RELIABILITYAccuracy – System should monitor the status of the meeting accurately by monitoring location, participants and time schedule of meeting.Availability – System shold be available from anywhere in the world on web. It should be available 24 hours a day 7 days a week. Consistency - System should not schedule avoid the conflict of scheduling multiple meetings on one schedule and location.
Reliability
AccuracyAvailability
Consistency
+
++
Accurate monitoring of
Participants
Location Schedule
++
+
+ +All over the world
++
Any time 24/ 7
++
Avoid multiple meeting on sameschedule
++
![Page 33: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/33.jpg)
SIG:MAINTAINABILITY
Extensible
Maintainablity
+
Flexible
+
Evolvable Modifiable
++
Accept Variations
++
Date and Time format
++
Location virtual/ actual
++Browsers
++
Add new functionality
++
Customizable to schedule formalor nonformal meetings
++
![Page 34: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/34.jpg)
USE CASE TO REQUIREMENTS MAPPING
![Page 35: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/35.jpg)
![Page 36: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/36.jpg)
TRACEABILITY
![Page 37: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/37.jpg)
TRACEABILITY
SCREEN – 1 Login Page
SCREEN –2 Registration Page
SCREEN –3 Invalid User Page
SCREEN –4 Welcome Page
SCREEN –5 Initiate Meeting Page
SCREEN –6 View Meet Page
SCREEN –7 Response Page
SCREEN –8 Update Meeting Page
SCREEN –9 Confirm Meeting Page
SCREEN –10 Cancel Meeting Page
SCREEN –11 Logout Page
![Page 38: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/38.jpg)
TRACEABILITY (CONTD)SFR 1 SCREEN - 1
SFR 2 SCREEN - 5
SFR 3 SCREEN - 7
SFR 4 SCREEN - 7
SFR 5 SCREEN - 5
SFR 10 SCREEN - 8
SFR 11 SCREEN - 8
SFR 12 SCREEN - 8
SFR 14 SCREEN - 7
SFR 15 SCREEN - 7
SFR 16 SCREEN - 7
SFR 17 SCREEN - 5
SFR 21 SCREEN - 8
SFR 23 SCREEN - 9
![Page 39: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/39.jpg)
Screen shots
THE PROTOTYPE!!
![Page 40: TERASOFT DISTRIBUTED MEETING SCHEDULER SYSTEM Project Phase 2.2 DeCEMBER 3 , 2009](https://reader035.fdocuments.us/reader035/viewer/2022081517/56816245550346895dd28135/html5/thumbnails/40.jpg)
Queries????
THANK YOU!!