White Paper: Optimizing the development process: Merging model-driven development and requirements-driven development processes

While linking development to requirements is an intuitive notion, when put into practice, managing the complexities of changing project requirements can present significant challenges. Ineffective requirements management can create inconsistencies that remain undiscovered until the final phase of development, which is when the code is most difficult and most expensive to fix. In the “rush to code,” development teams often lose sight of the fact that mapping projects to requirements is the best way to guarantee project success–delivering code on time that meets customer expectation–with the ability to effectively manage the inevitable requirements changes customers request as the project moves forward.

May 12th, 2011
White Paper: Optimizing the development process: Merging model-driven development and requirements-driven development processes

Full Text: Download PDF

Version: 1
Date File Uploaded: 2011-05-12
1An increasingly competitive marketplace encourages a "rush to develop," which makes it difficult to adjust to changing client requirements.

Today’s embedded and real time systems and software development market is not just increasingly competitive, but project complexity and client expectations have expanded exponentially as well. With the pressure to be first to market, and the cost of time-to-market delays often measurable by hundreds of thousands of dollars, it comes as no surprise that managers are looking for a solution that can help manage the diverse pressures of meeting productivity goals while simultaneously assuring that deliverables meet customer requirements.

While linking development to requirements is an intuitive notion, when put into practice, managing the complexities of changing project requirements can present significant challenges. Ineffective requirements management can lead to poor communication between customers, project managers and developers, creating inconsistencies that remain undiscovered until the final phase of development, which is when the code is most difficult and most expensive to fix. In the "rush to code,"

Topics covered in this article

White Paper: Optimizing the development process: Merging model-driven development and requirements-driven development processes

Full Text: Download PDF

Version: 1
Date File Uploaded: 2011-05-12
Silicon, software, and strategies for embedded devices
Embedded Computing Design magazine is the resource for engineers, architects, and decision makers involved with embedded devices. Topics explored span silicon, software, and strategies for designing and connecting with small devices in mobile, automotive, home, industrial, and medical applications. Departments include Deep Green discussing the latest in energy efficient, low power designs and applications. Content is available in print, E-letter, E-cast, white papers, video, RSS, social networks, and more. Subscriptions are free of charge.
©MMXIIEmbedded Computing Design.
An OpenSystems Media publication.