Авторизация
Поиск по указателям
Miles R., Hamilton K. — Learning UML 2.0
Обсудите книгу на научном форуме
Нашли опечатку? Выделите ее мышкой и нажмите Ctrl+Enter
Название: Learning UML 2.0
Авторы: Miles R., Hamilton K.
Аннотация: "Since its original introduction in 1997, the Unified Modeling Language has revolutionized software development. Every integrated software development environment in the world—open-source, standards-based, and proprietary—now supports UML and, more importantly, the model-driven approach to software development. This makes learning the newest UML standard, UML 2.0, critical for all software developers—and there isn't a better choice than this clear, step-by-step guide to learning the language." —Richard Mark Soley, Chairman and CEO, OMG
If you're like most software developers, you're building systems that are increasingly complex. Whether you're creating a desktop application or an enterprise system, complexity is the big hairy monster you must manage.
The Unified Modeling Language (UML) helps you manage this complexity. Whether you're looking to use UML as a blueprint language, a sketch tool, or as a programming language, this book will give you the need-to-know information on how to apply UML to your project, While there are plenty of books available that describe UML, Learning UML 2,0 will show you how to use it. Topics covered include:
• Capturing your system's requirements in your model to help you ensure that your designs meet your users' needs
• Modeling the parts of your system and their relationships
• Modeling how the parts of your system work together to meet your system's requirements
• Modeling how your system moves into the real world, capturing how your system will be deployed
Engaging and accessible, this book shows you how to use UML to craft and communicate your project's design. Russ Miles and Kim Hamilton have written a pragmatic introduction to UML based on hard-earned practice, not theory. Regardless of the software process or methodology you use, this book is the one source you need to get up and running with UML 2.0. Additional information including exercises can be found at www.learninguml2.com.
Russ Miles is a software engineer for General Dynamics UK, where he works with Java and Distributed Systems, although his passion at the moment is Aspect Orientation and, in particular, AspectJ. Kim Hamilton is a senior software engineer at Northrop Grumman, where she's designed and implemented a variety of systems including web applications and distributed systems, with frequent detours into algorithms development.
Язык:
Рубрика: Технология /
Статус предметного указателя: Готов указатель с номерами страниц
ed2k: ed2k stats
Год издания: 2006
Количество страниц: 286
Добавлена в каталог: 23.10.2006
Операции: Положить на полку |
Скопировать ссылку для форума | Скопировать ID
Предметный указатель
"Architectural BlueprintsThe "4+1" View Model of Software Architecture" (Krutchen)
# (hash symbol), protected visibility
( ) (parentheses), annotations
+ (plus symbol)
+ (plus symbol), public visibility 2nd
- (minus symbol), private visibility 2nd
4+1 view model (Krutchen) 2nd
: (colon)
: (colon), in attribute name
: (colon), in operation signature
:: (double colons), in fully-scoped class name
<< >> (guillemots), stereotypes 2nd
<<access>> stereotype
<<apply>> stereotype
<<artifact>> stereotype
<<component>> stereotype
<<deploy>> stereotype
<<deployment spec>> stereotype
<<device>> stereotype
<<executable>> stereotype
<<executionEnvironment>> stereotype
<<extend>> relationships
<<file>> stereotype
<<import>> stereotype
<<include>> relationships
<<library>> stereotype
<<manifest>> stereotype
<<realizations>> stereotype
<<service>> stereotype
<<source>> stereotype
<<subsystem>> stereotype
<<utility>> stereotype
Abstract classes 2nd
abstraction level of classes
Actions
actions, in Activity diagram
actions, inputs and outputs for
actions, objects passed between
actions, parallel
actions, transformations of objects between
activation bars
activation bars, indicating active participant
activation bars, return messages at end of
active states
Activities
activities, called within Activity diagram
activities, changing state of object
activities, enclosing in activity frame
activities, ending 2nd
activities, flow of
activities, inputs and outputs for
activities, interrupting
activities, naming
activities, starting 2nd
Activity diagram 2nd
Activity diagram, actions in
Activity diagram, calling other activities from
Activity diagram, compared to Interaction Overview diagram
Activity diagram, concurrent tasks in
Activity diagram, connectors in
Activity diagram, decisions in 2nd
Activity diagram, edges in
Activity diagram, ending
Activity diagram, ending flows in
Activity diagram, expansion regions in
Activity diagram, final node in
Activity diagram, guard conditions in
Activity diagram, in process view
Activity diagram, initial node in
Activity diagram, inputs and outputs for
Activity diagram, interrupting
Activity diagram, merges in 2nd
Activity diagram, objects in
Activity diagram, partitions in
Activity diagram, signals to and from external participants
Activity diagram, starting
Activity diagram, time events in
Activity diagram, when to create
activity final nodes
activity final nodes, in Activity diagram
activity final nodes, multiple
activity final nodes, object output as alternative to
activity frame 2nd
actors 2nd
actors, generalizations used with
actors, naming
actors, notation for
actors, participation with use cases, showing
actors, primary actor for use case
actors, relationships between
actors, system boundaries excluding
actors, tricky actors
aggregation between classes
agile methods of software development
Agile Software Development (Prentice Hall)
alt fragment
angle brackets (<< >>), stereotypes 2nd
annotations for partitions, Activity diagram
anonymous objects
arrows
arrows, arrowed lines (edges)
arrows, connecting states (transitions)
arrows, dependency arrows 2nd
arrows, dotted arrow (<<include>> relationships)
arrows, empty diamond arrowhead (aggregations)
arrows, extension arrow in profile
arrows, filled diamond arrowhead (compositions)
arrows, generalization arrow
arrows, generalization arrow, class inheritance
arrows, generalization arrow, use case inheritance
arrows, message arrows 2nd
arrows, on communication lines
arrows, on state-lines
Artifacts
artifacts, dependencies between
artifacts, deploying to a node
artifacts, deployment specifications as
artifacts, manifesting components
artifacts, notation for
artifacts, of components
artifacts, stereotypes applied to
assembly connectors 2nd
assert fragment
association classes
associations between classes
associations between classes, attributes representing 2nd
associations between classes, object links requiring
associations between classes, properties representing
Asynchronous messages 2nd 3rd
Attributes 2nd
attributes, as collections of objects (multiplicity)
attributes, associated with another class 2nd
attributes, inline attributes 2nd
attributes, naming
attributes, private visibility for, when to use
attributes, properties of
attributes, public visibility for, when to use
attributes, static
attributes, type of
attributes, visibility of
base use cases
behavioral state machines
binding templates
black-box component views
blueprint, UML used as
BPM (business process management) tools
brackets ([ ])
brackets ([ ]), guard conditions
brackets ([ ]), multiplicities on connectors
break fragment
business process management (BPM) tools
Business processes
call activity node
Chain of Responsibility (COR) design pattern
child classes
choice pseudostates
Class diagram 2nd
Class diagram, abstract classes in
Class diagram, attributes in
Class diagram, class relationships in
Class diagram, constraints in
Class diagram, in logical view
Class diagram, interfaces in
Class diagram, operations in
Class diagram, Package diagram modeled using
Class diagram, static class elements in
Class diagram, templates in
Class diagram, when not to use
Class diagram, when to create
class invariant
Classes
classes, abstract classes 2nd
classes, abstraction level of
classes, aggregation between
classes, association classes
classes, associations between 2nd
classes, attributes of 2nd
classes, compared to components
classes, composition relationship between 2nd
classes, constraints for 2nd
classes, delegation and
classes, dependencies between
classes, encapsulation and
classes, generalization relationship between
classes, interfaces for 2nd 3rd
classes, internal structures of
classes, name of
classes, notation for
classes, operations of 2nd
classes, parts of
classes, ports for 2nd
classes, public interface of
classes, realizing components
classes, relationships between 2nd
classes, static
classes, stereotypes applied to
classes, templates for 2nd
classes, tightly coupled 2nd
classes, visibility of elements in
clock, system, as tricky actor
collaborations 2nd
colon (:)
colon (:), in attribute name
colon (:), in operation signature
colons, double (::), in fully-scoped class name
Communication diagram 2nd
Communication diagram, communication links in 2nd
Communication diagram, compared to Sequence diagram 2nd
Communication diagram, creating from interactions
Communication diagram, in logical view
Communication diagram, incorporated into Interaction Overview diagram
Communication diagram, messages in 2nd
Communication diagram, messages, invoked conditionally
Communication diagram, messages, invoked multiple times
Communication diagram, messages, nested
Communication diagram, messages, sent by pariticipant to itself
Communication diagram, messages, simultaneous
Communication diagram, participants in 2nd
Communication diagram, when to create 2nd 3rd 4th
Communication diagram, when to use
communication lines
communication links 2nd 3rd
communication paths between nodes
Component diagram 2nd
Component diagram, components in
Component diagram, dependencies in
Component diagram, in development view
Component diagram, interfaces in
Component diagram, internal structures in
Component diagram, ports in
Component diagram, realizing classes in
Component diagram, views of components in
components
components, as subsystems
components, black-box view of
components, compared to classes
components, dependencies between
components, interfaces for 2nd
components, internal structure of
components, notation for
components, ports for
components, realized by classes
components, stereotypes applied to
components, white-box view of
composite states
Composite Structure diagram
Composite Structure diagram, classes with internal structures in
Composite Structure diagram, collaborations in
Composite Structure diagram, connectors in
Composite Structure diagram, objects with internal structures in
Composite Structure diagram, parts of classes in
Composite Structure diagram, ports in
Composite Structure diagram, properties in
Composite Structure diagram, when to create 2nd
Composite Structure diagram, when to use
composition relationship between classes 2nd
concurrent tasks, Activity diagram
Connectors
connectors, in Activity diagram
connectors, in Component diagram 2nd
connectors, in Composite Structure diagram
Constraints
constraints, for classes
constraints, for classes, in Class diagram
constraints, for classes, in Object diagram
constraints, in profiles
constraints, timing constraints
Constructors
COR (Chain of Responsibility) design pattern
create message 2nd
critical regions
curly braces ({ }), constraints
decisions, Activity diagram 2nd
Delegation
delegation connectors
Dependencies
dependencies, between artifacts
dependencies, between classes
dependencies, between components
dependencies, between packages
Deployment diagram 2nd
Deployment diagram, artifacts (files) in
Deployment diagram, communication paths in
Deployment diagram, execution environments in
Deployment diagram, hardware in
Deployment diagram, in physical view
Deployment diagram, nodes in
Deployment diagram, when to create
Deployment diagram, when to use
deployment specifications
Design patterns
design patterns, abstract classes and
design patterns, collaborations as
Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley) 2nd 3rd
destroy message
destroy method
development view 2nd
diagram notations
diagram notations, "t" in Timing diagram 2nd
diagram notations, arrows
Реклама