1 / 14

CMS Project Mid-Term Update

CMS Project Mid-Term Update. Prepared by PolyU A pollo Presented on Nov. 19th, 2011. APOLLO Team Introduction. Today’s Agenda. APOLLO TEAM Introduction What’s CMS Benefits of CMS Project Objectives Project Progress Update Potential Risks Project Plan Overview What we have done

russell-cochran
Download Presentation

CMS Project Mid-Term Update

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. CMS Project Mid-Term Update Prepared by PolyUApollo Presented on Nov. 19th, 2011

  2. APOLLO Team Introduction

  3. Today’s Agenda • APOLLO TEAM Introduction • What’s CMS • Benefits of CMS • Project Objectives • Project Progress Update • Potential Risks • Project Plan Overview • What we have done • System UI Design Overview • Further Actions

  4. What is a CMS? • A Content Management System (CMS) is a browser-based tool to build and manage web content. • Content is separated from code, allowing non-technical editors to focus on content.

  5. Benefits of Using the CMS • Reduced effort to build/maintain a site • Non-technical users are able to edit web pages • No knowledge of HTML is necessary • Global image library available • WYSIWYG editor, similar to Word • Historical audit-trail of changes • Link tracking helps reduce broken links • Content is searchable • Approval Workflow is possible (with email notifications) • Easily input metadata for SEO • Ability to schedule content to post / archive

  6. Project Objectives • User Friendly -- Devolve content creation throughout the institution regardless of contributors’ skills • Simplicity-- Enable the creation, management, and usage of standardised metadata • Security -- Provide security, governance and approval processes over content published on the web • Mobility -- Mobile devices accessible • Continue Improvement -- Continue to support a diverse array of existing technology platforms

  7. Potential Risks • Tight Schedule • Busy Team(part-time) • Less experience on UI design

  8. Project Plan Overview

  9. What we have done? • Project Plan completed and submitted on time • System Requirement Specification document completed and submitted on time • Bi-weekly meeting progress review and update to Dr. Hareton • System Design document 90% completed • SQA plan completed 80% • Development Model: Waterfall, Iteration, Agile • Necessary Tools finalized: • SVN on Sourceforge • Configuration Management on Sourceforge • Visual Paradigm • Microsoft Project 2010 • Microsoft Visio • Mockup • Lumzy • Eclipse • PHP • MySQL • Apache

  10. System UI Desgin Overview

  11. System UI Design Overview(Continued)

  12. Further Actions • Complete System Design and SQA • Coding • Testing • QA • Clouding Computing • Final Presentation

  13. Question?

  14. Thank you !!!

More Related