Post Secondary Electronic Standards Council - Common Data Exchange Standards
Description:
Any provider using the Common Data Services Standards (CDS) and registered in the service network could communicate directly with the appropriate exchange host for a targeted institution. The services would be 'payload agnostic' and while the immediate interest is for transcript exchange, the network could be used for the exchange of other existing or future PESC standard transactions.
As the technological landscape has evolved significantly over the years, web services standards are now available to enable automated directory lookup and efficient machine-to-machine communication in a highly secure transmission environment. The PESC CDS Task Force looks to maximize the use of this new technology to meet the emerging needs of schools, institutions, states and other service provider organizations to exchange student records, accounts and educational data.
The mission of the PESC CDS taskforce is to improve security, reliability, efficiency and speed in the transfer of all educational data types by developing an open web services network and associated standards to benefit the education of students, streamline processes for institutions, and facilitate the advancement of services offered for education. Please refer to http://www.pesc.org for more information on PESC.
Technical Requirements:
• Language – Java
• Framework – Apache CXF web services; Spring
• Deployment target – Tomcat
• Configuration of services – Spring
• Security – Spring
• Persistence layer – DataNucleus or Hibernate
• Database schema changes - Liquibase
• Build system – Maven
• Database – MySQL
• Development Environment
o Eclipse (free) - preference or
o IntellinJ (free – community edition or commercial version)
• Source Control
o GitHub (are components free?)
• Issue Tracking
• Wiki
• Documentation - Wiki
• Development Methodology
o Specifications for initial release – as per defined on project site
o Code review (less important on initial efforts – depends on size of development team and allocation of member’s time)
o Bi-weekly review for development progress during regular scheduled CDS meetings