[Corelinux-public] From Analysis To Design

[Jim K. <jrk...@so...>]

Here are some comments on the Analysis to Design doc:

The assumptions I am making about the reader at this point are:

A. That the effort of Analysis has is that the focus is on the problem
domain, not on a specific technical solution.
/*
 -- I understand the meaning here, but the verbage is confusing.  Remove
"has"?
*/

B. Class, Sequence, Collaboration, State, and Activity diagrams are
             understood. If you are unsure about these let me know and I
will post
             links to where you can find out more. For immediate
consumption
             http://www.cetus-links.org has a tremendous reference list.

/*
-- I need to familiarize myself with these diagrams, thanks for the
reference link!
*/

In general, the design is a technical expansion and adaptation of the
             analysis results. The classes, realtionships, and
collaborations from
             the analysis are complemented with new elements, now
focusing on how to
             implement the requirement.
/*
-- <sp.>  ... realtionships...
--  <?> ...now focusing on how to....
*/

1. Once a Analysis has been checked in it will move into the Design

/*
-- an Analysis... <?>
*/
<cut to the end>

I like this description of the process, it is very detailed, and covers
some important points.

Jim Koontz
jrk...@us...