Selecting And Viewing Staff Information And Availability

Your teammates should be selected from other students in your tutorial group. To register who is in your team, go to the Groups page on the unit’s MyLO site and select a group from the Assignment 1 list. Groups are named according to the tutorial group they are for. For example, if you are in the Tuesday 9am tutorial then pick one of the teams named is one of the team numbers. Join a team of your choosing (but discuss it with any other members first). You can
see who else is currently in a team before you add yourself to it by clicking the #/3 link on the Groups page. If it becomes necessary to form groups larger than three then you will need to contact the unit coordinator.

Your team will have access to its own discussion forum and MyLO locker (for sharing files). You do not have to use these. If you prefer another file sharing mechanism, such as Dropbox or a Google Doc for the scenarios, then you may use it instead. Your team will also have a single submission point in the Assignment 1 folder on MyLO.

Deliverables
There are five components of the deliverables in this assignment (items 2–6), which should be submitted in a single PDF in the following order.
1. A title page showing the name and number of the assignment and your group name
2. A structured scenario for each use case (7 in total)
3. Low-fidelity (lo-fi) prototypes of the UI views (hand-drawn or simply-sketched on a computer)
4. A package diagram
5. A class diagram for each package (about 3–5 in total, depending on the number of packages)
6. A sequence diagram for each scenario (7 sequence diagrams in total)

There are many tools for merging PDFs into a single document, such as this one (provided as an example with no warranty expressed or implied). If it is not possible to submit a single PDF then each component of the submission must still be in PDF; do not submit image files of your lo-fi prototypes.

Precondition

In this use case user view the all staff list and filtered staff list. At the home page a button is present. User just clicks on it and view the staff list. This list contains information related to staff family name, given name (title). This information arrange in alphabetically order by family name. In this use case user filter staff list in two ways: first one to filter by gender and second one to filter by category.

Precondition:

            RAP database exist and is populated with data.

Scenario:

Action	Software reaction
1.       User starts application	1.       Main view created with StaffListView and adjacent StaffListView visible. 2.       System retrieves basic staff information from the database: name, gender and category. 3.       Researchers are sorted alphabetically by family name. 4.       System shows names in staff list view.
2.       User select gender from the dropdown list	1.       System updates current set of filter to include selected gender. 2.       System create temporary list of staff. 3.       System refreshes the StaffListView with the filtered list.
4.       User modifies text in filter by name text field	1.       No reaction; not support to automatic refresh of list contend.

Scenario Notes:        

            Action 1 is precondition for all other action. The reaction of action 2 and 4 produce the intersection of two filters.

Post Condition:

            StaffListView display all subset of staff list.

Required View:

            StaffListView

Exceptions:

             If database is not exist or any other error occurs the system display a message to user. Request to user to close and restart the system.

Use case utilized:

            UC8_User_views_StaffList

Scenario 02: -

Use case #02: User_select_StaffList

Requirement:

            When the user selects a name in the list the system will show more details about the staff member (referred to as the Staff Details view), which should include: Name; Campus; Phone Number; Room Location; Email Address; Photo; Consultation hours; Table of units he or she is involved with in the current semester.

Overview:

            In this use case user select the staff from staff list. When user selects a staff from staff list, then system refresh the staff list with the staff information list. This information contains staff name, campus, phone number, room location, email address, photo, consolation hours, and table of unit.

Precondition:                                                                               

• RAP database exist and is populated with data.
• A staff list selected by the user from staff list view.

Scenario:

Action	Software reaction
1.       User start application	2.       Main view created with StaffListView and adjacent StaffListView visible. 3.       System retrieves basic staff information from the database: name, gender and category. 4.       Researchers are sorted alphabetically by family name. 5.       System shows names in staff list view.
2.       User filter the staff list by name or gender	1.       System accepts the user filter requirements. 2.       System creates a temporary the staff filtered list in staffListView. 3.       System refreshes the staff with the filtered list.
4.       User selects the name of staff from list.	1.       System accepts the user selected command from StaffSelectView. 2.       System creates a temporary list of information of user selected name. 3.       System refreshes the current list with selected staff information list.
5.       User selects a unit code from staff information list.	1.       System accepts the user selected command. 2.       System creates a temporary list of staff availability information of user selected unit code. 3.       System refreshes the current list with the staff availability list.

