{"title":"需求说明错误的早期检测","authors":"P. Jorgensen","doi":"10.1109/CMPASS.1988.9636","DOIUrl":null,"url":null,"abstract":"An important class of system errors is defined and initial results with two prototype requirements-analysis tools are described. A requirements-specification technique that is highly operational is presented; it expresses the sequential behavior of a system in terms of processes that are equivalent to Petri nets. Subsequent definitions based on directed graphs describe the possible ways in which individual processes might interact, thereby providing a basis for requirements-analysis tools that can detect class two errors at the end of the requirements-specification phase, rather than after system delivery.<<ETX>>","PeriodicalId":224212,"journal":{"name":"Computer Assurance, 1988. COMPASS '88","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1988-06-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"4","resultStr":"{\"title\":\"Early detection of requirements specification errors\",\"authors\":\"P. Jorgensen\",\"doi\":\"10.1109/CMPASS.1988.9636\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"An important class of system errors is defined and initial results with two prototype requirements-analysis tools are described. A requirements-specification technique that is highly operational is presented; it expresses the sequential behavior of a system in terms of processes that are equivalent to Petri nets. Subsequent definitions based on directed graphs describe the possible ways in which individual processes might interact, thereby providing a basis for requirements-analysis tools that can detect class two errors at the end of the requirements-specification phase, rather than after system delivery.<<ETX>>\",\"PeriodicalId\":224212,\"journal\":{\"name\":\"Computer Assurance, 1988. COMPASS '88\",\"volume\":\"1 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1988-06-27\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"4\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Computer Assurance, 1988. COMPASS '88\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/CMPASS.1988.9636\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Computer Assurance, 1988. COMPASS '88","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/CMPASS.1988.9636","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Early detection of requirements specification errors
An important class of system errors is defined and initial results with two prototype requirements-analysis tools are described. A requirements-specification technique that is highly operational is presented; it expresses the sequential behavior of a system in terms of processes that are equivalent to Petri nets. Subsequent definitions based on directed graphs describe the possible ways in which individual processes might interact, thereby providing a basis for requirements-analysis tools that can detect class two errors at the end of the requirements-specification phase, rather than after system delivery.<>
求助内容：
应助结果提醒方式：
京公网安备 11010802042870号
