1 / 26

Project Elements

Project Elements. Web content management system Document database Site Refresh. Content Management. Buy vs. Build? Off-the-shelf options are available Cautions Existing functionality may drive business adaptation Limited flexibility to accommodate changing needs Integration issues

claire-pittman
Download Presentation

Project Elements

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. Project Elements • Web content management system • Document database • Site Refresh

  2. Content Management • Buy vs. Build? • Off-the-shelf options are available • Cautions • Existing functionality may drive business adaptation • Limited flexibility to accommodate changing needs • Integration issues • Enterprise architecture requirements • Custom solution may be better

  3. Content Management • Enterprise Architecture Perspective • Relationship to other software systems and business processes • Specifically • Document database • Content development workflow • Future web site functionality

  4. Content Management • EVI’s Proposal for CMS • Conduct business needs analysis first • Consider enterprise architecture requirements • Build (or buy) optimally cost-effective solution

  5. Content Management • Business Needs Analysis Process • Interviews with key stakeholders • Business Requirements Document • Review, revision, and sign-off • Translate BRD to functional requirements • Use functional requirements to design the best solution

  6. Document Database • Our Vision • All common information maintained in a single location • Component-based architecture facilitates delivery through multiple channels • Web site • Formatted text for print documents • Dynamically generated PDF files • Export to other web sites and systems

  7. Document Database Print Export Module Component Architecture for Document Repository System PDF Export Module • Document • Repository • Database • Workflow • User Interface Web Site Other Export Module (XML)

  8. Document Database • Component-based Architecture • Logic at each level is self-contained and unaware of how other components function • Each component knows only how to send a request and interpret a response, or receive a request and produce a response • Any component or system that can speak their language can interact with these components

  9. Document Database • Component-based Architecture • Other benefits • More efficient • More flexible • More scaleable

  10. Document Database • Emphasis on Needs Analysis • Build system to accommodate future use • Enable move to future functionality sooner • Revising later likely to be much more expensive

  11. Document Database • Our Vision vs. Your Vision • Somewhat more than requested in the RFP • We think this is the best approach • Opportunity now • Consistent with enterprise view • Can be done within budget

  12. Site Refresh

  13. Site Refresh • External Relations vs. Software Development • Content management system and document database are software systems • Site refresh crosses over to marketing/ external relations: how to deliver content in a way that influences customer beliefs and behavior

  14. Site Refresh • Council ISP’s Goals: • Improve customer workflow • Increase “stickiness” • Boost traffic • Position programs (adventurous and fun yet academically serious) • Reduce volume of information requests

  15. Site Refresh • Requires awareness of customer • What is customer trying to accomplish? • What attracts/keeps customer to the site? • What is customer’s perception of programs and of Council? • What information does customer need, and how should it be delivered?

  16. Site Refresh • Qualitative Customer Research • If we talk to customers the wrong way, they may not respond • Qualitative research gives us information we need to communicate the right way • Helps us understand the functional, behavioral, and emotional drivers that influence the customer

  17. Site Refresh • Insight and Understanding • How do you look for a study abroad program? By location, or field of study, or something else? • What are the strengths and weaknesses of our competitors’ web sites? • Why do you want to study abroad? • What kinds of information do you need most?

  18. Site Refresh • Insight and Understanding • Once you have the information you need, what do you expect to be able to do from our web site? • What does study abroad mean to you? • What do you hope to learn about yourself through study abroad? What kind of person do you think study abroad will make you?

  19. Site Refresh • Insight and Understanding • This kind of information immensely valuable for crafting presentation • Not that difficult (or expensive) to get

  20. Site Refresh • Qualitative Customer Research: Preliminary Plan • Online surveys • On Council ISP site • Solicit via email broadcast • Recruit through members, information inquiries, etc. • Online focus groups (if needed) • Limited traditional focus groups (if needed) • Test resulting ideas and designs

  21. Review • Content Management System • Determine business needs first, then design best system • Document Database • Plan now for future functionality • Site Refresh • Based on qualitative customer research

  22. Why EVI? • Knowledge of travel business, student market, and Council ISP • Proven track record • Breadth of resources • Service and commitment

More Related