Designing class methods from dataflow diagrams

Peretz Shoval, Judith Kabeli-Shani

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

A method for designing the class methods of an information system is described. The method is part of FOOM - Functional and Object-Oriented Methodology. In the analysis phase of FOOM, two models defining the users' requirements are created: a conceptual data model - an initial class diagram; and a functional model - hierarchical OO-DFDs (object-oriented dataflow diagrams). Based on these models, a well-defined process of methods design is applied. First, the OO-DFDs are converted into transactions, i.e., system processes that supports user task. The components and the process logic of each transaction are described in detail, using pseudocode. Then, each transaction is decomposed, according to well-defined rules, into class methods of various types: basic methods, application-specific methods and main transaction (control) methods. Each method is attached to a proper class; messages between methods express the process logic of each transaction. The methods are defined using pseudocode or message charts.

Original languageEnglish
Title of host publicationInformation Systems Development
Subtitle of host publicationTowards a Service Provision Society
Pages1-10
Number of pages10
DOIs
StatePublished - 1 Dec 2009
Event17th International Conference on Information Systems Development, ISD 2008 - Paphos, Cyprus
Duration: 25 Aug 200827 Aug 2008

Publication series

NameInformation Systems Development: Towards a Service Provision Society

Conference

Conference17th International Conference on Information Systems Development, ISD 2008
Country/TerritoryCyprus
CityPaphos
Period25/08/0827/08/08

Keywords

  • Class diagram
  • Dataflow diagram
  • Information systems design
  • Methods
  • Object-oriented development
  • System development methodology
  • Transactions

ASJC Scopus subject areas

  • Information Systems

Fingerprint

Dive into the research topics of 'Designing class methods from dataflow diagrams'. Together they form a unique fingerprint.

Cite this