UML

Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)

Average customer rating:

Excellent Work!
Excellent guide!
Wanna master OO Design for real?
Great introduction to OOAD
Balanced Real-World Advice For Best Practices Software Development

Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
Craig Larman
Manufacturer: Prentice Hall PTR
ProductGroup: Book
Binding: Hardcover

General | Software | Computers & Internet | Subjects | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

Qualifying Textbooks - Spring 2007 | Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition
Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series)
Head First Design Patterns (Head First)
Agile and Iterative Development: A Manager's Guide
Writing Effective Use Cases

ASIN: 0131489062

Amazon.com

Good software starts with a good design, and the subtitle of Applying UML and Patterns, "An Introduction to Object-Oriented Analysis and Design (OOA/D) and the Unified Process" reinforces that that's what this book is about.

The first edition of Applying UML and Patterns became a standard. The second edition uses the unified process (UP) as the iterative process within which OOA/D is introduced, and extends the case study used in the first edition. Other changes have been made to reflect the growing consensus on the most effective ways to work with OOA/D and patterns.

Although you will learn UML, this isn't what Applying UML and Patterns is all about. It's designed to teach you to think of software as a collection of objects with properties and to manipulate the relationships between them. This is far more profound.

The case study enables Craig Larman to carry the design through to Java code. In practice, you will need a basic understanding of OO programming to benefit from Applying UML and Patterns, though you needn't know Java--you can implement the designs in the OO language of your choice with equal facility.

When it comes right down to it, Applying UML and Patterns is all about providing you with a language in which to think about software design. This is quite different from learning a language in which to code a design.

A facility with OOA/D will enable you to design and discuss programs independent of code, to produce more elegant and maintainable software, and to take a 30,000-foot view of the way your software interacts with the world. In effect, it can shift your viewpoint from that of a mechanic to that more sophisticated viewpoint of an engineer. Recommended. --Steve Patient. Amazon.co.uk

Book Description

