1 / 11

AMI-Enterprise

AMI-Enterprise. End-to-End Process Example October 2009. Overall Document Summary. Use Cases  System Reqs Spec (SRS)  Service Definitions. Business Processes to Services Methodology. End-to-End Example Step 1. Use Case Functional Decomposition. Function. End-to-End Example Step 2.

boris-walter
Download Presentation

AMI-Enterprise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AMI-Enterprise End-to-End Process Example October 2009

  2. Overall Document Summary Use Cases  System Reqs Spec (SRS)  Service Definitions

  3. Business Processes to Services Methodology

  4. End-to-End ExampleStep 1 Use Case Functional Decomposition Function

  5. End-to-End ExampleStep 2 Use Case Business Process BusinessActivity = Capture Compliance

  6. End-to-End ExampleStep 3 Use Case / Functional Requirements 3.8.8 Measurement and Verification 3.8.8-1 The DR solution shall provide the ability to measure the load reduction from DR program execution. 3.8.8-2 The DR solution shall provide the ability to validate the load reduction from DR program execution.

  7. End-to-End ExampleStep 4 SRS Use Case to Service Requirements Relationship Meter Reading Service

  8. End-to-End ExampleStep 5 SRS Class Relationship Meter Reading Classes

  9. End-to-End ExampleStep 6 Service Definitions: Services and Operations

  10. End-to-End ExampleStep 7 Service Definition SOA Artifacts • Service • MeterReading • WSDL/Design Artifacts • WSDL and XSD posted here: http://osgug.ucaiug.org/sgsystems/OpenAMIEnt/Shared Documents/Service Definitions/AMI-ENT_Artifacts.zip • MessageHeader.xsd • MeterReading.wsdl • MeterReadingRequest.wsdl • MeterReading.xsd • StandardAttachment.xsd • OutputData.xsd

  11. End-to-End ExampleStep 8 Service Definitions XML <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:m="http://www.smartgridipedia.org/2009/05/StandardAttachment" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xmime="http://www.w3.org/2005/05/xmlmime" targetNamespace="http://www.smartgridipedia.org/2009/05/StandardAttachment" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0"> <xs:import namespace="http://www.w3.org/2005/05/xmlmime" schemaLocation="xmlmime.xsd"/> <xs:element name="StandardAttachment" type="m:StandardAttachment"/> <xs:complexType name="StandardAttachment"> <xs:sequence> <xs:element name="Attachment" type="xmime:base64Binary" minOccurs="0"/> <xs:element name="AttachmentInfor" type="m:AttachmentInfor" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="AttachmentInfor"> <xs:sequence> <xs:element name="id" type="xs:string" minOccurs="0"/> <xs:element name="name" type="xs:string" minOccurs="0"/> <xs:element name="description" type="xs:string" minOccurs="0"/> . .. . . </xs:complexType> <xs:simpleType name="compressFlag"> <xs:restriction base="xs:string"> <xs:enumeration value="yes"/> <xs:enumeration value="no"/> </xs:restriction> </xs:simpleType> <xs:complexType name="AttributeList"> <xs:sequence> <xs:element name="sequence" type="xs:string" minOccurs="0"/> <xs:element name="name" type="xs:string" minOccurs="0"/> <xs:element name="value" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:complexType> </xs:schema>

More Related