Author Topic: Verification and Validation in GERAM Framework for Modeling of Information Syste  (Read 1868 times)

0 Members and 1 Guest are viewing this topic.

IJSER Content Writer

  • Sr. Member
  • ****
  • Posts: 327
  • Karma: +0/-1
    • View Profile
Quote
Author : Majid Aarabi, Misam Kashefi, M.R. Khoei, Muhamad Zameri Mat Saman, Hooshang M. Beheshti
International Journal of Scientific & Engineering Research Volume 2, Issue 10, October-2011
ISSN 2229-5518
Download Full Paper : PDF

Abstract - The main aim of this article is to propose a methodology for using verification and validation tools in a framework for modeling of an Industrial Enterprise Information Systems. The first part of this paper introduces the Generalized Enterprise Reference Architecture and Methodology (GERAM) framework and its parts that are used for modeling of industrial enterprise information systems. The second part introduces the verification and validation concepts and tools. The third part of this article proposes the use of the verification and validation tools in GERAM framework to improve the coherency, correctness, error-free, qualitative aspects and efficiency of an enterprise information system.

Index Terms - Information Systems, Enterprise modeling, Verification, Validation, Industrial Enterprise, ISO 15704, GERAM
 
1   INTRODUCTION
THE Intricacies of models, their results and effect on their environment as well as the reaction of the stakeholders to the modeled system before its im-plementation can be observed with modeling techniques. Models are the representation of reality of each system. The complexities of the existing information systems in industrial and manufacturing enterprises do not allow modelers to do modeling without regard to verification and validation of these designed models. Nowadays, there are many frameworks available providing a road map for the modeling of the information systems, but, many of these frameworks does not consider verification and validation approach of these models. The complexity and importance of modeling of the information systems in today’s competitive and global businee which is continually changing require modeling of information systems to be highly adaptive to changes in the market. For this reason, the application of verification and validation tools for the framework governing these models is critical. As a standard and comprehensive framework, the GERAM framework which is considered as an ISO 15704 does not consider the use of verification and validation tools in modeling.

2 ENTERPRISE AND MODELING FRAMEWORK
2.1 Enterprise architecture

Enterprise architecture was developed by John Zach-man while with IBM in the 1980s [1].

Architecture is the integrated structural design of an enterprise, the elements and components of it and the relationships among them which are related to the requirements of the enterprise [2]. In this definition, ‘‘an enterprise may be a company, an institution, or a department within a company’’ [3].

2.2 Information Systems Architecture
The architecture for an information system is the abstract plan that includes the corresponding designed processes of the system's structure suitable to the goals of the system based on design principles and a methodological framework [2].

2.3 ISO15704 (Annex A: GERAM)
IFIP-IFAC Task Force developed the Generalized Enter-prise Reference Architecture and Methodology (GE-RAM) [4-6], and adopted it as an Appendix of ISO15704:2000 [7, 8].
This framework started from the evaluation of exist-ing enterprise integration architecture (CIMOSA, GRAI/GIM and PERA). GERAM is about methods, models and tools which are needed to build and main-tain the integrated enterprise [7].

The structure of GERAM reflects its envisaged pur-pose of assessing candidate architectures for a given enterprise architecture task type and thus enabling users to make an informed decision on the combination of architecture frameworks (or architecture framework elements) to be used so that all necessary aspects are covered [9].

3   VERIFICATION AND VALIDATION (V&V)
V&V Challenges
The challenges of Verification and validation as stated in Pace [10] are:
 
• The first motivation of V&V is for modeling and si-mulation for risk reduction, i.e., to ensure that the simu-lation can achieve its user favorable objectives.
• Effective communication is a problem because of continuing differences in the details about concepts, terminology, and V&V paradigms among various modeling and simulation communities; excessive use of acronyms makes it difficult to communicate easily across different communities.
• Advances in modeling and simulation frame-work/theory can improve the V&V capabilities and is necessary to increase automated V&V techniques.
• Limitations in items required for effective V&V data and detailed characterization of uncertainties and errors, simulation/software artifacts, etc. They have to be addressed, with a lot of the management processes to cope with them.
• Cost and resource requirements for modeling and simulation V&V are not as well understood as they need to be because meaningful information about such is not widely shared within modeling and simulation communities, and much more information about cost and resource requirements needs to be collected and made available to facilitate development of more reliable estimation processes. The modeling and simulation V&V community is faced with two very different kinds of challenges. One set relates to modeling and simulation management (or implementation): how to do what we know how to do in a proper manner consistently. The other challenges have a research flavor: areas that we need to understand better in order to find viable technical solutions [10].

How choose the technique of V&V?
The model manager and V&V agent must be familiar with and select the techniques and approaches to use to maximize confidence in each model by considering such constraints/factors as:
-   Cost
-   Time
-   Model’s intended use
-   Model’s users
-   Data availability
-   Required level of verification & validation
-   Development approach
-   Model maturity [11]

Read More: Click here...