Scenario Notes:

            Action 1 is precondition that required performing other actions. Action 2 is optional to perform action 4. But action 4 is also required to perform action 5.

Post Condition:

            System displays the activity list of a particular staff member.

Required View:

            StaffSelectView

Exceptions:

            If database is not available or user selected unit code information is not available in the database the system display error. Please restart or stop the system or this information is not available.

Use case utilized:

            UC16_User_selects_StaffDetail

Scenario 03: -

Use case #03: User_show_ActivityGrid

Requirement:

            It would enhance the Staff Details view if the staff member’s activity (classes and consultation times) across a week could be displayed in a colour-coded grid

Overview:

            In this use case when user click on time table option in staff information list then it display the activity grid of that staff. In this activity list system display the days of week as columns and hours of the day as rows.

            Precondition:

            User selects a unit code from particular staff employee.

Scenario:

Action	Software reaction
1.       User selects a unit code of particular staff employee.	1.       System selects the user selected command. 2.       System creates a temporary list of select staff employee’s unit code availability list. This list creates in the form of table. Column displays the day to week and row displays the hours. 3.       System refreshes the staff employee list with the availability list.

Scenario Notes:

             To do action 1 user need to select a staff employee from the staff list.

Post Condition:

            User views unit list of a selected employee.

Required View:

Scenario 01: User Views Staff List

            StaffDetailView

Exceptions:

            If selected staff employee activity list not available in the database then system display an error message to user. This list is not available.

Use case utilized:

            UC19_User_shows_ActivityGrid

Scenario 04: -

Use case #04: User_Views_UnitList

Requirement:

            The system should be able to generate a list of the units under the control of the School, ordered alphanumerically.

Overview:

             In this use case the user view the all unit list by clicking the time table button on home page. This list is arranged in alphanumerically.

Precondition:

            User select a staff employee from the staff list and system display the time table of staff with unit code, unit and other information.

Scenario:

Action	Software reaction
1.       User select the staff from staff list	1.       System accepts the user command from staffselectview. 2.       System generates a temporary list of staff time table information. 3.       System refreshes the staff list with staff time table list.
2.       User alphabetically order the unit list	1.       System accepts the user sorted command. 2.       System generates the temporary sorted unit list. 3.       System refreshes the current unit list with sorted unit list.

Scenario Notes:

            Action 1 is required to perform the action 2.

Post Condition:

            User selects the unit from unit list.

Required View:

            UnitListView           

Exceptions:

            No exception. System sorted the unit list in alphabetical order.

Use case utilized:

            UC23_User_View_UnitList.

Scenario 05: -

Use case #05: User_Select_Unit

Requirement:

            Selecting a unit from this list should bring up a list of classes for that unit, ordered chronologically.

Overview:

            In this use case when user click on a particular unit from a unit list then it display the list of classes of the unit. This list contains the information related to day, start time, end time, type, room location, campus, staff member. User can also able to filter the classes by campus name.

Precondition:

             User views the unit list.

Scenario:

Action	Software reaction
1.       User select a unit from unit list	1.       System accepts the command from unitlistview. 2.       System creates a temporary list of selected unit class’s time list. 3.       System refreshes the unit list with the selected unit class’s time table list.
2.       User selects a staff from the unit class time table.	1.       System accepts the command in selectunitview. 2.       System goes to the staffdetailview to display that staff information.
3.       User filters the time table to view a single campus detail.	1.       System accepts the filter command. 2.       Create a temporary list of a single campus. 3.       Refresh the list with the selected single campus information list.

