Specifications include, but are not limited to: A. Provide varied and robust software capabilities within one comprehensive system.
B. Provide administrative permissions such as adding course prefixes, changing workflows,
adjusting the general design of pages within the system, moving proposals to different levels
within the workflow, etc.
C. Provide comprehensive permission control functions such as flexibility in assigning
responsibilities at each workflow level.
D. Provide control over submission requirements.
E. Include workflow support of curriculum-related items such as course grade changes,
substitution waivers, and course scheduling approvals.
F. Include a repository for forms relevant to the curriculum process.
G. Include email generation from within the system.