S60 Smartphone Quality Assurance: A Guide for Mobile Engineers and Developers

Chapter 12: Integration and Build Environment

S60-based phone integration needs to follow certain predefined steps. If the order is not followed, build creation fails. Such steps are introduced in this chapter. All middle-sized (and larger) software projects tend to set quite strict expectations on both Software Configuration Management (SCM) and build environment. This chapter introduces some general targets concerning configuration management.

12.1 Software Configuration Management

Whenever there is a need to maintain software, there is a need for software configuration management. Software maintenance can be both a long-term activity and a short-term activity. Long term means that a product needs to be reusable without there being major changes needed in the future. Short term means the activities within one product program, i.e. implementing the very first versions of modules and after that making the needed updates to the module in order to increase maturity. Every time a modification is made to a software file, then a check in and check out are needed. A proper software configuration management process contains as a minimum two things:

• rules for changing the code
• rules for the configuration management tool

12.2 Changing the Code

The larger the software under development, the more important it is to have good and reliable control over code changes. Following certain approved rules in the project enables this. Such rules are, for example:

• Keep all source code under version ...