|
Knowing that the
outcome will improve customer service and increase employee
productivity, corporations are now considering collaboration suites,
the most popular by IBM, MITRE, NASA JPL, Rockwell Collins and Sun
Microsystems. With
FaceBook functionality, users will welcome the technology tool,
which provides them with XML database-driven autonomic access to
content that can be restructured six ways to Sunday.
It is likely that
administrators of enterprise-wide, user-generated content will have
to monitor collaborative endeavours, ensuring that the collaboration
is work-related. More significantly, though, considerable attention
will be given to security, ensuring that sensitive data will not
leave the corporation.
It is interesting
that virtual collaboration and, ultimately, knowledge sharing work
toward the team players' dream corollary: tighter data security.
As employee collaboration increases, so does the need to be
mindful and precise about tracking strategies, processes and
business rules, and changes to management policies.
Inclusive
Documentation
The technical
writer elucidates requirements, evaluates business functional
requirements as described by technology user, analyses concepts into
details, and documents the requirements ensuring that stakeholders
know what they are getting, coupled with various software engineer
design documentation, coding, management, release and then
validation testing. Software development presents a lot of
paperwork.
It is
advantageous to consider using the inclusive information storage and
retrieval of Martin Documentation, which requires the inclusion of
every written word about the project into a framework that is
likened to a tree, and which is intended to supply diverse users
with what they specifically
need to know, including documentation for procedure development,
procedure change and error correction.
Putting
Down Roots
As we all well
know, the roots of a tree spread widely. In much the same way, the
roots of this documentation style contain procedures that can range
from a scribbled note on the back of a napkin to business and
functional requirements and vendor documentation - indeed, any written information about
the system.
Documents in the trunk comprehensively describe the
procedures: the higher up the tree you go, the less detail is given.
The trunk displays as an expanding outline, with varied levels of
documents stored electronically. Each document on the trunk may be
associated with subsidiary documentation, which can be represented
in a database as links to other information, including other
procedure documents.
Below
is an assortment of some of the documentation that can be found in
the Martin Documentation; the framework is likened to a tree.
BetaWatch
Inc. home of digital due diligence (tm) is led by
founder and senior consultant Temi Grafstein who works either as a
sole resource or with her team. Trained in the field of
documentation -- information science Temi collects, writes,
classifies, manipulates, stores, retrieves and disseminates
information by understanding problems from the perspective of
stakeholders, providing an array of services requiring the
ability to explain orally and in writing complex concepts in a clear
and understandable manner.
|
