Conceptual Model for a Software Maintenance Environment

Size: px
Start display at page:

Download "Conceptual Model for a Software Maintenance Environment"

Transcription

1 Conceptual Model for a Software Environment Miriam. A. M. Capretz Software Engineering Lab School of Computer Science & Engineering University of Aizu Aizu-Wakamatsu City Fukushima, Japan phone: fax: mcapretz@u-aizu.ac.jp Abstract A conceptual model for a software maintenance method named COMFORM (Configuration Management Formalization for ) is presented. COMFORM provides guidelines and procedures for carrying out the maintenance process, while establishing a systematic approach for the support of existing software systems. Incremental documentation, the process of building up the software documentation while the system is maintained, has a key role in this maintenance method. The documentation required by the method consists of keeping the maintenance history and information related to the software modules being maintained. Forms have been created in order to guide the maintainers during the maintenance process. Thus, their task will be of filling in forms for generating the required documentation instead of defining their own document structures. The system information obtained by filling in forms has been formalized according to a data model which provides a common basis for the representation of the method. This paper presents the conceptual model for COMFORM which was obtained using the data model termed Object Representation Model (ORM). ORM has been used because of its enhanced semantic capabilities and it provides the necessary generality and standardization for software representation. 1. Introduction Models, in general, are abstractions designed to understand a problem before implementing a solution. Because a model omits non-essential details, it is easier to manipulate than the original entity. To build a complex system, the developer should abstract different views of the system, build models using precise notations, and gradually add detail to transform the models into an implementation. Moreover, models are useful for preparing documentation and designing systems and databases. The approach to modelling and formalizing the software development process has recently been receiving attention, since such a strategy provides great benefits to clear expression of abstract concepts. Additionally, it may provide both an insight into the development process and the necessary means to design more supportive software engineering environments. The research described in this paper is concerned with the modelling of a software maintenance method named Configuration Management Formalization for (COMFORM) [5, 6, 7]. This method provides guidelines and procedures for carrying out the maintenance process, while establishing a systematic approach for the support of existing software systems. A change control framework has been established in COMFORM in order to preserve software quality. The Software Model (SMM) institutes this framework, which aims to systematize the software maintenance process by specifying the chain of events and the order of stages that a change has to go through. During software maintenance, documentation should provide an abstract representation of the operational software system, which guides the decisions that affect the system s evolution. In order to obtain the documentation required for the method, the following imperatives have been stated: standardization of the information to be stored, in order to guarantee its completeness and preciseness; and the uniformity of document structures of the software systems

2 to be maintained must be upheld. To satisfy these demands, information is obtained by filling in forms. The intention of creating forms is to make the maintainers task one of filling in forms for documentation, instead of defining their own document structures. The forms represent the results of SMM phases, which allow a methodical approach to be taken towards the establishment and control of traceability throughout the maintenance process. The information obtained by filling in forms has been formalized according to a data model, which provides a common basis for the representation of the method s functionality. The conceptual model for COMFORM has been defined using the data model termed Object Representation Model (ORM) [10]. ORM has been used because of its enhanced semantic capabilities, which provide the necessary generality and standardization for software representation. The remaining of this paper is organized as follows. In section 2, the software maintenance method COMFORM is outlined. The conceptual model for COMFORM using ORM is described in section 3. An illustrative example which helps to visualize the modelling of COMFORM is given in section 4. A summary is presented in section The COMFORM Method One of the main objectives of the COMFORM method is to provide a systematic approach to maintaining existing software systems. The approach consists of establishing steps and providing guidelines to improve the software maintenance process and to preserve software quality. COMFORM takes the Software Configuration Management (SCM) [2] discipline into account, since this discipline imposes a set of procedures and standards for managing evolving software systems. The application of the SCM discipline contributes directly to software quality by identifying and controlling change, assuring the change is being properly implemented, and reporting the change to others who may have an interest. A change control framework named the Software Model (SMM) is the backbone of the method. It systematizes the software maintenance process by specifying the chain of events and the order of stages that a change has to go through. The output of the SMM phases are represented by forms which allow a methodical approach towards the establishment and control of traceability throughout the maintenance process. These forms are the source of documentation of maintenance history and system redocumentation. The SMM identifies the activities undertaken during software maintenance and the information needed or produced by these activities. The model is based on the traditional waterfall life-cycle model of software development. This is a convenient approach because it allows the process to be represented in a graphical and logical form, providing a framework around which quality assurance activities can be built in a purposeful and disciplined manner. Being a maintenance model, the SMM highlights the considerable influence of the existing software system on this whole process. The outcome of each SMM phase is a completed form which represents a point in the maintenance process. These completed forms are, therefore, the natural milestones, i.e. the baselines of the software maintenance process, and offer objective visualization of the evolution of that process. Each SMM phase is linked to one particular form whose aim is to keep the system documentation and the history of software evolution. Forms are particularly useful for redocumenting software systems since form fields can be predefined by the system manager, thus establishing a standard for redocumenting software system. The following phases with their respective outcome forms comprise the SMM: Phases Request Evaluation Specification Redocumentation Implementation System Release Forms Proposal Approval Specification Module Module Source Code Configuration Release Following the SMM, all requests for software maintenance are presented in a standardised manner during the change request phase using the change proposal form. The completion of a change proposal form triggers the process of maintenance in COMFORM. The form contains the basic information necessary for the evaluation of the proposed change. In the change evaluation phase, the maintainer is primarily concerned with understanding the change, and its effect within the software system. A rejected proposed change is then abandoned. If the proposed change is approved then a corresponding change approval form is created. The change approval form is one of the documents used as the basis for planning the system release. It is a vehicle for recording information about a system defect, a requested enhancement or quality improvements. The change approval form along with its corresponding change proposal form, is the basic tool of a change management system. By documenting new software requirements or requirements that are not being met, these forms become the contract between the person requesting the change and the maintainers who work on the change.

