DOCSLIB.ORG

Comparative Study on Extended Entity Relationship and Unified Modeling Language

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Comparative Study on Extended Entity Relationship and Unified Modeling Language International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395 -0056 Volume: 02 Issue: 04 | July-2015 www.irjet.net p-ISSN: 2395-0072 COMPARATIVE STUDY ON EXTENDED ENTITY RELATIONSHIP AND UNIFIED MODELING LANGUAGE *1Mrs. Kavitha S., *2Ms. Nancy A., *1Assisant Professor, Department of Computer Science Auxilium College (Autonomous), Vellore, TamilNadu, India *2M.Phil Research Scholar, Department of Computer Science Auxilium College (Autonomous), Vellore, TamilNadu, India ---------------------------------------------------------------------***--------------------------------------------------------------------- Abstract - Entity Relationship modeling is the process to represent an object without knowing its properties, but of coming up with an abstract and conceptual in the relational model need to know its key attributes. representation of data. Entity Relationship diagrams Specialization ultimately model the databases. Entity Relationship Specialization Process of defining a set of model is generally better in relationship name and subclasses of an entity type. Defined on the basis of some participation representation than the Unified Modeling distinguishing characteristic of the entities in the super Language diagram. In Extended entity relationship class. Describing the relationship Super class/subclass or diagram is describing the data requirements for a new Class/subclass Super type/subtype or Type/subtype. information system in a direct and easy to understand Subclass can define: Specific attributes Specific graphical notation. Unified Modeling Language has a relationship types. Subclass can be subclass write more direct relation with object oriented analysis and design than one super class. to representation for the cardinality relationship compared with Entity Relationship diagrams. The fields Generalization are entities, attributes, relationship, cardinalities, Generalization Process of defining a more general identifiers to use the Extended Entity Relationship and entity type from given entity types reverse process of Unified Modeling Language diagrams with the specialization. Generalize into a single super class. Original representing notation. entity types are specialized subclasses. Entities in Key Words: Entity Relationship model, Extended entity generalization must all come from subclasses relationship (EER), Unified Modeling Language, object generalization is the reverse of the specialization process. oriented analysis and design. Several classes with common features are generalized into a super class; original classes become its subclasses. I. INTRODUCTION 1.1 Unified Modeling Language UML is a standard language for specifying, The Extended entity relationship (EER) model is a visualizing, constructing, and documenting the artifacts of conceptual (or semantic) data model, capable of software systems. UML stands for Unified Modeling describing the data requirements for a new information Language. UML is different from the other common system in a direct and easy to understand graphical programming languages like C++, Java, COBOL, etc.UML is notation. Data requirements for a database are described a pictorial language used to make software blue prints so in terms of a conceptual schema, using the EER model. EER UML can be described as a general purpose visual model of EER schemas are comparable to UML class modeling language to visualize, specify, construct and diagrams. Actually, what will be discussing is an extension document software system. of Peter Chen’s proposal (hence “extended” ER). These represent classes of objects (facts, things, people...) that 1.2 UML Class Diagram have properties in common and an autonomous existence. The EER model is very different from the relational model The class diagram is a static diagram. It in a number of ways; for example, in EER it is not possible represents the static view of an application. Class diagram © 2015, IRJET.NET- All Rights Reserved Page 390 International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395 -0056 Volume: 02 Issue: 04 | July-2015 www.irjet.net p-ISSN: 2395-0072 is not only used for visualizing, describing and of abstraction at which the developer operates, requiring documenting different aspects of a system but also for the developer to learn a new higher-level language that constructing executable code of the software application. may then be mapped into lower-level. The class diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It is also The experiment and two replications aimed at known as a structural diagram. comparing the support provided by ER and UML class diagrams during comprehension activities by focusing on 1.3 UML Object Diagram the single building blocks of the two notations. The results Object diagrams are derived from class diagrams reveal that UML class diagrams are generally more so object diagrams are dependent upon class diagrams. comprehensible than ER diagrams, even if the former has Object diagrams represent an instance of a class diagram. some weaknesses related to three building blocks. These The basic concepts are similar for class diagrams and findings suggest that a UML class diagram extension object diagrams. Object diagrams are used to render a set should be considered to overcome these weaknesses and of objects and their relationships as an instance. improve the comprehensibility of the notation. A data model is a set of concepts that can be used to describe II. Related work both the structure of and the operations on a database. The evaluation process of conceptual specifications developed using either Extended Entity- UML can be used to study mappings to different Relationship (EER) or Unified Modeling Language (UML) types of database systems. Introducing UML through a conceptual models. It provides a comprehensive comparison to the EER model, UML diagrams are used to framework for evaluating EER and UML conceptual teach different approaches for mapping conceptual schemas. Furthermore, it defines classes of metrics designs to the relational model. It cover object-oriented facilitating the evaluation process and leading to the and object-relational database systems, different features choice of the appropriate representation among several of UML are used over the same enterprise to understand schemas describing the same reality. Based on quality mapping alternatives for each model for object-oriented criteria proposed in the literature to select a subset of and object-relational database systems. In the relational criteria relevant to conceptual EER schema quality and object-relational models that require the development evaluation. Finally, this evaluation process to UML of code to maintain inverse relationships to address the schemas Following the development of framework, mapping techniques from the point of view. analyze a case study and provide evidence in the support of the usefulness of the framework. III. PREVIOUS IMPLEMENTATIONS The EER contains all concepts of ER. EER adds It created to design more accurate database more concepts like Specialization/Generalization, schemas reflect the data properties and constraints more Subclass/Super Class, Categories and Inheritance to get precisely. More complex requirements than traditional more accuracy than ER. UML includes a set of graphic applications. The Extended Entity-Relationship (EER) notation techniques to create visual models of Object- model is a conceptual (or semantic) data model, capable of oriented software intensive systems. Unified Modeling describing the data requirements for a new information Language is a standard for software development. EER system in a direct and easy to understand graphical Diagram on the other hand is used for database design. notation. Data requirements for a database are described in terms of a conceptual schema, using the EER model. EER Executable UML is fundamental approach to model EER schemata are comparable to UML class Model Driven Architecture a new way of writing diagrams. Actually, what we will be discussing is an specifications and developing applications, based on a extension of Peter Chen’s proposal (hence “extended” platform-independent model (PIM).In software ER).These represents classes of objects (facts, things, engineering, many industries used to build systems by people...) that have properties in common and an soldering wires together to form hard-wired programs. autonomous existence. Notion of object-orientation, an approach for structuring data and behavior together into classes and objects. Its moved from one language to another, Increased the level © 2015, IRJET.NET- All Rights Reserved Page 391 International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395 -0056 Volume: 02 Issue: 04 | July-2015 www.irjet.net p-ISSN: 2395-0072 Attributes are 14 UML diagram types to help you model this These describe the elementary properties of behavior. They can be divided into two main categories entities or relationships. An attribute associates with each structure diagrams and behavioral diagrams. instance of an entity (or relationship) a value belonging to a set known as the domain of the attribute. The domain 4.1 Class Diagram contains the admissible values for the attribute. Class diagrams are used UML diagram type. It is For example, Surname, Salary and Age are the main building block of any object oriented solution. It possible attributes of the Employee entity, while Date and shows the classes in
Load more

