Peretz Shoval

The chapter provides an overview of FOOM–Functional and Object-oriented Methodology–for analysis and design of information systems. FOOM integrates the functional and...

In the analysis phase of the information system development, the user requirements are studied, and analysis models are created. In most UML-based methodologies, the analysis...

Functional and Object Oriented Analysis and Design: An Integrated Methodology teaches students of information systems, software engineering, computer science, and related areas...

The term “object oriented” spread in the last decade and a half, throughout many fields of computing, including the analysis and design of information systems (IS). The use of...

The objects model (or object oriented [OO] model) is a conceptual-application model that is used to define a database schema representing a certain reality. The model views the...

This chapter discusses considerations and rules for identifying classes, attributes, relationships, and functions; and presents case study examples (problems), that is...

This chapter first explains why it might be preferred to first create an entity relationship diagram (ERD) and then map it to a class diagram. The chapter then describes the...

This chapter first explains the need to map a class diagram to a relational schema. Then, most of the chapter is dedicated to presenting and demonstrating the mapping rules based...

This chapter reviews the evolution of object oriented (OO) methodologies and unified modeling language (UML). Most of the chapter is dedicated to presenting and demonstrating the...

This chapter starts with a brief discussion on approaches to system development methodologies and the motivation for the development of the integrated methodology FOOM. Then it...

This chapter elaborates on the activities and products of the analysis stage with functional and object oriented methodology (FOOM). The products of this stage include a...

This chapter explains the roles of a data dictionary (DD) in the development of the information system (IS) and describes its components. The chapter presents a possible...

This chapter starts with an overview of the design phase according to the functional and object oriented methodology (FOOM) and presents the subphases and their products. Then...

This chapter deals with the design of the interfaces between the users and the system. First, it describes a method for the design of menus trees—for the entire system as well as...

This chapter describes how to map a top-level description of a transaction into a detailed description, and then how to “decompose” a detailed description of a transaction into...

Functional and Object Oriented Methodology (FOOM) combines two essential software-engineering paradigms: the functional (process-oriented) approach and the object-oriented (OO)...

Many paradigms for system analysis and design have been proposed over the years. Early approaches have advocated the functional approach. Common methodologies that support this...

FOOM (Functional and Object-Oriented Methodology) and OPM (Object-Processes Methodology) are methodologies used for analyzing and designing information systems. Both integrate...

HERD is a semi-algorithmic method for creating hierarchical ER diagrams from bottom up. The method is based on packaging operations that are applied in several steps on a given...

FOOM (Functional and Object-Oriented Methodology) is an integrated methodology for information systems’ analysis and design, which combines two essential software-engineering...

Entity-Relationship (ER) schemas include cardinality constraints that restrict the dependencies among entities within a relationship type. The cardinality constraints have direct...

FOOM is an integrated methodology for analysis and design of information systems, which combines the two essential software-engineering paradigms: the functional- (or process-)...

We propose FOOM (Functional and Object-Oriented Methodology), an integrated methodology for information systems analysis and design, which combines two essential...

Entity Relationship (ER) schemas include cardinality constraints, that restrict the dependencies among entities within a relationship type. The cardinality constraints have...

A database conceptual schema serves as a communication medium between professional analysts/designers and users who wish to comprehend and validate the conceptual schema. The...

The purpose of a data model is to express the semantics of the real world that it models. One common situation that should be modeled is that of many-to-many relationships...