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

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

3. Functional Decomposition Example

4. Business Process Model Example

5. Use Case Model Example

6. Sequence Diagram Example

7. 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”

8. 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

9. 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