Women Authors From The United States

"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."

"The key books about object-oriented graphical modeling languages appeared between 1988 and 1992. Leading figures included Grady Booch [Booch,OOAD]; Peter Coad [Coad, OOA], [Coad, OOD]; Ivar Jacobson (Objectory) [Jacobson, OOSE]; Jim Odell [Odell]; Jim Rumbaugh (OMT) [Rumbaugh, insights], [Rumbaugh, OMT]; Sally Shlaer and Steve Mellor [Shlaer and Mellor, data], [Shlaer and Mellor, states] ; and Rebecca Wirfs-Brock (Responsibility Driven Design) [Wirfs-Brock]."

"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."

"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."

"The goal of is to improve encapsulation. It does so by viewing a program in terms of the client/server model."

"is inspired by the client/server model. It focuses on the contract by asking:"

"Object-oriented programming increases the value of these metrics by managing this complexity. The most effective tool available for dealing with complexity is abstraction. Many types of abstraction can be used, but encapsulation is the main form of abstraction by which complexity is managed in object-oriented programming. Programming in an object-oriented language, however, does not ensure that the complexity of an application will be well encapsulated. Applying good programming techniques can improve encapsulation, but the full benefit of object-oriented programming can be realized only if encapsulation is a recognized goal of the design process."

"A subsystem is a set of classes (and possibly other subsystems) collaborating to fulfill a set of responsibilities. Although subsystems do not exist as the software executes, they are useful conceptual entities."

"Object-oriented programming languages support encapsulation, thereby improving the ability of software to be reused, refined, tested, maintained, and extended. The full benefit of this support can only be realized if encapsulation is maximized during the design process. We argue that design practices which take a data-driven approach fail to maximize encapsulation because they focus too quickly on the implementation of objects. We propose an alternative object-oriented design method which takes a responsibility-driven approach. We show how such an approach can increase the encapsulation by deferring implementation issues until a later stage."

"Responsibility-driven design specifies object behavior before object structure and other implementation considerations are determined. We have found that it minimizes the rework required for major design changes."

"A conceptual level view of an object design describes the key abstractions. While someone might think of key abstractions as being nothing more or nothing less than high-level descriptions of "candidate classes", I prefer to consider a conceptual design from a slightly different angle--I'm thinking about design at a slightly different level. An object-oriented application is a set of interacting objects. Each object is an implementation of one or more roles. A role supports a set of related (cohesive) responsibilities. A responsibility is an obligation to perform a task or know certain information. And objects don't work in isolation, they collaborate with others in a community to perform the overall responsibilities of the application. So a conceptual view, at least to start, is a distillation of the key object roles and their responsibilities (stated at a fairly high level). More than likely (unless you form classification hierarchies and use inheritance and composition techniques) many candidates you initially model will map directly to a single class in some inheritance hierarchy. But I like to open up possibilities by think first of roles and responsibilities, and then as a second step towards a specification-level view, mapping these candidates to classes and interfaces."

"Frameworks are skeletal structures of programs that must be fleshed out to build a complete application. For example, a windowing system or a simulation system can both be viewed as frameworks fleshed out by a windowed application or a simulation, respectively."

"Encapsulation is the key to increasing the value of such software metrics as reusability, refinability, testability, maintainability, and extensibility. Object-oriented languages provide a number of mechanisms for improving encapsulation, but it is during the design phase that the greatest leverage can be realized. The data-driven approach to object-oriented design focuses on the structure of the data in a system. This results in the incorporation of structural information in the definitions of classes. Doing so violates encapsulation. The responsibility-driven approach emphasizes the encapsulation of both the structure and behavior of objects. By focusing on the contractual responsibilities of a class, the designer is able to postpone implementation considerations until the implementation phase. While responsibility-driven design is not the only technique addressing this problem, most other techniques attempt to enforce encapsulation during the implementation phase. This is too late in the software life-cycle to achieve maximum benefits."

"Frameworks are white boxes to those that make use of them. Application developers must be able to quickly understand the structure of a framework, and how to write code that will fit into the framework. Frameworks are reusable designs as well as reusable code."

"What was the use of writing if someone didn't read what you have to say?"

"He knew what she'd be reading first as she started from the beginning, reading what he'd had to say when he was younger, and then growing older, stories at first about tiny mice who lived in families in back of the wall, and stories about school, and apartments in Greenpoint and Carnasie and Flatbush, elves in Ireland that he'd pictured as Pop had told him about them, and the woman with lace on her sleeves. She kept turning pages, and then halfway through, she whispered, "Water Street." Thomas knew she was reading now about a boy who listened at a register, thinking about a family, and a lighthouse, and then she turned the next page and took a breath. It was the story he really wanted her to see: a story about a girl who though less of herself than everyone else did, who worried about everyone, even when she didn't want to, even when it made her irritable. A girl who was afraid, and who hardly knew it yet, but was on her way to being a healer like her mother, because there'd never be anything else for her, and how lucky they were just to know her."

