IBM的rose培训笔记小结内容介绍

参加了IBM rose的培训和考试，看课件后，留下的简单的摘抄笔记。

Module 0: About This Course
understand the value of modeling to
.. Improve communications among team
members through the use of a standard
language (UML).
.. Expose software development problems early.
.. Manage software complexity.

curriculum [简明英汉词典]
[kE5rikjulEm]
n.课程

competence [简明英汉词典]
[5kRmpEtEns]
n.能力

Course Organization
.. Module 1: Visual Modeling and the UML
Time: 30 minutes
.. Introduces both visual modeling and the UML.
.. Module 2: Rose Modeling Basics
Time: 30 minutes
.. Introduces the Rational Rose interface and
basic features.
.. Module 3: Using Rose in a Team
Time: 45 minutes
.. Introduces features in Rational Rose that
facilitates developing in a team.
.. Module 4: The Use-Case Model
Time: 90 minutes
.. Defines the use-case model and its elements.
.. Module 5: Use-Case Realization Structure
Time: 30 minutes
.. Defines the elements of the use-case
realization structure.
.. Module 6: Interaction Diagrams
Time: 90 minutes
.. Begins with a discussion on classes, followed by both types of interaction diagram sequence and collaboration.
.. Module 7: Class Diagrams
Time: 60 minutes
.. Discusses the final piece of the use-case realization structure, the class diagram.
.. Module 8: Introduction to Round-Trip Engineering
Time: 30 minutes
.. Introduces round-trip engineering followed by a brief demonstration.

Module 1: Visual Modeling and the UML
Visual Modeling is modeling using standard graphical notations

Use-case analysis is a technique to capture business processes from a user’s perspective.

The UML is the standard language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system.

The UML combines the best from
.. Data modeling
.. Business modeling
.. Object modeling
.. Component modeling

A use-case diagram is created to visualize the interaction of your system with the outside world.

An activity diagram shows the flow of events within our system.

A sequence diagram shows step by step what must happen to accomplish a piece of functionality provided by the system.

A collaboration diagram displays object interactions organized around objects and their links to one another.

A class diagram shows the structure of your software.

A statechart diagram shows the lifecycle of a single class.

A component diagram illustrates the organization and dependencies among software components.

A deployment diagram visualizes the distribution of components across the enterprise.s

.. Stereotypes can be used to extend the UML notational elements.
.. Stereotypes may be used to classify and extend associations, inheritance relationships, classes, and components.

Module 2: Rose Modeling Basics
Models are constructed using views to depict different perspectives and diagrams to depict a system’s building blocks.

A view is a perspective of the model that is meaningful to specific stakeholders.

The Use-Case View is the “heart” of the other views because it specifies WHAT the system should do.

The Logical View supports the functional requirements of the system.

The Process View addresses the performance, scalability, and throughput of the system.

In Rose, the Implementation View is called the Component View.The Component View addresses ease of development, management of software assets, reuse, sub-contracting, and off-theshelf components.

The Deployment View addresses issues like deployment, installation, and performance.

A diagram is a graphical means to view a system’s parts, including classes, interfaces,collaborations, components, nodes,dependencies, generalizations, and associations.

Module 3: Using Rose in a Team
Rational Rose supports
.. Controlled evolution of the model.
.. Partitioning of models into architecturally significant units.
.. Reuse of architecturally significant model elements.

A virtual path map allows models to be moved between different folder structures and to be updated from different workspaces.

Reuse refers to archiving and maintaining artifacts for future projects.

.. Rational Rose supports controlled evolution, partitioning and reuse.
.. A package is the smallest element that can be a controlled unit.
.. A controlled unit is a model element that can be placed under version control.
.. Model itself (.mdl)
.. Use-Case and Logical View packages (.cat)
.. Component View packages (.sub)
.. Deployment View diagram (.prc)
.. Model elements (.prp)

