1. A Novel Idea in Application Development Ask the Users What They Want Michael Nola Copyright Mike Nola, 2003. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.

2. Previous/current development projects of AIS How projects were done in past, why CSM was different AIS talked to user, took their best guess Submitted “completed” project for testing Went back to the drawing board to correct problems……or user lived with problems

3. The Value Of Prototyping From A Programming Perspective Reservation screen (prototype) http://www.isd.fsu.edu/users/csm/phasei/sectionReservations.html Personnel screen (prototype) http://www.isd.fsu.edu/users/csm/phasei/sectionPersonnel.html What we envisioned vs where we are now Technical considerations, throw away work as a waste of time, scripted walk through Important: Have management buy in UP Front so they give ample time for development

4. The Value Of Prototyping From A Programming Perspective (Continued) What it bought the programmers: familiarized programmers with business process and needs Reality of user needs Identified fields needed, shaped design issues about how much information or scrolling, to allow on screen, start developing workflow process

5. Other Users That We Involved Cashiering, Personnel, Space Management, Registration, Board Reporting etc., etc…… We coerced the users of these systems as to the changes that needed to be made Had to identify the changes that had to be made to these systems, got buy-in for changes to these systems Business rule clarification was covered when working with other systems and processes (reporting, space, contact hour calc)

6. Coding Considerations As objects are completed they are tested internally then given to core user group for testing, client is involved in developing testing 2-3 key end users identified and involved in development testing (change from previous projects) Coding is JAVA object-oriented/modular Allowed users to test in tandem with development Reusable code-considerations for long term use add length of time but saves time elsewhere

7. Where are we now in development We have completed about 85% to 90 % We have coded 283 Java classes 40.jsp files (HTML pages) 80 XML files 10 other files (javascript, properties files etc., etc) We have 18 images associated with this system

8. System Issues With Implementation Overlap of existing system with new system Backload data from new to old; old to new (covering risks) My opinion of the design methodology we are using

9. The New Course Schedule Master System Demo of new CSM System https://staging.ais.fsu.edu/servlet/login

10. Q & A Kimberly Barber Associate Registrar/ Client Lead Florida State University 850-644-6127 Kbarber1@admin.fsu.edu Mike Nola Coordinator, Computer Applications/Project Lead Florida State University Phone 850-644-4513 mnola@admin.fsu.edu