/24-7PressRelease/ - NEW YORK, NY, March 29, 2007 - Its quite a complicated matter to assess the effects of diverse aspects of embedded software projects project in cutting the entire investment of time and staff during the project. Therefore, its almost impossible to exactly respond the question "How to save 30 per cent of efforts for embedded software development?" Still, in this survey we will introduce a number of aspects of embedded software development project which en bulk may substantially decrease its development effort by approximately 10 to 50 per cent.
Decrease the amount of Software to be developed. Its a generic approach to decrease software development effort - to develop only the needed amount of software components. First of all, avoid "requirements creep" as it tends to add increasingly more must-have functionalities to embedded software in the course of development, leading to excessive expenses, even more than was originally planned.
Another way to develop the least software, is to purchase "off-the-shelf" products for some components of embedded software system, instead of writing all the software from the ground up. Whereas the repeated utilization of existing software does not cut development efforts to zero, it is indeed more effective than writing new code with features similar to what others have already developed, debugged and field-tested.
Accelerating the Learning Curve for an RTOS
As the decision is made to use an RTOS, a development team must learn the RTOS and the way it works. It5s one of the causes that re-use of conventional software like RTOS is not infinitely efficient. For a usual up to date RTOS, it may take several months before software engineers master the RTOS.
This all is because of the vast number of operating system abstractions and options to learn, and the trade-offs among them. For example, lots of RTOSs have a diversity of inter-task communication and synchronization procedures including message queues, pipes, event flags etc. A software engineer must learn and understand all these aspects, compare its strong and weal suits, before he learns to use RTOS optimally. So, the lasting learning is conditioned by the variety of choices. However, the learning time can be substantially reduced by avoiding some of these abstractions and options from consideration in the embedded software design. This can be attained by ruling out some RTOS features from consideration, or through selecting an RTOS with a simpler, easier-to-understand set of features.
Circa 90 to 95 per cent of all RTOS service requests will be restricted to several services, thus resulting in a simple and easy-to-learn API to the RTOS.
Embedded software development library.
---
Press release service and press release distribution provided by http://www.24-7pressrelease.com# # #
