Business Objectives

Justifying XML project from different perspectives:

• Financial -- re-purposing
• Customers -- flexible apps, incr. satisfaction
• Internal business processes -- streamlining
• External bus. proc.
• Employees

Strategic alignment; support from senior mgt.

Training

tech. familiarity is essential for success. e.g. XSLT func. progr. paradigm

Define Requirements

• UML -- great tool/methodology for modelling XML applications. Use cases; act. diag.; collab & seq. diagrams
• Involve stakeholders
• What are the deliverables?
• What are the measures of success?

Model Data and Processes

• UML Class diagrams
• XML Schemas; map UML diags. to XML Schemas

Important to consider XSD as the schema language for content management, esp. if intending to deploy web services -- WSDL has XSD as it's type system. Namespace support and modularization are other benefits.

• Model relationships -- XLink; XPointer; Semantic Web; Ontology
• Accessibility
• Device Independence
• Industry Standards -- requirements have priority; map with XSLT; simplify: use subsets of industry schemas
• Avoid ambiguity and complexity

Convert Legacy Data

• Map between relational data and XML
• From flat files
• Up-translation
• Outsourcing

Create Content

• Editing interface -- expensive to customise, but often necessary. Special skills req. to customise the env.

Sometimes simple HTML form + scripting is enough. Or possibly XForms, or full editor. Encryption and signing may be important

Manage Content

- CMS -- chunking; check-in/out; workflow; storage; versioning; metadata; security

• Integration with ent. plat. -- e.g. J2EE, .NET
• Reuse and re-purpose content
• E-learning is good way to re-purpose. Shareable Courseware Object Reference Model (SCORM) -- XML vocab for creating learning content.

Look at vendor history for CMS, talk to customers, get references, look at financial strength.

Publish

- XSLT - XSL-FO - Online: HTML, WML, E-Book, Digital Talking Book

Publish and Invoke Web Services

• May need to plan to expose cont. manage. services as Web Services -- additional revenue? e.g. get most ROI on tools/functionality generated
• Aggregate Web Services to build cont. management functionalities -- cost efficiency, buy rather than build.

Example WS in CM

• Syndication (ICE)
• Data transformation -- between schemas; to PDF
• Language transformatin
• Distributed content authoring

Web Service lifecycle...