Applying mental models to making controlled critically safe decisions in IT project management (original) (raw)
Related papers
The Use of Case Tools for Modeling as a Support for Information System Design
2012
Analysis, definition and business processes modeling are all realized by the top-to -down method, starting from the precise setting of the business process goals and resources, which are used to define necessary elements for the information system designing. Models of business processes enable the clear, precise and unambiguous definition of business processes for which the CASE tools are used. The paper deals with the use of CASE tools for modeling of Mcirosoft Viso, BPwin RationalRouse with an example of a sales process. The result of this work involves defining sales activities with appropriate diagrams and the pre-established sequence of steps in the processes that are the basis for the
The paper discusses how a story-telling theory and a related visual tool can support communication between users and analyst in developing an effective information systems design. To this end the paper firstly surveys approaches to requirements engineering from the communication point of view, then introduces a multimedia-based template as a tool to facilitate the construction of a shared mental model of the system between user and designer, and finally illustrates a case study and outlines some possible extensions of the proposed approach. Two main approaches are used for Information System (IS) design: structured system design (SSD, [l]) and object oriented design (OOD,[2]). Both the approaches make use of expressive graphical notations (e.g., data flow diagrams and entity relation diagrams in SSD, object model and interaction model in OOD). Formal notations allow the designer to describe a scenario or formulate an architecture unambiguously and support checking the system's consistency and correctness [2]. Although the above notations effectively support communication among IS professionals, they prove limited in the communication between analyst and user, especially in the process of requirements validation when the IS specification is investigated to ensure that it reflects the user needs and statements [3]. It is in fact difficult for the user to interpret and check requirements expressed in unfamiliar language and formalisms [4]. Another communication problem is that while some of the user's expectations are explicitly formulated as systems goals and requirements, most expectations remain unexpressed, held within a "mental model" of the system developed by the user during the requirements definition process [4]. The user's mental model includes expected functionality, performance, appearance, fit with business processes, and other
How do practitioners use conceptual modeling in practice?
Data & Knowledge Engineering, 2006
Much research has been devoted over the years to investigating and advancing the techniques and tools used by analysts when they model. As opposed to what academics, software providers and their resellers promote as should be happening, the aim of this research was to determine whether practitioners still embraced conceptual modeling seriously. In addition, what are the most popular techniques and tools used for conceptual modeling? What are the major purposes for which conceptual modeling is used? The study found that the top six most frequently used modeling techniques and methods were ER diagramming, data flow diagramming, systems flowcharting, workflow modeling, UML, and structured charts. Modeling technique use was found to decrease significantly from smaller to medium-sized organizations, but then to increase significantly in larger organizations (proxying for large, complex projects). Technique use was also found to significantly follow an inverted U-shaped curve, contrary to some prior explanations. Additionally, an important contribution of this study was the identification of the factors that uniquely influence the decision of analysts to continue to use modeling, viz., communication (using diagrams) to/from stakeholders, internal knowledge (lack of) of techniques, user expectations management, understanding modelsÕ integration into the business, and tool/software deficiencies. The highest ranked purposes for which modeling was undertaken were database design and management, business process documentation, business process improvement, and software development.
An Experimental Comparison of Use Case Models Understanding by Novice and High Knowledge Users
Proceedings of the 2010 conference on New Trends in …, 2010
Use cases were introduced into the Unified Modeling Language to capture the functional requirements in object oriented systems development. This work reports the results of comparing two controlled experiments conducted on use case models with different subjects, in which the effect of use case format on users understanding of systems requirements is assessed. Replication with subjects of different knowledge in use case technique allowed us to investigate whether subjects experience play any role in the comprehension of use case models. The results of the controlled experiments showed that for the comprehension tasks, which required only surface understanding of the Use Case model, the provision of diagrams along with the textual use case descriptions significantly improved comprehension performance of both novice and high knowledge users. However, diagrams had no effect on users performance in the deep understanding tasks. Moreover, there was no evidence that prior experience with use cases has influenced subject's performance in surface and deep understanding tasks in familiar and unfamiliar application domains.
IJCSIS Vol 17 No 9, September Issue, 2019
Use cases as textual visual modeling techniques have become a key construct and the foundation of the most popular de facto standard technique for performing software requirements analysis and specification. This paper describes use cases in terms of a recently proposed model: the thinging machine (TM) model. Such a link to TM strengthens the notion of use cases and clarifies related concepts. For example, the concept of events is utilized in an unconstrained way in use cases, and TM may contribute in this direction. Several selected use cases are remodeled using TM. This study provides many insights. For example, one result shows that use cases are an activation apparatus of "mega-triggering" (high-level events) wherein a group of submachines (processes) are actuated.
European Modern Studies Journal , 2024
This research endeavors to investigate the process of eliciting data flow by employing both data flow diagrams and user case diagrams. Through an in-depth analysis of existing literature and comprehensive comparisons between these two diagrammatic representations, the study concludes that the most effective approach for systems analysts involves the concurrent utilization of both types of diagrams. These two diagrams will enhance the understanding of data flow dynamics within the system, encompassing the data flow between system functions and the seamless flow of data among those engaged with the system. By leveraging the strengths of both data flow diagrams and use case diagrams, analysts can achieve a more holistic and nuanced comprehension of the intricate data flow relationships inherent in complex systems.
Modelling risks in IS/IT projects through causal and cognitive mapping
The electronic journal of …, 2005
Due to the rapid introduction of new technology and the increasing complexity of the marketplace, Software systems development and implementation has become progressively more difficult. This paper proposes an evaluation framework for identifying the causes of shortfalls in implemented information system projects. This framework has been developed during a longitudinal case study of a problematic project, which is described.
2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings., 2003
Several processes have been proposed for the transition from functional requirements to an object-oriented design, but these processes have been subject to little empirical validation. A use case driven development process is often recommended when applying UML. Nevertheless, it has been reported that this process leads to problems, such as the developers missing some requirements and mistaking requirements for design. This paper describes a controlled experiment, with 53 students as subjects, conducted to investigate two alternative processes for applying a use case model in an objectoriented design process. One process was use case driven, while the other was a responsibility-driven process in which the use case model was applied as a means of validating the resulting class diagram. Half of the subjects used the modelling tool Tau UML Suite from Telelogic; the other half used pen and paper. The results show that the validation process led to class diagrams implementing more of the requirements. The use case driven process did, however, result in class diagrams with a better structure. The results also show that those who used the modelling tool spent more time on constructing class diagrams than did those who used pen and paper. We experienced that it requires much more effort to organize an experiment with a professional modelling tool than with only pen and paper.
A model formulation system for information system project selection
Computers & Operations Research, 1993
Scope and Purpose-Operations research scientists have had to teach students how to formulate mathematical programming models before they could apply them in specific domains of knowledge. Computer based technologies, like decision support systems (DSS), have been finding ways to bring the mathematical programming methodologies to users who may not be skilled in model formulation. The development of DSS based on mathematical programming algorithms, usually does not take advantage of general purpose problem solving capacities of their embedded methodologies. Many users find it difhcuit to develop unique mathematical programming constraints in their models even though they are occasionally required in an actual problem fo~uiation. Often these DSS are limited to a specific decision application within a specific business organization. New model management systems (MMS) are starting to emerge in the literature that are not organization specific and take advantage of more of the general purpose capabilities of mathematical programming models without the user being knowledgeable about it's methodology. In this paper, we present the development of a microcomputer-based model formulation system on linear goal programming for use in decision support in information system project selection.