HTW Berlin Fachbereich 4 Internationaler Bachelor Studiengang Internationale Medieninformatik (Bachelor) Informatik 3 Winter Term 2023/24
	Info 3: Informatik III Modern Software Engineering

Please work with the same team this week as last week. Give your report from Lab 3 to the group from which you obtained the use cases.

When we did the CRC-Card exercise last year you heard about a methodology for designing classes that is similar to the Booch method.

Take all the documents you have from the requirements phase. Underline all the nouns (in an English language text) in one color, such as blue Underline all the verbs in another color, such as red Underline all the adjectives in a third color, such as green. The blue words are all candidate classes—they will not all be classes, but they are candidates. Take a lot of pieces of paper or cards (not too small), and write each noun at the top of one of the pieces of paper and draw a line all across the paper underneath the word. The red words might make good methods—they just need to be assigned to classes. Divide the rest of the paper in two pieces—write the verbs on the bottom part. Decorate with attributes as deemed necessary, which get written on the top piece. The green words can be attributes or relationships—distribute them accordingly. Does your diagram make sense? Resort the cards and the methods, making new cards and ripping up the old ones, until finally your diagram seems to be consistent. Now use a class diagram drawing tool to make a class diagram that included all attributes and methods needed.

You will be preparing class diagrams for your Shopping List App as continued by another group in their Lab 3. First read through the changes and the sequence diagrams the other group produced. Do the changes make sense? Can you understand the sequence diagrams? Note this down in your report.

Make a list of all class candidates from the use cases and the sequence diagrams. Evaluate their suitability for classes based on the following criteria:

• Do the instances of the classes have attributes that are necessary in the system?
• Is the information about the existence of instances of the class necessary?
• Is the 'class' essential for the system?

Feel free to introduce new classes or throw out old ones! Make a list of candidate methods, including setter and getter methods for important information. Assign the methods to the classes selected.

Now draw a class diagram using any UML-Tool. We have some interesting ones such as Enterprise Architect on the lab computers. Play around with them! Make sure to include attributes, methods, and associations. Take your scenarios and use cases—can you walk them through the class diagram? Record any changes you needed to make!

Your report is due at 22.00 the day before your next CG exercise and should include all materials (including copies of the materials you obtained from the other group in an appendix), properly marked with the authors of these scenarios. Don't forget to include your own names on your report, and post the materials in the Moodle area for each team member.