Java modeling in color with UML : enterprise components and process
Author(s)
Bibliographic Information
Java modeling in color with UML : enterprise components and process
Prentice Hall PTR, 1999
Available at 4 libraries
  Aomori
  Iwate
  Miyagi
  Akita
  Yamagata
  Fukushima
  Ibaraki
  Tochigi
  Gunma
  Saitama
  Chiba
  Tokyo
  Kanagawa
  Niigata
  Toyama
  Ishikawa
  Fukui
  Yamanashi
  Nagano
  Gifu
  Shizuoka
  Aichi
  Mie
  Shiga
  Kyoto
  Osaka
  Hyogo
  Nara
  Wakayama
  Tottori
  Shimane
  Okayama
  Hiroshima
  Yamaguchi
  Tokushima
  Kagawa
  Ehime
  Kochi
  Fukuoka
  Saga
  Nagasaki
  Kumamoto
  Oita
  Miyazaki
  Kagoshima
  Okinawa
  Korea
  China
  Thailand
  United Kingdom
  Germany
  Switzerland
  France
  Belgium
  Netherlands
  Sweden
  Norway
  United States of America
Note
Includes bibliographical references and index
Description and Table of Contents
Description
This is the first book to teach software design in color. Peter Coad and his co-authors use four colors to represent four "archetypes": forms that appear repeatedly in effective component and object models. Given a color, you'll know the kind of attributes, links, methods, and interactions that class is likely to have. Using these color "building blocks," you can build better models for any business. Coad's team plugs these archetypes into a 12-class domain-neutral component that reflects his unparalleled modeling experience. The book delivers 47 ready-to-use, domain-specific components, each designed to help you build better models and apps. Finally, the authors introduce Feature-Driven Development, a new process for getting the most out of Java modeling and development. It's like having Peter Coad at your side, guiding you towards more effective design!
Table of Contents
1. Archetypes, Color, and the Domain-Neutral Component.
Archetypes. Color. The Four Archetypes in Color. Given a Class, What's the Color, What's the Archetype? The Domain-Neutral Component. Interactions Within the Domain-Neutral Component. Component Connectivity. Twelve Compound Components. Suggested Reading Paths. Summary.
2. Make or Buy.
Material-Resource Management. Facility Management. Manufacturing Management. Inventory Management.
3. Sell.
Product-Sale Management. Cash-Sale Management. Customer-Account Management.
4. Relate.
Human Resource Management. Relationship Management.
5. Coordinate and Support.
Project-Activity Management. Accounting Management. Document Management.
6. Feature-Driven Development.
The Problem: Accommodating Shorter and Shorter Business Cycles. The Solution: Feature-Driven Development. Defining Feature Sets and Features. Establishing a Process: Why and How. The Five Processes within FDD. Chief Programmers, Class Owners, and Feature Teams. Tracking Progress with Precision. Summary and Conclusion.
Appendix A: Archetypes in Color.
Appendix B: Modeling Tips.
Appendix C: Notation.
Index.
by "Nielsen BookData"