Center for Industrial Technology and Enterprise San Jose, Cebu City
SCHEDULER : A dynamic Schedule Generator REQUIREMENTS SPECIFICATIONS
Jake Quimbo Romnick Revalde Emmanuel Broniola ITP 3E
Chapter 1 Introduction 1.1 Purpose The primary objective of this software is to provide a unique way of setting up your schedules. It enables the users to make their detailed schedule in a less amount of time and effort. This software is primarily designed to be used in schools to prevent the problems of the schedules.
1.2 Scope The project is known as Automatic Scheduler. This software encompasses the following general functionalities: • Dynamic Export to different kinds of document – When users ask for a copy of his schedule in a different document format, he can tell the software to do what he wants. • Dynamic GUI Interaction – Administrators would be able to interact with the system dynamically through the user-friendly GUI which also guides the them all throughout the whole system. • Dynamic Data Manipulation – the software also has the capability to manipulate data dynamically. If an administrator ask for a deletion or addition of a schedule to the database, the software would be able to do so quickly. That’s is how it is being very dynamic.
1.3 Project Constraints and Limitations • •
The software only supports administrator accounts only. The software has no network support.
1.4 Hardware Requirements •
At least 128MB bytes of RAM
Requirements Specifications
2
•
At least 40G of hard disk
1.5 Software Requirements Any Windows Platform xampp (any version)
PHP 4 Browsers like Mozilla Firefox(3.0.7), Opera, Google Chrome, etc. 1.6 Definitions of Terms Administrators – Power users who can only use this software . They all have the privileges that the software can offer. CakePHP – PHP framework used in the software.
1.7 References Gscripts.net En.wikipedia.org Script.aculo.us Cakephp.org
Requirements Specifications
3
Chapter 2 System Analysis
Tables: Users – By default, they are set as administrators, meaning they are entitled to super privileges. Schedule Categories – Database table for assigning groups to each schedule in the database. Schedules – Database table used for storing item data or schedule for a specific date or time.
2.1 System or Software Architecture The major components of the software are: •
Users – By default, they are set to be administrators. Users are assigned to a specific username and password which they use in order to login and use the software. They are entitled to privileges like adding, deleting, editing, etc. of database data.
•
Schedule Categories – These are names of groups of items in the database. A category could be of any sort.
Requirements Specifications
4
•
Schedule – contains the schedule data of the user.
A discussion must follow to describe the interaction of the major components. ) 2.2 2.3 Entity-Relationship Diagram
Chapter 3 Functional Requirements 3.1 Dynamic Conversion to Different Document Type The software gives the user the ability to convert the table of schedule to different types of document such as a .doc file, .xls file, .pdf file, etc. Just one click on the GUI icons and the
Requirements Specifications
5
software will do the rest. The software only requires that the user be able to input necessary information to the forms that the software is asking.
Chapter 4 User Interface 3.2 Main User Interface The main user interface of this software is when the software asks the user to input his name and prompts to him all the available functionalities of the software. The user then clicks on one menu there and then, the software will be the one who will direct the user to a different page where that functionality is present and is used.
3.3 Control 1 The main menus include the following link: Home - main page for logged in users. This will be the first page display after users are finished logging in. Schedule categories – specifies the name of the group of schedules. Schedules – list of schedules in the database. Search – enables users to navigate and search for a keyword. If a match is found by the system, the user would be prompted with the search results.
Requirements Specifications
6
Requirements Specifications
7