“People often ask me which is the best book to introduce them to the world of OO design. Ever since I came across it, `Applying UML and Patterns' has been my unreserved choice.” —Martin Fowler, author, “UML Distilled” and “Refactoring”

The first edition of “Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design” quickly emerged as the leading OOA/D introduction; translated to many languages and adopted in universities and businesses worldwide. In this second edition, well-known object technology and iterative methods leader Craig Larman refines and expands this text for developers and students new to OOA/D, the UML, patterns, use cases, iterative development, and related topics.

The book helps newcomers to OOA/D learn how to “think in objects” by presenting three iterations of a single, cohesive case study, incrementally introducing the requirements and OOA/D activities, principles, and patterns that are most critical to success. It introduces the most frequently used UML diagramming notation, while emphasizing that OOA/D is much more than knowing UML notation. All case study iterations and skills are presented in the context of an “agile” version of the Unified Process -- a popular, modern iterative approach to software development. Throughout, Larman presents the topics in a fashion designed for learning and comprehension.

Among the topics introduced in Applying UML and Patterns are: * requirements and use cases, * domain object modeling, * core UML, * designing objects with responsibilities, * “Gang of Four” and other design patterns, * mapping designs to code (using Java as an example), * layered architectures, * architectural analysis, * package design, * iterative development, * the Unified Process.Foreword by Philippe Kruchten, the lead architect of the Rational Unified Process.

“Too few people have a knack for explaining things. Fewer still have a handle on software analysis and design. Craig Larman has both.” —John Vlissides, author, “Design Patterns” and “Pattern Hatching”

“This edition contains Larman's usual accurate and thoughtful writing. It is a very good book made even better.” —Alistair Cockburn, author, “Writing Effective Use Cases” and “Surviving OO Projects”

Customer Reviews:

Excellent Work!.......2007-04-23

As pointed out by many, this book is a very nice introduction to Object Oriented Analysis and Design. The author's explanations were very clear. This book covers agile practices, UML, many patterns including Gang of Four (GoF), and software architecture. Overall I really enjoyed reading this book. From an industry standpoint as well as an academic standpoint, I believe this book does an excellent job. This book will be part of my library for a long time to come. Highly recommended.

Excellent guide!.......2006-11-10

Well, I think this book should be a must read for any pro or beginer in the software design/build area, it takes you from the start trying to make you understand what your client want you to understand, until the best practices to have patterns, tests, and a good team development, so do not hesitate to buy it!.

Wanna master OO Design for real?.......2006-06-03

I had a degree in Computer Science from a respectable university when I read the book. Still, I learned from the book so much that I realized I barely scratched the surface of OO design before reading it.

It teaches OO Analysis and Design using many techniques, such as writing use cases, modeling the business domain, drawing UML diagrams, using CRC cards, and going through agile iterative development cycles.

This book will not only provide you with a chance to learn OO Design, but also requirements gathering, analysis, and basic architecture and project management.

Great introduction to OOAD.......2006-03-13

This book is a great introduction to OOAD, agile development, Patterns and UML. It goes from the basic concepts to real world applications. It is has lots of content though but it is worth reading it from beginning to end.

Balanced Real-World Advice For Best Practices Software Development.......2006-02-18

I read the first edition of this book years ago when I was making the transition to objects. It was about the tenth book on the subject that I had read, but it was the first one that consistently anticipated the questions that came up when I was actually trying to build something using UML, long after the hype and "objects will save us" party atmosphere had died down. Craig Larman has carefully remembered, or has taught this enough to have been reminded of, the kinds of questions software practitioners actually encounter on the way to building systems using UML. This 3rd edition is twice as big as the first, and it is twice as good only because it is twice as much of Larman's excellent teaching.

This book is so good that even developers experienced with UML, the GRASP patterns, and agile development methods will gain from it, reminding us once again to balance the best practices that we apply perhaps a little unevenly at times. It is clearly a book by someone who has been there, and has remembered what it was like during the learning process. But perhaps its greatest strength is its application of very good theory in a very pragmatic way, in short, its balance. This is one of a very few books that I recommend to everyone I know in software.

Head First Object-Oriented Analysis and Design: A Brain Friendly Guide to OOA&D (Head First)

Average customer rating:

Good for beginners
Great idea, but quality may be slipping
Where's my book??????
C# Code is available for this book from user forum
Must Read!!!

Head First Object-Oriented Analysis and Design: A Brain Friendly Guide to OOA&D (Head First)
Brett D. McLaughlin , Gary Pollice , and Dave West
Manufacturer: O'Reilly Media, Inc.
ProductGroup: Book
Binding: Paperback

General | Programming | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

General | Programming | O'Reilly | By Publisher | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

Head First Design Patterns (Head First)
Head First Java, 2nd Edition
Head Rush Ajax (Head First)
Head First Design Patterns Poster (Head First)
Head First HTML with CSS & XHTML (Head First)

ASIN: 0596008678

Book Description

"Head First Object Oriented Analysis and Design is a refreshing look at subject of OOAD. What sets this book apart is its focus on learning. The authors have made the content of OOAD accessible, usable for the practitioner."

Ivar Jacobson, Ivar Jacobson Consulting

"I just finished reading HF OOA&D and I loved it! The thing I liked most about this book was its focus on why we do OOA&D-to write great software!"

Kyle Brown, Distinguished Engineer, IBM

"Hidden behind the funny pictures and crazy fonts is a serious, intelligent, extremely well-crafted presentation of OO Analysis and Design. As I read the book, I felt like I was looking over the shoulder of an expert designer who was explaining to me what issues were important at each step, and why."

Edward Sciore, Associate Professor, Computer Science Department, Boston College

Tired of reading Object Oriented Analysis and Design books that only makes sense after you're an expert? You've heard OOA&D can help you write great software every time-software that makes your boss happy, your customers satisfied and gives you more time to do what makes you happy.

But how?

Head First Object-Oriented Analysis & Design shows you how to analyze, design, and write serious object-oriented software: software that's easy to reuse, maintain, and extend; software that doesn't hurt your head; software that lets you add new features without breaking the old ones. Inside you will learn how to: <ul>

Use OO principles like encapsulation and delegation to build applications that are flexible</li>

Apply the Open-Closed Principle (OCP) and the Single Responsibility Principle (SRP) to promote reuse of your code</li>

Leverage the power of design patterns to solve your problems more efficiently</li>

Use UML, use cases, and diagrams to ensure that all stakeholders are communicating clearly to help you deliver the right software that meets everyone's needs.</li> </ul>

By exploiting how your brain works, Head First Object-Oriented Analysis & Design compresses the time it takes to learn and retain complex information. Expect to have fun, expect to learn, expect to be writing great software consistently by the time you're finished reading this!

Customer Reviews:

Good for beginners.......2007-06-08

I decided to buy this book based on the reputation of the 'head first' series regarding ease of 'consumption'. The main goal was to find new ideas about how to transmit object oriented analysis to newcomers.

Overall this book is very easy to read from cover to cover. The jokes, examples and exercises do force you to think and assimilate the concepts shown.

In the end I had just one 'complaint': I wish the authors could have extended the coverage with more complex scenarios and more day-to-day situations.

Great idea, but quality may be slipping.......2007-05-31

I love the Head First (HF) Series, and as I am neither a programmer or a software person the HF books have proved a great entry into the discipline.

The HF idea works for my learning style, and I think the suitability is independent of age as I am a middle-age male.

It also difficult to know how good the HF books are because the information they present is new, and effectiveness is judged by how much you learn. I have found that after completing the HF OOAD I have been able to go from novice to following with ease the more formal books of Grady Booch (OOAD 2nd Ed) and Graig Larman (applying UML and patterns). I am serious about learning this stuff.

HF OOAD gently takes you through the full OOAD journey in which you are an active participant.

While the HF books seem 'informal and funky' they have a high level of design, are well thought out, are serious, and are produced by TEAMS of gifted and talented people. The quality control is generally good. But, these kind of books need to be well thought out as the style only works when everything fits together (so beware of imitations). Like good teachers, they take your hand, give you clues that are later amplified, and take you to places you never imagined. You miss the characters after you finish each book.

The requirement for talented writers and the demand for more lines of HF style books I think is becoming problem. As I write this review, the HF OOAD book is not fully supported by its website as promised in the book with half the chapters not supported by code. While I got by successfully without this support (and wrote the code myself as you are meant to but I used eclipse which you are not meant to according to HF authors - so I cheated), the later chapters did cover some pretty demanding work from my point of view.

It is because the supporting code is not on the web that I have given this HF OOAD book three stars. I am writing this review so that I can rate it with three stars, and hopefully add pressure for the HF series to get its act together.

Where's my book??????.......2007-05-27

I didn't recieve it!! It's an absurd. Can you give me any explanation????

C# Code is available for this book from user forum.......2007-05-18

If you are a C# programmer there is a link to the equivalent C# sample code for each chapter in the user forums of the book's web site.

Must Read!!!.......2007-05-12

As usual the head first series rocks!!. The book is a must read.

UML 2.0 in a Nutshell (In a Nutshell (O'Reilly))

Average customer rating:

One of the Best UML Reference Books On the Market Today & Very Portable
Excellent reference book
Get UML Info in a Snap
UML users should purchase
Really very useful and handy book

UML 2.0 in a Nutshell (In a Nutshell (O'Reilly))
Dan Pilone , and Neil Pitman
Manufacturer: O'Reilly Media, Inc.
ProductGroup: Book
Binding: Paperback

General | Programming | Computers & Internet | Subjects | Books

General | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

Nutshell | Series | O'Reilly | By Publisher | Books

General | Programming | O'Reilly | By Publisher | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

The Elements of UML 2.0 Style
Learning UML 2.0 (Learning)
Head First Design Patterns (Head First)
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition

ASIN: 0596007957
Release Date: 2005-06-01

Book Description

System developers have used modeling languages for decades to specify, visualize, construct, and document systems. The Unified Modeling Language (UML) is one of those languages. UML makes it possible for team members to collaborate by providing a common language that applies to a multitude of different systems. Essentially, it enables you to communicate solutions in a consistent, tool-supported language. Today, UML has become the standard method for modeling software systems, which means you're probably confronting this rich and expressive language more than ever before. And even though you may not write UML diagrams yourself, you'll still need to interpret diagrams written by others. UML 2.0 in a Nutshell from O'Reilly feels your pain. It's been crafted for professionals like you who must read, create, and understand system artifacts expressed using UML. Furthermore, it's been fully revised to cover version 2.0 of the language. This comprehensive new edition not only provides a quick-reference to all UML 2.0 diagram types, it also explains key concepts in a way that appeals to readers already familiar with UML or object-oriented programming concepts. Topics include: <ul>

The role and value of UML in projects </li>

The object-oriented paradigm and its relation to the UML </li>

An integrated approach to UML diagrams </li>

Class and Object, Use Case, Sequence, Collaboration, Statechart, Activity, Component, and Deployment Diagrams </li>

Extension Mechanisms </li>

The Object Constraint Language (OCL)</li></ul> If you're new to UML, a tutorial with realistic examples has even been included to help you quickly familiarize yourself with the system.

Customer Reviews:

One of the Best UML Reference Books On the Market Today & Very Portable.......2007-03-12

When searching for a very good UML reference book last year, I happened upon the book entitled "UML 2.0 in a Nutshell" by Dan Pilone with Neil Pitman. The book, which measures a mere 8.9 by 6 by 0.8 inches, is both lightweight and highly portable; which is one of the reasons that I decided to purchase a copy. However, it was ultimately the content of the book, and not its compact size, that convinced to me that this would a very useful resource. Condensed within 216 pages, "UML 2.0 in a Nutshell" lives up to its title, as the book is an extremely informative resource in understanding the various graphical elements that comprise UML with its nine types of diagrams.

The book's 12 chapters and two appendices are divided into four main parts: an introduction, static diagrams, behavioral modeling diagrams and finally, extensions and applications of UML.

First Part: Introduction

chapter 1: Fundamentals of UML

This chapter provides a short, but good introduction to the fundamentals of UML. If you have never used UML before, this will help to introduce several key concepts of UML; but you might want to consider purchasing a UML tutorial book, such as "UML Weekend Crash Course" by Thomas A. Pender, to obtain a more hands-on approach to learning UML.

Second Part: Static Diagrams

Chapter 2: Class Diagrams

Class diagrams are one of the most important aspects of UML. With class diagrams, the relationships between classes can be thoroughly illustrated, including the strengths of the relationships between classes. This chapter provides a precise description of the various ways that class relationships can be defined within UML: dependencies, associations, aggregations, compositions and generalizations; as well as association classes. This chapter also discusses class members (variables & methods), whether a class might be abstract or an interface, and templates.

Chapter 3: Package Diagrams

Classes that are contained within a common package can be illustrated within UML using package diagrams. This chapter also includes relationships between packages and use case packages.

Chapter 4: Composite Structures

This chapter discusses composite structures that exist during runtime, including connectors and ports, as well as collaborations.

Chapter 5: Component Diagrams

Components (replaceable & executable pieces of a larger system whose implementations are usually hidden) can be used in UML as either a black-box or white-box view. This chapter discusses both uses.

Chapter 6: Deployment Diagrams

This chapter discusses how the deployment of an application (which may include many pieces) can be illustrated within UML, including artifact instances, manifestations, nodes, devices, execution environments and communication paths.

Third Part: Behavioral Modeling Diagrams

Chapter 7: Use Case Diagrams

This chapter documents how an actor (a person or another application) interacts with applications and their internal components.

Chapter 8: Statechart Diagrams

This chapter discusses the two types of state machines that can be described in UML: behavioral state machines and protocol state machines. This includes states, composite states, submachine states, transitions, activities, pseudo-states and event processing.

Chapter 9: Activity Diagrams

This chapter discusses how activities and actions are illustrated within UML, including activity edges, activity nodes, object nodes, control nodes and more advanced activity modeling: activity partitions, exception handling, expansion regions, looping, streaming, interruptible activities and data store nodes.

Chapter 10: Interaction Diagrams

How UML is able to illustrate interactions between objects is accomplished through interaction diagrams. This chapter discusses usage of interaction participants, messages, execution occurrences, state invariants, event occurrences, traces, combined fragments, interaction occurrences, decompositions, continuations, sequence timing, timing diagrams and communication diagrams.

Fourth Part: UML Extensions & Applications

Chapter 11: Tagged Values, Stereotypes and UML Profiles

This chapter discusses use of stereotypes, tagged values, constraints and UML profiles.

Chapter 12: Effective Diagramming

This chapter is essentially a "do" and "don't do" chapter that emphasizes the need to keep UML diagrams as simple as possible, though that is not always possible.

The two appendices: Appendix A is about MDA (Model-Driven Architecture) and Appendix B is about the object constraint language (OCL), which is an extension of UML 2.0.

Overall, I rate "UML 2.0 in a Nutshell" with 5 out of 5 stars and highly recommend it to anyone learning and/or using UML on a regular or infrequent basis. I have yet to see a book as well written as this in explaining the many aspects of UML in as a concise & easy-to-understand form as "UML 2.0 in a Nutshell".

Excellent reference book.......2007-03-07

I bought this book recently to learn about the differences and new stuff included in this version of UML. I sincerely think this book was an excellent choice. The author describes each UML diagram in a focused way and in very simple words. I'm actually reading it and i am very pleased with this book. It fits all my expectations about a quick reference guide into the world of UML 2.0. Note this isn't a learning book about this language it's only like its title said UML 2.0 in a nutshell.

Get UML Info in a Snap.......2007-02-11

This is a great quick-reference to keep in your laptop bag. The examples are very short, but very complete.

Very well done!

UML users should purchase.......2006-10-26

I needed better explanations on using UML correctly. I already owned a few books that were -- OK but lacking in a clear style of explaining the correct use of some of the UML. After reading the reviews on Amazon of other books, and the reviews of the updated version of this book - I took the leap and purchased this 2.0 update.

I am very pleased with the book, it is well written, and clear in its subject introduction and explanation of UML's symbols usage.

Being a thinner book makes it possible to have the information at hand when I need to carry my references back and forth from office and home.

I would like to thank the prior reviewers - who had received a copy from the publisher, for posting their reviews. The publisher was confident that they had fixed the problems with the earilier book, and I would agree that they have a very good product now.

The publisher deserves some congratulations on this approach. Good job!

Really very useful and handy book.......2006-08-25

Believe or not after reading of the book you take UML seriously and get thorough survey what all is possible to draw in it. There is a lot of real small examples, perhaps one of the most important notes to the book. Only problem is that dashed lines are in diagrams so tiny you can not recognize them from standard full lines. You have to use a reading glass (magnifier).

UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering

Average customer rating:

Clean, reasonable guide to OO and UML for beginner to medium level BA
The best business analyst book on the market
Business Analyst
Overall a very good book
Excellent Book for UML

UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering
Howard Podeswa
Manufacturer: Course Technology PTR
ProductGroup: Book
Binding: Paperback

PCs | Hardware | Computers & Internet | Subjects | Books

General | Computers & Internet | Subjects | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

Qualifying Textbooks - Spring 2007 | Stores | Books

Writing Effective Use Cases
Mastering the Requirements Process (2nd Edition)
The Software Requirements Memory Jogger: A Pocket Guide to Help Software And Business Teams Develop And Manage Requirements (Memory Jogger) (Memory Jogger)
Software Requirements, Second Edition
More About Software Requirements: Thorny Issues and Practical Advice

ASIN: 1592009123

Book Description

The IT Business Analyst is one of the fastest growing roles in the IT industry. Business Analysts are found in almost all large organizations and are important members of any IT team whether in the private or public sector. "UML for the IT Business Analyst" provides a clear, step-by-step guide to how the Business Analyst can perform his or her role using state-of-the-art object-oriented technology. Business analysts are required to understand object-oriented technology although there are currently no other books that address their unique needs as non-programmers using this technology. Assuming no prior knowledge of business analysis, IT, or object-orientation, material is presented in a narrative, chronological, hands-on style using a real-world case study. Upon completion of "UML for the IT Business Analyst," you will have created an actual business requirements document using all of the techniques of object-orientation required of a Business Analyst. "UML for the IT Business Analyst" puts together all of the technology pieces needed to proficiently perform the Business Analyst role.

Customer Reviews:

Clean, reasonable guide to OO and UML for beginner to medium level BA.......2007-02-02

There are so many opinions about how UML should be used and none can claim universal application. It is not only the complexity of UML and OO methodologies, but the variety of software tools that support these methods and then you have to deal with an infinite variety of real life situations and people. At the end of the day, a BA must write documentation and communicate findings, outcome and models to stakeholders, users, developers, architects and sometimes to third parties involved in the project. Every single person has a different view, companies have different document templates and actors have different education and skills. How can you write a book to teach UML and make anyone happy? You can't. So, you have to get something from every book you read that suits you, your training and the project methodology used in your business.

I think that Howard manages to walk you through the complexity of all this, recognising the inherent limitations that I listed above and present a framework that you can use to expand your horizons. The author is reasonably disciplined about the UML standard, so this is not a popular book for, say, accountants or florists that want to know about UML. Another positive point of this book is that you are provided with documentation templates that you can use straight away to write business requirements for your next project. Additionally, the author combines the description of UML constructs with an induction into OO methodology. Some authors fail to make this connection between the standard and the work methodology.

The book is written by using a real life project large enough to cover almost every aspect of UML. Howard is quite practical, whenever he feels that in practice some tools are not widely used, he will say so and avoid spending too much time on something just to show you how much he knows. The examples are simplified to keep the size of the book at a sane level. The depth of the book is adjusted so that beginners are not intimidated by the complex concepts, especially when it comes to discuss static modelling.

The last section of the book talks about testing and spends sufficient on explaining the foundation of structured test methodology. Testing is becoming more and more specialised work and progressively fewer business analysts do both business requirements and test implementation. However, it is important to connect these two activities, and Howard does that very well. Testing should be based on business requirements and verify that the requirements are fulfilled.

One not so positive comment that I would make about the book, is that it mixes too much the role of the business analyst and system analysts. I believe that he should have put more emphasis on separating the roles, because they require distinct set of skills. Also he should have made the reader aware that the project management methodology has an impact on the way the business analyst works. The subject of project management is not discussed very much here. If you work in a large organisation this is an important factor to consider. On the book cover the claim is that you will learn how to use IBM Rational Rose. I think that this is a little bit exaggerated. Overall this is a clean, nice and useful book, if you fall in the right category.

The best business analyst book on the market.......2007-01-11

This book has industrial standard templates for each phase of the project. - Both the templates and steps are easy to follow.

Business Analyst.......2006-11-10

i was one in many people to read the reviews and now i am writing one ..its really a good book for every new business analyst or a fresher BA who want to know what is BA and his role in real world.Good book in a perfect price.I like it.

Overall a very good book.......2006-11-04

Does a good job of explaining what UML is and how an analyst can use it to make everyone's job a little easier. It has perked the interest of several people at the company where I work.

Excellent Book for UML.......2006-08-08

This book is a great approach to learn UML and object oriented Requirements gathering. A class-room training for 30 bucks. Fantastic for beginners too..

Business Modeling With UML: Business Patterns at Work

Average customer rating:

Not particularly useful
A very good guide to business-level modelling with UML
Excellent ideas, excellent read!
Very high level, often inconsistent
Difficult to apply the recommendation using Rational Rose

Business Modeling With UML: Business Patterns at Work
Magnus Penker , and Hans-Erik Eriksson
Manufacturer: Wiley
ProductGroup: Book
Binding: Paperback

General | Business & Investing | Subjects | Books

General | Programming | Computers & Internet | Subjects | Books

General | Computers & Internet | Subjects | Books

Modeling & Simulation | Computer Science | Computers & Internet | Subjects | Books

Object-Oriented Software Design | Computer Science & Information Systems | New & Used Textbooks | Stores | Books

Programming Languages | Computer Science & Information Systems | New & Used Textbooks | Stores | Books

General | Business & Finance | New & Used Textbooks | Stores | Books

All Amazon Upgrade | Amazon Upgrade | Stores | Books

Business & Investing | Amazon Upgrade | Stores | Books

Computers & Internet | Amazon Upgrade | Stores | Books

Qualifying Textbooks - Spring 2007 | Stores | Books

Look Inside Business Books | Trip | Specialty Stores | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

Enterprise Modeling with UML: Designing Successful Software through Business Analysis (The Addison-Wesley Object Technology Series)
UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering
UML in Practice: The Art of Modeling Software Systems Demonstrated through Worked Examples and Solutions
Business Process Management With a Business Rules Approach: Implementing the Service Oriented Architecture
The Elements of UML 2.0 Style

ASIN: 0471295515

Amazon.com

Until now, the Unified Modeling Language (UML) has been primarily used to design software, but should you use it to model your entire business as well? That's the intriguing argument of Business Modeling with UML, a text that combines leading-edge enhancements to UML with some solid thinking about business. Written for any manager with some technical background, this book looks at the possibilities of UML used to model entire organizations.

The book makes a strong case for the advantages of modeling businesses in UML. With models, an organization can provide better software, define and implement new goals, and even decide whether to outsource certain operations. The Erickson-Penker Business Extensions for UML, invented by the authors and presented within the text, permit UML to document the entire business enterprise. This book shows how to model businesses, from business architecture to processes, business rules, and goals. Short case studies--for Web-centric and more traditional companies--are used to illustrate key concepts here.

Later sections of the book will perhaps take a little more background in software engineering to appreciate fully as the book presents a handful of business patterns, which offer reusable solutions to common problems (just like software patterns). The authors also look at how to leverage a business model to create better software.

In engineering, a new car is modeled and thoroughly tested on a computer before any physical prototype is ever built. As the authors point out, a business that has accurate models can test out new ideas cheaply and then adapt to changing market conditions quickly. This title makes a case that UML--a tool traditionally used by software developers--is ready to tackle the job. Read this notably informative and intelligent book to see the possible benefits of business modeling in UML for your organization. --Richard Dragan

Topics covered: Business modeling basics, UML notation and Erickson-Penker Business Extensions, class diagrams and powertypes, object diagrams, statecharts, activity diagrams and swimlanes, sequence and collaboration diagrams, collaboration and use case diagrams, component and deployment diagrams, stereotypes, business architectures, business processes, resources, goals, business rules, Object Constraint Language (OCL) and collections, business views and patterns, business goal allocation, business goal decomposition, business goal-problem, and software architectures

Book Description

"An excellent hands-on book for practitioners eager to document the internal structure and everyday workings of business processes. This clear and practical book belongs on the shelf of everyone dedicated to mapping, maintaining, and streamlining business processes." -Richard Mark Soley, Phd, Chairman and CEO, OMG
"Eriksson and Penker have not just written another patterns book; this is a significant contribution to the key field of business-IT alignment. While capturing profound academic insights, what makes the book so refreshing from a practitioner's viewpoint is the richness of accessible, down-to-earth examples and its pragmatic, unpretentious style."-Paul allen Principal of CBD Strategies and Architectures, Sterling Software
"UML may have been designed by and for software engineers, but Eriksson and Penker have defined a practical extension to UML for describing business processes. They put this extended UML immediately to use with a gallery of common business patterns that should jump start any BPR effort."-Philippe Krchten, Director of Process Development Rational Software
"This book is a marriage between proven business modeling concepts and the techniques of UML. It provides real-world strategies for developing large-scale, mission-critical business systems in a manner accessible to both software and business professionals."-ScottW. Ambler, Author of Process Patterns
Following up on their bestselling book, UML Toolkit, Hans-Erik Eriksson and Magnus Penker now provide expert guidance on how to use UML to model your business systems. In this informative book, key business modeling concepts are presented, including how to define Business Rules with UML's Object Constraint Language (OCL) and how to use business models with use cases. The authors then provide 26 valuable Business Patterns along with an e-business case study that utilizes the techniques and patterns discussed in the book.
Visit our Web site at www.wiley.com/compbooks/

Customer Reviews:

Not particularly useful.......2004-06-30

I am looking for a book that would be able to flesh out proper business processes utilizing well defined modeling language/framework. Although UML is extremely useful for software development, the author's work did make its case stand with me on UML's usefulness as business process modeling tool.

The examples are too simplistic and the suggested modeling diagrams are far too cluterred for a business personel to understand.(Cluttered diagrams on a simple example) The book would be better if it had a growing case study and used real world examples and diagrams.

A very good guide to business-level modelling with UML.......2003-07-13

One of the weaknesses of the Unified Modelling Language is its relatively limited support for modelling at the Enterprise level, especially to accurately model business processes. The UML purists believe that everything should be reduced to Use Cases, while these authors recognise that much more is necessary.

The book covers five quite distinct topics:
1. An introduction to business modelling and UML, explaining the problems the authors want to help solve, and describing each of the relevant techniques of UML,
2. A proposal for a group of extensions to UML (using that language's own established extensibility mechanisms) so that that it can better model business processes,
3. A description of the variety of views and models which will be required to establish a comprehensive understanding of the business, or at least part of it,
4. A repository of "business patterns", which you can use to model the business,
5. A comprehensive worked example.

Each of these is quite detailed. In particular, the book contains probably the best introduction to the Object Constraint Language (OCL), and its use to model business rules, that I have read anywhere. The sections on how to do business modelling are also very good, as are the introductions to the relevant UML techniques.

The "Eriksson-Penker extensions for business modelling" are important because several UML-based case tools have now implemented them as an emerging standard for business process modelling with UML. If you want to fully understand how these work, this is the book to read.

The business patterns are more of a "curates egg". Some are extremely useful, and others innovative which could easily solve your problems where there is an accurate match. That said, some are less good and seem to state the obvious, although with patterns it is always difficult to know if you are judging some harshly simply because you are so familiar with them and other readers will get more value. Some of the pattern explanations are a bit repetitive, and the "examples" often sound very artificial, but overall they are useful, and a single one which solves a real business modelling problem for you will justify the rest.

At over 400 pages, some of which is occasionally slightly slow and ponderous this is not an ideal book to read from cover to cover. But it is definitely one to study, focusing on whichever topic is most relevant to you at any time, and I can happily recommend it.

Excellent ideas, excellent read!.......2003-02-01

In this book, Eriksson and Penker (E-P) define UML extensions for describing business processes. Here's a summary of my interpretation of thier ideas:

Processes are generally modeled using UML activity diagrams. A "process" is shown as an Activity stereotyped as <<process>>. The <<process>> activity is also given a new icon and a set of tagged values. I think the icon was added to make buissness developers feel more at home. Instead of a retangle with rounded corners, it looks like a big arrow. Four base types of objects are shown in a process diagram: Goal, Input, Output and Resource objects. "The input objects are resources that are transformed or *consumed* as part of the process..." An input object may become an output object with a state change, but this is not always the case. Sometimes input objects are consumed. E-P say "An output object can be a completely new object created during the processes or it can be a transformed input object". Another quote: "During its execution, the process interacts with other resource objects, objects other than the input and output objects, that are just as vital. These objects carry information required by the process or they are resources responsible for executing the activities in the process, such as people or machines.". Output objects flowing from one process can become input objects or resource objects flowing to another process. Goal objects define a set of rules for controlling the process. A process diagram is drawn with input objects to the left, resource objects below, goal objects above and output objects to the right of each process symbol. Object flows (dashed arrows) are used to connect the objects to the processes. Just as in standard UML, <<process>> Activities can contain sub <<process>> Activities and Activities. Non-process Activities being automic. The State of an object can be shown with standard UML syntax. A description on the use of "swimlanes" in activity diagrams is also given. Classes of objects and their associations are provided by standard class diagrams. E-P also describe the use of sequence diagrams and state diagrams in a business modeling context. They even provide a meta-model for thier Modeling extensions! The book also describes another type of process diagram that they call an "assembly line" diagram. It appears to be a process diagram that utilizes Packages to represent resource collections. I believe that Eriksson and Penker stayed within the UML standard and in fact thier extensions don't appear to be that "extensive". Mostly some stereotyping, some tagged values and an icon. The second half of the book is dedicated to design patterns for busineess development. But many of these patterns could be very usefull to you. They also show how to provide object constraints using OCL and provide a pretty decent UML primer.

One thing that is bothering me about the process diagrams it that they do not show object collaboration very well. I think that the contractual message passing between objects needs to be shown with informational interface objects rather than parameter lists. I'm withholding judgement at this point. After all, the business models they are describing will never be translated into code, but rather business forms and process documentation and executed by people and not computers. They do however, give a method for creating software system models for automating part of the business system.

All mistakes, misconceptions and missuse of terminolgy in the above description of Eriksson and Penker's book are my own.

Adios,
-Andy

Very high level, often inconsistent.......2003-01-27

The models in this book are interesting but they are too high level to be useful. The modelling style is inconsistent e.g. missing multiplicities. Some of the models are contradictary.
If you have absolutely no idea about any of this stuff, and are interested in the absolute basics, then this book might be useful. If you want to understand the subtleties of a business domain, it won't help.

Difficult to apply the recommendation using Rational Rose.......2003-01-18

I enjoyed the concepts, and the book is actually very readable. But when it came time to start applying the techniques my tune changed a bit. If you are using a simple drawing tool (like Visio or similar) to render your UML diagrams, then this book may be helpful to you. If you are using a more sophisticated tool like Rational Rose, then I think you will have difficulty creating the necessary business extensions and stereotypes. (Is that a criticism of the book or of Rose - you decide).

Another criticism is that the authors appear to have made themselves readily available for questions and additional info, but in fact this is not true in my case. Also the the URL that is provided on page xix (in the introduction), which is supposed to contain additional examples and articles is no longer available. I hate that! It appears as though the authors have left this book behind them, so perhaps you might as well to.

Book Description

Scott Ambler, award-winning author of Building Object Applications that Work, Process Patterns, and More Process Patterns, has revised his acclaimed first book, The Object Primer. Long prized by both students and professionals as the best introduction to object-oriented technology, this book is now completely up-to-date, with all modeling notation rewritten in the just-released UML 2.0. All chapters have been revised to take advantage of Agile Modeling (AM), which is presented in the new chapter 2 along with other important new modeling techniques. Review questions at the end of each chapter allow readers to test their newly acquired knowledge. In addition, Ambler takes time to reflect on the lessons learned over the past few years by discussing the proven benefits and drawbacks of the technology. This is the perfect book for any software development professional or student seeking an introduction to the concepts and terminology of object technology. Previous Edition Pb (2001): 0-521-78519-7 Scott W. Ambler is a senior object consultant with Ronin International, Inc. and a popular speaker at conferences worldwide. He has worked with OO technology since 1990 as a business architect, system analyst, system designer, mentor, Smalltalk/C++/Java developer, and OO software process manager. He is a member of the IEEE Computer Society, the ACM, and Mensa.

Customer Reviews:

Great book for analysts too!!!!.......2005-12-13

I am an experienced analyst looking for an antidote to the RUPies use-case-jaundiced view of requirements. This book provided the perfect foil to the sentiment that use cases are all that is in the requirements universe.

It is not meant to be an exhaustive treatise of UML models, rather, it offers a different and, to me, refreshing view of what requirements for system building are supposed to be: agile, responsive and as varied as the projects that they are used on.

Additionally, the writing is light enough to be enjoyed and (what a novel idea) actually read. I have read Mr. Jacobson's books as well as Mr. Rumbaugh's. Albeit their authority status, their writing styles leave you wondering who they were writing for. It certainly wasn't me.

If you are looking for an alternative to the use-cases-as-panacea view of the world, this book will present a good fundamental look at how to get requirements written in a different way. And along the way, you will have a good time reading the book.

If you understand the target audience this is the best book on the market.......2005-07-11

For those who want a quick, fun introduction and intermediate mastery of UML 2.0 without getting sidetracked in all the esoteric notation that is rarely used, this is your book. I have used it since its release (and the edition before that) for teaching UML and good Object Oriented Design concepts. Many will throw stones (UML Purists that are more interested in UML Metamodel Purity then getting systems built for example) but don't let that phase you. If you need to learn UML 2.0 and have fun doing it, this book will do an incredible job for you. Scott writes in a very accessible style, not trying to show off his deep technical knowledge of UML (which he has). I admire him for writing this book as it is a tremendous service to our community. He simply wants people to get working as fast as possible. I admire his ability to have such a deep grasp of UML yet not flaunt it and distill things down to the necessary 20% that is all you need 80% of the time. More accurately, perhaps it is more accurate to say he covers the necessary 35%-40% that covers 90% of what you need to be effective.

The negative reviews come from people who are likely purists or are taken aback by his somewhat fun and informal style. As we have seen with books such as `Head First Design Patterns' I have seen greater success with books that take this format for people who are starting out. The other books can come later if needed.

