From koffice-devel  Sat Feb 23 20:43:22 2008
From: Carsten Pfeiffer <carsten.pfeiffer () alumni ! tu-berlin ! de>
Date: Sat, 23 Feb 2008 20:43:22 +0000
To: koffice-devel
Subject: Re: Some KOffice questions
Message-Id: <200802232143.25005.carsten.pfeiffer () alumni ! tu-berlin ! de>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=120386058830767
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2105085559=="

--===============2105085559==
Content-Type: multipart/signed;
  boundary="nextPart1565432.gBhtd6ygX8";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1565432.gBhtd6ygX8
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Samstag, 23. Februar 2008 schrieb A. Gunes Koru:

Hi Gunes,

may contributions to KOffice were rather small, but I'll try to answer anyw=
ay.=20
I'll CC the KOffice developers' list, so that they may add some comments if=
=20
they want.

> Hi Carsten,
>
> I've been looking at some KOffice source code for a while, which made
> me wonder about five short questions that I listed below. I wanted to
> drop a quick email and get your opinions because you contributed to
> KOffice. This is not anything big, and it will take less than 5 min. of
> your time. You can just hit reply, type your answers in, and hit the
> send button.
>
> Thanks so much in advance! I really appreciate your help and ideas.
>
> Gunes
>
> P.S. I am a professor of information systems at UMBC, and I am just
> asking these questions because I am curious (no connection with any
> company or organization, no special interest, etc.See my web pages at
> http://umbc.edu/~gkoru).
>
>
> =3D=3D Here we go:
>
>  Please answer Q1, Q2, and Q3 for a Koffice product that you have  the
> most experience with (e.g. KSpread):
>
> Q 1. Let us assume that you are asked to simplify the design of the
> product without changing its functionality  (also known as
> "refactoring" or "restructuring"). The classes  that you end up
> choosing to focus on would be mostly: (put an "X" mark after one of the
> below options).
>
> * larger classes X
> * smaller classes
> * size would not be a factor
>
>  Q 2. What would be the reason for your answer to Q1?
> (enter textual response below)

Larger classes often do too much, that is, they tend to implement more than=
=20
one concern. As the separation of concerns plays a major role in improving=
=20
those so-called "ilities" (reliability, changeability, maintainability,=20
evolvability, ...), these classes are a good target for refactorings.

>  Q 3. Please indicate your agreement or disagreement with this
> statement:
>
> "As the product gets larger, the need for refactoring increases"
>
> (put an "X" mark after one of the below options).
>
> * Strongly Agree
> * Agree X
> * Neutral
> * Disagree
> * Strongly Disagree
>
>
>  Please answer Q4 and Q5 by using your general knowledge about all
> KOffice products (i.e. KWord, KSpread, KPresenter, etc.)
>
>  Q 4. Please indicate your agreement or disagreement with this
> statement:
>
> "Larger KOffice products (e.g. those with larger  number of classes or
> lines of code) are more likely to have gone under more refactoring
> efforts/attempts  compared with smaller KOffice products". (put an "X"
> mark after one of the below options).
>
> * Strongly Agree
> * Agree X
> * Neutral
> * Disagree
> * Strongly Disagree
>
>
>  Q 5. Please indicate your agreement or disagreement with this
> statement:
>
> "As time goes on, the size of a KOffice product under use gets larger,
> and, if we look at our past experience, this principle have always
> applied." (put an "X" mark after one of the below options).
>
> * Strongly Agree
> * Agree X
> * Neutral
> * Disagree
> * Strongly Disagre
>
>  If you have any additional comments or opinions about the above
> questions and the related topics, please put it here:  (enter text)
>
>
>
>
>
>
>
> =3D=3D Thanks so much!

Cheers,
Carsten

--nextPart1565432.gBhtd6ygX8
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----

iQEVAwUAR8CFbKWgYMJuwmZtAQLfXwgAoh/zjWFc/OMwnGv6gNzTHRTtR29jm/9F
BxBORph1VTj5KSjJ1ppRwUUeupnSI6NMnIjS+xVoAL2FAeRuYmquWeLsqR4JunvE
V4RaUTPsBABojw1OdcgsAhaQr6JpZXMgLYx0tlXwtT2BRwdXmUVhpTuBuE7oIZ2d
AJebH9BNPY7P8bhR5E0t6ZM1FweRdu21HlhIGQwd77OBHGwmCn+Rs+RszJZ1GkPv
X7JuFiipiHOaYLTqbPz6Imw0lXFnjPrsnXWUY+qnmoBN0gAaI57tN0AqU3wUWdrT
+Aadn2p1Q84kC7sOuefrBs9EDpGXl8WZTdFX9eJy/eRZCDaZbFTBRg==
=nOqI
-----END PGP SIGNATURE-----

--nextPart1565432.gBhtd6ygX8--


--===============2105085559==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============2105085559==--