COMP by H M Ishrar Hussain ID#: (Team 6)

Transcription

1 COMP 6471 by H M Ishrar Hussain ID#: ()

2 Use Case Diagram of Activity ment Assignment 3 Administrator Project r Activity ment View Log Authenticate Operation Execution Log Operation Execution Start Session Project ment Collaborative Publication User ment Change ment CU-WME User End Session File ment Actors of the Use Case CU-WME User: All kinds of users of CU-WME system fall under this category of actors. They can be Administrator, Project r or just a Project Assistant/Member. They all may work with different goals on different components of CU-WME system, but, in case of Activity ment, they all contribute identically. As they perform different operations on different components of CU-WME, execution of those operations are authenticated and logged by the Activity ment. CU-WME Users also start and end their work session on the Activity ment. Administrator and Project r: Both Administrator and Project r are specializations of the actor CU-WME user. Both view the logs that are created for each work session of the CU-WME user by the Activity ment. User ment : On request of CU-WME user, User ment runs different user management operations, e.g. create user, delete user, create role, delete role, edit role etc., which it needs Activity ment to authenticate before execution and to log success or failure of their execution. File ment : On request of CU-WME user, File ment runs different file management operations, e.g. copy file, delete file, create directory, remove directory etc., which it needs Activity ment to authenticate before execution and to log success or failure of their execution. Page 1 of 6

3 Assignment 3 Change ment : On request of CU-WME user, Change ment runs different change management operations, e.g. create repository, delete repository, add new files to repository, delete files from repository, create new version, merge versions etc., which it needs Activity ment to authenticate before execution and to log success or failure of their execution. Collaborative Publication : On request of CU-WME user, Collaborative Publication runs the operation of publishing documents, which it needs Activity ment to authenticate before its execution and to log success or failure of its execution. Project ment : On request of Project r, Project ment runs different project management operations, e.g. create task, modify task, delete task, create schedule, edit schedule etc., which it needs Activity ment to authenticate before execution and to log success or failure of their execution. Brief format description of the Use Cases: Use Case 1: Log Operation Execution Actors: CU-WME User, Change ment, Collaborative Publication, User ment, File ment and Project ment. This use case starts when CU-WME User requests to execute an operation on any of the components of CU-WME, i.e. Change ment, Collaborative Publication, User ment, File ment and Project ment. Activity ment (AMS) records the date and time for request of execution in the log of the user s session, and directs the corresponding component of CU-WME to execute the operation. The component finds the operation does not need authentication of the user. The component then executes the operation and returns success to AMS. AMS records date and time of the success in executing the operation in log of the user s session. Use Case 2: Authenticate Operation Execution Actors: User ment, Change ment, Collaborative Publication, File ment and Project ment. Page 2 of 6

4 Assignment 3 This use case starts when any of the components of CU-WME (i.e. Change ment, Collaborative Publication, User ment, File ment or Project ment ) finds that authentication of the user is required before execution of an operation. The component requests AMS to authenticate the user requesting the operation to be executed. AMS first validates the session of the user, and then retrieves corresponding roles and privileges information of the user from User ment. AMS then returns the corresponding roles and privileges information of the user to the requesting component, along with a flag indicating if the user has been authenticated. Use Case 3: Start Session Actors: CU-WME User and User ment. This use case starts when CU-WME User provides his/her identification information (which can be username-password pair, finger/hand print, retina/voice recognition pattern etc.) and requests to start a work session on CU-WME. AMS then retrieves the identification information of the corresponding user and verifies the information provided by the user. AMS finds that the user is authorized to start a session, and registers the session by saving the session s information along with the user id (which can be the username). AMS then creates a log file tagged with the user id, date and time, and opens it for writing. Use Case 4: End Session Actors: CU-WME User. This use case starts when CU-WME User requests to end a work session on CU-WME. AMS unregisters the session by removing the session s information. AMS then closes the log file of the user s session. Use Case 5: View Log Actors: Administrator, Project r. This use case starts when Administrator or Project r requests to view log files of the work sessions of a particular user. AMS displays the list of all the log files of the work sessions of that user, sorted in order of date/time. Administrator or Project r selects a log file to view. AMS displays the contents of the log file. Page 3 of 6

5 Fully-dressed Description of Log Operation Execution Use Case Assignment 3 Use Case 1: Log Operation Execution Level: Purpose: User-Goal This feature allows the CU-WME users to log their activities. Primary Actors: CU-WME User and components of CU-WME (i.e. Change ment, Collaborative Publication, User ment, File ment and Project ment. Stakeholders and Interests: - CU-WME User: Wants to log their activities. - Change ment : Wants to log the execution of their operations (e.g. create repository, delete repository, add new files to repository, delete files from repository, create new version, merge versions etc.). - Collaborative Publication : Wants to log the execution of their operation, publish document. - User ment : Wants to log the execution of their operations (e.g. create user, delete user, create role, delete role, edit role etc.). - File ment : Wants to log the execution of their operations (e.g. copy file, delete file, create directory, remove directory etc.). - Project ment : Wants to log the execution of their operations (e.g. create task, modify task, delete task, create schedule, edit schedule etc.). Preconditions: CU-WME User has been identified and authenticated. The session for the CU-WME User has been started. The log file of this session tagged with the user id (which can be username), date and time has been created, and is now open for writing. Success Guarantee: The success or failure in executing the operation has been logged in the log file. Main Scenario: 1. CU-WME User requests to execute an operation on any of the components of CU-WME, i.e. Change ment, Collaborative Publication, User ment, File ment and Project ment. 2. AMS appends current date and time for the request of execution of the operation to the log file of the user s session. 3. AMS directs the corresponding component of CU-WME to execute the operation. 4. The component finds the operation does not need authentication of the user. 5. The component then executes the operation and returns the flag indicating success to AMS. 6. AMS appends the date and time of successful execution of the operation in the log file of the user s session. Page 4 of 6

6 Assignment 3 Extension: 4a. The component finds the operation needs authentication of the user: 4a1. AMS performs Authenticate Operation Execution use case. 4a2. The component receives the flag indicating the user is authenticated to execute the operation. Branch to 5. 4a2a. The component receives the flag indicating the user is not authenticated to execute the operation: 4a2a1. The component returns the flag indicating failure to AMS. 4a2a2. AMS appends the date and time of the failure in executing the operation in the log file of the user s session. 5a. The component fails to execute the operation and returns the flag indicating failure to AMS: 5a1. AMS appends the date and time of the failure in executing the operation in the log file of the user s session. Special Requirements: - No interrupt from the user will be accepted by CU-WME, after receiving the request to execute an operation from the user till the use case ends. Component Consistency Summary Use Case Diagram of CU-WME CU-WME Administrator Files Backup Repository Contents Project Assistant Publish Documents Achieve Millstones Project r Users Operate Projects Teams CU-WME User Activity Page 5 of 6

7 Discussion on Consistency with other components of CU-WME Assignment 3 The use case of Managing Activity is primarily handled by the Activity ment. All the requests of the users to execute any kind of operations of any components of CU-WME is first received by the Activity ment so that the initiation of the operation can properly be logged with date and time. Again, after the corresponding component executes or fails to execute the operation, its completion is also properly logged with date and time by the Activity ment. The Activity ment also allows the feature to authenticate the execution of any operation of any component by the use to session. Page 6 of 6