SC-B5 Colloquium Calgary 2005 CIGRE SC B5 COLLOQUIUM CALGARY Contribution to PS2 – Q#1 How does the specification team value this user input and rank prioritization.

Slides:



Advertisements
Similar presentations
The e-Framework Bill Olivier Director Development, Systems and Technology JISC.
Advertisements

NetPay provides best and effective solution for company Managers to maintain their employee scheduling task (including staff in/out details, overtime,
Deep Learning and Neural Nets Spring 2015
Design Concepts and Principles
Risks  All projects have some degree of risk  Risks are issues that can cause problems  Delay in schedule  Increased project costs  Technical risk.
Frankfurt (Germany), 6-9 June 2011 Coordination between TSOs and DSOs – a necessity for system planning and operation Dr. Ralph Pfeiffer Amprion GmbH 1.
Preventive Software Maintenance: The Past, the Present, the Future Nikolaos Tsantalis Computer Science & Software Engineering Consortium for Software Engineering.
Steven A. Kunsman (USA) CIGRE Study Committee B5 Preferential Subject 2 Specification and Evaluation of Substation Automation Systems Session Summary Steven.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
INFORMATION SYSTEMS PLANNING Module A. Stakeholder Requirements Specification Information Technology Staff Analysis Design and Implementation Requirements.
Administrivia Lifecycle Architecture (LCA) group assignment will go out later today. Informal feedback meetings with LCO groups EasyShare: Mon, 2:45pm-3:15pm,
Types of Requirements  Functional Requirements  Descriptions of actions or processes that create or update information.  Outlines of reports or on-line.
171 Use Case Descriptions Chapter 4 – Facade Iteration Initial Requirements (Inception Phase)
On Fairness, Optimizing Replica Selection in Data Grids Husni Hamad E. AL-Mistarihi and Chan Huah Yong IEEE TRANSACTIONS ON PARALLEL AND DISTRIBUTED SYSTEMS,
AJAC Systems Hotel Reservation System
Planning. SDLC Planning Analysis Design Implementation.
Slide 1 Requirements Workflow. Slide 2 The Phases/Workflows of the Unified Process Figure 3.1 l Phase is Business context of a step Workflow is Technical.
OSG Logging Architecture Update Center for Enabling Distributed Petascale Science Brian L. Tierney: LBNL.
Monitoring the Regional Framework for Action for Children
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Investigating System Requirements
Support for design of statistical surveys at Statistics Sweden
Project Administration Chapter-4. Project Administration Project Administration is the process which involves different kinds of activities of managing.
BTS Business Trip Scheduler Lital Badash Eran Banous Yanir Quinn Academic Advisor: Prof. Ehud Gudes Technical Advisor: Mr. Eugene Kovalyov (Amdocs) Mr.
SE: CHAPTER 7 Writing The Program
Problem Statement: Users can get too busy at work or at home to check the current weather condition for sever weather. Many of the free weather software.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
SC-B5 Colloquium Calgary 2005 CIGRE SC B5 COLLOQUIUM CALGARY Contribution to PS2 – Q#2 Contribution to PS2 – Q#2 What are the experiences in utilities.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 7 Storing Organizational Information - Databases.
Capacity Building Committee Architecture and Data Committee Meeting Seattle – July 2006.
An iPhone Application By Negar Shojaian, Matt Akkerman and Kevin Kang.
1 februari 2007 Martha Brouwer (program manager Traffic Management and Public Transport) Network Operations in the Netherlands.
Software Engineering COSC 4460 Class 4 Cherry Owen.
Supporting New Business Imperatives Creating a Framework for Interoperable Media Services (FIMS)
. A PRESENTATION ON “ ANDROID APPLICATION FOR ALZHEIMER PATIENT ” BY: HEMALI VITHALANI AASHKA KOTECHA TRISHLA SHAH GUIDED BY: PROF.RADHIKA KOTECHA.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Abstract Introduction End Product & Deliverables Resources Project Requirements Team Members: Faculty Advisors: Client: Team Members: Faculty Advisors:
Cigre / IEC UHV Symposium, New Delhi Strategic Agenda for CIGRE‘s Technical Activities Klaus Fröhlich.
CSE 303 – Software Design and Architecture
INFORMATION X INFO425: Systems Design Systems Design Project Deliverable 1.
1  [company] Inc. [year] Girl Scouts of the USA Secure Site Project Kickoff [date]
Program Development Cycle
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 6 Essentials of Design.
CIGRE Study Committee B5 Colloquium September 2005, Calgary, Canada PS1 - Question 7 What would be the future practice for selecting harmonic restraint.
Statistics Monitor of SPMSII -High level and detailed design Warrior Team Pu Su Heng Tan Kening Zhang.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
INFSO-RI Enabling Grids for E-sciencE NA2 Dissemination and Outreach Joanne Barnett, EGEE External Relations Officer, TERENA Secretariat.
Roommates Carlos Csiszer Brooke Gallagher Daniel Katz Madeline McCann Trinity Sheppard Cristian Taveras.
Organizing and leading the IT function Two set of tensions guide policies for developing, deploying and managing IT systems. 1.Innovation and control a.How.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Investigating System Requirements
Information Systems Development
CIGRE SC B5 COLLOQUIUM CALGARY
Stream 2: Technical research Achievements and future plans
Cigre SCB5 Colloquium 2005 September, Calgary Preferential Subject 2
CIGRE 2005 SC B5 Contribution to Question 2-1
V-Shaped SDLC Model Lecture-6.
Systems Analysis and Design in a Changing World, 6th Edition
Lenovo Technical

Fast Acer Technical Support By Call PC Expert

Investigating System Requirements
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Eight-QueenS Problem: Fuzzy Constraint Satisfaction Problem Using Soar
Portfolio, Programme and Project
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
Singular Selection of Format
Title of slides 2019 CIGRE SC-A2, B2 & D1 INDIA COLLOQUIUM
Dragonfly Initiation and Planning Request
Presentation transcript:

SC-B5 Colloquium Calgary 2005 CIGRE SC B5 COLLOQUIUM CALGARY Contribution to PS2 – Q#1 How does the specification team value this user input and rank prioritization of the requirements ? How should lower priority requirements be stated in the specification since these requirements may easily be fulfilled by the technical solution at minimal cost ? CIGRE SC B5 COLLOQUIUM CALGARY Contribution to PS2 – Q#1 How does the specification team value this user input and rank prioritization of the requirements ? How should lower priority requirements be stated in the specification since these requirements may easily be fulfilled by the technical solution at minimal cost ? Florin Balasiu, Transelectrica Romania

SC-B5 Colloquium Calgary 2005 Costumer technical specifications contain: 1. Functional requirements system functions protection functions supervision&control functions 2. Performance requirements overall performance – time synchronisation and time response reliability, availability, security requirements maintainability and expandability 3. Constrains interfaces to NCC and to Protection-Control Centre limitations due to existing buildings, roads, preserved structures Prioritization of requirements

SC-B5 Colloquium Calgary 2005 Functional requirements for OHL protection functions example Mandatory Suggested

SC-B5 Colloquium Calgary 2005 Mind the importance of the substation in the grid e.g. only main 1 protection for certain 220 kV OHLs Focus on “what” instead of “how”. Avoid too many details. e.g. protection&control architecture functional redundancy – n-1 criterion Preference for requirements based on international standards Extensive use of previous experience – updated internal procedures Use weighting questionnaires for divergent issues Use old stagers together with young ones Prioritization of requirements – Hard task