You can buy much more academic books that will go into great detail on the semantic meanings of UML 2.0 model elements such as stereotypes that are almost never used or understood, advanced concepts in categorizing classes in a class diagram that are rarely used, etc. but you will rarely see any of them in practice. Rather then waste your time learning these items why not learn what you need to learn so you and your team can start communicating in Visual Diagrams as quickly and efficiently as possibly?

Kind Regards,
Damon Carr

Read This Book!.......2005-06-03

This book should really be called "Agile Models Distilled" or perhaps "Agile Model Driven Development". It does for modeling what UML Distilled does for UML: it provides a concise overview of a wide range of modeling techniques. One thing that is a real eye opener in this book is how many simple techniques exist work involving your users in the modeling process, as well as developers who may not want to learn the complex UML tools which management foists on them.

A huge benefit of the book is that it actually covers the entire software development lifecycle. It describes testing techniques that you can use throughout your project and shows how TDD fits together with modeling. The simple and straightforward approach to modeling that's covered in this book fits incredibly well with the TDD approach favored by many agile developers; it's a great way to increase your productivity as a developer. The book works through a case study, showing how to model and then code portions of a business application, so you get a pretty good idea how to actually do this stuff in practice.

This book shows how to be effective at modeling on agile projects, something few other books show how to do. It shows that you need to go beyond the UML although makes it clear that the UML is still an important part of your modeling effort. The book shows how it all fits together, but doesn't go into the excruciating details of how to apply each modeling
technique: if it did that it would be several thousand pages long. If you want to gain an understanding of the types of modeling skills you need to learn to be effective, this book is it.

