Volume 7 Number 11 (Nov. 2012)
Home > Archive > 2012 > Volume 7 Number 11 (Nov. 2012) >
JSW 2012 Vol.7(11): 2538-2552 ISSN: 1796-217X
doi: 10.4304//jsw.7.11.2538-2552

Is In-Depth Object-Oriented Knowledge Necessary to Develop Quality Robustness Diagrams?

Mohamed El-Attar1, Mahmoud O. Elish1, Sajjad Mahmood1, James Miller2

1Department of Information and Computer Science King Fahd University of Petroleum and Minerals P.O. Box 5066, Dhahran 31261, Kingdom of Saudi Arabia
2Department of Electrical and Computer Engineering University of Alberta Edmonton, Alberta T6G 2VB, Canada

Abstract—PURPOSE: Robustness analysis is a technique that can be performed to help ensure the correctness, completeness and consistency of use case and domain models. Robustness analysis also helps bridge the gap between the analysis and design phases by providing a guided approach to identify a first-guess set of objects that will realize scenarios described in use cases. It is necessary to perform robustness analysis in the early phases of the development lifecycle in order to reap its benefits. In particular, robustness analysis needs to be performed by business analysts during the requirements phase to improve the quality of their models as well as help provide a seamless transition to the design phase. However, a core skill that is required to develop robustness diagrams is knowledge of OO concepts which business analysts normally do not have. To overcome this limitation, business analysts acquire brief knowledge of OO concepts via a small learning curve in order to develop and reap the benefits of creating robustness diagrams. However, is this brief knowledge of OO concepts attained through a small learning curve enough to allow business analysts to develop quality robustness diagrams?

Index Terms—Robustness Analysis, Robustness Diagrams, Use Cases, Business Analysts, Controlled Experiment


Cite: Mohamed El-Attar, Mahmoud O. Elish, Sajjad Mahmood,James Miller, "Is In-Depth Object-Oriented Knowledge Necessary to Develop Quality Robustness Diagrams?," Journal of Software vol. 7, no. 11, pp. 2538-2552, 2012.

General Information

  • ISSN: 1796-217X (Online)
  • Frequency:  Quarterly
  • Editor-in-Chief: Prof. Antanas Verikas
  • Executive Editor: Ms. Yoyo Y. Zhou
  • Abstracting/ Indexing: DBLP, EBSCO, CNKIGoogle Scholar, ProQuest, INSPEC(IET), ULRICH's Periodicals Directory, WorldCat, etc
  • E-mail: jsweditorialoffice@gmail.com
  • APC: 500USD
  • Jun 12, 2024 News!

    Vol 19, No 2 has been published with online version   [Click]

  • Jan 04, 2024 News!

    JSW will adopt Article-by-Article Work Flow

  • Apr 01, 2024 News!

    Vol 14, No 4- Vol 14, No 12 has been indexed by IET-(Inspec)     [Click]

  • Apr 01, 2024 News!

    Papers published in JSW Vol 18, No 1- Vol 18, No 6 have been indexed by DBLP   [Click]

  • Mar 01, 2024 News!

    Vol 19, No 1 has been published with online version    [Click]