September, 2011: A fifty-five page requirements document has just been completed. Now we are performing a check off exercise to see if Grouper will meet most of what campus leaders have set forth as their business needs. Stay tuned for results.
November, 2011: The Groups and Affiliations Management Service project team is conducting architecture sessions. What are the components of the service and how do they relate to one another? Grouper has been selected as the center of the service.
December, 2011: Many design meetings were conducted. Within them we 1) articulated a Registration Flow for adding new people not already in our Person Hub, 2) developed some use cases, 3) identified some APIs between the components of our Group and Affiliation Management Services (GAMS), 4) adopted a set of stem and group naming standards, and 5) drafted specifications for a new Special Populations repository for those who are not already known to the University. Next steps include defining a more comprehensive system design, mocking up some User Interfaces for the registration process, and playing with Grouper in a DEV environment.