1 / 45

StudentInformation

StudentInformation. Steve Reeling. Agenda. Project Update and Roadmap Discipline Module Redesign Update SIS 2014 Contacts Medical Module Redesign Release Cycles/Feature Releases Hosting Project Update Cornucopia/VendorLink Update. Discipline Module. Why a new module? Limited usage

shepry
Télécharger la présentation

StudentInformation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. StudentInformation Steve Reeling

  2. Agenda • Project Update and Roadmap • Discipline Module Redesign Update • SIS 2014 • Contacts • Medical Module Redesign • Release Cycles/Feature Releases • Hosting Project Update • Cornucopia/VendorLink Update

  3. Discipline Module • Why a new module? • Limited usage • Challenging workflow • Use of third party tools • Mostly used for EMIS reporting • Missing some elements • Difficult to enter data • Pending reporting requirement changes

  4. Discipline Module • What does it do? • What it does now, Plus… • Create Referrals (new incident) from Gradebook • More info about incident • Classification • Victims • Witnesses • Contact with parents • Better usability • Easy data entry – single page • Parallel rollout with SIS

  5. Discipline Phases • Phase 1 Goal(s) • Get/keep necessary Reporting Data • Create an efficient and effective Discipline system vs. a state reporting tool. • Add additional data elements; victims, witnesses, injury… • Update Design – Student Profile, Masthead (top of page), Navigation, simpler data entry… • Phase 2 Goal(s) – Based upon user feedback • Drive Efficiencies and Time Savings through Workflow Management • Extend Discipline capabilities into other areas (Teacher, Penalty Tracking, Reporting/Analysis…)

  6. Teacher Clicks an Icon next to Student

  7. So What's the Plan? • Development Phase 1 ends Q1 2014 • End User Testing start of Q1 2014 • Training with ITC/End User start of Q2 2014 • Launch into production end of Q2 2014

  8. End User Sessions • Held at ITC – late January, February, March • Several have volunteered already • District Staff Required – No Staff, No Input. • Asst. Principle, Admin, Teacher, Attendance Clerk • Districts Data – SI and GB Databases Required • Restored to training site before session • Fresh within 2 days • Classroom Setting • Structured - User Cases to run through for each role • Unstructured – What else do they do with Discipline. • Its as if they were doing their job • Why – no risk to production data, time to adjust, no hotfix nightmare, can interact with real users, low risk- high reward.

  9. Introduction StudentInformation 2014

  10. Application Toolbars • Main Toolbar(Product Identification, Suite & Product Navigation, District/School Selection, User Options, Settings & Help) • Breadcrumb Bar(Breadcrumbs, Student Search, Go To Navigation) • Favorites Bar

  11. StudentInformation • Special SIS Challenges: • 5+ Level Navigation • Go To Navigation • Student Context

  12. StudentInformation Sample

  13. Suite Navigation

  14. Product Navigation – Go To

  15. Product Navigation – Favorites Bar

  16. Product Navigation – Top Level Menu

  17. Product Navigation – Level 2

  18. Product Navigation – Level 3

  19. School & Year

  20. Change Working School

  21. Student Search

  22. Student Context & Paging

  23. Student Information

  24. Student Paging

  25. User Preferences & Information

  26. Additional Options

  27. Medical Module Redesign • Start Research in Q1 2014 • Design Concepts start Q2 2014 • End User Testing start of Q1 2015 • Training with ITC/End User start of Q2 2015 • Launch into production end of Q2 2015

  28. Release Cycle/Feature Releases • Major feature changes – high risk of being disruptive • Towards end of school year, beginning of summer • Beta phase in non-production environment • Minor feature changes – low/no risk of being disruptive • Minimal changes during school year that require training of end users • Focused on EMIS required changes and showstopper defects

  29. Hosting Project Update • Goals • Minimize risk to user base • Reduce the variance in the skill set of hosting providers • Singular, managed and controllable ecosystem • Eliminate openness of access to code and data changes • Solid backup processes • Solid disaster recovery processes • Monitor, measure and analyze system usage patterns

  30. Overview – Current State • Many Browser Standards • Many Server Options Configuration • Many Environmental Factors; Firewalls, Network, Active Directory, Feature Usage… • Near Infinite Testing Scenarios FireFox Chrome Safari IE 8, 9, 10 ProgressBook Suite • Main Browsers - MEC • IE 10 • Safari 6 • Chrome 29 • IE 8 • Chrome 30 • Main Browsers - OHIO • IE 10 • IE 8 • IE 9 • Chrome 29 • Chrome 30 Windows OS 2008R2 Windows OS 2012 SQL Server 2008R2 SQL Server 2012

  31. Overview – Future State • Many Browser Standards • Reduced Environmental Factors; Firewalls, Network, Active Directory, Feature Usage… • Managed Hosting Environment Option FireFox Chrome Safari IE 8, 9, 10, 11 X ProgressBook Suite • Sunset IE 8 Support in April • Include Beta Support of IE 11 in 14.2 • Best effort support for Chrome, Firefox updates – random and frequent Windows OS 2008R2 Windows OS 2012 SQL Server 2008R2 SQL Server 2012 X X • Defined Server Configuration • Singular OS, SQL and IIS setting • Date TBD, Most Likely end of School year

  32. Cornucopia/VendorLink Update

  33. Q&A

  34. Student Profile Page

  35. Student Roster Detail

More Related