Determining Content Management System Requirements

1
Determining Content Management System Requirements
Bill RoseInstructional Designer, IST Solutions
Institute,Penn States School of Information
Sciences and Technologybrose_at_ist.psu.edu
October 11, 2004
2
Best Practices for Determining CMS Requirements
Goal
To raise your awareness of the importance of the
requirements definition process and equip you to
locate the knowledge and tools needed to carry
out your own requirements definition.
CMS Selection
Identifying the best possible match between a set
of needs and a system that meets those needs.
- Dont start by researching the features of
numerous systems
- Instead, conduct a proper requirements analysis
3
Best Practices for Determining CMS Requirements
Requirements Definition
Requirements are needs, as seen from the system
users perspective requirements deal with what a
system must do, not on how the system will do it.
Defining requirements means to surface,
understand, and document every required
capability for every user of the system.
The Process
1. Establish the business case get authorization
to proceed
2. Establish the requirements team
3. Analyze the organization deploying the CMS
4. Analyze the end-users working with the CMS
5. Analyze all the work flow processes carried
out in the CMS
6. Process research data gathered develop use
case diagrams, scenarios, and new work flow
diagrams
7. Determine all functional and non-functional
requirements
8. Document all requirements
CMS evaluation and selection begin
4
Best Practices for Determining CMS Requirements
Why spend precious time effort doing a needs
analysis?
- CMSs are complex
- CMSs are numerous
- Organizations are unique
- Organizations are complex
- Communication is critical yet often imprecise
- Process is anything but systematic
- Opinions are rifeWe should buy.
- Needs are expressed in isolationbut the
solution has to fit the organization as a whole
- Expressed needs can be too fuzzy to be useful
in CMS evaluation
5
Best Practices for Determining CMS Requirements
Do you want to risk failure?
- CMS Watchs 1 CMS pitfall Picking a content
management product before developing a business
case and solid requirements.
- The Standish Group, 1995 Of the 8 major
reasons software development projects fail, 5
relate to requirements errors these account for
just over 50 of software project failures.
- If you dont know what you want, the vendor
will be happy to determine it for you! -)
6
Best Practices for Determining CMS Requirements
Where do I begin? Begin with a reckoning
Time Six to nine months from starting needs
analysis to actually selecting a product 20-40
of overall development time if building your own.
Product range According to CMS Watch, more than
1,000 products purport to manage Web content.
Building CMS literacy Building up your
knowledge of capabilities, tech requirements,
product updates.
Risks Brainstorm and plan how you will handle
should they arise. Examples Total cost of
ownership higher than expected system not
flexible enough and must be adapted
Business case Vital! Plan to complete this as
your first step. Why is a CMS the answer to your
issues? What are those issues? What does the
organization lose by not addressing them? What
will it cost to address them with a CMS?
7
Best Practices for Determining CMS Requirements
1. Establish the business case get authorization
to proceed
- Business case establishes the need for the CMS
by addressing the following
- Opportunity
- Justification (ROI)
- Scope
- Constraints
- Functional areas and functional goals
8
Best Practices for Determining CMS Requirements
2. Establish the requirements team
- Very important to have a broad-based,
interdisciplinary team
- CMS Watch This is 2 of the top 5 mistakes in
making a CMS selection
- Web site technical team
- Web site content reps
- Other key functional area stakeholders
(marketing rep)
- Management
- Financial
9
Best Practices for Determining CMS Requirements
3. Analyze the organization deploying the CMS
- Identify all stakeholders anyone with a
vested interest in the CMS
- Who are they? Top management () immediate
supervisors, Web team, IT support, end users
within the organization, etc.
- Securing support from stakeholders at the
outset is critical keep their needs clearly in
view from start to finish
- Seek to disclose all relevant business issues
(mission, strategy, operations, tactics, critical
success factors)
10
Best Practices for Determining CMS Requirements
4. Analyze the end-users working with the CMS
- Identify user types and how each type
interacts with the system
- Consider the kind of interface (s) your users
will need
- Consider the kind of documentation and training
your users will need
- Do some users only require reports and other
informational output from the CMS (rather than
directly interacting with it)?
11
Best Practices for Determining CMS Requirements
5. Analyze all the work flow processes carried
out in the CMS
- Work flow (and therefore CMS interactions) may
differ from functional area to functional area
- Study each areaWhat is the sequence of tasks?
How does information flow?
- Can the processes be improved? Now is the time
to change them!
- Graphically depict the as is workflow
12
Best Practices for Determining CMS Requirements
6. Process research data gathered
- Perform Gap Analysisthe difference between
the as is and the desired
- Develop use case diagrams (or data flow
diagrams) and scenario descriptions
- Analyze everything you gathered to date stop
when you feel there are no open issues remaining
between you and documenting the requirements
13
Best Practices for Determining CMS Requirements
7. Determine all functional and non-functional
requirements
1. Functional requirements What the system must
do from the end-users perspective capabilities
that must be present and fully adequate
2. Non-functional requirements Technical, such
as system performance, but also constraints,
restrictions, other characteristics imposed on
the system
14
Best Practices for Determining CMS Requirements
8. Document all requirements

• Because requirements are specific and numerous,
  they must be written down, both for definition
  and for communication to stakeholders

- Consider using scenarios to document your
requirements

- For formal documentation, consider using
Concept of Operations (ConOps) as a guide
15
Best Practices for Determining CMS Requirements
What process tools should I use?
- Make use of the available requirements tools
and CMS feature checklists derive rather than
re-create
- Victorian Government Web Content Management
Requirements Definition Report is one example
- See the handout for additional similar
resources, both for the requirements elicitation
process and CMS selection
16
Best Practices for Determining CMS Requirements
Conclusion
- We havent even made it to CMS evaluation and
selection yet!
- As with any systematic process, dont be a
slave to it adapt it to your situation so you
can still benefit
- Goal To raise your awareness of the importance
of the requirements definition process and equip
you to locate the knowledge and tools needed to
carry out your own requirements definition.