Home - TechInnovaSolution/Mentor-management GitHub Wiki
Requirements Analysis
1. INTRODUCTION
PURPOSE OF THE SYSTEM
The transition between High School and University can be such a gruelling experience. Students encounter many challenges during the year; many of them are unable to overcome those challenges because of a lack of proper guidance. There exists mentorship programs on campus to tackle those problems, but most of them have proved ineffective. The main reasons are because prospective mentees are not motivated enough to walk to a particular location in order to sign up for the program and because of an inefficient follow up structure. The Mentor Management application is being developed to bridge that gap. It aims to create an efficient system that allows mentees and mentors to sign up at their comfortable location and using any device. It also enables mentees to receive briefings and schedule meetings from the application. This application serves as a connection between mentees and mentors.
SCOPE OF THE SYSTEM
The system allows screen size responsiveness and can thus run on any kind of device including desktop computers and mobile devices. It is designed as a self-service application where mentees and mentors can fill information themselves. It also comprises an administrator whose job is limited to monitor the transactions between mentors and mentees. A help menu is incorporated for users who are struggling to use the application. In developing the application we assume that prospective mentees know the importance of getting mentored, the job of making students aware is generally carried out by the Counselling and Career Department of the university. The system is built only for the purpose of facilitating fast and reliable sign up process. Although the application enables scheduling of meetings, those meetings are to be held physically, that is, the pair has to meet in person. The system does not allow online meeting through audio or videoconferencing.
OBJECTIVES AND SUCCESS CRITERIA OF THE PROJECT
The system will be considered a success if:
- It allows any kind of users (Administrator, Mentor, and Mentee) to sign up and login.
- It successfully captures the users’ information into the database.
- It facilitates the matching of Mentor-mentee according their background.
- It is able to schedule meetings of the pair.
DEFINITION, ACRONYMS AND ABBREVIATION
Application System: An application program (app or application for short) is a computer program designed to perform a group of coordinated functions, tasks, or activities for the benefit of the user.
System administrator: A person who is responsible for managing a multi-user computing environment.
Mentor: A person who gives a younger or less experienced person help and advice over a period of time, especially at work or school.
Mentee: Someone who is given support and advice about their job by a mentor. Screen size responsiveness: A design method that allows tailoring of content to different screen sizes. User-friendly System: A system that is easily operated and understood by means of a straightforward guide in jargon-free language.
REFERENCES The above definitions were taken from the CAMBRIDGE ONLINE DICTIONARY and Google-enabled dictionary.
OVERVIEW
This Requirement Analysis Document provides the description of the general outlook of the Mentor Management Application. The proposed solution of the system and all the functional and non-functional requirements are found below to help the stakeholders have a full understanding of the system which will deliver SSS Mentor-mentee services.
2. Current System
Currently there is no system that can help university students find a mentor. A mentor is necessary to assist students know what careers correspond to the degree that they are studying or hope to study, what combination of courses are recommended for a career their hoping to pursue and overall give the particular student advice on their professional life. Because tertiary is very challenging and confusing for a lot of students, guidance from a more experienced individual that has either been through the same challenges and was able to rise above them or someone who has achieved this student’s set goals, would prove very resourceful to a majority of students. For instance, a student studying a BSc in Biology might have passion about nature and animals but in the midst of their university career start to wonder what they could do with their qualification, or whether they need to study further to enter their career of choice. A lot of students spend most of their time on their mobile smart phones/tablets and mentees spend more of their time in front of a computer which is why the system is a web application.
3.1. Functional Requirements
- Allow facilitator to register mentors and mentees onto the system using their details.
- Generate email to both mentors and mentees with their login credentials.
- Allow mentors and mentees to update their profiles.
- Allow mentees to fill in their mentor preference form.
- Filter suggestions of possible mentors that mentees should choose based on preferences.
- Allow mentee to select mentor from list of suggestions.
- Allow mentors to view mentee profiles.
- Allow mentees to view mentor profiles.
- Allow mentors and mentees to fill in evaluation forms.
- Capture and store data from evaluation forms.
- Allow mentors and mentees to have virtual meetings (e.g. Skype facility).
- Allow facilitator to set-up general meetings.
- Allow facilitator to log attendance of general meetings.
- Assign mentors and mentees to a team.
- Allow facilitator to group teams based on their location.
- Allow mentors and mentees to request meetings with each other.
- Generate email to mentor and mentee to confirm that a meeting has been set up.
- Allow mentor to confirm that the meeting has taken place.
- Allow facilitator to upload videos of general meetings.
- Allow mentors and mentees to rate meetings.
- Allow mentor to rate mentee.
- Allow mentee to rate mentor.
- Allow facilitator to add suggestions of activities that can be done for mentors and mentees.
3.2. Non-functional Requirements
Usability
- All delays in the system longer than 0.5 seconds will produce a dialog box that says "Please wait."
- It is possible to reach any given system function from the main window in less than 4 clicks.
- It is possible to accomplish any given task with just the keyboard, without the mouse.
- All buttons in the system will adhere to established button convention (link to established button convention regarding size, naming, position, etc.)
- All screens will have a help button. Each help button on a given screen must provide at least one 'topic' for each control on the screen.
Reliability
- The system will check the all operator inputs to see that they fall within their required ranges.
- The system will check all disks for bad blocks each time it is booted.