Author of the publication

The case for dumb requirements engineering tools

, , , and . Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ), (2012)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

 

Other publications of authors with the same name

Community building as an effective user engagement strategy: A case study in academic libraries., , , , and . J. Assoc. Inf. Sci. Technol., 71 (2): 208-220 (2020)Domain system statecharts: The good, the bad, and the ugly, , , and . (2006)Unified use case statecharts: case studies, , , and . Requirements Engineering, 12 (4): 245--264 (October 2007)The case for dumb requirements engineering tools, , , and . Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ), (2012)Specification and Prototyping: Some Thoughts on Why They Are Successful., and . TAPSOFT, Vol.2, volume 186 of Lecture Notes in Computer Science, page 117-128. Springer, (1985)The prevalence and severity of persistent ambiguity in software requirements specifications: Is a special effort needed to find them?, and . Sci. Comput. Program., (2020)On the time required for retention., , , , and . HLLCA, page 165-178. ACM, (1973)Downsizing EPMcreate to Lighter Creativity Techniques for Requirements Elicitation., , and . REFSQ Workshops, volume 1796 of CEUR Workshop Proceedings, CEUR-WS.org, (2017)Deriving a Compiler From an Operational Semantics Written in VDL., and . Comput. Lang., 10 (2): 147-164 (1985)The Use of a Module Interconnection Specification Capability in the SARA System Design Methodology., and . ICSE, page 294-307. IEEE Computer Society, (1979)