3 The maintenance design specification phase is characterised by the structure of the modification, which is in the form of a complete, consistent and comprehensible common specification of all the changes proposed and approved for a planned scheduled release. In addition, how the software components have to be modified needs to be clarified. The resultant form for this phase is the maintenance specification form which is generated after having selected the approved changes for the next system release. The maintenance design redocumentation along with the maintenance implementation phases facilitate system comprehension by incremental redocumentation, as proposed by the method. The forms associated with these two phases aim at documenting the software components of an existing software system. The forms will be filled in when the corresponding software component has to be modified. The forms associated with these phase are the module design and module source code forms respectively. While the module design form is aimed at keeping general and stable information for a software component its corresponding module source code form aims at keeping the information pertaining to modifications performed on these components. System release is the last phase of the SMM before a new configuration containing the approved changes is released to the user. Once modifications on the system have been performed under the configuration control function, the task at this stage is to certify that all baselines have been established. A configuration release form is the software system release planning document, which aims to keep the information pertaining to the history of a maintenance phase. The analogy between the approach proposed by this work and large projects such as REDO [1], MACS [9] and Re- Form [11] is that the proposed method (COMFORM) also aims to provide a method for software maintenance and places considerable emphasis on a single integrated representation of the original system in an object base. These environments, however, aim to reverse engineer the software systems and hand them over to current software engineering techniques in order to carry on their maintenance. The novelty of the COMFORM method is that, unlike the approach to software maintenance taken by these large projects, it takes a less drastic approach to the incrementallyrecovereddocumentationof existing software systems while the maintenance process is being performed. Therefore, COMFORM is not only a reverse-engineering method. It tackles the problem of incremental documentation, and at the same time, it provides guidance to carry on maintenance in a controlled way by applying the software configuration management discipline. Consequently, control over software systems is improved as maintenance is performed. The benefit of this technique is that it is a less expensive method, by which the maintainability and documentation of software systems increase as they are maintained. Moreover, the method can be routinely used to control the inevitable process of change. The complete description of each of the SMM phases along with the content of each of its outcome forms have already been presented elsewhere [6, 7]. In this paper we concentrate on the description of the conceptual model of the COMFORM method as well as the benefits the modelling provides for the implementation of the method in order to generate a generic software maintenance environment. 3. The Conceptual Model of COMFORM using ORM 3.1. The ORM Concepts This subsection describes the Object Representation Model (ORM) [10] formalism. Although ORM is not a well-known representation model, it has been used as it presents a very simple representation schema which attend our needs in this work. ORM provides further capabilities, but only those features which are employed in this research are emphasized in this section. Some of the fundamental concepts of ORM have the same features as semantic models [8]. For example, real-world aspects are modelled through objects (entities in semantic models), which may, in turn, be associated with other objects by relationships. Both objects and relationships may have attributes, which have an associated characteristic. Every element of ORM can be classified according to pre-defined standards, i.e., the types of the elements. The concept of type is equivalent to the set of entities and relationships of semantic models. However, this concept is also the same as that of object-oriented models [3, 4] which assign a type to each object, aiming at characterizing the properties and operations of the objects. The conceptual support of ORM consists of modelling data through objects and information associated with objects. This information may be the specification of some object characteristic (attribute), or the indication of a possible link with other objects (relationship); the latter may also have several attributes. The mathematical basis for the model is the graph theory. Therefore in ORM, the nodes of a digraph represent the objects of the real world; the arcs represent the associations (relationships) which exist among them. In general, object-oriented models name all objects of the same type as a class and the occurrence of each object as an object instance. Associations of objects are made through stored properties of each class, and the association is seldom explicitly stated. In ORM, associations of objects are made explicitly and, therefore, a clarification of terms to designate objects and relationships must be provided. Consequently,

4 the term object is used to designate an object instance, and the term relationship is used to designate a unique relationship between two given objects. Analogously, the term object type is used to designate all objects having the same properties; relationship type is used to designate all relationships having the same properties and linking the same object types. Graphic symbols used in the ORM diagrams are those ones used traditionally in the graphical representation of graphs. Object types in ORM diagrams are represented by divided circles. The upper half of the circle is used to write the name of the object type, while the name of the host cluster associated with the object type is written in the lower half (see Figure 1). A relationship is represented by an arc linking object types which are associated through the relationship type. In ORM, every relationship type has its correspondingly opposite relationship type. Additionally, every relationship type contains a maximum and minimum mapping, which characterize the quantity of relationships of a particular type in which the source object may be involved. The Cluster Mechanism Concept. The cluster mechanism is an important concept within ORM. It aims to provide a structure for organizing object types. The description of an object can be refined through a set of other objects. Each object of a set depends on (in terms of existence and identification), and is constrained by the object which refines them. The set of objects constrained by an object is termed a cluster of objects. A cluster of objects also owns a type, and therefore, objects of a particular type belong to the same particular cluster type. In other words, the set of cluster types establishes a partition on the set of object types, in as much as the set of all clusters of objects establishes a partition on the set of objects of an object base. In this way, similar to other terms in ORM, cluster type is used to designate the constraint on a set of object types; cluster of objects is used to designate an instance of a cluster type. A cluster type may have several object types associated with it as the designer establishes that they represent a particular focus of interest and thus should be manipulated as a particular set. The cluster mechanism is similar to the aggregation concept of object-oriented programming languages in the sense that it also denotes part-of hierarchies. However, the cluster mechanism provides not only the constraint on a set of objects and aims to establish a hierarchy among the objects, but it also provides the scheme which facilitates the manipulation of such sets for generation of versions within an object base. A cluster type may also comprise other cluster types so that they can be organized hierarchically and more detailed system information can be obtained as far down as one goes into the cluster hierarchy The COMFORM Model The conceptual model of COMFORM using the most important features of ORM is depicted in Figure 1. It - Reason for change - CP description - CP baseline established by (Reason for abandoning) - CP status - CP proposed by - CP date - CP identification Proposal Request is approved to give 1-1 has been approved from 1-1 Approval Evaluation 1-1 is required by 0-1 is specified by involves 1-n 0-n requires 1-n specifies 1-m is involved in Specification Specific. 0-n affects is affected by - CA identification - CA date - CA authorized by - CA status - CA baseline established by - Type of change - Identification of change - Resource estimates for change(design) - Resource estimates for change(coding) - Resources estimates for change(testing) - Priority of implementation - Consequences if not implemented - * version control - System tests - Integration tests - Consequences of change - Specification of change - MS baseline established by - MS status - MS formulated by - MS date - MS identification 0-m Module Redoc. *version control corresponds 1-1 to has a 1-1 correspondence with version identification version date version author version status status date version baseline established by description of modification - SC understood by - Comments - Tests outcome - SC baseline established by - SC implemented by SC date - SC identification - MD identification - MD date - MD designed by - MD status - MD baseline established by - Module Purpose - Algorithms outline - Interface definitions - Test plans Figure 1. The COMFORM model Module Source Code Implement. illustrates the forms which are the phase products of the SMM, through the object, relationship and attribute types. SMM forms have been chosen as the basic object types of the model as they represent the main and essential entities within COMFORM. Each of these object types are within a cluster type named after its respective SMM phase. The fields of the forms are either relationship or attribute types of the model. The relationship types link object types, providing a natural strategy for checking consistency and traceability between the forms. The attribute types related

