Human Resource Information System, | Good Grade Guarantee!
Sample Case Study: Human Resource Information System, Requirements DocumentThis system was developed in an earlier KIT206/506 and will be referred to in some of the online modulesas an illustrative example; it is not the basis of the current semester’s assignments1/3Human Resource Information System1. IntroductionThe ICT Discipline within the School of Technology, Environments and Design requires theHuman Resource Information System. The objective of the system is to provide easy accessfor front desk staff to critical (but public) information about each staff member so they cananswer student queries easily. This information includes phone, room location and the unitsthey teach. The information, which includes both textual data and staff photos, is to bepresented via a Windows 10 application.2. Existing SystemsCurrently this information is available via a disparate set of webpages. The new system willoperate in parallel to these webpages. On the School website on the People page there aregenerated staff lists that give phone and location details:https://www.utas.edu.au/technology-environments-design/people/information-andcommunication-technologyUnit class times can be found on the School timetable, at:https://secure.utas.edu.au/computing-information-systems/resources/timetablesAn alternative timetable layout, for all units across the University, is available at:https://student-timetable.utas.edu.au/#SearchThere also currently exists an administration system that allows the support staff to enter allthe required information into the database to be displayed. This project does not include theredevelopment of this administration system.3. PlatformThe Human Resource Information System must operate within the Standard OperatingEnvironment (SOE) of School desktop machines, which are a mixture of Dell and Appleproducts that all run Windows 10. The information that the system will display is currentlystored in a MySQL database, named the “School Database”, and this database content andstructure cannot be changed. As this system does not include redevelopment of theadministrative entering system that facilitates input of the information into the database, thenew system must work with the existing database.The final system is to be developed using C# and the sources shared with School technicalstaff so that they may maintain it into the future.4. UsersAdministrative and technical support staff will use the new system. Both groups will haveaccess to the same features, so there will be no need to differentiate between users.5. ComponentsThe Human Resource Information System will consist of two main components: staff lists andunit timetable display. These may be enhanced by the addition of another component: searchfacilities.5.1 Staff ListsThe user shall be able to view an interactive list of staff employed by the School. The list willbe accessed by selecting a tab labelled ‘Staff’. Ideally this list should be visually compact. Whenthe 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:Sample Case Study: Human Resource Information System, Requirements DocumentThis system was developed in an earlier KIT206/506 and will be referred to in some of the online modulesas an illustrative example; it is not the basis of the current semester’s assignments2/3• Name• Campus• Phone Number• Room Location• Email Address• Photo• Consultation hours• Table of units he or she is involved with in the current semesterSelecting a unit code in the table of units should take the user to the timetable view (describedbelow). It would also be useful for each staff member’s current availability to be displayed:‘teaching’ (with details of the unit code and room) if they are in a timetabled class; ‘consulting’if it is during their consultation times; ‘free’ otherwise. This would allow front desk staff todirect enquiries appropriately, given a staff member’s availability.The Staff List view should be able to filter the listed staff based on their category. The usershould be able to list all staff, academic, technical, administrative, and casual. The School hasa large number of staff and being able to restrict the list in this fashion will allow the user tofind people quickly.5.2 Timetable displayThe system should be able to generate a list of the units under the control of the School.Selecting a unit from this list should bring up a timetable view of classes for that unit. Thisview should be tabular, showing days of the week by time of day, with the followinginformation in each cell that has a scheduled class for the selected unit:• type (Lecture, Tutorial, Practical, Workshop)• day• time• staff member• room locationIt should be possible to go from a timetable entry to the Staff Detail view for the relevant unitcoordinator or staff member, just as if selecting that person in the Staff List.The user will be able to filter the timetable so that it displays information for a single campus.This feature should make it easier for staff to access information relevant to their location.5.3 Search FacilitiesIt would enhance the application’s utility if the user could also search the database for:• Staff Member by name• Timetable information by unit codeWhile the other views will allow users to filter the lists of results (based on staff category orclass campus), this search functionality would be accessible on a dedicated Search view thatis compact and visible in all other views. The search view will allow the user to indicate whattype of search they would like to conduct (one of the above choices). Based on that choiceone of the following will happen:• Staff Member: the user will enter a name, or part of a name, and the system willsearch the staff database and take the user to the Staff List view, showing all staffSample Case Study: Human Resource Information System, Requirements DocumentThis system was developed in an earlier KIT206/506 and will be referred to in some of the online modulesas an illustrative example; it is not the basis of the current semester’s assignments3/3whose names are partial matches. If the name doesn’t match any staff member thena message should pop up saying “Sorry, there is no staff member matching thatname”. If there is only one match then the Staff Detail view should immediately bedisplayed. This facility should make it quicker for front desk staff to find a particularstaff member’s details by entering partial identifying information. If this searchfunction is implemented it should be possible to ‘clear’ the search to show all staffnames again.• Unit Timetable Information: the user will enter a unit code or part of a unit code (e.g.,KIT206, 506 or 101) and the system will take the user to the Unit Timetable View anddisplay the matching unit codes. If there is no partial match then they will get a popupmessage saying “Sorry, no unit matching that code is offered by ICT”. If there is onlya single match then the Timetable View for that unit should be displayed immediately.This facility should make it easier for staff to quickly bring up information about aparticular unit to answer student queries. If this search is implemented it should bepossible to ‘clear’ the search to show all units again.6. ManualThe system will need to have an associated technical manual. This manual should explain thesystem development so that the system can be maintained by School Technical Staff.
QUALITY: 100% ORIGINAL – NO PLAGIARISM.
- **REMEMBER TO PRECISE PAGE NUMBER**
- Hit The Order Button To Order A **Custom Paper**