Florida Virtual School (FLVS)

1. Florida Virtual School (FLVS) Processes and Integration

2. Project Set-Up Phase • C&I will create a master Curriculum ticket with a list of all FLVS courses to be migrated for the specified school year. This is usually a discussion between Lorri McDaniels (Senior Director of Curriculum Production) and Pat Hoge (Senior Vice President of Curriculum & Instruction). • C&I will create a master MS&D ticket for each FLVS course that is being integrated. • Naming convention if tickets should follow:[Course folder name in SVN] – remove navigation, tabs, and validate HTML TortoiseSVN

3. Project Set-Up Phase • C&I ensures that all FLVS files are received, including: • Files are uploaded to the FTP server (Content/Develop) • Files are transferred over to SVN for C&I and MS&D purposes • C&I analyzes course and scopes changes that need to be made to course • Alternate versions are determined (st, ho, ss) • C&I provides course ID number and name to Application Management • Course creation requests will be submitted for each course shell • C&I will have a review period for prioritization/analysis • C&I/MS&D will make any necessary adjustments to the scope and estimates for given courses (each course will receive its own documented functional estimate)

4. FLVS (Third Party) Files Prepared Section • MS&D performs the following tasks: • Moving files to the extra drive (CID numbers and names need to be provided before this can occur) • Check files into the EMS • Provide External Document linking URL’s (which is attached to the Master MS&D IA ticket) • Validate HTML within course files • Other issues are addressed (e.g., removing FLVS specific navigation) • MS&D returns the ticket to C&I after the previous tasks are completed • C&I verified the changes and notifies MS&D of any additional or missed work that is required. Individual MS&D tickets are closed after verification.

5. Create Alignment Documents • Course shells are created in bulk at the beginning of the project or Course Creation Request Forms are submitted. • When ensuring files received are in proper order, the following subtasks are to be followed: • C&I creates versions (st, ho, ss) • C&I builds the units and lessons based on the FLVS Proof Shell • MS&D renames source folders to match CA structure:0000_0000_CourseName_ST/HO/SS_FLVS/CA • MS&D creates copies and checks files into the extra drive

6. External Document Linking/Modifying Content (Project Assistant) • EMS Integration Specialist will create an IA ticket and delegate course linking and course modifications • IA will contain the external document linking URL • The Specialist will provide any additional pertinent information that would be needed to complete this task • If a new textbook is provided for a specific course, this should always happen before content editing (and, align assessment content with the new textbook). This is most common in courses that are located on the CA side of the curriculum manager. • Once Project Assistant is complete linking the external documents and course modifications, they are then reviewed by the Project Associate. • EMS Integration Specialist conducts a final review of linking and course modifications.

7. External Document Linking/Modifying Content (Project Assistant) After Content Edits Before Content Edits

8. Assessment Creation (Project Assistant) • EMS Integration Specialist will assign out (by module/unit) assessments to be created in Connexus by the Project Assistant. These tasks will come via an IA ticket, which will contain all pertinent information that will be needed in order to create these assessments successfully. • The PA will use the FLVS Proof Shell to “copy and paste” (import) the assessments into the assessment manager within Connexus.

9. Assessment Creation (Project Assistant) Assessment Manager FLVS Proof Shell

10. Assessment Creation (Project Assistant) • Once assessments are created, PA’s will attach the assessment to the correct location within the course. • The PA will update the assessment IA ticket with all of the assessment ID’s that have been created for the specified module/unit. • The Project Associate will review all completed assessments: • Check to ensure that all question groups and questions were created appropriately and correctly • All correct answers are given the appropriate point value • Assessment metadata is set correctly • Assessments are attached to the correct location within the course • Project Associate will PDF all assessment answer keys by each semester, NOT by unit.

11. Editorial Process • The Senior Managing Editor will assign out the review of course content of FLVS courses on the CA side of the curriculum manager. • The Senior Managing Editor will assign out the review of (all) assessments. Assessments are submitted to editorial for review by course.

12. Course Metadata • EMS Integration Specialist will review and ensure the course metadata is set, which includes: • Building (status) • Course Year • Locations • Display Name • Course Directions & Tips • Grading Type • OLE • Grade Book weights • Grading scale

13. Course Metadata • Create metadata review ticket for each course and assign ticket to the Senior Manager of Curriculum Development to review the course metadata • FLVS Metadata completion (lesson days, etc.) • CA Metadata completion (weighting, lesson days, etc.). The review ticket should include the editorial content review spreadsheet.

14. QA (Quality Assurance) Process and Course Release • Once files and assessments have been integrated into the course shell, the course will need to be sent to the FLVS QA team before or during the Connections QA team (never should be sent after the Connections QA process). • C&I conducts a final click-through • MS&D fixes emerging functionality issues within the course (any outstanding issues will need to have a new MS&D IA ticket created) • QA test all officially supported internet platforms and browsers • Click-through edits implemented • QA verification • MS&D deploys files from CMS to Live • Once course Metadata has been verified by Curriculum Development, then the Course Release Checklist is submitted to Cate Darlington for final course release.

15. Review FLVS course on CA side of Curriculum Manager with Instruction Team • Once all of the CA courses have been approved for release, they should be reviewed with the Instruction Team. The course CID’s should be sent to the Instruction Team prior to any scheduled meetings.