The objective of this project is to allow staff to upload an excel sheet of the lecturers and staff who are required to meet in the semester. An automated email will be sent to the staff and students to invite them to book and schedule a meeting on available dates. Only staff and lecturers have the authority to view and print full details of meetings such as student ID and name whereas students can only view and print details of their own booking.
-This Design Document would cover a detailed design specification of the portal, which includes data design, process design, architecture/infrastructure design, and interface design.
Data design is the process of analysing and creating data objects, connection data flow and information. This section of the document will identify the relationships that have been produced in the form of a data dictionary. The data dictionary indicates the connections between objects in the data structure. The section will also include an Entity Relationship Diagram (ERD) and CRUD matrix.
-The process design sections of the document consists of data flow diagrams, expanded use case narratives and pseudocode. Data flow diagrams provide a detailed illustration of the portal’s software elements. For process descriptions, expanded use case narratives have been included to provide a detailed view of the portal.
Architecture / Infrastructure design
-This section of the document includes a three-tiered architecture diagram to illustrate the architecture designed for our MeetMe V2 booking system which consists of the data layer, the process layer and the interface layer. The three-tiered architecture indicates the boundaries, relationship and constraints from user level to database to integrate with each component. This section also defines software components and identifies infrastructure requirements such as capacity, performance, integration & compatibility, platform strategy, security, backup & recovery, scalability, future-proofing
In this section, detailed screenshots of the actual portal will be shown, this provides the client with a better idea of the user interface.
-This design document serves as the blueprint for developing the Meeting scheduling software "Meet Me Version 2" and it attempts to offer a clear picture of the software. It serves as a point of reference for the system. It would help to distribute development tasks across programmers and programming teams. This document should be able to be used to reconstruct the system if it is destroyed.
-The design phase is determined by the following factors:
-The size of the system to be built;
-the complexity of the system; and
-the structure of the design and implementation teams.
-The intended audience for this document is our client, Dr. Florence. The technical aspects of the project are thoroughly explained in detail and discussed in depth. This provides the client with a clearer understanding of how the system works and ensures that if the client decides to hand over the project to another team after the launch, that team is able to maintain the software.
-The “Requirements and analysis (RA)” and “Project Management Plan (PMP)” were prerequisites leading up to this design document. The PMP detailed the timeline, process and overall scope for MeetMe V2. This document further complements the RA by going into further detail the functional requirements to complete the portal successfully.
-The goal of data design is to:
-expand and create data items
-Determine the existence of all data structures and their actions.
-Make a complete data dictionary.
-Make a database design (ERD)
-CRUD Matrix for Data-to-Process.
You project this teaching period is to develop a booking system to be used initially by Murdoch academic staff, (the ORGANISER), to book meeting time slots with multiple students in a set time period. When it is necessary to meet many students academic staff spend considerable time to make all the required appointments. Currently academic staff create a calendar of the meetings and this has proved to be very time consuming. This system is intended to save significant time and make booking the meetings much more efficient.
The system will allow the organiser to upload an excel spreadsheet of all students that require are required to meet the academic. The system would then generate and send a personalized email to each student. This requires the organiser to create a template for that batch of appointments. Upon receipt, the student should be able to click on a dedicated link in the email to arrive at the booking site. The student can then view all available time slots and select their preferred meeting time slot. On confirmation of booking an email will be sent to the student confirming the time and place for the meeting with advise on cancellation issues.
The student will not see any details of other students for interview. The interviewer will be able to view the progress of the bookings and will have access to a calendar (printable on request) of the meeting schedule with the student identity visible. The system should also send a calendar request to Outlook for both the academic and the student/s. NB all previous calendars of meeting are to be kept for record keeping purposes.
The system should be web-based, allowing many academics to use the system at any one time or have an academic having multiple meeting processes concurrently ongoing (multiple calendars) to schedule meetings and be able to make Outlook bookings for both the academic and the student. (i.e., when the meeting is booked and confirmed an automatically generated email should be sent by the system to both the student and Academic which books an Outlook calendar appointment and putting it into a Microsoft Teams calendar appointment) The system should have the ability to have a central administrator with the academics having the ability to register to use MeetMe.