RM Webcasts
Stay up to date on a variety of upcoming live events from the leading industry thinkers. Don't forget to browse the archives of on-demand events and presentations.
 Subscribe as a reader
|
 |
|
|
Featuring author and testing expert Robin Goldsmith
Testing based on requirements is a fundamental method for confirming that products and systems work appropriately. Effectively managing requirements, especially tracing them to the tests that confirm them, is essential. However, the thoroughness of test coverage is often compromised by requirements-based testing traps that are unapparent to testers, analysts, and managers.
In this Web seminar, Robin Goldsmith, a respected authority on software testing practices and author of Discovering REAL Business Requirements for Software Project Success will identify key sources of requirements-based testing oversights.
|
|
|
Featuring Gary Mogyorodi, President, Canadian Software Testing Board
In many organizations, testing is viewed as slowing down the delivery of the system, partly because it is the last step in the development process. This presentation aims to contradict this notion and explains how a RBT process can improve overall project delivery timelines and software quality. In this Webcast, testing expert Gary Mogyorodi discusses:
- The importance of testable requirements.
- The 12-point Requirements-Based Testing process.
- The Ambiguity Review process.
- Cause-Effect Graphing, a rigorous approach to testing, contrasting and comparing it to other testing techniques used in industry.
- How to use quantitative completion criteria for organizing a testing effort.
- The important issues in implementing the quality program and the organization required to support it.
|
|
Date: Thursday, October 30, 2008
Time: 12:00 PM (EDT)
Software development organizations today are looking for new ways to
create efficiencies and discover new ideas as they attempt to stay
ahead of the competition. The ability to reuse work frees resources to
make early, innovative improvements and implement them quickly.
Reuse has traditionally been a concept reserved for code and
software components largely because code is often the first
consistently recognisable element of knowledge. However, organizations
who can recognise other existing elements of knowledge - like
requirements - can reap the benefits of reuse early in the development
lifecycle. This realization identifies a need to be able to make
requirements knowledge consistent and hence reusable.
Join Suzanne Robertson, originator of the Volere requirements
techniques and a founder of The Atlantic Systems Guild, for a lesson in
how a well-defined requirements knowledge structure is key to
implementing a requirements reuse strategy. Suzanne will outline a
structure for building traceable connections between high-level
business or domain requirements, atomic requirements and all the levels
in between like systems analysis models/deliverables, design
models/components, code and testing, thus laying the foundation for
reuse. The resulting requirements knowledge model is a framework that
you can use to manage requirements knowledge regardless of modelling
notation, methodology, degree of agility, or tool usage.
|
|
Date: October 22, 2008
Time: 2:00 PM to 3:00 PM (EDT)
In some of today's hotly competitive markets, such as telecommunications and
automotive, a company's ability to deliver the next generation of its product
ahead of the competition can mean significant gains in market share and market
position. Engineering organizations must continually strive to shorten
development cycles while maintaining a high level of software quality. In this
environment, the ability to reuse software requirements across projects can
provide a significant advantage.
|
Paul Conte
[ View on-demand ]
How often do you hear stories with the theme "We gave them just what they asked for, how were we to know it wasn't what they wanted?" Stories like this keep coming up because it's truly difficult to effectively manage changing requirements over the course of time that it takes to deliver great software. How do we bridge this disconnect between the end users and development - essentially, how do we communicate in real-time, and keep the lines of communication open throughout the software lifecycle?
Join industry expert Paul Conte for a deeper look at the requirements challenge. He'll discuss best practices around the creation and management of requirements, and talk about the importance of integrating requirements into your application lifecycle management process. By improving collaboration capabilities and managing requirements throughout the lifecycle we can overcome frustrations like rework, and ultimately give our users the applications they want, when they want them.
|
|
It is well
documented that no, or poorly written requirements are a significant cause of
project failures. As a result, many organizations are implementing more formal
requirements management practices. This introduces an opportunity for the QA
organization to update their processes and improve application quality.
In this
Webcast Brad Van Horne, Product Manager for MKS, discusses how to implement an
automated requirements based
testing methodology. He reviews:
1. How to
ensure that all of the project's requirements have complete test planning and
test execution coverage.
2. How to create, and then manage, the resolution
of defects found during testing.
3. How to measure project readiness through
live management dashboards.
4. The benefits of a single repository for
managing requirements, test cases and defects.
Watch this
Webcast and learn how requirements based testing will ensure the projects you
deliver are guaranteed to meet the needs of the
business.
[ View On-demand ]
|
Industry experts in
software risk mitigation note that 80 percent of software projects are at risk
due to creeping requirements. Therefore managing changing requirements and
scope creep must be an integral part of your development process. However, most
current market solutions are decoupled from the development process. You need a
solution that fosters collaboration between people in the business generating
requirements and the software developers building the end-product.
Join us for a look at MKS
Integrity for Requirements Management, built as part
of MKS’s end to end application lifecycle management platform. MKS Integrity
enables traceability, change, and configuration management of requirements
through every stage of the software development process and is distinctive in
its support for requirements reuse. No other requirements management vendor
offers the same level of lifecycle integration or traceability, and none
provide MKS’s sophisticated requirements reuse capabilities. See how MKS can
help you advance your requirements management practice for greater efficiency
and traceability and ultimately help you better meet the needs of the business.
[ View On-demand ]
|
Doug Akers - Tactical and Solutions Product Manager, MKS Inc.
Karl E. Wiegers - Consultant, Process Impact, and Author of "Software Requirements, 2nd Edition"
[ View On-demand ]
Originally broadcast live from the Hilton Parsippany
in New Jersey
on February 14, 2006, this is a 3-hour recorded session of an onsite seminar.
Are you concerned about the impact of less than optimal
requirements processes? Many businesses are realizing that poor requirements
processes and disjointed communication between the business and IT are key
contributors to their IT project failures and delays.
Join software requirements expert and author Karl Wiegers
for his talk on “Software Requirements: An Executive Overview.” Karl looks at
the business value of investing in better requirements and shows the benefits
of selected requirements practices. Karl is joined by Dan Hagee from Anexinet,
who will present a real life success story on how his organization refined its
requirements processes to dramatically improve project delivery times and
overall customer satisfaction. Then, Doug Akers
of MKS shares an innovative approach to managing software requirements - one
that allows all stakeholders to collaborate in the requirements process and
gain greater auditability, visibility and control over IT projects.
|
|
Karl E. Wiegers - Consultant, Process Impact, and Author of "Software Requirements, 2nd Edition"
[ View On-demand ]
Successful software projects are built on a foundation of
well-understood requirements. However, many development organizations get
caught in traps that prevent them from effectively collecting, documenting, or
managing their requirements. This presentation describes ten typical
requirements problems that can sabotage your project. Several symptoms that
indicate you might be getting caught in each trap are described, along with
suggestions for avoiding or escaping from the trap.
The requirements traps discussed are:
- Confusion
about what a requirement is
- Inadequate
customer involvement
- Vague
and ambiguous requirements
- Unprioritized
requirements
- Building
functionality no one uses
- Analysis
paralysis
- Scope
creep
- Insufficient
change impact analysis
- Inadequate
requirements version control
|
|
|
|
|
<< Start < Prev 1 2 Next > End >>
|
|
Page 1 of 2 |
Webcasts
