Integration Vs Interfacing in a Student Information System
Written by Brendan Croese Tuesday, 13 December 2011 11:43
In the world of Student Information Systems sellers often use the term "Integration". Many claim to include a completely integrated cashbook suite, which is in fact a product in its own right, while others claim a fully integrated scheduling program when in truth they are interfacing with an external Timetabling package. This integration is attained by interfacing and moving a subset of information between the packages. Examples like a Student Management System that is employed to store student and family details while a completely separate Library Software System are employed. In this latter eventuality student's class and demographic info are transferred between the 2 packages. Such updates might be automated through scheduling routines or require human intervention to guarantee regualr massaging of the information.
Such integration(using numerous separate packages while externally synchronising info between them all) has an advantage in that the user can look in the market for the "best fit" package if it is supported by the SMS integration. Alternately procure the product of choice and in house create the program info update. This is often a pricey process and may require re-working if either seller modifies their program directions.
Where interfacing replaces true integration the systems are liable to breaking when either seller issues updates which can lead to severely out of date information, or worse corrupted data.
True integration is when the full collection of software is controlled by a single vendor and all info is stored in a single data store. The advantages of true integration are several including:
- cost savings
- common feel and look
- common support
- single information location
- straightforwardness of backup
- currency of data (no interface time lag
- trustworthiness of info (single entry)
- straightforwardness of reporting across all info enabling complicated management reports unavailable in non integrated systems
Clearly the perfect solution is a fully integrated single database where all parts provide a "best fit" solution. Such a Student Management School Software solution is found at www.pcschool.net PCSchool integrates
- Attendance
- Curriculum
- Finance
- Library
- Point of Sale
- Calendar
- Interview Booking
- Single rock solid SQL database without any limit.
About the Author:
Author: Brendan Croese Dip Bus, Grad Dip. Teaching, B Business.Brendan is the first writer of the software package PCSchool. For more information seehttp://www.pcschool.net For information on new initiatives in PCSchool go tohttp://studentmanagementsoftware.wordpress.com/
| Next > |
|---|