5 to each object type (form) provide additional features associated with the forms. The attribute, together with the relationship types are the contents of the forms which have to be specified, in order to enable them to go through the completeness checks. One example of a SMM form (the Approval form) is shown Figure 2. CA identification: CA authorized by: Approval CA status: CA baseline established by: Date: Status date: 1. Related CP: 2. Type of change: 3. Identification of change: 4. Involved sw components id.: 5. Resource estimates for change (design): 6. Resource estimates for change (coding): 7. Resource estimates for change (testing): 8. Priority of implementation: 9. Consequences if not implemented: ages the grouping of forms in clusters in such a way that both the dependency and hierarchy of forms can be established. This mechanism plays an important role in the modelling of COMFORM, since it provides the capabilities to implement various COMFORM concepts. The use of clusters enables the implementation of scheduled releases, and also facilitates the implementationof version control. In addition, the cluster mechanism allows the storage of information of several existing software systems in the same object base; it also helps in the task of establishing baselines, since every form belongs to its respective cluster, which in turn comprises all the necessary information for the task. In the model of COMFORM, every cluster type comprises only one object type (form). The cluster types of the model are named after SMM phases. In addition, the object types they consist of are the products, i.e. the forms, which correspond to the result of these phases. The cluster hierarchy of COMFORM is depicted in Figure 3. Global System Figure 2. The change approval form Redocumentation System Release Implementation The modelling of COMFORM using ORM provides several benefits to help in the implementation of the method. The traceability and consistency of forms can be easily obtained by following the relationship types between them as represented in Figure 1. For instance, a change proposal form is traceable in the change approval form, through the relationship is approved to give/has been approved from which links them. This relationship will be generated after a proposed change is approved. The change proposal form characterizes the start of a maintenance activity and contains summary details of a proposed change in order to carry out its preliminary evaluation. Thus, the main evaluation information about a proposed change is contained in a change approval form. Constructing the relationship types as defined in the COMFORM model allows one to navigate through all the associated forms in a particular system release. It is worth noting that not all object types need to be directly associated with each other to obtain the traceability and consistency checks among them. The Cluster Mechanism in COMFORM. The cluster mechanism is an additional concept of ORM which encour- Request Evaluation Specification Figure 3. The cluster hierarchy of COMFORM The global cluster type at the top of the hierarchy, is the most generic one and encloses all other cluster types of the model. The next cluster type in the hierarchy is named system, and holds the information related to specific software systems being maintained. This way, the model permits COMFORM to maintain several existing software systems, without the information in one interfering with that in another. The third level in the hierarchy, comprises three cluster types named maintenance design redocumentation, system release and maintenance implementation. They are in the same level in the hierarchy because when a cluster of objects in the system type becomes accessible, i.e., documentation about a particular system is available, the maintainer is able to obtain any information related to that system (configuration release, module design or module

6 source code forms). In order to have control of the changes included in each system release, in the last level of the cluster hierarchy, the system release cluster type comprises the change request, change evaluation and maintenance design specification cluster types, which hold the forms to document the maintenance history of a particular system release. One of the goals of using the cluster mechanism in COM- FORM is the implementation of scheduled releases, and determination of the contents of each system release. The main advantage of scheduled releases is that changes are not introduced to the system at random. proposals should be organized and planned to be included in different system releases. This approach enables the optimization of maintenance tasks by grouping together those approved changes which involve the same software components, or have similar changes to be performed. 4. An Illustrative Example In order to clarify the COMFORM model described in the previous section, consider a simple example given in Figure 4. This figure shows the clusters of objects (ovals) and forms (rectangles), and illustrates the notion of cluster hierarchy. For the sake of simplicity, the name of the cluster types is omitted, since each SMM form is associated with its respective cluster type named after the SMM phase. The different cluster types are illustrated in the figure by the different patterns of the ovals. System1 is the name of the software system being maintained using COMFORM. System releases have been generated for system1. The first system release generated the form CR1 which contains and is related to other forms which document the software component which suffered modification as well as the history of the change performed. The change for this release was first proposed using the change proposal form CP1. After its approval, the change approval form CA1 and maintenance specification form MS1 were generated to keep the history of the change. The change involved modifications in the software component which then was documented in the module design and module source code forms MD1 and SC1 respectively. It is clear from this example that the information for a particular software system being maintained by COMFORM can be kept separate in an object base. Once a particular software system is instantiated, information about its system releases and software components (module design and module source code forms) can be obtained. If details of a particular system release are required, the cluster of objects which comprises its corresponding configuration release form provide all the required information. Although this paper has not given further details about System1 CP2 System Release MD1 SC1 CA2 Redocumentation Implementation MS2 CR1 CR2 Specification Evaluation Request CA1 MS1 MD2 SC2 CP1 System Figure 4. Illustrative example of the modelling versions of forms, it is worth mentioning that a version of a configuration release form aims at linking configuration releases together, which are either dependent on each other or part of the same context. This concept allows, for instance, the creation of a version of a configuration release form to correct errors in the previous releases. In doing so, the set of versions of configuration release forms provides the history of system release evolution. 5. Summary In this research work, ORM has been employed in order to analyse the requirements of the software maintenance process and to design a solution to this problem. It has been chosen as it provides some desirable and appropriate characteristics for the task. These characteristics yield benefits such as the provision of a visual approach to information representation (diagram), which is able to convey a considerable amount of information. Moreover, the implementation of the model can easily provide comprehensive analysis capabilities, which include traceability, consistency and completeness checks. As the model converts the form fields to object, relationship and attribute types, the implementation of the method can be obtained by generating a uniform set of services to create, retrieve and manipulate these types in a persistent object base. Thus the modelling of COMFORM followed by its implementation generate a more flexible manipulation of the form fields, i.e., object, relationship and attribute

7 types. Therefore, meta files can be generated containing different sets of customizable forms (object types (forms) with different relationship and attribute types) in a way that enables COMFORM to attend the needs of the maintenance of diverse software system profiles. References [1] K. H. Bennett, Automated support of software maintenance, Information and Software Technology, 33(1), 1991, pp [2] E.H.Bersoff,V.D.Henderson,andS.G.Siegel, Software Configuration Management - An Investment in Product Integrity, Prentice-Hall, [3] G. Booch, Object-Oriented with Applications, The Benjamin/Cummings Publishing Company, Inc., [4] L.F.CapretzandM.A.M.Capretz, Object-Oriented Software: and, World Scientific, Singapore (in press), [5] M. A. M. Capretz and L. F. Capretz, The object-oriented paradigm for software evolution, in Proc. 18th Annual International Computer Software & Applications Conference (IEEE COMPSAC94), Taipei, Taiwan, Nov. 1994, IEEE Computer Society Press, pp [6] M. A. M. Capretz and M. Munro, COMFORM - a software maintenance method based on the software configuration management discipline, in Proc. of the Conference on Software -1992, Orlando, Florida, Nov. 1992, IEEE Computer Society Press, pp [7] M. A. M. Capretz and M. Munro, Software configuration management issues in the maintenance of existing systems, Journal of Software : Research and Practice, 6(1), 1994, pp [8] P. P.-S. Chen. The entity-relationship model - toward a unified view of data, ACM Transactions on Database Systems, 1(1), 1976, pp [9] C. Desclaux and M. Ribault, MACS: assistance capability for software a K.A.D.M.E., in Proceedings of the Conference on Software -1991, Sorrento, Italy, 1991, pp [10] C. Traina Jr., Data Model and Machine Dedicated to Engineering Applications, PhD thesis, University of São Paulo, IFQSC-USP, São Carlos-SP, Brazil, (in Portuguese), Dec [11] H. Yang, The supporting environment for a reverse engineering system - the maintainer s assistant, in Proceedings of the Conference on Software -1991, Sorrento, Italy, 1991, pp

