On the program to develop the replacement for the Marine One helicopter, costs have mushroomed to $11.2 billion from $6.1 billion. The Defense Science Board issued a new study blaming “poor communication” about aircraft requirements between the government and contractors. Without effective requirements engineering practices that keep all your engineering teams (systems, software, electrical/electronic, mechanical), product stakeholders (marketing, legal, finance, safety/quality assurance, manufacturing) and your partners/suppliers on the same page, you run the risk of experiencing quality issues late in design and development, or worse, product recalls. This presentation will cover how effective practices, supported by IBM’s requirements engineering solution, can:

• Break-down silos by providing common visibility of requirements
• Trace requirements through the product development lifecycle to ensure quality, conformance and compliance
• Mitigate the risks of scope creep by effective change management
• Make management of requirements for similar products simpler