IRMA-International.org: Creator of Knowledge
Information Resources Management Association
Advancing the Concepts & Practices of Information Resources Management in Modern Organizations

FOOM-An Integrated Methodology for Analysis and Design of Information Systems

FOOM-An Integrated Methodology for Analysis and Design of Information Systems
View Free PDF
Author(s): Judith Kabeli (Ben-Gurion University, Israel)and Peretz Shoval (Ben-Gurion University, Israel)
Copyright: 2002
Pages: 6
Source title: Issues & Trends of Information Technology Management in Contemporary Organizations
Source Editor(s): Mehdi Khosrow-Pour, D.B.A. (Information Resources Management Association, USA)
DOI: 10.4018/978-1-930708-39-6.ch106
ISBN13: 9781930708396
EISBN13: 9781466641358

Abstract

FOOM is a Functional and Object-Oriented Methodology for analysis and design of information systems, which combines the two essential software-engineering paradigms: the functional- (or process-) oriented approach and the object-oriented (OO) approach. In FOOM, system analysis includes both functional and data modeling activities, thereby producing both a functional model and a data model. These activities can be performed either by starting with functional analysis and continuing with data modeling, or vise versa. FOOM products of the analysis phase include: an initial object schema, which can be created from the user requirements and a hierarchy of OO-DFDs (object-oriented data flow diagrams). System design is performed according to the OO approach. The products of the design phase include: a) a complete object schema, consisting of the classes and their relationships, attributes, and method interfaces; b) object classes for the menus, forms and reports; and c) a behavior schema, which consists of detailed descriptions of the methods and the application transactions, expressed in pseudo-code and message diagrams. The seamless transition from analysis to design is attributed to ADISSA methodology, which facilitates the design of the menus, forms and reports classes, and the system behavior schema, from DFDs and the application transactions.

Body Bottom