Week 3 Iteration 1 Domain Models System Sequence Diagrams.

Slides:



Advertisements
Similar presentations
FROM INCEPTION TO ELABORATION Use Cases, Domain Models & SSDs Oh My!
Advertisements

Chapter 2. Iteration The most import aspect of OOA/D An agile practice vs waterfall – early and repeated programming, feedback, adaptation waterfall is.
INFO415 Approaches to System Development: Part 1
Object-Oriented Analysis and Design CHAPTERS 8, 9: BASICS, INTRO TO DOMAIN MODELS 1.
Chapter 22 UML Tooks and UML as Blueprint Model-Driven Architecture (MDA) Object-Constraint Language (OCL)
Chapter 9 Domain Models The classic OOAD model. Fig. 9.1.
Chap 1 UML vs Thinking in Objects! – Visual modeling Learning UML – Look at the book examples – Alan Holub’s UML reference card – Use library resources.
Object-Oriented Analysis and Design
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
Mastering Object-Oriented Analysis and Design with UML Module 4: Analysis and Design Overview.
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.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development.
Object-oriented Analysis and Design
Domain model: visualizing concepts
Dr. Kivanc DincerCS319 Week 1 - Sept.12,20051 Chapter 4 INCEPTION IS NOT THE REQUIREMENTS PHASE Objectives Define the inception step. Motivate the following.
Jan 8, Ron McFadyen1 Waterfall Spiral UP Case study UML Use Cases.
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
COMP 350: Object Oriented Analysis and Design Lecture 2
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
INFO 355Week #61 Systems Analysis II Essentials of design INFO 355 Glenn Booker.
CIS 321—IS Analysis & Design
UML - Development Process 1 Software Development Process Using UML (2)
IS0514 Lecture - Week 2 Best Practice Development Methodology.
Mapping Designs to Code Larman, Chapter 20 CSE432 Object Oriented Software Engineering.
Software Development Stephenson College. Classic Life Cycle.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
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.
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
THE UNIFIED PROCESS UP Programming. What is the unified process  The Unified Process is a programming methodology that emphasizes the right blend of.
Sept Ron McFadyen1 Today Sept 16: Chapters 1, 2, 3 Introductory material Next Tuesday Sept 21: Rational Rose and Use Cases Chapter 6 - Use.
Systems Analysis and Design in a Changing World, Fourth Edition
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
The Rational Unified Process 1 EECS810: Software Engineering.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN Objectives Describe the book goals and scope Define OOA/D (Object-Oriented Analysis and Design) Illustrate.
Object-Oriented Analysis and Design Jan 26, 2009.
Object-Oriented Analysis and Design Week 11, 2009.
Week 2. Topics Inception phase Evolutionary requirements Use cases.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Chapter 8: Iteration 1 - Basics.  We review here the requirements for first iteration of our case studies. They are a subset of the requirements as described.
Chapter 3: Case Studies What is and is not Covered in the Case Study?  Traditional business software applications include UI elements, core application.
Project Deliverables CIS 4328 – Senior Project 2 And CEN Engineering of Software 2.
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.
Nick Small, Shawn Boughey, Karolina Latkoska Project Briefing 1.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XIV. From Requirements to Design in the UP.
CS 389 – Software Engineering Lecture 2 – Part 2 Chapter 2 – Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
TK2023 Object-Oriented Software Engineering
Elaboration popo.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
System Development Process
Unified Process (UP).
COMP 350: Object Oriented Analysis and Design Lecture 2
Week 2.
Chapter 2 – Software Processes
Chapter 18.
Chap 1 UML vs Thinking in Objects! Learning UML Visual modeling
OBJECT ORIENTED ANALYSIS AND DESIGN
The Unified/Rational Unified Process (UP/RUP) Defined
Chapter 23 Iteration 2.
Multi Core Processing What is term Multi Core?.
Chapter 16 Class Diagrams.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Week 3 Iteration 1 Domain Models System Sequence Diagrams.
Other System Requirements
CSCI 360: Software Architecture & Design
Presentation transcript:

Week 3 Iteration 1 Domain Models System Sequence Diagrams

Chapter 8 Iteration 1

The book vs. real life In a normal development: –Risk areas –OOAD –Database design –Usability and more In the book –OOAD Look at the NextGen OS and Monopoly examples Don’t implement everything at once!

Fig. 8.1

Process Elaboration –Initial series of iterations –Core, risky software architecture –Majority of requirements get discovered –Major risks are mitigated Start software development early Be adaptive

Artifacts in Elaboration Domain Model Design model Software Architecture Data model Use cases, UI prototypes, Storyboards