Object-Oriented Software Engineering Using UML, Patterns, and Java
Brügge, Bernd|Dutoit, Allen H.
Language: English
Published by Pearson Education, 2009
- Softcover
- New
Condition: New
US$ 129.98
Quantity: 1 available
Add to basketItem description from seller
For courses in Software Engineering, Software Development, or Object-Oriented Design and Analysis at the Junior/Senior or Graduate level. This text can also be utilized in short technical courses or in short, intensive management courses.
Seller Inventory # 4086182
- Title
- Object-Oriented Software Engineering Using UML, Patterns, and Java
- Author
- Brügge, Bernd|Dutoit, Allen H.
- Publisher
- Pearson Education
- Publication year
- 2009
- Condition
- New
- Binding
- Kartoniert / Broschiert
- Language
- English
- ISBN 10
- 1292024011
- ISBN 13
- 9781292024011
- Edition
- 3rd Edition
- Dimensions
- 2.4 x 27.6 x 21.6
"Synopsis" may belong to another edition of this title.
From the Inside Flap
The K2 towers at 8,611 meters in the Karakorum range of the western Himalayas. It is the second highest peak of the world and is considered the most difficult 8000er to climb. An expedition to the K2 typically lasts several months in the summer, when the weather is most favorable. Even in summer, snow storms are frequent. An expedition requires thousands of pounds of equipment, including climbing gear, severe weather protection gear, tents, food, communication equipment, and pay and shoes for hundreds of porters. Planning such an expedition takes a significant amount of time in the life of a climber and requires dozens of participants in supporting roles. Once on site, many unexpected events, such as avalanches, porter strikes, or equipment failures, will force the climbers to adapt, find new solutions, or retreat. The success rate for expeditions to the K2 is currently less than 40%.
The United States National Airspace System (NAS) monitors and controls air traffic in the United States. The NAS includes more than 18,300 airports, 21 air route traffic control centers, and over 460 control towers. This adds up to more than 34,000 pieces of equipment, including radars, communication switches, radios, computer systems, and displays. The current infrastructure is aging rapidly. The computers supporting the 21 air route traffic control centers, for example, are IBM 3083 mainframes that date back to the early 1980s. In 1996, the United States government initiated a program to modernize the NAS infrastructure, including improvements such as satellite navigation, digital controller/pilot communications, and a higher degree of automation in controlling the air routes, the order in which aircraft land, and control of ground traffic as aircraft move from and to the runways. Modernizing such a complex infrastructure, however, can only be done incrementally. Consequently, while new components offering new functionality are introduced, older components still need to be supported. For example, during the transition period, a controller will have to be able to use both analog and digital voice channels to communicate with pilots. Finally, the modernization of the NAS coincides with a dramatic increase in global air traffic, predicted to double within the next 10-15 years. The previous modernizing effort of the NAS, called the Advanced Automation System (AAS), was suspended in 1994 because of software-related problems, after missing its initial deadline by several years and exceeding its budget by several billions of dollars.
Both of the above examples discuss complex systems, where external conditions can trigger unexpected changes. Complexity puts the problem beyond the control of any single individual. Change forces participants to move away from well-known solutions and to invent new ones. In both examples, several participants need to cooperate and develop new techniques to address these challenges. Failure to do so results in the failure to reach the goal.
This book is about conquering complex and changing software systems. The theme
The application domain (mountain expedition planning, air traffic control, financial systems, word processing) usually includes many concepts that software developers are not familiar with. The solution domain (user interface toolkits, wireless communication, middleware, database management systems, transaction processing systems, wearable computers, etc.) is often immature and provides developers with many competing implementation technologies. Consequently, the system and the development project are complex, involving many different components, tools, methods, and people.
As developers learn more about the application domain from their users, they update the requirements of the system. As developers learn more about emerging technologies or about the limitations of current technologies, they adapt the system design and implementation. As quality control finds defects in the system and users request new features, developers modify the system and its associated work products, resulting in continuous change.
Complexity and change represent challenges that make it impossible for any single person to control the system and its evolution. If controlled improperly, complexity and change defeat the solution before its release, even if the goal is in sight. Too many mistakes in the interpretation of the application domain make the solution useless for the users, forcing a retreat from the route or the market. Immature or incompatible implementation technologies result in poor reliability and delays. Failure to handle change introduces new defects in the system and degrades performance beyond usability.
This book reflects more than 10 years of building systems and of teaching software engineering project courses. We have observed that students are taught programming and software engineering techniques in isolation, often using small problems as examples. As a result, they are able to solve well-defined problems efficiently, but are overwhelmed by the complexity of their first real development experience, when many different techniques and tools need to be used and different people need to collaborate. Reacting to this state of affairs, the typical undergraduate curriculum now often includes a software engineering project course, organized as a single development project. The tools: UML, Java, and Design Patterns
We wrote this book with a project course in mind. This book can be used, however, in other situations as well, such as short and intensive workshops or short-term R&D projects. We use examples from real systems and examine the interaction between state-of-the art techniques, such as UML (Unified Modeling Language), Java-based technologies, design patterns, design rationale, configuration management, and quality control. Moreover, we discuss project management related issues that are related to these techniques and their impact on complexity and change. The principles
We teach software engineering following five principles:
Practical experience. We believe that software engineering education must be linked with practical experience. Understanding complexity can only be gained by working with a complex system; that is, a system that no single student can completely understand.
Problem solving. We believe that software engineering education must be based on problem solving. Consequently, there are no right or wrong solutions, only solutions that are better or worse relative to stated criteria. Although we survey existing solutions to real problems and encourage their reuse, we also encourage criticism and the improvement of standard solutions.
Limited resources. If we have sufficient time and resources, we could perhaps build the ideal system. There are several problems with such a situation. First, it is not realistic. Second, even if we had sufficient resources, if the original problem rapidly changes during the development, we would eventually deliver a system solving the wrong problem. As a result, we assume that our problem-solving process is limited in terms of resources. Moreover, the acute awareness of scarce resources encourages a component-based approach, reuse of knowledge, design, and code. In other words, we support an engineering approach to software development.
Interdisciplinarity. Software engineering is an interdisciplinary field. It requires contributions from areas spanning electrical and computer engineering, computer science, business administration, graphic design, industrial design, architecture, theater, and writing. Software engineering is an applied field. When trying to understand and model the application domain, developers interact regularly with others, including users and clients, some of whom know little about software development. This requires viewing and approaching the system from multiple perspectives and terminologies.
Communication. Even if developers build software for developers only, they would still need to communicate among themselves. As developers, we cannot afford the luxury of being able to communicate only with our peers. We need to communicate alternatives, articulate solutions, negotiate trade-offs, and review and criticize others' work. A large number of failures in software engineering projects can be traced to the communication of inaccurate information or to missing information. We must learn to communicate with all project participants, including, most importantly, the client and the end users.
These five principles are the basis for this book. They encourage and enable the reader to address complex and changing problems with practical and state-of-the-art solutions. The book
This book is based on object-oriented techniques applied to software engineering. It is neither a general software engineering book that surveys all available methods nor a programming book about algorithms and data structures. Instead, we focus on a limited set of techniques and explain their application in a reasonably complex environment, such as a multiteam development project that includes 20-60 participants. Consequently, this book also reflects our biases, our strengths, and our weaknesses. We hope, nevertheless, that all readers will find something they can use. The book is structured into 12 chapters organized into four parts, which can be taught as a semester-long course.
Part I, Getting Started, includes three chapters. In this part, we focus on the basic skills necessary for a developer to function in a software engineering context.
In Chapter 1, Introduction to Software Engineering, we describe the difference between programming and software engineering, the current challenges in our discipline, and basic definitions of concepts we use throughout the book. In Chapter 2, Modeling with UML, we describe the basic elements of a modeling language, UML (Unified Modeling Language), used in object-oriented techniques. We present modeling as a technique for dealing with complexity. This chapter teaches the reader how to read and understand UML diagrams. Subsequent chapters teach the reader how to build UML diagrams to model various aspects of the system. We use UML throughout the book to model a variety of artifacts, from software systems to processes and work products. In Chapter 3, Project Communication, we discuss the single most critical activity that developers perform. Developers and managers spend more than half of their time communicating with others, either face-to-face or via E-mail, groupware, video conference, or written documents. While modeling deals with complexity, communication deals with change. We describe the main means of communications, their application, and discuss what constitutes effective communication.
In Part II, Dealing with Complexity, we focus on methods and technologies that enable developers to specify, design, and implement complex systems.
In Chapter 4, Requirements Elicitation, and Chapter 5, Analysis, we describe the definition of the system from the users' point of view. During requirements elicitation, developers determine the functionality users need and a usable way of delivering it. During analysis, developers formalize this knowledge and ensure its completeness and consistency. We focus on how UML is used to deal with application domain complexity. In Chapter 6, System Design, we describe the definition of the system from the developers' point of view. During this phase, developers define the architecture of the system in terms of design goals and a subsystem decomposition. They address global issues, such as the mapping of the system onto hardware, the storage of persistent data, and global control flow. We focus on how developers can use design patterns, components, and LTML to deal with solution domain complexity. In Chapter 7, Object Design, we describe the detailed modeling and construction activities related to the solution domain. We refine the requirements and system models and specify precisely the classes that constitute the system and define the boundary of existing class libraries and frameworks. For the specification of class interfaces we use UML's Object Constraint Language.
In Part III, Managing Change, we focus on methods and technologies that support the control, assessment, and implementation of changes throughout the life cycle. In Chapter 8, Rationale Management, we describe the capture of design decisions and their justifications. The models we develop during requirements elicitation, analysis, and system design help us deal with complexity, by providing us with different perspectives on what the system should be doing and how it should do it. To be able to deal with change, we need also to know why the system is the way it is. Capturing design decisions, the evaluated alternatives, and their argumentation enables us to access the rationale of the system. In Chapter 9, Testing, we describe the validation of system behavior against the system models. Testing detects faults in the system, including those introduced during changes to the system or its requirements. Testing activities include unit testing, integration testing, and system testing. We describe several testing techniques such as whitebox, blackbox, path testing, state-based testing, and inspections. In Chapter 10, Software Configuration Management, we describe techniques and tools for modeling the project history. Configuration management complements rationale in helping us deal with change. Version management records the evolution of the system. Release management ensures consistency and quality across the components of a release. Change management ensures that modifications to the system are consistent with project goals. In Chapter 11, Project Management, we describe techniques necessary for initiating a software development project, tracking its progress, and dealing with risks and unplanned events. We focus on organizations, roles, and management activities that allow a large number of participants to collaborate and deliver a high-quality system within planned constraints.
In Part IV, Starting Over, we revisit the concepts we described in the previous chapters from a process perspective. In Chapter 12, Software Life Cycle, we describe software life cycles, such as Boehm's Spiral Model and the Unified Software Development Process, which provide an abstract model of development activities. In this chapter, we also describe the Capability Maturity Model, which is used for assessing the maturity of organizations. We conclude with two examples of software life cycles, which can be applied in a class project.
The topics above are strongly interrelated. To emphasize their relationships, we selected an iterative approach. Each chapter consists of five sections. In the first section, we introduce the issues relevant to the topic with an illustrative example. In the second section, we describe briefly the activities of the topic. In the third section, we explain the basic concepts of the topic with simple examples. In the fourth section, we detail the technical activities with examples from real systems. Finally, we describe management activities and discuss typical trade-offs. By repeating and elaborating on the same concepts by using increasingly complex e...
"About the title" may belong to another edition of this title.
Shipping rates from Germany to U.S.A.
| Item | 13 to 40 business days | 13 to 40 business days |
|---|---|---|
| First item | US$ 54.94 | US$ 54.94 |
Payment methods
- Bank Wire Transfer
- Check
- Paypal
Store description
Online Handel nur mit Neubüchern
Seller's business information
Moluna GmbH
Engberdingdamm 27
Greven, Germany 48268
Terms of sale
Instructions for revocation/
Standard Business Terms and customer information/ data protection declaration
Revocation right for consumers
(A ‘consumer’ is any natural person who concludes a legal transaction which, to an overwhelming extent, cannot be attributed to either his commercial or independent professional activities.)
Instructions for revocation
Revocation right
You have the right to revoke this contract within one month without specifying any reasons.
The revocation period is one month with effect from the day,
-
on which you or a third party nominated by you, which is not the carrier, had taken possession of the products, provided you had ordered one or more products within the scope of a standard order and this/these product/products is/are delivered uniformly;
-
on which you or a third party nominated by you, which is not the carrier, had taken possession of the last product, provided you had ordered several products within the scope of a standard order and these products are delivered separately;
-
on which you or a third party nominated by you, which is not the carrier, had taken possession of the last part delivery or the last unit, provided you had ordered a product, which is delivered in several part deliveries or units;
In order to exercise your revocation right, you must inform us (Moluna GmbH, Engberdingdamm 27, 48268 Greven, Telephone number: 02571/5 69 89 33, Fax number: 02571/5 69 89 30, E-Mail address: abe@moluna.de) of your decision to revoke this contract by means of a clear declaration (e.g. a letter sent via post, fax or email). You can use the enclosed specimen revocation form for this, which however is not mandatory.
In order to safeguard the revocation period, it is sufficient that you send the notification about the exercise of the revocation right before the expiry of the revocation period.
Consequences of the revocation
If you revoke this contract, we shall repay all the payments, which we received from you, including the delivery costs (with the exception of additional costs, which arise from that fact that you selected a form of delivery other than the most reasonable standard delivery offered by us), immediately and at the latest within 14 days from the day on which we received the notification about the revocation of this contract from you. We use the same means of payment, which you had originally used during the original transaction, for this repayment unless expressly agreed otherwise with you; you will not be charged any fees owing to this repayment.
We can refuse the repayment until the products are returned to us or until you have furnished evidence that you have sent the products back to us, depending on whichever is earlier.
You must return or transfer the products to us immediately and, in any case, at the latest within 14 days with effect from the day on which you inform us of the revocation of this contract. The deadline is maintained if you send the products before the expiry of the 14 day deadline.
You bear the direct costs for returning the products.
You must pay for any depreciation of the products only if this depreciation can be attributed to any handling with you that was not necessary for checking the condition, features and functionality of the products.
Criteria for exclusion or expiry
The revocation right is not available for contracts
for delivery of products, which are not prefabricated and for whose manufacturing an individual selection or stipulation by the consumer is important or which are clearly tailored to the personal requirements of the consumer;
for delivery of products, which can spoil quickly or whose use-by date would be exceeded quickly;
for delivery of alcoholic drinks, whose price was agreed at the time of concluding the contract, which however can be delivered 30 days after the conclusion of the contract at the earliest and whose current value depends on the fluctuations in the market, on which the entrepreneur has no influence;
for delivery of newspapers, periodicals or magazines with the exception of subscription contracts.
The revocation right expires prematurely in case of contracts
for delivery of sealed products, which are not suitable for return for reasons of health protection or hygiene if their seal has been removed after the delivery;
for delivery of products if they have been mixed inseparably with other goods after the delivery, owing to their condition;
for delivery of sound or video recording or computer software in a sealed package if the seal has been removed after the delivery.
Specimen - revocation form
(If you wish to revoke the contract, please fill up this form and send it back to us.)
-
To Moluna GmbH, Münsterstr. 105, 48268 Greven, Fax number: 02571/5 69 89 30, Email address: abe@moluna.de :
-
I/we () herewith revoke the contract concluded by me/ us () regarding the purchase of the following products ()/
the provision of the following service () -
Ordered on ()/ received on ()
-
Name of the consumer(s)
-
Address of the consumer(s)
-
Signature of the consumer(s) (only in case of a notification on paper)
-
Date
(*) Cross out the incorrect option.
Standard Business Terms and customer information / data protection declaration
I. Standard business terms
§ 1 Basic provisions
(1) The following terms and conditions of business apply for all contracts concluded with us as the supplier (Moluna GmbH) via the websites AbeBooks and/or ZVAB. Unless otherwise agreed, the inclusion of your own terms and conditions is explicitly rejected.
(2) A ‘consumer’ in the sense of the following regulations is every natural person who concludes a legal transaction which, to an overwhelming extent, cannot be attributed to either his commercial or independent professional activities. The term ‘businessman’ refers to every natural person, legal person or legally responsible partnership that concludes a legal transaction in pursuance of his/its independent professional or commercial activity.
§ 2 Conclusion of the contract
(1) The subject-matter of the contract is the selling of products .
(2) If an article is placed by us with AbeBooks or ZVAB, the activation of the page on AbeBooks or ZVAB shall involve the binding offer to conclude a contract under the terms and conditions contained in the article page.
(3) The contract shall become effective via the online shopping cart system as follows:
The products intended for purchase are moved to the "shopping cart". You can select the "Shopping Cart" using the appropriate buttons on the navigation bar and make changes there at any time.
After calling up the “Checkout” page and entering the required personal data and payment and shipping conditions, all order information is then displayed again on the order summary page.
Before submitting the order, you have the ability once more to review or change any information here (you may also use the "back" button on the Internet browser), or to cancel the purchase.
By clicking the “Buy now” button to submit the order, you declare your legally binding acceptance of the order which makes the contract effective.
(4) The execution of the order and the sending of all the details necessitated by the conclusion of the contract take place via e-mail, in a partially-automated manner. Consequently, you have to ensure that the e-mail address that you have deposited with us is the correct one, and that the receipt of the respective e-mails is guaranteed. In particular, you have to ensure that the respective e-mails are not blocked by a SPAM filter.
§ 3 Right of retention, reservation of proprietary rights
(1) You can only exercise a right of retention if the situation in question involves claims arising from the same contractual relationship.
(2) The goods remain our property until the purchase price is paid in full.
(3) If you are a businessman, the following conditions also apply:
a) We retain ownership of the goods until all the claims arising from the ongoing business relationship have been settled in full. The goods subject to retention of title may not be pledged or transferred by way of security before ownership of the said goods changes hands.
b) You can re-sell the goods within the framework of an orderly transaction. In this regard, you hereby cede all the claims amounting to the magnitude of the billing amount that accrue to you as a result of the re-selling operation to us, and we accept the cession. Furthermore, you are authorised to collect the claim in question. However, insofar as you do not discharge your payment obligations in an orderly fashion, we reserve the right to collect the claim ourselves.
c) In a situation involving the combination and amalgamation of the goods subject to retention of title, we acquire co-ownership of the newly-formed item. This co-ownership corresponds to the ratio that exists between the invoice value of the goods subject to retention of title and the other processed items at the time of processing.
d) If you make a request of this nature, we shall be obligated to release the securities that are due to us, to the extent that the realisable value of our securities exceeds the claim to be secured by more than 10%. We are responsible for selecting the securities to be released.
§ 4 Warranty
(1) The statutory warranty rights are applicable.
(2) As a consumer, you are requested to promptly check the product for completeness, visible defects and transport damage as soon as it is delivered, and promptly disclose your complaints to us and the shipping company in writing. Even if you do not comply with this request, it shall have no effect on your legal warranty claims.
(3) If a characteristic of the goods deviates from the objective requirements, the deviation shall only be deemed to be agreed if you were informed of the same by us before submitting the contractual declaration and the deviation was expressly and separately agreed between the contracting parties.
(4)
Insofar as you are an entrepreneur, the following shall apply in deviation from the above warranty provisions:
a) Only our own specifications and the manufacturer's product description shall be deemed agreed as the quality of the goods, but not other advertising, public promotions and statements by the manufacturer.
b) In the event of defects, we shall, at our discretion, provide warranty by rectification of the defect or subsequent delivery. If the rectification of defects fails, you may, at your option, demand a reduction in price or withdraw from the contract. The rectification of defects shall be deemed to have failed after a second unsuccessful attempt, unless the nature of the goods or the defect or other circumstances indicate otherwise. In the event of rectification of defects, we shall not be obliged to bear the increased costs arising from the transport of the goods to a place other than the place of performance, unless such transport is in accordance with the intended use of the goods.
c) The warranty period shall be one year from delivery of the goods. The shortening of the period shall not apply
- for culpable damage attributable to us arising from injury to life, limb or health and for other damage caused intentionally or by gross negligence;
- insofar as we have fraudulently concealed the defect or have assumed a guarantee for the quality of the item;
- in the case of items which have been used for a building in accordance with their customary use and have caused its defectiveness;
- in the case of statutory rights of recourse that you may assert against us in connection with rights arising from defects.
§ 5 Choice of law, place of fulfilment, jurisdiction
(1) German law shall apply. This choice of law only applies to customers if it does not result in the revocation of the protection guaranteed by the mandatory provisions of the law of the country in which the respective customer’s usual place of residence is located (benefit-of-the-doubt principle).
(2) If you are not a consumer, but a businessman, a legal entity under public law or an institutional fund governed by public law, our place of business is the place of jurisdiction as well as the place of fulfilment for all services that follow from the business relationships that exist with us. The same condition applies to situations in which you are not associated with a general place of jurisdiction in Germany or the EU, as well as situations in which the place of residence or the usual place of residence is not known at the time of commencement of proceedings. This has no bearing on the capacity to call upon the court associated with another place of jurisdiction.
(3) The provisions of the UN Convention on Contracts for the International Sale of Goods are explicitly inapplicable.
II. Customer information
- Identity of the seller
Moluna GmbH
Engberdingdamm 27
48268 Greven
Germany
Telephone: 02571/5698933
E-Mail: abe@moluna.de
- Information regarding the conclusion of the contract
The technical steps associated with the conclusion of the contract, the contract conclusion itself and the correction options are executed in accordance to the regulations "conclusion of the contract" in our standard business terms (part I.).
- Contractual language, saving the text of the contract
3.1 Contract language shall be English.
3.2 The complete text of the contract is not saved with us. Before the order is sent, the contract data can be printed out or electronically saved using the browser’s print function. After the order is received by us, the order data, the legally-mandated details related to distance selling contracts and the standard business terms are re-sent to you via e-mail.
- Main features of the product or service
The key features of the goods and/or services can be found in the respective quote.
- Prices and payment arrangements
5.1 The prices mentioned in the respective offers represent total prices, as do the shipping costs. They include all the price components, including all the incidental taxes.
5.2 The dispatch costs that are incurred are not included in the purchase price. They can be viewed by clicking the appropriate button on our website or in the respective quote, are shown separately over the course of the order transaction and must additionally be borne by you, insofar as free delivery is not confirmed.
5.3 The payment methods that are available to you are shown by clicking the appropriate button on our website or are disclosed in the respective quote.
5.4 Unless otherwise specified for the respective payment methods, the payment claims arising from the contract that has been concluded become payable immediately.
- Delivery conditions
6.1 The delivery conditions, delivery date and existing supply restrictions, if applicable, can be found by clicking the appropriate button on our website or in the respective quote.
Unless a different period is specified in the item description or our delivery conditions, the goods are delivered within 3-5 days after the conclusion of the contract (in case an advance payment has been agreed upon, after the payment authorisation).
6.2 If you are a consumer, the following is statutorily regulated: The risk of the sold item accidentally being destroyed or degraded during shipping only passes over to you when the item in question is delivered, regardless of whether or not the shipping operation is insured. This condition does not apply if you have independently commissioned a transport company that has not been specified by us or a person who has otherwise been appointed to execute the shipping operation.
If you are a businessman, the delivery and shipping operations take place at your own risk.
- Statutory warranty right
Liability for defects is governed by the “Warranty” provisions in our General Terms and Conditions of Business (Part I).
last update: 01.01.2022
Data protection declaration
Unless stated otherwise below, the provision of your personal data is neither legally nor contractually obligatory, nor required for conclusion of a contract. You are not obliged to provide your data. Not providing it will have no consequences. This only applies as long as the processing procedures below do not state otherwise.
“Personal data” is any information relating to an identified or identifiable natural person.
Responsible person
Contact us at any time. The contact details of the person responsible for data processing can be found in our legal notice.
Collection, processing, and transfer of personal data in orders
When you submit an order we only collect and use your personal data insofar as this is necessary for the fulfilment and handling of your order as well as processing of your queries. The provision of data is necessary for conclusion of a contract. Failure to provide it will prevent the conclusion of any contract. The processing will occur on the basis of Article 6(1) b) GDPR and is required for the fulfilment of a contract with you.
Your data is transferred here for example to the shipping companies and dropshipping providers, payment service providers, service providers for handling the order and IT service providers that you have selected. We will comply strictly with legal requirements in every case. The scope of data transmission is restricted to a minimum.
Duration of storage
After contractual processing has been completed, the data is initially stored for the duration of the warranty period, then in accordance with the retention periods prescribed by law, especially tax and commercial law, and then deleted after the period has elapsed, unless you have agreed to further processing and use.
Rights of the affected person
If the legal requirements are fulfilled, you have the following rights according to art. 15 to 20 GDPR: Right to information, correction, deletion, restriction of processing, data portability. You also have a right of objection against processing based on art. 6 (1) GDPR, and to processing for the purposes of direct marketing, according to art. 21 (1) GDPR.
Right to complain to the regulatory authority
You have the right to complain to the regulatory authority according to art. 77 GDPR if you believe that your data is not being processed legally.
Right to object
If the data processing outlined here is based on our legitimate interests in accordance with Article 6(1)f) GDPR, you have the right for reasons arising from your particular situation to object at any time to the processing of your data with future effect.
If the objection is successful, we will no longer process the personal data, unless we can demonstrate compelling legitimate grounds for the processing that outweigh your interests or rights and freedoms, or the processing is intended for the assertion, exercise or defence of legal claims.
last update: 10.01.2022