Case 3 – Object Serialization

Think-Design-Write Test-Code

5 Days

Having successfully completed your first piece of work your boss now approaches you with some more work to do.

She tells you that the data you have been keeping in memory needs to be made persistent. “In other words”, she says, “it needs to be stored to disk when the application ends and then read back in when it starts up again”.

During your discussion she says that the engineers for the application have decided that the Chat object you created in your last piece of work needs to be modified so that it contains an additional method and an additional constructor (See the description below).

Chat object changes:

• Method – save: parameter 1 – String – file name
• Method – constructor: parameter 1 – String – file name

You boss says that the messages need to be stored to disk and, if they have been stored previously, read back in when the Chat class is instantiated. She also says that you should make any adjustments to the UML Class diagram, the test matrix, and the JUnit tests that are needed for this new functionallity.

As she is leaving she says,”Could you get this done by the end of today? I’ll stop by.”

• Deliverables
  1. A UML class diagram for your solution
  2. A UML sequence diagram for your solution
  3. A modified test matrix
  4. A modified JUnit test
  5. An assessment case
  6. A presentation of your teams solution to the problem
• Resources
  1. Serialization
  2. UML Sequence Diagrams

  3. 

     An example of an iterative sequence diagram.

  4. Java API: ObjectOutputStream, ObjectInputStream
  5. Visual Paradigm