earticle

영어

This paper surveyed 30 system designers and developers who had been participating in a project for five months to examine the usefulness of design artifacts for object-oriented system development. A set of nine requirement and design documents was selected in consideration of the IEEE guidelines. Overall the respondents appeared to agree that the artifacts were useful for system development. On the other hand, the contribution of design artifacts to maintenance was rated lower due to the frequent changes over the iterative process. Of the artifacts, considered more useful were use case specifications, UI design and operation specifications. The respondents were the most reluctant to write test cases. Designers did not like to document more details in the design artifacts than did developers. A future study is required to determine the economics and change management of documentation.