Lab 2


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Lab 2

  1. 1. Advance Software Engineering LAB # 02 LAB #02OBJECTIVE: • Introduction To IBM Rational Rose.What is visual modeling? • Visual modeling is the process of graphically depicting the system to be developed. • Visual modeling allows you to present essential details of a complex problem and filter out the nonessential details. • It also provides a mechanism for viewing the system to be developed from different perspectives.Why should I model my software? Designing a model for software systems is as essential as having a blueprint for a large building. Good models: • Identify requirements and communicate information· • Focus on how system components interact, without getting bogged down in specific details· • Allow you to see relationships among design components· • Improve communication across your team through the use of a common, graphical languageWhy should I use Rational Rose?There are a number of reasons to use Rational Rose for your development work. Here are just a few: · • 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 dynamic behaviors, such as business requirements analysis, business scenario analysis with sequence and collaboration diagrams, state modeling, and additional code generation capabilities for DDL and IDL, along with the inclusion of a scripting language to provide access. • Model-driven development results in increased developer productivity. • Use-case and business-focused development results in improved software quality. • Common standard language--the Unified Modeling Language (UML) --results in improved team communication. • Reverse-engineering capabilities allow you to integrate with legacy OO systems. • Models and code remain synchronized through the development cycle. 1
  2. 2. Advance Software Engineering LAB # 02Rose Enterprise • Supports multiple languages including (VC++, VB, Java, and CORBA)The Rose graphical user interface • The most common elements are: • Standard toolbar • Diagram toolbox • Browser • Diagram window • Documentation window • SpecificationsThese items are briefly discussed in subsequent slides. How, where, and why each of these elements isused will become clearer as you progress through the tutorial.The Standard Toolbar remains the same for all views and diagrams. It contains standard Windowsfunctions as well as those specific to Rational Rose Real Time. The Diagram Toolbox is used for addingelements to the model by drawing them on a diagram. The toolbox elements change depending on theactive diagram. For example, the Use-Case Diagram has a tool for adding actors, but the Component 2
  3. 3. Advance Software Engineering LAB # 02Diagram does not have this tool. Browsers are hierarchical and can be expanded and contracted. Whenyou start Rational Rose Real Time, the Model View, the Containment View, and the Inheritance Viewbrowsers are docked on the left side of the interface in a stacked format. They can be set tovisible/invisible, docked, or floating. To activate a specific browser, select the appropriate tab located atthe bottom of the interface. There are two additional browsers, also referred to as editors, which can beopened to perform specific tasks: the Structure/State Diagram Browser/Editor, and the Run Time System(RTS) Browser/Editor. These browsers cannot be moved.Rational Rose Real Time offers four main views located on the Model View browser. Each view isrelated to a software lifecycle phase, and the diagrams are artifacts of those phases. Use-Case View showswhat a system (subsystem, class, or interface) does but does not specify how the system internallyperforms its tasks. Logical View represents the architectural processes as the model moves from analysis,through design, and into development. Component View contains concrete representations of the system.Components realize the active and data classes, and provide the components for building an executablemodel. Deployment View shows how the system is to be distributed. It defines the processors, andcontains a diagram of the nodes in the system.Rational Rose is organized around the following views of a software project:• Use Case Views• Logical Views• Component Views• Deployment ViewsEach of these views presents a different aspect of the model and is explained in subsequent slides.The use-case viewThe use-case view helps you to understand and use the system. This view looks at how actors and usecases interact. The diagrams in this view are:• Use-case diagrams• Sequence diagrams• Collaboration diagrams• Activity diagrams 3
  4. 4. Advance Software Engineering LAB # 02This view contains a Main diagram by default. Additional diagrams can be added throughout the analysisand design process.The logical viewThe logical view addresses the functional requirements of the system. This view looks at classes and theirrelationships. The diagrams in this view are:• Class diagrams• Statec hart diagramsThis view contains a Main diagram by default. Additional diagrams can be added throughout the analysisand design process.The component viewThe component view addresses the software organization of the system. This view containsinformation about the software, executable and library components for the system. This viewcontains only component diagrams. The component view contains a Main diagram by default.Additional diagrams can be added to this view throughout 4
  5. 5. Advance Software Engineering LAB # 02The deployment viewThe deployment view shows the mapping of processes to hardware. This type of diagram is mostuseful in a distributed architecture environment where you might have applications and servers atdifferent locations. This view contains only one diagram – the deployment diagram.Diagrams• A diagram is a graphical representation of the elements of your system.• Different diagram types allow you to view your system from multiple perspectives.• You can create various types of diagrams in Rational Rose. The diagram types include:• Use-Case• Class• Activity• State chart• Component• Deployment 5