# 电子工程代写|面向对象的系统设计代写Object-Oriented Systems Design代考|MPCS51410

## 电子工程代写|面向对象的系统设计代写Object-Oriented Systems Design代考|Conclusions and Outlook

In this chapter we presented two approaches which will allow us to evaluate the design of object-oriented software systems, the Detection Strategy and the Class Blueprint:

Detection Strategy: It provides us with a means to detect flawed (from a design point of view) entities in object-oriented systems. The design strategies produce lists of suspects that comply with specific heuristics encoded with metrics.

Class Blueprint: It provides us with a powerful visual means to inspect the suspects detected by the detection strategies.

In the beginning of this chapter (see 46 ) we argued that metrics can help to evaluate designs, but those have to be meaningful metrics that are put in the context of rules, best practices and heuristics that express the harmony of a design.

Although we partially agree with Fowler stating that “no set of metrics rivals informed human intuition” $\left[\mathrm{FBB}^{+} 99\right]$, there is a big disadvantage: human intuition does not scale with the dimensions of today’s software systems. Therefore, in order to find and improve disharmonious design fragments in the next three chapters we employ detection strategies and the class blueprint.

Consequently in the remaining chapters, we present in detail 11 such design disharmonies. For each of them we describe the detection strategy that helps to detect them automatically using metrics, we look at selected examples using the class blueprint, and conclude each disharmony with a discussion of how to cure flawed entities using refactorings.

## 电子工程代写|面向对象的系统设计代写Object-Oriented Systems Design代考|Rules of Identity Harmony

As mentioned at the end of Chapter 4 before presenting the various identity disharmonies, let us first take a closer look on the most important harmony rules related to a single design entity.

We identified three distinct aspects that contribute to the identity (dis)harmony of a single entity: its size, its interface and its implementation. We summarize each of these aspects in the form of a rule, a rationale and a set of practical consequences. The three rules of identity harmony that we defined are:When considering quality and harmony the first aspect we think about is proportion. The same applies to object-oriented software design. While this first rule is simple to understand it is crucial to follow it. Most of the maintenance and reuse problems come from an unbalanced distribution of a system’s complexity (responsibilities) among classes [Rie96, WBM03] or among operations [FBB ${ }^{+}$99]. This does not mean that all classes or operations must have the same size; rather, it warns us about the danger of going to extremes. Both extremes can be dangerous: too large classes or operations are a maintenance nightmare, while many tiny classes are in most cases a sign of class proliferation and hinder understanding. In the same manner, while it is desirable to have slim operations, sometimes this is abused and we end up with an excessive number of methods, that again hampers maintenance.

## 电子工程代写|面向对象的系统设计代写Object-Oriented Systems Design代考|Rules of Identity Harmony

myassignments-help数学代考价格说明

1、客户需提供物理代考的网址，相关账户，以及课程名称，Textbook等相关资料~客服会根据作业数量和持续时间给您定价~使收费透明，让您清楚的知道您的钱花在什么地方。

2、数学代写一般每篇报价约为600—1000rmb，费用根据持续时间、周作业量、成绩要求有所浮动(持续时间越长约便宜、周作业量越多约贵、成绩要求越高越贵)，报价后价格觉得合适，可以先付一周的款，我们帮你试做，满意后再继续，遇到Fail全额退款。

3、myassignments-help公司所有MATH作业代写服务支持付半款，全款，周付款，周付款一方面方便大家查阅自己的分数，一方面也方便大家资金周转，注意:每周固定周一时先预付下周的定金，不付定金不予继续做。物理代写一次性付清打9.5折。

Math作业代写、数学代写常见问题

myassignments-help擅长领域包含但不是全部: