Hardware/software design requirements planning: Part 4 - Computer software approaches
Jeffrey O. Grady, JOG Systems Engineering, Inc.
EETimes (11/10/2011 1:48 PM EST)
It is not possible for a functioning system to exist that is entirely computer software because software requires a machine medium within which to function. Systems that include software will always include hardware, a computing instrument as a minimum, and most often will involve people in some way.
Software is to the machine as our thoughts, ideas, and reasoning are to the gray matter making up our mind. While some people firmly believe in out-of-body experiences for people, few would accept a similar situation for software.
A particular business entity may be responsible for creating only the software element of a system and, to them, what they are developing could be construed a system, but their product can never be an operating reality by itself.
This is part of the difficulty in the development of software; it has no physical reality. It is no wonder then that we might turn to a graphical and symbolic expression as a means to capture its essence.
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 2: Decomposition using structured analysis
- Hardware/software design requirements analysis: Part 1 - Laying the ground work
- How to use UML in your SoC hardware/software design: Part 4
- Dealing with automotive software complexity with virtual prototyping - Part 2: An AUTOSAR use case
New Articles
Most Popular
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)
- Synthesis Methodology & Netlist Qualification
- Streamlining SoC Design with IDS-Integrate™