.. Controlled units can be loaded or unloaded to reduce startup latency.
.. A model workspace is a snapshot of all currently loaded controlled units and open diagrams.
.. Virtual path maps allow models to be moved between different folder structures and to be updated from different workspaces.

.. Reuse refers to archiving and maintaining artifacts for future projects. Rose supports reuse with the following
.. Frameworks
.. Architecturally-significant packages
.. Subsystems
.. Mechanisms
.. Rose uses two version control add-ins
.. Version Control Add-In (for SCC-compliant version control systems)
.. ClearCase Add-In

The Model Integrator is a stand-alone tool that can be used to
.. Compare the differences between Rose models.
.. Merge different Rose models into a resultant model.

Module 4: The Use-Case Model
.. The why and what of a use-case model
.. A use-case model allows the customer and system developer to communicate WHAT the system should do, in a language understandable to the customer.
.. Consider the use-case model as the visual contract between customer and developer.

.. A use-case model is representation of the system intended functions and its environment.
.. It is created in the Use-Case View and can include the following
.. Use-case diagrams
.. Use-case flow of events
.. Supplemental information
.. Activity diagrams

.. Elements of a use-case diagram
The use-case realization structure includes the following elements
.. Use-case realization packages
.. Traceabilities diagrams
.. Interaction diagrams
.. Class diagrams

.. Flow of events and project artifacts
.. Elements of an activity diagram
.. Reports

A class is a set of objects that share the same attributes, operations, relationships,and semantics.

A relationship is a semantic connection among elements.

A generalization is a parent/child relationship where one class shares the structure and behavior of one or more classes.

Module 8: Introduction to Round-Trip Engineering
Round-trip engineering helps maintain architectural integrity.
.. Detect and assess architectural changes
.. Communicate accepted architectural changes
.. Synchronize your model and source code
during every iteration

.. Round-trip engineering is the ability to move back and forth between model and code.
.. Round-trip engineering helps maintain architectural integrity.
.. Round-trip engineering differs among implementation languages.

Essentials of Visual Modeling with UML
Module 1: Introduction to Object Technology
A set of principles (abstraction,encapsulation,polymorphism) guiding software construction,together with languages,databases, and other tools that support those principles. (Object Technology - A Manager’s Guide, Taylor,1997.)

Object-orientation (OO)
.. Melds the data and data flow process together early in the lifecycle
.. Has a high level of encapsulation
.. Promotes reuse of code differently
.. Permits more software extensibility

Module 2: Principles of Visual Modelin
A model is a simplification of reality.

Module 2: Principles of Visual Modeling
.. The model you create influences how the problem is attacked.
.. Every model may be expressed at different levels of precision.
.. The best models are connected to reality.
.. No single model is sufficient.

Principle 1: The Choice of Model Is Important
Principle 2: Levels of Precision May Differ
Principle 3: The Best Models Are Connected to Reality
Principle 4: No Single Model Is Sufficient

The UML is a language for
..Visualizing
..Specifying
..Constructing
..Documenting
the artifacts of a software-intensive system.

The UML is largely process independent. A process fully benefits from the UML when the process is:
.. Use-case driven
.. Architecture-centric
.. Iterative and incremental

Module 3: Concepts of Object Orientation
An object is an entity with a well-defined boundary and identity that encapsulates state and behavior.

What Is Polymorphism?
The ability to hide many different implementations behind a single interface.

Module 4: Use-Case Modeling
What Is a Use-Case Model?
.. A use-case model is representation of the
system’s intended functions and its
environment.
.. It is created in the Use-Case View and
can include the following
.. Use-case diagrams
.. Use-case flow of events
.. Supplemental information
.. Activity diagrams

What Are Artifacts?
.. Artifacts are documents, models, or model elements used to capture and convey project information.
.. In Rose, you will attach only those artifacts important to maintaining the use-case model.

What Is an Activity Diagram?
.. An activity diagram in the use-case model can be used to capture the activities in a use case.
.. It is essentially a flow chart, showing flow of control from activity to activity.

