# Residential Buildings Complex Boundaries Generation Based on Spatial Grid System
## 3 Overview
In our case, it is essential to support the extendibility of applied strategy (Inner-Bounded, Outer-Bounded, or even the combination of them), method (the collections of rules), and algorithm (rule-based limited set of steps needed to reach an arbitrary problem solution). The initial conceptual framework model, in the form of an object-oriented diagram, is presented in Figure 2.  
The Framework is a concept to which the interoperability concerns are allocated. It delegates the extendible point handling to StrategyManager, AlgorithmManager, and RulesManager components with the extending points: Strategy Interface, Algorithm Interface, and ElementaryRule fabric respectively (see Figure 2). The explicit dependency between each ConcreteAlgorithm and corresponding ConcreteRulesCollection has to be maintained in order to enable the analysis of algorithm-rules correlation (see Figure 2). Figure 2: The initial framework conceptual model. The other essential point of framework specification is the way of preserving concrete products (generated set of building boundaries) joined with a particular instance of Strategy, Algorithm, and Parameter combination data. The initial conceptual framework model from the persistency aspect is presented in Figure 3 in the form of an object-oriented diagram. The role of the Framework concept is the same. The Persistency interface concept enables the extendibility of wide variety of persistent forms and structure handlers used to store a large volume of data usually created in the particular processing. It isolates the persistent layer from its dynamic management. The Framework delegates the internal data structure concerns to the FrameworkInstance-Model concept. It is loaded and saved through the Persistency interface methods implementation. The Framework delegates the visualizations concerns of internal data structure to the FrameworkInstanceView concept and data structure transformation actions concerns to the FrameworkInstanceControler concept. The role of GetModel, SetModel, and NotifyView interfaces is to relax dependences of FrameworkInstanceModel, FrameworkInstanceView, and FrameworkInstanceControler concepts. The method used in the proposed solution receives the area of a building as an input in the form of two-dimensional grid representation (particularly 1 \(\times\) 1 m cells) and varies available algorithms in order to, if possible, generate corresponding building boundaries that satisfy initial constraints (lot and building size) preserving the grid cells interconnection principle. This approach is chosen to initially simplify the overall shape thereby generating particular solutions that:  
* can be, for verification purposes, easily compared with other methods  
Figure 3: The initial framework conceptual model—persistency aspect. * are suitable for further enhancements and development in the domain of building's layout design. Boundary shape can be either rudimentary with a small number of variations, or quite complex just as is the case in the real examples examination. The primary focus of the proposed method is the focus on complex building boundaries. As the boundary complexity directly influences algorithm complexity and the time for analytical calculation, the method is exercised through the application of different spatial grid transformation algorithms, described in the algorithm section of the article. These variations had a direct impact on criteria that restricts the number of lines composing the particular floor plan. This calculated number is used as a metric for comparative analysis and the evaluation of the proposed method with regards to other published solutions. The resolution of 1 m of the final image was chosen because in related work research smaller cells of the system caused the generation of buildings that are too complex compared to real buildings and larger cells composed results that are simple and similar to related work findings.