The counting scope is determined by the purpose of the count. It identifies the systems, applications, or subsets of an application that will be sized. The application boundary identifies the border between the application being measured and both external applications and users. The user should be able to define the scope of the application and the business functionality in the user's language. The boundary between related applications is based on separate business functionality rather than on technical considerations.
Several examples are appropriate.
The initial boundary already established for an application is not influenced by the counting scope. The application boundary for an application being enhanced remains as it was except, of course, that added functionality may expand the boundary, and deleted functionality may reduce the boundary. An enhancement does not become its own application boundary, but it is defined by the counting scope. Development projects and enhancement projects often include more than a single application. In these cases, the multiple application boundaries are identified within the counting scope, but they are counted separately.