Use of Semantic Web and Web 2.0 techniques could enable domain experts such as engineers to be involved in the modelling of a problem such as product design, and so understand, assess, and develop possible solutions. The article also examines how modelling, ontologies and Semantic Web/Web 2.0 technology can aid in collaborative management of complex systems such as those involved in process modelling and product design. Visualisation of the most useful representation of the collaborative knowledge and models, and translation between the human and computing representation of this is important for this collaborative modelling.
Visualisation is necessary to provide traceability for decision making, as an audit trail for information, to justify a decision and/or cost, or to understand a process, or a product data structure. It is necessary to navigate a database in order to validate it, the structure of the visual interface needs to show the structure of the data, and the model. The best way to do this is to relate them all so that any change to the database, changes the structure of the model and this changes the structure of the visualisation, or vice versa. Semantic search allows someone to see results or individual items but enables going straight to these items, that does not show the context and the model is still a 'black box', unless the Semantic search actually returns the relevant portion of the structure so that the context of the returned information is displayed.
For each organisation type, a process architecture(s) can be identified that offers potential for reuse by other organisations of the same type. This can enable a better connection between process designers and modelling tools and a shared understanding between domain experts and model developers. A shared understanding and reuse of process architectures can enable improved decision making and performance especially for complex systems, indeed, complexity is a core problem found in most organisational activities. Problems with incompatible software and team communication cause inability to meet delivery deadlines and to control costs, poor product/service quality, delays and cancelled orders, resulting in lack of competitiveness and, ultimately, job losses. So shared understanding of processes between all involved within organisations is essential.
A User Driven Modelling/Programming (UDM/P) collaborative approach and its application to systems/process modelling research needs to be developed. This could enable taxonomic and diagrammatic visualisation and calculation of sequences, times, and costs for complex processes. Provision of a process repository of reusable process architectures could assist industry and organisations to develop more effective service and production processes.
Examples of difficulties in modelling complex processes/projects include:
Lack of interoperable tools that are usable by domain experts with limited programming knowledge.
Lack of tools for process modelling and web service discovery and lack of online search facilities is hindering development and reuse of process models.
Overuse of non integrated spreadsheets and poor links between these and 'high end' tools, such as specialist process modelling tools and CAD. This hampers the scope for modellers to investigate problems systematically and communicate solutions between users of the various tools.
Poor human/computer translation that fails to convey the model present in human minds to computer models. A systematic approach of layered abstraction combined with sophisticated structuring and translation is required for successful modelling.
Because of the lack of automated human computer translation, modellers currently need to request the help of professional developers such as provided by an IT department, this can slow model creation and embed misunderstandings.
Almost all organisations use spreadsheets to manage information and calculations. However, it is often difficult to follow the relationships between items of information, leading to confusion, and incorrect conclusions. Spreadsheets are often produced by individuals who have had little formal training and there may be inaccurate and undocumented models produced that lack visibility of structure and relationships. Spreadsheets are popular because models can be created without writing code. with aerospace, ideas discussed in this paper are built partly from that Rolls-Royce aerospace DATUM project. Thus we will develop structured visual process modelling tool(s) that can be used without code writing (though they will produce code that can be edited if required).
Collaborative modelling to determine requirements was investigated. Alternatives to current software development approaches are necessary. The need is to translate from a model-based visual representation understood by users to software. Successful interaction requires mapping between levels of abstraction, and translation between these levels required by people and computers is difficult. He explains that this problem means systems are created that make people cope with the problems of mis-translation. Rules and information can be illustrated diagrammatically. It is possible to describe algorithms through concrete examples rather than abstractly. Models must be designed and visualised to convey to users a representation of problems that assists with their vision of them. This subject is basis of the development and visualisation techniques evaluated in this paper. These techniques enable users to create and understand models, which are translated into software representations.