SSWG Work Plan for 2011

DRAFT - SSWG Work Plan for 2011 - DRAFT

The following are potential items for the SSWG's 2011 work plan.  This document will evolve as the work plan is finalized.

High Priority

  • What are the issues of sharing and reuse at UC Davis? [Recast as Framework for Efficient IT Application Development?] Identify the issues UC Davis must address to create an environment that facilitates the sharing and reuse of software. It is expected that an outcome of this effort will be additional action items for the SSWG and other groups involved with IT governance at UCD.  Examples of such issues include:
    • Vision statement
    • Inventory of applications available / needed
    • Common look and feel
    • Funding / organizational
    • Business processes not common
    • Campus-level technology services (IAM, Rice, Data Warehouse)
    • Knowledgeable technical staff and training
    • Transition strategies
  • Finalize Repository and Process for SSWG Standards and Guidelines. Develop a repository for recommendations, standards, and other information produced by the SSWG. Also develop processes for maintaining the information in that repository, including a collaborative process for vetting the documents and a periodic review process.   A key aspect of this process will be to ensure wide dissemination of the vetted statements, as well as broad consultation in the vetting process itself.
  • Guidelines for the Use of Source Code Repositories. [Recast as Software Management?]  Now that some developers are starting to use external repositories like GitHub, we should establish guidelines for their use to ensure appropriate security and protection of University intellectual property.
  • Define standard configurations for recommended application platforms. Develop recommended configurations and support infrastructure for the recommended platforms listed in Preliminary Recommendations for Application Platforms to Foster Interoperability, Sharing, and Reuse.

Medium Priority

  • Guidelines for the Development of Secure Software.
  • Standards for interfacing with campus core services. Work with development teams to create interface standards for core campus services like identity management, work flow, service bus, enterprise data, etc. Since some of these standards are still evolving, this work will also recommend timelines for adoption of these standards.  In 2010, the SSWG will work with the Identity and Access Management (IAM) project to establish its interface standards.  Interface standards for Kuali Rice and the Data Warehouse will addressed, although they may not be complete in 2010.
  • Other Items Considered for 2010 But Not Included in the Work Plan

Ongoing

  • Develop Standards and Guidelines As Required by UC Davis.  As needs are identified, the SSWG will develop standards, guidelines, etc. to address them.  Examples might include usability, development methodology, and interface standards for applications.