22-01-2008 Stephane Deghaye (AB/CO) ATC/ABOC days.

Slides:



Advertisements
Similar presentations
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Advertisements

RUP/UP Software Development Method Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
1 Prescriptive Process Models. 2 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive process.
ITIL: Service Transition
FESA 3 Implementation Status Stephane Deghaye BE/CO On behalf of the FESA team and many users.
Object-Oriented Analysis and Design
Rational Unified Process
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Software IMprovement using Product LinEs Project Final Presentation Liana Lisboa – PM Project: Starship.
Iterative development and The Unified process
COMP 350: Object Oriented Analysis and Design Lecture 2
The web application development process Basharat Mahmood, COMSATS Institute of Information Technology, Islamabad, Pakistan. 1.
Software System Integration
Accelerator Complex Controls Renovation, LHC Excluded Purpose and Scope M.Vanden Eynden on behalf of the AB/CO Group.
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 CMPT 275 Software Engineering Software life cycle.
RUP Fundamentals - Instructor Notes
Using IBM Rational Unified Process for software maintenance
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
The Rational Unified Process
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Object Oriented Analysis and Design Introduction.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Object Oriented Design and Analysis Rational Unified Process.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
WWWWhat timing services UUUUsage summary HHHHow to access the timing services ›I›I›I›Interface ›N›N›N›Non-functional requirements EEEExamples.
Chapter 7 Applying UML and Patterns Craig Larman
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Status Report – Injection Working Group Working group to find strategy for more efficient start-up of injectors and associated facilities after long stops.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 8 Workflows of the Process Taken from Walker Royce’s textbook – Software Project Management plus a number of Personal Comments.
The Rational Unified Process 1 EECS810: Software Engineering.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Nov, F. Di Maio, M.Vanden Eynden1 CO Proposal concerning AB Front-End Software Responsibilities First detailed proposal based on the global Front-end.
Rational Unified Process (RUP)
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
26 Jan 06Marine Pace - AB/CO1 LEIR Controls : Gain of Experience for the Running-in of LHC Marine Pace on behalf of AB/CO and LSA.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
AT Control Forum First Meeting. Introduction  The AT Controls FORUM :  Is responsible for coordination of the overall strategy for controls activities.
Feedbacks from EN/STI A. Masi On behalf of EN-STI Mathieu Donze` Odd Oyvind Andreassen Adriaan Rijllart Paul Peronnard Salvatore Danzeca Mario Di Castro.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Introduction Requirements and the Software Lifecycle (3)
Final Report – Injector Re- Commissioning Working Group (IRWG) Working group to find strategy for more efficient start-up of injectors and associated facilities.
LS1 – View from Applications BE-CO LS1 review – 1 December 2015 Greg Kruk on behalf of the Applications section.
Stephane Deghaye (AB/CO) The InCA project - S. Deghaye Accelerator Complex Controls Renovation Workshop Motivations & Objectives.
Proposal: Use of ECRs for “Controls” Changes and Renovations Rende Steerenberg, Samy Chemli, Marine Gourber-Pace, Klaus Hanke, Verena Kain, Bettina Mikulec,
The OP Viewpoint on the Accelerator Complex Controls Renovation R. Steerenberg on behalf of the OP group Accelerator Complex Controls Renovation Workshop.
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
Object oriented analysis and design 1 Software Development Life Cycle (SDLC)
CS 389 – Software Engineering Lecture 2 – Part 2 Chapter 2 – Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
TK2023 Object-Oriented Software Engineering
Software Development.
V4.
Status and Plans for InCA
The Web Application Development Process Models
DT249/4 Information Systems Engineering Lecture 0
FESA evolution and the vision for Front-End Software
COMP 350: Object Oriented Analysis and Design Lecture 2
Chapter 2 – Software Processes
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Other System Requirements
Presentation transcript:

Stephane Deghaye (AB/CO) ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 2 InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 3 InCA - S. Deghaye ATC/ABOC days

From Strategy for PS complex control software renovation Working Group Mandate, M. Benedikt, E. Hatziangeli, R. Steerenberg. 1.Summarise the PS complex requirements for Core control software. 2.Evaluate the application of the present LHC Software Architecture (LSA). 3.Draft a proposal for an adaptation of LSA to comply with the requirements. 4.Develop an alternative proposal based on the existing PS control philosophy. 5.Compare both solutions. 4 InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 5 InCA - S. Deghaye ATC/ABOC days

InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 7 InCA - S. Deghaye ATC/ABOC days

Presentation of LSA Current features of LSA core Standard applications (Trim editor, EquipState…) Good basis for parameter control  Needs modifications (top-down & bottom-up)  GUI philosophy not suitable (choose action  select GUI  select device)  Lack of acquisition & statuses 8 InCA - S. Deghaye ATC/ABOC days

Presentation of Java/XMotif PS system Generic applications Configuration tools GUIs fit user requirements (acquisitions…)  Some parts have become obscure  Performance & Scalability problems  Low-level services only and difficult to extend 9 InCA - S. Deghaye ATC/ABOC days

LSA: good basis but modifications needed.  LSA: Big area of requirements not covered. PSA: Look & feel fit the needs.  PSA: performance & scalability problems  PSA: obscure & obsolete parts  Injector Control Architecture 10 InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 11 InCA - S. Deghaye ATC/ABOC days

InCA - S. Deghaye ATC/ABOC days

InCA - S. Deghaye ATC/ABOC days 13 Reuse CO components Modif. to fit Injector needs

InCA - S. Deghaye ATC/ABOC days 14 Performance Scalability Flexibility Security

InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 16 InCA - S. Deghaye ATC/ABOC days

Need to synchronise with eqp group renovation programs Ready with high-level controls when they go PRO Not too early to avoid unnecessary development Slow down or speed up their renovation to minimise temporary solutions. Close contact with CO3 1 st round of discussion with eqp groups done 17 InCA - S. Deghaye ATC/ABOC days

InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 19 InCA - S. Deghaye ATC/ABOC days

InCA - S. Deghaye ATC/ABOC days 20 Inception: Vision & 1 st version Use Case model done. Elaboration: Validation of the architecture with critical Use Cases implemented: Parameter acquisition. Parameter hierarchy refactoring ABS (hardware renovation)

InCA - S. Deghaye ATC/ABOC days 21 Construction: Implementation of the other Use Cases & Periodic MDs to validate the developments Transition: InCA in production. Low-priority Use Case development & bug fixes

InCA - S. Deghaye ATC/ABOC days The system is put in production after few iterations to validate the developments  Machine time needed ! Tests foreseen in 2008 (4 * 1/2 day)

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 23 InCA - S. Deghaye ATC/ABOC days

Parameter acquisition scalability To be tackled in 1 st prio (elaboration phase). Need to work in the FEC part as well (vertical picture) Changes in the parameter hierarchy model (  &  ) To be tackled in 1 st prio (elaboration phase). GM classes owned by eqp groups Close contact with CO3. Component-based Needs work & support from the teams in charge (LSA, SIS, OASIS…).  LHC is still 1 st prio but InCA work must be included in plannings. Teething problems Unavoidable! Reduced effect by periodic MDs. 24 InCA - S. Deghaye ATC/ABOC days

PS Complex Control Software Renovation WG Requirements - What Services? Solution Evaluation – LSA, PS system. Injector Control Architecture  Component View  3-tier Architecture  Deployment View Dependencies with AB groups Project Planning Risks & Solutions Conclusions 25 InCA - S. Deghaye ATC/ABOC days

PS Renovation Working Group Summary of the PS complex requirements. Vision & Glossary in EDMS (doc no & ) Evaluation of LSA & PS systems  InCA proposal InCA 3-tier system based on AB/CO modules Keeps WorkingSet/Know view in the CCC PS bay.  New components & modifications of the existing ones needed to fulfil injector needs.  Close contact with the eqp groups.  Machine time to validate 26 InCA - S. Deghaye ATC/ABOC days

Thank you for your attention! 27 InCA - S. Deghaye ATC/ABOC days