There are many benefits that the MxSuite can bring to your software development process, resulting in significant savings of both time and money. Here are ten process improvement steps to consider:
1.Have some of your developers focus on the Application Layer, and some on the Device Drivers. MxVDev allows the application developers to develop and test an application long before there is any available hardware. Their need for emulators is postponed until much later in the project.
2.During High Level Design, focus on partitioning your system and defining the interfaces and layers. A well-partitioned system is much easier to test. MxVDev works best in a system with a strongly-defined architecture.
3.Don't allow hardware availability and reliability to slow your developers. Put MxVDev on their desks early in the project. They will have much more confidence in their code when the hardware is ready.
4.Use generic PC tools when possible. Tools designed for PC development are much less expensive than tools designed for a specific embedded environment. In general, they are much more reliable, too! Measuring TestCase code coverage is easy and inexpensive if you do it only on the PC. Don't blow your whole budget on expensive emulators!
5.Plan for TestCase re-use. You get very little re-use payback from unit-level tests which test small units (such as single functions) in isolation. When you make a small change to one function, the test for that function needs to change, and the tests for the rest of the system will likely all pass. Re-executing unit test cases on small units has little benefit - don't bother automating them!
6.System level tests are the tests that you will re-use time and again during regression testing. This is where you should focus your automation. Re-use and automation have to target System Level Tests. MxVDev allows you to start building system test cases very early in the development cycle and re-use and enhance these test cases during software development, unit testing, integration testing and system testing. At the end of the development cycle, the MxVDev test cases can be used to drive your National Instruments™ test equipment.
7.MxVDev lets you partition your development effort, and get remote developers up and running quickly. There are no emulators, hardware, or other equipment to ship. With MxVDev on the developers' desks, you can send everything they need via e-mail.
8.Use Static Analysis tools to improve your source code quality and enforce your coding standards. They will also help you improve portability, which is important when developing on a PC.
9.Don't get bogged down using scripting languages to develop test cases. They are slow to write and debug, and difficult to understand when maintenance is required. MxVDev allows you to build your test cases graphically. It is as easy as drawing a timing diagram! MxVDev also helps you build more complete, comprehensive and complex cases.
10.Use two approaches to measuring TestCase completeness - requirements coverage and code coverage. MxVDev allows you to put traceability information back into the requirements and facilitates the use of inexpensive, PC-based code coverage tools.