- Shopping Bag ( 0 items )
Ships from: Chicago, IL
Usually ships in 1-2 business days
Step-by-step introduction to the use of the Unified Modeling Language and patterns in the analysis, design and construction of software projects. One integrated case study based on the point-of-sale system is developed throughout as a means to clarify and define the software development process. Presents a concise review of the object-oriented analysis, design and development process then introduces the point-of-sale case study through development and understanding of the requirements' specification and use case process description. Continues with the analysis phase by building and expanding a conceptual model with attributes and associations. Defines behaviors via system sequence diagrams and contracts. Shifts from analysis to design with use cases, collaboration diagrams, responsibility patterns and class diagrams. Discusses visibility concepts and system design issues before going on to the construction and analysis phases. Shows how to map designs to code (Java), explains development cycle requirements, extends the conceptual model, and organizes elements and model behavior in state diagrams. Introduces additional patterns in the design phase and concludes with discussions of special topics related to UML notation, development process issues, frameworks, patterns and persistence.
Posted November 30, 2001
I find this book to be very informative for all those indivisuals who are interested in learning UML. This book was used as a reference book in my bachelors degree in a design course. The best part of this book is the detail with which even minor things like Concept model is explained + the way in which all Designs Patterns are explained. Way to go!!!Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted May 10, 2001
This book seems to have all the terminology and covers all the concepts, but I couldn't digest the information because the presentation was pure textbook drone. If you are looking for a more conversational style of text, developer to developer, which is to the point, this book is NOT a good buy. On the other hand, if you like formatted text boxes and meaningless bullet points with textbased prose, this is right on the money. One redeeming feature of the book is its many examples of UML diagrams and OO artifacts.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted September 18, 2000
After reading through chapter one I was involved. I expected this to be another average text book reading, but it shocked me. My initial thought after reading this was it can actually help me to understand my job responsibilities better. As a Business Analyst I must apply the methods in this book on a daily basis, and the way the information is outlined and the illustrations the author provides are great guides to enhancing the knowledge you need to know and may already know. So this is a must for those who use OO technology on a frequent basis.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted December 21, 1999