| Summary: | 碩士 === 國立中山大學 === 資訊管理研究所 === 86 === In traditional system engineering, there are many problems present in system development life cycle, system development technologies, and system models. These problems directly or indirectly influence the success of developing a system. Accordingly, our research introduces the Requirement-Oriented System Engineering that emphasizes on using user requirements to consolidate the development of systems and appreciates the integration and controllability of system development. We redesign the system development life cycle and adopt the Hierarchical System Development Life Cycle to let an expected system can be developed from top to town or bottom to up. It also let system models, prototypes, and system testing be tightly combined. Simultaneously, we lay stress on the linkage between customers and developers in the process of system development. Besides, to keep consistence and integrity among system models, we invoke the Communicating Agent for System Modeling as a base of system modeling and then adds multiple viewpoints and techniques of system analysis in it. Finally, we generate three consecutive system models: requirement model; analysis model, and design model. Three exist rules that help transform from one model to another. Therefore, it solves the non-homogenous problems among system models in different development phase, so that the constructed system can match user requirement after a series of transformation among those system models.
Although object-oriented requirement analysis technologies have been widely used in information system development like structured analysis technologies, traditional requirement extraction technologies remain in eliciting functional requirements. Since functional requirement extraction techniques and object-oriented requirement analysis techniques have many obviously differences in perspectives of requirement abstraction, partition and projection, it made extracting functional requirements can not be followed by object-oriented requirement analysis directly. Accordingly, our research addresses an extraction and analysis technology of multiple requirements to improve the traditional requirement extraction technologies. By adding structural requirement extraction techniques in traditional methods, the elicited system requirements are more consistent with the essence of structured and object-oriented analysis, and more adopted to object-oriented requirement analysis methods. Beside, our research not only provides a complete and concrete specification to multiple requirements as an explicit reference, it also rearranges requirement extraction and analysis approaches by associating them together. Since there is an explicit reference to multiple requirements and the obstacle of transformation between requirement extraction and analysis is elimenated, we can then easily obtain a correct, complete and consistent system requirement.
|
|---|