A Good Book if You are the Right Audiance.......2004-08-23

This book is an overview of agile model-drive development, while uses a story about practice agile development for a university system. This application is so simple that it may take only one small incremental step to develop. The author does not care to complete this system at the end since he knows it is very simplistic. It is not necessary to carry out any refectory and iteration. On the journey, the author often stops to tell his experience and point out some treasures exposed along the path. However, at the end, you realize that you are still at Disney Land, although this time guided by a real pathfinder who repeatedly told us it is for real. The author provided several UML diagrams supposedly developed on a white board. But it makes no difference whatsoever if they are printed. They are just decorations to make it looks real. Actually, it is hard to read, as complained by other reviewers.

The main title of the third edition, The Object Primer, is misleading. This book is mainly about agile model-driven development, which is part of the subtitle. A better title of this book should be The Primer of Agile Model-Driven Development. This book does not teach you very much about object itself. Chapter 2 gives you a review of object-oriented concepts. If you are new to OO, such brief coverage will not help you very much. This is not a book that teaches you UML either. UML 2.0 is used throughout this book in straightforward cases. If you are new to UML, you have to read other books first.

This is a well-written book and you may learn a lot IF you are one of the targeted audiences. The author stated, this book is aimed at two primary audiences - existing developers and university/college students who want to gain the fundamental skills required to succeed on modern software development projects. The author give a quite "radical" (his own words) definition of developer as ANYONE involved in the development of a software applications, including programmers, analysts, designers, business stakeholders, database administrators, support engineers, and so on. I understand ANY author wants to sell his/her books as much as possible. But this author is established. He does not have to make us believe that the university registrar needs to read this book merely to be part of the team working on university system mentioned this book. My recommendation is that this book is really written for software developers and students who already have reasonable understanding and certain experience in terms of object-oriented approaches and UML, and they wish to have an overview on how to conduct agile development.

