PowerAda A Development Model

Chapter 5

• Notice
• Chapter 1. Overview
• Chapter 2. Getting Started
• Chapter 3. Basic PowerAda Concepts
• Chapter 4. The PowerAda Development Environment
• Chapter 5. Project Management with PowerAda
• Chapter 6. The PowerAda Debugger: adbg
• Chapter 7. Interface to Other Languages
• Chapter 8. Implementation Details
• Chapter 9. Optimization
• APPENDIX A - Glossary
• APPENDIX B - Support Packages
• APPENDIX C - Implementation Characteristics
• APPENDIX D - Demos and Tutorials
• APPENDIX E - Tools Reference
• APPENDIX F - Debugger Command Reference
• Index

Contents |  Installation Guide | Release Notes

First | Prev | Next | Last

While powerada provides an excellent interactive interface, there is generally a practical requirement to build everything in an automated fashion for baselining, delivery, and testing. Here is a model that has worked well in practice.

• Identify where PowerAda will be installed and where development will be done.
• Customize PowerAda for your development environment.
• Choose a configuration management (CM) tool, install it, and integrate it with PowerAda.
• Organize existing software and other files into a PowerAda project.
• Create initial configuration files (adalib.imports and adalib.files).
• Install the software and configuration files into your CM system.
• Define an automated build process in which all or part of the software is extracted from the CM system and built into a baseline project using a customized shell script.
• Users develop relative to the baseline that best meets their needs.
• Identify the target environment in which testing and integration will occur (which is initially the same as the development environment.)
• Define the process whereby users can use Aprobe and Adbg to debug and test in the target environment.