Pub Date : 1993-01-04DOI: 10.1109/ISRE.1993.324844
Lewis Johnson, S. Greenspan, J. Lee, G. Fischer, C. Potts
A discussion on recording requirements assumptions and rationale is summarized. Among the topics discussed by the participants are: incrementality in rational management; grounding argumentations in construction; architecture for integrated design environments; requirements definition in design; representation of rationale; rationale management systems; and incremental formalization of rationale.<>
{"title":"Recording requirements assumptions and rationale","authors":"Lewis Johnson, S. Greenspan, J. Lee, G. Fischer, C. Potts","doi":"10.1109/ISRE.1993.324844","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324844","url":null,"abstract":"A discussion on recording requirements assumptions and rationale is summarized. Among the topics discussed by the participants are: incrementality in rational management; grounding argumentations in construction; architecture for integrated design environments; requirements definition in design; representation of rationale; rationale management systems; and incremental formalization of rationale.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"87 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":"126176906","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.324831
A. Ohnishi, K. Agusa
Computer-aided requirements definition methods/environment are presented. A composite requirements model (requirements frame) is proposed, and several supporting methods of software requirements definition based on the model are developed. They are: analysis of requirements; describing requirements; verification of an SRS (software requirements specification); SRS execution; and software preliminary design. With these methods, it is possible to obtain an SRS of good quality (correctness, testability, traceability, feasibility, and usability). The authors have been developing an environment of requirements definition, named CARD, by using these methods. They present some examples of experimental uses of CARD.<>
{"title":"CARD: a software requirements definition environment","authors":"A. Ohnishi, K. Agusa","doi":"10.1109/ISRE.1993.324831","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324831","url":null,"abstract":"Computer-aided requirements definition methods/environment are presented. A composite requirements model (requirements frame) is proposed, and several supporting methods of software requirements definition based on the model are developed. They are: analysis of requirements; describing requirements; verification of an SRS (software requirements specification); SRS execution; and software preliminary design. With these methods, it is possible to obtain an SRS of good quality (correctness, testability, traceability, feasibility, and usability). The authors have been developing an environment of requirements definition, named CARD, by using these methods. They present some examples of experimental uses of CARD.<<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":"124376278","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.324841
W. Rzepka, J. Sidoran, D. White
The program of research and development of requirements engineering technologies at Rome Laboratory since the early 1980s is described. Research is based on a process model of requirements engineering, and implementation of this model using conventional technologies. R&D activities have led to the enhancement of a requirements analysis tool and the development of two requirements validation tools based on rapid prototyping. Ongoing work is integrating these three tools into a requirements engineering workstation. Other research uses artificial intelligence to creat an alternative software development paradigm called the knowledge-based software assistant. These efforts are described, together with their impact on future plans for evolutionary development of the workstation environment.<>
{"title":"Requirements engineering technologies at Rome Laboratory","authors":"W. Rzepka, J. Sidoran, D. White","doi":"10.1109/ISRE.1993.324841","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324841","url":null,"abstract":"The program of research and development of requirements engineering technologies at Rome Laboratory since the early 1980s is described. Research is based on a process model of requirements engineering, and implementation of this model using conventional technologies. R&D activities have led to the enhancement of a requirements analysis tool and the development of two requirements validation tools based on rapid prototyping. Ongoing work is integrating these three tools into a requirements engineering workstation. Other research uses artificial intelligence to creat an alternative software development paradigm called the knowledge-based software assistant. These efforts are described, together with their impact on future plans for evolutionary development of the workstation environment.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"18 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":"114403644","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.324851
Julio Cesar Sampaio do Prado Leite, Ana Paula M. Franco
A strategy for conceptual model acquisition is proposed. Knowledge acquisition is performed with a simple structure, i.e., the lexicon. Using the lexicon and an AI-based approach, a conceptual model is derived. The approach assists in the construction of a first cut version of the conceptual model, which should undergo a validation process. A prototype is built using an object-oriented AI shell. The system is tested with a library example (a 50 entries lexicon).<>
{"title":"A strategy for conceptual model acquisition","authors":"Julio Cesar Sampaio do Prado Leite, Ana Paula M. Franco","doi":"10.1109/ISRE.1993.324851","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324851","url":null,"abstract":"A strategy for conceptual model acquisition is proposed. Knowledge acquisition is performed with a simple structure, i.e., the lexicon. Using the lexicon and an AI-based approach, a conceptual model is derived. The approach assists in the construction of a first cut version of the conceptual model, which should undergo a validation process. A prototype is built using an object-oriented AI shell. The system is tested with a library example (a 50 entries lexicon).<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"47 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":"125685329","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.324834
M. Feather
The ability to rapidly reconnoitre requirements, i.e., construct, critique, contrast and complete a system's requirements, necessitates dealing with the inherent nature of requirements (their incompleteness, inconsistency, ambiguity, etc.). It is shown how such explorations can be sustained by linking a network of domain requirements with instantiations of those requirements for a particular instance of that domain.<>
{"title":"Requirements reconnoitring at the juncture of domain and instance","authors":"M. Feather","doi":"10.1109/ISRE.1993.324834","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324834","url":null,"abstract":"The ability to rapidly reconnoitre requirements, i.e., construct, critique, contrast and complete a system's requirements, necessitates dealing with the inherent nature of requirements (their incompleteness, inconsistency, ambiguity, etc.). It is shown how such explorations can be sustained by linking a network of domain requirements with instantiations of those requirements for a particular instance of that domain.<<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":"128897181","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.324823
M. Ryan
A formalism is motivated and described for representing defaults in specifications. The formalism is called ordered theory presentations. The ability to represent defaults narrows the gap between a customer's initial requirements and a formal specification, and supports reuse on both a small and a large scale. Issues are illustrated throughout reference to the lift example. The application of the formalism to specification revision is considered.<>
{"title":"Defaults in specifications","authors":"M. Ryan","doi":"10.1109/ISRE.1993.324823","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324823","url":null,"abstract":"A formalism is motivated and described for representing defaults in specifications. The formalism is called ordered theory presentations. The ability to represent defaults narrows the gap between a customer's initial requirements and a formal specification, and supports reuse on both a small and a large scale. Issues are illustrated throughout reference to the lift example. The application of the formalism to specification revision is considered.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"165 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":"122841775","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.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.324848
S. Greenspan, M. Feblowitz
Service-providing enterprises (SPEs) employ systems composed of people, computer hardware and software, and other mechanisms to perform service actions in the customer's environment as well as to carry out internal operations as part of the SPE infrastructure. These systems are termed service-oriented systems (SOSs). The authors address the question of how to reformulate and simplify the requirements engineering process by adopting an SOS paradigm. It is shown that there are advantages to viewing many large, complex systems within the SOS paradigm. This is due to the increasingly service-oriented economy as well as the increased demands for a paradigm for integration of and interoperability between systems across multiple enterprises. The domain of SOSs is described, together with the technique by which SPE forms the context for requirements modeling and analysis. A requirements modeling framework consisting of several viewpoints and their interrelationships is outlined in order to define the SOS requirements analysis task. The context in which the defined requirements modeling task will be useful is explained.<>
{"title":"Requirements engineering using the SOS paradigm","authors":"S. Greenspan, M. Feblowitz","doi":"10.1109/ISRE.1993.324848","DOIUrl":"https://doi.org/10.1109/ISRE.1993.324848","url":null,"abstract":"Service-providing enterprises (SPEs) employ systems composed of people, computer hardware and software, and other mechanisms to perform service actions in the customer's environment as well as to carry out internal operations as part of the SPE infrastructure. These systems are termed service-oriented systems (SOSs). The authors address the question of how to reformulate and simplify the requirements engineering process by adopting an SOS paradigm. It is shown that there are advantages to viewing many large, complex systems within the SOS paradigm. This is due to the increasingly service-oriented economy as well as the increased demands for a paradigm for integration of and interoperability between systems across multiple enterprises. The domain of SOSs is described, together with the technique by which SPE forms the context for requirements modeling and analysis. A requirements modeling framework consisting of several viewpoints and their interrelationships is outlined in order to define the SOS requirements analysis task. The context in which the defined requirements modeling task will be useful is explained.<<ETX>>","PeriodicalId":375368,"journal":{"name":"[1993] Proceedings of the IEEE International Symposium on Requirements Engineering","volume":"172 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":"122280236","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.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}