Functional Architecture
An architecture model is defined as a partial abstraction of a system. This means that it is an approximation covering the different properties and features of the system. It must indicate all the crucial features of the system. Through architecture modeling, the characteristics of the system are identified as well as proper visualization of the information in the model. (Queirós, Silva, A. G., Simões, 2018).The intended behavior of the system is captured through the functional requirements. The expected behavior could be in terms of the task to be handled by the system, the jobs, or the functions at hand. Having a first functional requirement will enhance the uniqueness and improve the ability to meet the intended behavior.
The architecture model is operated within a hierarchy of governance structures. For any architecture model to be successful in terms of architecture governance, it must have gone through some compliance (Kumar, Nori, Natarajan, & Lokku, 2014). One, the architecture model should be consistent. This means that during its implementation, some features must be shared with the specifications and must be implemented according to the specifications. One our case, this was not met, and therefore it needs to be checked in the nest system. Secondly, the model and functional requirements must be compliant. All the features of the system must be implemented according to the functional system. Both the specifications stated at the functional system must be fully met during the implementation process.
To ensure that the same mistakes done during the first time are not repeated in the second time, I would ensure that both the functional system and the architecture model have the necessary elements and the expected produced outcomes (Shaw, & Garlan, 1996). Some of these elements that must be there for anything successful are the architecture principles, the availability of standards to cover all architectures. These standards include data, application, technology, among others. Among the expected outcomes is the compliance assessments.
References
Kumar, A., Nori, K. V., Natarajan, S., & Lokku, D. S. (2014). Value Matrix: From Value to Quality and Architecture. In Economics-Driven Software Architecture (pp. 205-240). Morgan Kaufmann.
Queirós, A., Silva, A. G., Simões, P., Santos, C., Martins, C., da Rocha, N. P., & Rodrigues, M. (2018, June). Smartwalk: personas and scenarios definition and functional requirements. In 2018 2nd International Conference on Technology and Innovation in Sports, Health, and Wellbeing (TISHW) (pp. 1-7). IEEE.
Shaw, M., & Garlan, D. (1996). Software architecture (Vol. 101). Englewood Cliffs: prentice Hall.