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.
To read the full article, click here
Related Semiconductor IP
- 1.8V/3.3V I/O library with ODIO and 5V HPD in TSMC 16nm
- 1.8V/3.3V I/O Library with ODIO and 5V HPD in TSMC 12nm
- 1.8V to 5V GPIO, 1.8V to 5V Analog in TSMC 180nm BCD
- 1.8V/3.3V GPIO Library with HDMI, Aanlog & LVDS Cells in TSMC 22nm
- Specialed 20V Analog I/O in TSMC 55nm
Related White Papers
- Why Embedded Software Development Still Matters: Optimizing a Computer Vision Application on the ARM Cortex A8
- Platform Software Verification Approaches For Safety Critical Systems
- Managing the complexity of embedded software development through design automation tools
- Design patterns in SystemVerilog OOP for UVM verification