A requirement is a management tool. Ideally, before analysis begins, a list of requirements is published, naming all the things that the system under analysis is supposed to do when it is finished. As a result, the requirements list can become a check list to see if the analysis has met all stated goals.

System Architect provides Requirements as definition types. Both of these definitions present a suggested property set (that is, for a Requirement, you may enter Source Document, Author, and so on). Users generally have their own particular properties they need to capture.

System Architect gives you the ability to create new definition types, and modify the properties of existing definition types, with its customizable metamodel and USRPROPS.TXT.

A full explanation of USRPROPS.TXT is provided in the help system.

System Architect includes some management reports that can be submitted periodically: Requirement Not Used and Requirement to Symbol Cross-Reference.