| Summary: | 碩士 === 國立東華大學 === 資訊工程學系 === 89 === Abstract
Many analysis methods have been developed, most of them assume that requirements are available. This assumption is generally incorrect, because requirements may be incomplete, inconsistent, or even in conflict. A specification developed based on incorrect requirements. Will be incorrect. Moreover, design document and program code develop based on incorrect specification will also be incorrect . In this regard, requirement should be gathered and verified a specification is developed. Base on this consideration, we have developed a technique to gather requirement . This technique utilizes meeting to combine requirement requirements gathered by stakeholders and ages a UML-based model to represent requirements. Requirements represented by the model are then verified by stakeholders. Since the UML-based model is the most important in our technique, we call our technique a model-driven requirements gathering technique.
|
|---|