An Approach to Software Component Specification

An Approach to Software Component Specification Page 1 of 5 An Approach to Software Component Specification Jun Han Peninsula School of Computing and Information Technology Monash University, Melbourne, Australia Abstract. Current models for software

More information

Certification Authorities Software Team (CAST) Position Paper CAST-25

Certification Authorities Software Team (CAST) Position Paper CAST-25 Certification Authorities Software Team (CAST) Position Paper CAST-25 CONSIDERATIONS WHEN USING A QUALIFIABLE DEVELOPMENT ENVIRONMENT (QDE) IN CERTIFICATION PROJECTS COMPLETED SEPTEMBER 2005 (Rev 0) NOTE:

More information

UML-Based Conceptual Modeling of Pattern-Bases

UML-Based Conceptual Modeling of Pattern-Bases UML-Based Conceptual Modeling of Pattern-Bases Stefano Rizzi DEIS - University of Bologna Viale Risorgimento, 2 40136 Bologna - Italy srizzi@deis.unibo.it Abstract. The concept of pattern, meant as an

More information

Meta Architecting: Towered a New Generation of Architecture Description Languages

Meta Architecting: Towered a New Generation of Architecture Description Languages Journal of Computer Science 1 (4): 454-460, 2005 ISSN 1549-3636 Science Publications, 2005 Meta Architecting: Towered a New Generation of Architecture Description Languages Adel Smeda, Tahar Khammaci and

More information

European Conference on Quality and Methodology in Official Statistics (Q2008), 8-11, July, 2008, Rome - Italy

European Conference on Quality and Methodology in Official Statistics (Q2008), 8-11, July, 2008, Rome - Italy European Conference on Quality and Methodology in Official Statistics (Q2008), 8-11, July, 2008, Rome - Italy Metadata Life Cycle Statistics Portugal Isabel Morgado Methodology and Information Systems

More information

System Design and Modular Programming

System Design and Modular Programming CS3 Programming Methodology Lecture Note D1, 2 November 2000 System Design and Modular Programming System design involves meeting competing requirements and satisfying constraints on the system and the

More information

Use-Case Driven Domain Analysis for Milk Production Information Systems

Use-Case Driven Domain Analysis for Milk Production Information Systems Use-Case Driven Domain Analysis for Milk Production Information Systems Andrea Carla Alves Borim a, Antônio Mauro Saraiva b and Carlos Alberto Ramos Pinto c a Faculdade Comunitária de Campinas Anhanguera

More information

CS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS

CS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS 1. Explain iterative waterfall and spiral model for software life cycle and various activities

More information

The Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements

The Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements Journal of Software Engineering and Applications, 2016, 9, 112-127 Published Online April 2016 in SciRes. http://www.scirp.org/journal/jsea http://dx.doi.org/10.4236/jsea.2016.94010 The Analysis and Proposed

More information

Statistical Testing of Software Based on a Usage Model

Statistical Testing of Software Based on a Usage Model SOFTWARE PRACTICE AND EXPERIENCE, VOL. 25(1), 97 108 (JANUARY 1995) Statistical Testing of Software Based on a Usage Model gwendolyn h. walton, j. h. poore and carmen j. trammell Department of Computer

More information

OpenChain Specification Version 1.2 pc6 (DRAFT) [With Edit Markups Turned Off]

OpenChain Specification Version 1.2 pc6 (DRAFT) [With Edit Markups Turned Off] OpenChain Specification Version 1.2 pc6 (DRAFT) [With Edit Markups Turned Off] DRAFT: This is the near final draft of the 1.2 version of the OpenChain Specification. We have recently completed the final

More information

A Model Transformation from Misuse Cases to Secure Tropos

A Model Transformation from Misuse Cases to Secure Tropos A Model Transformation from Misuse Cases to Secure Tropos Naved Ahmed 1, Raimundas Matulevičius 1, and Haralambos Mouratidis 2 1 Institute of Computer Science, University of Tartu, Estonia {naved,rma}@ut.ee

More information

Introducing MESSIA: A Methodology of Developing Software Architectures Supporting Implementation Independence

Introducing MESSIA: A Methodology of Developing Software Architectures Supporting Implementation Independence Introducing MESSIA: A Methodology of Developing Software Architectures Supporting Implementation Independence Ratko Orlandic Department of Computer Science and Applied Math Illinois Institute of Technology

More information

E-R Model. Hi! Here in this lecture we are going to discuss about the E-R Model.

E-R Model. Hi! Here in this lecture we are going to discuss about the E-R Model. E-R Model Hi! Here in this lecture we are going to discuss about the E-R Model. What is Entity-Relationship Model? The entity-relationship model is useful because, as we will soon see, it facilitates communication

More information

One-Point Geometric Crossover

One-Point Geometric Crossover One-Point Geometric Crossover Alberto Moraglio School of Computing and Center for Reasoning, University of Kent, Canterbury, UK A.Moraglio@kent.ac.uk Abstract. Uniform crossover for binary strings has

More information

Chapter 2 Overview of the Design Methodology

Chapter 2 Overview of the Design Methodology Chapter 2 Overview of the Design Methodology This chapter presents an overview of the design methodology which is developed in this thesis, by identifying global abstraction levels at which a distributed

More information

Style-specific techniques to design product-line architectures

Style-specific techniques to design product-line architectures Style-specific techniques to design product-line architectures Philippe Lalanda Thomson-CSF Corporate Research Laboratory Phone: 33 1 69 33 92 90 Email: lalanda@thomson-lcr.fr Domaine de Corbeville 91404

More information

A Tutorial on Agent Based Software Engineering

A Tutorial on Agent Based Software Engineering A tutorial report for SENG 609.22 Agent Based Software Engineering Course Instructor: Dr. Behrouz H. Far A Tutorial on Agent Based Software Engineering Qun Zhou December, 2002 Abstract Agent oriented software

More information

Software Architectures

Software Architectures Software Architectures Richard N. Taylor Information and Computer Science University of California, Irvine Irvine, California 92697-3425 taylor@ics.uci.edu http://www.ics.uci.edu/~taylor +1-949-824-6429

More information

Chapter 8: Enhanced ER Model

Chapter 8: Enhanced ER Model Chapter 8: Enhanced ER Model Subclasses, Superclasses, and Inheritance Specialization and Generalization Constraints and Characteristics of Specialization and Generalization Hierarchies Modeling of UNION

More information

Software Engineering: Integration Requirements

