1. K-12 Teaching Application Support and Software Ongo-08 Client Dr. John Lamont Prof. Ralph Patterson Advisor Dr. Gregory Smith Team Members Sean Boyle Tony Brimeyer Justin Brown Paul Hartwell Duc Ho Amy Joines Nate Taucher Adam Wise

2. Introduction Problem Statement Concept Sketch Similar Products

3. Problem Statement Need Improve student performance in problem solving and geography on nationally standardized tests Proposed Solution Design Internet-based software applications to be used as a supplement to class work in mathematical problem solving and US and world geography

4. Concept Sketch

5. Similar Products Math Munchers Deluxe  Only for Math  Does not report back to Teacher  $29.99 on Amazon Where in the World is Carmen Sandiego  Does not report back to Teacher  $5-10 on Amazon

6. System Overview System Diagram Operating Environment Application Overviews

7. System Diagram

8. Operating Environment

9. Mathematical Teaching and Support Software

10. Globey’s World

11. Uncle Sam’s America

12. Framework A template used to give support and software settings to the whole system Set up the frames, navigation menus, and problem functionality for the software Coded modules that are used for the whole system Maintained by the Framework team

13. Goals Initial Semester Status Quality Goals Gradebook Goals Documentation Goals

14. Initial Semester Status Large number of defects existed in the application User interface inconsistencies No implemented student monitoring tools for teachers Lack of current documentation

15. Quality Goals Evaluate current state of application Minimize software defects Increase usability for intended users Code cleanup

16. Gradebook Goals Allow creation of assignments Tracking assignment results Graphical display of class performance Maintenance of data by teacher

17. Documentation Goals Help future developers understand the application  Capture all requirements  Capture design details of entire application Set a standard for documentation throughout the entire application

18. Semester Planning General Semester Planning Application Diagrams Semester Schedule Risks & Risk Management

19. General Semester Planning Broke entire system into 4 main components Listed the features of each component  Determined current state  Estimated hours required to complete unfinished or new features  Prioritized features Developed semester schedule

20. MTSS Diagram

21. USA Diagram

22. Framework Diagram

23. Semester Schedule

24. Risks & Risk Management Fixing quality issues while coding new features Fixing defect breaks another feature Under-estimating time and resources required for an activity

25. Quality Software Quality Methods for Improvement Quality Upgrade Results

26. Software Quality Upgrading the software quality was the primary task for this semester State at beginning of semester:  No thorough evaluation completed  60 unresolved defects  Issues with IE 7 functionality  Inconsistent appearance and functionality  Lack of code commenting  202,000+ lines of code

27. Methods for Improvement Evaluation UI Upgrade Code Cleanup Defect Fixing

28. Key method of improvement is defect fixing

29. Quality Upgrade Results (1/4) Total Number of Defects Reported

30. Quality Upgrade Results (2/4) Number of Unresolved Defects

31. Quality Upgrade Results (3/4) Code status  165,000 lines of code  Captured all functionality  Pre and Post conditions commented UI  Improved menu layout  Updated color scheme  Consistent page design

32. Quality Upgrade Results (4/4) Before After

33. Gradebook Need Statement Solution Design Method Design Testing Results

34. Need Statement Process needed for teachers to track student interaction with applications Method needed to evaluate student progress with classroom related material Create assignments from problem sets for classroom grading

35. Solution Gradebook application  Create assignments  Store student results Based on student performance teacher can modify teaching method

36. Design Method Gather specific requirements from client Create database schema based on requirements and entity relationships. Define pages to handle requirements Create page flow diagram Create incremental prototypes Evaluate and merge prototypes Test prototypes against requirements

37. Database Design

38. Design: ViewSectionResults.php Definition: displays assignment results for each member of the class section Responsibilities:  Viewable only by teacher or school admin.  Students displayed in left column  Assignment names displayed in top row  Student score displayed as cell in table  Display a histogram of the grades of the class section Interactions:  ViewAssignmentStatistics.php  ViewStudentAssignResults.php

39. Design: Page Flow Diagram

40. Testing Unit  Page Testing System Integration  Interaction Testing Verification Testing  Requirements Testing Results  44 defects opened  44 defects fixed

41. Final Gradebook Product

42. Conclusion Lessons Learned Actual Semester Resources Earned Value Analysis Final Status Acknowledgements

43. Lessons Learned Development methods  Incremental Prototyping Development  Pros/cons of prototyping Scheduling difficulties  Factor in unforeseen events  Planning and design are of equal importance as coding Large code base without documentation leads to wasted resources

44. Actual Semester Resources

45. Earned Value Analysis

46. Earned Value Analysis Totals

47. MTSS Final Status

48. Globey’s World Final Status

49. USA Final Status

50. Framework Final Status

51. Final Status Final project release: Dec. 5 Quality improved through evaluation and testing Documentation was created for future development

52. Acknowledgements Diana Gualillo  User Interface Consultant Kyle Banwart  Design Consultant Dr. Smith  Project and Course Advisor Dr. Lamont and Prof. Patterson  Clients

53. Demonstrations General Gradebook Defect Tracking Tool

54. Questions ?