Pub Date : 1997-07-14DOI: 10.1109/STEP.1997.615493
J. Wortmann, I. Claßen, G. Klawitter
This experience report documents the results of the project "Data Modelling for Advanced Flight Data Management" of the research group "Computergestutze Informotionssysteme" at Technische Universitat Berlin and the Eurocontrol Experimental Centre (EEC) Bretigny-sur-Orge France. A combination of classic object-oriented approaches, such as OMT, the Booch method and Jacobson's use case driven approach have bean combined for the creation of an analysis model, describing sector handover procedures in the context of Air Traffic Control (ATC). Due to the complex dynamic properties of ATC systems, Message Sequence Charts (MSC) and statecharts, have been used within this project for requirements analysis, although they are usually considered as design related.
{"title":"Object-oriented requirements analysis for air traffic control systems","authors":"J. Wortmann, I. Claßen, G. Klawitter","doi":"10.1109/STEP.1997.615493","DOIUrl":"https://doi.org/10.1109/STEP.1997.615493","url":null,"abstract":"This experience report documents the results of the project \"Data Modelling for Advanced Flight Data Management\" of the research group \"Computergestutze Informotionssysteme\" at Technische Universitat Berlin and the Eurocontrol Experimental Centre (EEC) Bretigny-sur-Orge France. A combination of classic object-oriented approaches, such as OMT, the Booch method and Jacobson's use case driven approach have bean combined for the creation of an analysis model, describing sector handover procedures in the context of Air Traffic Control (ATC). Due to the complex dynamic properties of ATC systems, Message Sequence Charts (MSC) and statecharts, have been used within this project for requirements analysis, although they are usually considered as design related.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"79745721","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 : 1997-07-14DOI: 10.1109/STEP.1997.615506
A. Brown
Established CASE vendors face a number of major challenges in upgrading their product lines to support the development and maintenance of large-scale distributed, web-based applications. This paper describes the characteristics of future applications, examines the challenges they pose to established CASE vendors, and suggests activities within the software research community that can help to address these challenges. As a result, the main contributions of the paper include a vision of how CASE products will evolve as we enter the 21st Century, and an analysis of the problems that will need to be overcome by established CASE vendors to realize that vision.
{"title":"CASE in the 21st Century: challenges facing existing CASE vendors","authors":"A. Brown","doi":"10.1109/STEP.1997.615506","DOIUrl":"https://doi.org/10.1109/STEP.1997.615506","url":null,"abstract":"Established CASE vendors face a number of major challenges in upgrading their product lines to support the development and maintenance of large-scale distributed, web-based applications. This paper describes the characteristics of future applications, examines the challenges they pose to established CASE vendors, and suggests activities within the software research community that can help to address these challenges. As a result, the main contributions of the paper include a vision of how CASE products will evolve as we enter the 21st Century, and an analysis of the problems that will need to be overcome by established CASE vendors to realize that vision.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"91122990","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 : 1997-07-14DOI: 10.1109/STEP.1997.615479
J. Han
Impact analysis and change propagation are among the major issues of software change management. In this paper, we introduce an approach to providing impact analysis and change propagation support as an integral part of software engineering environments, so that they can be applied during both software development and maintenance. In this approach, the activities are carried out on the original representation of software artifacts in the environment, rather than on a separate system model extracted. This very fact enables automated direct support for the process of actually carrying out and propagating the changes. Dependences and properties of software artifacts are used for impact analysis to achieve increased flexibility and expressiveness. Both impact analysis and change propagation are a combination of guided user intervention and automatic processing based on codified change patterns and propagation rules.
{"title":"Supporting impact analysis and change propagation in software engineering environments","authors":"J. Han","doi":"10.1109/STEP.1997.615479","DOIUrl":"https://doi.org/10.1109/STEP.1997.615479","url":null,"abstract":"Impact analysis and change propagation are among the major issues of software change management. In this paper, we introduce an approach to providing impact analysis and change propagation support as an integral part of software engineering environments, so that they can be applied during both software development and maintenance. In this approach, the activities are carried out on the original representation of software artifacts in the environment, rather than on a separate system model extracted. This very fact enables automated direct support for the process of actually carrying out and propagating the changes. Dependences and properties of software artifacts are used for impact analysis to achieve increased flexibility and expressiveness. Both impact analysis and change propagation are a combination of guided user intervention and automatic processing based on codified change patterns and propagation rules.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"84823092","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 : 1997-07-14DOI: 10.1109/STEP.1997.615466
L. Krzanik, Jouni Similä
Incremental delivery policies for software process improvement are anxiously required by the industry. Improvement projects need to show results as early as possible to capture the attention of the organization and to keep things focused on process improvement. Incremental policies are the foundation of building a provider-reset partnership in software process improvement. Few guidelines, if any, explicitly support such an approach. The authors examine a general approach to incremental software process improvement deployment, and investigate a method for verifying the suitability of conventional models of software process improvement for incremental improvement deployment. They present a framework including the necessary models, an evaluation method and support tools.
{"title":"Is my software process improvement suitable for incremental deployment?","authors":"L. Krzanik, Jouni Similä","doi":"10.1109/STEP.1997.615466","DOIUrl":"https://doi.org/10.1109/STEP.1997.615466","url":null,"abstract":"Incremental delivery policies for software process improvement are anxiously required by the industry. Improvement projects need to show results as early as possible to capture the attention of the organization and to keep things focused on process improvement. Incremental policies are the foundation of building a provider-reset partnership in software process improvement. Few guidelines, if any, explicitly support such an approach. The authors examine a general approach to incremental software process improvement deployment, and investigate a method for verifying the suitability of conventional models of software process improvement for incremental improvement deployment. They present a framework including the necessary models, an evaluation method and support tools.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89981319","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 : 1997-07-14DOI: 10.1109/STEP.1997.615460
S. Kokkots, C. Spyropoulos
Presents a modular architecture for designing internationalized software, called ISDA-i (Internationalized Software Design Architecture). This architecture successfully combines the user requirements for highly personalized applications with the developer requirements for easily maintained, reusable software components incorporating high localization potential. It enlarges the reusable software libraries and minimizes the size of the program core. All the configurable components of a software application are systematically stored in external configuration and resource files, which a system administrator or end-user may edit in order to modify its appearance and behavior.
{"title":"An architecture for designing internationalized software","authors":"S. Kokkots, C. Spyropoulos","doi":"10.1109/STEP.1997.615460","DOIUrl":"https://doi.org/10.1109/STEP.1997.615460","url":null,"abstract":"Presents a modular architecture for designing internationalized software, called ISDA-i (Internationalized Software Design Architecture). This architecture successfully combines the user requirements for highly personalized applications with the developer requirements for easily maintained, reusable software components incorporating high localization potential. It enlarges the reusable software libraries and minimizes the size of the program core. All the configurable components of a software application are systematically stored in external configuration and resource files, which a system administrator or end-user may edit in order to modify its appearance and behavior.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"73039662","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 : 1997-07-14DOI: 10.1109/STEP.1997.615473
M. Snoeck, G. Dedene
Model-driven development finds its origin in a reframed version of Zachman's (1987) Information Systems Architecture. This framework recognises levels of abstraction, which is not the same as levels of detail, in the systems development process. If the model-driven approach is applied in addition to object oriented analysis concepts, significant benefits are to be expected on the side of maintenance cost. Indeed, one of the main benefits of the model-driven development process is the perfect modular structure of the developed systems. This facilitates maintenance dramatically. However, in order to prove such a statement it is necessary to wait until sufficient experience is gained in the maintenance of systems developed according to this approach. M.E.R.O.DE. is an object oriented development based on two principles: model-driven development and specification by contract. The method was developed around 1988 and has been used by customers since 1991. The paper presents the result of a small scale and informal inquiry amongst the M.E.R.O.DE, users. As many systems they developed have been subject of maintenance, their experiences should allow one to asses or reject the hypothesis that model-driven development facilitates maintenance dramatically. Although the results presented pertain to one particular method, the model-driven approach can be adopted by users of any object oriented analysis method.
{"title":"Experiences with object oriented model-driven development","authors":"M. Snoeck, G. Dedene","doi":"10.1109/STEP.1997.615473","DOIUrl":"https://doi.org/10.1109/STEP.1997.615473","url":null,"abstract":"Model-driven development finds its origin in a reframed version of Zachman's (1987) Information Systems Architecture. This framework recognises levels of abstraction, which is not the same as levels of detail, in the systems development process. If the model-driven approach is applied in addition to object oriented analysis concepts, significant benefits are to be expected on the side of maintenance cost. Indeed, one of the main benefits of the model-driven development process is the perfect modular structure of the developed systems. This facilitates maintenance dramatically. However, in order to prove such a statement it is necessary to wait until sufficient experience is gained in the maintenance of systems developed according to this approach. M.E.R.O.DE. is an object oriented development based on two principles: model-driven development and specification by contract. The method was developed around 1988 and has been used by customers since 1991. The paper presents the result of a small scale and informal inquiry amongst the M.E.R.O.DE, users. As many systems they developed have been subject of maintenance, their experiences should allow one to asses or reject the hypothesis that model-driven development facilitates maintenance dramatically. Although the results presented pertain to one particular method, the model-driven approach can be adopted by users of any object oriented analysis method.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"73764060","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 : 1997-07-14DOI: 10.1109/STEP.1997.615476
V. Nanda, S. Lemire
This paper describes a practical, methodical and substantive approach to setting up the essentials of a process management infrastructure in an organization. The paper discusses the key elements of a process management infrastructure, as being implemented in an ongoing process improvement program at Ericsson. The catalysts for this improvement effort were: management need, customer demand, process capability assessments and competitive pressure.
{"title":"A methodical approach to establishing a process management infrastructure in an organization","authors":"V. Nanda, S. Lemire","doi":"10.1109/STEP.1997.615476","DOIUrl":"https://doi.org/10.1109/STEP.1997.615476","url":null,"abstract":"This paper describes a practical, methodical and substantive approach to setting up the essentials of a process management infrastructure in an organization. The paper discusses the key elements of a process management infrastructure, as being implemented in an ongoing process improvement program at Ericsson. The catalysts for this improvement effort were: management need, customer demand, process capability assessments and competitive pressure.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"85212401","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 : 1997-07-14DOI: 10.1109/STEP.1997.615465
R. Clark, A. Moreira
The rigorous object-oriented analysis (ROOA) method provides a systematic development process which, starting from a set of informal requirements, produces an executable object-oriented analysis model. The model is expressed in LOTOS and provides a precise and unambiguous formal requirements specification of the static, dynamic and functional aspects of a problem. There is, however, a wide gap between informal requirements and a formal specification. To help bridge this gap, the authors propose that a formal and executable model which specifies behaviour in terms of what the environment expects from the system should be constructed initially. This user-centred model will give very early feedback to the requirements capture process and can be used as a step in the construction of the ROOA model. Both models are expressed in the same executable formal language and so they can be composed to verify that the ROOA model is compatible with the user-centred model and the composition executed to validate it with respect to the requirements.
{"title":"Constructing formal specifications from informal requirements","authors":"R. Clark, A. Moreira","doi":"10.1109/STEP.1997.615465","DOIUrl":"https://doi.org/10.1109/STEP.1997.615465","url":null,"abstract":"The rigorous object-oriented analysis (ROOA) method provides a systematic development process which, starting from a set of informal requirements, produces an executable object-oriented analysis model. The model is expressed in LOTOS and provides a precise and unambiguous formal requirements specification of the static, dynamic and functional aspects of a problem. There is, however, a wide gap between informal requirements and a formal specification. To help bridge this gap, the authors propose that a formal and executable model which specifies behaviour in terms of what the environment expects from the system should be constructed initially. This user-centred model will give very early feedback to the requirements capture process and can be used as a step in the construction of the ROOA model. Both models are expressed in the same executable formal language and so they can be composed to verify that the ROOA model is compatible with the user-centred model and the composition executed to validate it with respect to the requirements.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"88923486","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 : 1997-07-14DOI: 10.1109/STEP.1997.615564
S. Bechhofer, C. Goble, A. Rector, W. Solomon, W. Nowlan
Terminologies, or constrained vocabularies, are a potentially rich means of representing the metadata required for applications that have partially structured and incomplete dynamic data to describe, and exploratory and inexact queries to express. Such applications include digital libraries and multimedia repositories and software management; specific application communities include medicine and art. The authors propose that terminologies are ideal for meeting today's information requirements and that a dynamic terminology service is the appropriate architectural approach. They present the requirements of a terminology server, and describe the implementation and practical use of one developed by the authors that uses a description logic, GRAIL, to represent the terms. The terminology server has been extensively used in applications relating to medicine and is being used in the integration of diverse information sources for molecular biology.
{"title":"Terminologies and terminology servers for information environments","authors":"S. Bechhofer, C. Goble, A. Rector, W. Solomon, W. Nowlan","doi":"10.1109/STEP.1997.615564","DOIUrl":"https://doi.org/10.1109/STEP.1997.615564","url":null,"abstract":"Terminologies, or constrained vocabularies, are a potentially rich means of representing the metadata required for applications that have partially structured and incomplete dynamic data to describe, and exploratory and inexact queries to express. Such applications include digital libraries and multimedia repositories and software management; specific application communities include medicine and art. The authors propose that terminologies are ideal for meeting today's information requirements and that a dynamic terminology service is the appropriate architectural approach. They present the requirements of a terminology server, and describe the implementation and practical use of one developed by the authors that uses a description logic, GRAIL, to represent the terms. The terminology server has been extensively used in applications relating to medicine and is being used in the integration of diverse information sources for molecular biology.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89260365","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 : 1997-07-14DOI: 10.1109/STEP.1997.615463
H. Yang, W. Chu, Y. Sun
Transformation and reuse techniques have been discussed for many years, and it is even more important to apply these techniques in practice. This paper introduces our approach to combining transformation and semantic interface analysis for reuse of COBOL programs. In our approach, COBOL programs are reverse engineered to their designs represented in entity-relationship (ER) diagrams. Both the original code and obtained ER diagrams are used by semantic interface analysis. Reusable components are annotated with conditions which are needed for checking suitability and are saved in a reuse library for reuse and reengineering. Our method is demonstrated in detail through an example in this paper. Besides being practical, the advantages of the approach include the fact that a formal link between the original COBOL program and its design in an ER diagram form is retained, and both the program code and the design can be reused.
{"title":"A practical system of COBOL program reuse for reengineering","authors":"H. Yang, W. Chu, Y. Sun","doi":"10.1109/STEP.1997.615463","DOIUrl":"https://doi.org/10.1109/STEP.1997.615463","url":null,"abstract":"Transformation and reuse techniques have been discussed for many years, and it is even more important to apply these techniques in practice. This paper introduces our approach to combining transformation and semantic interface analysis for reuse of COBOL programs. In our approach, COBOL programs are reverse engineered to their designs represented in entity-relationship (ER) diagrams. Both the original code and obtained ER diagrams are used by semantic interface analysis. Reusable components are annotated with conditions which are needed for checking suitability and are saved in a reuse library for reuse and reengineering. Our method is demonstrated in detail through an example in this paper. Besides being practical, the advantages of the approach include the fact that a formal link between the original COBOL program and its design in an ER diagram form is retained, and both the program code and the design can be reused.","PeriodicalId":68622,"journal":{"name":"软件","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"1997-07-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"81297594","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
扫码关注我们
求助内容：
应助结果提醒方式：