1.1 --- a/unix-phil.ms	Fri Feb 05 16:40:51 2010 +0100
     1.2 +++ b/unix-phil.ms	Wed Feb 10 13:19:04 2010 +0100
     1.3 @@ -28,7 +28,7 @@
     1.4  .ti \n(.iu
     1.5  This paper discusses the importance of the Unix Philosophy in software design.
     1.6  Today, few software designers are aware of these concepts,
     1.7 -and thus most modern software is limited and does not use software leverage.
     1.8 +and thus most modern software is limited and does not make use of software leverage.
     1.9  Knowing and following the tenets of the Unix Philosophy makes software more valuable.
    1.10  .AE
    1.11  
    1.12 @@ -47,27 +47,28 @@
    1.13  Introduction
    1.14  .LP
    1.15  Building a software is a process from an idea of the purpose of the software
    1.16 -to the finished program.
    1.17 +to its release.
    1.18  No matter \fIhow\fP the process is run, two things are common:
    1.19  the initial idea and the release.
    1.20 -But the the process inbetween can be of any shape.
    1.21 -The time of release and the maintainance work after the release are ignored here, for the moment.
    1.22 +The process inbetween can be of any shape.
    1.23 +The the maintainance work after the release is ignored for the moment.
    1.24  .PP
    1.25  The process of building splits mainly in two parts:
    1.26  the planning of what and how to build, and implementing the plan by writing code.
    1.27 -This paper focuses on the planning \(en the design \(en of software.
    1.28 -The here discussed ideas may be applied to any development process.
    1.29 -Though the Unix Philosphy does recommend how the software development process should look like,
    1.30 -this shall not be of matter here.
    1.31 +This paper focuses on the planning part \(en the designing of the software.
    1.32 +.PP
    1.33 +Software design is the plan of how the internals and externals of the software should look like,
    1.34 +based on the requirements.
    1.35 +This paper discusses the recommendations of the Unix Philosphy about software design.
    1.36 +.PP
    1.37 +The here discussed ideas can get applied by any development process.
    1.38 +The Unix Philosphy does recommend how the software development process should look like,
    1.39 +but this shall not be of matter here.
    1.40  Similar, the question of how to write the code is out of focus.
    1.41  .PP
    1.42 -This paper discusses the connection between software design and the Unix Philosphy.
    1.43 -Software design is the work between the requirements and the plan of how the internals and externals
    1.44 -of the software should look like.
    1.45 -However, the term ``Unix Philosophy'' was used but not explained yet.
    1.46 -.PP
    1.47 +The name ``Unix Philosophy'' was already mentioned several times, but it was not explained yet.
    1.48  The Unix Philosophy is the essence of how the Unix operating system and its toolchest was designed.
    1.49 -It is no limited set of rules, but what people see what is common to typical Unix software.
    1.50 +It is no limited set of rules, but what people see to be common to typical Unix software.
    1.51  Several people stated their view on the Unix Philosophy.
    1.52  Best known are:
    1.53  .IP \(bu
    1.54 @@ -102,7 +103,7 @@
    1.55  .]
    1.56  .LP
    1.57  These different views on the Unix Philosophy have much in common.
    1.58 -Especially, the main concepts are seen by all of them.
    1.59 +Especially, the main concepts are similar for all of them.
    1.60  But there are also points on which they differ.
    1.61  This only underlines what the Unix Philosophy is:
    1.62  A retrospective view on the main concepts of Unix software;
    1.63 @@ -117,11 +118,13 @@
    1.64  Importance of software design
    1.65  .LP
    1.66  Why should we design software at all?
    1.67 -It should be general knowledge, that a bad plan is better than no plan.
    1.68 +It is general knowledge, that a bad plan is better than no plan.
    1.69  As stated earlier in this document, the process of building a software
    1.70  means going from an idea to a release.
    1.71  The development process tells how to get from the idea to the release.
    1.72 -Software design tells how the built software should look like.
    1.73 +Software design is the shape of the built software.
    1.74 +This means, that different designs of a software would be different target points to go to.
    1.75 +Thus, the design of a software defines the global direction the development goes.
    1.76  .PP
    1.77  It is not enough that the released software offers all requested functionality.
    1.78  It is a misbelief that only function matters.
    1.79 @@ -138,7 +141,7 @@
    1.80  Developers should, for their own best, have maintainability and extendability in mind
    1.81  when they design the software.
    1.82  .PP
    1.83 -Users of the software do not care about maintainability and extendability,
    1.84 +Users of the software, in contrast, do not care about maintainability and extendability,
    1.85  at least not directly.
    1.86  They care about usability and flexibility.
    1.87  They want the software to directly solve their problems.