4 citations found. Retrieving documents...
Finkelstein, A. C. W., Finkelstein, L. and Maibaum, T. S. E. (1990) Engineering-In-The-Large: Software Engineering and Instrumentation, Proceedings, UK IT '90, pp 1-8, Peter Peregrinus.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Resolving Requirements Conflicts with Computer-Supported.. - Easterbrook (1993)   (5 citations)  (Correct)

....help with conflicting requirements. The demand for a single consistent specification means that 2 requirements conflicts are suppressed when the specification is written. Formal methods do not necessarily help, even though formal languages are intended to prevent ambiguity and inconsistency [Finkelstein, Finkelstein Maibaum 1990]. The ability to reason formally with specifications is a huge step towards detecting the presence of conflict, but carries the implication that inconsistencies are errors which must be eliminated. Methods developed to support formal specification reflect this philosophy, and miss the chance to ....

Finkelstein, A. C. W., Finkelstein, L. and Maibaum, T. S. E. (1990) Engineering-In-The-Large: Software Engineering and Instrumentation, Proceedings, UK IT '90, pp 1-8, Peter Peregrinus.


Elicitation of Requirements from Multiple Perspectives - Easterbrook (1991)   (17 citations)  (Correct)

....Most methodologies require a single consistent specification as a basis for a coherent design, which means that conflicts are suppressed when the specification is written. Formal methods do not necessarily help, even though formal languages are intended to prevent ambiguity and inconsistency [Finkelstein, Finkelstein Maibaum 1990]. The ability to formally reason with specifications is a huge step towards detecting the presence of conflict, but carries the implication that inconsistencies are errors which must be eliminated. Methods developed to support formal specification reflect this philosophy, and miss the chance to ....

....(e.g. Cunningham et al. 1985] and those that argue for a degree of informality in specifications (e.g. Balzer, Goldman Wile [1978] Plenty of reasons have been suggested for adopting formal specification languages, of which the most important is the level of precision they offer. Finkelstein, Finkelstein Maibaum [1990] discuss the advantages, suggesting that with a formal specification it should be possible: to eliminate ambiguity using the formal semantics; to test the specification for incompleteness and inconsistency; to formally verify a subsequent design or implementation; to trace back components of ....

Finkelstein, A. C. W., Finkelstein, L. and Maibaum, T. S. E., 1990, "Engineering-In-The-Large: Software Engineering and Instrumentation", Proceedings, UK IT '90, pp 1-8, Peter Peregrinus.


Handling Conflict Between Domain Descriptions With.. - Easterbrook (1991)   (27 citations)  (Correct)

....Most methodologies require a single consistent specification as a basis for a coherent design, which means that conflicts are suppressed when the specification is written. Formal methods do not necessarily help, even though formal languages are intended to prevent ambiguity and inconsistency [Finkelstein, Finkelstein Maibaum 1990]. The ability to formally reason with specifications is a huge step towards detecting the presence of conflict, but carries the implication that inconsistencies are errors which must be eliminated. Methods developed to support formal specification reflect this philosophy, and miss the chance to ....

Finkelstein, A. C. W., Finkelstein, L. and Maibaum, T. S. E. (1990) Engineering-In-The-Large: Software Engineering and Instrumentation, Proceedings, UK IT '90, pp 1-8, Peter Peregrinus.


Technology Transfer: Software Engineering and Engineering.. - Finkelstein, Nuseibeh (1992)   (1 citation)  Self-citation (Finkelstein)   (Correct)

....methods within the traditional engineering design process. There are clear similarities between the disciplines of software engineering and instrument design, yet enough differences to tempt the transfer of successful development techniques from either discipline to the other. The SEED project [Fink90] has systematically studied these similarities and differences in its attempt to transfer technology and expertise from one discipline to the other. Concurrently, an organisational framework for systems development methodologies has been constructed to describe, manage and apply the engineering ....

A. Finkelstein, T. Maibaum and L. Finkelstein, "Engineering-in-the-Large: Software Engineering and Instrumentation", Proceedings of UK IT 1990 Conference (IEE), Southampton, Conference Publication 316, pp.1-7, 19th-22nd March 1990.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC