Incose: People, process, tools webinar - visure solutions - systems engineering

www.visuresolutions.com

People, Process and Tools:People, Process and Tools:The Path to Better Requirements

Marcia Stinson

Introducing Marcia Stinson

� 20 years experience in formal software development and system engineering, including weapon control systems

� Requirements engineering consultant to Fortune 500 companies, helping them develop requirements processes,

them develop requirements processes, templates, guidelines, information models and aids

� IIBA-certified instructor in use case and elicitation methods

� Former VP of Professional Services at Telelogic

� M.S. Mathematics, and B.S. Mathematics and Education, Central Missouri State University

Agenda

What we’ll cover

� The importance of good requirements

� Training people on the process, and the skills required to follow the process effectively

� Defining a process for requirements definition and

� Defining a process for requirements definition and management

� Selecting tools that support your process

The Importance ofThe Importance ofGood Requirements

The Requirements Effect

Study after study has

shown that clear,

accurate and

complete

requirements have the

biggest impact on Waste 46% of your time

Faulty requirements and low requirements maturity:

biggest impact on

project success.

IAG Consulting found

that faulty

requirements can eat

up 39% or more of

your resources. Deliver fewer projects on time and on budget

Waste 39% of your development budget

Source: “Borland: Best Practices for Requirements Development & Management”

Only a third of projects

succeed

� Systems and software

projects with poor

requirements experience

more defects, delays and

cost overruns

� 68% of projects are delivered

Source: CHAOS Summary, The Standish Group, 2009

� 68% of projects are delivered

late, over budget, or not

according to requirements.

� Less than a third are

successful.

� 24% are cancelled before

they are completed, or

delivered but never used.

Understanding your internal

customers' software

requirements is crucial to

delivering the right solutions

� Meet their needs

� Keep the organization running effectively

The Effect of Requirements Analyst Capability

The requirements analyst capability is the most

significant contributor to project effort.

� Best requirements analysts: 29% less effort

� Worst requirements analysts: 42% more effort

42%-29% Requirements Analyst Capability

42%-29%

-24% 34%

-19% 22%

-19% 29%

-16% 20%

-15% 19%

Requirements Analyst Capability

Programmer Capability

Personnel Continuity

Apps Experience

Language and Tools Exp

Platform Exp

Teamwork

Source: “Software Estimation: Demystifying the Black Art” 2006

Training People on the Training People on the Process and the Skills Required to Follow the Process Effectively

The J-Curve Effect of Learning New Skills

The J-Curve Effect

� The advanced beginner has difficulty applying a new skill.

� Reverts to old ways, creating a productivity gap

Expert

Cumulative time

Novice

Advanced Beginner

Competent

Proficient

2mos 6mos 18 mos 2.5+ yrs 5 yrs 10 yrs

Expert

The J-curve effect can occur when an Advanced Beginner struggles in applying new practices.

Avoiding the J-Curve Effect

Two critical components of

successful skill adoption

� Move staff from one stage to the next faster

� Avoid the J-curve effect

These two models can help

� Breadth approach

� Depth approach

The Breadth Approach

� Develop a solid foundation of Best Practice skills

� Refine these skills over time.

Expert

Cumulative time

Novice

Advanced Beginner

Competent

Proficient

Expert

The Depth Approach

� Establish internal mentors who have experience applying their skills within organization-specific projects.

� These mentors will take on a broader role that includes coaching and guiding skills-adoption.

Expert

Novice

Advanced Beginner

Competent

Proficient

Expert

Cumulative time

Defining Your Defining Your Requirements Process

Be sure to include all relevant participants in the

requirements definition process

� Identify all stakeholders up front

� Get them engaged!

Who Should Be Involved?

Systems

Engineers

Subject Matter

Experts

Requirements

EngineersConsultants

Managers

Project

Managers

Engineers

Marketing

Development

Define Your Information Model

Define your requirements

process including:

� Types of requirements

� Relationship between requirements

� Metrics that will be required

� Additional information (attributes) that will help categorize and manage requirements

Visual Representations Establish and Enforce Traceability

Selecting tools that Selecting tools that support your process

Requirements Definition Tools Overview

What to look for in a tool

� Builds upon industry best practices forrequirements definition and management

� Allows you to define your process first

• Can be configured to support your process

• From simple to complex processes

� Visually supports multiple end-to-end processesand methodologies

� Flexible, open platform based on standards

� Single collaborative platform for all stakeholders

� Low total cost of ownership and fast time-to-value

Systems Engineers’ Look at Visure Solutions IRQA

IRQA provides Systems Engineers with:

� Graphical representation of requirements

• Flows down to subsystems and components

• Functional decomposition

� Flexible import/export and roundtrip support

• Word, Excel, DOORS, and other external tools

� Open architecture with an integration platform and plug-in SDK to extend IRQA or automate tasks

• Based on standard programming languages

• Create customized requirements solutions

� Integrated risk management

• Supports FMEA/FMECA, facilitating traceability, impact analysis and reporting on risk elements

