Standardized Administration Tools (SAT) Project

(Was: School Administration Tools)

Table of Contents

Project Objective: Purpose

The purpose is to investigate and implement a toolset for administration of CS data such as room/desk purposes and assignment; inventory of rooms by type; people and their positions; visitors and their sponsors; and many other elements. Investigation will include discussion with CS administrative staff, and discussion with other units to determine what tools they have. Implementation will include a CS database, front-ends that are useful to end-users, and automation of workflows where ever practical.

Project Scope/Deliverables

The high-level outcomes of this project are as follows:
  • identification of Administrative tools and functionality for inclusion in database
  • specification of a scope and timeline for Fall 2018 and following
    • what features are critical
    • whether to consider non-CS usage
  • implementation of a postgres database
  • implementation of one or more user front-ends, varieties not specified as of yet

Scope Includes/Excludes

Includes

  • Investigation includes discussion with identified end-users
  • App will cover data for Grad Students, Faculty, Researchers, Visitors, Staff and Undergraduates
  • Making available necessary documentation
  • Importing- or access to- back-data from existing spreadsheets/tools; as much as to be useful

Excludes

See SchoolAdministrationToolsRequirementsGathering#Future_work
  • workflow to handle change-requests [ for this version, we can simply email requests to the responsible person ]
  • feed student data into the Grad Office database - either by filemaker 16 reading our postgres data, or our app hitting an API on the filemaker server to trigger updates
  • People data adding/editing: accreditation, grants, awards won
  • travel claim system
  • non-administrative and administrative access by other permission levels controlled by groups - big area for improvement; could possibly use "Grouper" software.

Constraints

  • These tools need to be at least as easy to use as what staff are currently doing

Assumptions and Risks

  • Assumption that we can identify all of the staff workflow and data needs- without leaving out seldom-used but critical requirements that we later discover.
  • Workflow and data needs are fairly stable and won't be invalidated by new rules and requirements shortly after deploying.
  • Discussions with people outside CS will allow us to non-ambiguously decide that either one of:
    • processes are fairly standard across campus and so it's worth it to design it to be potentially useful outside of CS; or else
    • processes are quite independent across campus so it's not worth trying to design for wider usefulness at this time.
  • A risk is that while scoping the project, we fall down a rabbit-hole of "this person does this, but that relies on having data from this other person, which relies on still another set of data, and what's the optimal way to get that data" through the entire term

Project Members

drallen (project manager), lfolland, ijmorland, jdatanasov

Project Stakeholders

CS Administrative Staff (including Grad Office), CSCF

Project Sponsor

Martin Karsten/Ken Salem

RT

See also

Implementation Plan

  • 2018-01 - 2018-04
    • 2018-03-01: Start working on web-UI using pre-existing schema v1 DONE
    • 2018-03-31: Have completed interviews with end-users DONE
    • 2018-04-10: Have completed schema v2 DONE
    • 2018-04-20: Have Demoed to selected end-users: Lawrence DONE, Greg, Diana
    • 2018-04-26: Plans for further development and deployment DONE
  • 2018-05 - 2018-08
    • 2018-05-31: Have roadmap for Spring 2018 DONE
    • 2018-08-30: Have go/no-go for further development DONE
  • 2018-09 - 2018-12
    • 2018-09-30: Have roadmap for Fall 2018 DONE
    • 2018-12-06: Have demoed to Lawrence DONE
    • 2018-12-14: Have go/no-go for further development DONE
  • 2019-01 - 2019-04

Meeting Notes

-- DanielAllen - 2018-01-16

Topic revision: r11 - 2019-03-25 - DanielAllen
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback