“Users can work with analysts and object designers to formulate and tune system requirements. People from business, analytical and object design disciplines can come together, learn from each other and generate meaningful descriptions of systems that are to be built. Each participant and each project has slightly different concerns and needs. Practical application of use cases can go a long way to improve our ability to deliver just what the customer ordered.”

—  Rebecca Wirfs-Brock

About Conclusion
Designing scenarios: Making the case for a use case framework (1993)

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Users can work with analysts and object designers to formulate and tune system requirements. People from business, anal…" by Rebecca Wirfs-Brock?
Rebecca Wirfs-Brock photo
Rebecca Wirfs-Brock13
American software engineer 1953

Related quotes

Ed Yourdon photo

“Designed as a companion volume to the acclaimed Object-Oriented Analysis, this book focuses on the middle part of the software lifecycle: the activity of design. It shows readers how to apply object-oriented design, and how to tailor and expand the method to suit specific organization and project needs. Readers will explore the major issues in OOD; the role of OOD in the systems lifecycle; how to use graphical notation; strategies for creating design; and hints for evaluating the efficiency of a design created with OOD. For software engineers and other users undertaking real-world systems development projects and designing overall software architecture for systems will find this reference approach to improving systems design indispensable.”

Ed Yourdon (1944–2016) American software engineer and pioneer in the software engineering methodology

Abstract.
Object-oriented design (1991)

“The objective of the Computer-Aided Design Project is to evolve a machine systems which will permit the human designer and the computer to work together on creative design problems.”

Douglas T. Ross (1929–2007) American computer scientist

Source: Computer-Aided Design: A Statement of Objectives (1960), p. iii: Abstract.

“Experienced object designers explore the design space from many different angles. They refine ideas of how their system should respond while they are in the middle of building and discarding ideas about how their design should work. Getting a design to gel involves making assumptions, seeing how they play out, changing one’s mind or perspective slightly and re-iterating. Design is a difficult, involved task. It inherently is a non-linear process. Yet, we are asked to trace our design results back to system requirements. And, if we uncover some implications during design, we’d like to tune our system requirements to reflect necessary design compromises.”

Rebecca Wirfs-Brock (1953) American software engineer

Abstract
Designing scenarios: Making the case for a use case framework (1993)

Béla H. Bánáthy photo

“When it comes to the design of social and societal systems of all kinds, it is the users, the people in the system who are the experts. Nobody has the right to design social systems for someone else. It is unethical to do so. Design cannot be legislated, it should not be bought from the expert, and it should not be copied from the design of others. If the privilege of and responsibility for design is "given away," others will take charge of designing our lives and our systems. They will shape our future.”

Béla H. Bánáthy (1919–2003) Hungarian linguist and systems scientist

Source: Designing Social Systems in a Changing World (1996), p. 128; Cited in: Roberto Joseph et al. (2002) " Banathy's Influence on the Guidance System for Transforming Education http://www.indiana.edu/~syschang/decatur/reigeluth_pubs/documents/95_banathy_influence_on_gste.pdf". World Futures: The Journal of General Evolution, 58(5/6) 379-394

“Recently, I have had conversations with a number of people who were attempting their first object-oriented project. Most of these people claimed to be using “use cases” in their object-oriented analysis and design approaches. However, listening to them describe their projects, it became quite apparent to me that there is a great deal of confusion regarding the definition, context, and use of use cases. This confusion can (and often does) lead to poorly-designed systems.”

Edward V. Berard

Edward V. Berard (1996) " Be Careful With" Use Cases http://www.tao.com/pub/html/use_case.html" The Object Agency, Inc.

“Use cases, scenarios or scripts are roughly synonymous terms for important ways to focus our design activities. I prefer the term use case (although quickly saying it three times can leave your tongue tied) because it emphasizes usage. A use case is a textual description of a sequence of interactions between an actor (roughly corresponding to an external agent or class of users) and the system we are designing. Use cases were first described by Ivar Jacobson in his book “Object Oriented Software Engineering A Use Case Driven Approach.”
Use cases have been around in various forms for quite some time. Jacobson, however, made the keen observation that use cases can be treated as refineable, extensible and even reusable specifications of system requirements. We’ve had these same goals for object designs. We know that it is harder to actually accomplish them than it is to talk about them.”

Rebecca Wirfs-Brock (1953) American software engineer

About What is a Use Case?
Designing scenarios: Making the case for a use case framework (1993)

Stuart A. Umpleby photo

“Systems science is generally said to have emerged during and after World War II, although there were precursors to the basic ideas. The people who created each school of thought were working largely independently, although many of them knew each other. They came from different disciplines, they were working on different problems, they formulated different variations of the principles of systems and cybernetics, and they often chose to affiliate with different academic societies.”

Stuart A. Umpleby (1944) American scientist

Source: "The origins and purposes of several traditions in systems theory and cybernetics," 1999, p. 79: Introduction

A. Wayne Wymore photo

“[In the year 1957] I have just returned from an exciting meeting of the American Society for Engineering Education where I heard a paper on the new discipline of systems engineering. It is no longer sufficient for engineers merely to design boxes such as computers with the expectation that they would become components of larger, more complex systems. That is wasteful because frequently the box component is a bad fit in the system and has to be redesigned or worse, can lead to system failure. We must learn how to design large-scale, complex systems from the top down so that the specification for each component is derivable from the requirements for the overall system. We must also take a much larger view of systems. We must design the man-machine interfaces and even the system-society interfaces. Systems engineers must be trained for the design of large-scale, complex, man-machine-social systems.”

A. Wayne Wymore (1927–2011) American mathematician

Systems Movement: Autobiographical Retrospectives (2004)

August-Wilhelm Scheer photo

“Business information systems can be either designed as custom applications or purchased as off-the-shelf standard solutions. The development of custom applications is generally expensive and is often plagued by uncertainties, such as the selection of appropriate development tools, the duration of the development cycle, or the difficulties involved in assessing costs. Thus, empirical surveys have shown that between half to two-thirds of information systems projects fail. The current tendency to shift from individual development to standardized, prepackaged software solutions is therefore not surprising.”

August-Wilhelm Scheer (1941) German business theorist

August-Wilhelm Scheer, and Frank Habermann. " Enterprise resource planning: making ERP a success http://ecis.seattleu.edu/courses/ecis464spring04/Articles/Making%20ERP%20a%20Success.pdf." Communications of the ACM 43.4 (2000): 57-61.

“It is conceivable that we might be able to provide good medical care for everyone needing it, in a new system designed to assure equity, provided we can restrain ourselves, or our computers, from designing a system in which all 200 million of us are assumed to be in constant peril of failed health every day of our lives. In the same sense that our judicial system presumes us to be innocent until proven guilty, a medical care system may work best if it starts with the presumption that most people are healthy. Left to themselves, computers may try to do it in the opposite way, taking it as given that some sort of direct, continual, professional intervention is required all the time, in order to maintain the health of each citizen, and we will end up spending all our money on nothing but this.”

Lewis Thomas (1913–1993) American physician, poet and educator

Source: Aspects of Biomedical Science Policy (1972), p. 4

Related topics