Sue Brandreth's Learning Resources

Fowler, M. with Scott, K. (2003) UML Distilled – A Brief Guide to the Standard Object Modeling Language (Object Technology Series),  Third Edition, Addison-Wesley

Download eBook PDF (PDF 7,564KB)

Companion Web Site: http://martinfowler.com/books/uml.html

The long-awaited third edition of the best-selling UML book on the market; fully-updated and compliant with UML 2.0. This eagerly-anticipated third edition gets students thinking about efficient object-oriented software design using the latest version of the industry-standard for modeling software: UML 2.0. The author has retained the book’s convenient, concise format that has made it an essential resource in courses introducing UML. The book describes all the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them. A true treasure for the software engineering community.

Pressured with tight deadlines, application developers do not have the luxury of keeping completely up-to-date with all of the latest innovations in software engineering. Once in a great while, a tremendous resource comes along that helps these professionals become more efficient.
The first two editions of UML Distilled have been perennial best-sellers because of their concise, yet thorough, nature. This eagerly-anticipated third edition allows you to get acquainted with some of the best thinking about efficient object-oriented software design using the latest version of the industry-standard for modeling software: UML 2.0. The author has retained the book’s convenient format that has made it an essential resource for anyone who designs software for a living. The book describes all the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them. A true treasure for the software engineering community.

Table of Contents

Why bother with the UML?

• What Is the UML?
• Ways of Using the UML.
• How We Got to the UML.Notations and Meta-Models.
• UML Diagrams.
• What is Legal UML?
• The Meaning of UML.
• UML is not enough.
• Where to Start with the UML.
• Looking for More Information.

2. Development Process.

• Iterative and Waterfall Processes.
• Predictive and Adaptive Planning.
• Agile Processes.
• Rational Unified Process.
• Fitting a Process to a Project.
• Fitting the UML into a process.
• Understanding Legacy Code.
• Choosing a Development Process.
• Where to Find Out More.

3. Class Diagrams: The Essentials.

• Properties.Attributes.
• Associations.
• Multiplicity.
• Programming Interpretation of Properties.
• Bi-directional Associations.
• Operations.
• Generalization.
• Notes and Comments.
• Dependency.
• Constraint Rules.
• When to Use Class Diagrams.
• Where to Find Out More.

4. Sequence Diagrams.

• Creating and deleting participants.
• Loops, conditionals and the like.
• Synchronous and Asynchronous Calls.
• When to use Sequence Diagrams.

5. Class Diagrams: Advanced Concepts.

• Keywords.
• Responsibilities.
• Static Operations and Attributes.
• Aggregation and Composition.
• Derived Properties.
• Interfaces and Abstract Classes.
• Read Only and Frozen.
• Reference Objects and Value Objects.
• Qualified Associations.
• Classification and Generalization.
• Multiple and Dynamic Classification.
• Association Class.Template (Parameterized) Class.
• Enumerations.Active Class.
• Visibility.Messages.

6. Object Diagrams.

• When to use Object Diagrams.

7. Package Diagrams.

• Packages and Dependencies.
• Package Aspects.
• Implementing Packages.
• Where to Find Out More.
• When to Use Package Diagrams.

8. Deployment Diagrams.

• When to use deployment diagrams.

9. Use Cases.

• Content of a Use Case.
• Use Case Diagrams.
• Levels of Use Cases.
• Use cases and features (or stories).
• When to Use Use Cases.
• Where to Find Out More.

10. State Machine Diagrams.

• Internal Activities.
• Activity States.
• Superstates.Concurrent States.
• Implementing State Diagrams.
• When to Use State Diagrams.
• Where to Find Out More.

11. Activity Diagrams.

• Decomposing an action.
• Partitions.
• Signals.
• Tokens.
• Flows and Edges.
• Pins and Transformations.
• Expansion Regions.
• Flow Final.
• Join Specifications.
• And there’s more.
• When to Use Activity Diagrams.
• Where to Find Out More.

12. Communication Diagrams.

• When to use Communication Diagrams.

13. Composite Structures.

• When to Use Composite Structures.

14. Component Diagrams.

• When to use Component Diagrams.

15. Collaborations.

• When to Use Collaborations.

16. Interaction Overview Diagrams.

• When to use Interaction Overview Diagrams.

17. Timing Diagrams.

• When to use Timing Diagrams.

Appendix A Changes between UML Versions.

