{"title":"结合用户界面和领域需求的分析","authors":"G. Kösters, H. Six, J. Voss","doi":"10.1109/ICRE.1996.491445","DOIUrl":null,"url":null,"abstract":"A requirements analysis method called FLUID is proposed which in contrast to conventional methods explicitly captures the requirements of direct manipulation user interfaces. The main concepts addressing the user interface requirements comprise a task model and a UIA model. The latter reveals the essential structure of the user interface and defines the basic dialog behavior, the presentation of domain model components on the screen, and links to the domain model. User interface requirements are described on a level of abstraction similar to that of conventional requirements, e.g. details of screen layout and dialog behavior are deferred to later development stages. The result of the entire requirements analysis-a combination of domain model and UIA model-serves as a basis for the further development process. The method also provides for (semi) automatic generation of user interface prototypes at intermediate stages of the analysis.","PeriodicalId":152956,"journal":{"name":"Proceedings of the Second International Conference on Requirements Engineering","volume":"153 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1996-04-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"25","resultStr":"{\"title\":\"Combined analysis of user interface and domain requirements\",\"authors\":\"G. Kösters, H. Six, J. Voss\",\"doi\":\"10.1109/ICRE.1996.491445\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"A requirements analysis method called FLUID is proposed which in contrast to conventional methods explicitly captures the requirements of direct manipulation user interfaces. The main concepts addressing the user interface requirements comprise a task model and a UIA model. The latter reveals the essential structure of the user interface and defines the basic dialog behavior, the presentation of domain model components on the screen, and links to the domain model. User interface requirements are described on a level of abstraction similar to that of conventional requirements, e.g. details of screen layout and dialog behavior are deferred to later development stages. The result of the entire requirements analysis-a combination of domain model and UIA model-serves as a basis for the further development process. The method also provides for (semi) automatic generation of user interface prototypes at intermediate stages of the analysis.\",\"PeriodicalId\":152956,\"journal\":{\"name\":\"Proceedings of the Second International Conference on Requirements Engineering\",\"volume\":\"153 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1996-04-15\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"25\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the Second International Conference on Requirements Engineering\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICRE.1996.491445\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the Second International Conference on Requirements Engineering","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICRE.1996.491445","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Combined analysis of user interface and domain requirements
A requirements analysis method called FLUID is proposed which in contrast to conventional methods explicitly captures the requirements of direct manipulation user interfaces. The main concepts addressing the user interface requirements comprise a task model and a UIA model. The latter reveals the essential structure of the user interface and defines the basic dialog behavior, the presentation of domain model components on the screen, and links to the domain model. User interface requirements are described on a level of abstraction similar to that of conventional requirements, e.g. details of screen layout and dialog behavior are deferred to later development stages. The result of the entire requirements analysis-a combination of domain model and UIA model-serves as a basis for the further development process. The method also provides for (semi) automatic generation of user interface prototypes at intermediate stages of the analysis.