Document-based vs. Model-based Engineering In principle, there are two fundamentally different ways of working with systems and information: model-based engineering (MBE 1 ) and document-based engineering (DBE 2 ). Both methods have their advantages and disadvantages. DBE is well known and established within LKAB but is best suited for smaller systems and organizations. MBE is suited for handling complexity and enables a more comprehensive systems analysis. This is critical for meeting the everchanging challenges in a changing world that rapidly moves toward intense digitalization. New skills, new organization and new mindsets are necessary in facing this endeavor. The application of traditional document-based engineering for the development and maintenance of complex systems can result in tens of thousands of documents being generated during a system’s lifecycle. These documents must be stored, structured, maintained and communicated to the right people for a seamless operation. Changes to one document may require manual work to update subsequent documentation. This process is not only tedious but is also susceptible to errors and faults. Furthermore, inadequate documentation may eventually lead to serious damage, failure, or extensive extra work to recreate information. Model-based engineering allows for the harmonization of a broad scope of information from different fields. Changes in data or models are automatically propagated to all relevant systems and their users; therefore, information will be consistent and updated. Models will also identify any shortcomings, enabling traceability and analysis of the modeled system.
Goals with Model-based Engineering
1 MBE’s Swedish terminology within LKAB is modellbaserat arbetssätt 2 DBE’s Swedish terminology within LKAB is dokumentbaserat arbetssätt
4
Made with FlippingBook Ebook Creator