Systems Engineers’ Look at Visure Solutions IRQA

IRQA provides Systems Engineers (continued)

� Model-Based Systems Engineering

• Integrates with UML/SysML tools and Matlab/Simulink linking requirements with system and design models

� Requirements-based testing for verification and validation

validation

� Flexible views and traceability

� Product lines and variants support with requirements, use case and test-case reuse

� Web access for collaboration among distributed teams

� Powerful reporting

• Project dashboards and compliance documents

Demonstration of IRQADemonstration of IRQA

What IRQA does best

Enable collaboration

� Visual process structures improveunderstanding

� Web-based access keeps everyoneworking in a single database

� Role-based user groups and workflows

� Role-based user groups and workflowsaid ease-of-use

� Semantic analysis avoids incomplete,unclear or duplicate requirements

� Verification and validation lets everyone knows what will happen and when

� Checking out a single requirement aids team efficiency

� Discussion forums allow continued feedback

What IRQA does best

Support process and methods

� Information metamodel helps you define different types of requirements and their relationships with one another

� Block diagrams graphically capture, communicate and enforce requirements

communicate and enforce requirements processes, their elements and relationships

� Flexible, process-neutral approach allows you to define, control and enforce your requirements processes, across the spectrum from agile to waterfall

� Process focus improves compliance with user requirements, standards and regulations

What IRQA does best

Mitigate risk

� Improve requirements quality with semantic analysis

� Open architecture, integration platform and import/export capability supports requirements exchange and validation

exchange and validation

� Traceability to block diagrams and all external artifacts in a single database improves analysis and understanding of change impact

� Requirements attributes for priority, cost, risk and origin provide weight, so you can focus on the most important requirements first

� Customized workflows and alerts for transitioning requirements keep the project moving forward on schedule

Summary

What we learned

� Requirements definition capability

• Affects total project effort

• Can make or break a project

� Accelerate past the J-Curve

People

� Accelerate past the J-CurveEffect with:

• Breadth and depth training

� The three tiers to success are:

• People

• Process

• Tools

� Engage all relevant stakeholders

ToolsProcess

Summary

What we learned (continued)

� Visure Solutions IRQA’s process-enforcement requirements collaboration platform

• Enforces your process

• Defines your information architecture

• Builds on best practices in the requirements definition and management industry

• Bridges the gap between systems, software, and test engineering in a single tool.

Summary

Address all three areas for project success

Limited time special offer

How we can help

� Best Practices training courses (tool-independent)

• Requirements Best Practices:

Getting It Right Up Front

• Requirements Definition and

Contact Visure at:

Peter Haniak

• Requirements Definition and

Management with Use Cases

• Just $2,500 each

• 15 students max

• On-site (US only)

• Special offer: No additional charge for instructor’s travel and living expenses!

Peter HaniakSales, North America

peter_rtss@visuresolutions.com(514) 944-0154

Limited time special offer

How we can help

� Trade-Up IRQA Test Drive

• For INCOSE members only

• Complimentary consultation to identify evaluation criteria

• 30-day test drive

• Trade-in credit for existing licenses

Peter HaniakSales, North America

peter_rtss@visuresolutions.com(514) 944-0154

Questions?Questions?

Thank youThank you

Incose: People, process, tools webinar - visure solutions - systems engineering

Technology

Transcript of Incose: People, process, tools webinar - visure solutions - systems engineering

P INCOSE oi Pauper Zs

Visure Basics Tutorial - storage.googleapis.com

INCOSE Usability Working Group

CSEP 1 Copyright (c) 2007 by INCOSE, Subject to Restrictions on Slide 2, INCOSE Copyright Notice. INCOSE Certification of Systems Engineers Program Program.

Release Notes...• Visure Requirements integration with HP ALM v4.8 • Visure Requirements integration with Enterprise Architect 4.8 • Visure Requirements integration with Atlassian

Check the Quality of your Requirements ... - Visure Solutions€¦ · Visure Quality Analyzer Natural Language Processing to check the quality of your requirements to automatically

INCOSE 2011 - Tool Vendor Challenge - Visure Solutions

INCOSE eNewsletter / Q1- 2016

Visure Solutions INCOSE Tool Vendor Challenge 2013

LOTTO FONDIARIO - VISURE CATASTALIurbanistica.comune.pescara.it/wp-content/uploads/2020/03/... · 2020-03-13 · LOTTO FONDIARIO - VISURE CATASTALI D-----Direzione Provinciale di

Incose Membership2008

Incose - Sistemas__flotantes_con_placas_de_yeso.pdf

INCOSE Systems Engineering Competency Framework ( ISECF )€¦ · INCOSE BoD tasked CWG 20 In 2014, INCOSE leadership tasked the Competency Working Group ( CWG ) with two objectives:

(INCOSE): the Systems

Incose SE Handbook 2004

27 incose generative_design_9jun2010

Visure Solutions Requirements Definition and Management

Prototyper - Visure Solutions - Requirements Engineering

INCOSE Chicagoland Chapter

INCOSE: TRANSFORMATION