FOOM - Functional and Object-Oriented Methodology for Analysis and Design of Information Systems

2002 ◽  
pp. 58-86 ◽  
Author(s):  
Peretz Shoval ◽  
Judith Kabeli
Keyword(s):  
Information Systems ◽  
System Analysis ◽  
Functional Model ◽  
Data Modeling ◽  
Object Oriented ◽  
Analysis And Design ◽  
Seamless Transition ◽  
Flow Diagrams ◽  
Entity Relationship ◽  
Entity Relationship Diagram

FOOM is an integrated 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 vice versa. FOOM products of the analysis phase include: a) a hierarchy of OO-DFDs (object-oriented data flow diagrams), and b) an initial object schema, which can be created directly from the user requirements specification or from an entity-relationship diagram (ERD) that is mapped to that object schema. 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.

The Application of FOOM Methodology to IFIP Conference Case Study

2003 ◽  
pp. 82-95
Author(s):  
Judith Kabeli ◽  
Peretz Shoval
Keyword(s):  
Functional Analysis ◽  
Information Systems ◽  
Object Oriented ◽  
Class Diagram ◽  
Design Phase ◽  
Complete Class ◽  
Analysis And Design ◽  
Systems Analysis And Design ◽  
Flow Diagrams

FOOM (Functional and Object-Oriented Methodology) is an integrated methodology for information systems’ analysis and design, which combines two essential software-engineering paradigms: the functional/data approach (or process-oriented) and the object-oriented (OO) approach. Having applied FOOM in a variety of domains, this chapter presents the application of the methodology to the specification of the IFIP Conference system. We focus on the analysis and design phases. FOOM-analysis phase includes data modeling and functional analysis activities and produces an initial Class Diagram and a hierarchy of OO data flow diagrams (OO-DFDs). The products of the design phase include: (a) a complete class diagram; (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 pseudocode and message diagrams.

scholarly journals Rancangan Sistem Informasi Penjualan pada Toko Kue

2015 ◽  
Vol 6 (1) ◽  
pp. 31
Author(s):  
Angelina Permatasari
Keyword(s):  
Information System ◽  
Information Systems ◽  
Information Needs ◽  
System Analysis ◽  
Design Method ◽  
Object Oriented ◽  
Design Methods ◽  
Analysis And Design ◽  
Analysis Methods ◽  
Object Oriented Analysis

The purpose of this research is to analyze the problems that may occur in the cake stores, especially theselling system used in the store, identify information needs and designing suitable sales information systems for the store. The methodology used in this research are analysis and design methods. Analysis methods that used in this research are study literature, observation, survey of the old system, analysis of survey needs, identification of information needs and interview. While the design method that used in this research is Object Oriented Analysis and Design (OOAD). The results achieved is sales information system for cake store in the form ofapplication design to replace the manual system. Conclusion, a computerized sales information system can improve existing sales procedures and solve the problems that may occur in the old system.

Essentials of Functional and Object-Oriented Methodology

2005 ◽  
pp. 1108-1115 ◽  
Author(s):  
Peretz Shoval ◽  
Judith Kabeli
Keyword(s):  
Data Model ◽  
System Analysis ◽  
Analysis And Design ◽  
Use Of Data ◽  
Functional Aspects ◽  
Data Flows ◽  
Relational Database Schema ◽  
Flow Diagrams ◽  
Entity Relationship ◽  
Conceptual Data

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 approach are SSA and SSD (DeMarco, 1978; Yourdon & Constantine, 1979). SSA is based on the use of data flow diagrams (DFDs), which define the functions of the system, the data stores within the system, the external entities, and the data flows among these components. Early SSA and similar methodologies emphasized the functional aspects of system analysis, neglecting somehow the structural aspects, namely the data model. This was remedied by enhancing those methodologies with a conceptual data model, usually the entity-relationship (ER) model (Chen, 1976), that is used to create a diagram of the data model, which is later mapped to a relational database schema.

Manufacturing Plant Management Information System Analysis and Design Based on UML

2010 ◽  
Vol 455 ◽  
pp. 237-241
Author(s):  
X.Y. Yang ◽  
H.B. Zheng ◽  
Z.W. Zhang
Keyword(s):  
Asset Management ◽  
System Analysis ◽  
Structural Model ◽  
System Development ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Plant Management ◽  
Management Information ◽  
Static Structure ◽  
Analysis And Design

With the development of manufacturing automation and intelligent increasing speed, the construction in plant management information has been important tasks to promote business innovation ability, improve competitiveness and manufacturing execution. In this paper, UML (Unified Modeling Language) and object-oriented modeling technology were applied to model the static structure and dynamic behavior of the plant management information from requirement analysis to system implementation, including functional requirement model, static structural model, asset management time sequence chart, system physical model and so on. The visualized system analysis method and technology better planned the system design and improved the efficiency of the system development. It will play a guiding role in the object-oriented software development.

scholarly journals Object Oriented VS Structured Analysis and Design in System Development Courses

2019 ◽  
Vol 8 (6S3) ◽  
pp. 82-88
Keyword(s):  
System Analysis ◽  
Survey Methodology ◽  
System Development ◽  
Object Oriented ◽  
Analysis And Design ◽  
Institutions Of Higher Learning ◽  
Structured Analysis ◽  
The One ◽  
Structured Analysis And Design

Objectives: The main aim of this study was to investigate the factors that influence students’, academicians’, clients’, as well as developer’s preferences in choosing their preferred approach in system development, namely structured analysis design (SAD) or object-oriented analysis and design (OOAD). Methods: The research design was based on a survey methodology and a case study. For the survey, questionnaires were administered to 30 students and 38 academicians, who were randomly selected from several Malaysian universities. For the case study, the requirements of the information system were modeled and presented to several clients to elicit their feedback. The survey data were analyzed using SPSS Findings: The result shows that students preferred the use of OOAD approach, which clearly outnumbered those who preferred the SAD approach, which stood at 33%. Interestingly, the majority (53%) of academicians preferred the use of a mixture of both approaches. Likewise, the clients shared a similar view with the academicians, whereas the developer preferred the OOAD approach. Application/Improvements: Clearly, the findings suggest that both approaches are essential, but the one that is widely used by developers and preferred by students is OOAD, and thus should be given priority when it comes to structured analysis and design. As such, curriculum designers and institutions of higher learning, particularly those offering system analysis and design and related courses, should make the necessary changes to the existing curriculum such that the academic programs offered will be able to produce highly competent and skilled analysts and designers as required by the industry.

An Examination of Topical Coverage for the First Accounting Information Systems Course

2002 ◽  
Vol 16 (2) ◽  
pp. 143-164 ◽  
Author(s):  
Craig E. Bain ◽  
Alan I. Blankley ◽  
L. Murphy Smith
Keyword(s):  
Information Systems ◽  
Internal Control ◽  
System Analysis ◽  
Accounting Information ◽  
Accounting Information Systems ◽  
Analysis And Design ◽  
Internet Education ◽  
Software Applications ◽  
Introductory Accounting ◽  
Software And Hardware

This study examines topics currently addressed in the introductory Accounting Information Systems (AIS) course and makes comparisons to past studies. The study includes an examination of 12 current AIS textbooks, syllabi from current AIS instructors, and the results of a survey of AIS faculty and professionals. The divisions of topics in the books and on the syllabi suggest that introduction to systems, internal control, and transaction processing are the most important topics to be covered. After these topics, the rankings diverge. The results of this study suggest that the emphasis historically placed on system analysis and design, while still important, is somewhat less than in the past. This was also apparent from the results of the authors' surveys of AIS faculty and professionals who use technology in their jobs. Both faculty and professionals agree that greater importance should be placed on teaching internal control and transactions processing, while moderate importance should be placed on software and hardware issues. Professionals ranked ethics and Internet education of greater importance than did faculty, while faculty rated computer fraud (which may tie in with ethics) and database management systems of greater importance than did the professionals. Professionals also placed higher importance on teaching software applications (particularly spreadsheet applications) than did faculty.

Causal Mapping for the Investigation of the Adoption of UML in Information Technology Project Development

2005 ◽  
pp. 233-262 ◽  
Author(s):  
Tor J. Larsen ◽  
Fred Niederman
Keyword(s):  
Information Technology ◽  
Information Systems ◽  
Object Oriented ◽  
Collection Method ◽  
Causal Mapping ◽  
Analysis And Design ◽  
Technology Project ◽  
Information Technology Project ◽  
Application Developers ◽  
Object Oriented Analysis

This research project gathered data about the use of UML and object-oriented analysis and design as the approach to the development of information systems. The data collection method consisted of interviews with information systems application developers with wide ranging differences in background. The authors used causal mapping for analysis of the data gathered. This chapter focuses on the authors’ experiences with causal mapping as a method for exploring issues and relationships. Causal mapping was also used to document tips on its use illustrating these with findings regarding UML and object-oriented analysis and design in particular.

Information Systems Analysis with FOOM

2011 ◽  
pp. 178-229
Author(s):  
Peretz Shoval
Keyword(s):  
Information Systems ◽  
Systems Analysis ◽  
Data Flow ◽  
Functional Model ◽  
Object Oriented ◽  
Flow Diagram ◽  
Class Diagram ◽  
Data Flow Diagram ◽  
Data Objects

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 data/objects model in the form of an initial class diagram, and a functional model in the form of hierarchical object oriented Data flow diagram (OO-DFDs). The two diagram types are synchronized in order to guarantee the correctness and completeness of the two models. The chapter presents various examples of diagrams of both types.

Introduction to the Objects Approach in Software

2011 ◽  
pp. 1-12
Author(s):  
Peretz Shoval
Keyword(s):  
Artificial Intelligence ◽  
Information Systems ◽  
Programming Languages ◽  
Operating Systems ◽  
Object Oriented ◽  
Main Field ◽  
Analysis And Design ◽  
Development Costs ◽  
Graphical Interfaces

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 OO approach began in the early 1970s in fields such as computers architecture, operating systems, and artificial intelligence. But the main field to which the approach penetrated was programming languages, beginning with Simula and then with Smalltalk. Some years passed by until the approach became popular in the programming field. Reasons for the vigorous penetration of the approach include the emergence of the windows-based graphical interfaces technology, the desire to economize development costs by reusing existing software, and the transition from centralized computing to distributed- and Internet-based computing. As aforesaid, the approach penetrated into other fields of computing due to its success in the field of programming, including the field of analysis and design of IS.

Sign in / Sign up

Export Citation Format

Share Document