The author provided instructions on how to read this book. I somehow do not total agree with his recommendation. Below is my suggestion following his classification of different groups of readership.

For Programmers, Designers, and Project Managers, the author suggests them to read the entire book. I somehow feel different. If you are a project manager but not that technical, you will feel this book difficult if not impossible. If you are a project manager for a software development project merely since you are PMI certified, you have a lot to learn before you come to this book. If you are a VB programmer and you are not confident on what OO really means, you should read other books.

For Business Analysts and User Representatives, the author said Chapters 4 through 9 is written specifically for you. Well, this is 6 chapters with 144 pages out of a book of 12 chapters with 492 pages. Furthermore, I am not sure why the author believes you need to learn Singleton Design Pattern (12.2.1) and Façade Design Pattern (12.2.2).

For Students, the author asks you to read the book cover to cover. I agree with the author on this, as long as you are the right type of the students who have learned OO and UML and who needs to get the idea how agile approach works and how a project is developed conceptually. If you are still not sure about polymorphism, this book will not help you.

I am an experienced developer and I teach as well at university. I am within the targeted audiences of this book and I do buy many books. I completed this book within days after receiving it since it is quite readable. I am glad I added this book to my collection and I will certainly review it again and again, but perhaps mainly for my teaching duties.

I still give this book a 4-star rating since it gives us a good conceptual model kind of overview on agile model-driven development, with practical advices sometimes. However, he has yet had the time to implement his model (write more substance). He sees the needs of readers and he has made one more incremental deliverable, the 3rd edition. We hope he will get the feedback from us and make another try quickly, one with more implementations. For instance, since this book is an overview, the author should have provided references whenever necessary that lead us to further studies and discussions. The book contains a reference list with more than 100 entries at the end of the book. The problem is that the author expects a developer to figure out what references are relevant when he/she is reading a particular chapter or subject.

