1 / 14

UML CASE Tools - StarUML -

UML CASE Tools - StarUML -. Agenda for today. Why need UML tools? Main UML tools StarUML Case Study using StarUML. Brief re-cap of UML. Modeling language used in analysis , design and implementation phases Textual and graphical notation to document specification

samira
Download Presentation

UML CASE Tools - StarUML -

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML CASE Tools- StarUML -

  2. Agenda for today • Why need UML tools? • Main UML tools • StarUML • Case Study using StarUML Software Engineering 2

  3. Brief re-cap of UML • Modeling language used in analysis, design and implementation phases • Textual and graphical notation to document specification • Main diagram types: • structural: class, component, deployment diagrams • behavioral: use case, sequence, statechart diagrams Software Engineering 3

  4. Why need UML tools? • Advantages of “e-design” over “paper-design” • modifications made easier • communication between designers easier • co-ordination and handling of large projects easier Software Engineering 4

  5. Why need UML tools? • Advantages of UML-tools over drawing-tools • uniformnotations • certain checks provided • UML-tools provide add-ons Software Engineering 5

  6. Add-ons • Document generation • HTML, PDF etc. • Round-trip engineering • code generation from diagram (forward engineering) • diagram generation from code (reverse engineering) • Test generation • Simulation • Model validation and verification Level of sophistication Software Engineering 6

  7. UML tools • Big competition among UML tool vendors • plg.uwaterloo.ca/~migod/uml.html • objectsbydesign.com/tools/umltools_byCompany.html • Many free tools/editions with limited capabilities • Compatibility ensured by XML dialect • XMI – XML Metadata Interchange • may contain diagram layout info (Diagram Interchange Standard) Software Engineering 7

  8. Main UML tools • Commercial • Rational Rose (IBM) • Together Designer (Borland) • Rhapsody (I-Logix) • Poseidon (Gentleware) • Free • Omondo • Visual Paradigm (Visual Paradigm) • Open source • ArgoUML (Tigris) • StarUML • And many, many more… Software Engineering 8

  9. Choosing a UML tool • Platform support • UML 2.0 and XMI support • Support of all diagram types • Intuitive and clear GUI • Add-ons • Actively maintained • Document generation and printing support Software Engineering 9

  10. StarUML • Free and open source • Supports • Windows only • UML 2.0 and XMI • all diagram types • diagram printing • code generation (C++, C#, Java) • EJB and GoF pattern application Download: staruml.sourceforge.net Code:staruml.tigris.org StarUML is the tool we suggest. You can use any other tool for the project. We accept diagrams in PDF or in StarUML’s .uml format. Software Engineering 10

  11. Tool demo via case study • Digital sound-recorder (Dictaphone) • Based on: Ivan Porres Paltor, Johan Lilius: Digital Sound Recorder: A case study on designing embedded systems using the UML notation Software Engineering 11

  12. Main features • Capacity for 10 different messages, each max. of 2 minutes • Messages can be recorded,played back and deleted • Messages can be locked/unlocked to prevent unwanted deletion/overwriting • LCD display Software Engineering 12

  13. Problem Statement • The recorder stores up to 10 messages • Each message is max. 2 minutes long • The user can record message • Recording of a message ends after 2 minutes or when the user stops recording • Recording destroys the original message at chosen slot • Sufficient level of battery is checked before recording message • Message of a given slot can be replayed • Sufficient level of battery is checked before replaying message • Messages can be locked/unlocked • Locked messages cannot be deleted or over-written by recording to the same slot • User uses LCD display and buttons to interact with recorder Software Engineering 13

  14. Your tasks (suggestion) • Develop use case diagramWrite flow of event for one or two interesting use cases • Develop sequence diagrams for selected use cases Remember: need not model all possible scenarios • Develop class diagram • Refine sequence diagrams from step 2 according to the classes you have identified in step 3 Remember: you might need to refine your class diagram • Draw state diagram for classes with interesting behavior Remember: typical candidates are control objects Software Engineering 14

More Related