Code Walkers

1. Code Walkers Final Presentation Report Ethan Bowyer Andrew Doyle Chad Sloan Stephanie Shaver

2. Team Members

3. Project Overview/Scope Project Overview: We will develop a content management system for the Sports Club Council that can be accessed via the World Wide Web. Project Scope: Our client had asked us to recreate the Sports Club Council’s website with a better feel and more functionality. The updates to the site include: - Login for each club - Interactive Calendar that displays events - The ability for users to submit articles and posts - Photo Gallery which has been organized by club then date - List of all clubs included in the Sports Club Council (including officer information of officers that make up Sports Club Council) as well as links to the individual sports clubs - Links to various forms used by the Sports Club Council (Such as Sports Club Handbook and Fundraiser form)

4. Software Development Process: Planning The first step in any software process is the Planning Phase. During the Planning Phase our team: - Met with our client, Mr. Ridpath - Asked what Mr. Ridpath wanted from the new website - Looked at all the possible complications that could occur during the process - Identified all the resources of our particular project - Identified all the risks involved with our project and solutions to fix them or make sure they do not happen - Figured out what we would be able to accomplish in Joomla! - Researched various possible plug-ins for Joomla! - Wrote out a schedule of how we would complete various parts of the content management system

5. Software Development Process: Requirements Once we were finished with the Planning Phase we moved into the Requirements Phase. In the Requirements phase, the CodeWalkers: - Wrote out all of the requirements of the project along with their importance, risk factors, and other requirements each depend on. - Checked different scenarios that would be the best and worst for the site - Drew out models of how the content management system will work with internal and external components - Updated schedule to how much had been accomplished by this time

6. Software Development Process: Design After the Requirements phase is the Design Phase. In this phase we: - Mapped out what each requirements functionality would do and how it would appear on the site - Took screenshots of in-progress content management system - Described conceptual view of the system through an architectural context model as well as a process model - Updated schedule based on what had been completed and what still needed to be completed

7. Project Challenges and Lessons Learned User’s Requirements: - Calendar that shows different club events - News Posts on main page - Articles - More Organized Photo Gallery - Follows Radford Color Scheme Challenges: - Using new Joomla! 1.6 without any previous experience - Learning how to implement and work with Joomla! and Joomla! plugins - Team member could have been sick or unable to make a meeting. - Making sure everything the client requested was possible in the time provided. Lessons Learned: - Use and operate Joomla! 1.5 - Properly document steps of software engineering process - Manage different stages of the software engineering process

8. Project Demo • We will be demonstrating: • CLUB USER FUNCTIONALITY : • Editing a Calendar Event • Adding a Post • Uploading a photo

9. Conclusion Possible Enhancements: - Article Sections and Photo Gallery must be updated for every club added or deleted (may be possible to make automated) - Updates for components - Being able to upload videos - Having cycling current news photos, that will display recently added pictures

10. Questions