|
In part 2, we will look at building out functional requirements that are aligned with business drivers and how to use those requirements to develop functional and technical specifications for your project.
Translating business requirements into a plan that can drive technology selection and guide developers in actually coding and configuring a CMS is one of the most challenging if not the most challenging aspect of a project. What, for example, will a concept like "content workflow approval process" mean in terms of the system? What details will a vendor need to demonstrate that capability, and what details will developers need to implement it? In many cases, an item like this is considered a "checkbox item." The vendor checks it off and claims to provide it. But saying you need this general class of capability versus making it useful and deployable are two entirely different things. During this process so much can be lost in translation that by the time the user sees the finished application, the capability can be unrecognizable or unusable.
Session attendees will learn the following:
- What "out-of-the-box" functionality can really mean
- How to decide whether a function needs to be demonstrated with your data or in a generic fashion
- Ways to score features and functions for vendor offerings
- How to ensure a business requirement is correctly translated into a technical specification
Live Seminar
Cost: $99
Replay
Cost: $69
When you register, your location becomes a Click U Live! site. The cost is per site [phone connection], not per person. You can host as many people as you like for one low site fee! So be sure to invite your colleagues to learn with you! Register before 22 April and save $10.00! Program registrations beyond that date will be $109.
Browser Test and System Requirements
Browser:
Test your browser and operating system by joining a WebEX test meeting.
|
User Links