http://nodal.ercot.com 1Lead from the front

Texas Nodal

Assurance Framework

CSD Template

Jeyant Tamby

November 6, 2006

http://nodal.ercot.com 2Lead from the front

Texas Nodal

Development and Assurance Framework for Texas Nodal

• ERCOT RUP (aka powERUP) is a RUP based development and assurance framework that accounts for:– We said we will “do RUP, but with exceptions …”, meaning RUP in a COTS

environment– We have different levels of RUP usage across vendors– We are working to the Nodal Transition Plan

• ERCOT RUP is a web-site that contains– Definition of the development lifecycle– Definition of a minimum set of work-products at project and program levels– Guidelines for producing and reviewing the work products

• This is an basic introduction to ERCOT RUP, covering:– powERUP Website– Work Product Checklist– Conceptual System Design Template and Checklist

http://nodal.ercot.com 3Lead from the front

Texas Nodal

http://nodal.ercot.com 4Lead from the front

Texas Nodal

http://nodal.ercot.com 5Lead from the front

Texas Nodal

http://nodal.ercot.com 6Lead from the front

Texas Nodal

Work Product Checklist

• Milestones– Lifecycle Objectives– Preliminary Architecture– Lifecycle Architecture– Internal Operational Capability– preFAT– FAT– Program Level: SAT & EDS

• Disciplines– Requirements– Analysis & Design– Implementation– Test– Deployment

• Work Products

http://nodal.ercot.com 7Lead from the front

Texas Nodal

Project-level Work Products LCO PA LCA IOC Pre-FAT FAT Description

Business Requirements B UBusiness Requirements are used to gain TPTF approval. Contains Functional Requirements and Supplementary Requirements

Vision/Charter B UThe vision represents thebreadth view of the requirements and drives scope management in iterative projects. Contains: Use case model diagram, use case outlines, stakeholder profiles

Use Case Model Survey D B U

The use case model survey contains the list of use cases and actors and their short descriptions. Additionally, the survey contains a diagram that shows the relationships between the use cases and actors. It provides a "table of contents" to the set of use cases for the project.

Supplementary Specification D B UThe supplementary specification captures the non-functional requirements and the functional requirements that are common to ultiple use cases.

Use Case Specification D B UThe use case specification contains the textual properties for a specific use case, including the basic flow of events, alternative flows and related information.

Conceptual Design Document D B U UThe Conceptual Design document gives the high-level view of the architecture and is used to validate requirements, identify project risks, and gain alignment between projects

Detailed DesignThie Detailed Design work product packages the Software Architecture Document, the Data Model and the Data Migration Document together.

Software Architecture Doc D B UThe Software Architecture Document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system

Architectural Proof of Concept C C

The Architectural Proof of Concept is a working version of the application that implements the architecturally significant use cases. Its goal is to prove that the architecture is sound and that the technical risks have been reduced or eliminated.

User Interface Prototype C CThe User Interface Prototype shows the views and navigation of the proposed user interface

Data Model D B UThe Data Model defines the physical structure of the data and the data dictionary.

Data Migration Document D BThe Data Migration document defines the source to target data mapping and any transformations required to get current system data migrated to the Nodal system.

Standard Interfaces Document D B U The Standard Interfaces Document defines the externally-visible view of the services provided by a project, including the inputs, outputs, and processing.

Migration Control Document D B U U

The purpose of the Migration Control Document is to define the order in which the components should be implemented, which builds to create when integrating the system, and how components are to be deployed and assessed.

Code Review Checklist B B B BThe purpose of the code review record is to capture the results or conclusions of the code review activity and identify any action items arising from the review

Unit Tests and Log B B B B

Unit tests encompass the developer testing of the product. It includes unit testing and integration testing. The unit test log contains raw output captured during a unique execution of one or more tests. The purposes of a unit test log are to provide verification that a set of unit tests was executed, and to provide information relating to the success of those unit tests.

Test Execution Plan B B B BThe test execution plan identifies which test cases will be run by whom and when.

Test Case B B B B A test case describes a single scenario to be executed as a test.

Re

qu

ire

me

nts

An

aly

sis

an

d D

es

ign

Imp

lem

en

tati

on

Te

st

Project Level Work Products

http://nodal.ercot.com 8Lead from the front

Texas Nodal

Program Level Work Products

Program-level artifacts These work products constrain the project-level work products

Requirements Management Plan

Describes the requirements artifacts, requirement types, and their respective requirements attributes, specifying the information to be collected and control mechanisms to be used for measuring, reporting, and controlling changes to the product requirements.

Reference ArchitectureTest StrategyTest PlanConfiguration Management PlanRisk Management Plan

http://nodal.ercot.com 9Lead from the front

Texas Nodal

Conceptual System Design

• Content Template

• Content Checklist

• Project Example

• CRR CSD

CSD Checklist

CSD

http://nodal.ercot.com 10Lead from the front

Texas Nodal

Questions

Q?