Pub Date : 1993-07-19DOI: 10.1109/CASE.1993.634811
Oscar Barros
Presents an integrated methodology for deriving the requirements of an information system based on the design of the organizational components external to the computer. This methodology, which is supported by a CASE software, results in the definition and formal specification of computer objects that satisfy the above requirements. Such objects can be executed for requirements validation.
{"title":"Requirements elicitation and formalization through CASE-supported external design and object-oriented specification","authors":"Oscar Barros","doi":"10.1109/CASE.1993.634811","DOIUrl":"https://doi.org/10.1109/CASE.1993.634811","url":null,"abstract":"Presents an integrated methodology for deriving the requirements of an information system based on the design of the organizational components external to the computer. This methodology, which is supported by a CASE software, results in the definition and formal specification of computer objects that satisfy the above requirements. Such objects can be executed for requirements validation.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125907901","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-07-19DOI: 10.1109/CASE.1993.634835
K. P. Tan, G. H. Ong, P. Wong
A heuristics method for the automatic placement of data flow diagrams (DFDs) is presented. It fulfills the whole set of aesthetics requirements for a nice DFD layout within an acceptable time bound. The system allocates the process with most data flows at the center of a 2-D grid space and effectively handles the positional preference for entities, processes, and data stores. The test cut function detects any crisscrossing of data flows and any cutting of DFD objects. The pop function pops up to those objects of high intersection weight to the upper layer under aesthetics optimization. This 3-D DFD contains only linear data flows with all crisscrossings eliminated. A noncutting connection between two objects can be seen clearly by rotating the 3-D DFD at every 90/spl deg/ step. Thus, the heuristics method realizes the abstraction of automatic diagram creation.
{"title":"A heuristics approach to automatic data flow diagram layout","authors":"K. P. Tan, G. H. Ong, P. Wong","doi":"10.1109/CASE.1993.634835","DOIUrl":"https://doi.org/10.1109/CASE.1993.634835","url":null,"abstract":"A heuristics method for the automatic placement of data flow diagrams (DFDs) is presented. It fulfills the whole set of aesthetics requirements for a nice DFD layout within an acceptable time bound. The system allocates the process with most data flows at the center of a 2-D grid space and effectively handles the positional preference for entities, processes, and data stores. The test cut function detects any crisscrossing of data flows and any cutting of DFD objects. The pop function pops up to those objects of high intersection weight to the upper layer under aesthetics optimization. This 3-D DFD contains only linear data flows with all crisscrossings eliminated. A noncutting connection between two objects can be seen clearly by rotating the 3-D DFD at every 90/spl deg/ step. Thus, the heuristics method realizes the abstraction of automatic diagram creation.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130702495","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-07-19DOI: 10.1109/CASE.1993.634819
G. Avellis, L. Borzacchini, A. Cavallo, P. Cotugno, G. De Mastro
System design recovery and impact analysis are critical phases in the process of software maintenance. It is argued that the interdependence of abstraction recovery tools and application domains plays a key role in providing intelligent assistance in software maintenance, and the use of a blackboard model to address the issue of knowledge sources integration is advocated. A software maintenance expert sytem (SMES) based on a blackboard architecture has been developed to evaluate the approach. Explicit links between specification, design and implementation objects have been represented in the blackboard working memory, as well as the design decisions in the abstraction recovery process. These links are then used in the software evolution process to support impact analysis.
{"title":"A blackboard architecture for intelligent assistance in software maintenance","authors":"G. Avellis, L. Borzacchini, A. Cavallo, P. Cotugno, G. De Mastro","doi":"10.1109/CASE.1993.634819","DOIUrl":"https://doi.org/10.1109/CASE.1993.634819","url":null,"abstract":"System design recovery and impact analysis are critical phases in the process of software maintenance. It is argued that the interdependence of abstraction recovery tools and application domains plays a key role in providing intelligent assistance in software maintenance, and the use of a blackboard model to address the issue of knowledge sources integration is advocated. A software maintenance expert sytem (SMES) based on a blackboard architecture has been developed to evaluate the approach. Explicit links between specification, design and implementation objects have been represented in the blackboard working memory, as well as the design decisions in the abstraction recovery process. These links are then used in the software evolution process to support impact analysis.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115575583","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-07-19DOI: 10.1109/CASE.1993.634833
F. Oquendo
The European SCALE project is presented. This project aims to develop, demonstrate, and assess a set of advanced CASE process-centered environments for improving the support of system composition strategies explicitly based on the planned and intensive reuse of components.
{"title":"SCALE: Software process-centered CASE environments for system composition and component reuse","authors":"F. Oquendo","doi":"10.1109/CASE.1993.634833","DOIUrl":"https://doi.org/10.1109/CASE.1993.634833","url":null,"abstract":"The European SCALE project is presented. This project aims to develop, demonstrate, and assess a set of advanced CASE process-centered environments for improving the support of system composition strategies explicitly based on the planned and intensive reuse of components.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123948176","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-07-19DOI: 10.1109/CASE.1993.634826
C. Chee, S. S. Erdogan, S. Rahardja
Describes the features and design of SML, an integrated Software Module Library management system aimed at encouraging the reuse of software. SML aims at providing a user-friendly interface and an easy-to-use system in which software engineers can donate routines for use by other engineers, as well as retrieve software modules contributed by other engineers, resulting in improved productivity. To prevent user abuse, SML contains built-in checks using a credit facility to ensure that engineers contribute to SML besides merely retrieving from it. Security considerations in SML include access control checks to ensure that only authorized users can gain access to the system, and encryption facilities to prevent users from bypassing SML and directly accessing the routine library. Quality control is also enforced in SML through a decentralized user feedback mechanism, to maintain the high quality of routines contributed to the library.
{"title":"Software reusability with SML","authors":"C. Chee, S. S. Erdogan, S. Rahardja","doi":"10.1109/CASE.1993.634826","DOIUrl":"https://doi.org/10.1109/CASE.1993.634826","url":null,"abstract":"Describes the features and design of SML, an integrated Software Module Library management system aimed at encouraging the reuse of software. SML aims at providing a user-friendly interface and an easy-to-use system in which software engineers can donate routines for use by other engineers, as well as retrieve software modules contributed by other engineers, resulting in improved productivity. To prevent user abuse, SML contains built-in checks using a credit facility to ensure that engineers contribute to SML besides merely retrieving from it. Security considerations in SML include access control checks to ensure that only authorized users can gain access to the system, and encryption facilities to prevent users from bypassing SML and directly accessing the routine library. Quality control is also enforced in SML through a decentralized user feedback mechanism, to maintain the high quality of routines contributed to the library.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129361588","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-07-19DOI: 10.1109/CASE.1993.634780
H.C. Chan
Through examination of the processes involved in designing and using information systems that are heavily dependent on databases, it is shown that while the design of database models has been greatly assisted by CASE tools, the usage has been largely left out. Developers can design the database model at the conceptual level while CASE tools transform that into a model at the logical level for implementation. However, usage of the database demands that queries be written based on the logical level model. Developers and users cannot write queries based on the original conceptual level model. It is agreed that CASE tool developers and researchers should provide tools for people to effectively utilize data and information systems at the conceptual level.
{"title":"CASE: The vehicle for effective data utilization","authors":"H.C. Chan","doi":"10.1109/CASE.1993.634780","DOIUrl":"https://doi.org/10.1109/CASE.1993.634780","url":null,"abstract":"Through examination of the processes involved in designing and using information systems that are heavily dependent on databases, it is shown that while the design of database models has been greatly assisted by CASE tools, the usage has been largely left out. Developers can design the database model at the conceptual level while CASE tools transform that into a model at the logical level for implementation. However, usage of the database demands that queries be written based on the logical level model. Developers and users cannot write queries based on the original conceptual level model. It is agreed that CASE tool developers and researchers should provide tools for people to effectively utilize data and information systems at the conceptual level.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131002301","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-07-19DOI: 10.1109/CASE.1993.634805
S. Isoda, Shuichiro Yamamoto, H. Kuroki, A. Oka
Two experiments conducted to investigate how useful the CASE method (software development based on the structured methodology and supported by upper CASE tools) is and how it can be successfully introduced into software development organizations are described. In the first experiment, sample programs are developed by both the CASE and conventional methods to compare reliability of the developed programs and analysis/design improvement due to learning effect. In the second experiment, the CASE method is introduced and applied to actual software development. Two major conclusions were reached through these experiments: the CASE method enables twice as much program reliability as the conventional method does, and the success or failure of introducing the CASE method largely depends on management factors, especially on developers' maturity.
{"title":"Evaluation and introduction of the structured methodology and a CASE tool","authors":"S. Isoda, Shuichiro Yamamoto, H. Kuroki, A. Oka","doi":"10.1109/CASE.1993.634805","DOIUrl":"https://doi.org/10.1109/CASE.1993.634805","url":null,"abstract":"Two experiments conducted to investigate how useful the CASE method (software development based on the structured methodology and supported by upper CASE tools) is and how it can be successfully introduced into software development organizations are described. In the first experiment, sample programs are developed by both the CASE and conventional methods to compare reliability of the developed programs and analysis/design improvement due to learning effect. In the second experiment, the CASE method is introduced and applied to actual software development. Two major conclusions were reached through these experiments: the CASE method enables twice as much program reliability as the conventional method does, and the success or failure of introducing the CASE method largely depends on management factors, especially on developers' maturity.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131642634","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-07-19DOI: 10.1109/CASE.1993.634776
B. Bailer, K. Bauknecht, C. Schatzmann
In the fall of 1991, Swiss companies from all industries were asked to document their CASE experiences with a structured report. Thirteen accounts were published in 1992. Most companies are past the stage of experimentation with CASE. Some of them use CASE quite successfully on rather broad scale, while others do not seem to be able to apply CASE widely despite positive evaluations and test results. The main findings of these reports, some cautionary remarks, and a few recommendations for future CASE users are given.
{"title":"Ways to CASE: An analysis of selected CASE experiences","authors":"B. Bailer, K. Bauknecht, C. Schatzmann","doi":"10.1109/CASE.1993.634776","DOIUrl":"https://doi.org/10.1109/CASE.1993.634776","url":null,"abstract":"In the fall of 1991, Swiss companies from all industries were asked to document their CASE experiences with a structured report. Thirteen accounts were published in 1992. Most companies are past the stage of experimentation with CASE. Some of them use CASE quite successfully on rather broad scale, while others do not seem to be able to apply CASE widely despite positive evaluations and test results. The main findings of these reports, some cautionary remarks, and a few recommendations for future CASE users are given.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"65 4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123129273","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-07-19DOI: 10.1109/CASE.1993.634827
H.Y. Lee
The types of knowledge that are brought to bear at every stage of the software development life cycle are identified. However, some knowledge, though used, is lost when it is not captured explicitly or embedded within a software artifact. The knowledge encoded in a software artifact as software concepts can be reused. A model is proposed to illustrate the various dimensions of software reuse, namely component granularity, component origin and abstraction levels. This model is related to software reuse in CASE tools, and the degree of knowledge reuse is indicated.
{"title":"Software engineering knowledge for software reuse","authors":"H.Y. Lee","doi":"10.1109/CASE.1993.634827","DOIUrl":"https://doi.org/10.1109/CASE.1993.634827","url":null,"abstract":"The types of knowledge that are brought to bear at every stage of the software development life cycle are identified. However, some knowledge, though used, is lost when it is not captured explicitly or embedded within a software artifact. The knowledge encoded in a software artifact as software concepts can be reused. A model is proposed to illustrate the various dimensions of software reuse, namely component granularity, component origin and abstraction levels. This model is related to software reuse in CASE tools, and the degree of knowledge reuse is indicated.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121363511","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-07-19DOI: 10.1109/CASE.1993.634823
P. Layzell, M. Freeman
Software maintenance tools, which have evolved to include an emphasis on reuse, range from source code analyzers to semi-intelligent tools which seek to reconstruct system designs and specification documents from source code. It is clear, however, that relying solely upon source code as the basis for reverse engineering has many problems. These problems include poor abstraction, leading to overdetailed specification models and the inability to link other parts of a software system, such as documentation and user expertise, to the underlying code. This paper describes the work of the ESPRIT DOCKET project, which has developed a prototype environment to support the development of a system model linking the user-oriented business aspects of a system to operational code using a variety of knowledge source inputs (code, documents and user expertise). The aim is to provide a coherent model to form the basis for system understanding and to support the software change and evolution process.
{"title":"DOCKET: A CASE tool and method to support software system understanding and modification","authors":"P. Layzell, M. Freeman","doi":"10.1109/CASE.1993.634823","DOIUrl":"https://doi.org/10.1109/CASE.1993.634823","url":null,"abstract":"Software maintenance tools, which have evolved to include an emphasis on reuse, range from source code analyzers to semi-intelligent tools which seek to reconstruct system designs and specification documents from source code. It is clear, however, that relying solely upon source code as the basis for reverse engineering has many problems. These problems include poor abstraction, leading to overdetailed specification models and the inability to link other parts of a software system, such as documentation and user expertise, to the underlying code. This paper describes the work of the ESPRIT DOCKET project, which has developed a prototype environment to support the development of a system model linking the user-oriented business aspects of a system to operational code using a variety of knowledge source inputs (code, documents and user expertise). The aim is to provide a coherent model to form the basis for system understanding and to support the software change and evolution process.","PeriodicalId":442754,"journal":{"name":"Proceedings of 6th International Workshop on Computer-Aided Software Engineering","volume":"57 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1993-07-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131442134","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
扫码关注我们
求助内容：
应助结果提醒方式：