Applications Development

This report outlines the secure development methods and integrity controls currently used by SAFECode members to deliver high-assurance systems to government and commercial customers.

Community source is designed to coordinate the work of different user IT organizations sharing the same purpose and requirements. An alternative to commercial applications and custom development, it gives users control and shares risk across peer organizations. Although several such public sector communities exist and yield great promises, many struggle with achieving critical mass and a viable business model. This panel will compare and contrast community source with more traditional software sourcing options and explore critical sustainability success factors.

Administrative systems should be affordable, flexible, and customizable. They should help end users plan for and achieve their goals, helping them complete tasks along the way. This presentation will show how the vision, principles, and design developed for Kuali Student can be applied to other next-generation administrative systems and outline some community source development opportunities.

Academia has adopted open source software for some online learning initiatives because it addresses persistent technical challenges

The open source learning management system has gradually reached maturity. In this session, we will share ideas and lessons learned about making open source LMS enterprise-ready. Currently SFSU has one of the largest Moodle installations in the United States and is the sole university hosting an anonymous Moodle CVS server.

Interested in moving beyond ERPs or your homegrown SIS? Come find out about a new approach, Kuali Student, built by and for the higher ed community. An extended Q&A will provide answers to your toughest technical, functional, and financial questions.

UW–Madison successfully managed a large IT project using a new collaborative development methodology. The goal was to bring the product to life quickly with fewer bugs and greater input from both functional and technical people. This methodology impacted our organization in unexpected ways. We'll share successes and lessons learned.

This session will outline how we used agile software development to build OSASC, a flexible web advising support system that helps 50 OSU academic advisors serve over 16,000 students each quarter. We faced a short implementation timeline (three months), lacked funding and a programmer, and needed to serve busy advisors. Agile methods enabled us to maximize resources when time and costs were fixed.

IAM and security must be on the same page regarding web application development to facilitate proper access. What coding practices and assessment practices should web developers use? What tools are out there to help (OWASP)? Do we need cross-site scripting and pup code review to ensure proper leveraging of enterprise IAM or should web applications manage their own IAM/account data? This session will discuss strategies for how to include security and access requirements in the development process and code.