Balzer R.: Tolerating inconsistency. Proc. 13th International Conference on Software Engineering, Austin Texas, 158165  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... and different types of styles (text, graphic, formula, notations) Since formal requirements are built out of non formal, the acquisition process must allow many freedoms (incompleteness, inconsistency, redundancy, ambiguity, different levels of abstraction, heterogeneous forms of expressions [Balzer 1991, Feather Fickas 1991] Only a few existing systems support the process of the transition between formal and nonformal requirements and offer parts of the necessary freedom (e.g. KATE [Fickas 1987] Requirements Apprentice [Reubenstein Waters 1991] However, they neither represent non formal ....

Balzer R.: Tolerating inconsistency. Proc. 13th International Conference on Software Engineering, Austin Texas, 158165

....have been published only in conference or workshop versions. There may be parts of the other Inscape papers (ICSE9 [15] ICSE11 [17] and TAV3 [18] included as well all of which have been published only in conference versions. 2 1. Introduction In his paper Tolerating Inconsistency [2], Balzer stated that Instead of treating inconsistency informally (i.e. outside the system) or as hard constraints, formalisms are needed for spotting such violations, treating them as problems, organizing resources to resolve them, recognizing when this has occurred, and limiting access to the ....

Robert Balzer. `Tolerating Insconsistency", 13th International Conference on Software Engineering, May 1991, Austin Tx.

No context found.

Balzer R.: Tolerating inconsistency. Proc. 13th International Conference on Software Engineering, Austin Texas, 158-165

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