AMI-Enterprise DR Use Case Team Status Terry Mohn & Kay Stefferud Miami, FL, April 14, 2009, Hosted by FPL.

Slides:

Advertisements

Similar presentations

What colour is the house on the hill? Waterloo – Wellington IIBA Chapter presentation April 11, 2007 David Milne.

Advertisements

SG-Systems Boot Camp Use Case Process with TOGAF AMI-ENT Example Kay Stefferud Chair, SG-Systems Use Cases For more information visit:

Designing an Architecture 1.Design Strategy Decomposition Designing to Architecturally Significant Requirements Generate and Test This generate-and test.

PROJECT RISK MANAGEMENT

May 2010 Slide 1 SG Communications Boot Camp Matt Gillmore 03/07/11.

For OpenSG Discussion: Preliminary SG-Enterprise Charter Greg Robinson, Co-Chair, SG-Enterprise Wayne Longcore, Chair, SG-Enterprise.

0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.

# 1 Information Exchange Standards Development Collaboration for AMI and HAN For further information, contact: Wayne Longcore

0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.

Business Technology Solutions B usiness T echnology S olutions Smart Grid Program Consumers Energy’s focus on Using and Enhancing Industry Standards.

Rose-Hulman Institute of Technology Sriram Mohan 18.September.2008 CSSE 497 Requirements Review.

1 Software Requirements Specification Lecture 14.

Phase II Instructor: Dr. Lawrence Chung Rachel Bock, Ruben Cavazos, Chih-Lin Cheng, Victor Isbell, Swathi Kandimalla, Nikhil Mishra, Amy Polcari, Ramon.

Distributed Monitoring and Mining Advisor: Dr. Stuart Faulk Team: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom Mooney OMSE-555/556 Software Engineering.

McLean VA, May 3, 2010 SG Systems Systems Requirements Specification Approach Overview.

Project CIM Test Development Process John Simmins Weekly Status and Planning Meeting 2/1/2011.

Negotiation and Specification Process

Business Analysis and Essential Competencies

HN Accounting Review Background  Review team set up April 2008, comprising representatives from 6 colleges  ‘Limited’ review –structure of HNC and.

CIM Test Development Process John Simmins Weekly Status and Planning Meeting 3/21/2011.

# 1 AMI Enterprise Task Force of the Utility AMI Working Group SRS Team Status Report (Palo Alto, Jan. 09) Joe Zhou.

E-Store System for MEHE Final status report Team #2 Sandeep, Vijay, Jennifer, Ali, Meghna April 6 th, 2007.

DGM07: Research Methodology SESSION 1 April 2, 2011 Dr. Naseem Abidi.

OpenSG Closing Plenary Oct 22 nd, Agenda SG Conformity SG Communications SG Systems SG Security Feedback Next Meeting.

# 1 AMI Enterprise Task Force of the Utility AMI Working Group Overview & Plans For further information, contact Wayne Longcore Chairman of AMI-Ent TF.

1 Iowa Core Curriculum Session 2 January

Systems Design Approaches The Waterfall vs. Iterative Methodologies.

Information Technology Project Management by Denny Ganjar Purnama, MTI Universitas Pembangunan Jaya April 2014.

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.

OpenSG Status UCAIug Members Meeting Chris Knudsen – Chair Gary Stuebing – Vice-Chair November 9 th, 2009.

Project Proposal Document Optimization 15 February 2007 Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes.

BABOK Version 3.

“SG-Systems” (Smart Grid – Operational Applications Integration) “Boot Camp” Overview Greg Robinson, Co-Chair, SG-Systems Brent Hodges, Chair, SG-Systems.

1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.

AMI Enterprise Developing Interoperability for Distribution Systems January 2009 Terry Mohn, Technology Strategist SDG&E Vice Chairman, GridWise Alliance.

Introduction A strategy was required to be able to maintain desktop configuration and reduced support cost. Hardware and software capabilities continually.

1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++

Chapter 6+7 in textbook 1 Chapter 4 Software Requirements 1.

CT1404 Lecture 2 Requirement Engineering 1 1. Today's Lecture Definition of a Software Requirement Definition of Software Requirements Management Characteristics.

AMI-Enterprise Use Case Team Status Kay Stefferud Columbus OH, July , Hosted by AEP.

CIM Test Methodology Overview John Simmins 5/3/2011.

(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.

Project CIM Test Development Process

Software Development A Proposed Process and Methodology.

Knoxville, TN October 20, 2009 SG-Systems Systems Requirements Specification Team Status and Breakout Session.

What's New for Build Automation in Team Foundation Server 2015 Paul Hacker Solution Architect, Microsoft ALM MVP.

Overview AMI-Enterprise For further information, contact: Wayne Longcore Chair of AMI-Enterprise Task Force, Board Of Directors.

May 9th 2011 IETF SIPREC INTERIM - draft-ietf-siprec-architecture 1 An Architecture for Media Recording using the Session Initiation Protocol draft-ietf-siprec-architecture.

Lecture 4: Enterprise Architecture

CIM Test Development Process John Simmins Weekly Status and Planning Meeting 3/15/2011.

SG-Systems Working Group Status: Active, meet once at each face-to-face meeting Charter: The SG-Systems Working Group defines requirements, policies, and.

Software Requirements Specification Document (SRS)

Requirements Analysis

Slide 1 EIM Charter Identify and articulate common EIM requirements: Use cases System Requirements Specification (SRS) Work with other OpenSG groups, particularly.

“SG-Systems” ( Smart Grid – Operational Applications Integration ) Charter & Status Greg Robinson, Co-Chair, SG-Systems Brent Hodges, Chair, SG-Systems.

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

SmartPosition Customer Review and Feedback Presentation.

Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.

Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.

B U D I L U H U R U N I V E R S I T Y POST GRADUATE PROGRAM MAGISTER ILMU KOMPUTER (M.Kom) IS PROJECT MANAGEMENT.

CIM Test Development Process

Requirement Engineering

TPM – A Tailored Approach Project Management Web Button Design

How can we move the Cash Transfer debate forward at national level?

Project Analysis Course

EIM Charter Identify and articulate common EIM requirements:

Requirements Factoring Themes

Effective Project Management: Traditional, Agile, Extreme

Presented by (Abdisamad Abdullahi Abdulle)

Use Case Process with Examples Kay Stefferud

Presentation transcript:

AMI-Enterprise DR Use Case Team Status Terry Mohn & Kay Stefferud Miami, FL, April 14, 2009, Hosted by FPL

Methodology Functional Requirements Functional Decompo- sition Use Case Development Functional Requirements SRS Service Definitions

Functional Decomposition Example

Business Process Model Example

Use Case Model Example

Sequence Diagram Example

Vetting the Functional Requirements Functional Requirements specify WHAT not HOW –Shall manage demand –Not “Shall reduce demand using direct control of swimming pool pumps” Characteristics of good requirements –Unambiguous, clearly stated –Complete –Testable, verifiable –Required, mandatory –No “ands”, no “ors”

Functional Requirements Working Session 3-4 small groups Evaluate subset of requirements Requirement statement, contains “shall” –Clear Yes/No –Needed Mandatory Optional Future –Verified Yes/No

Moving Forward Identify and prioritize remaining scope Identify stakeholders for Enterprise Architect (EA) model Identify publically available server for EA model DR Distribution Automation Outage Management etc OpenSG NIST IEC others DOE OpenSG IEC