· Text/Graphic Artifact Recognition--An artifact itself should be allowable in either of these two types, or in combination

· Bi-directional Linking of Artifacts--An artifact should be traceable to related artifacts

· Distributed Usage--Multiple users can use the system from different

locations simultaneously

· Security--Each user should be authenticated and be associated with a logical set of privileges which can be modified by supervisory users with more privileges

· Application Integration--Components of the LCAM should integrate seamlessly (whether custom or off-the-shelf)

· Project Organization--Artifacts should be manageable at the project level, and multiple projects should be supported

· Cross-Project Artifact Management--Artifacts of a project should be reusable by other projects (shared)

· Revision Control--It should be possible to trace through the modification history of each artifact

· Attribute Definition--The LCAM should support meta-data for the artifacts and the projects

· User-defined Documents/Artifacts--Artifact types should be flexible

· Artifact Searching--It should be possible to find an artifact through keyword searching

· Life-cycle Support--The LCAM should be flexible in usage enough to support different life cycles

· Artifact Import--The LCAM should support creation of artifacts from existing document types

· Report Generation--The LCAM should support creation of hard-copies of summary information for a project

· On-Line Documentation and Help