Skip to end of metadata
Go to start of metadata
ANALYSIS
CustomersIdentify customers and their business needs: who needs the groups, when do they need them, for how long, and for what business reasons (email, sharing, access control, etc.).
Application UseIdentify what applications the customers needs to use with the groups.
Membership (Business Definition)Define the desired group membership(s) – who's included and who isn't – in business terms and business rules used by the customer to describe the group membership(s).
Business ProcessIdentify the business process (e.g. student registration, course enrollment, employment, research administration) that masters data that matches the desired group membership(s).
System of RecordIdentify the authoritative system of record where the institutional data is defined and mastered.
Business DomainIdentity the business domain(s) from UW Data Map.
Subject AreaIdentify the subject area(s) from UW Data Map.
DESIGN
TypeDefine the group type. Do the reference groups represent a simple group, a role, or a permission?
Home GroupChoose a home group that aligns with the UW Group Naming Plan and the business domain of the related institutional data.
Group IDs

Define the group IDs and subgroup IDs that customers need to identify and reference. Some business processes master data that can be used for IDs.

Since the membership only includes Seattle branch, shouldn't the ID represent that it's not all first year students? e.g.

uw_affiliation_student-seattle-first-year-2016

uw_affiliation_student-first-year-2016

Display Name

Define user-friendly display name values for contexts where groups are searched, listed, or selected by display name. Some business processes master data that can be used for display names.

Since the membership only includes Seattle branch, shouldn't the display name represent that it's not all first year students?

UW Seattle First Year Students 2016 

UW First Year Students 2016

Lifecycle Policy (Creation)

Define when the groups will be created. Some reference groups are created or "pre-provisioned" automatically. Other reference groups are created only by customer request.

How long does this 2016 group need to exist?
Is there a need to create a 2017 group next year? If so, when?

Lifecycle Policy (Deletion)

Define when the groups will be deleted.

How long does this 2016 group need to exist?
Is there a need to create a 2017 group next year? If so, when?

Membership (Direct)

Define the direct memberships of the groups and subgroups.

Since the membership only includes Seattle branch, shouldn't the membership definition represent that it's not all first year students?

UW Seattle students admitted for their first year for Summer or Autumn 2016: students enrolling in college directly after graduating from high school, regardless of the number of credits they are "transferring" to the UW (via AP, IB, Running Start, College in the High School, etc.)

Membership (Exceptions)

Define how membership exceptions are managed, both additions and deletions.

None

Membership (Grace Period)

Define the grace period on membership, if needed.

None

Membership (Opt-in)Define the opt-in policy for the membership, if needed.
Membership (Opt-out)Define the opt-out policy for the membership, if needed.
Contact Person

Define the contact address.

None

Description

Define descriptions that help potential customers understand fit for purpose and use, including lifecycle policy, membership policy, data quality standards, appropriate use guidelines, access control policy, ownership, and contact information. Some business processes master data that can be used for descriptions.

Since the membership only includes Seattle branch, shouldn't the description represent that it's not all first year students?

UW Seattle students admitted for their first year for Summer or Autumn 2016: students enrolling in college directly after graduating from high school, regardless of the number of credits they are "transferring" to the UW. This group is updated nightly from the Student Database. It is available for appropriate business purposes in support of programs designed for UW students. Access to the membership is controlled because it contains a limited amount of student information that falls under the protections of FERPA. See http://www.washington.edu/students/reg/ferpafac.html for more information about use of FERPA-protected information. Please contact help@uw.edu for questions about using this group.

More InformationDefine where additional information for customers will be located.
Application Settings (Exchange)

Define the status and settings for use in UW Exchange.

Inactive

Application Settings (Google)

Define the status and settings for use in UW Google Apps.

 Inactive

ACCESS CONTROL
Data CustodianIdentify the responsible data custodian(s).
Classification

Determine the appropriate UW data classification (Public, Restricted, Confidential).

Restricted

Access Control PolicyDecide and document the access control policy including membership viewer control, sender control, appropriate use guidelines, terms and conditions of use, etc.
Membership Viewer ControlDefine the membership viewer control, including exceptions to the access control policy.
Sender ControlDefined the sender control, including exceptions to the access control policy.
IMPLEMENTATION
Data Source

Identify the service that will be used as the data source for provisioning. It may or may not be the same as the system of record.

Master: Student Database (SDB)
For Provisioning: EDW (UWSDBDataStore)

Membership (Technical)

Define the technical definition of the memberships in terms used by the data source and its data elements, as well as any additional filtering.

SELECT DISTINCT sr_adm_appl.system_key, sr_adm_appl.appl_qtr,
sr_adm_appl.appl_yr, sr_adm_appl.appl_status, sr_adm_appl.appl_branch,
sr_adm_appl.advance_payment, sr_adm_appl.appl_type
FROM sr_adm_appl
WHERE (sr_adm_appl.appl_qtr IN (3,4)) AND (sr_adm_appl.appl_yr = 2016) AND
(sr_adm_appl.appl_status IN (11,12,14,15,16)) AND
(sr_adm_appl.appl_branch=0) AND (sr_adm_appl.advance_payment=true) AND
(sr_adm_appl.appl_type="1");

ProvisioningDefine a provisioning model for data integration and reconciliation that ensures the groups are created in accordance with their lifecycle policy and managed in accordance with their data quality standards.
De-ProvisioningDefine a de-provisioning model that ensures the groups are deleted in accordance with their lifecycle policy.
MonitoringDefine a monitoring solution that helps identify incidents and problems, particularly those that impact availability and reliability.
Data Quality Standards

Define data quality standards under normal operations, including data validation rules, timeliness of updates, defined error rates, integrity monitoring, and reliability. The standards will depend on the business process, system of record, data source, provisioning and de-provisioning models, monitoring, and operations.

Internal DocumentationDefine what internal documentation will be developed and where it will be maintained.
Customer DocumentationDefine what customer documentation will be developed and where it will be maintained.
Communication PlanDefine the communication plan to inform audiences about the new reference groups.
OPERATIONS
Request FulfillmentDefine how requests will be fulfilled. For example, standard requests for information, access to memberships, membership exceptions, email settings, design changes, etc.
Incident ManagementDefine how incidents will be handled.
  • No labels