1 Tutorials plan CS 236700 - Tutorials plan. 2 Week by week W1+W2: Modularity Code generation via Rose Writing use cases Drawing use-cases Relationships.

Slides:



Advertisements
Similar presentations
And so to Code. Forward, Reverse, and Round-Trip Engineering Forward Engineering Reverse Engineering Round-Trip Engineering.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
CS3773 Software Engineering Lecture 03 UML Use Cases.
Objects and Classes First Programming Concepts. 14/10/2004Lecture 1a: Introduction 2 Fundamental Concepts object class method parameter data type.
©1998, 1999, 2000 Rational Software - All rights reserved Session VM08 Structuring Your Rational Rose Model Robert Bretall Rational Software.
Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.
1 SWE Introduction to Software Engineering Lecture 15 – System Modeling Using UML.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
CSCI928 Software Engineering Requirements & Specifications Modeling System Interactions Tri A. Kurniawan, M.Eng. Ph.D Candidate
Software Design by Dr. Eitan Hadar Web:
1 RNDS Deployment, Collaborations and Sequences CS : Software Design Winter /T6.
Ims5024 Week 71 IMS 5024 Object orientation (2). Ims5024 Week 72 Content Group assignment Use-cases State transition diagrams Place in ISD Evaluation.
Slide 11B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
CO320 Introduction to Object- Oriented Programming Michael Kölling 3.0.
1 Use case sample cs System Overview  A new web-based front-end for an existing library  There is a global book info service  Typical actions.
Object Oriented Software Development
Software Engineering CS B Prof. George Heineman.
PRESENTATION 2 Sri Raguraman CIS 895 Kansas State University.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Object-Oriented Analysis and Design OVERVIEW. Objectives  Describe Information Systems  Explain the role of a systems analyst  Introduce object-oriented.
Recap (önemli noktaları yinelemek) from last week Paradigm Kay’s Description Intro to Objects Messages / Interconnections Information Hiding Classes Inheritance.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
More on “The Huddersfield Method” A lightweight, pattern-driven method based on SSM, Domain Driven Design and Naked Objects.
An Introduction to Java Chapter 11 Object-Oriented Application Development: Part I.
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
Design Class Diagrams (DCDs)
Chapter 16 Applying UML and Patterns Craig Larman
Sept. 18, 2003CS WPI1 CS 509 Design of Software Systems Lecture #3 Thursday, Sept. 18, 2003.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
CSC 395 – Software Engineering Lecture 14: Object-Oriented Analysis –or– Ripping the Band-Aid Off Quickly.
♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.
NJIT UML Class Diagrams Chapter 16 Applying UML and Patterns Craig Larman.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
System sequence diagrams
Identifying & Creating Use Cases – Part 1 Month Day, Year.
Copyright ©2004 Cezary Z Janikow 1 OOAD Overview n OO language – Necessary for OO systems? – Sufficient for OO systems? Owning a hummer doesn’t make you.
PRESENTATION 2 Sri Raguraman CIS 895 Kansas State University.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
M1G Introduction to Programming 2 3. Creating Classes: Room and Item.
SAD2 - UML Lecturer: Dr. Dimitrios Makris 1st Lecture
UML Review of Use case diagrams. 2 Unified Modeling Language The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson,
Using Rational Rose XDE Month Day, Year. Agenda Training Plan Overview XDE Review Next Steps.
Use Case Model Use case description.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Topic: UML Group 1 Adrian Baijnauth Ashima Dogra Atif Sayed Bruno Baldassarra Frank Scaini Sabrina Babooram Zain Yusuf.
Blood Donors System Project Lead : Chaitanya M Project Members : Anbalagan Nagarjuna R Nithyasri B.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Using ClearCase Month Day, Year. Agenda Training Plan Overview ClearQuest Review Next Steps.
Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.
Week 6, Class 3: Composite Swing composites File composites Computer composites SE-2811 Slide design: Dr. Mark L. Hornick Content: Dr. Hornick Errors:
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
Demand Response Use Case & Functional Requirements Development UCAIug Meeting Jan 6, 2009 Mark van den Broek.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
Using Rational Administrator Month Day, Year. Agenda Training Plan Overview Using Rational Administrator Review Next Steps.
1 Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.
CS 350 – Software Design UML – The Unified Modeling Language – Chapter 2 The Unified Modeling Language is a visual language used to create models of programs.
BIO 101 Week 5 Learning Team Food Web Diagram Check this A+ tutorial guideline at 101/BIO-101-Week-5-Learning-Team-Food-
BTS430 Systems Analysis and Design using UML
Software Engineering Summarized Slides.
Object-Oriented Design
Topic 12 Patterns and Relationships Lessons 12-1 thru 12-3
Rational Rose 2018/12/30.
Chapter 11: Class Diagram
Checkpoint Reading DMAC code:
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
PASSI (Process for Agent Societies Specification and Implementation)
Chapter 11: Class Diagram
Presentation transcript:

1 Tutorials plan CS Tutorials plan

2 Week by week W1+W2: Modularity Code generation via Rose Writing use cases Drawing use-cases Relationships between actors Introduction to Java W3: Use case analysis of RNDS Problem description: specifications/requirements Finding actors Use case diagram Full description of selected UC

3 Week by week W4: Class analysis of RNDS Drawing class diagrams Identifying classes Determining responsibilities of classes Representing Domain entities WP,Aircraft,FlightPlan Relationships analysis for selected classes has-a vs. is-a, policy-based-design W5: Sequence analysis of RNDS Sequence diagram Determining interaction between classes Detailed description of selected use-case related sequences Detailed description of selected inner sequences

4 Week by week W6: Detailed class design of RNDS Methods, fields, parameters, return values, etc... W7-W9: Design Patterns applying Design Patterns over RNDS code. Show automatic Design Patterns generation thru Rose. Integrating Design Patterns into an actual system W10-W13: Overview Show domain specific problems + solutions Web applications Enterprise applications RT applications Information systems