So it started, the design phase is now on. I started already for the teacher panel and something with the administration panel. It is still a bit bare, I am still putting the contents that make sense. My design skills are still in the hibernation mode so, the detail is a bit off I am hoping to create the body out of it, the whole panel is still out of sync.
As it was defined previously, it will be as simple as a school project. But of course the synchronicity of the contents should be as tight as a drum. It should work as one and look as one. Like any other system the contents should be organized as the data could come from any direction and it is always subject for corrections.
The teacher’s access will have basic panels, the dashboard will have a filter according to the level he/she is handling. It will have so called ‘cards’, that will be grouped by level. The cards will have the number of students on that level and section if there are several. It will also contain the teacher’s schedule id and the status of the grades. The status should be released in every quarter. On that note, there should be no corrections done or it will be requested to admin that will have adjustments on the grades.
Watch out for my next post so I can write about the admin panel.
What to design first? Yes, you read it right, I will be starting to design the admin panel first so the workflow will be the backend first before the frontend, which includes the inquiry forms and login for the students. Why backend to frontend? The reason behind is that the backend will all have the information needed in the frontend. The static pages for the frontend will be less headache than the information or data flow we need in the backend.
We will going to have a login for the administrators (school principals, director) and for the department heads and teachers. If you would picture a school set up this will be a medium size private organization. Basically the teachers can input grades for that day then the initial average will be computed but still the whole grading sheet will be subject for revision so it will have an open status until the teacher will finalize it for that quarter. The administrators can arrange schedules and assign teachers for a grade level. They can also adjust percentages for the composition of the final grades and fees needed per grade level.
The Administrator panel should have the controls to adjust or approve any pending items needed for school management.
The set-up should be minimal but rich with process that will be needed for learning experience. Having this set-up this should cover the school management needs.
Let’s start designing then.
You already have the database, and so how will you execute it?
For geneSIS project we will be going with PHP. The plan is to have it as simple coding as possible for learning reference only.
Though the project will be not as small as we initially think it is, we will learn a lot on building the system. The project will run in PHP MysQL and APACHE via XAMPP. It is a all in one installer from Bitnami.
The target is for the beginners needs some inspiration to start web development. I am excited as a beginner that hungers for new experience.
I already built the database but it will evolve eventually as we go along with the project. The database consists of 5 tables. Four tables for admin parts, and 1 for inquiry.
The inquiry table is more of the potential enrollees or students in the school. The other four is for the schedule, level and of course for the teachers, the other one is for the relationship of the three.