No matter the technical capabilities of a framework, without trust users will look elsewhere. Ultimately, the decision to utilize a framework comes down to whether or not you trust the code in the framework and those developing it to be able to support your desired use-case. Onerous dependency issues, complicated, hard to follow instructions or build failure can all result in a user passing on the platform. For instance, the build system is the first thing potential framework users come into contact with when they download a new software framework. Rapid, continuous integration development cycleĮach of these characteristics is meant to build trust in the framework by those attempting to use it. Integrated, automatic, and rigorous testing Straightforward APIs providing sensible default information The pursuit of this goal has led to many of the unique features of MOOSE:
At every turn, decisions were made to enable this class of users to be successful with the framework. Every single aspect of MOOSE was driven by this singular principle from the build system to the API to the software development cycle. MOOSE is meant to be approachable by non-computational scientists who have systems of PDEs they need to solve. MOOSE was conceived with one major objective: to be as easy and straightforward to use by scientists and engineers as possible. The Multiphysics Object Oriented Simulation Environment (MOOSE), mission is just that: provide a framework for engineers and scientists to build state-of-the-art, computationally scalable finite element based simulation tools. The main object of creating a framework is to provide an interface to application developers that saves time and provides advanced capabilities not attainable otherwise. Framework System Design Description Introductionįrameworks are a software development construct aiming to simplify the creation of specific classes of applications through abstraction of low-level details.
0 kommentar(er)
