Hardware/software design requirements planning - Part 2: Decomposition using structured analysis
Jeffrey O. Grady, JOG Systems Engineering, Inc.
EETimes (11/7/2011 11:41 PM EST)
In this series of articles, Jeffrey O. Grady, author of “System Verification,” delineates the basics of requirements planning and analysis, an important tool for using Agile programming techniques to achieve better code quality and reliability in complex embedded systems software and hardware projects. Part 2: Decomposition using structure analysis Structured decomposition is a technique for decomposing large complex problems into a series of smaller related problems. We seek to do this for the reasons discussed earlier.
We are interested in an organized or systematic approach for doing this because we wish to make sure we solve the right problem and solve it completely. We wish to avoid, late in the development effort, finding that we failed to account for part of the problem that forces us to spend additional time and money to correct and brings into question the validity of our current solution.
E-mail This Article | Printer-Friendly Page |
Related Articles
- Hardware/software design requirements planning: Part 3 - Performance requirements analysis
- Hardware/software design requirements planning: Part 4 - Computer software approaches
- Hardware/software design requirements analysis: Part 1 - Laying the ground work
- Dealing with automotive software complexity with virtual prototyping - Part 2: An AUTOSAR use case
- Optimizing embedded software for power efficiency: Part 2 - Minimizing hardware power