Use Case Process with Examples Kay Stefferud kay.stefferud@lmco.com AMI-Enterprise Use Case Process with Examples Kay Stefferud kay.stefferud@lmco.com Presented at UCA Boot Camp July 13, 2009 AEP Columbus Ohio

Methodology SRS Use Cases: Best Practice for Requirements Development Functional Requirements Functional Decompo-sition Use Case Development Detailed System Definition Service Defini-tions SRS Use case development is considered a best practice to derive requirements. Use case formats vary. Typical formats are textual, sequence diagrams and graphical. Purpose of use cases is to convey the system functions and how the system will be used. Use Cases: Best Practice for Requirements Development

Use Case Example – Textual Title I1: Utility installs, provisions and configures the AMI [and Utility HAN] system Section 1 – Overview Section 2 – Actors Actor Name Actor Type Actor Description Section 3 --Scenarios Triggering Event Primary Actor PreCond PostCond Section 4 – Functional Requirements Functional Requirements Associated Scenario Associated Step Section 5 - Information Exchange Use case diagram abbreviated example of textual format. Full versions typically run from 2-4 pages. SCE textual use cases run 10-20 pages. Title is Utility installs, provisions and configures the AMI [and Utility HAN] system

Use Case Example – B1.3 Use case diagram example with swim lanes – referred to as sequence diagram Title is AMI Meter transmits non-usage (event) messages Scenario steps are numbered from 01 to 08

UCA Use Case Enterprise Architect (EA) Format Contain: Business Process Models Functional Decomposition Graphical Use Cases Requirements Sequence Diagrams High Level Class Architecture Posted on UCA AMI ENT site http://osgug.ucaiug.org/utilityami/AMIENT/Shared%20Documents/Use%20Cases/AMI%20ENT%20Use%20Cases%20version%201.0.doc Use case standard process used for Demand Response Management System (DRMS)

Business Process Model Example – EA DRMS Business Process Model an example from DRMS Use cases. Business Process Models typically diagrammed early in use case development. Title is Remove DR Device from Data Repository.

Functional Decomposition Example – EA Functional Decomposition diagram example using Enterprise Architect (EA). Functional decomposition diagrams help define the overall system functionality and define the system in a logical manner. Many different functional decompositions are possible, and functional decompositions do not define system architectural features.

Use Case Example – EA DRMS Use case diagram example using Enterprise Architect (EA). Title is Provision Demand Response Equipment. Add DR Device Requirements are shown on the next slide.

Example – DRMS Requirements 3.10.1 Add DR Device 3.10.1-1 The DR solution shall manage the provisioning of new active DR devices. 3.10.1-2 If a DR device is capable of self-configuring on a network, then the DR solution shall be capable of commissioning the device into the DR program. 3.10.1-3 The DR solution shall maintain a database of all active DR devices. 3.10.1-4 The DR solution shall manage the provisioning of existing active DR devices. 3.10.1-5 The DR Solution shall validate the location of DR devices. 3.10.1-6 The DR solution shall manage the provisioning of new types of future DR devices. Use case diagram abbreviated example of textual format. Full versions typically runs from 2-4 pages. SCE textual use cases run 10-20 pages. Title is Utility installs, provisions and configures the AMI [and Utility HAN] system

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

Moving Forward – Class Architecture