How to Improve the Safety of Signalling Systems with a Shortened Construction Period in Engineering Construction Projects Gao Guoliang Safety Assurance.

Slides:



Advertisements
Similar presentations
Kyle Hartmann. RAD was created in response to long lead times and low flexibility Focuses on communication Quicker and better requirements interpretation.
Advertisements

Prescriptive Process models
Chapter 4 Quality Assurance in Context
Taking a Waterfall Project Agile REF: Paul Geberth GCSS-J Project Manager Establishment of an Agile Project.
ISNE101 Dr. Ken Cosh. Recap  We’ve been talking about Software…  Application vs System Software  Programming Languages  Vs Natural Languages  Syntax,
Alternate Software Development Methodologies
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Agile development By Sam Chamberlain. First a bit of history..
Software Quality Engineering Roadmap
The Process of Interaction Design. Overview What is Interaction Design? —Four basic activities —Three key characteristics Some practical issues —Who are.
The Process of Interaction Design
What is Interaction Design?
RIT Software Engineering
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
SE 450 Software Processes & Product Metrics 1 Defect Removal.
Fundamentals of Information Systems, Second Edition
CS3500 Software Engineering Agile Software Development (1) Agile software development, proposed in 2001 by the non-profit Agile Alliance, has four basic.
User Centered Design Lecture # 5 Gabriel Spitz.
An Agile View of Process
Chapter 3 Software Processes.
What is Business Analysis Planning & Monitoring?
Chapter : Software Process
Chapter 3 – Agile Software Development Lecture 2 1Chapter 3 Agile software development.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Chapter 2 The process Process, Methods, and Tools
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Transaction Processing Systems and System Development Life Cycle
Chapter 3 Agile Software Development (2/2) Yonsei University 2 nd Semester, 2013 Sanghyun Park.
Why use RequisitePro RequisitePro is a comprehensive tool that supports any of today's requirements management processes. The predominant requirements.
Distributed Agile: Ten Guiding Principles Student: Yu Chang 張鈺 Raja Bavani, Chief Architect, Mindtree 28Dec Department of Computer Science and Information.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Teaching material for a course in Software Project Management & Software Engineering – part II.
Industrial Software Project Management Some views on project managing industrial and business software projects.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 3 Slide 1 Software Processes l Coherent sets of activities for specifying, designing,
Software lifecycle support and management system for safety-related signalling systems Lei Chen Research institute of general technology Beijing.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
Project monitoring and Control
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
Fundamentals of Information Systems, Second Edition 1 Systems Development.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Developed by Reneta Barneva, SUNY Fredonia The Process.
1 Software Engineering and Security DJPS April 12, 2005 Professor Richard Sinn CMPE 297: Software Security Technologies.
Agile Software Development Jeff Sutherland, one of the developers started it In February 2001, 17 Tools: continuous integration, automated or xUnit test,
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
CS 5150 Software Engineering Lecture 2 Software Processes 1.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
© 2016 LDRA Ltd The FACE Conformance Verification Matrix in Practice.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
A way to develop software that emphasizes communication, collaboration, and integration between development and IT operations teams.
CS223: Software Engineering Lecture 18: The XP. Recap Introduction to Agile Methodology Customer centric approach Issues of Agile methodology Where to.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Announcements/Assignments
CS223: Software Engineering
Progile Automated Verification Engineer • PAVE •
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
How to Successfully Implement an Agile Project
Presentation transcript:

How to Improve the Safety of Signalling Systems with a Shortened Construction Period in Engineering Construction Projects Gao Guoliang Safety Assurance Department Beijing National Railway Design and Research Institute of Signal and Communication Co. Ltd.

Agenda Great challenge and why? Feasible solutions Technique measures Overall design Risk analysis Process&Tools measures Agile development practice Utilization of automation tools Conclusion

Great challenge and why? Reality A shortened construction period for a signalling system Social Influence Small proportion share of budget Restriction and limitation from other systems Challenge Systematic process could be broke, and become disordered

Feasible solutions Removal the causes Social Influence Small share R&L from Other systems very difficult poor results Mitigation their impacts Focus the key and important tasks Technique measures Management measures

Technique measures——Overall Design Special Attention to Overall Design avoid its random modification sufficient consideration to the interactions and mutual influences strict change control Minimization of Modification of Equipments existed equipments existed pose restrictions and limitations to overall system design overall system design may necessitate change requests for them

Technique measures——Risk Analysis Effective and efficient risk analysis is the key to improving efficiency and safety. Risk Analysis Based Approach Joint efforts and involve stakeholders Share hazard log Qualitative Risk Analysis Retrospective Risk Analysis against NCRs

Process measures——Agile practices Iteration development Continuous Integration Test-driven Development

Process measures——Iteration development Incremental iteration development has the advantages of early verification and feedback of requirements to allow timely adjustment of both the direction and the focus of development during the next iteration and prioritize the release of the most important parts.

Process measures——Continuous Integration Traditional integration very difficult and risky exponentially more risky with time masks a large set of bugs Continuous integration frequent integration for small changes a clean build, full integration, and running all tests a fully working system—that is compiling, deploying, and testing— and not just a successful compile. Continuous Integration reduces time to market and increasing quality to market by finding Integration bugs often and early. Continuous Integration also increases visibility of the progress of the project by making it explicit to the development team and stakeholders.

Process measures——Test-driven Development a rapid cycle of testing, coding, and refactoring test-first development test and refactoring baby steps Test first focus on the interfaces and behaviours than implementation. The tests act as living documentation of the code, and will be run with each build for Continuous integration.

Process measures——Test-driven Development TDD uses an approach similar to double-entry bookkeeping. It’s theoretically possible for the test and code to both be wrong in exactly the same way, thereby making it seem like everything’s OK when it’s not. Pair Programming can be used to mitigate the risk, as Pair Programming could achieve synchronizing verification on codes by the way.

Tools measures——Automation testing tools Supporting tools to Agile development unit testing tools (e.g. CppUnit) building tools (e.g. Maven, Ant) continuous integration tools (e.g. CruiseControl and Hudson) Function testing tools Developed specially Integration testing tools for large signalling systems The effective utilization of can bring about considerable reduction of feedback time and improvement of work efficiency.

Tools measures—— Automatic Data Generation and Verification Tools Input and verification of massive engineering data is not possible by manual means, it is essential to apply automatic data generation and verification tools. these tools belong to the category of tool class T3, require extensive tests supplemented by manual check if necessary, as well as ergodicity tests during subsequent system tests, to minimize data errors caused by these tools.

CONCLUSION Faced with shortened construction period, supplies of signalling systems encounter the great challenge of improving the safety of signalling systems while meeting the requirements of employers. In this case, strict compliance with the requirements of the lifecycle specified in EN 50126: 1999 may have practical difficulties in producing favourable results. It is up to suppliers of signalling systems to adopt appropriate response measures to pay special attention to the key links and exercise control over the greatest risks. The measures for solving technical problems from the perspective of overall system design and risk analysis and for solving process problems from the perspective of agile development and automation tool utilization so as to maximize the safety of signalling systems under the precondition of improvement of efficiency.

Contact Details: Tel: Fax: Thank you for your attention!