{"title":"朝向一个可重用的基于需求的系统模型的持续构建过程","authors":"M. Glas, S. Sartorius","doi":"10.1109/AERO.2012.6187338","DOIUrl":null,"url":null,"abstract":"The conceptual development process is the joint effort of designers and future operators to elicit and analyze requirements and to design a system which plausibly meets these requirements. A continuous build-up of a structured product model that explicitly interrelates system design and its metrics to requirements is desirable. However, requirements and system modeling are usually conducted separately using different tools. Moreover, the phases of the development process are often separated in time, personnel, and space. This practice leaves a considerable number of system design decisions untraceable. We address these problems by two propositions: (1) A use case which describes an iterative, concurrent, and continuous refinement process of the requirements and system model, and (2) a framework that allows the creation of an integrated system and requirements model and the gradual application of increasingly rigorous rules on the model. We demonstrate our approach by a simple conceptual aircraft design example and discuss whether our approach is scalable and promotes the reuse of model parts.","PeriodicalId":6421,"journal":{"name":"2012 IEEE Aerospace Conference","volume":"15 1","pages":"1-8"},"PeriodicalIF":0.0000,"publicationDate":"2012-03-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"Towards a continuous build-up process of a reusable requirements-based system model\",\"authors\":\"M. Glas, S. Sartorius\",\"doi\":\"10.1109/AERO.2012.6187338\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The conceptual development process is the joint effort of designers and future operators to elicit and analyze requirements and to design a system which plausibly meets these requirements. A continuous build-up of a structured product model that explicitly interrelates system design and its metrics to requirements is desirable. However, requirements and system modeling are usually conducted separately using different tools. Moreover, the phases of the development process are often separated in time, personnel, and space. This practice leaves a considerable number of system design decisions untraceable. We address these problems by two propositions: (1) A use case which describes an iterative, concurrent, and continuous refinement process of the requirements and system model, and (2) a framework that allows the creation of an integrated system and requirements model and the gradual application of increasingly rigorous rules on the model. We demonstrate our approach by a simple conceptual aircraft design example and discuss whether our approach is scalable and promotes the reuse of model parts.\",\"PeriodicalId\":6421,\"journal\":{\"name\":\"2012 IEEE Aerospace Conference\",\"volume\":\"15 1\",\"pages\":\"1-8\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-03-03\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2012 IEEE Aerospace Conference\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AERO.2012.6187338\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2012 IEEE Aerospace Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AERO.2012.6187338","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Towards a continuous build-up process of a reusable requirements-based system model
The conceptual development process is the joint effort of designers and future operators to elicit and analyze requirements and to design a system which plausibly meets these requirements. A continuous build-up of a structured product model that explicitly interrelates system design and its metrics to requirements is desirable. However, requirements and system modeling are usually conducted separately using different tools. Moreover, the phases of the development process are often separated in time, personnel, and space. This practice leaves a considerable number of system design decisions untraceable. We address these problems by two propositions: (1) A use case which describes an iterative, concurrent, and continuous refinement process of the requirements and system model, and (2) a framework that allows the creation of an integrated system and requirements model and the gradual application of increasingly rigorous rules on the model. We demonstrate our approach by a simple conceptual aircraft design example and discuss whether our approach is scalable and promotes the reuse of model parts.