Allocating Software Space Plan and Software Stuff
The Software Space Plan is the detailed development of components, using the Software Stuff as the local data structures of each one of the components. Up to this point, architecture has been shaped primarily by the change cases. The user required behaviour has not been accounted for in any very explicit way. In the previous section, it was assumed that there was no detailed behaviour available, but several considerations could be taken. Here, that we should make that behaviour available. We should have a complete set of specifications which, when taken together, provide all of the behaviour and information required by users.The form of those specifications should be either collaboration responsibility specifications or interface views. Design patterns and Idioms can be helpful here for implementation of tasks at component internal level.The main task here is to merge the architecture and behaviour to produce a system that successfully addresses both the user and development-sponsor requirements. The process requires a set of behaviour allocation decisions. Inputs are a list of behaviours observed in use cases, and the architecture components defined. The results of allocation decisions may be shown in two formats: each behaviour analysis may be followed by the names of the architecture components to which they are allocated; or architecture components may be followed by the behaviour analysis it contains.
Jorge Luis Ortega Arjona.