OV-6c Template Operational Event/Trace Description – step-by-step instructions and template Click the mouse button to see the next slide. Use the browser.

Slides:



Advertisements
Similar presentations
Instruction: Use mouses left button. Use mouses left button. If mouse buttons dont work, use arrow keys of keyboard for slide show. If mouse buttons dont.
Advertisements

Instruction: Use mouses left button. Use mouses left button. If mouse buttons dont work, use arrow keys of keyboard for slide show. If mouse buttons dont.
Chapter 7 Structuring System Process Requirements
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
Ana M. Fernández  A UML diagram that depicts: ◦ interactions between objects. ◦ how the business currently works by showing how various.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
Chapter 6 Functional Modeling
Functional Modeling Chapter 6.
Unified Modeling Language
Interactions. 2 Objects communicate with each other by sending messages. Sending a message is another name for a member function call. –Some C++ examples.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
CS 310 Ch8: System models Abstract descriptions of systems being analyzed to help the analyst understand the system functionality communicate with customers.
Chapter 7 Structuring System Process Requirements
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models. System modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Chapter 7 System models.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 15 The Unified Modeling Language: a Primer.
Interaction Diagram An interaction diagram is a graphical representation of interactions between objects. Sequence diagram: shows the sequence in which.
Use Case Model Use case description.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
CSE Senior Design I Architecture Design Review/Final Exam Template CSE 4316 Final Exam.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Introduction to Rational Rose 2000 Create Use Case Model.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
THE MOUSE Left Click THE MOUSE Right Click.
INTEGRATOR’S BROWSER FUNCTIONS Use The Function
ACTIVITY DIAGRAMS 《UML面向对象建模基础》.
WHAT IS A Process Map? Illustration of the sequence of activities, inputs and outputs to the activities, and relationship across multiple functions, or.
Multilinear Events Sequencing
Business System Development
Interactions.
OV-1 Template High-level Operational Concept Graphic – step-by-step instructions and templates Click the mouse button to see the next slide. Use the browser.
Physical Data Model – step-by-step instructions and template
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Abstract descriptions of systems whose requirements are being analysed
Use Case Model Use case description.
Database Design Using the REA Data Model
System Interface Description – step-by-step instructions and templates
System models October 5, 2005.
IDEF0/Activity Model – Functional Decomposition
Week 12: Activity & Sequence Diagrams
Object Oriented Analysis and Design
INFS 6225 Object Oriented Systems Analysis & Design
UML Interaction diagrams
PowerPoint Notes.
OV-2 Template Operational Node Connectivity Description – step-by-step instructions and templates Click the mouse button to see the next slide. Use the.
SV-10c Template Systems Event/Trace Description – step-by-step instructions and template Click the mouse button to see the next slide. Use the browser.
SV-2 Template Systems Communications Description – step-by-step instructions and templates Click the mouse button to see the next slide. Use the browser.
Activity Model – step-by-step instructions and templates
OV-6b Template Operational State Transition Description – step-by-step instructions and template Click the mouse button to see the next slide. Use the.
Operational Rules Model – step-by-step instructions and template
Logical Data Model – step-by-step instructions and template
, editor October 8, 2011 DRAFT-D
Systems Architecture & Design Lecture 3 Architecture Frameworks
HOW TO APPROVE MULTIPLE CREDIT CARD TRANSACTIONS IN PAYMENTNET
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Command Relationship Chart – step-by-step instructions and template
SV-10b Template Systems State Transition Description – step-by-step instructions and template Click the mouse button to see the next slide. Use the browser.
Chapter 4 Sequence Diagrams
Presentation transcript:

OV-6c Template Operational Event/Trace Description – step-by-step instructions and template Click the mouse button to see the next slide. Use the browser Back button to return to the Tutorial.

Four Steps in developing your OV-6c Step 1 - Identify the Product's Timescale Decide on the timescale that this product is expected to represent (as-is, to-be, transitional) Multiple timescales are often needed for each product; a separate OV-6c should be produced for each timescale that is needed

Step 2 - Reference Existing Architecture Products Node Connectivity Description (OV-2) Review the operational nodes and information exchange requirements documented in your OV-2 and determine those relevant to the scope of the OV-6c State Transition Description (OV-6b) Review the events documented in your OV-6b and determine those relevant to the scope of the OV-6c

Step 3 - Relate Operational Nodes to Events Determine the relationship between operational nodes (typically organisations or roles) and events, to include specification of the node's response to the event Sequence Events Determine the logical order in which events occur Events may occur serially or in parallel

Step 4 - Illustrate Operational Event/Trace Description Depict Related Nodes and Events Portray the operational nodes on one axis of the diagram Portray the timeline associated with each node as a line connected to the node Depict events to which nodes must respond as arrows flowing into or out of the appropriate nodal timeline Depict Sequential Relationship Between Nodes and Events Portray the relationship between nodes and events in terms of the sequence in which they occur. Label the left side of the diagram with specific points in time, and then order the events in the diagram accordingly to reflect the actual sequence in which they (will) occur

Template A timing diagram template has been provided, following this slide Don’t forget to update your Integrated Dictionary (CV-2) with any new terms or abbreviations introduced in the OV-6c Delete the instruction slides when OV-6c completed

OV-6c Operational Event/Trace Description template GROUP NAME GROUP NAME NODE NAME NODE NAME NODE NAME NODE NAME NODE NAME Event Name Event Name Time Frame Event Name Event Name Event Name Event Name Event Name Event Name Time Frame Event Name Event Name Time Frame Event Name Event Name Time Frame Event Name Event Name Time Frame