Chapter 23 Iteration 2.

Slides:

Advertisements

Similar presentations

Chapter 29 State Machine Diagrams Sate Machine Diagrams Represent state of an object Behavior as reaction to events.

Advertisements

Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 16, Methodologies: Putting It All Together.

Chapter 22 UML Tooks and UML as Blueprint Model-Driven Architecture (MDA) Object-Constraint Language (OCL)

Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.

Chapter 9 Domain Models The classic OOAD model. Fig. 9.1.

COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.

NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.

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.

Case Study The NextGen POS System

Domain model: visualizing concepts

From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.

Chapter 3 Case Studies.

COMP 350: Object Oriented Analysis and Design Lecture 2

Week 3 Iteration 1 Domain Models System Sequence Diagrams.

TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.

Chapter 7: The Object-Oriented Approach to Requirements

Chapter 9 Domain Models. Domain Model in UML Class Diagram Notation A “visual dictionary”

Model the User Experience Today:  Detail some Use Cases  Develop a storyboard of the use cases  Sketch mock-ups of the use case's information requirements.

Systems Analysis and Design in a Changing World, Fifth Edition

Mapping Designs to Code Larman, Chapter 20 CSE432 Object Oriented Software Engineering.

Chapter 18 Object Design Examples with GRASP. Objectives Design use case realizations –A use-case realization describes how a particular use case is realized.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.

Week 10 Iteration 3 What is here Iteration 3 works like iteration 2 More OO design This week more UML.

12 Systems Analysis and Design in a Changing World, Fifth Edition.

Chapter 11: Software Prototyping Omar Meqdadi SE 273 Lecture 11 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.

1 ITEC 3010 “Systems Analysis and Design, I” LECTURE 10: Use Case Realizations [Prof. Peter Khaiter]

Key Takeaway Points A use case is a business process; it begins with an actor, ends with the actor, and accomplishes a business task for the actor. Use.

Chapter 6 Use Case –The interaction between an actor and the system.

Chapter 7 Applying UML and Patterns Craig Larman

Jan 7, A UP project organizes the work and iterations across four major phases: – Inception -- approximate vision, business case, scope, vague estimates.

Systems Analysis and Design in a Changing World, 3rd Edition

UML Mars UML DIAGRAM 2 Interaction Component Sequences Class Tools: Sticky notes and flipcharts PlantUML through

Domain Model Refinement Larman, chapter 31 CSE 432: Object-Oriented Software Engineering Glenn D. Blank, Lehigh University.

♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.

Sept Ron McFadyen1 Today Sept 16: Chapters 1, 2, 3 Introductory material Next Tuesday Sept 21: Rational Rose and Use Cases Chapter 6 - Use.

CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)

Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.

Use Case Controller System sequence diagram (SSD) shows input messages from external actors within use case Only indicates that messages go to system Use.

System sequence diagrams

Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.

Software Engineering 1 Object-oriented Analysis and Design Chap 24 Iteration 2 More Patterns.

Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.

Chapters 10, 11 SSD (Revision) SD DCD Exam Object-Oriented Design.

Larman chapter 101 Domain Model: Visualizing concepts Larman chapter 10.

T Iteration I1 Demo Software Trickery PP Iteration

Summary from previous lectures

Chapter 3: Case Studies What is and is not Covered in the Case Study?  Traditional business software applications include UI elements, core application.

(Further analysis and Refactoring) Larman, chapters 23 and 24 Glenn D. Blank, CSE432.

Chapter 8. Iteration 1, Elaboration: book view differs from reality for pedagogical reasons not doing “risk-driven” up front uses many OOA/D skills should.

1 Chapter 13: Class Diagram Chapter 19 in Applying UML and Patterns Book.

Object Design Examples with GRASP

Elaboration popo.

Chapter 9 Domain Models.

Systems Analysis and Design in a Changing World, 6th Edition

System Sequence Diagrams and Operation Contracts

Domain Model: Visualizing concepts

System sequence diagrams

Chapter 6 Use Case The interaction between an actor and the system.

Systems Analysis and Design in a Changing World, 6th Edition

Chapter 25 GRASP The other four.

Week 10 Iteration 3.

State Machine Diagrams

Chapter 25 GRASP The other four.

Week 3 Iteration 1 Domain Models System Sequence Diagrams.

Week 3 Iteration 1 Domain Models System Sequence Diagrams.

Other System Requirements

Presentation transcript:

Chapter 23 Iteration 2

What is different in the second iteration?

All software has been tested! Results of iteration 1 All software has been tested! Unit Acceptance Load Usability Customer engagement Integrated system

Iteration planning meetings Reverse engineering with UML tools UI work Not covered in text Iteration planning meetings Reverse engineering with UML tools UI work Databases Requirements workshop at start of iteration 2

Risk and Business value Tools to use in planning iterations!

Fix misses from iteration 1 Customer issues Better understanding Add some new requirements for iteration 2

Chapter 24 Quick Analysis Update

NextGen POS

SSD – needs some new external ops! Domain model is ok! Next Gen POS Uses cases ok SSD – needs some new external ops! Support external actors! Domain model is ok!

Fig. 23.1 SSD

Add special square rules Player gets $1500 Bank is unlimited Monopoly Add special square rules Player gets $1500 Bank is unlimited Passing go gives $200 Goto Jail : but get out next turn. Income Tax - pay min($200, 10% of net)

Monopoly Use cases ok No new SSD ops Domain model changes!

Fig. 23.2 New Domain Model

In both cases - add to functionality Change the required artifacts Summary In both cases - add to functionality Change the required artifacts Keep testing!