The list price of this book is $45; but it sells at $30 with Super Saver Shipping (free shipping) at Amazon.com. As a matter of fact, this book is free for me since I bought it by using the $30 discount I received when I signed up with Amazon Platinum Visa Card.

/* The statement and opinions expresses here are my own and do not necessarily represent those of my employer */

The Book to Give Your Friends Who "Don't Get It".......2004-08-20

The Object Primer is a great read. Scott walks you through the development lifecycle in clear and simple language. And all along the way, Scott points out the landmarks to the reader. Scott has a way of knowing just what a person needs.

For example, on page 122, Scott provides a basic list of twelve pointers for interviewing. How often was there a problem in requirements because of misunderstanding. These pointers address techniques they did not teach us in CS-101. The primer is full of helpful lists like these pointers. And who, besides Scott, would like to include this?

This new edition has been updated to reflect the emerging consensus of the Agile Modeling community. Whether you are a seasoned developer, a software development manager, or novice programmer, this book will provoke you to thoughtful consideration of how you develop software.

Systems Analysis and Design with UML Version 2.0: An Object-Oriented Approach

Average customer rating:

Confusing
A good set of core skills for object oriented system analyst
Systems Analysis and Design with UML Version 2.0 : An Object-Oriented Approach
Outstanding Reference on UML 2.0 & System Design
Pragmatic and consise!

Systems Analysis and Design with UML Version 2.0: An Object-Oriented Approach
Alan Dennis , Barbara Haley Wixom , and David Tegarden
Manufacturer: Wiley
ProductGroup: Book
Binding: Hardcover

Systems Analysis & Design | Computer Science | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

Qualifying Textbooks - Spring 2007 | Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design (2nd Edition) (The Addison-Wesley Object Technology Series)
Visual Modeling with Rational Rose 2002 and UML (3rd Edition)
Database Systems: Design, Implementation, and Management, Seventh Edition
Information Technology Project Management, Fourth Edition
UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering

Accessories:

Networking in the Internet Age
Managing and Using Information Systems: A Strategic Approach
Systems Analysis and Design , Casebook on CD-ROM

ASIN: 0471348066

Book Description

A modern, hands-on approach to doing SAD--in UML!
Get the core skills you need to actually do systems analysis and design with this highly practical, hands-on approach to SAD using UML! Authors Alan Dennis, Barbara Haley Wixom, and David Tegarden guide you through each part of the SAD process, with clear explanations of what it is and how to implement it, along with detailed examples and exercises that allow you to practice what you've learned.
Now updated to include UML Version 2.0 and revised, this Second Edition features a new chapter on the Unified Process, increased coverage of project management, and more examples.
Highlights
* Written in UML: The text takes a contemporary, object-oriented approach using UML.
* Focus on doing SAD: After presenting the how and what of each major technique, the text guides you through practice problems and then invites you to use the technique in a project.
* Rich examples of both success and failure: Concepts in Action boxes describe how real companies succeeded and failed in performing the activities in the chapters.
* Project approach: Each chapter focuses on a different step in the Systems Development Life Cycle (SDLC) process. Topics are presented in the order in which they are encountered in a typical project.
* A running case: This case threaded throughout the text allows you to apply each concept you have learned.

Customer Reviews:

Confusing.......2007-02-10

This book is just majorly confusing and really for the major eggheads. I'm using it because I have to for class but I'd rather go to another approach for learning this stuff. I'm using Learn to Program with C# by Smiley and it discusses some of the topics, from the early stages in the reading, as to the phases of development and because of that it helped me to understand this better. However, this stuff is really hard to grasp without the egghead mentality.

A good set of core skills for object oriented system analyst.......2006-03-11

The UML writing style of this book is very easy to follow, and a great way to gradually introduce the whole concept of object-oriented analysis and design methodologies to the readers, especially the beginners. The authors did a great job illustrating the entire system development life cycle with a coherent and realistic example using the latest UML notations, practical methodologies, and various analytical artifacts. The only criticism I have is that sometimes the description of a particular topic spans over multiple pages without sub-leveling or sub-topics or highlights, making it very difficult for user to go back and perhaps mine certain important concepts embedded in the discussion. Perhaps more generalization relationship and diagrams can be helpful. Overall, it is a very good source of reference for object-oriented design in layman's term. I will strongly recommend it to my colleagues.