Software Engineering: Integration Requirements Software Engineering: Integration Requirements AYAZ ISAZADEH Department of Computer Science Tabriz University Tabriz, IRAN Abstract: - This paper presents a discussion of software integration requirements,

More information

Comparative analyses for the performance of Rational Rose and Visio in software engineering teaching

Comparative analyses for the performance of Rational Rose and Visio in software engineering teaching Journal of Physics: Conference Series PAPER OPEN ACCESS Comparative analyses for the performance of Rational Rose and Visio in software engineering teaching To cite this article: Zhaojun Yu and Zhan Xiong

More information

Pattern-Based Architectural Design Process Model

Pattern-Based Architectural Design Process Model Pattern-Based Architectural Design Process Model N. Lévy, F. Losavio Abstract: The identification of quality requirements is crucial to develop modern software systems, especially when their underlying

More information

AN ONTOLOGICAL EVALUATION OF JACKSON'S SYSTEM DEVELOPMENT MODEL. Fiona Rohde. Department of Commerce The University of Queensland, 4072.

AN ONTOLOGICAL EVALUATION OF JACKSON'S SYSTEM DEVELOPMENT MODEL. Fiona Rohde. Department of Commerce The University of Queensland, 4072. AN ONTOLOGICAL EVALUATION OF JACKSON'S SYSTEM DEVELOPMENT MODEL Fiona Rohde Department of Commerce The University of Queensland, 4072. Australia ABSTRACT Within the discipline of information systems, numerous

More information

Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach

Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Developing Software Applications Using Middleware Infrastructure: Role Based and Coordination Component Framework Approach Ninat Wanapan and Somnuk Keretho Department of Computer Engineering, Kasetsart

More information

The architecture of Eiffel software 3.1 OVERVIEW classes clusters systems

The architecture of Eiffel software 3.1 OVERVIEW classes clusters systems 3 Draft 5.02.00-0, 15 August 2005 (Santa Barbara). Extracted from ongoing work on future third edition of Eiffel: The Language. Copyright Bertrand Meyer 1986-2005. Access restricted to purchasers of the

More information

Łabiak G., Miczulski P. (IIE, UZ, Zielona Góra, Poland)

Łabiak G., Miczulski P. (IIE, UZ, Zielona Góra, Poland) UML STATECHARTS AND PETRI NETS MODEL COMPARIS FOR SYSTEM LEVEL MODELLING Łabiak G., Miczulski P. (IIE, UZ, Zielona Góra, Poland) The system level modelling can be carried out with using some miscellaneous

More information

Fundamentals of Design, Implementation, and Management Tenth Edition

Fundamentals of Design, Implementation, and Management Tenth Edition Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition Chapter 3 Data Models Database Systems, 10th Edition 1 Objectives In this chapter, you will learn: About data modeling

More information

Requirements Engineering for Enterprise Systems

Requirements Engineering for Enterprise Systems Association for Information Systems AIS Electronic Library (AISeL) AMCIS 2001 Proceedings Americas Conference on Information Systems (AMCIS) December 2001 Requirements Engineering for Enterprise Systems

More information

Web Services Annotation and Reasoning

Web Services Annotation and Reasoning Web Services Annotation and Reasoning, W3C Workshop on Frameworks for Semantics in Web Services Web Services Annotation and Reasoning Peter Graubmann, Evelyn Pfeuffer, Mikhail Roshchin Siemens AG, Corporate

More information

ISO/IEC/ IEEE INTERNATIONAL STANDARD. Systems and software engineering Architecture description

ISO/IEC/ IEEE INTERNATIONAL STANDARD. Systems and software engineering Architecture description INTERNATIONAL STANDARD ISO/IEC/ IEEE 42010 First edition 2011-12-01 Systems and software engineering Architecture description Ingénierie des systèmes et des logiciels Description de l'architecture Reference

More information

A Study on Website Quality Models

A Study on Website Quality Models International Journal of Scientific and Research Publications, Volume 4, Issue 12, December 2014 1 A Study on Website Quality Models R.Anusha Department of Information Systems Management, M.O.P Vaishnav

More information

Guiding System Modelers in Multi View Environments: A Domain Engineering Approach

Guiding System Modelers in Multi View Environments: A Domain Engineering Approach Guiding System Modelers in Multi View Environments: A Domain Engineering Approach Arnon Sturm Department of Information Systems Engineering Ben-Gurion University of the Negev, Beer Sheva 84105, Israel

More information

Ch 4: Requirements Engineering. What are requirements?

Ch 4: Requirements Engineering. What are requirements? Ch 4: Engineering What are? Functional and non-functional The software document specification engineering processes elicitation and analysis validation management The descriptions of what the system should

More information

Software Development Chapter 1

Software Development Chapter 1 Software Development Chapter 1 1. Introduction Software Applications are increasingly used to tackle problems that concern everyday life : Automatic Bank tellers Airline reservation systems Air traffic

More information

ISO INTERNATIONAL STANDARD. Information and documentation Managing metadata for records Part 2: Conceptual and implementation issues

ISO INTERNATIONAL STANDARD. Information and documentation Managing metadata for records Part 2: Conceptual and implementation issues INTERNATIONAL STANDARD ISO 23081-2 First edition 2009-07-01 Information and documentation Managing metadata for records Part 2: Conceptual and implementation issues Information et documentation Gestion

More information

Functional Modeling with Data Flow Diagrams

Functional Modeling with Data Flow Diagrams Functional Modeling with Data Flow Diagrams Amasi Elbakush 5771668 Teaching Assistant : Daniel Alami Utrecht University 1 Introduction Data Flow Diagrams (DFDs) are a visual representation of the flow

More information

Ontology based Model and Procedure Creation for Topic Analysis in Chinese Language

Ontology based Model and Procedure Creation for Topic Analysis in Chinese Language Ontology based Model and Procedure Creation for Topic Analysis in Chinese Language Dong Han and Kilian Stoffel Information Management Institute, University of Neuchâtel Pierre-à-Mazel 7, CH-2000 Neuchâtel,

More information

VO Software Engineering

VO Software Engineering Administrative Issues Univ.Prof. Dr. Peter Auer Chair for Information Technology Email: auer@unileoben.ac.at Lecture Thursday 10:15 11:45 Project Lab Montag 16:00 19:00 Literature Helmut Balzert, Lehrbuch

More information

SOFTWARE QUALITY. MADE IN GERMANY.

SOFTWARE QUALITY. MADE IN GERMANY. UPCOMING IMPACT OF THE SECOND EDITION OF THE ISO 26262 MGIGroup, 11.07.2017 SOFTWARE QUALITY. MADE IN GERMANY. SOLUTIONS FOR INTEGRATED QUALITY ASSURANCE OF EMBEDDED SOFTWARE MOTIVATION Release ISO 26262:2011

More information

POAD Book: Chapter 4: Design Patterns as Components Chapter 5: Visual Design Models

