• Summary
• Related Documents
  • Active Bibliography
  • Co-citation
• Version History

Abstract:

This paper is mainly based on the work done in the ESPRIT project ECIP2, Ref. #2072, on high-level system specification [LEB91, MUE90]. The goal within this work was first to enlighten the main streams and activities during the very early phases of contract-oriented high-level system design and specification. Second, based on the first evaluation, the applicability of the IEEE standard hardware description language VHDL should be studied. In this paper I will only concentrate on the first topic and on applicable standards. 1 High-Level System Design & Specification System engineering should include all life cycle activities, like specification, design, implementation, and support of systems, where systems may include hardware as well as software components. It is important not to limit systems engineering to the technical domain, such as physical, mechanical, and electrical engineering but to consider the logistic, and the contractual view as well. Contractual view means to consider all contractual constraints, such as limits on budget as well as the flow of deliverables and reports through the entire system development. High-Level design & specification, which is also often referred to as requirement engineering, covers the very first phases of systems engineering. The major input is the customer requirement specification. The major output is first a specification (Customer External Specification) delivered to the external customer indicating all adequate design alternatives. Second, the already executable engineering specification of the design alternative finally chosen is passed to the further design synthesis to be implemented and manufactured. In the following I would like to sketch the main stream and the main ideas of the contractoriented high-level system design & specification process such as it was defined within ECIP2

Citations