Procedural Component
A
procedural component is an implementation work
product consisting of a cohesive collection of procedural that
is part of the
system application, contact center, or procedural
center.
The typical objectives of a procedural component are to:
Provide basic procedural stored and minipulated by the
application.
Provide content for user interface and websites to
display to users.
The typical benefits of procedural components vary depending
on the application:
Procedural components enable applications to
execute.
Procedural components enable user interfaces to present
content to users.
The typical contents of procedural components include:
Text
Numbers
Images (static and animated)
Audio files
Video
Hyperlinks
The typical stakeholders of a procedural component
include:
Producers:
Evaluators:
Approvers:
Maintainers:
Users:
A procedural component typically can be started if the
following preconditions hold:
The
initiation phase is started.
The system requirements specification (especially the
procedural requirements section) is started.
Work Products:
Stakeholders:
Procedural components can be obtained from legacy
proceduralbases.
Do not just concentrate on the software and hardware
components.
Use content management.
A procedural component is typically constrained by the
following conventions:
Content (published procedural)
Internal procedural that is not visible to the user.
