0% found this document useful (0 votes)
399 views

Oose Notes Chapter 1

Visual modeling uses abstract models to represent complex problems in a simplified way. Models promote understanding of requirements, better design, and more maintainable systems. Notations provide a language for communicating decisions and semantics to capture strategic and tactical decisions. The Unified Modeling Language (UML) is used to specify, visualize, and document object-oriented systems. The Rational Unified Process (RUP) provides guidelines for iterative development using UML modeling. Rational Rose and Visual Modeler are modeling tools that support UML and code generation.

Uploaded by

Dipankar Saini
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
399 views

Oose Notes Chapter 1

Visual modeling uses abstract models to represent complex problems in a simplified way. Models promote understanding of requirements, better design, and more maintainable systems. Notations provide a language for communicating decisions and semantics to capture strategic and tactical decisions. The Unified Modeling Language (UML) is used to specify, visualize, and document object-oriented systems. The Rational Unified Process (RUP) provides guidelines for iterative development using UML modeling. Rational Rose and Visual Modeler are modeling tools that support UML and code generation.

Uploaded by

Dipankar Saini
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 22

Visual Modeling

Is a way of thinking about problems using models


organized around real-world ideas.

Models are useful for:-


1. Understanding problems,
2. Communicating with everyone involved with the
project (customers, domain experts, analysts,
designers, etc.),
3. Preparing documentation,
4. Designing programs and databases.

Modeling promotes better understanding of requirements,


cleaner designs, and more maintainable systems.
• Models:-
– Are abstractions that portray the essentials
of a complex problem or
– structure by filtering out nonessential
details, thus making the problem easier to
understand.

• Abstraction:-
– is a fundamental human capability that
permits us to deal with complexity.
To build complex systems
– The developer must abstract different views of the
system,
– Build models using precise notations,
– Verify that the models satisfy the requirements of the
system,
– And gradually add detail to transform the models into
an implementation.

Constructing a model allows the designer to focus on


the big picture of how a project's components interact,
without having to get bogged down in the specific
details of each component.
Component need for successful
project
• You can learn a notation, but if you don't know
how to use it, you will probably fail.

• You may have a great process, but if you can't


communicate the process, you will probably fail.

• And lastly, if you cannot document the artifacts of


your work (tool), you will probably fail.
Role of Notations
Notation has three roles:
• It serves as the language for communicating decisions
that cannot be inferred from the code itself.

• It provides semantics that are rich enough to capture all


important strategic and tactical decisions.

• It offers a form concrete enough for humans to reason


and for tools to manipulate.
UML
• UML is a language used to specify, visualize, and
document the artifacts of an object-oriented system
under development.

• Provide a very robust notation, which grows for analysis


into design.

• Certain elements of the notation (for example, classes,


associations, aggregations, inheritance) are introduced
during analysis.

• Other elements of the notation (for example,


containment implementation indicators and properties)
are introduced during design.
History of UML
The Role of Process
A successful development project
satisfies:-
– The customer's expectations,
– Developed in a timely and Economical fashion,
– Is resilient (flexible) to change and adaptation.

The development process must be


controlled and measured to ensure that
the project is indeed completed.
Iterative and Incremental
Development
• Development proceeds as a series of iterations
that evolve into the final system.

• Each iteration consists of one or more of the


following process components:
– business modeling,
– requirements,
– analysis,
– design,
– implementation, test, and deployment.
• The developers do not assume that all requirements are
known at the beginning of the life cycle; indeed change is
anticipated throughout all phases.
Risk
• It is a Risk Mitigates process.

• Technical risks are assessed and prioritized early in the


life cycle and are revised during the development of each
iteration.

• Risks are attached to each iteration so that successful


completion of the iteration alleviates the risks attached to
it.

• The releases are scheduled to ensure that the highest


risks are tackled first.

• Building the system in this fashion exposes and mitigates


the risks of the system early in the life cycle.
The Rational Unified Process

• An extensive set of guidelines that address the


technical and organizational aspects of software
development focusing on requirements analysis
and design.

• Use to Control an iterative and incremental life


cycle.
The Rational Unified Process is structured
along two dimensions:

• Time:-
Division of the life cycle into phases
and iterations
• Process components:-
Production of a specific set of
artifacts with well-defined activities
Structuring a project along the time dimension
involves the adoption of the following time-based
phases:-

• Inception—specifying the project vision

• Elaboration—planning the necessary activities and


required resources; specifying the features and
designing the architecture

• Construction—building the product as a series of


incremental iterations

• Transition—supplying the product to the user community


(manufacturing, delivering, and training)
Structuring the project along the process
component dimension includes the
following activities:

• Business Modeling—the identification of


desired system capabilities and user needs

• Requirements—a narration of the system


vision along with a set of functional and
nonfunctional requirements

• Analysis and Design—a description of how


the system will be realized in the
implementation phase
• Implementation—the production of the
code that will result in an executable
system

• Test—the verification of the entire


system

• Deployment—the delivery of the system


and user training to the customer
Development Process
Rational Rose tool
• The Rational Rose product family is
designed to provide
– the software developer with a complete set
of visual modeling tools for development of
robust,
– efficient solutions to real business needs in
the client/server, distributed enterprise, and
real-time systems environments.
Rational Rose tool
– Rational Rose products share a common
universal standard,
– Modeling accessible to nonprogrammers
wanting to model business processes.
– Programmers modeling applications logic.
Microsoft Visual Modeler is the entry-level product, designed
specifically for the first-time modeler.
The tool provides the capability to:-

• Identify and design business objects, and then map them to


software components
• Partition services across a three-tiered service model
• Design how components will be distributed across a network
• Generate Visual Basic code frameworks directly from your
model
• Use reverse engineering to create models from existing
components and applications
• Use round-trip engineering facilities to keep your designs
synchronized with your code
Rational Rose extends Visual Modeler
for dynamic behaviors, such as business
requirements analysis

•Business scenario analysis with sequence and


collaboration diagrams,

•State modeling, additional code generation


capabilities for DDL and IDL, along with the
inclusion of a scripting language to provide access
to the Rose domain.

You might also like