Understanding architectural merging
The recipes in the previous chapter were all about system specifications (requirements). In those recipes, we created specifications in an agile way by using epics, use cases, and user stories as organizing elements. One of the key benefits of that approach is that different engineers can work on different functional aspects independently to construct viable specifications for the different aspects of system. A downside of this is that when it comes to creating an architecture, those efforts must be merged together since the system architecture must support all such specification models.
What to merge
During functional analysis, various system properties are identified. Of these, most should end up in the system architecture, including the following:
- System functions
- System data
- System interfaces
Issues with merging specifications into a single architecture
Merging specifications into an architecture sounds easy, right...
