Differences between revisions 1 and 86 (spanning 85 versions)

$/!\$ It was found that many of the students had not done Java B. This will result in difficulties in understanding the basic concepts of object orientation that form the bases of this assignment. However this assignment is to help you to get a better understanding and hopefully to use object-oriented thinking elsewhere in your design, so lets lower our ambitions a bit, and focus only on the essence of object-orientated analysis and design. Also due to the limited time, [#dp the sencond half] of this assignment, that is, design patterns, will be only an introduction. The individual task has been adjusted accordingly.

Owning a hammer doesn't make one an architect.

Introduction

So you have done Java A and even B. Congratulations. Have you also found that Java offers something that is more than a programming language? With this assignment, we will try to wrap up your knowledge about Java, or any other object-oriented programming language you know (C++, Object Pascal, Python, Ruby ...), to get the essence of object orientation, to turn yourself from a craftsman back to a designer: Use object orientation as a tool to slice the complex into the simple, and put them back again in a structured way.

Schedule

<project xmlns:pg="http://www.logilab.org/namespaces/pygantt_docbook" id="monprojet">
<label>Object Orientation and Design Patterns</label>
<task id="uml">
  <label>Introduction to UML</label>
  <task id="lecture1">
    <label>Lecture: Introduction to UML</label>
    <duration>1</duration>
    <constraint type="begin-after-date">2005/02/21</constraint>
  </task> 
  <task id="task1">
    <label>Task 1: Practice UML diagrams</label>
    <duration>10</duration>
    <constraint type="begin-after-date">2005/02/21</constraint>
  </task>
</task>
<task id="ooad">
  <label>OOA and OOD</label> 
  <task id="lecture2">
    <label>Lecture: Object Reloaded</label>
    <duration>1</duration>
    <constraint type="begin-after-date">2005/03/07</constraint>
  </task>
  <task id="task2">
    <label>Task 2: Modeling your product</label>
    <duration>10</duration>
    <constraint type="begin-after-date">2005/03/07</constraint>
  </task>
  <task id="presentation1">
    <label>Presentation: result of Task2</label>
    <duration>1</duration>
    <constraint type="begin-after-date">2005/03/21</constraint>
  </task>
</task>
<task id="dp">
  <label>Design Patterns</label>
  <task id="lecture3">
    <label>Lecture: Design Patterns I</label>
    <duration>1</duration>
    <constraint type="begin-after-date">2005/03/14</constraint>
  </task>
  <task id="lecture4">
    <label>Lecture: Design Patterns II</label>
    <duration>1</duration>
    <constraint type="begin-after-date">2005/04/04</constraint>
  </task>
  <task id="task3">
    <label>Task 3: Redesign your software</label>
    <duration>10</duration>
    <constraint type="begin-after-date">2005/03/21</constraint>
  </task>
</task>
<task id="deadline">
  <label>Final deliverable: Deadline</label> 
  <duration>1</duration>
  <constraint type="begin-after-date">2005/04/06</constraint>
</task>
</project>

Week 1
Week 2
Week 3

Anchor(dp)

Week 4
Week 5
Week 6
Week 7

Final deliverables

Report of Task 2 and 3.
In your report, include a section to convince me that an object-oriented approach can also be useful for you as a intelligent product and service designer (not as a software designer or a programmer), or a section to convice me that the object-oriented approach is useless at all in design. Explain why, and if it can be useful, tell me how.
Deadline: Aprial 6, 9:00AM Sharp.

Online Resources

[http://www.uml.org/ Official OMG UML site], but do not try to read the entire UML specification.
[http://bdn.borland.com/article/0,1410,31863,00.html Borland's UML Tutorial]
[http://odl-skopje.etf.ukim.edu.mk/uml-help/ UML Totorial in 7 days] by Slobodan Kalajdziski;
[http://www.holub.com/goodies/uml/ Allen Holub's UML Quick Reference]
[http://www.phruby.com/stencildownload.html UML 2.0 stencils for Visio 2003]
[http://www.objectcentral.com/oobook/oobook.htm Essense of Object Oriented Programming]
[http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/ Object-Oriented Analysis and Design using CRC Cards]

References

[1]	F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, and M. Stal. Pattern-Oriented Software Architecture, Volume 1: A System of Patterns. John Wiley & Sons, Inc., 1996.
[2]	J.W. Cooper. The Design Patterns java Companion. Addision-Wesley Design Patterns Series, 1998. Free electronic copy available from http://www.patterndepot.com/put/8/JavaPatterns.htm.
[3]	B. Eckel. Thinking in Java. Prentice Hall, 3rd edition, 2002. Free electronic copy available from http://www.mindview.net/Books/TIJ/.
[4]	e. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns - Elements of Reusable Object-oriented Software. Addison-Wesley, 1995.
[5]	F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, and M. Stal. Pattern-Oriented Software Architecture, Volume 1: A System of Patterns. John Wiley & Sons, Inc., 1996.
[6]	D.C. Schmidt, M. Stal, H. Rohnert, and F. Buschmann. Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects. John Wiley & Sons, 1st edition, 2000.

JunHu: ObjectOrientedAnimals/200503 (last edited 2008-10-03 20:18:42 by localhost)