Overview
The MAUI architecture is made up of layers of technology that work together to provide the infrastructure needed by the various functional applications.
| Layer | Description |
|---|---|
| Interfaces | Provides the various interfaces for interacting with MAUI, from the web screens that most use, to the programmatic interfaces for accessing MAUI data via departmental applications. |
| Applications | The functional applications that contain the unique business rules for the various Provost departments. Examples include Prospects, Applicants, Courses, Enrollment, Degree Evaluation, etc. |
| Services | These are generic services that all parts of the application can make use of. Examples include: Identity management, batch processing, communication, workflow, etc. |
| Development Environment | The languages, libraries, tools and processes that developers use to build the MAUI application. |
| Database | Stores all of the MAUI data. Different views of the data help solve different problems (transaction processing vs reporting) |
| OS, Network | The machines that run the web and database servers and the networking to manage connections in a secure way. |
| Other Resources | On-campus (active directory, Nolijweb) and off-campus (verisign/paypal) services that we need to integrate with |
The architecture team is responsible for all of the layers below the applications. The developers on the architecture team implement the following services as part of the service layer that all of the other developers rely on.
| Service | Description |
|---|---|
| Batch Processing | Infrastructure to support jobs that either take a while to complete or need to be run on a regular basis |
| Communication | Sends and tracks communications with students and others from MAUI. This handles both letters and email communication as well as text messages and other formats in the future. |
| Configuration and Lookup | Manages configuration information and lookup values (state codes, country codes, etc.) |
| Data Import and Export | Services for importing and exporting large amounts of data into and out of MAUI. |
| Electronic Folder | Consolidates communication and forms into a single electronic folder that holds all of a student's important paperwork in a single virtual file |
| Identity Management | Everything associated with people and keeping just a single record representing a person. Duplicate checking, record merge, synchronization with NAMS, and security all build on top of identity management. |
| Logging | Changes to data, viewing data, and other important business events are all logged in MAUI. |
| Metrics, Monitoring, Management | MAUI tracks important business metrics as well as internal metrics that allow us to monitor usage, performance and other factors that allow us to keep MAUI up and running |
| Reporting | Individual reports will be developed by the functional areas, but providing a consistent reporting infrastructure (such as remodeling the data) is the responsibility of the architecture team. |
| Workflow | Workflow allows us to model business processes in the application and track the flow of information through those processes. |
