Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324857
A. J. Schouwen, D. Parnas, J. Madey
A functional approach to specifying the requirements of a computer system is discussed. The method allows system requirements to be documented, whether the system is implemented using a computer and peripheral devices, or, for example, relays and analog components. The method is a refinement of the method used in the A-7 aircraft software requirements model document. The approach is illustrated with examples derived from a software requirements document for a water level monitoring system.<>
{"title":"Documentation of requirements for computer systems","authors":"A. J. Schouwen, D. Parnas, J. Madey","doi":"10.1109/ISRE.1993.324857","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324857","url":null,"abstract":"A functional approach to specifying the requirements of a computer system is discussed. The method allows system requirements to be documented, whether the system is implemented using a computer and peripheral devices, or, for example, relays and analog components. The method is a refinement of the method used in the A-7 aircraft software requirements model document. The approach is illustrated with examples derived from a software requirements document for a water level monitoring system.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"1 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":"131005738","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.324828
N. Maiden, A. Sutcliffe
Domain abstraction reuse during requirements engineering is evaluated as a paradigm during use of a research tool. Iterative fact acquisition and abstraction retrieval, supported by example-based explanation of abstractions, are implemented in a prototype known as AIR (adviser for intelligent reuse). Observation of the use of AIRs by inexperienced software engineers reveal the effectiveness of this paradigm despite several problems. These problems are examined so as to identify improvements for future versions of intelligent requirements engineering environments.<>
{"title":"Requirements engineering by example: an empirical study","authors":"N. Maiden, A. Sutcliffe","doi":"10.1109/ISRE.1993.324828","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324828","url":null,"abstract":"Domain abstraction reuse during requirements engineering is evaluated as a paradigm during use of a research tool. Iterative fact acquisition and abstraction retrieval, supported by example-based explanation of abstractions, are implemented in a prototype known as AIR (adviser for intelligent reuse). Observation of the use of AIRs by inexperienced software engineers reveal the effectiveness of this paradigm despite several problems. These problems are examined so as to identify improvements for future versions of intelligent requirements engineering environments.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"93 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":"134045425","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.324856
S. Kent, T. Maibaum, W. Quirk
Recent research has advocated the use of deontic logics in requirements specification. A form of deontic action logic is described, and it is shown how it can be used to specify both temporal constraints and error recovery. The logic includes a deontic predicate of bounded obligation, and normative predicates. Bounded obligation allows bounds to be placed on the performance of actions, and can be used to specify temporal constraints. The formalism also allows the removal and extension of obligations before they must be met. The normative predicates indicate when a system has performed an action normally or abnormally, and allow the specification of corrective actions that recover from error situations.<>
{"title":"Formally specifying temporal constraints and error recovery","authors":"S. Kent, T. Maibaum, W. Quirk","doi":"10.1109/ISRE.1993.324856","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324856","url":null,"abstract":"Recent research has advocated the use of deontic logics in requirements specification. A form of deontic action logic is described, and it is shown how it can be used to specify both temporal constraints and error recovery. The logic includes a deontic predicate of bounded obligation, and normative predicates. Bounded obligation allows bounds to be placed on the performance of actions, and can be used to specify temporal constraints. The formalism also allows the removal and extension of obligations before they must be met. The normative predicates indicate when a system has performed an action normally or abnormally, and allow the specification of corrective actions that recover from error situations.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"86 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":"132581099","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.324829
N. Takeda, A. Shiomi, Kazuhisa Kawai, H. Ohiwa
The KJ method, a technique for obtaining a panoramic view of entire index card arrangements on a computer display, is described. The KJ editor simulates the activity of arranging index cards on a desk. Such activity is essential for carrying out the so-called KJ method, which is used in Japanese business. The editor is used for requirements analysis. It is found that the editor can be used for recording the analytical thinking process and that the resultant chart becomes a very good medium communication between the design and the sponsor/user.<>
{"title":"Requirement analysis by the KJ editor","authors":"N. Takeda, A. Shiomi, Kazuhisa Kawai, H. Ohiwa","doi":"10.1109/ISRE.1993.324829","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324829","url":null,"abstract":"The KJ method, a technique for obtaining a panoramic view of entire index card arrangements on a computer display, is described. The KJ editor simulates the activity of arranging index cards on a desk. Such activity is essential for carrying out the so-called KJ method, which is used in Japanese business. The editor is used for requirements analysis. It is found that the editor can be used for recording the analytical thinking process and that the resultant chart becomes a very good medium communication between the design and the sponsor/user.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"45 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":"123931030","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.324853
Yasunori Ishihara, H. Seki, T. Kasami
A method of translating natural language specifications of communication protocols into algebraic specifications is presented. Such a natural language specification specifies action sequences performed by the protocol machine (program). Usually, a sentence implicitly specifies the state of the protocol machine in which the described actions should be performed. A method of analyzing the implicitly specified states of the protocol machine is proposed, taking the OSI session protocol specification as an example. The method uses the following properties: (a) syntactic properties of a natural language; (b) syntactic properties introduced by the target algebraic specifications, e.g., subtype relations; and (c) properties of a data type, e.g., properties of timer. The results of applying this method to the main part of the OSI session protocol specification is shown.<>
{"title":"A translation method from natural language specifications into formal specifications using contextual dependencies","authors":"Yasunori Ishihara, H. Seki, T. Kasami","doi":"10.1109/ISRE.1993.324853","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324853","url":null,"abstract":"A method of translating natural language specifications of communication protocols into algebraic specifications is presented. Such a natural language specification specifies action sequences performed by the protocol machine (program). Usually, a sentence implicitly specifies the state of the protocol machine in which the described actions should be performed. A method of analyzing the implicitly specified states of the protocol machine is proposed, taking the OSI session protocol specification as an example. The method uses the following properties: (a) syntactic properties of a natural language; (b) syntactic properties introduced by the target algebraic specifications, e.g., subtype relations; and (c) properties of a data type, e.g., properties of timer. The results of applying this method to the main part of the OSI session protocol specification is shown.<<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":"127140239","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.324845
E. Sibley, R. Wexelblat, J. Michael, M. Tanner, D. Littman
Three significant challenges facing the discipline of software engineering are understanding how software designers reason about policy, understanding how they define requirements based on this reasoning, and providing machine-based intelligent tools that support reasoning about policy. The authors are developing the concept of a policy workbench: knowledge-based tools that support reasoning about such properties of policies as consistency, completeness, and correctness, and the implications of policy for the behavior of a system. They discuss how such a workbench might help software designers reason about the relationships between policies and requirements.<>
{"title":"The role of policy in requirements definition","authors":"E. Sibley, R. Wexelblat, J. Michael, M. Tanner, D. Littman","doi":"10.1109/ISRE.1993.324845","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324845","url":null,"abstract":"Three significant challenges facing the discipline of software engineering are understanding how software designers reason about policy, understanding how they define requirements based on this reasoning, and providing machine-based intelligent tools that support reasoning about policy. The authors are developing the concept of a policy workbench: knowledge-based tools that support reasoning about such properties of policies as consistency, completeness, and correctness, and the implications of policy for the behavior of a system. They discuss how such a workbench might help software designers reason about the relationships between policies and requirements.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"19 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":"126756184","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.324840
M. Jarke, J. Bubenko, C. Rolland, A. Sutcliffe, Y. Vassiliou
NATURE is a collaborative basic research project on theories underlying requirements engineering funded by the ESPRIT III program of the European communities. Its goals are to develop a theory of knowledge representation that embraces subject, usage and development worlds surrounding the system, including expressive freedoms; a theory of domain engineering that facilitates the identification, acquisition and formalization of domain knowledge as well as similarity-based matching and classifying of software engineering knowledge; and a process engineering theory that promotes context and decision-based control of the development process. These theories are integrated and evaluated in a prototype environment constructed around an extended version of the conceptual modeling language Telos.<>
{"title":"Theories underlying requirements engineering: an overview of NATURE at Genesis","authors":"M. Jarke, J. Bubenko, C. Rolland, A. Sutcliffe, Y. Vassiliou","doi":"10.1109/ISRE.1993.324840","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324840","url":null,"abstract":"NATURE is a collaborative basic research project on theories underlying requirements engineering funded by the ESPRIT III program of the European communities. Its goals are to develop a theory of knowledge representation that embraces subject, usage and development worlds surrounding the system, including expressive freedoms; a theory of domain engineering that facilitates the identification, acquisition and formalization of domain knowledge as well as similarity-based matching and classifying of software engineering knowledge; and a process engineering theory that promotes context and decision-based control of the development process. These theories are integrated and evaluated in a prototype environment constructed around an extended version of the conceptual modeling language Telos.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"5 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":"126470173","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.324821
I. Sommerville, T. Rodden, P. Sawyer, R. Bentley, M. Twidale
Experiences from an interdisciplinary project involving software engineers and sociologists are reported. The project is concerned with discovering the requirements of a user interface to a flight database which is used to provide real-time information to air-traffic controllers. The sociologists are conducting an ethnographic analysis of the activity of air-traffic control, and this is being used for the development of a prototype system. An overview of the project is given, the contribution of sociologists to requirements engineering is discussed, and tool support which will allow ethnographic observations to be integrated into the requirements engineering process is suggested.<>
{"title":"Integrating ethnography into the requirements engineering process","authors":"I. Sommerville, T. Rodden, P. Sawyer, R. Bentley, M. Twidale","doi":"10.1109/ISRE.1993.324821","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324821","url":null,"abstract":"Experiences from an interdisciplinary project involving software engineers and sociologists are reported. The project is concerned with discovering the requirements of a user interface to a flight database which is used to provide real-time information to air-traffic controllers. The sociologists are conducting an ethnographic analysis of the activity of air-traffic control, and this is being used for the development of a prototype system. An overview of the project is given, the contribution of sociologists to requirements engineering is discussed, and tool support which will allow ethnographic observations to be integrated into the requirements engineering process is suggested.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"4 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":"130658400","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.324855
J. Souquières, N. Lévy
A framework allowing the expression of both the incremental construction of a specification and the development process behind the construction (decisions and their rationale) is proposed. A data structure composed of a workplan and the product is introduced and used to model a specification development. The availability of development operators is a critical point of the specification development model. Operators encapsulate general problem solving strategies. Development operators are defined by their parallel action on the workplan, the product, and the links between them. The implementation of the proposed approach requires an environment managing the workplan and the current specification being built. The operators will be chosen via menus dynamically defined according to the current task type.<>
{"title":"Description of specification developments","authors":"J. Souquières, N. Lévy","doi":"10.1109/ISRE.1993.324855","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324855","url":null,"abstract":"A framework allowing the expression of both the incremental construction of a specification and the development process behind the construction (decisions and their rationale) is proposed. A data structure composed of a workplan and the product is introduced and used to model a specification development. The availability of development operators is a critical point of the specification development model. Operators encapsulate general problem solving strategies. Development operators are defined by their parallel action on the workplan, the product, and the links between them. The implementation of the proposed approach requires an environment managing the workplan and the current specification being built. The operators will be chosen via menus dynamically defined according to the current task type.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"96 9","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-01-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131893863","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.324850
B. Ramesh, Luqi
Rapid prototyping offers an iterative approach to requirements engineering to alleviate problems such as uncertainty, ambiguity, and inconsistency inherent in the process. As the systems development process is characterized by changing requirements and assumptions, involving multiple stakeholders with often differing viewpoints, it will be beneficial to capture in a structured manner the history of the development process. The authors describe how CAPS (computer aided prototyping system) as a prototyping tool, augmented with REMAP (representation and maintenance of process knowledge) framework for reasoning with process knowledge, helps firm up software requirements. This is accomplished by iterative negotiations between various customers and by examination of executable prototypes in the context of evolving requirements.<>
{"title":"Process knowledge based rapid prototyping for requirements engineering","authors":"B. Ramesh, Luqi","doi":"10.1109/ISRE.1993.324850","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324850","url":null,"abstract":"Rapid prototyping offers an iterative approach to requirements engineering to alleviate problems such as uncertainty, ambiguity, and inconsistency inherent in the process. As the systems development process is characterized by changing requirements and assumptions, involving multiple stakeholders with often differing viewpoints, it will be beneficial to capture in a structured manner the history of the development process. The authors describe how CAPS (computer aided prototyping system) as a prototyping tool, augmented with REMAP (representation and maintenance of process knowledge) framework for reasoning with process knowledge, helps firm up software requirements. This is accomplished by iterative negotiations between various customers and by examination of executable prototypes in the context of evolving requirements.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"1 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":"128403885","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}