scispace - formally typeset
Search or ask a question

Showing papers by "Grady Booch published in 1995"


Book
01 Jan 1995
TL;DR: This book discusses Object-Oriented Architectures, Management and Planning, and What They Don't Teach You in Programming Class, as well as special Topics, including Managers Who Hate Programmers, and the Programmers.
Abstract: 1. First Principles. When Bad Things Happen to Good Projects. Establishing a Project's Focus. Understanding a Project's Culture. The Five Habits of Successful Object-Oriented Projects. Issues in Managing Object-Oriented Projects. 2. Products and Process. In Search of Excellent Objects. Object-Oriented Architectures. The Artifacts of a Software Project. Establishing a Rational Design Process. 3. The Macro Process. The One Minute Methodology. Conceptualization. Analysis. Design. Evolution. Maintenance. 4. The Micro Process. I'm OK, My Program's OK. Identifying Classes and Objects. Identifying the Semantics of Classes and Objects. Identifying Relationships Among Classes and Objects. Implementing Classes and Objects. 5. The Development Team. Managers Who Hate Programmers, and the Programmers. Who Work For Them. Roles and Responsibilities. Resource Allocation. Technology Transfer. Tools for the Worker. 6. Management and Planning. Everything I Need to Know I'll Learn In My Next Project. Managing Risk. Planning and Scheduling. Costing and Staffing. Monitoring, Measuring, and Testing. Documenting. Projects in Crisis. 7. Special Topics. What They Don't Teach You in Programming Class. User-Centric Systems. Data-Centric Systems. Computation-Centric Systems. Distributed Systems. Legacy Systems. Information Management Systems. Real Time Systems. Frameworks. Epilogue. Summary of Recommended Practices. Summary of Rules of Thumb. Glossary. Bibliography. Index. 0805305947T04062001

207 citations


Proceedings ArticleDOI
17 Oct 1995
TL;DR: The objective of this panel is to share the experiences of the panelists and offer some practical advice on how the identification and application of patterns can evolve from a cult to a culture.
Abstract: The concept and application of “patterns” are as old as organized human endeavor. Recently, patterns have become the focus of much discussion within the objectoriented community. Papers, discussion groups, conferences, and books have focused on identifying, discussing and applying patterns. To establish a common base terminology for the panel [from Webster]: cult a group with great devotion to some person, idea, or thing, particularly when such devotion may be viewed as some sort of intellectual fad (in the sense of early adopters of a new technology, i.e. the leaders) culture a group that has achieved a state of advancement in civilization with distinctive beliefs, traditions, etc. (in the sense of the creation of a broad following, where the “new” technology is part of the established business practice) Using the above definitions, the journey from “cult” to “culture” requires increasing maturity in discipline, learning, and mechanisms for transmitting knowledge to succeeding generations. This panel will focus on the evolution of the development/application of patterns from a cult to a culture. Our panelists represent a wide base of expertise that includes: design methodologies; education; management practices; patterns; process; programming languages and team organization. The objective of the panel is to share the experiences of the panelists and offer some practical advice on how the identification and application of patterns can evolve from a cult to a culture.

4 citations