Maturity models (MM) have been introduced, over the last five decades, as guides and references for the information system management in organizations from different sectors of activities. In the education sector, MM have also been used to evaluate higher education institutions (HEI) in several dimensions, such as ICT, management, process management, course curricula, course/HEI accreditation, e/m-learning, online courses and pedagogical strategies. The HEI have an enormous complexity due to the specificity and quantity of their processes, demanding capable information systems (IS) and tools to manage these IS. Based on the guidelines of a methodology for a systematic literature review, the MM of different subareas of education are identified and categorized in this paper. For each MM associated with HEI IS, it is identified the methodology of development and validation, as well as the scope, stages and their characteristics by dimensions. This study resulted in the need to develop a MM for IS that supports HEI in their core business activities and management.

No abstract

No abstract

Abstract. Applications refactorings that imply the schema evolution are common activities in programming practices. Although modern objectoriented databases provide transparent schema evolution mechanisms, those refactorings continue to be time consuming tasks for programmers. In this paper we address this problem with a novel approach based on aspect-oriented programming and orthogonal persistence paradigms, as well as our meta-model. An overview of our framework is presented. This framework, a prototype based on that approach, provides applications with aspects of persistence and database evolution. It also provides a new pointcut/advice language that enables the modularization of the instance adaptation crosscutting concern of classes, which were subject to a schema evolution. We also present an application that relies on our framework. This application was developed without any concern regarding persistence and database evolution. However, its data is recovered in each execution, as well as objects, in previous schema versions, remain available, transparently, by means of our framework.