This is the third book in the series by Tom and Mary Poppendieck, who explain Lean Software Development, a method for implementing the Toyota Production System in the software business.

Leadership and 24 Frames for Leading the Software Business. It is neither a business book nor a mere technical manual. It is a book that foreshadows the beginning of the software industry’s maturation period.

REA refers to R (Resource), E (Event), and A (Agent), which are the three major elements in the structural model of business applications. Modeling rules are defined for these elements.

Therefore, in order to model them, it is necessary to cut into the target business field at a certain depth. Many of the previous modeling would have been merely adapted from UML (Unified Modeling Language).

This has caused problems with variations in the quality of the modeling, but REA can prevent such problems to some extent. In addition, because it follows certain rules, the REA model can be rewritten as a model of logistics and commercial distribution (this is called a value chain model).

When the structuring by REA is finished, further structuring by policy level and addition of behavior models using aspects are done, and finally the design and implementation of business applications are obtained.

This is the first book in Japan that systematically explains requirements development by the director of the Requirements Development Alliance, which was established last year.

This book describes the requirements development methodology Openthology 1.0, which will be presented for the first time at the second Requirements Development Summit on March 17, 2006.

This book is a must-read for those who are interested in requirements development in user companies, consulting companies, and system integrator companies.

Thank you for your patience. This is the long-awaited third edition.

This book is not a programming guide for XML applications; the emphasis is on the analysis/design of XML vocabularies and their use in distributed systems.

Readers who must develop systems using XML, or who are considering the benefits of such systems, will find this book useful (from the author’s foreword).

This book describes a concrete method for developing web applications using the Unified Modeling Language (UML).

With the spread of the Internet and e-commerce, there is a huge demand for Web applications, and it is no exaggeration to say that the methodology to support their efficient development is now an important issue for the software industry.

In this sense, this book is truly long-awaited.

This book attempts to classify objects into four categories that do not exist in the problem domain (“moment-time isolation”, “role”, “description (catalog item-like description)”, and “party, place, or thing”) and represent them with colors.

The color coding allows the modeling to be more expressive while also improving the understanding of the modeling.

This book uses the same terminology and classification as the previous book, Java Object Design with UML, so it can be read in conjunction with that book for a deeper understanding.

A classic book on object modeling using strategies and patterns by Peter Cord, a master of the art of object modeling, this book explains the key business object design techniques for 3-tier and N-tier architectures with easy-to-understand examples.

The accompanying handbook covers 148 strategies and 31 patterns. It is immediately applicable to the reader’s business object design.

J It has been two years since Java Design was published, and in that time Java has gained wide acceptance.

The first edition focused more on design rather than programming, and while Java programming books change rapidly, this book about design remained a bestseller for two years. It remained a bestseller for two years.

The most visible feature of the second edition is the unification of the UML (Unified Modeling Language) notation. The content features include 68 new pages of new sections.