POAD Book: Chapter 4: Design Patterns as Components Chapter 5: Visual Design Models POAD Book: Chapter 4: Design Patterns as Components Chapter 5: Visual Design Models Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU Outline Chapter 4: Design Patterns

More information

Fausto Giunchiglia and Mattia Fumagalli

Fausto Giunchiglia and Mattia Fumagalli DISI - Via Sommarive 5-38123 Povo - Trento (Italy) http://disi.unitn.it FROM ER MODELS TO THE ENTITY MODEL Fausto Giunchiglia and Mattia Fumagalli Date (2014-October) Technical Report # DISI-14-014 From

More information

DATA MODELS FOR SEMISTRUCTURED DATA

DATA MODELS FOR SEMISTRUCTURED DATA Chapter 2 DATA MODELS FOR SEMISTRUCTURED DATA Traditionally, real world semantics are captured in a data model, and mapped to the database schema. The real world semantics are modeled as constraints and

More information

Introduction to Software Engineering

Introduction to Software Engineering Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,

More information

ANALYTICS DRIVEN DATA MODEL IN DIGITAL SERVICES

ANALYTICS DRIVEN DATA MODEL IN DIGITAL SERVICES ANALYTICS DRIVEN DATA MODEL IN DIGITAL SERVICES Ng Wai Keat 1 1 Axiata Analytics Centre, Axiata Group, Malaysia *Corresponding E-mail : waikeat.ng@axiata.com Abstract Data models are generally applied

More information

Efficient Prefix Computation on Faulty Hypercubes

Efficient Prefix Computation on Faulty Hypercubes JOURNAL OF INFORMATION SCIENCE AND ENGINEERING 17, 1-21 (21) Efficient Prefix Computation on Faulty Hypercubes YU-WEI CHEN AND KUO-LIANG CHUNG + Department of Computer and Information Science Aletheia

More information

Automated Improvement for Component Reuse

Automated Improvement for Component Reuse Automated Improvement for Component Reuse Muthu Ramachandran School of Computing The Headingley Campus Leeds Metropolitan University LEEDS, UK m.ramachandran@leedsmet.ac.uk Abstract Software component

More information

SOME TYPES AND USES OF DATA MODELS

SOME TYPES AND USES OF DATA MODELS 3 SOME TYPES AND USES OF DATA MODELS CHAPTER OUTLINE 3.1 Different Types of Data Models 23 3.1.1 Physical Data Model 24 3.1.2 Logical Data Model 24 3.1.3 Conceptual Data Model 25 3.1.4 Canonical Data Model

More information

Bipartite Graph Partitioning and Content-based Image Clustering

Bipartite Graph Partitioning and Content-based Image Clustering Bipartite Graph Partitioning and Content-based Image Clustering Guoping Qiu School of Computer Science The University of Nottingham qiu @ cs.nott.ac.uk Abstract This paper presents a method to model the

More information

Chapter 8 Visualization and Optimization

Chapter 8 Visualization and Optimization Chapter 8 Visualization and Optimization Recommended reference books: [1] Edited by R. S. Gallagher: Computer Visualization, Graphics Techniques for Scientific and Engineering Analysis by CRC, 1994 [2]

More information

CoE CENTRE of EXCELLENCE ON DATA WAREHOUSING

CoE CENTRE of EXCELLENCE ON DATA WAREHOUSING in partnership with Overall handbook to set up a S-DWH CoE: Deliverable: 4.6 Version: 3.1 Date: 3 November 2017 CoE CENTRE of EXCELLENCE ON DATA WAREHOUSING Handbook to set up a S-DWH 1 version 2.1 / 4

More information

is easing the creation of new ontologies by promoting the reuse of existing ones and automating, as much as possible, the entire ontology

is easing the creation of new ontologies by promoting the reuse of existing ones and automating, as much as possible, the entire ontology Preface The idea of improving software quality through reuse is not new. After all, if software works and is needed, just reuse it. What is new and evolving is the idea of relative validation through testing

More information

RIGOROUSLY AUTOMATING TRANSFORMATIONS OF UML BEHAVIOR MODELS

RIGOROUSLY AUTOMATING TRANSFORMATIONS OF UML BEHAVIOR MODELS RIGOROUSLY AUTOMATING TRANSFORMATIONS OF UML BEHAVIOR MODELS Jon Whittle 1, João Araújo 2, Ambrosio Toval 3, and Jose Luis Fernández Alemán 3 1 QSS / NASA Ames Research Center, M/S 269-2, Moffett Field,

More information

Solved Question Paper June 2017

Solved Question Paper June 2017 Solved Question Paper June 2017 1.a) What are the benefits of Object Oriented Methodology in real life applications? Briefly explain each element of the state diagram with respect to dynamic modeling.

More information

Using Clusters on the Vivisimo Web Search Engine

Using Clusters on the Vivisimo Web Search Engine Using Clusters on the Vivisimo Web Search Engine Sherry Koshman and Amanda Spink School of Information Sciences University of Pittsburgh 135 N. Bellefield Ave., Pittsburgh, PA 15237 skoshman@sis.pitt.edu,

More information

An Archiving System for Managing Evolution in the Data Web

An Archiving System for Managing Evolution in the Data Web An Archiving System for Managing Evolution in the Web Marios Meimaris *, George Papastefanatos and Christos Pateritsas * Institute for the Management of Information Systems, Research Center Athena, Greece

More information

0. Database Systems 1.1 Introduction to DBMS Information is one of the most valuable resources in this information age! How do we effectively and efficiently manage this information? - How does Wal-Mart

More information

Recommended Practice for Software Requirements Specifications (IEEE)

Recommended Practice for Software Requirements Specifications (IEEE) Recommended Practice for Software Requirements Specifications (IEEE) Author: John Doe Revision: 29/Dec/11 Abstract: The content and qualities of a good software requirements specification (SRS) are described

More information

Transformation of analysis model to design model

Transformation of analysis model to design model 2010 International Conference on E-business, Management and Economics IPEDR vol.3 (2011) (2011) IACSIT Press, Hong Kong Transformation of analysis model to design model Lalji Prasad Truba College of Engineering

More information

Final Project Report

Final Project Report 16.04.02 Final Project Report Document information Project Title HP Tool Repository of SESAR standard HP methods and tools Project Number 16.04.02 Project Manager DFS Deliverable Name 16.04.02 Final Project

More information

Implementing Trusted Digital Repositories

Implementing Trusted Digital Repositories Implementing Trusted Digital Repositories Reagan W. Moore, Arcot Rajasekar, Richard Marciano San Diego Supercomputer Center 9500 Gilman Drive, La Jolla, CA 92093-0505 {moore, sekar, marciano}@sdsc.edu

More information

Why Consider Implementation-Level Decisions in Software Architectures?

Why Consider Implementation-Level Decisions in Software Architectures? 1. Abstract Why Consider Implementation-Level Decisions in Software Architectures? Nikunj Mehta Nenad Medvidović Marija Rakić {mehta, neno, marija}@sunset.usc.edu Department of Computer Science University