Systems Analysis and Design with UML Version 2.0 : An Object-Oriented Approach.......2005-10-02

Item recived as presented

Outstanding Reference on UML 2.0 & System Design.......2005-08-27

I have looked at over twenty books on UML and its updates over the past few years, and this book is a gem.

It is concise, and provides a clear picture of the entire systems design process

It shows how UML 2.0 can be used to support system requirements capture, specification, analysis, and design.

It clearly says what is important and what is not, and what is not covered in the book.

Very pleasing to look at visually, with nice pictures and colors, and very good use of footnotes.

I would recommend this highly to all university faculty considering creating or teaching a course in system design using UML. Excellent job by the authors in exceeding the goals and expectations set by this book.

The above views are my personal views, and don't reflect those of any other institution.

I am using parts of it at a graduate course I teach at Georgia Tech.

Pragmatic and consise!.......2005-08-08

The book offers a very pragmatic approach to the subject of system analysis and design. It also has the advantage of not being dispersive, so the reader does never loose the focus. Repetition occurs only occasionally, for concepts that may be more hostile to digest.

The only thing that I reckon is missing is a support with some templates that is possible to use (e.g. a CD-ROM with examples of analysis and design).

Overall, I would say is a very good deal! Definitely worth having it!

Use Case Driven Object Modeling with UML: Theory and Practice

Average customer rating:

Great methodology, well explained
Well Written & Great Methodology
workable process, well-written book
Good book, very informative and well written.
Finally, the complete life cycle.

Use Case Driven Object Modeling with UML: Theory and Practice
Doug Rosenberg , and Matt Stephens
Manufacturer: Apress
ProductGroup: Book
Binding: Hardcover

General | Programming | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

Agile Development with ICONIX Process: People, Process, and Pragmatism
UML 2 Certification Guide: Fundamental & Intermediate Exams (The OMG Press)
The Elements of UML 2.0 Style
UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering
Writing Effective Use Cases

ASIN: 1590597745

Book Description

Use Case Driven Object Modeling with UML--Theory and Practice shows how to drive an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. In addition to a comprehensive explanation of the foundations of the approach, the book makes extensive use of examples and provides exercises at the back of each chapter.

This book leads by example. It demonstrates common analysis and design errors, shows how to detect and fix them, and suggests how to avoid making the same errors in the future. The book also encourages you to examine its UML examples and to search for specific errors. You'll get clues, then later receive the answers during "review sessions" toward the end of the book.

Customer Reviews:

Great methodology, well explained.......2007-05-26

The book combines explaining how to drive use cases to code and lots of examples. In fact one of the best parts is the 'bad example' followed by the corrected version - lots of those.

Iconix is pretty easy to use ONCE YOU UNDERSTAND IT. This book goes a long way toward understanding how to write good use cases that CAN be used for software development rather than just documentation.

I've read many, many use case books and this one boils the details down to something that is pragmatic. I've used the Iconix technique in both industry and the university and it works in both areas.

Good book? Yes. Buy it? Yes!

Well Written & Great Methodology.......2007-05-19

Easily one of the best methodology books I've read in quite some time. The book is very well written and flows very well. The structure walks you through the entire ICONIX process from beginning to end and explains in-detail the steps involved and most importantly "why". I also liked how the authors referenced other highly ranked OO books to reinforce how to allocate behavior to your objects during sequence diagraming.

I never heard of ICONIX until recently and I was very happy I got this book. The process is logical, stream-lined, and easy to pickup. The chapter on sequence diagrams just clicked for me and brought everything together.

I highly recommend this book!

workable process, well-written book.......2007-05-13

The book has a directness and simplicity that mirrors the development approach they describe; and, it covers more than "object modeling" - this is a complete concept-to-code approach which strikes a very nice balance. Excellent!

Good book, very informative and well written........2007-03-29

The introduction to the book starts with an interesting phrase "The difference between "theory" and "practice" is that in theory there is no difference between theory and practice, but in practice there is." The authors like to apply this statement to UML modeling, and continue later saying, in theory, everything in UML is useful, but in practice, a whole lot of people and projects need to know how to drive an OO software design from use cases.

Use Case Driven Object Modeling with UML-Theory and Practice shows how to take an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. The authors focus on one simple question, "how do you get from use cases to code?". The authors are real experts on the ICONIX process. This book is for Beginners as well as for advanced programmers. Beginners will learn a powerful methodology, Use-Case Driven Object Modeling. On the other hand, advance developers can apply Use Case to their preferred methodology.

The authors break down the design of an Internet bookstore, which involves showing many common mistakes, and then showing the relevant pieces of the model with their mistakes corrected. What really makes this book unique is the fact that you, the reader, get to correct the mistakes.
Chapter highlights

Highlights of this book include:

1. Each chapter starts with the theory, and then explores said theory using the Internet Bookstore project.
2. Each chapter has a "Top 10" list of guidelines, and the first half of each chapter is structured around its top 10 list.
3. This book also contains practical exercises of various types like, Workbook exercises, Student exercises and Inline exercises within the chapters.

Personally, I believe this is a very good book, very informative and well written. Before reading this book, I hadn't heard of ICONIX process, and this book did give me a good insight about the same. If you are sold on ICONIX and have been using it, the Top 10 list of guidelines, and the exercises at the end of each chapter in itself is worth the price of the book.

Finally, the complete life cycle........2007-03-24

I always liked Doug's ICONIX process for getting requirements through to initial design. It is better than any competing methodology, period. This time, however, he and Matt actually provide a concrete example of what it takes to get something built for real from that design. Now my developer friends will actually listen. Good stuff.

Object-Oriented Software Engineering: Using UML, Patterns and Java, Second Edition

Average customer rating:

Heavy reading
Excellent Book for Programmers Entering Software Development
Plagued with errors
You can't ask for better
For a first industry project !

Object-Oriented Software Engineering: Using UML, Patterns and Java, Second Edition
Bernd Bruegge , and Allen H. Dutoit
Manufacturer: Prentice Hall
ProductGroup: Book
Binding: Hardcover

General | Programming | Computers & Internet | Subjects | Books

Systems Analysis & Design | Computer Science | Computers & Internet | Subjects | Books

General | Operating Systems | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

Qualifying Textbooks - Spring 2007 | Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

Operating System Concepts
Introduction to Algorithms
Learning UML 2.0 (Learning)
Business Ethics
Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement

ASIN: 0130471100

Book Description

This widely used book teaches practical object-oriented software engineering with the key real world tools UML, design patterns and Java. This step-by-step approach allows the reader to address complex and changing problems with practical and state-of-the-art solutions. This book uses examples from real systems and examines the interaction between such techniques as UML, Java-based technologies, design patterns, rationale, configuration management, and quality control. It also discusses project management related issues and their impacts. A valuable book for development engineers, software engineers, consulting engineers, software architects, product managers, project leaders, and knowledge managers.

Customer Reviews:

Heavy reading.......2007-02-02

This is not the best. You can probably can get something else that it is not that heavy to read. No good for rookies.

Excellent Book for Programmers Entering Software Development.......2005-06-09

This is NOT a book on Unified Modeling Language (UML). It's not a book on Object Constraint Language (OCL). It's also not a book on Capability Maturity Models (CMM), Class-Responsibilities-Collaborators (CRC) cards, Decision Representation Language (DRL), Extreme Programming (XP), Gantt charts, Issue-Based Information Systems (IBIS), Joint Appication Design (JAD), Key Process Areas (KPA), the Liskov Substitution Principle, Model-View-Controller (MVC) architectural styles, Nonfunctional Requirements (NFR) Frameworks, Object Design Documents (ODD), PERT charts, the Questions-Options-Criteria (QOC) model, Requirements Analysis Documents (RAD), Royce's methodology, Software Configuration Management Plans (SCMP), System Design Documents (SDD), Software Project Management Plans (SPMP), the Unified Software Development Process, User Manuals, V-Models, Work Breakdown Structures (WBS), or any of the myriad other tools introduced in the book.