Scenario Notes:

            Action 1 is required to perform action 2 and 3. If you want to perform action 3 then you need to perform action 1 first.

Post Condition:

            User generates heat maps.

Required View:

            SelectUnitView, SelectStaffView, StaffListView

Exceptions:

             If unit classes list not available in the system then system display an error to user tis list is not available.

Use case utilized:

            UC24_User_selects_Unit

Scenario 06: -

Use case #06: User_generate_HeatMap

Requirement:

            It would enhance the application’s utility if it could generate ‘heat maps’ of activity across the week.

Overview:

            In this use case the user select a unit from the unit list and click dropdown heat map button. There two option in heat map; one is unit classes, second is consultation time. User able to generate two types to heat map.

Precondition:

            User views the unit list in UnitListView.

Scenario:

Action	Software reaction
1.       User selects a unit from unit list and tap heat map dropdown button.	1.       System accepts the user command. 2.       System list to heat map option in dropdown list. One is unit classes and another is consultation time.
3.       User select unit class option	1.       System accepts the command. 2.       Create temporary selected unit classes list. 3.       Refresh the unit list with the unit classes list.
4.       User select the consultation time option	1.       System accepts the command. 2.       Create a temporary consultation time list. 3.       Refresh the unit list with the consultation time list.

Scenario Notes:

            Action 1 is required to perform action 3 or 4. If you perform action 4 then action 3 is not required only action 1 is required.

Post Condition:

            No post condition

Required View:

            HeatMapView, StaffListView, StaffSelectView, UnitListView

Exceptions:

            If any list is not available then systems display the error message to user; this list is not available.

Use case utilized:

            UC28_User_genrate_HeatMap

Scenario 07: -

Use case #07: User_generates_ClashMap

Requirement:

            It would further enhance the application’s utility if it could generate a variant of the heat map that shows clashes between a unit’s classes and the consultation time of staff involved in teaching that unit.

Overview:

            In this use case user generate clash map. Firstly user selects a unit from unit list and click on clash map button. System display all clash units by word “clash”.

Precondition:

            User views the unit list in UnitListView.

Scenario:

Action	Software reaction
1.       User selects a unit from unit list and select Clash Map button.	1.       System accepts the user command. 2.       System create temporary list of Clash Map list. 3.       System refreshes the unit list with the clash map list.

Scenario Notes:

            User view the unit list before perform the action 1.

Post Condition:

            No post condition. Just go to back or home page.

Required View:

            ClashMapview, StaffListView, StaffSelectView, UnitListView

Exceptions:

            If selected unit class list is not available in the database then system display the message to user this clash map is not available.

Use case utilized:

            UC37_User_generates_ClashMap

Alhir, S. (2003) Learning UML. Sebastopol, Calif.: O'Reilly.

Ambler, S. (2003) The elements of UML style. Cambridge: Cambridge U.P.

Ambler, S. (2005) The elements of UML 2.0 style. Cambridge [U.K.]: Cambridge University Press.

Dennis, A., Wixom, B. and Tegarden, D. (2015) Systems Analysis and Design. New York: Wiley.

Eliot, G. (2016) The mill on the Floss. New York: Open Road Integrated Media.

Harmon, P. and Sawyer (1999) UML for Visual Basic 6.0 Developers. San Francisco, Cal.: Morgan Kaufmann.

Harmon, P. and Watson, M. (1998) Understanding UML. San Francisco, CA: Morgan Kaufmann Publishers.

Holt, J. (2007) UML for systems engineering. London: The Institution of Electrical Engineers.

Kimmel, P. (2011) UML demystified. New York: McGraw Hill Professional.

Mason, D. and Willcocks, L. (1994) Systems analysis, systems design. Henley-on-Thames: A. Waller.

Naiburg, E. and Maksimchuck, R. (2002) UML for database design. Boston: Addison-Wesley.

Siau, K. and Halpin, T. (2001) Unified modeling language. Hershey, Pa.: Idea Group Pub.