Software Engineering 1 Object-oriented Analysis and Design Chap 22 UML Tools and UML as Blueprint.

Slides:



Advertisements
Similar presentations
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Advertisements

HCI in the software process Chapter 6
Object-Oriented Analysis and Design Introduction 1.
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
Chapter 22 UML Tooks and UML as Blueprint Model-Driven Architecture (MDA) Object-Constraint Language (OCL)
Unified Modeling Language
CS3773 Software Engineering Lecture 03 UML Use Cases.
1 UML – an overview What is UML? UML stands for Unified Modelling Language. ”The Unified Modelling Language is a visual language for specifying, constructing.
Eva TrosborgSlide no.: 1Elaboration Iteration 2 Object Oriented design and more patterns Fall 2005 UML Tools and UML as Blueprint (chapter 22, p 397)
NJIT 1 On to Object Design Chapter 14 Applying UML and Patterns.
Kari R. Schougaard, PhD Stud. Værktøjer og Teknikker, 2006 UNIVERSITY OF AARHUS Department of Computer Science Unified Modeling Language Visual language.
IELM 511: Information System design
SwE 313 Introduction to Rational Unified Process (RUP)
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Object Oriented Design. Goal  Introduction to UML: u what are classes and instances? u Basic project analysis  Introduction to Prototyping/AgentSheets.
ACM/JETT Workshop - August 4-5, 2005 UML Modeling using MagicDraw UML for Java Programmers.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty.
*Object-Oriented Design (Schach Chap 14)
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
UML Tools ● UML is a language, not a tool ● UML tools make use of UML possible ● Choice of tools, for individual or group use, has a large affect on acceptance.
Technical Overview.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Class, Sequence and UML Model.  Has actors and use cases.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
PowerDesigner 与对象建模. 2 Why Using UML? Visually define and communicate the structure and behavior of an application Represent systems using Object-Oriented.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
On to Object Design 徐迎晓 复旦大学软件学院
1 On to Object Design Chapter 14 Applying UML and Patterns.
Object-Oriented Analysis and Design An Introduction.
11 Partnership for Performance How to hear this lecture Click on the icon: to hear the narration for each slide.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Object-Oriented Analysis and Design Fall 2009.
Designing Complex Software Systems: Introduction CS 6961 – Lecture 0 Nathan Dykman.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Session # 3 Prepared by: Amanullah Quadri. Rational Software Modeler and Eclipse  Development Platform integrated with Eclipse.  Results in a richer.
CSC172 Class Design Pepper. Goals How to design classes How to think in terms of objects StarUML Code Generation.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
Verification of behavioural elements of UML models using B Truong, Ninh-Thuan and Souquieres, Jeanine In Proceedings of the 2005 ACM Symposium on.
ARTIFACT UML Actor A Use Case 1 Use Case 2 Actor B Document FileManager GraphicFile File Repository DocumentList FileList Customer name addr withdraw()
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 16, Methodologies: Putting it all together.
Technical Overview The Fastest Way to Create Architecture!
CSC480 Class Design Pepper. Goals How to design classes StarUML Code Generation.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
LehighUML Project John Pequeno, Adam Balgach, Sally Moritz & Professor Glenn Blank.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Ch- 8. Class Diagrams Class diagrams are the most common diagram found in modeling object- oriented systems. Class diagrams are important not only for.
Visible Logic, Visible Quality, Visible Code Alan Spark Software Engineer TechMeetup Aberdeen Wednesday 16 th June 2010.
Object Oriented Analysis and Design 1 Chapter 9 From Design to Implementation  Implementation Model  Forward, Reverse, and Round-Trip Engineering  Mapping.
TK2023 Object-Oriented Software Engineering CHAPTER 9 INTRODUCTION TO OBJECT DESIGN.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 1 Extracting Sequence.
Object Oriented Programming Criteria: P2 Date: 07/10/15 Name: Thomas Jazwinski.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Technical Overview. What Is MagicDraw?  Business Analysts  Software Analysts  Programmers  QA Engineers  Documentation Writers MagicDraw is a powerful.
Modeling with Rational Rose Huzefa Kagdi Software Development Laboratory Department of Computer Science Kent State University Kent Ohio, USA.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Dr. Kivanc DincerCS319 Week 6 - Oct.17,20051 Chapter 14 Onto Object Design Objectives Understand dynamic and static object design modeling. Try agile modeling,
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
Object Oriented Analysis & Design By Rashid Mahmood.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Star UML and CRC Cards Pepper.
Unified Modeling Language
1.Introduction to Rational Unified Process (RUP)
MCS morning (3rd semester) Department of CS&IT
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
On to Object Design c. 14.
Presentation transcript:

Software Engineering 1 Object-oriented Analysis and Design Chap 22 UML Tools and UML as Blueprint

Software Engineering 2 Object-oriented Analysis and Design Forward, Reverse, and Round-Trip Engineering  Forward engineering m the generation of code from diagrams;  Reverse engineering m generation of diagrams from code  Round-trip engineering m generation in either direction and can synchronize between UML diagrams and code, ideally automatically and immediately as either is changed.  All UML tools claim to support these features, but many are half crippled. m code isn't just declarations of variables, it's dynamic behavior. m If tool can generate a sequence diagram from the code, you can then much more easily follow the call-flow logic of the system to learn its basic collaborations.

Software Engineering 3 Object-oriented Analysis and Design Common Report of Valuable Features  the most consistent report of UML tool value m for reverse engineering, m as a visualization learning aid to understand existing code. m Generating UML package, class, and interaction diagrams from code and viewing the diagrams on a monitor, or printing them on large plotter paper,  More UML tools become well-integrated with text- strong IDEs (Eclipse, Visual Studio..), and their usability improves m more consistent value reported in using the tools for both forward and round-trip engineering.

Software Engineering 4 Object-oriented Analysis and Design Look For in a Tool  Choosing a UML tool m try a free UML tool. m try it on a real project with as many developers as possible, before making a decision. m Decide based on the guidance of your developers who have really used it for a long period. m integrates into your favorite text-strong IDE. m supports reverse engineering sequence diagrams from code. m Choose a tool that supports printouts to a plotter, on large plotter paper, in large font and diagram sizes, so that large- scale visualization is possible.

Software Engineering 5 Object-oriented Analysis and Design Update the Diagrams After Coding 1  If using a UML tool integrated with an IDE, working alone, and not doing wall sketching m synchronizing the diagrams is a simple reverse- engineering operation in the IDE.  If working with a small team and want to spend a modeling day each iteration at the whiteboards, applying UML as sketch. Consider this scenario: m At the start of a three-week time boxed iteration, there was a modeling day involving UML wall sketches. m This is followed by about three weeks of code and test. m it's time to start the next iteration's modeling day.

Software Engineering 6 Object-oriented Analysis and Design Update the Diagrams After Coding 2  if you wanted to do some wall sketching, based on the existing state of the code base. m Just before the modeling day, use a UML tool to reverse engineer the code into UML diagrams, package, class, and interaction diagrams. m for the most interesting ones, print them large on long plotter paper. Hang them relatively high in the modeling room on the walls m during the modeling day, developers can refer to them, sketch on top of them, and sketch below them on whiteboards or static cling sheets.