2 days The course is an abbreviated version of a longer more in depth 5 day course. Concentration of the course will be on parts 2 Planning, 5 Stakeholder Needs, 6 Mapping, 7 Planning the Database Back End, 9 Design and 11 Development and Coding.
A basic knowledge of creating web pages although not totally necessary. A knowledge or an involvement in what is required in the day to day running of the school. A knowledge of basic databases and simple SQL. Prerequisites are generally recommended but not necessarily required
Who should do this course:
Technical Staff, Teachers and Administrators who want to create or have a need to contribute to the school’s intranet using database managed processes to create electronic formats for the running of the school.
Participants will be able to create processes that allow for retrieval, addition, editing and secure viewing of database managed WebPages on an intranet/internet. The course will follow the process of the System Development Life Cycle (SDLC) adapted to the unique process required for the school School Intranet Development Life Cycle (SIDLC). The result of the week will be the ability to link into the databases around the school and create web pages from that data while also developing useful process tools on the web such as class lists, attendance rosters, discipline and achievement records, parental information, medical information, sports days, subject selection etc. The approach to the course will combine the use and promotion of the school’s intranet using available resources at the school, sourcing outside contractors and using off the shelf products.
1. Introduction to the brief.
The intranet should have an outline of the needs wants and desires of all the key stakeholders. We will go through a classic brief out what a school requires and who requires discussing the implications of each as we go. We will alter this brief to suite the purposes of the training course.
In this section we plan out each section of the project to give ourselves a timeline of completion for each phase. Usually done in a software package such as MS Project. This will include organising meetings with all the key stakeholders to methods of obtaining feedback on the intranet.
3. Server Requirements for the intranet to function.
Making sure that the server/intranet will display our pages as we create them.
4. Setting Up our intranet on our local server
Setting up our development machine with all the relevant local servers to enable us to test our intranet as we develop it. We will start to develop our testing procedures here also.
5. Stakeholder Needs
Setting Up meetings to enable us to list all the stakeholder requirements. This will also set us on the path to creating the necessary levels of security in our system.
A full map of page flow and process flow of the intranet is developed. This is best created in MS Visio.
7. Planning the database back end
Creation of the necessary tables to generate the pages in our intranet. This would also include any links with databases within the school.
8. Phasing the plan
Creating escape points in the intranet plan where we can go live with sections of the intranet to allow staff to use and learn the functions of the intranet as it is developed.
Creating any template pages that we can use in the intranet. This is essentially headings, page formats and styles throughout.
From the phase plan we work out the necessary menus required at each implementation phase so as to not create redundant menus.
11. Development and Coding
Creation of the pages. It is in this section we learn the CFML, HTML, SQL, Java and ASP to create our pages. From here we code the pages. The first section would be the log in pages.
12. Integration and Testing
Each section is tested locally. Upon each test we add to the testing document so that a full test can be carried out at the implementation of each phase.
Publishing to the intranet and internet. Live testing.
14. Operation and Maintenance
Tips on what to expect from the staff when the system goes live. How to create impressive help files and training tips.
15. Continuous Improvement
Creating feedback areas and also planning for upgrades and improvements.
16. A look at off the shelf products
We will look at some of the off the shelf products which are relevant to all schools which will circumvent much of the code that is required by all schools.
A discussion forum between the group time permitting