Team Error

According to tdan.com, an enterprise data model is an integrated view of the data produced and consumed across an entire organization. It represents a single integrated definition of data, unbiased of any system or application. It is also independent of “how” the data is physically sourced, stored, processed or accessed. In the second iteration, Team Error has designed an enterprise logical data model for Miami University. This Model focuses specifically on 4 business components: Niihka, Library, Building Access, and MyCard, and how they interact with BannerWeb, the  administrative software system used by Miami University.

 

We used  UML(Unified Modeling Language)  to provide a concise design of the system and to illustrate relationships(one-to-one, one-to-many, and many-to-many) between various entities represented. We also used colors to group modules with their respective submodules. The choice of colors is independent from ones used in both the Application Context and Application Integration Models.

 

• BannerWeb Entity: In this model, BannerWeb Entity represents a high-level abstract view of all the data that exists in BannerWeb. We added it to show its relationship with the identity module.

 

• Identity: An identity is  a person(student, faculty, or staff). It represents an abstraction of all data elements that can be derived from a person(Social Security Number, UniqueID, First Name, Last Name,...). Identity is a composition of the BannerWeb Entity. Tt gets all its data from BannerWeb and therefore, cannot exist without it. BannerWeb and Identity have a one-to-one relationship, since no two persons can share the same identification.

 

• Account:  The account model is a composition of the identity and it holds all the required data and functions used by the “identity” to create accounts across the various business components. It is an interface to the 4 main components, explained below:

 

• Niihka Account:  is an interface to both the student and instructor account. As illustrated on the model, the student can view grades and course resources.  The instruction account  can not only view , but also edit them.

 

• Library Account: allows access to online resources, interlibrary Loan & Storage requests, room reservation, and physical resources. The library account is an aggregation of its components(as shown in the Model), since all of them can be accessed and used without it.

 

• Building/Dorm Access Account: allows access to certain buildings on Miami’s campus. It show the composition relationship with the WebCard Service Center(which deals with lost IDs and replacements).

 

• MyCard Account: allows access to the main money accounts( Meal Plan, Mulaa, and MuBucks). Meal Plan and MuBucks are aggregations since they are not required of everybody. However, every “identity” has a mulaa account, even if it has a balance of zero.

 

 

Narrative of Model