iConf - internet based conferencing utility
 
 
design use-cases
  • actor identification
    • actor responsibilities
    System Administrator (SA) maintenance of the server side of iConf
    Conference Administrator (CA) creates conference
    regulates access to conference
    regulates user level of participants
    set "chapters" in the conference
    Advanced Participant (AP) access to whiteboard
    access to text chatting
    (note: the Conference Administrator is implicitly an Advanced Participant
    Chat Participant (CP) access to only text chatting
    Witness (WN) ability to watch the conference but is not an active participant
    Registered User (RU) user with a registered user profile on the iConf server
    General User (GU) general access to the client side of iConf
  • use-case diagram

    •  
    Package: User Management
     
    Package: Conference Management
     
    Package: Session Management
     
    Package: Session Participation
     
     
     
  • use-case description 
    • UC1.1: Register
    Actors General User
    Trigger General User starts the application for the first time and has been not registered till now.
    Process 1.1.1: Display registration form
    1.1.2: Create an object for the user
    1.1.3: Pass the object of the user to the server to be stored into database.
    1.1.4: Server returns the userid for the new registration
    1.1.5:The new userid is shown to the user
    Variations 1.1.4.1: In case the userid is not acceptable to the user it sends the new option for userid
    1.1.4.2: Subsequently the whole process from 3 and 4 is repeated
    UC1.2: Login
    Actors General User
    Trigger General User who has already registered himself before wants to login
    Process 1.2.1: User types userid and password.
    1.2.2: Validity of the login is checked at server.
    1.2.3: The server responds accordingly
    1.2.4: If successful then the user enters the logged state.
    Variations 1.2.4.1 If login is unsuccessful the complete login use case is repeated.
    UC1.3: Access Update
    Actors Registered User
    Trigger The registered user wants to update his access optoins.
    Process 1.3.1: The user is shown his/her current access option and asked for new one.
    1.3.2 The new option is updated at the server's database.
    Variations 1.3.2.1: If no change is done then it is not sent to the server.
    UC1.4: User Lookup
    Actors Registered User
    Trigger The registered user wants to have a lookup at the users list.
    Process 1.4.1 The server is asked to show the lists of users.
    1.4.2. The server returns the list.
    UC1.5: Update Profile
    Actors Registered User
    Trigger Registered User wants to update his profile.
    Process 1.5.1: The user data screen shown while registration is shown again
    1.5.2: The user types the new data.
    1.5.3: The new data is updated at server.
    UC1.6: Delete User
    Actors SystemAdministrator
    Trigger The system adminstrator wants to delete a particular user.
    Process 1.6.1 The user id is deleted from hte server database.
Package: User Management

 
UC2.1: Conference Lookup
Actors Registered User
Trigger The user wants to see conference list.
Process 2.1.1: The user enters the from and to date.
2.1.2: The complete list of conferences from the specified date to specified date is searched for at Server.
2.1.3: The list is displayed to the user.
UC2.2: Conference Scheduling
Actors Registered User
Trigger he registered user wants to create / schedule a conference.
Process 2.2.1: The server is sent the date,time and category for the conference.
2.2.2: The server responds
Variations 2.2.2.1: If there is already one confernce scheduled at that time in the same category the user is notified.
2.2.2.2: The user may schedule it for someother time or the same
UC2.3: Conference Invitation
Actors Conference Adminstrator
Trigger The conference admistrator wants to invite users for a particular conference.
Process 2.3.1: Select the users. 
2.3.2: Place an invitation message in the java space for appropriate users. 
2.3.3: The listeners for each user puts the message in the mailbox. 
UC2.4: Conference Cancelling
Actors Conference Administrator
Trigger The conference Admninistrator wants to cancel a conference.
Process 2.4.1: The cancel notification is placed in the java space.
2.4.2: The listener for system administrator gets the message.
2.4.3: The conference is removed from the server.
2.4.4: Conference cancellation notification is placed in javaspace for all the users invited to it.
2.4.5: A response is sent to conference adminstrator.
UC2.5: Conference Participate
Actors Registered User
Trigger A registered user wants to participate in a particular conference.
Process 2.5.1: A participation request is placed in javaspace for a specific conference administrator.
2.5.2: The conference adinstrator's listener picks the message .
2.5.3: Specific responce is sent to the user in concern conveying whether request accepted or denied.
Package: Conference Management

 
UC3.1: Conference Security Control
Actors Conference Administrator(CA)
Trigger A conference is being started.
Process 3.1.1: Choose a conference in CA's conference list
Variations 3.1.1.1: May offer more than 2 security levels 
3.1.1.2: Security levels may be defined as allowing everyone be witness or explicitly choose witness 

 
UC3.2: User Security Level Control
Actors Conference Administrator(CA)
Trigger CA gets request or complaint
Process 3.3.1: CA gets the request
3.3.2: CA makes decisions
3.3.3: CA change the role of the user
Variations 3.3.1.1: CA may change the roles of a set of users without request 
UC3.3: Security Level Change Request/Response
Actors Advanced Participant, Chat Participant, Witness
Trigger The user wants to change its security level
Process 3.4.1: Send a request to the CA
3.4.2: Wait for response
Package: Session Management

 
UC4.1: Text Chat
Actors Chat Participant, Advanced Participant, Conference Administrator
Trigger The users want to chat with other users by typing text messages
Process 4.1.1: The user writes message in the message dialog
4.1.2: Push send button
4.1.3: The text chat field of all the users will be refreshed to reflect the new message
Variations 4.1.1.1: The user can also send private message to some specified user 
4.1.1.2: The user can choose not to show the message from some specified user
4.1.1.3: The user can encrypt some private message
UC4.2: WhiteBoard Discussion
Actors Advanced Participant, Conference Administrator
Trigger The users want to draw some graph to show his/her ideas
Process 4.2.1: Choose a drawing component on the whiteboard of a specified conference
4.2.2: Use the component to draw a graph on the whiteboard
4.2.3: After finising the drawing, push refresh button 
4.2.4: The whiteboards of all the users of the conference will be refreshed to refresh the change
Variations 4.2.1: An advanced user may be able to erase some portion of the whiteboard 
Package: Session Participation

 
 
 
 
  • dynamic UML diagrams
    • Initialization use cases:

    Back to Table of Contents.
     
    e-mail us: iConf