• Revisions to the UML.
• Changes in UML Distilled.
• Changes from UML 1.0 to 1.1.
• Type and Implementation Class.
• Complete and Incomplete Discriminator Constraints.
• Composition.Immutability and Frozen.
• Returns on Sequence Diagrams.
• Use of the Term “Role”.
• Changes from UML 1.2 (and 1.1) to 1.3 (and 1.5).
• Use Cases.Activity Diagrams.
• Changes from UML 1.3 to 1.4.
• Changes from UML 1.4. to 1.5.
• From UML 1.x to UML 2.0.
• Class Diagrams (Basic).
• Interaction Diagrams.
• Class Diagrams (Advanced).
• State Diagrams.
• Activity Diagrams.

Bibliography.

O’Docherty, M. (2005) Object-Oriented Analysis and Design – Understanding System Development with UML 2.0, John Wiley and Sons, Ltd

Download eBook PDF (PDF 8,485KB)

Companion Web Site: http://eu.wiley.com/legacy/wileychi/odocherty/

Covering the breadth of this core topic, Object-Oriented Analysis and Design provides a thorough grounding in object-oriented concepts, the software development process, UML and multi-tier technologies. Beginning with the basic ground work underpinning object-oriented software projects, it follows the steps of a typical development project (Requirements Capture, Design, Specification & Testing), showing how an abstract problem is taken through to a concrete solution. The authors take a programming language agnostic approach – so code is kept to a minimum to avoid detail and deviation into implementation minutiae.

A single case study running through the text provides a realistic example of software development, from an initial proposal through to a finished system. Key artefacts such as the requirements document and detailed designs are included, plus exercises in each aspect of the case study,  to enable readers to  produce similar documents for a different system.

Table of Contents

Schmuller, J. (2004) Sams Teach Yourself UML in 24 Hours: Complete Starter Kit, Third Edition, Sams Publishing

Download eBook PDF (PDF 4,269KB)

Bennet, Simon, McRobb, Steve and Farmer, Ray (2010 ) Object-Oriented Systems Analysis and Design Using UML, Fourth Edition, McGraw-Hill Education

Student Companion Website: http://highered.mcgraw-hill.com/sites/0077125363/student_view0/

PowerPoint Preentations

01 02

04_04 04_05a 04_05b 04_05c 04_06a 04_06b 04_07a 04_07b 04_08 04_09a 04_09b 04_09c 04_10 04_11 04_12 04_13 04_14 04_15 04_16 04_17 04_18 04_19 04_20 04_21a 04_21b

The fourth edition of Object- Oriented Systems Analysis and Design has been revised and updated to reflect the most up-to-date approaches to information systems development. Still a best-seller in its field, Bennett’s, McRobb’s and Farmer’s text remains a key teaching resource for Systems Analysis and Design courses at both undergraduate and postgraduate level.

The book provides a clear, practical framework for development that uses all the major techniques from UML 2.2. It follows an iterative and incremental approach based on the industry-standard Unified Process, placing systems analysis and design in the context of the whole systems lifestyle. Structured in four parts, the first provides the background to information systems analysis and design and to object-orientation. The second part focuses on the activities of requirements gathering and systems analysis, as well as the basic notation of UML. Part three covers the activities of systems architecture and design, and UML notation for object design, and the book concludes with the implementation of systems and the issues of how the systems life cycle is organized and how reusable components can be developed.

Table of Contents

Tegarden, David, Dennis, Alan, Wixam, Barabara Haley (2013) System Analysis and Design UML Version 2.0 – An Object-Oriented Approach, International Student Version, Fourth Edition, John Wiley and Sons

The Fourth edition of Dennis/Wixon/Tegarden′s Systems Analysis and Design with UML continues to offer a concise, modern and applied introduction to OO SAD. The new edition offers updated material, more hands–on exercises, and more applied examples. Furthermore a new emphasis on agile methods tackles programming issues and on business process modeling and ethics to add strategic coverage that appeals to IS majors. Additional coverage of new mobile devices and tablets refresh the content as well as supplementary material, including minicases, coverage of ethics, business process modeling, mobile applications and better illustrations, examples, and exercises.

Table of Contents

Grassle, P., Baumann, H. and Baumann, P. (2005) UML 2.0 in Action – A Project Based Tutorial – A Detailed and Practical Walk-through showing how to apply UML to Real World Development Projects, Packt Publishing

Download eBook PDF (PDF 6,707KB)

If you’ve read the UML documentation or a guide to the UML syntax, but don’t feel you really know where to start with UML on a live project, then this unique book is what you need. Written as a practical case study, the book sets out to give you the intuitive feel for UML you need to confidently add it to your core development toolkit. The authors walk through a rich analysis and design scenario, explaining which parts of UML to use, and how to use them. The emphasis is on the systematic and practical application of UML to real business cases. The book was written for business analysts, technical architects and developers. It does not require detailed programming knowledge, nor is prior experience of UML mandatory. It shows how, with UML, simple models of business processes and specification models can be created and read with little effort.