Pub Date : 1994-05-24DOI: 10.1109/ECBS.1994.331667
D. Dalcher
As forensic engineering is generally being recognised as a step in the right direction for ECBS, we consider the future progress of our march. Is it feasible to try and identify a general direction at this stage? Are the ideas outrageous enough to generate further discussion?.<>
{"title":"Working group presentation: forensic ECBS-looking forward","authors":"D. Dalcher","doi":"10.1109/ECBS.1994.331667","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331667","url":null,"abstract":"As forensic engineering is generally being recognised as a step in the right direction for ECBS, we consider the future progress of our march. Is it feasible to try and identify a general direction at this stage? Are the ideas outrageous enough to generate further discussion?.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116582392","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331675
B. Lennartsson, N. Shahmehri, S. Bonnier
Presents experiences from modelling real-time applications in the declarative functional language H, developed hand-in-hand with a novel parallel graph reduction architecture called rp8601, both designed with the requirements of real-time embedded systems in mind. In rp8601, the analogue and digital interactions with the environment have been designed into the chips and into the language, and so have mechanisms to handle time constraints. Traditionally, declarative programming means that the programmer need not be aware of the processor operations. Instead, he can focus on the abstract relations between the input and output streams. The specific real-time requirements have normally not been taken into account in the declarative view. Our conclusion is that declarative functional programming is a viable technique for the development of complex software for embedded real-time systems. However, considerable efforts have to be spent on educating and training the application programmers in the new programming paradigm.<>
{"title":"On exploiting declarative programming and parallel execution in computer based real-time systems","authors":"B. Lennartsson, N. Shahmehri, S. Bonnier","doi":"10.1109/ECBS.1994.331675","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331675","url":null,"abstract":"Presents experiences from modelling real-time applications in the declarative functional language H, developed hand-in-hand with a novel parallel graph reduction architecture called rp8601, both designed with the requirements of real-time embedded systems in mind. In rp8601, the analogue and digital interactions with the environment have been designed into the chips and into the language, and so have mechanisms to handle time constraints. Traditionally, declarative programming means that the programmer need not be aware of the processor operations. Instead, he can focus on the abstract relations between the input and output streams. The specific real-time requirements have normally not been taken into account in the declarative view. Our conclusion is that declarative functional programming is a viable technique for the development of complex software for embedded real-time systems. However, considerable efforts have to be spent on educating and training the application programmers in the new programming paradigm.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"151 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116413295","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331668
M. Voss
An ECBS Task Force activity of prime importance is the case study initiative. We report on its history and conceptual deficits and summarize the results of the Stockholm Workshop working group sessions about that topic.<>
{"title":"Working group report-ECBS case study","authors":"M. Voss","doi":"10.1109/ECBS.1994.331668","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331668","url":null,"abstract":"An ECBS Task Force activity of prime importance is the case study initiative. We report on its history and conceptual deficits and summarize the results of the Stockholm Workshop working group sessions about that topic.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130361370","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331685
K. Jackson
For any computer based system development to be successful, it is necessary that certain information is created and recorded. The ECBS information model described here represents the sum of the information which must be generated and/or collected during the life of any project to develop a computer based system. The basis for selecting the information was to adopt the attitude of a technical auditor in asking the question: "What information would I expect to find recorded in a project's files ?". The paper places this information in the context of a process model used to develop such systems within a project development organisation.<>
{"title":"An information model for computer based systems","authors":"K. Jackson","doi":"10.1109/ECBS.1994.331685","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331685","url":null,"abstract":"For any computer based system development to be successful, it is necessary that certain information is created and recorded. The ECBS information model described here represents the sum of the information which must be generated and/or collected during the life of any project to develop a computer based system. The basis for selecting the information was to adopt the attitude of a technical auditor in asking the question: \"What information would I expect to find recorded in a project's files ?\". The paper places this information in the context of a process model used to develop such systems within a project development organisation.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"76 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114645721","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331677
N. Karangelen, N. Hoang
The cost and schedule time expended to design and develop modern computer-based systems has grown dramatically over the past decade. Advanced system engineering development methods and automation techniques are required to manage the complexity inherent in the design of large, complex computer-based systems and to provide an efficient mechanism for evaluating various design options. Simulation-based design (SBD) is a system design approach centered upon the creation of virtual system prototypes and virtual environments within an integrated system design capture and simulation framework. A methodology is presented in this paper which supports SBD for complex real-time computer-based systems including: (1) a multi-domain approach to capturing system design information and (2) a mechanism for simulation of the conceptual, functional and implementation aspects of the design as captured. Finally, selected opportunities for automation support of the SBD approach are discussed.<>
{"title":"Simulation based design for large complex computer based systems","authors":"N. Karangelen, N. Hoang","doi":"10.1109/ECBS.1994.331677","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331677","url":null,"abstract":"The cost and schedule time expended to design and develop modern computer-based systems has grown dramatically over the past decade. Advanced system engineering development methods and automation techniques are required to manage the complexity inherent in the design of large, complex computer-based systems and to provide an efficient mechanism for evaluating various design options. Simulation-based design (SBD) is a system design approach centered upon the creation of virtual system prototypes and virtual environments within an integrated system design capture and simulation framework. A methodology is presented in this paper which supports SBD for complex real-time computer-based systems including: (1) a multi-domain approach to capturing system design information and (2) a mechanism for simulation of the conceptual, functional and implementation aspects of the design as captured. Finally, selected opportunities for automation support of the SBD approach are discussed.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121989773","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331671
D. Dalcher
Software development efforts are characterised by; project failures, runaway projects and integration and communication problems. Analysing why some projects finish on target while others lose track of their original objectives, constraints and milestones, can only be viewed as a long term investment. The study of failures is a sensible approach for utilising past experience and advancing to the next level of maturity. This paper introduces the discipline of forensic engineering and frames it within the ECBS environment. The value of failure analysis is discussed from a number of viewpoints. This paper calls for a new attitude towards failure, where in order to maximise potential learning, acceptance of failure is the new order of the day.<>
{"title":"Falling down is still part of growing up-success, failure and forensic ECBS","authors":"D. Dalcher","doi":"10.1109/ECBS.1994.331671","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331671","url":null,"abstract":"Software development efforts are characterised by; project failures, runaway projects and integration and communication problems. Analysing why some projects finish on target while others lose track of their original objectives, constraints and milestones, can only be viewed as a long term investment. The study of failures is a sensible approach for utilising past experience and advancing to the next level of maturity. This paper introduces the discipline of forensic engineering and frames it within the ECBS environment. The value of failure analysis is discussed from a number of viewpoints. This paper calls for a new attitude towards failure, where in order to maximise potential learning, acceptance of failure is the new order of the day.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"115 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125571347","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331666
D. Dalcher
The case study presented introduces the background to the development of the Nimrod AEW (Airborne Early Warning System) and its eventual demise. The Nimrod programme represents the largest development effort of its time. In the context of forensic ECBS, it represents a classical catalogue of failures.<>
{"title":"The Nimrod AEW flies again; a procurement case study","authors":"D. Dalcher","doi":"10.1109/ECBS.1994.331666","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331666","url":null,"abstract":"The case study presented introduces the background to the development of the Nimrod AEW (Airborne Early Warning System) and its eventual demise. The Nimrod programme represents the largest development effort of its time. In the context of forensic ECBS, it represents a classical catalogue of failures.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"96 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125711396","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331670
H. Lawson, W. Rossak, H. Simpson
Starting with the See-Saw and Problem Solving diagrams (H. Lawson, 1994), a useful definition of the major constituents of architecture for computer-based systems engineering, was made. This definition extends previous results. A first evaluation of the definition was based upon examining the properties of the British Aerospace DORIS approach as presented by H.R. Simpson (1994).<>
{"title":"Working group report-CBS architecture","authors":"H. Lawson, W. Rossak, H. Simpson","doi":"10.1109/ECBS.1994.331670","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331670","url":null,"abstract":"Starting with the See-Saw and Problem Solving diagrams (H. Lawson, 1994), a useful definition of the major constituents of architecture for computer-based systems engineering, was made. This definition extends previous results. A first evaluation of the definition was based upon examining the properties of the British Aerospace DORIS approach as presented by H.R. Simpson (1994).<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"60 5","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114040532","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331686
S. White
Several members of the IEEE Computer Society Task Force on Engineering of Computer Based Systems (ECBS) worked together to identify the state of practice in ECBS. Findings were documented in a paper titled "Systems Engineering of Computer-Based Systems," published in IEEE Computer, Nov., p.54-65 (1993). Problems identified by the group that were not covered in that paper are discussed here.<>
{"title":"Problems in engineering computer-based systems","authors":"S. White","doi":"10.1109/ECBS.1994.331686","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331686","url":null,"abstract":"Several members of the IEEE Computer Society Task Force on Engineering of Computer Based Systems (ECBS) worked together to identify the state of practice in ECBS. Findings were documented in a paper titled \"Systems Engineering of Computer-Based Systems,\" published in IEEE Computer, Nov., p.54-65 (1993). Problems identified by the group that were not covered in that paper are discussed here.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"125 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115426277","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 : 1994-05-24DOI: 10.1109/ECBS.1994.331679
T. Kramer, M.K. Senehi, J. Michaloski, S. Ray, W. Rippey, S.E. Wallace, R. Quintero, J. Albus
Presents a reference architecture for the control of mechanical systems. The architecture, called the "Joint Architecture", is derived in part from existing real-time control systems and manufacturing systems integration architectures at the National Institute of Standards and Technology. The Joint Architecture is under development and not yet complete. It is a hierarchical control architecture and focuses on the control of systems for manufacturing discrete parts by machining. A definition of "architecture" has been adopted which includes explicit levels of abstraction, termed "tiers of architectural definition", and five elements of architectural definition: (i) statement of scope and purpose, (ii) domain analyses, (iii) architectural specification, (iv) methodology for architectural development, and (v) conformance criteria. This paper gives an overview of the Joint Architecture and describes its two most abstract tiers.<>
{"title":"A reference architecture for control of mechanical systems","authors":"T. Kramer, M.K. Senehi, J. Michaloski, S. Ray, W. Rippey, S.E. Wallace, R. Quintero, J. Albus","doi":"10.1109/ECBS.1994.331679","DOIUrl":"https://doi.org/10.1109/ECBS.1994.331679","url":null,"abstract":"Presents a reference architecture for the control of mechanical systems. The architecture, called the \"Joint Architecture\", is derived in part from existing real-time control systems and manufacturing systems integration architectures at the National Institute of Standards and Technology. The Joint Architecture is under development and not yet complete. It is a hierarchical control architecture and focuses on the control of systems for manufacturing discrete parts by machining. A definition of \"architecture\" has been adopted which includes explicit levels of abstraction, termed \"tiers of architectural definition\", and five elements of architectural definition: (i) statement of scope and purpose, (ii) domain analyses, (iii) architectural specification, (iv) methodology for architectural development, and (v) conformance criteria. This paper gives an overview of the Joint Architecture and describes its two most abstract tiers.<<ETX>>","PeriodicalId":184633,"journal":{"name":"Proceedings 1994 Tutorial and Workshop on Systems Engineering of Computer-Based Systems","volume":"71 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1994-05-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127165331","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
扫码关注我们
求助内容：
应助结果提醒方式：