The report describes in details the functional and technical requirements of the components that comprise the MOEEBIUS system architecture. More specifically, it defines the distinct technological components that needs to be included in the MOEEBIUS framework, in order to address the needs of end-users as well as the constraints set by the identified business models and the energy performance assessment methodology.
Initially, the report describes the methodology towards the definition of the detailed modules of the MOEEBIUS system, taking into account the end users and business requirements definition.
Moreover, the decument analyzes the static and dynamic components of the MOEEBIUS system. More specifically, the core components of the system are identified (static view) and then the interactions among them are specified (dynamic view).
As the report pays close attention to the key elements (functional modules and components) of the MOEEBIUS system, the definition of functional and non-functional requirements is also provided. The project system requirements are divided in the two following categories:
- The section about functional requirements contains the operations and activities that the MOEEBIUS framework must be able to perform. These requirements are mapped to the different functional components of the MOEEBIUS system,
- The non-functional requirements section includes on the one hand the description of pilot building requirements and on the other hand the definition of the qualities, attributes and restrictions that the MOEEBIUS solution must meet.
By defining the MOEEBIUS components along with the list of functional and nonfunctional requirements, the project consortium is activating the work for the definition of the MOEEBIUS reference architecture. The different functional components identified in this document will be extensively described in the “MOEEBIUS Architectural Design and Technological/Functional Specifications - Communication interfaces and protocols definition” report as a part of the overall MOEEBIUS framework, while the list of system requirements will allow the project consortium to define MOEEBIUS system specifications. Thus, this document can be considered as a living document acting as the guideline for the development of the respective component that set the MOEEBIUS platform. Therefore, it will remain an open issue ‘till all components and subsystems are built and all modules are integrated to the MOEEBIUS platform.
Read the latest project report to find out more about the functional and technical requirements of the components that comprise the MOEEBIUS system architecture. Download the report >>>