14.RoseBasics

14.RoseBasics - Rational Rose Basics Visual Modeling...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Rational Rose Basics Visual Modeling Textbook – Chapter 3 Original Notes from Rational Software Corporation – modified considerably for instructional purposes
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 What is Visual Modeling Helps organize, visualize, and understand complexity . Is the mapping of real processes of a system to a graphical representation . Is a proven and accepted engineering technique. Rose uses a common vocabulary, the Unified Modeling Language (UML).
Background image of page 2
3 Models Models themselves are constructed using different views and diagrams to accurately depict different stakeholder perspectives and the system’s building blocks, respectively. Models are complete representations of the system. Views allow different stakeholders to see the system from their own perspectives Views contain Models… E.g. Logical View contains analysis model, business object model, design model (Sometimes models can contain ‘views’ too…) Models generally contain a number of diagrams – some of these terms are ‘used’ interchangeably… E.g. Design model contains class diagrams, sequence diagrams, and a number of others…. Diagrams: means by which we view of the system. Different building blocks (model elements) for different types. E.g.: classes, interfaces, collaborations, components, nodes, dependencies, generalizations, and associations. The 4 + 1 Architectural Views: how they work in Rose.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Process View Deployment View Logical View Use-Case View Implementation View End-user Functionality Programmers Software management Performance Scalability Throughput System integrators System topology Delivery, installation communication System engineering Analysts/Designers Structure / Behaviors Very Important:  4 + 1 Architectural  View
Background image of page 4
5 4+1 Architectural View Use Case View - represents the system’s intended functions and environment as seen by its end users . Serves as a contract between customer and developer. Is essential to analysis, design and test activities. Includes use case diagrams, use case flow of events, and supplemental documentation. It can also include activity diagrams . Is the heart of and drives all other views . Central !! Used for requirements capture and analysis…and much, much more
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 4+1 Architectural View Logical View Supports modeling the functional requirements of the system , meaning the services the system should provide its end users. Includes analysis class modeling, use case realizations, and interaction diagrams and more. It can also include state-chart and activity diagrams. – discuss. Much analysis and design involve packages and models in this view. In fact, ‘most’ analysis and design in done here…
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/26/2011 for the course CEN 6016 taught by Professor Sanchez,a during the Spring '08 term at UNF.

Page1 / 27

14.RoseBasics - Rational Rose Basics Visual Modeling...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online