Data Modeling and Functional Modeling–Which Comes First?

2011

One of the most important phases of information sys tem development include data modelling processes, where conceptual data modelling presents an essenci al part. There are many approaches and methods formally based or those that give heuristics as gui delines. This paper aims to present integration of models for conceptual data modelling. Special emphasize is giv en to comparison of methods and integration of data modelling process with other processess in informat ion system development.

The Computer Journal, 1988

In 'Towards a tool kit for the systems analyst', Benyon and Skidmore discuss various approaches to systems analysis and include a comparison of De Marco's data flow diagrams and Checkland's conceptual models. This note compares the two in greater detail and concludes that the underlying methodologies are much further apart than Benyon and Skidmore suggest.

Communications of the AIS

The software analysis process consists of two main activities: data modeling and functional modeling. While traditional development methodologies usually emphasize functional modeling via dataflow diagrams (DFDs), object-oriented (OO) methodologies emphasize data modeling via class diagrams. UML includes techniques for both data and functional modeling which are used in different methodologies in different ways and orders. This article is concerned with the ordering of modeling activities in the analysis stage. The main issue we address is whether it is better to create a functional model first and then a data model, or vice versa. We conduct a comparative experiment in which the two opposing orders are examined. We use the FOOM methodology as a platform for the experiment as it enables the creation of both a data model (a class diagram) and a functional model (hierarchical OO-DFDs), which are synchronized. The results of the experiment show that an analysis process that begins with data modeling provides better specifications than one that begins with functional modeling.

Most of information systems use nowadays were modeled and documented using structured approach. Expansion of these systems in terms of functionality and maintainability requires shift towards object-oriented documentation and design, which has been widely accepted by the business. In this paper, we compared between Data flow diagram and Use case diagram to find out the strengths and weakness over each of them. As a result, the author concluded that DFD still powerful tool through system analysis and design process, and can be included in object-oriented approach. Index Terms-System analysis and design, traditional approach, object-oriented approach, data flow diagram, use case diagram.

Proceedings of the 21st International Conference on Enterprise Information Systems, 2019

Object Oriented Analysis and Design uses diagrams for three types of modeling: structural, dynamic and functional. For external point of view, functional modelling is used to define business requirements through users' requirements, to refine system functionality and to define processes that have to be enabled with the objects, containing attributes and methods. The functional model specifies the meanings of operations over the objects and actions of the dynamic modelling. The acquired functional models are visualized by UML use case diagrams and use case scenarios according to the software engineering principles. As a result of using use case diagrams, activity diagrams have to be done as a part of the functional model. These components of the model define the basic building blocks, roles and activities as well as the rules. They are used in the next software development phases in order the developers to have a clear understanding of the whole project. The paper presents the practical application of the functional modelling by using use case diagrams through scenario methods and highlighted processes with the use case and activity diagrams for information system for IT education company management.

2009

The chapter provides an overview of FOOM–Functional and Object-oriented Methodology–for analysis and design of information systems. FOOM integrates the functional and object-oriented approaches. In the analysis phase, two main models are created: a) a conceptual data model, in the form of an initial class diagram; and b) a functional model, in the form of OO-DFDs (object-oriented data-flow diagram).

Information systems, 1991

A methodology that combines and integrates the major stages of information systems development is presented. The methodology is based on hierarchical data-flow diagrams (DFD), which are used to perform a functional analysis of the system. This enables the conducting of process design on the one hand, and information structure analysis and database design on the other hand. Specifically, we describe a method that connects the transactions of the system, the product of the process design stage, with the record types (relations), the product of the database design stage. This connection closes the gap between the procedural and structural aspects of the system, and enables a smooth transition to the stage of system construction. It also facilitates the design of sub-systems and their database sub-schemas. Software tools that support all stages of the methodology are reviewed, emphasizing the tool DS2Ds that connects the transactions with the record types.

Lecture Notes in Business Information Processing, 2009

Business process modelling is a common activity when modelling an organization during the requirements engineering process of an information system. It is a must for modelling of process-aware information systems, and it can be considered the main activity. Nonetheless, business process diagrams must be complemented with a data perspective of these systems. This paper presents a requirements engineering approach that provides methodological guidance to meet this need through the integration of two other approaches. First, functional requirements are elicited and specified from business process diagrams. Next, the information flows of these requirements are specified. Finally, data modelling is carried out by following a set of guidelines. and/or information sources on the basis of process models , and their characteristics imply that RE approaches for their development must differ from traditional ones . First, detailed process models are necessary in the RE process. Second, new systems must support new ways of (better) running an organization.

Annals of Software Engineering, 2000

Conceptual modelling is situated in the broader view of information systems require-ments engineering. Requirements Engineering (RE) explores the objectives of different stakeholders and the activities carried out by them to meet these objectives in order to derive ...

Notes on Numerical Fluid Mechanics and Multidisciplinary Design, 2005

The focus of this paper is not on the requirements of an information system to be developed, but rather on the requirements that apply to the modelling techniques used during information system development. We claim that in past and present, many information systems modelling techniques have been developed without a proper understanding of the requirements that follow from the development processes in which these techniques are to be used. This paper provides a progress report on our research efforts to obtain a fundamental understanding of the requirements mentioned. We discuss the underlying research issues, the research approach we use, the way of thinking (weltanschauung) that will be employed in finding the answers, and some first results. -What are the purposes that modelling techniques should serve when used in information system development?