Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324832
M. Lefering
In the IPSEN research project at Aachen University in Germany, integration tools that integrate documents of different working areas have been developed. They execute a transformation algorithm and check the consistency incrementally by installing and maintaining links between those documents. A framework is introduced that allows the efficient realization of new integration tools. The functionality and architecture of such an integrator are described. It integrates a requirements engineering document and a programming in the large document that describe a software design in the IPSEN module interconnection language.<>
{"title":"An incremental integration tool between requirements engineering and programming in the large","authors":"M. Lefering","doi":"10.1109/ISRE.1993.324832","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324832","url":null,"abstract":"In the IPSEN research project at Aachen University in Germany, integration tools that integrate documents of different working areas have been developed. They execute a transformation algorithm and check the consistency incrementally by installing and maintaining links between those documents. A framework is introduced that allows the efficient realization of new integration tools. The functionality and architecture of such an integrator are described. It integrates a requirements engineering document and a programming in the large document that describe a software design in the IPSEN module interconnection language.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"60 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123993793","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324859
S. White
Advances in microprocessor and network technology led to the proliferation of complex systems with distributed processing and databases, internal communication systems, and heterogeneous components. The processing components can by themselves comprise a system or they may be embedded in a physical system. Both the encompassing system and the processing system are known as computer-based systems (CBS). Due to complex CBS dynamics and component interdependencies, current system engineering processes are inadequate. Problems with current practice are summarized, and a new solution is proposed.<>
{"title":"Requirements engineering in systems engineering practice","authors":"S. White","doi":"10.1109/ISRE.1993.324859","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324859","url":null,"abstract":"Advances in microprocessor and network technology led to the proliferation of complex systems with distributed processing and databases, internal communication systems, and heterogeneous components. The processing components can by themselves comprise a system or they may be embedded in a physical system. Both the encompassing system and the processing system are known as computer-based systems (CBS). Due to complex CBS dynamics and component interdependencies, current system engineering processes are inadequate. Problems with current practice are summarized, and a new solution is proposed.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121983644","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324833
D. Partridge, D. Garlan, D. Barstow, J. Kramer
The question of specifying systems or domains is addressed. Among the issues discussed are: the requirements of first-class connectors for domain specifications; the use of application frameworks as domain specifications; the role of connectors in domain specifications; domain model specification; the question of what precisely is meant by a domain of the question of reuse; and the difficulty in producing sound domain specifications.<>
{"title":"Should we specify systems or domain?","authors":"D. Partridge, D. Garlan, D. Barstow, J. Kramer","doi":"10.1109/ISRE.1993.324833","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324833","url":null,"abstract":"The question of specifying systems or domains is addressed. Among the issues discussed are: the requirements of first-class connectors for domain specifications; the use of application frameworks as domain specifications; the role of connectors in domain specifications; domain model specification; the question of what precisely is meant by a domain of the question of reuse; and the difficulty in producing sound domain specifications.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129708545","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324835
S. Easterbrook
It is shown how domain modelling can be used within requirements engineering to reveal the conceptual models used by the participants, and relate these to one another. Existing elicitation techniques used in AI adopt a purely cognitive stance, in that they model a single problem-cognitive stance, and ignore the social and organizational context. A framework for representing alternative, conflicting viewpoints in a single domain model is described. The framework is based on the development of a hierarchy of viewpoint descriptions, where lower levels of the hierarchy contain the conflicts. The hierarchies can be viewed in a number of ways, and allow the participants to develop an understanding of each other's perspective. The framework is supported by a set of tools for developing and manipulating these hierarchies.<>
{"title":"Domain modelling with hierarchies of alternative viewpoints","authors":"S. Easterbrook","doi":"10.1109/ISRE.1993.324835","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324835","url":null,"abstract":"It is shown how domain modelling can be used within requirements engineering to reveal the conceptual models used by the participants, and relate these to one another. Existing elicitation techniques used in AI adopt a purely cognitive stance, in that they model a single problem-cognitive stance, and ignore the social and organizational context. A framework for representing alternative, conflicting viewpoints in a single domain model is described. The framework is based on the development of a hierarchy of viewpoint descriptions, where lower levels of the hierarchy contain the conflicts. The hierarchies can be viewed in a number of ways, and allow the participants to develop an understanding of each other's perspective. The framework is supported by a set of tools for developing and manipulating these hierarchies.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123985738","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324830
Thomas J. Smith
A hypertext system, READS, designed to support the key requirements engineering activities of requirements discovery, analysis, decomposition, allocation, traceability and reporting is discussed. READS facilitates the construction, browsing, and maintenance of a typed hypertext network mapped onto a high-speed relational database server through a user interface designed specifically for the system engineer. READS is an integral part of an evolving Paramax system development environment whose goals include the specification of a requirements engineering process and the tool suite necessary to support it. An interface between READS and software using pictures has been developed to test this concept, and it is in active use in many Paramax programs.<>
{"title":"READS: a requirements engineering tool","authors":"Thomas J. Smith","doi":"10.1109/ISRE.1993.324830","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324830","url":null,"abstract":"A hypertext system, READS, designed to support the key requirements engineering activities of requirements discovery, analysis, decomposition, allocation, traceability and reporting is discussed. READS facilitates the construction, browsing, and maintenance of a typed hypertext network mapped onto a high-speed relational database server through a user interface designed specifically for the system engineer. READS is an integral part of an evolving Paramax system development environment whose goals include the specification of a requirements engineering process and the tool suite necessary to support it. An interface between READS and software using pictures has been developed to test this concept, and it is in active use in many Paramax programs.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"71 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129214469","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324837
M. Harrison, P. Barnard
Requirements that involve the usability of systems can be properties of interactions rather than systems alone. This proposition is demonstrated by means of four examples. The authors suggest that a notation like CSP (communicating sequential processes) may be used to provide a framework for considering different modeling approaches. Interaction requirements that relate to multiwindowed systems, walk up and use systems, and dynamic systems such as power stations are considered. It is shown how models provide different representations to which advice from the different disciplines of human computer interaction may be applied.<>
{"title":"On defining requirements for interaction","authors":"M. Harrison, P. Barnard","doi":"10.1109/ISRE.1993.324837","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324837","url":null,"abstract":"Requirements that involve the usability of systems can be properties of interactions rather than systems alone. This proposition is demonstrated by means of four examples. The authors suggest that a notation like CSP (communicating sequential processes) may be used to provide a framework for considering different modeling approaches. Interaction requirements that relate to multiwindowed systems, walk up and use systems, and dynamic systems such as power stations are considered. It is shown how models provide different representations to which advice from the different disciplines of human computer interaction may be applied.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116195468","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324818
P. Luff, M. Jirotka, C. Heath, D. Greatbatch
Methods for requirements elicitation have emphasized techniques for their elicitation and representation. The conception of tasks embodied in these methods is often vague or left implicit and generally characterized in individualistic terms. The authors draw from empirical materials to reveal the social and collaborative nature of task that is also overlooked in participative design or in attempts to elicit multiple viewpoints of an activity. Exploring the socio-interactional nature of activities leads to some radical implications for the technological design. An approach that utilizes ethnographic studies of real-world settings with detailed analysis of interactions of the participants may make an important contribution to the development of requirements method.<>
{"title":"Tasks and social interaction: the relevance of naturalistic analyses of conduct for requirements engineering","authors":"P. Luff, M. Jirotka, C. Heath, D. Greatbatch","doi":"10.1109/ISRE.1993.324818","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324818","url":null,"abstract":"Methods for requirements elicitation have emphasized techniques for their elicitation and representation. The conception of tasks embodied in these methods is often vague or left implicit and generally characterized in individualistic terms. The authors draw from empirical materials to reveal the social and collaborative nature of task that is also overlooked in participative design or in attempts to elicit multiple viewpoints of an activity. Exploring the socio-interactional nature of activities leads to some radical implications for the technological design. An approach that utilizes ethnographic studies of real-world settings with detailed analysis of interactions of the participants may make an important contribution to the development of requirements method.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"77 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124709639","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324852
K. Ryan
The potential role of natural language processing in the requirements engineering process has been overstated in the past, possibly due to fundamental misunderstandings of the requirements engineering process itself. Since more realistic ambitions are likely to lead to less disappointment in the future, an effort is made to identify some phases and tasks where natural language processing may usefully be applied. It is suggested that the validation of requirements must remain an informal, social process.<>
{"title":"The role of natural language in requirements engineering","authors":"K. Ryan","doi":"10.1109/ISRE.1993.324852","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324852","url":null,"abstract":"The potential role of natural language processing in the requirements engineering process has been overstated in the past, possibly due to fundamental misunderstandings of the requirements engineering process itself. Since more realistic ambitions are likely to lead to less disappointment in the future, an effort is made to identify some phases and tasks where natural language processing may usefully be applied. It is suggested that the validation of requirements must remain an informal, social process.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125762785","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324824
John S. Anderson, Brian Durney
A process is described for generating and validating specifications, together with an automated tool which supports this approach. The input to the process is a set of client objectives, expressed as transitions between states. These transitions fall into two classes: those which should be supported, and those which should be prevented. The output is a specification of a target artifact, expressed as a set of capabilities. A valid specification is a set of artifact capabilities that can be used to achieve all desired transitions but cannot be used to achieve any undesirable transitions. An automated system is used for reasoning about scenarios (sequences of actions) to generate and evaluate specifications. Scenarios are employed to identify missing capabilities that would enable artifact users to achieve their goals, and to determine whether a particular capability set will allow prohibited transitions.<>
{"title":"Using scenarios in deficiency-driven requirements engineering","authors":"John S. Anderson, Brian Durney","doi":"10.1109/ISRE.1993.324824","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324824","url":null,"abstract":"A process is described for generating and validating specifications, together with an automated tool which supports this approach. The input to the process is a set of client objectives, expressed as transitions between states. These transitions fall into two classes: those which should be supported, and those which should be prevented. The output is a specification of a target artifact, expressed as a set of capabilities. A valid specification is a set of artifact capabilities that can be used to achieve all desired transitions but cannot be used to achieve any undesirable transitions. An automated system is used for reasoning about scenarios (sequences of actions) to generate and evaluate specifications. Scenarios are employed to identify missing capabilities that would enable artifact users to achieve their goals, and to determine whether a particular capability set will allow prohibited transitions.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124902300","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324825
R. Lutz
The root causes of safety-related software errors in safety-critical embedded systems are analyzed. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than those that produce nonsafety-related software errors. Safety-related software errors are shown to arise most commonly from: discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system; and misunderstandings of the interface of the software with the rest of the system. These results are used to identify methods by which requirements errors can be prevented. The goal is to reduce safety-related software errors and to enhance the safety of complex, embedded systems.<>
{"title":"Analyzing software requirements errors in safety-critical, embedded systems","authors":"R. Lutz","doi":"10.1109/ISRE.1993.324825","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324825","url":null,"abstract":"The root causes of safety-related software errors in safety-critical embedded systems are analyzed. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than those that produce nonsafety-related software errors. Safety-related software errors are shown to arise most commonly from: discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system; and misunderstandings of the interface of the software with the rest of the system. These results are used to identify methods by which requirements errors can be prevented. The goal is to reduce safety-related software errors and to enhance the safety of complex, embedded systems.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"92 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131002082","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：