
![]() |
e-Macao - Development Project |
![]() |
![]() |
![]() |
This project was a component of the e-Macao Project which was executed from 2004 to 2006. The e-Macao Project aimed at advancing the state of Electronic Government in Macao by establishing a government-wide direction for its development and then creating an initial impetus in this direction within individual agencies.
e-Macao followed five design principles: Project objectives: Gaining experience with e-Government development through the implementation of prototypes for G2C, G2B, G2G. Common functionality is identified and implemented as infrastructure support: Requirements, Modeling, Design, and Implementation.
|
![]() |
During 2006, project activities concentrated on building prototype software infrastructure for e-Government, supporting rapid development and run-time execution of various Electronic Public Services (EPS). Five main infrastructure components were identified, specified and implemented based on the concrete experience building three representative EPS earlier during the project - Social Welfare Service, Business License Service and Government-to-Government Messaging Service. The five components - Front Office Framework, Back Office Framework, Workflow Infrastructure, Messaging Framework and Infrastructure Management Services, jointly span design-time, run-time and maintenance aspects of EPS. A common family of technologies comprising Java, XML, Web Services and the J2EE framework, all based on open standards and open-source software, were applied. To demonstrate the use of the infrastructure, the Business License Service was re-engineered from the standalone to the infrastructure-supported system, with concrete guidelines defined for building new infrastructure-supported EPS. The infrastructure was demonstrated to the Government during two workshops in February and June. G2C e-Service Development: A prototype Social Welfare Approval System has been developed. The requirements for the system were formulated based on the review of 18 Social Welfare Services in Macao and interviews with various agencies that deliver, often cooperatively, such services to the public. UML was used during development and the implementation was done using J2EE and various open-source components. The system was demonstrated to the government during a workshop and a report "Electronic Delivery of Social Welfare Services" was prepared. G2B e-Service Development: A prototype License Approval System has been developed. The requirements for the system were based on the review of 29 Licensing Services in Macao and interviews with various agencies that deliver, often cooperatively, such services to the public. UML was used during development and the implementation was done using J2EE and various open-source components. The system was demonstrated to the government during a workshop and a report "Electronic Delivery of Licensing Services" was prepared. G2G e-Service Development: A prototype Core G2G Messaging Gateway (XG2G) has been developed to support automated messaging between agencies. The requirements for the system were based on the review of G2G collaborations documented during preparatory interviews for G2C and G2B development, as well as G2C and G2B requirements themselves. RAISE and UML were used during development and the implementation was done using JMS. The system was demonstrated to the government during a workshop and a report "Core Government Message Gateway" was prepared. e-Service Middleware Analysis: Based on e-service development experience during the tasks 3 to 5 and review of international best practices, requirements for e-service middleware have been formulated. Four concrete infrastructure components have been identified: Front-Office Framework, Back-Office Framework, Government-Wide Workflow Management and Extensible Gateway for Government Messaging. The requirements were presented to the government as a basis for subsequent development. e-Service Middleware Modeling: Based on the requirements for four e-service infrastructure components obtained during the Task 6, requirements models were formulated in UML. Two kinds of models were created for every infrastructure component: Conceptual Class Diagrams to capture the main concepts of the domain and their relationships and Use Case Diagrams to document and relate individual requirements. e-Service Middleware Design: Based on the requirements models for four e-service infrastructure components, identified and documented through the Tasks 6 and 7, the corresponding design models were formulated in UML. Two kinds of models were created for every infrastructure component: Design Class Diagrams to document the architecture of every component and Collaboration Diagrams to document the interactions occurring between relevant sub-components. |
![]() |
|
![]() |
|








