Purpose
The purpose of this deliverable is to define detailed customer requirements in order to build up portal content. In detail, the deliverable might include:
·
Description of content requirements (business processes/functions,
Business Intelligence, Knowledge Management and collaborative scenarios)
·
Functional
specification and design of the portal applications built up from required
content
·
Technical
specification and design of the required content objects
·
Specification of the relevant data sources or
applications and their technical portal integration concept
·
Validation of the SAP Business Content offering
and specification of deficient areas
How should it be produced?
For clarification reasons
the roadmap structure includes for each of the listed topics separate outputs.
On the other hand it might be helpful to combine content requirements,
functional and technical specification of a distinct web application in one
output document.
It might also make sense, to
distinguish between pure content applications (build up from content, which is
extracted from any source system) and generic applications, which are more or
less part of the portal platform/framework (e.g. real time collaboration,
search…).
Further on this deliverable is produced primarily by content specification
workshops. They need to be scheduled according to in-scope content scenarios. A
good starting point for identifying the content requirements might be the
content program and strategy of the company. Another starting point might be
the company’s process organization and known “pain points”.
A
crucial “pain point” to be solved by a portal implementation might involve
processes that require single-user activities in several applications (cross-application
processes).
Another
typical “pain point” might be the requirement for a company-specific user
interface in certain areas.
It
might also be necessary to analyze existing processes in terms of identifying
“pain points” and inefficiencies.
The
workshops should include representatives from the business, or business process
owners.
After
identifying the portal-relevant content and the associated data sources and
applications, the portal integration concept should be discussed with the aim
of meeting user expectations. These workshops should include representatives
with the appropriate technical and development skills.
What if this is not done?
Without this detailed content specification, it is
impossible to:
· Conduct scope management
· Identify later change requests
· Have adequate budget controlling during the
project
· Block additional requirements during the
project timeline
Source of Input (Deliverable/Other) |
Input
|
Portal Content Program |
(All deliverable outputs) |
|
(All deliverable outputs) |
Project Charter |
Project Scope |
Outputs
Refer to the breakdown of the deliverable in the roadmap
structure.
The content requirements document is only one part of an
overall portal solution blueprint. It has to be completed by additional
platform oriented concepts (User Mangement /Security, User Interface, Technical
Design…).
A list of available iViews can be obtained at www.iviewstudio.com. Available iViews
can be listed according to different criteria, thus the iViews that could fit
to the project scope might be checked with the customer.