Examining ubiquitous security-capital issues in implementing a Campus-System-as-a-Service(CSaaS) model in the cloud computing age: Case study sub-Saharan region

The system was envisioned as a benchmarked model to build Campus-System-as-a-Service (CSaaS) in a cloud computing environment. The CSaaS architecture model demonstrated that building such a system requires strong improvements in security which in turn insists upon a huge budget to accomplish its obj...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Hauptverfasser: Mbale, J., Mufeti, K., Hamutenya, V.
Format: Tagungsbericht
Sprache:eng
Schlagworte:
Online-Zugang:Volltext bestellen
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:The system was envisioned as a benchmarked model to build Campus-System-as-a-Service (CSaaS) in a cloud computing environment. The CSaaS architecture model demonstrated that building such a system requires strong improvements in security which in turn insists upon a huge budget to accomplish its objectives. The demand and acquisition of an exorbitant budget poses a challenge to the sub-Saharan institutions due to scarcity of resources. Nevertheless, a solution was sought. The concept of a consortium was put forth to combat their deficiencies. Some examples of these African consortia are: the Partnership for Higher Education in Africa, involving eight (8) universities; The Higher Education Institutions (HEIs) in Western and Central Africa comprising a hundred (100) institutions, the initiatives for the formation of National Research and Education Network (NRENs), are but a few of such organizations. All such assemblages demonstrated the capacity of sub-Saharan campuses to pool their material, capital and human resources together in a way that would exploit technologies like cloud computing. The CSaaS architecture model demonstrates how the underlying consortium campuses can be connected through the CSaaS system to the cloud. Such a system would be capable of managing Campus Management Systems which would include: student registration, examinations, student results, students learning materials, library information, research, scholarships, admission information, undergraduate and postgraduate programmes, student recreation, website, eLearning, internship, alumina, timetable, campus strategic plan, institution estate, hostels, dining and kitchen, campus clinic/hospital, staffing, administration, etc. With such a huge range of applications, the consortium members would only pay for the services on demand. They would not be responsible for the provision of maintenance and services of hardware and software facilities.