Differences between revisions 64 and 65
Revision 64 as of 2005-03-07 09:07:51
Size: 8390
Editor: dyn176206
Comment:
Revision 65 as of 2005-03-07 09:46:45
Size: 9386
Editor: ID00243
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

{{{#!Gantt view-end=2005/03/14,
<project xmlns:pg="http://www.logilab.org/namespaces/pygantt_docbook" id="monprojet">
  <label>Specification</label>
  <task id="module">
    <label>Module Gantt.py</label>
    <task id="func1">
      <label>Implementation Parser</label>
      <duration>2</duration>
      <constraint type="begin-after-date">2005/03/03</constraint>
    </task>
    <task id="func2">
      <label>Testing</label>
      <duration>3</duration>
      <constraint type="begin-after-date">2005/03/05</constraint>
    </task>
  </task>
  <task id="documentation">
    <label>Documentation</label>
    <task id="doc_func1">
      <label>Documentation Gantt.py</label>
      <duration>1</duration>
      <constraint type="begin-after-end">func1</constraint>
    </task>
    <task id="doc_func2">
      <label>Examples</label>
      <duration>3</duration>
      <constraint type="begin-after-end">func2</constraint>
    </task>
  </task>
</project>
}}}

<project xmlns:pg="http://www.logilab.org/namespaces/pygantt_docbook" id="monprojet">
  <label>Specification</label>
  <task id="module">
    <label>Module Gantt.py</label>
    <task id="func1">
      <label>Implementation Parser</label>
      <duration>2</duration>
      <constraint type="begin-after-date">2005/03/03</constraint>
    </task>
    <task id="func2">
      <label>Testing</label>
      <duration>3</duration>
      <constraint type="begin-after-date">2005/03/05</constraint>
    </task>
  </task>
  <task id="documentation">
    <label>Documentation</label>
    <task id="doc_func1">
      <label>Documentation Gantt.py</label>
      <duration>1</duration>
      <constraint type="begin-after-end">func1</constraint>
    </task>
    <task id="doc_func2">
      <label>Examples</label>
      <duration>3</duration>
      <constraint type="begin-after-end">func2</constraint>
    </task>
  </task>
</project>

/!\ 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.

TableOfContents

(!) 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

Week 1
  • Lecture: An introduction to UML (21-02 15.45-17.30 HG 2.80)
    • [attachment:UMLintro_presentation.pdf Slides], for viewing on screen
    • [attachment:UMLintro_handouts.pdf Handouts], for printing, with additional details
  • Reading:
  • <!> Task 1, to be finished in 2 weeks:

    Week 2
  • No lectures.
  • <!> Continue Task 1.

  • Week 3
  • Lecture: Object oriented analysis and design (OOA & OOD) (07-03 15.45-17.30 HG 2.80)

  • Reading:
    • [http://www.objectcentral.com/oobook/oobook.htm Essense of Object Oriented Programming] Several chapters of this book by Wampler are available online. Chapter 2 is a very good overview of object-oriented programming.

    • [http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/ Object-Oriented Analysis and Design using CRC Cards] CRC (Control, Responsibilities, and Collaborators) cards are an important tool for identifying and defining the classes you need for your program. They are an excellent low-tech method requiring only index cards.

  • <!> Task 2, to be finished in 2 weeks:

    • Modeling (not programming!) a product designed by yourself, using use case diagrams, class diagrams, sequence diagrams and activity diagrams.
  • Anchor(dp)

    Week 4
  • Lecture: Design Patters I: Observer, Iterator, Singleton, Factory ... (14-02 15.45-17.30 HG 2.80)
  • Reading: [http://www.patterndepot.com/put/8/JavaPatterns.htm The Design Patterns java Companion]

    • You may also refer to the following famous books (if you are lucky, you may grab a copy from the university library):
      • GoF: [#Gamma+HelmETAL-DesiPattElemReus:95 Design Patterns -- Elements of Reusable Object-oriented Software]

      • POSA 1: [#BUSCHMANN:1996 Pattern-Oriented Software Architecture, Volume 1: A System of Patterns]

      • POSA 2: [#Schmidt+StalETAL-PattSoftArchVolu:00 Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects]

  • <!> Continue Task 2.

  • Week 5
  • No lectures.
  • Presentation: Everybody gets 5 minutes to present the results of Task 2. (21-03 15.45-17.30 HG 2.80)
  • <!> Task 3, to be finished in 2 weeks

    • Find a program you wrote before, for example, the program you wrote for Java A or Java B, or any other programs in any language

    • Read your program again.
    • Now, how would you like to impprove your design using a object-oriented approach?
      • Show me your original code,
      • identify the problems if there is any,
      • redesign it using object-oriented approach,
      • apply design patterns in your desgin,
      • try to communicate your object-oriented new desgin with me using UML diagrams.

        /!\ Implementation of your new design is appreciated, but not obligatory.

    Week 6
  • No Lectures
  • <!> Continue Task 3

  • Week 7
  • Lecture: Design Patterns II: Interface architectures (MVC, PAC) (03-04 15.45-17.30 HG 2.80)
  • Feedback, Q&A

  • 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 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

    References

    @BOOK{Buschmann+MeunierETAL-PattSoftArchVolu:96,
      author       = {Buschmann, F. and Meunier, R. and Rohnert, H. and Sommerlad, P. and Stal, M.},
      title        = {Pattern-Oriented Software Architecture, Volume 1: A System of Patterns},
      publisher    = {John Wiley & Sons, Inc.},
      year         = 1996, 
    }
    @BOOK{Cooper-DesiPattjavaComp:98,
      author       = {Cooper, J.W.},
      title        = {The Design Patterns java Companion},
      publisher    = {Addision-Wesley Design Patterns Series},
      year         = 1998,
      note         = {Free electronic copy available from \url{http://www.patterndepot.com/put/8/JavaPatterns.htm}},
    }
    
    @BOOK{Eckel-ThinJava:02,
      author       = {Eckel, B.},
      title        = {Thinking in Java},
      publisher    = {Prentice Hall},
      year         = 2002,
      edition      = {3rd},
      note         = {Free electronic copy available from \url{http://www.mindview.net/Books/TIJ/}},
    }
    
    @BOOK{Gamma+HelmETAL-DesiPattElemReus:95,
      author       = {Gamma, e. and Helm, R. and Johnson, R. and Vlissides, J.},
      title        = {Design Patterns -- Elements of Reusable Object-oriented Software},
      publisher    = {Addison-Wesley},
      year         = 1995,
    }
    
    @book{BUSCHMANN:1996, 
      author="Buschmann, F. and Meunier, R. and Rohnert, H. and Sommerlad, P. and Stal, M.",
      title="Pattern-Oriented Software Architecture, Volume 1: A System of Patterns",
      publisher="John Wiley & Sons, Inc.",
      year=1996,
    } 
    
    @BOOK{Schmidt+StalETAL-PattSoftArchVolu:00,
      author       = {Schmidt, D.C. and Stal, M. and Rohnert, H. and Buschmann, F.},
      title        = {Pattern-Oriented Software Architecture, Volume 2:  Patterns for Concurrent and Networked Objects},
      publisher    = {John Wiley & Sons},
      year         = 2000,
      edition      = {1st},
    }

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