Activity
.. An activity represents the performance of a task within the workflow.
.. In the UML, an activity is represented by a lozenge (horizontal top and bottom with convex sides).

Module 1: Best Practices of Software Engineering
Practice 1: Develop Iteratively
Practice 2: Manage Requirements
Practice 3: Use Component ArchitecturesResilient Component-Based Architectures
Practice 4: Model Visually (UML)
Practice 5: Continuously Verify Quality
Practice 6: Manage Change

.. Best Practices guide software engineering by addressing root causes.
.. Best Practices reinforce each other.
.. Process guides a team on who does what,when, and how.
.. The Rational Unified Process is a means ofachieving Best Practices.

Module 2: Requirements Overview
Use-Case Flow of Events
.. Has one normal, basic flow
.. Several alternative flows
.. Regular variants
.. Odd cases
.. Exceptional flows for handling error situations

What Is a Scenario?
.. A scenario is an instance of a use case.

What Is an Activity Diagram?
.. An activity diagram in the Use-Case Model can be used to
capture the activities in a use case.
.. It is essentially a flow chart, showing flow of control from
activity to activity.

Module 3: Analysis and Design Overview
What Is Architecture?
.. Software architecture encompasses a set of significant decisions about the organization of a software system.
.. Selection of the structural elements and their interfaces by which a system is composed
.. Behavior as specified in collaborations among those elements
.. Composition of these structural and behavioral elements into larger subsystems
.. Architectural style that guides this organization

Module 4: Architectural Analysis
A package is a general-purpose mechanism for organizing elements into groups.

Avoiding Circular Dependencies

What Is a Design Pattern?
.. A design pattern is a solution to a common design problem.
.. Describes a common design problem
.. Describes the solution to the problem
.. Discusses the results and trade-offs of applying the pattern
.. Design patterns provide the capability to reuse successful designs.

An architectural pattern expresses a fundamental structural organization schema for software systems. It provides a set of predefined
subsystems, specifies their responsibilities, and includes rules and guidelines for organizing the relationships between them

What Are Key Abstractions?
.. A key abstraction is a concept, normally uncovered in Requirements, that the system must be able to handle
.. Sources for key abstractions
.. Domain knowledge
.. Requirements
.. Glossary
.. Domain Model, or the Business Model (if one exists)

Module 5: Use-Case Analysis
Use-Case Analysis Steps
.. Supplement the Use-Case Description
.. For each Use-Case Realization
.. Find Classes from Use-Case Behavior
.. Distribute Use-Case Behavior to Classes
.. For each resulting analysis class
.. Describe Responsibilities
.. Describe Attributes and Associations
.. Qualify Analysis Mechanisms
.. Unify Analysis Classes
.. Checkpoints

One boundary class per actor/use case pair

Use-case behavior coordinator

Collaboration Diagrams vs. Sequence Diagrams
.. Collaboration Diagrams
.. Show relationships in addition to interactions
.. Better for visualizing patterns of collaboration
.. Better for visualizing all of the effects on a given object
.. Easier to use for brainstorming sessions

Sequence Diagrams
.. Show the explicit sequence of messages
.. Better for visualizing overall flow
.. Better for real-time specifications and for complex scenarios

Module 6: Identify Design Elements
Identify Design Elements Steps
.. Identify classes and subsystems
.. Identify subsystem interfaces
.. Identify reuse opportunities
.. Update the organization of the Design Model
.. Checkpoints

Module 7: Describe the Run-time Architecture
Describe the Run-time Architecture Steps
.. Analyze concurrency requirements
.. Identify processes and threads
.. Identify process lifecycles
.. Map processes onto the implementation
.. Distribute model elements among processes

Module 8: Describe Distribution
The Deployment View is an “architecturally significant” slice of the Deployment Model.
Distribution Patterns
.. Client/Server
.. 3-tier
.. Fat Client
.. Fat Server
.. Distributed Client/Server
.. Peer-to-peer