Embed Size (px)
Citation preview
REQUIREMENTS MANAGEMENTSOFTWARE: AN OVERVIEW
FEBRUARY 2018
• Introduction to Fenix Australasia
• Background
• Overview of Software functionality
• Demonstration
• Application of the software
• Commercial arrangements
• Questions
OVERVIEW OF PRESENTATION
INTRODUCTION
Fenix Australasia was established in 2018 and forms part of Fenix Rail Systems.
We aim to help the Australasian rail industry prepare for the future through adoption of technology and innovation.
Our team has a track record for providing trusted advice and rail systems engineering services to the rail industry across Australasia.
Backed by our parent company, Fenix Rail Systems, we are respected for our work in delivering information, signalling and communications technology solutions.
OUR LEADERSHIP TEAM
Craig Purcell, Group CEO
Mark Quintana, Regional Director
Brian McNaughton, Technical Director
Eddie Murphy, Project Director (Worldwide)
RAIL SYSTEMS REQUIREMENTS MANAGEMENT SOFTWARE
BACKGROUND
MGB Systems were approached by Hitachi Rail to assist them in the development and Management of a Customised Requirements Management (RM) Database for the Rail Systems Requirements for the Ho Chi Minh Urban Railway Project (Line 1).
Hitachi determined they needed a customised database suited to their project, rather than a commercial ‘off the shelf’ product such as IBM DOORS.
They felt that a customised system would allow for a flexible and cost effective approach to the RM process.
The result was a bespoke software product developed for that project and for other applications.
HO CHI MINH URBAN RAILWAY (LINE 1) PROJECT
Signalling Communications Overhead Traction Power System
Trackwork Rolling Stock
T h e P r o j e c t
Power Systems Facilities SCADA Platform Screen Doors
Fare Collection Systems
Depot Equipment and Systems
Design of a Customised RM Database to manage the System Requirements for 10 sub-systems including:1
THE PROJECT BRIEF
T h e P r o j e c t Initial Database Development Workshop with Hitachi to identify the functional requirements of the database.
Development and Initial Population of the Database with System Requirements taken from project specifications and other documents supplied by Hitachi (System Requirements Specification – SRS)
Assignment of System Requirements to Sub-Systems (Sub-System Requirements Specifications - SSRS)
Act as the Requirements Manager for the system during the initial stage (Technical Design - TD) of the project
Verify compliance with requirements during TD stage of the project. MGB reviewed/verified nominated compliance evidence for TD stage for all sub-systems
Train Hitachi staff in Vietnam in Requirements Management principles and in the use of the Requirements Management Database
2
3
4
5
6
7
REQUIREMENTS MANAGEMENT PROCESS
The RM Database was specifically designed to support the V&V process detailed in Hitachi’s Project Verification and Validation Plan.
The objective of the V&V plan was to provide traceability from System Requirements identified from project specifications, plans, etc., to compliance evidence compiled from verification activities undertaken at nominated stages of the project.
RM SOFTWARE FUNCTIONALITY
The following slides describe the current database functionality and
the associated V&V process.
Software functionality can be modified to suit an alternative process specified by the client.
HOW TO USE THE SOFTWARE
STAGE 1Requirements identification
STAGE 2Configuration
STAGE 3Verification &
Validation
Reports
HOW TO USE THE SOFTWARE
Agree project requirements source documents.
• Identify requirements.
• Define sub systems.
• Define project stages where compliance with requirements is to be tested.
Example Source documents:
• System Assurance Plans
• System Specifications
• User Specifications
• Hazard Logs
• Operation and Maintenance Requirements
• Any other source where system requirements are identified
Example Project Stages:
• Technical Design, Preliminary Design, CCB Gate1, etc.
• Construction and Installation Design, Detailed Design, CCB Gate 2 etc.
• Testing and Commissioning, SAT, FAT, SIT etc.
STAGE 1Requirements identification
STAGE 2Configuration
STAGE 3Verification &
Validation
Reports
HOW TO USE THE SOFTWARE
• Customise database.
• Populate requirements.
• Assign requirements to sub systems.
• Define verification and validation activities.
• Nominate type of V&V activity required at each stage
STAGE 1Requirements identification
STAGE 2Configuration
STAGE 3Verification &
Validation
Reports
System & Sub System Requirements Specifications
HOW TO USE THE SOFTWARE
• Compliance evidence nominated.
• Review compliance evidence (V&V activity).
• Record compliance status and review comments
Typical activities:
• Nominate evidence
• Review evidence
• Add comments recording outcome of review
• Update V&V status
STAGE 1Requirements identification
STAGE 2Configuration
STAGE 3Verification &
Validation
Reports
HOW TO USE THE SOFTWARE
STAGE 1Requirements identification
STAGE 2Configuration
STAGE 3Verification &
Validation
Reports
Report Type Summary
SRS Report A complete (or filtered) list of Requirements listed in the database
SSRS Reports Sub-System Reports showing requirements assigned to a particular sub-system. Includes details of V&V activities & status
Gap Report Filters the requirements to only display those that have not reached the ultimate status – Verified or Validated
Deleted and Superseded Reports
Retained in the database but not normally displayed in SRS or SSRS reports
Custom reports Other Reports designed during configuration stage
OTHER FUNCTIONALITY & INFORMATION
Web based application.
Can be hosted on Client or off-site web servers.
O.S.: Windows Server 2008 or later.
Internet Information Services 7 or later.
Microsoft .Net framework 4.5 or later.
Database: MS SQL Server 2008 or later
Configurable User Rights.
Delete and Supersede Requirements.
Software optimised for Microsoft web browser. Can be used with other browsers.
SOFTWARE DEMONSTRATION
REFEREE
“It demonstrates traceability from a statement within a document/ test procedure/test report
to a technical requirement.”
“They find the system easy to use especially the people who have used DOORS before; it is
simple to use and compliant system.”
“Our Internal ISA is happy we now have a process and databases. It is easy to use
and fully traceable system”
B a r r y B a l d r e y , H i t a c h i
APPLICATION OF SOFTWARE
Requirements Management of internal projects – Internal project team reporting to Project Manager.
Requirements Management of external contractors – Internal project team performing verification and validation of contractor evidence of compliance against requirements.
Contractor Management – Contractors can prepare data for inclusion in the database in a pre-defined spreadsheet format.
COMMERCIAL ARRANGEMENTS
One off, perpetual license fee across PTA.
Fee for service for:
Bespoke development
Specific PTA wide or project configuration.
Annual maintenance fee
Schedule of rates for support
QUESTIONS
THANK YOU
Fenix Australia (Australasia)Levels 20 & 21
Tower 2 Darling Park201 Sussex Street
SydneyNew South Wales
NSW 2000Australia
www.fenixrailsystems.com