This IS a book to introduce newly-minted programmers to the kind of things, tools, and processes they can look forward to (with either anticipation or dread) in the real world of software development. As the authors state on page viii of the Preface:

"We have observed that students are taught programming and software engineering techniques in isolation, often using small problems as examples. As a result, they are able to solve well-defined problems efficiently, but are overwhelmed by the complexity of their first real development experience, when many different techniques and tools need to be used and different people need to collaborate."

It's been many years since I was involved in major software development projects (and those were all in the military). But, this book seems to have covered everything that all new programmers need to know so that they aren't simply lost when they enter their first software project. The readers certainly won't be experts in the things covered, but they'll at least have a good grounding and be able to bootstrap themselves from there (especially since the authors provide "Further Readings" and a Bibliography at the end of each chapter). For instance, on page 71, under Further Readings, they list three works on UML: one of which is the 566 page official specification, "OMG Unified Modeling Language Specification."

Overall, this is an excellent book for anyone who is just entering the software development world. I rate it at 5 stars out of 5.

As a side note, Florida State University (FSU) uses this book in its COP 3331: "Object-Oriented Analysis and Design" course.

Plagued with errors.......2005-04-22

It is a highly readable book. The authors are good at explaining concepts with clarity.

But the book is sloppy in any area that requires precision. They make no distinction of the four kinds of message sending in sequence diagrams. It is important for a UML user to differentiate synchronous, asynchronous, return and flat arrows. Otherwise a diagram will have different meaning. The authors use indiscriminately the notation of synchronous message when most of messages in their diagrams should be asynchronous.

The coverage on OCL is even worse. More than half of the OCL constraints are wrong!!!

You cannot rely on the corrections found on the authors' website because it only contains minor typos but misses the serious mistakes.

Though it is more prescriptive than the standard software engineering books such as the ones by Pressman and Sommerville, I would NOT recommend its use as a textbook due to the many errors. I found "Object-oriented Systems Analysis and Design" by Bennett, McRobb and Farmer a better how-to book in software engineering.

You can't ask for better.......2005-03-04

I'm currently following a Msc in Software Development in England. This book is very good. Finally an excellent source to go through in all its aspects. Examples as well as explanations are clear, sound, and solid. The book provides short, though detailed definitions that avoid verbose and useless comments. The book is guiding the reader through the explanation of how to carry out and accomplish a real project. What I mostly like is the heuristics given for identifing and setting forth all the artifacts needed during Requirements Elicitation and Analysis. Hat off to the authors of this great reference.

For a first industry project !.......2005-01-30

The book is definitely a guide telling you how to do right thing in a right way. Good introduction to UML and show you how to prepare document for your customer.
Highly recommend !!!

Unified Modeling Language User Guide, The (2nd Edition) (The Addison-Wesley Object Technology Series)

Average customer rating:

Waste of money.
Misleading tutorial on UML 2.0
Hi Mr. Book Disposal
Do not buy this book for UML learning
Historical, strongly structured and thorough reference

Unified Modeling Language User Guide, The (2nd Edition) (The Addison-Wesley Object Technology Series)
Grady Booch , James Rumbaugh , and Ivar Jacobson
Manufacturer: Addison-Wesley Professional
ProductGroup: Book
Binding: Hardcover

Booch, Grady | Authors, A-Z | Computers & Internet | Subjects | Books

Jacobson, Ivar | Authors, A-Z | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

Look Inside Computer Books | Trip | Specialty Stores | Books

Qualifying Textbooks - Spring 2007 | Stores | Books

General | Software Books | Custom Stores | Stores | Software
Similar Items:

Unified Modeling Language Reference Manual, The (2nd Edition) (The Addison-Wesley Object Technology Series)
UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition
The Unified Software Development Process
Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series)
UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design (2nd Edition) (The Addison-Wesley Object Technology Series)

ASIN: 0321267974

Amazon.com

One of the most important recent developments in software engineering is the Unified Modeling Language (UML) standard for documenting software designs. Written by UML's inventors (the so-called Three Amigos of software engineering), The Unified Modeling Language User Guide provides a very appealing guide to all the fundamentals of using UML effectively. The book opens with a basic tour of the essential concepts and modeling diagrams used in UML, including class diagrams, use case diagrams, and basic modeling principles. The authors pay close attention to modeling classes (and documenting the relationships between classes) as well as use case diagrams (which show how software will be used by various actors in a system). This book mixes in a little software-engineering theory, too, but it makes use of clear examples and actual UML diagrams to illustrate key concepts.

Later in the book, the authors discuss more difficult notational diagrams (such as state diagrams and activity diagrams, which can be used to model behavior in a system). Whatever your background in software engineering, you'll no doubt appreciate the author's clear explanations of basic (and advanced) modeling concepts, as well as the nuts-and-bolts details of today's powerful UML. With its combination of expert modeling advice and excellent detail on the specifics of UML, this book will be absolutely essential reading for anyone who wants to use UML for real-world software design. --Richard Dragan

Customer Reviews:

Waste of money........2007-01-04

Book is complete waste of money. Find more prevalent information online. Not really a required book. Not used at all.

Misleading tutorial on UML 2.0.......2006-02-27

I picked up this book as a way to familiarize myself with the changes to UML in UML 2.0, which are extensive, as I found the OMG specification nearly impenetrable. I had liked the first edition, though I too felt Fowler's Distilled was a much better intro to give to students and engineers learning UML for the first time. This edition, though, does not meet expectations. The typos and bad references throughout are bad enough. Join that with a complete lack of real-world design examples, poor organization, and poor design. Why a chapter on State Machines and a separate chapter on State Diagrams that repeats a lot of the earlier chapter? The blue cross references make it clear that the book is spaghetti design at its worst. Check out the table of contents, you won't know where to look for your favorite diagrams; check out the index, and you won't be able to find the definition of the concept you just can't quite remember. The glossary is useful, as the UML 2.0 spec dispensed with a glossary, making it even more impenetrable. On the other hand, the authors make no attempt to call out the new UML 2.0 features, which would have made my day. What I find most unforgivable, though, is the authors' inability to present the new UML as it really is: the book is seriously misleading in many ways for learning UML 2.0. My biggest peeve is the way they treat the new and highly useful composite structure diagrams. In the list of diagrams, they don't even mention it, calling it by the name of a different diagram, the "Component Diagram", which they feel is the same thing. They then separate the discussion of composite classes and components, making it seem as though they're totally unrelated. They fail to mention quite a few of the new UML features (the X navigation adornments that make non-navigability explicit, for example, which is critical to code generation, or the fact that you can have multiple stereotypes associated with model elements. In their defense, the UML standard isn't very clear on these diagram types, but this is a practical tutorial that should take practice into account. There are constant references to the Reference Guide for more advanced features; these are mostly the UML 2.0 features that they didn't feel were important enough to include in the comprehensive tutorial. The appendix on UML notation simply ignores many UML 2.0 notations. I can't help but feel shortchanged.

Hi Mr. Book Disposal.......2006-02-08

Start reading Chapter 1 of this book for even just the first few pages, and for various topics, it will say to go to future Chapters. If you take a look at those future chapters, there will be notes on the side telling you to go back to Chapter 1 or to other chapters. You can run into infinite loops or dead ends not really picking up anything. It is possible to maybe find what you were looking for, or find that the explanation for it is just not