Get our computer engineering ebooks to upgrade or stay update on it. Nowadays, computer has been advanced so rapidly since it's become one of the most multifunctional tools. We can do almost anything on computer right now like browsing internet, playing games, watching movies, doing design and the list go on and on and on. From a serious work like coding to entertainment. A magic box that very useful and can do anything. You are on the right way by being here since we have huge amounf of it.

Selasa, 22 November 2016

A Design Pattern Oriented Programming Environment

A Design Pattern Oriented Programming Environment
Voc9AwAAQBAJ
94
By:"Normen Seemann"
"Computers"
Published on 2014-04-01 by diplom.de

In PP, the refine construct allows to specify the refinement on the \u003cb\u003edesign pattern\u003c/b\u003e \u003cbr\u003e\nlevel, whereas the recast construct (cf. appendix A) which as part of the \u003cbr\u003e\ncomponent definition is used to specify the refinement on the component level.

READ NOW

Inhaltsangabe:Einleitung: Diese Diplomarbeit ist zusammen mit der Diplomarbeit Entwicklung einer patternorientierten Programmiersprache und eines dazugehörigen Compilers von S. Bünnig (Best.Nr. 29011914) die Grundlage für die Studienarbeit Patternorientierte Programmierung am Anwendungsbeispiel von N. Seemann und S. Bünnig (Best.Nr. 29011913). Ein Entwurfsmuster beschreibt ein in unserer Umwelt beständig wiederkehrendes Problem und erläutert den Kern der Lösung für dieses Problem, so dass diese Lösung beliebig oft anwendbar ist, ohne dass man sie jemals ein zweites Mal gleich ausführen muss. Das Ziel dieser Arbeit besteht nun darin, diesen abstrakten Grundgedanken auf dem Gebiet der Softwareentwicklung formal in einem Programmiermodell zu fassen, das Entwurfsmuster und damit verbundene Konzepte direkt unterstützt und als Erweiterung des objektorientierten Programmiermodells verstanden werden kann. Im Anschluss daran wird ein Sprachentwurf für eine sogenannte patternorientierte Programmiersprache vorgestellt, die es ermöglichen soll, Entwurfsmuster zu implementieren und wiederzuverwenden. Abstract: The development of large scale software systems in a systematic way is still a challenging task in software engineering. The use of structural, modular and object oriented programming techniques and environments have proven to be powerful and reliable for the creation of correct, reusable and maintainable software. Specifically, the object oriented programming model has improved the quality of software by providing structures for better support of abstraction, encapsulation and reusability. In recent years, these properties have become more important since hardware and software systems have grown bigger and more complex. Also, customers have made higher requirements an the quality of software. Object oriented programming languages like Eiffel, Smalltalk or C++ provide basic facilities for network programming, database access, etc. in form of class libraries which exploit these concepts. This helps developers concentrate an the solving of the actual problems, without having to spend time an reinventing already implemented solutions to common problems. The object-oriented paradigm primarily involve objects. These usually represent abstractions of real world entities. Objects are typically defined by classes in programming languages. Classes representing different entities may be related to each other in several different ways. These normally abstract the relationships between the real-word entities that they model. Relationships between classes can be categorized into two kinds - static and dynamic. Static relationships operate at the class level, and include inheritance and subtyping. Dynamit relationships such as association and aggregation operate an the object instance level. The relationships together form what is called the class structure. Classes and relations between classes have to be identified by the designer. These can be achieved using object oriented analysis and design techniques. A specific implementation of the classes and their relations in an object oriented programming language represents the solution of the problem. It is the developer's responsibility to ensure that significant portions of the implementation can be reused in an appropriate way. The ability to do this usually requires deep understanding of object oriented programming techniques, as well as expertise in implementing software systems. Anectdotal experience in [8] suggests that similar problems require similar designs of classes and their structures. These structures of classes and relationships lead to the notion of a design pattern. However, a design pattern captures more than just a class structure - it also contains algorithms for the so-called higher behaviour and paradigms which describe the purpose of the design pattern. In [8] there are listed 23 such design patterns for various purposes. Knowledge of these design pattern can help to create better software in terms of reusability, maintainability and extensibility. It still remains the task of the developer to implement applications of a design pattern as part of a problem solution. The elements which describe such a design pattern may have to be forced into an object oriented form. If the design pattern had been implemented for a very specific problem, and needs to be used in a second similar problem that's different in detail, it would have to be reimplemented from scratch. Object oriented programming techniques allow the reuse and extension of classes by subtyping, inheritance and other refinement methods. However, since object oriented frameworks do not support any notion of a design pattern, it is impossible to reuse a design pattern itself. In chapter 2, design pattern oriented notions are introduced informally. Then, a formal approach will be presented in the following chapters. A design pattern oriented model will be introduced as extension of the object oriented model based an algebraic specification techniques. It directly supports design patterns and design pattern oriented refinements in order to overcome the problems mentioned above. In chapter 6, this model will then be used to describe the denotational semantics of the design pattern oriented imperative programming language PP. PP is a kernel language that supports fundamental features of design pattern oriented programming. In this way, a formal basis is presented for subsequent considerations in this area. Table of Contents: 1.Introduction5 2.Design pattern oriented programming7 2.1The object oriented programming model7 2.2Implementing design patterns10 2.2.1The notion of the design pattern10 2.2.2Problems when design patterns are implemented12 2.3Design pattern oriented software engineering14 2.3.1The design pattern in PP, Instantiation14 2.3.2Implementations, locations, levels and visible elements16 2.3.3Refinements18 2.3.4Reuse vs. Instantiation of design patterns22 2.4Related work23 2.5Remarks and outlook24 3.Basic notions of algebraic specifications and abstract data types25 3.1Partially ordered sets, dependency sets25 3.2Signatures, E-algebras28 3.3Visibility of operations29 3.4Terms and their interpretation30 3.5Operators on signatures33 3.6Operators on specifications37 3.7Relations in SPEC38 3.7.1Object oriented relations38 3.7.2The dependency relation39 4.A design pattern specification framework40 4.1The notion of a design pattern specification40 4.2The refinement relation42 5.A design pattern oriented command language46 5.1State based signatures46 5.2Object algebras49 5.3Commands and method implementations51 5.3.1Commands and their execution53 5.3.2Method implementations56 5.3.3Command translations57 6.A design pattern oriented imperative kernel language60 6.1The syntax of PP60 6.2The (dynamic) semantics of PP63 6.2.1The flattening of design patterns63 6.2.2The semantics of flattened design patterns67 6.3A deduction system for components and design patterns in PP70 6.4The satisfiability of design patterns74 7.Final remarks75 7.1Related work75 7.2Future work75 7.3Conclusion76 A.The syntax of PP in EBNF77 B.Basic notions of partial finite mappings (cf.[5])79 C.Selected design pattern implementations80 C.1List80 C.2Subtyping83 C.3Composite83 C.4GraphicComposite84

This Book was ranked 39 by Google Books for keyword design pattern.

The book is written in enfor NOT_MATURE

Read Ebook Now
false
true

Printed Version of this book available in
BOOK

Availability of Ebook version is true,"listPrice": {"amount": 42.99,"currencyCode": "USD"in falseor true

Public Domain Status false

Rating by

SAMPLE

false

To Get More Computer Engineering Ebooks Click Here

Tidak ada komentar:

Posting Komentar

Comments

Contact Us

Nama

Email *

Pesan *