1 / 15

V.1.0 061112

Certification and Professional Education Cloud Computing Course Series Development Structure and Status Dennis Frailey , Ph.D., Dorian McClenahan , Ed.D . V.1.0 061112. Overview – Program Development Structure and Processes.

morrison
Download Presentation

V.1.0 061112

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. Certification and Professional EducationCloud Computing Course SeriesDevelopment Structure and StatusDennis Frailey, Ph.D., Dorian McClenahan, Ed.D. V.1.0 061112

  2. Overview – Program Development Structure and Processes • The IEEE Computer Society Education Activities Board – Professional Development Committee has developed a comprehensive product development infrastructure. • From SME recruitment and vetting – through product deployment and evolution Author and Reviewer Recruitment Core SME team Recruiting Topic generation Topic review and validation Course maintenance and evolution Course build and review V.1.0 061112

  3. SME recruitment SME recruitment: Three ways a SME can join a development team: 1. The CS Education Product Developer (EPD) approaches a SME to recruit directly 2. SME contacts Professional Development Committee Chair, member or the EPD and expresses an interest 3. OR – the PDC ( see legend) and/or STC approaches a SME to gauge interest and recruit. Processes for each of the above are depicted in the swim-lane chart to the right. V.1.0 061112

  4. SME Vetting Vetting process 1. The CS EPD sends a SME Interest form – the prospective SME completes and returns 2. The EPD checks for basic qualifications and prepares a dossier: a. Advanced degree b. Teaching and course build experience c. Relevant industry experience d. Relevant publications 3. EPD forwards dossier to Professional Development Committee Chair (PDC) for review. 4. If accepted, dossier is forwarded to Subject Team Chair (STC) for review. If accepted, SME is assigned to a project and given specific duties. 4. EPD prepares all SME paperwork. V.1.0 061112

  5. SME Profiles and Assignment Matrix For each vetted SME that joins a Subject Team, the EPD enters all SME data, such as contact information, qualifications, assignments and history with the Volunteer Database. SME assignments are tracked via the SME Assignment Matrix, which assigns the SME to a Subject Team, and tracks their intended tasks. There is a SME Assignment Matrix for each of the CS C & PE product types. V.1.0 061112

  6. SME Dossier EPD also keeps a Dossier file that includes a CV; CS History Tracker, biography and the SME Interest Form V.1.0 061112

  7. Professional Development Committee Structure and SME Charter The CS SME Corps is governed by a SME Charter, which outlines the structure of the EAB Professional Development Committee. Below is a graphic outlining the PD Committee structure. Note that there is a Subject Matter Chair for each major subject area, such as Cloud Computing, Self Assessment, and Specialty courseware. • Each Subject Matter Chair has specific responsibilities identified in the SME Charter. These include, but are not limited to: • Maintain oversight of the product line • Product a White Paper for each new product (see following slide for an example) • Establish and maintain a core reference list • Establish a three-year plan for each product line in that subject category • Identify, select and evaluate course authors and reviewers • ……and a host of detailed second-level duties V.1.0 061112

  8. Professional Development – White Paper Example Each new product line is defined by means of a White Paper, developed as one of the first documents in a new initiative. This White Paper will include: 1. Introduction to the subject 2. Rationale 3. Overall approach to the subject 4. Curricular model 5. Project deliverables 6. Timeline 7. Any additional details specific to a particular initiative V.1.0 061112

  9. Topic Generation, Analysis and Vetting A process is required to determine if that idea is first – marketable, and second – course worthy. Idea Harvest, Marketability analysis Course-worthy? The Marketing Analysis is performed first – if the proposed course idea is not marketable, no further action is deemed necessary. V.1.0 061112

  10. Course Author and Reviewer Guidelines With SMEs recruited and vetted, and with a topic reviewed, analyzed and approved, the next step is to issue to the intended course author format and course build guidelines. These Guideline documents have been built for each type of educational products, including the following: • Assessment courseware • Specialty courseware • Essential Sets • Knowledge Area Focus V.1.0 061112

  11. Course Build Building the Course Once vetted, course topic ideas are moved to the build process where they become organized learning experiences. This is a complex process, and is reproduced on this and the following 2 slides. V.1.0 061112

  12. Course Build (continued) V.1.0 061112

  13. Course Build (continued) The entire model – called the Topic Evolution Life-Cycle, looks like this: Taken as a whole,the process swim-lane model looks like this………………. Legend Marketability Course worthiness Course build, review and deployment V.1.0 061112

  14. Cloud Computing Project Status • Three of the five courses are currently under development. • The remainder will commence course builds by late summer • All five courses on line by 2Q 2013 V.1.0 061112

  15. Cloud Computing Project Status (continued) • IEEE/CS Courses • Cloud Overview Webinar • Cloud in the Business Environment • Cloud Economics, Metrics and Migration • Cloud Governance • Security issues in Cloud • IEEE Metro Area Workshops • The Cloud in the Business Environment - a Manager's Overview • Security Issues in the Cloud • Normalized Timeline for 2012 • 11 May – review of deliverables outline – SME team and Dorian • 15 May – Identify articles for Cloud Computing Essential Set – review by SME team and Dorian • 21 May – Identify Cloud Computing Glossary – review by SME team and Dorian • 7June – 1st Draft of PowerPoint Slides ready for Presentation – review by SME team and Dorian • 11 June – Face-to-Face review in Seattle • 26 June - All comments on 1st Draft review by SME team and Dorian to Shafer • 13 July – Final Draft of PowerPoint Slides ready for Presentation – review by SME team and Dorian • 30 July - All comments on Final Draft review by SME team and Dorian to Shafer • 13 August – Final Version of PowerPoint presentation with speakers notes complete – to Dorian • 20 August – Draft of The Cloud in the Business Environment - a Manager's Overview Practical Applications Workbook – review by SME team and Dorian • 31 August - All comments on workbook Draft review by SME team and Dorian to Shafer • 14 September – Final version of workbook complete – to Dorian V.1.0 061112

More Related