"She didn't want to touch the baby. Didn't want to know if she was dead. But still she reached down, her arms underneath that small body, and pulled it up against her. The body was burning with fever. But alive. Alive!"

"What had it been like the first time Da tried to read the same page? She could almost see his finger under each word, the whisper of his voice as he sounded out the words to himself. How had he ever done that? It seemed impossible."

"The girl's mouth was chapped, tight and pinched, her skin dry. Mama would say she looked woebegone, but as Bird looked at her eyes, the word she thought of was desperate."

"She wanted to put her head down on her knees and close her eyes. She felt the way she had years ago when she'd tumbled down the stairs and had the wind knocked out of her: a pain in the chest and stomach so strong it was hard to breathe."

"No one in the world like my sister Birdie."

"Sometimes in life you have to do the hardest things to get somewhere—to change your life."

"He was laughing again. What was it about Bird that made him do that?"

"How different everyone looked. How louldly they talked about who was starting work tomorrow, who would start in a week, while Sister Raymond sat at her desk looking serene. Bird felt a lurch in her chest. Of all of them, she though, she might be the one who'd miss school the most."

"Outside it had begun to rain, a fine mist of a rain: fall leaves were plastered to the walkway, and puddles filled with bits of hay and coal lay in the street. A nice bit to remember for the writing. Water Street! He loved to look at it."

"He remembered everything. Maybe that was why he was such a great writer. What he remembered he'd put on paper, but it came out different, more interesting, more exciting than she'd ever been able to imagine."

"How many times had she seen Annie sew in a sleeve, easing both sides so that they wouldn't pucker, taking a stitch, and smoothing out the fabric again? And now Mama was doing the same thing to someone's head. Someone's skin."

"She gives him candy. They're probably going to get married."

"How quiet everything was this Sunday afternoon, how still. No horse and wagon clopped down the street, no cart; no one stood on the corner talking. It was as if they were the only ones in the world."

"I don't think he's touched a washcloth to his face since the day he was born."

"Everything stopped: forks half raised, a bowl being passed. It seemed that the man was bathed in red, great swaths of it across his shirt and hands. And then Thomas realized: he was covered in blood."

"How could she know what she wanted to do with her life? All these years she thought she'd be a healer like Mama, and now she knew it was never going to happen."

"Is there anyone noisier in the world than Bird Mallon?"

"And the boy was right in back of her, his neck thin as a pencil. "My name is Thomas," he said. "Thomas Neary." She didn't answer. "The horse's name is Alfred, in case you want to know." He screwed up his face. "Or maybe Fernando.""

""A new start," Pop said as they stopped at the corner and waited to cross over to where te horse and cart waited for them. "A new apartment, Thomas. A new life." A new world to write about."

"Writing wasn't easy for her. It wasn't like arithmetic, not like a column of numbers to be added or subtracted from the top of the blackboard to the bottom, neat and organized; or science, figuring out the why of things."

"Leave it to Annie. She knew everything."

"Bird. A good name for her. She wasn't a sparrow or a songbird, though. She stood so straight, and her face was strong."

"He wrote stories about everything he saw, and he saw a lot. He walked through the streets of Brooklyn along the water, or leaned against the store windows on Livingston Street watching people hurrying along, making up stories about this one or that one."

"With just the sweep of a pen, Thomas, you can change the world, all of it."

"If only she could have held on to that day, held on to that moment forever, grasped it in her fists so it wouldn't escape. If only."

"Thomas watched him for a few minutes. Pop was good-looking, muscular, and his hair was almost gold even though it was getting a little thin on top. Thomas must have taken after his mother, whoever she was."

"But that was a realworld, and he didn't have to put it down on paper. He ripped the page out of the book, tore it into shreds, and threw them behind the tree, where they settled into the weeds."

"But what gave him the most satisfaction was going back through the pages to read about his first story appearing in the Saturday Evening Post. That afternoon he'd bought Bird the largest bag of lemon drops he could find. "He gives her candy," she had said, remembering too."

"Some people gain freedom by trading one form of bondage for another."

"Maybe it’s better to be half of something wonderful than a whole nothing at all."

"Fusion power we licked; static cling has us on the ropes. It’s a funny world."

"Truth and information are not the same thing!"

"“Truth and information are not the same thing. I promise you that’s a fact.” “So you told yourself. But you have to admit that they do coincide often enough to let us all get around in the world safely.”"

"Old responses live long, die hard, and frequently leave a troublesome corpse."