Machine to Machine Interface Update 1 Machine to Machine Interface Update February 7th, 2007.

Slides:

Advertisements

Similar presentations

Team Norms Wind Device Project Common Changes to Unit:

Advertisements

Integration Update 1 External Interfaces & Integration July Stephen Kerr.

Developing mobile apps for businesses and brands.

Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz

GAI Proprietary Information

Lecture 5 Themes in this session Building and managing the data warehouse Data extraction and transformation Technical issues.

Managing the Information Technology Resource Jerry N. Luftman

Project Management Process Project Description Team Mission/ Assignment Major Milestones Boundaries Team Identification Measures of Success Roles & Responsibilities.

1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.

Page 1 R Risk-Driven and Iterative Development. Page 2 R Copyright © 1997 by Rational Software Corporation What the Iterative Life Cycle Is Not It is.

System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.

The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.

Certified Business Process Professional (CBPP®) Exam Overview

Project Management Process Project Description Team Mission/ Assignment Major Milestones Boundaries Team Identification Measures of Success Roles & Responsibilities.

What is Business Analysis Planning & Monitoring?

CPSC 871 John D. McGregor Processes – a first iteration Module 1 Session 1.

Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,

1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.

Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.

Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.

CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.

1 Texas Nodal Texas Nodal Program Implementation TPTF June 6, 2006 Agenda.

ERCOT and Utilicast Public Document February 17, 2009 Nodal Program Oversight Report 9 System Integration Assessment.

1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.

Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.

Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.

Large Scale Software Systems Derived from Dr. Fawcett’s Notes Phil Pratt-Szeliga Fall 2010.

Project Life Cycle.

Machine to Machine Interface Update 1 Machine-to-Machine Interface Update January 10, 2007 Daryl Shing.

Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.

Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.

Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.

Design Process for Architecture. Architectural Lifecycle Not all lifecycle plans support Architecture! It is hard to achieve architecture based design.

Hall 180 Cryogenic test facility: Project management: Project Change Request, EVM and Interface Sheet L. Serio.

Lead from the front Texas Nodal 1 Texas Nodal Critical Path Update TPTF Date xxx.

February 5, 2009 Technical Advisory Committee Meeting Texas Nodal Program Implementation: Program Update Trip Doggett.

Targets for project progress 2015: graduation review – clear documentation and PoC implementation specify general framework and API requirements gap analysis.

January 15, 2008 Monthly Board of Directors Meeting Texas Nodal Market Implementation Program Update Jerry Sullivan.

Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.

1/22/08 RTR Project Presentation to TPTF RTR Project Michael Daskalantonakis & Brian Cook.

Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.

J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.

PRJ566 Project Planning & Management Software Architecture.

Reconfiguring Nodal Stakeholder Participation Presentation to the ERCOT Technical Advisory Committee Texas Nodal Transition Planning Task Force February.

Project Initiation at The Regence Group 12/19/2015John Garrigues1.

IAEA International Atomic Energy Agency Methodology and Responsibilities for Periodic Safety Review for Research Reactors William Kennedy Research Reactor.

Lead from the front Texas Nodal 1 EDW Update to TPTF November 5, 2007 Janet Ply EIS Nodal EDW Project Manager.

Lead from the front Texas Nodal 1 Texas Nodal Market Implementation ERCOT Board Of Directors – August 15, 2006 TPTF Meeting August.

Stages of design  High level design  High level data structure  Architecture  Low level design-code design  Algorithms  Low level data structures.

TPTF CIM Health Check Raj Chudgar Program Director for Market Redesign.

State of Georgia Release Management Training

September 22, 2008 TPTF Nodal Status Report: Project Status Updates Nodal Project Managers.

Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.

Lead from the front Texas Nodal 1 Texas Nodal Market Implementation Integration Update October 24, 2006 Daryl Shing, Enterprise.

Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.

Describing MCM Mission Package Software Interoperability with Architectural Descriptions.

1 SCR756 – Enhancements to the MarkeTrak application –Fondly called - MarkeTrak Phase 3 –ERCOT CEO determined that SCR756 is not necessary prior to the.

Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.

June 5, 2008 TAC Texas Nodal Market Implementation Program Update Jerry Sullivan.

October 13, 2008 TPTF Nodal Status Report: Program Update Ron Hinsley.

1 1 Texas Nodal Program UpdateMarch 21, 2008 Nodal SAS70 Audit – Readiness Approach & Timeline March ‘08June ‘08 Sept ‘08 Dec ‘08 Jan ‘09 Define Readiness.

The Open Group Architecture Framework (TOGAF)

Project Roles and Responsibilities

Design Process for Architecture

Irish Retail Market Assurance

Guidance notes for Project Manager

Design Process for Architecture

Portfolio, Programme and Project

Establishing a Strategic Process Roadmap

Design Process for Architecture

Presentation transcript:

Machine to Machine Interface Update 1 Machine to Machine Interface Update February 7th, 2007

Machine to Machine Interface Update 2 Approach to interface analysis Identify Integrations –Functional teams create CSDs. –System of Systems Architecture (SoSA) describes the enterprise level integration points needed for the overall Nodal solution. –Integration Design Authority (Technical & Business Architects), project teams and integration vendors work together to produce artifacts as described previously Repeatable Interface Specifications & Design –Integration artifacts are produced that contain: Data Element Name, Element Attributes, Volumetrics, Data Frequency etc. Business Triggering Events that drive the movement of information –The integration teams use these artifacts to analyze the interface and develop Use Cases Identify gaps, integration characteristics, mismatches and transformations of data that is necessary between systems –Integration specifications and Use Cases are the input to design and implementation of the integration between systems. –Feed the design back into SoSA.

Machine to Machine Interface Update 3 The integration factory constructs interfaces Interface Build Plan Interface Specification Interface Design Interface Build FAT & ITEST Interface team assigned Interface specs agreed Interface design agreed Interface conforms with spec Inputs Activities EDS Schedule EDS Definitions Project Schedules Interface Priorities Seek project commitments Ramp up design and build teams Produce iteration plan for the interface Outline the information flows in the interface Information flows in the interface are enumerated Interface team resolves discrepancies in interface definition between source, target & system Define behavior and information contained in the interface SoSA – use cases & domain Project CSDs Interface docs from source and target systems Integration design patterns Existing designs Source & target designs (CSD & Detailed Design) Numerous build inputs incl. Test Cases, Environment config, makefiles, … Integration pattern selected Impacts on source and target assessed and incorporated Collaborate with Source & target systems teams Spec stubs and data Interface tests defined Updated design documentation Updated test and dev environments Updated source and libraries Stubs built

Machine to Machine Interface Update 4 Integration Timeline What to expect –Several integration specification & integration design documents are currently in preparation. External interfaces will come to TPTF for approval. –Many are being produced significantly ahead of Projects’ build schedules –Rework may be necessary to Projects, SoSA and integration artifacts as the interface specification work progresses Timeline Dependencies –Work in progress - the detailed build schedules have not been finalized between projects and EDS’s –Shows earliest start, latest finish & delivery dates for interface specification and design artifacts –Based on approximately 150 external interfaces and 250 internal –Does not account for substantial refactoring

Machine to Machine Interface Update 5 Integration Timeline - Part 1

Machine to Machine Interface Update 6 Integration Timeline - Part 2