Recommended publications
  • Model Based Systems Engineering Approach to Autonomous Driving
    DEGREE PROJECT IN ELECTRICAL ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2018 Model Based Systems Engineering Approach to Autonomous Driving Application of SysML for trajectory planning of autonomous vehicle SARANGI VEERMANI LEKAMANI KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Author Sarangi Veeramani Lekamani [email protected] School of Electrical Engineering and Computer Science KTH Royal Institute of Technology Place for Project Sodertalje, Sweden AVL MTC AB Examiner Ingo Sander School of Electrical Engineering and Computer Science KTH Royal Institute of Technology Supervisor George Ungureanu School of Electrical Engineering and Computer Science KTH Royal Institute of Technology Industrial Supervisor Hakan Sahin AVL MTC AB Abstract Model Based Systems Engineering (MBSE) approach aims at implementing various processes of Systems Engineering (SE) through diagrams that provide different perspectives of the same underlying system. This approach provides a basis that helps develop a complex system in a systematic manner. Thus, this thesis aims at deriving a system model through this approach for the purpose of autonomous driving, specifically focusing on developing the subsystem responsible for generating a feasible trajectory for a miniature vehicle, called AutoCar, to enable it to move towards a goal. The report provides a background on MBSE and System Modeling Language (SysML) which is used for modelling the system. With this background, an MBSE framework for AutoCar is derived and the overall system design is explained. This report further explains the concepts involved in autonomous trajectory planning followed by an introduction to Robot Operating System (ROS) and its application for trajectory planning of the system. The report concludes with a detailed analysis on the benefits of using this approach for developing a system.
    [Show full text]
  • Information Technology and Software Development
    Course Title: Information Technology and Software Development NATIONAL OPEN UNIVERSITY OF NIGERIA SCHOOL OF SCIENCE AND TECHNOLOGY COURSE CODE: CIT 703 COURSE TITLE: Information Technology and Software Development National Open University of Nigeria, Victoria Island, Lagos Page 1 Course Title: Information Technology and Software Development Course Code Course Title Information Technology and Software Development Course Developer/Writer Eze, Festus Chux Department of Computer Science Ebonyi State University Abakaliki Course Editor Programme Leader Course Coordinator National Open University of Nigeria, Victoria Island, Lagos Page 2 Course Title: Information Technology and Software Development Introduction Information Technology and Software Development is a three credit load course for all the students offering Post Graduate Diploma (PGD) in Computer Science, Information Technology and other allied courses. Software Development is a major branch in computing and information Technology. A software development professional oversees the processes of software development, the management of software development project, the maintenance of the installed software in an organisation. For sometime the field has been dominated with what is the definitive process of software development. Furthermore there has been the running battle between professionals and managers on who should control a software development project. There is an attempt to classify it as any other project that an organisation handles hence anybody could manage it. Whereas others see it as a highly professional issue that requires high precision in design, management and implementation. However, software development is all involving. It involves the user (client) whose interest is paramount. The developing organisation and her professionals ( team)are of great importance. Therefore a successful exercise can only take place when all these variegated interests are harmonised.
    [Show full text]
  • APECS: Polychrony Based End-To-End Embedded System Design and Code Synthesis
    APECS: Polychrony based End-to-End Embedded System Design and Code Synthesis Matthew E. Anderson Dissertation submitted to the faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Engineering Sandeep K. Shukla, Chair Lamine Mili Alireza Haghighat Chao Wang Yi Deng April 3, 2015 Blacksburg, Virginia Keywords: AADL, CPS, Model-based code synthesis, correct-by-construction code synthesis, Polychrony, code generators, OSATE, Ocarina Copyright 2015, Matthew E. Anderson APECS: Polychrony based End-to-End Embedded System Design and Code Synthesis Matthew E. Anderson (ABSTRACT) The development of high integrity embedded systems remains an arduous and error-prone task, despite the efforts by researchers in inventing tools and techniques for design automa- tion. Much of the problem arises from the fact that the semantics of the modeling languages for the various tools, are often distinct, and the semantics gaps are often filled manually through the engineer's understanding of one model or an abstraction. This provides an op- portunity for bugs to creep in, other than standardising software engineering errors germane to such complex system engineering. Since embedded systems applications such as avionics, automotive, or industrial automation are safety critical, it is very important to invent tools, and methodologies for safe and reliable system design. Much of the tools, and techniques deal with either the design of embedded platforms (hardware, networking, firmware etc), and software stack separately. The problem of the semantic gap between these two, as well as between models of computation used to capture semantics must be solved in order to design safer embedded systems.
    [Show full text]
  • Examples of UML Diagrams
    UML Diagrams Examples Examples by Technology or Application Domain Online shopping UML diagrams Ticket vending machine UML diagrams Bank ATM UML diagrams Hospital management UML diagrams Digital imaging and communications in medicine (DICOM) UML diagrams Java technology UML diagrams Application development for Android UML diagrams Software licensing and protection using SafeNet Sentinel HASP security solution Examples by Types of Diagrams Activity diagram examples Class diagram examples Communication diagram examples Component diagram examples Composite structure diagram examples Deployment diagram examples Information flow diagram example Interaction overview diagram examples Object diagram example Package diagram examples Profile diagram examples http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 1 of 33 Sequence diagram examples State machine diagram examples Timing diagram examples Use case diagram examples Use Case Diagrams Business Use Case Diagrams Airport check-in and security screening business model Restaurant business model System Use Case Diagrams Ticket vending machine http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 2 of 33 Bank ATM UML use case diagrams examples Point of Sales (POS) terminal e-Library online public access catalog (OPAC) http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 3 of 33 Online shopping use case diagrams Credit card processing system Website administration http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 4 of 33 Hospital
    [Show full text]
  • Tram - Trng - Modeling - UML Startup - All.Pages 2 1991 Booch 91
    UML Start-Up Training UB1 Index History Overview Diagrams Use Case Diagram Sequence Diagram Activity Diagram Class Diagram Composite Structure Diagram UML State Machine Diagram This training course is designed with the intention to teach UML in not Package Diagram longer than a day. Yes UML is a complicated language with a lot of diagrams, model elements, a complex syntax and semantic; and most people claim that it takes a long time to learn that language. But: if we concentrate our efforts to the most important part of the language you will be able to become familiar with it in a day. And: use it frequently, then you’ll get the less important things by use and by reading a good book: the standard (visit the web pages from OMG and you’ll manage to download the standard, it’s free of charge). History The “OO tower” of Babel In the early Nineties there was a vast amount of competing object oriented modeling approaches together with corresponding kinds of diagrams and CASE environments which, sometimes more and sometimes less, differ from each other. Examples: Object-Oriented Analysis (OOA): Coad-Yourdon 1991 Object-Oriented Design (OOD): Booch 1991 Object Modeling Technique (OMT): Rumbaugh 1991 OO Software Engineering (OOSE): Jacobson 1992 Fusion: Coleman 1994 The Idea: Unified Modeling Language The idea of Grady Booch: A number of OO modeling dialects is replaced by a standardized language in order to bury unnecessary ditch (and religious) wars in the OO environment unite advantages of different modeling approaches relieve potential users of being spoilt for choice provide for the preconditions for data exchange between OO tools enable close integration of OO tools reduce dependencies of users of one supplier release tool manufacturers of the support of many approaches.
    [Show full text]
  • Borland Together 2008 Borland Together UML 2.1 Guide Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707
    Borland Together 2008 Borland Together UML 2.1 Guide Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707 Copyright 2009-2010 Micro Focus (IP) Limited. All Rights Reserved.Together contains derivative works of Borland Software Corporation, Copyright 2008-2010 Borland Software Corporation (a Micro Focus company). MICRO FOCUS and the Micro Focus logo, among others, are trademarks or registered trademarks of Micro Focus (IP) Limited or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. BORLAND, the Borland logo and Together are trademarks or registered trademarks of Borland Software Corporation or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. All other marks are the property of their respective owners. ii Contents Concepts...................................................................................................................5 UML 2.1 Overview......................................................................................................................5 UML 2.1 Implementation in Together .........................................................................................6 Provided and Required Interface Links of a Port........................................................................6 Required Interface...........................................................................................................7 Provided Interface...........................................................................................................8
    [Show full text]
  • Fakulta Informatiky UML Modeling Tools for Blind People Bakalářská
    Masarykova univerzita Fakulta informatiky UML modeling tools for blind people Bakalářská práce Lukáš Tyrychtr 2017 MASARYKOVA UNIVERZITA Fakulta informatiky ZADÁNÍ BAKALÁŘSKÉ PRÁCE Student: Lukáš Tyrychtr Program: Aplikovaná informatika Obor: Aplikovaná informatika Specializace: Bez specializace Garant oboru: prof. RNDr. Jiří Barnat, Ph.D. Vedoucí práce: Mgr. Dalibor Toth Katedra: Katedra počítačových systémů a komunikací Název práce: Nástroje pro UML modelování pro nevidomé Název práce anglicky: UML modeling tools for blind people Zadání: The thesis will focus on software engineering modeling tools for blind people, mainly at com•monly used models -UML and ERD (Plant UML, bachelor thesis of Bc. Mikulášek -Models of Structured Analysis for Blind Persons -2009). Student will evaluate identified tools and he will also try to contact another similar centers which cooperate in this domain (e.g. Karlsruhe Institute of Technology, Tsukuba University of Technology). The thesis will also contain Plant UML tool outputs evaluation in three categories -students of Software engineering at Faculty of Informatics, MU, Brno; lecturers of the same course; person without UML knowledge (e.g. customer) The thesis will contain short summary (2 standardized pages) of results in English (in case it will not be written in English). Literatura: ARLOW, Jim a Ila NEUSTADT. UML a unifikovaný proces vývoje aplikací : průvodce ana­lýzou a návrhem objektově orientovaného softwaru. Brno: Computer Press, 2003. xiii, 387. ISBN 807226947X. FOWLER, Martin a Kendall SCOTT. UML distilled : a brief guide to the standard object mode•ling language. 2nd ed. Boston: Addison-Wesley, 2000. xix, 186 s. ISBN 0-201-65783-X. Zadání bylo schváleno prostřednictvím IS MU. Prohlašuji, že tato práce je mým původním autorským dílem, které jsem vypracoval(a) samostatně.
    [Show full text]
  • Deriving Architecture Design Variants for System Optimization from Design Space Descriptions Expressed Using a Uml Profile
    DERIVING ARCHITECTURE DESIGN VARIANTS FOR SYSTEM OPTIMIZATION FROM DESIGN SPACE DESCRIPTIONS EXPRESSED USING A UML PROFILE Alexander Wichmann Francesco Bedini Ralph Maschotta Armin Zimmermann Technische Universität Ilmenau Department of Computer Science and Automation System and Software Engineering Group PO-Box 100 565, 98684 Ilmenau, Germany [email protected] ABSTRACT In complex (dynamic) systems, models are usually too complex for a direct evaluation, and simulation is the method of choice (indirect optimization). Another aspect is the structure of the design space for complex system. In a recent paper of the authors, an approach is presented for design space description with a UML profile-based description of architectural variations of complex dynamic systems. In orderto execute a simulation of a system variant, one has to be chosen based on the used heuristic, and specified in a standardized way to be used for constructing the actual simulation model with the use of a library of template models. This paper approaches a method to automatically generated individual UML object models from the design space specification for a given parameter selection. Keywords: UML profile, architecture design space description, system optimization, design variants 1 INTRODUCTION Model-based systems design is an important help in the design process of complex systems and aims at reduced risks and better design decisions without the need to implement costly prototypes. In the end, each engineering task can be viewed as an optimization problem of finding the best design alternative under given constraints. However, automatic optimization methods can often not be used because of the complexity of the problem field.
    [Show full text]
  • Evaluating Information Systems: Constructing a Model Processing Framework Relatório Final
    Evaluating Information Systems: Constructing a Model Processing Framework Relatório Final João Dias Santa de Vasconcelos Duarte Dissertação para obtenção do Grau de Mestre em Engenharia Informática e de Computadores Júri Presidente: Prof. José Tribolet Orientador: Prof. André Vasconcelos Vogal: Prof. Pedro Sousa Acompanhante: Eng. José Alegria Junho de 2009 Dedico este trabalho à minha família e à minha namorada, Ana. Não teria conseguido sem o vosso apoio. Muito obrigado. i Abstract Enterprises are growing increasingly hungry for information: the will to empower decisions with carefully digested data, the wish of transform all implicit knowledge into clearly dened, explicit repositories that can be shared by all and the desire to monitor all aspects of their internal dynamics. In the past decade, the rush to technology has created several aws when it comes to managing computers, applications, mid- dleware and information systems and so organisations struggle to understand how all these elements are behaving. Even today, as Enterprise Architectures grow in signicance and are acknowledged as advantageous arti- facts to help manage change, their benet to the organisation has yet to be fully explored. We therefore combine our desire for real-time evaluation with the benets of architecture representation to produce an ontologically supported method of modelling, capturing and evaluating systemic behaviour. We produce a conceptual framework to performing this task, while avoiding the imprecise denitions of quality and quality attributes. According to our abstraction, transfering that responsibility to the end user is essencial since such aspects are subjective and depend on the human context in which they exist. This conceptualisation was materialised in a model-eval-display loop framework, and implemented using Model Driven Software Development practices and tools.
    [Show full text]
  • Unified Modeling Language (UML)
    Unified Modeling Language (UML) Troy Mockenhaupt Chi-Hang ( Alex) Lin Pejman ( PJ ) Yedidsion Overview Definition History Behavior Diagrams Interaction Diagrams Structural Diagrams Tools Effect on Software Engineering Definition A standard language for specifying, visualizing, and constructing software artifacts Non-restrictive Expressive and visual modeling language Independent of language and process History First modeling languages emerge 1970s “method wars” of the 1990s Methods began merging techniques 1994 – Booch and Rumbaugh unify Booch and Object Modeling Technique 1995-1996 Jacobson incorporates OOSE methods – term UML is coined 1997 – Object Management Group (OMG) accepted UML as standard History (cont.) UML 2.0 adopted in 2005 2.1.1 and 2.1.2 in 2007 ( never formally released ) UML 2.2 in 2009 UML 2.3 in 2010 UML 2.4.1 2011 UML 1.x vs 2.x 1.x vs 2.x Significant changes 1.x 2.x Activity Diagram Specialized form of Increasing the scope State Diagrams of usage Package Diagram Insufficient for large Added models Component Diagram No port and Added connectors Timing Diagram No syntax for timing Added purposes Behavior Diagrams ● Activity Diagram (basic program flow & capture decision points) ● Use Case Diagram (model user/system interactions) ● State Machine Diagram (“run state” of a model when it executes) Activity Diagram ● Shows the overall flow of control ● Comprises: choice, iteration, and concurrency ● Business and operational step-by-step workflows of components in a system ● A form of flowchart that
    [Show full text]
  • A UML Profile for Delta-Oriented Programming to Support Software
    A UML Profile for Delta-Oriented Programming to Support Software Product Line Engineering? Maya R. A. Setyautami1, Reiner Hähnle2, Radu Muschevici2, and Ade Azurat1 1 Fakultas Ilmu Komputer Universitas Indonesia Depok, Indonesia {mayaretno|ade}@cs.ui.ac.id 2 Department of Computer Science Technische Universität Darmstadt, Darmstadt, Germany {haehnle|radu}@cs.tu-darmstadt.de Abstract. Feature-based approaches to software design, like delta-ori- ented programming, are well-suited to support multi-product software development paradigms, such as Software Product Lines. Currently, the popular UML notation does not support delta-oriented software design, so that several ad-hoc notations tend to be used. This paper presents a systematic approach to import concepts from delta-oriented programming into the mainstream notation UML. This is done with minimal overhead by specifying a new, slim, delta-oriented UML profile. It is compatible with languages that support delta-oriented programming such as DeltaJ and ABS. The usefulness of the profile is evaluated with a case study. 1 Introduction The modeling of product variability—to identify and to manage the commonalities and differences among software products—is a key issue of any software product line (SPL) development process [14]. Variability modeling spans all phases of SPL development, from analyzing the problem by gathering requirements, to design and implementation of a solution in the form of software. Variability modeling is thus a concern in both the problem space and the solution space. In the problem space, variability is typically modeled by abstracting require- ments to features and describing dependencies between features in a feature model [10].
    [Show full text]
  • Product Support\Lifefitness\Treadmills
    1 2 YOU ARE CAUTIONED THAT ANY CHANGES OR MODIFICATIONS TO THIS EQUIPMENT COULD VOID YOUR PRODUCT WARRANTY. MISE EN GARDE : TOUTE MODIFICATION, TOUT CHANGEMENT APPORTÉS À L’APPAREIL PEUVENT ANNULER LA GARANTIE. Before using your Life Fitness 3500 treadmill, it is essential that you read this ENTIRE operation manual. It won’t take very long, and it will help you set up your Life Fitness 3500 aerobic trainer quickly and use it correctly. Avant d’utiliser l’exerciseur Life Fitness, il est nécesaire de lire le guide d’utilisa- tion COMPLÈTEMENT.. Il suffit de quelques instants pour apprendre à assembler et à utiliser correctement l’exerciseur aérobique Life Fitness. WARNING - To reduce the risk of burns, fire, electric shock, or injury to persons: • An appliance should never be left unattended when plugged in. Unplug from outlet when not in use. • To disconnect, turn all controls to the off position, then remove the plug from the outlet. • Connect this appliance to a properly grounded outlet only. See Grounding Instructions. MISE EN GARDE - Pour réduire les risques de brûlure, d’incendie, de secousse électrique ou de blessure: • Ne jamais laisser un appareil sans surveillance lorsqu’il est branché. Le débrancher s’il n’est pas utilisé. • Pour débrancher l’appareil, fermer tous les contrôles et retirer la fiche de la prise murale. • Brancher l’appareil dans une prise correctement mise à la terre. Se reporter- aus «Instructions de mise à la terre». 3 CORPORATE HEADQUARTERS 10601 West Belmont Avenue Franklin Park, Illinois 60131 U.S.A. (847) 288-3300 • FAX: (847) 288-3703 (800) 735-3867 (Toll-free within the U.S.
    [Show full text]