@@ -125,102 +125,3 @@ <h2>This is an H2 in a blockquote</h2>
125125
126126< p > I start my morning with a cup of coffee and
127127< a href ="http://www.nytimes.com/ "> The New York Times</ a > .</ p >
128-
129- < p > < img src ="image.jpg " title ="Title " alt ="alt text " /> </ p >
130-
131- < p > < img src ="image2.jpg " title ="Title " alt ="alt text " /> </ p >
132-
133- < p > I wish SmartyPants used named entities like < code > &mdash;</ code >
134- instead of decimal-encoded entites like < code > &#8212;</ code > .</ p >
135-
136- < p > If you want your page to validate under XHTML 1.0 Strict,
137- you’ve got to put paragraph tags in your blockquotes:</ p >
138-
139- < p > ```</ p >
140-
141- < blockquote >
142- < p > For example.</ p >
143- </ blockquote >
144-
145-
146- < p > ```</ p >
147-
148- < h1 > August 31, 2011</ h1 >
149-
150- < p > Homework: Problems 2.10-2.19; complete registration system</ p >
151-
152- < hr />
153-
154- < h2 > Chapter 2</ h2 >
155-
156- < h3 > Phases of Software Development</ h3 >
157-
158- < ol >
159- < li > Analysis</ li >
160- < li > Design</ li >
161- < li > Implementation</ li >
162- </ ol >
163-
164-
165- < h4 > Analysis phase</ h4 >
166-
167- < p > < em > Requirements</ em > – what the customer wants or needs. Understanding on needs expressed by:</ p >
168-
169- < ul >
170- < li > Use cases can (can use UML)</ li >
171- < li > User manual style of analysis document</ li >
172- </ ul >
173-
174-
175- < h4 > Design phase</ h4 >
176-
177- < p > Goals of OO design:</ p >
178-
179- < ol >
180- < li > Identify classes – things in the system</ li >
181- < li > Identify responsibilities of the classes</ li >
182- < li > Identify relationships between classes</ li >
183- </ ol >
184-
185-
186- < p > Classes consist of:</ p >
187-
188- < ol >
189- < li > Behavior: Methods represent the class behavior</ li >
190- < li > State: Fields represent the state of the class instance (object)</ li >
191- < li > Identity: each unique object should have its own address in memory
192- which contains its state</ li >
193- </ ol >
194-
195-
196- < p > Types of classes that are common:</ p >
197-
198- < ol >
199- < li > Tangible things</ li >
200- < li > Agents</ li >
201- < li > Events and transactions</ li >
202- < li > Users and roles</ li >
203- < li > Systems</ li >
204- < li > System interfaces and devices</ li >
205- < li > Foundational classes</ li >
206- </ ol >
207-
208-
209- < p > Types of class relationships:</ p >
210-
211- < ol >
212- < li > Dependency (< em > uses a</ em > )</ li >
213- < li > < p > Aggregation (< em > has a</ em > )</ p >
214-
215- < ul >
216- < li > Aggregation – 1:many</ li >
217- < li > Association – 1:1</ li >
218- < li > Composition – “< em > if I’m composed of other things, then I am considered
219- responsible for the lifetime for those things</ em > ”</ li >
220- </ ul >
221- </ li >
222- < li > Inheritance (< em > is a</ em > )</ li >
223- </ ol >
224-
225-
226- < p > Classes and relationships are the basis for a UML class diagram.</ p >
0 commit comments