More information

Configuration Management for Component-based Systems

Configuration Management for Component-based Systems Configuration Management for Component-based Systems Magnus Larsson Ivica Crnkovic Development and Research Department of Computer Science ABB Automation Products AB Mälardalen University 721 59 Västerås,

More information

Hierarchical Online Mining for Associative Rules

Hierarchical Online Mining for Associative Rules Hierarchical Online Mining for Associative Rules Naresh Jotwani Dhirubhai Ambani Institute of Information & Communication Technology Gandhinagar 382009 INDIA naresh_jotwani@da-iict.org Abstract Mining

More information

Digital Archives: Extending the 5S model through NESTOR

Digital Archives: Extending the 5S model through NESTOR Digital Archives: Extending the 5S model through NESTOR Nicola Ferro and Gianmaria Silvello Department of Information Engineering, University of Padua, Italy {ferro, silvello}@dei.unipd.it Abstract. Archives

More information

Module Outline. What is Object-Oriented? Some Possible Definitions. Why Object-oriented? Fundamentals of Object Orientation

Module Outline. What is Object-Oriented? Some Possible Definitions. Why Object-oriented? Fundamentals of Object Orientation Module Outline Fundamentals of Object Positioning Object Oriented Analysis Fundamentals of Object 1. Encapsulation 2. Abstraction 3. Inheritance 4. Polymorphism The need of Modeling Unified modeling language

More information

The Relationships between Domain Specific and General- Purpose Languages

The Relationships between Domain Specific and General- Purpose Languages The Relationships between Domain Specific and General- Purpose Languages Oded Kramer and Arnon Sturm Department of Information Systems Engineering, Ben-Gurion University of the Negev Beer-Sheva, Israel

More information

ITERATIVE MULTI-LEVEL MODELLING - A METHODOLOGY FOR COMPUTER SYSTEM DESIGN. F. W. Zurcher B. Randell

ITERATIVE MULTI-LEVEL MODELLING - A METHODOLOGY FOR COMPUTER SYSTEM DESIGN. F. W. Zurcher B. Randell ITERATIVE MULTI-LEVEL MODELLING - A METHODOLOGY FOR COMPUTER SYSTEM DESIGN F. W. Zurcher B. Randell Thomas J. Watson Research Center Yorktown Heights, New York Abstract: The paper presents a method of

More information

UML data models from an ORM perspective: Part 4

UML data models from an ORM perspective: Part 4 data models from an ORM perspective: Part 4 by Dr. Terry Halpin Director of Database Strategy, Visio Corporation This article first appeared in the August 1998 issue of the Journal of Conceptual Modeling,

More information

A Design Rationale Representation for Model-Based Designs in Software Engineering

A Design Rationale Representation for Model-Based Designs in Software Engineering A Design Rationale Representation for Model-Based Designs in Software Engineering Adriana Pereira de Medeiros, Daniel Schwabe, and Bruno Feijó Dept. of Informatics, PUC-Rio, Rua Marquês de São Vicente

More information

DATABASE SYSTEMS CHAPTER 2 DATA MODELS 1 DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT

DATABASE SYSTEMS CHAPTER 2 DATA MODELS 1 DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT DATABASE SYSTEMS DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT CHAPTER DATA MODELS 1 Coronel & Crockett 978184480731) In this chapter, you will learn: Why data models

More information

An Efficient Staging Algorithm for Binding-Time Analysis

An Efficient Staging Algorithm for Binding-Time Analysis An Efficient Staging Algorithm for Binding-Time Analysis Takuma Murakami 1, Zhenjiang Hu 1,2, Kazuhiko Kakehi 1, and Masato Takeichi 1 1 Department of Mathematical Informatics, Graduate School of Information

More information

Introduction. Chapter 1. What Is Visual Modeling? The Triangle for Success. The Role of Notation. History of the UML. The Role of Process

Introduction. Chapter 1. What Is Visual Modeling? The Triangle for Success. The Role of Notation. History of the UML. The Role of Process Quatrani_Ch.01.fm Page 1 Friday, October 27, 2000 9:02 AM Chapter 1 Introduction What Is Visual Modeling? The Triangle for Success The Role of Notation History of the UML The Role of Process What Is Iterative

More information

Semantic Web in a Constrained Environment

Semantic Web in a Constrained Environment Semantic Web in a Constrained Environment Laurens Rietveld and Stefan Schlobach Department of Computer Science, VU University Amsterdam, The Netherlands {laurens.rietveld,k.s.schlobach}@vu.nl Abstract.

More information

Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards

Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards Fundamentals to Creating Architectures using ISO/IEC/IEEE Standards What to Architect? How to Architect? IEEE Goals and Objectives Chartered by IEEE Software Engineering Standards Committee to: Define

More information

Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary

Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary December 17, 2009 Version History Version Publication Date Author Description

More information

Software Architecture Recovery based on Dynamic Analysis

Software Architecture Recovery based on Dynamic Analysis Software Architecture Recovery based on Dynamic Analysis Aline Vasconcelos 1,2, Cláudia Werner 1 1 COPPE/UFRJ System Engineering and Computer Science Program P.O. Box 68511 ZIP 21945-970 Rio de Janeiro

More information

SOFTWARE ENGINEERING UML FUNDAMENTALS. Saulius Ragaišis.

SOFTWARE ENGINEERING UML FUNDAMENTALS. Saulius Ragaišis. SOFTWARE ENGINEERING UML FUNDAMENTALS Saulius Ragaišis saulius.ragaisis@mif.vu.lt Information source Slides are prepared on the basis of Bernd Oestereich, Developing Software with UML: Object- Oriented

More information

Development of an Ontology-Based Portal for Digital Archive Services

Development of an Ontology-Based Portal for Digital Archive Services Development of an Ontology-Based Portal for Digital Archive Services Ching-Long Yeh Department of Computer Science and Engineering Tatung University 40 Chungshan N. Rd. 3rd Sec. Taipei, 104, Taiwan chingyeh@cse.ttu.edu.tw

More information

Circular Logic. Robotic Tram Data Collection System Software Configuration Management Plan Version 2.3 4/8/ Circular Logic

Circular Logic. Robotic Tram Data Collection System Software Configuration Management Plan Version 2.3 4/8/ Circular Logic Circular Logic Robotic Tram Data Collection System Software Configuration Management Plan Version 2.3 4/8/2008 2008 Circular Logic Document Control Approval The Guidance Team and the customer will approve

More information

Change Detection System for the Maintenance of Automated Testing

Change Detection System for the Maintenance of Automated Testing Change Detection System for the Maintenance of Automated Testing Miroslav Bures To cite this version: Miroslav Bures. Change Detection System for the Maintenance of Automated Testing. Mercedes G. Merayo;

More information

An Architecture for Semantic Enterprise Application Integration Standards

