Combining use case diagram and integrated definition's IDEF0 - A preliminary study

Rozilawati Razali, Parnian Najafi, Seyed Hadi Mirisaee

Research output: Chapter in Book/Report/Conference proceedingConference contribution

4 Citations (Scopus)

Abstract

Functional requirements are the statements of services that a system should provide to its users. It is imperative to state explicitly those requirements at the very beginning of system development process, as they act as the basis for the later stages. Normally, this is accomplished through modelling. Modelling enables functional requirements to become apparent to stakeholders. The modelling can be in the form of textual, graphical or even the combination of both. This paper discusses two instances of graphical modelling notations, namely Use Case Diagram (UCD) of Unified Modelling Language (UML) and IDEF0 of Integrated Definition Methods (IDEF). It compares the utility of both notations in illustrating the functional requirements of a telecommunication system. The preliminary outcome of the study seems to suggest that UCD and IDEF0 respectively have specific limitations, which can be compensated by the strengths of the other. It is therefore envisaged that the usefulness of a model can be improved by having both notations together. The paper concludes the discussion by suggesting a way on how both notations can be used collectively for modelling functional requirements of a system.

Original languageEnglish
Title of host publication2nd International Conference on Software Engineering and Data Mining, SEDM 2010
Pages231-236
Number of pages6
Publication statusPublished - 2010
Event2nd International Conference on Software Engineering and Data Mining, SEDM 2010 - Chengdu
Duration: 23 Jun 201025 Jun 2010

Other

Other2nd International Conference on Software Engineering and Data Mining, SEDM 2010
CityChengdu
Period23/6/1025/6/10

Fingerprint

Unified Modeling Language
Telecommunication systems

Keywords

  • Functional requirements
  • Graphical modelling
  • IDEF0 and Use Case
  • Requirements engineering

ASJC Scopus subject areas

  • Software

Cite this

Razali, R., Najafi, P., & Mirisaee, S. H. (2010). Combining use case diagram and integrated definition's IDEF0 - A preliminary study. In 2nd International Conference on Software Engineering and Data Mining, SEDM 2010 (pp. 231-236). [5542919]

Combining use case diagram and integrated definition's IDEF0 - A preliminary study. / Razali, Rozilawati; Najafi, Parnian; Mirisaee, Seyed Hadi.

2nd International Conference on Software Engineering and Data Mining, SEDM 2010. 2010. p. 231-236 5542919.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Razali, R, Najafi, P & Mirisaee, SH 2010, Combining use case diagram and integrated definition's IDEF0 - A preliminary study. in 2nd International Conference on Software Engineering and Data Mining, SEDM 2010., 5542919, pp. 231-236, 2nd International Conference on Software Engineering and Data Mining, SEDM 2010, Chengdu, 23/6/10.
Razali R, Najafi P, Mirisaee SH. Combining use case diagram and integrated definition's IDEF0 - A preliminary study. In 2nd International Conference on Software Engineering and Data Mining, SEDM 2010. 2010. p. 231-236. 5542919
Razali, Rozilawati ; Najafi, Parnian ; Mirisaee, Seyed Hadi. / Combining use case diagram and integrated definition's IDEF0 - A preliminary study. 2nd International Conference on Software Engineering and Data Mining, SEDM 2010. 2010. pp. 231-236
@inproceedings{01a5362d13c5427e80d79833b63a0820,
title = "Combining use case diagram and integrated definition's IDEF0 - A preliminary study",
abstract = "Functional requirements are the statements of services that a system should provide to its users. It is imperative to state explicitly those requirements at the very beginning of system development process, as they act as the basis for the later stages. Normally, this is accomplished through modelling. Modelling enables functional requirements to become apparent to stakeholders. The modelling can be in the form of textual, graphical or even the combination of both. This paper discusses two instances of graphical modelling notations, namely Use Case Diagram (UCD) of Unified Modelling Language (UML) and IDEF0 of Integrated Definition Methods (IDEF). It compares the utility of both notations in illustrating the functional requirements of a telecommunication system. The preliminary outcome of the study seems to suggest that UCD and IDEF0 respectively have specific limitations, which can be compensated by the strengths of the other. It is therefore envisaged that the usefulness of a model can be improved by having both notations together. The paper concludes the discussion by suggesting a way on how both notations can be used collectively for modelling functional requirements of a system.",
keywords = "Functional requirements, Graphical modelling, IDEF0 and Use Case, Requirements engineering",
author = "Rozilawati Razali and Parnian Najafi and Mirisaee, {Seyed Hadi}",
year = "2010",
language = "English",
isbn = "9788988678213",
pages = "231--236",
booktitle = "2nd International Conference on Software Engineering and Data Mining, SEDM 2010",

}

TY - GEN

T1 - Combining use case diagram and integrated definition's IDEF0 - A preliminary study

AU - Razali, Rozilawati

AU - Najafi, Parnian

AU - Mirisaee, Seyed Hadi

PY - 2010

Y1 - 2010

N2 - Functional requirements are the statements of services that a system should provide to its users. It is imperative to state explicitly those requirements at the very beginning of system development process, as they act as the basis for the later stages. Normally, this is accomplished through modelling. Modelling enables functional requirements to become apparent to stakeholders. The modelling can be in the form of textual, graphical or even the combination of both. This paper discusses two instances of graphical modelling notations, namely Use Case Diagram (UCD) of Unified Modelling Language (UML) and IDEF0 of Integrated Definition Methods (IDEF). It compares the utility of both notations in illustrating the functional requirements of a telecommunication system. The preliminary outcome of the study seems to suggest that UCD and IDEF0 respectively have specific limitations, which can be compensated by the strengths of the other. It is therefore envisaged that the usefulness of a model can be improved by having both notations together. The paper concludes the discussion by suggesting a way on how both notations can be used collectively for modelling functional requirements of a system.

AB - Functional requirements are the statements of services that a system should provide to its users. It is imperative to state explicitly those requirements at the very beginning of system development process, as they act as the basis for the later stages. Normally, this is accomplished through modelling. Modelling enables functional requirements to become apparent to stakeholders. The modelling can be in the form of textual, graphical or even the combination of both. This paper discusses two instances of graphical modelling notations, namely Use Case Diagram (UCD) of Unified Modelling Language (UML) and IDEF0 of Integrated Definition Methods (IDEF). It compares the utility of both notations in illustrating the functional requirements of a telecommunication system. The preliminary outcome of the study seems to suggest that UCD and IDEF0 respectively have specific limitations, which can be compensated by the strengths of the other. It is therefore envisaged that the usefulness of a model can be improved by having both notations together. The paper concludes the discussion by suggesting a way on how both notations can be used collectively for modelling functional requirements of a system.

KW - Functional requirements

KW - Graphical modelling

KW - IDEF0 and Use Case

KW - Requirements engineering

UR - http://www.scopus.com/inward/record.url?scp=77956542375&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=77956542375&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:77956542375

SN - 9788988678213

SP - 231

EP - 236

BT - 2nd International Conference on Software Engineering and Data Mining, SEDM 2010

ER -