Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

I am doing research on software development methodologies are commonly used for embedded software development, and how they differ from their non-embedded software development counterparts.

I am having a hard time finding good resources on this topic so if you can recommend me some papers, websites or other material, I will be very grateful.

share|improve this question

migrated from stackoverflow.com Oct 10 '11 at 11:18

This question came from our site for professional and enthusiast programmers.

2 Answers 2

Please check this out may be useful: The Art of Designing Embedded Systems by jack ganssle. http://www.ganssle.com/book.htm

I feel software development methodology is similar but in implementation is different as it has dependencies with Hardware and sometime need calibration( to find tune its functional behavior)

share|improve this answer

I would suggest looking at the work of Stephen J. Mellor. His work on the Shlaer-Mellor method was done at Project Technology (now defunct), but was in the context of work at CERN. Developments of this method were done when he worked at Mentor Graphics, in the context of embedded development and chip design. Much of his work in this context was picked up by Kennedy-Carter in connection with "hard" real time systems. Following links to Kennedy-Carter (mine were well out of date) led me to Advanced Systems which seems to be the successor of that company, and which is providing methods and services in connection with embedded systems.

As part of their development of this method, Kennedy-Carter developed a number of architectures, including at least one simulation architecture, enabling developers to step through the application in a software environment.

I would add that research in this area is handicapped, because the firms, using such methods to develop embedded systems, tend to view their methods as proprietary, and one of the elements that give them a competitive edge. This does mean that public availability of resources can be patchy and difficult to find.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.