An Architecture for Semantic Enterprise Application Integration Standards An Architecture for Semantic Enterprise Application Integration Standards Nenad Anicic 1, 2, Nenad Ivezic 1, Albert Jones 1 1 National Institute of Standards and Technology, 100 Bureau Drive Gaithersburg,

More information

Requirements Engineering. Establishing what the customer requires from a software system. Requirements Engineering. What is a Requirement?

Requirements Engineering. Establishing what the customer requires from a software system. Requirements Engineering. What is a Requirement? Engineering Establishing what the customer requires from a software system Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 5 and 6 Slide 1 Engineering

More information

SHOTGUN SURGERY DESIGN FLAW DETECTION. A CASE-STUDY

SHOTGUN SURGERY DESIGN FLAW DETECTION. A CASE-STUDY STUDIA UNIV. BABEŞ BOLYAI, INFORMATICA, Volume LVIII, Number 4, 2013 SHOTGUN SURGERY DESIGN FLAW DETECTION. A CASE-STUDY CAMELIA ŞERBAN Abstract. Due to the complexity of object oriented design, its assessment

More information

Telecom Italia response. to the BEREC public consultation on

Telecom Italia response. to the BEREC public consultation on Telecom Italia response to the BEREC public consultation on Guidelines on Net Neutrality and Transparency: Best practise and recommended approaches - BOR (11) 44 (2 November 2011) Telecom Italia response

More information

Unified feature based integration of design and process planning

Unified feature based integration of design and process planning Unified feature based integration of design and process planning G. Chen 1, Y.-S. Ma 1*, G. Thimm 2 and S.-H. Tang 2 1 CAD/CAM Lab, School of MPE, Nanyang Technological University, Singapore 639798 2 Design

More information

A l Ain University Of Science and Technology

A l Ain University Of Science and Technology A l Ain University Of Science and Technology 4 Handout(4) Database Management Principles and Applications The Entity Relationship (ER) Model http://alainauh.webs.com/ 1 In this chapter, you will learn:

More information

A COMPARATIVE ANALYSIS TO VALIDATE THE BENIFITS OF FORMAL VERSUS INFORMAL SOFTWARE MODEL TRANSFORMATION

A COMPARATIVE ANALYSIS TO VALIDATE THE BENIFITS OF FORMAL VERSUS INFORMAL SOFTWARE MODEL TRANSFORMATION A COMPARATIVE ANALYSIS TO VALIDATE THE BENIFITS OF FORMAL VERSUS INFORMAL SOFTWARE MODEL TRANSFORMATION Kaden Daley and Emanuel S. Grant University of North Dakota Department of Computer Science Grand

More information

A UML-based Process Meta-Model Integrating a Rigorous Process Patterns Definition

A UML-based Process Meta-Model Integrating a Rigorous Process Patterns Definition A UML-based Process Meta-Model Integrating a Rigorous Process Patterns Definition Hanh Nhi Tran, Bernard Coulette, Bich Thuy Dong 2 University of Toulouse 2 -GRIMM 5 allées A. Machado F-3058 Toulouse,

More information

PRINCIPLES AND FUNCTIONAL REQUIREMENTS

PRINCIPLES AND FUNCTIONAL REQUIREMENTS INTERNATIONAL COUNCIL ON ARCHIVES PRINCIPLES AND FUNCTIONAL REQUIREMENTS FOR RECORDS IN ELECTRONIC OFFICE ENVIRONMENTS RECORDKEEPING REQUIREMENTS FOR BUSINESS SYSTEMS THAT DO NOT MANAGE RECORDS OCTOBER

More information

A Model-Based Reference Workflow for the Development of Safety-Related Software

A Model-Based Reference Workflow for the Development of Safety-Related Software A Model-Based Reference Workflow for the Development of Safety-Related Software 2010-01-2338 Published 10/19/2010 Michael Beine dspace GmbH Dirk Fleischer dspace Inc. Copyright 2010 SAE International ABSTRACT

More information

Object Relational Mappings

Object Relational Mappings Object Relational Mappings First step to a formal approach Bachelor thesis Tom van den Broek January 30, 2007 Contents 1 Introduction 2 2 The two models 4 2.1 The object model.........................

More information

A Comparison of the Booch Method and Shlaer-Mellor OOA/RD

A Comparison of the Booch Method and Shlaer-Mellor OOA/RD A Comparison of the Booch Method and Shlaer-Mellor OOA/RD Stephen J. Mellor Project Technology, Inc. 7400 N. Oracle Rd., Suite 365 Tucson Arizona 85704 520 544-2881 http://www.projtech.com 2 May 1993 The

More information

Comparison of Simple Graphical Process Models

Comparison of Simple Graphical Process Models JIOS, VOL. 36, NO. 2 (2012) SUBMITTED 07/12; ACCEPTED 10/12 Comparison of Simple Graphical Process Models Katarina Tomičić-Pupek University of Zagreb Faculty of Organization and Informatics Varaždin Ivan

More information

International Journal of Advancements in Research & Technology, Volume 2, Issue5, May ISSN

International Journal of Advancements in Research & Technology, Volume 2, Issue5, May ISSN International Journal of Advancements in Research & Technology, Volume 2, Issue5, May-2013 194 A REVIEW ON OBJECT MODELLING METHODOLOGIES ROHIT SHARMA 1, Dr. VINODINI KATIYAR 2 1 Research Scholar, C.M.J.

More information

MIT Database Management Systems Lesson 01: Introduction

MIT Database Management Systems Lesson 01: Introduction MIT 22033 Database Management Systems Lesson 01: Introduction By S. Sabraz Nawaz Senior Lecturer in MIT, FMC, SEUSL Learning Outcomes At the end of the module the student will be able to: Describe the

More information

Design. Introduction

Design. Introduction Design Introduction a meaningful engineering representation of some software product that is to be built. can be traced to the customer's requirements. can be assessed for quality against predefined criteria.

More information

ISO TC46/SC11 Archives/records management

ISO TC46/SC11 Archives/records management ISO TC46/SC11 Archives/records management GUIDANCE FOR IMPLEMENTING DOCUMENTED INFORMATION CLAUSE USING PROCESSES AND CONTROLS OF ISO 30301:2011 Management system for records EXPLANATORY PAPER NOVEMBER

More information

ASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper)

ASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper) ASSURING DATA INTEROPERABILITY THROUGH THE USE OF FORMAL MODELS OF VISA PAYMENT MESSAGES (Category: Practice-Oriented Paper) Joseph Bugajski Visa International JBugajsk@visa.com Philippe De Smedt Visa

More information

Matching Models of Different Abstraction Levels: A Refinement Equivalence Approach

Matching Models of Different Abstraction Levels: A Refinement Equivalence Approach Matching Models of Different Abstraction Levels Chapter IV Matching Models of Different Abstraction Levels: A Refinement Equivalence Approach Pnina Soffer, Haifa University, Israel Iris Reinhartz-Berger,

More information