1. MyIsern 2.0 Team Onyx

2. Group Process Team Blue Revisited –Familiar with work styles/schedules. –Focused on strengths and assigned tasks/issues accordingly. –Also brought in experiences from second groups. Scrums after class –Quick meetings to address issues.

3. Group Process, cont’d Sinclair Library Meetings –Hong & Sonny worked at Sinclair Met at Sinclair Library Mondays and Wednesdays (3:00pm – 7:00pm). –Worked on separate issues, but have someone to turn to when stuck with a problem. Agile Programming. –Used when designing the UI. –John & Marcius worked on it at home. Used Instant Messaging, phone to communicate with members.

4. Code Quality and Assurance Used Test Units learned from ICS 413 –Junit, Pmd, Emma, etc. Planning on using DBunit to test database.

5. Development Practices Agile Programming –Helpful with tasks that were unfamiliar or new. Issue Tracking –Enable to start tasks without having to excessively ask “What do I do now?”

6. Three Prime Directives Looked up different Open-Source Software Projects for good and bad examples of software that fulfill three prime directives. –Fulfilling PD’s starts with Project website. Include links to necessary pages, featured downloads, installation and developer guide.

7. 1 st Prime Directive The system successfully accomplishes a useful task. –Be able to successfully add, edit, and display Researcher, Collaboration, and Organization objects. –Can only be verified by end-user.

8. 2 nd Prime Directive An external user can successfully install and use the system. –Installation guide Include WAR file and tools needed to run file. Include easy to follow installation instructions. Include contact information if technical problems/bugs are found. In Wiki pages and downloadable distribution –Include pictures for steps if necessary. –Can only be verified by external installer.

9. 3 rd Prime Directive An external developer can successfully understand and enhance the system. –Developer’s guide Include software tools needed, IDE used. Include build instructions with expected results. Also important to list features/bugs that are known.

10. Problems Learning new software –Derby Mainly interaction between database and the application. –Startup guide helped a little. Time management –End of semester = Projects galore! Resulted in less FTF meetings, more online, phone communication. Mother Nature –Blackouts due to Winter Storm prevented online communication at key times.

11. Lessons Learned Prime Directives Revisited –Reason for building software is to help an organization, person, the world, etc in some way. Make sure target audience can easily install the application you are creating. Make sure that a developer who will possibly take over the project can easily understand what is happening.

12. Questions?