Report 3 Discussion

From ALESwiki

UML Software Link http://www.visual-paradigm.com/product/vpuml/

Whats due on the Report 3?

Revisions & Corrections to Report 2
3.4.3 Object Model - The next 2 sub-sections contains information about the objects in our software. As you will remember, I believe the method we used to find models was to take one of our scenarios and find all the Nouns. This was a good start to find our objects.
- 3.4.3.1 Data Dictionary - This contains a loosely named list of objects, represented as classes. We give a loosely defined name, short description of its function, public methods and private properties(along with quick descriptions).
- 3.4.3.2 Class Diagrams - This is just a diagram of the above showing the connections and relations between the classes.

3.4.4 Dynamic Models - This looks like a detailed sequence diagram.

3.4.5 User Interface - Navigational paths and Screen Mock ups - A more detailed description of the navigation paths/menus of our system. Still no real name/details put in there.

We can all look at the RAD doc he posted.

http://www.cs.gsu.edu/~cscxlh/CSC4350_6350/samples/RAD_Bonus.pdf

http://www.cs.gsu.edu/~cscxlh/CSC4350_6350/samples/samplerad.htm

http://www.cs.gsu.edu/~cscxlh/CSC4350_6350/samples/SampleRAD2.pdf

Here is another link I found to some Object Modelling info:

http://www.ics.uci.edu/~djr/ics125/OMT.html

Table of contents

4.1 Entity Objects
4.2 Boundary Objects
4.3 Control Objects

[edit]

Object Model?

I copied the links to the links page.

Is the class model only the classes of the UI (window, button, slider) or the class model of the game as well?

[edit]

Class Model

Looking at the docs, it looked like the whole game. These are not specific classes and names. Just general class ideas and functionality,... I think.

[edit]

Model (john)

My vision of the system is as follows

From the very top, user level, what appears is a standard interface. The user can choose to create a new game, save a game, ask for help from standard browsers. If the user chooses to begin a game, then they go to the board editor. Once past the board editor, they can play the game.

The game window should allow for zooming, panning, and altering two properties of the water. Each of these activities will affect what the user sees, either by changing the field of view, expanding the field of view, or changing the color of the water (field).

User Interface

The user is primarily concernced with keeping the game simulation running. This means maintaining a balance between the various types of living creatures in the simulation. The living creatures are also part of the object model.

The Class Living Creatures may contain the methods reproduce and eat, a destructor and a constructor, various access methods for the statistics of the game and for game play--a predator must be able to access a prey's destructor either directly or through message passing, such as setting health to 0--and then data members such as health and age.

The algae class will probably be satisfactorily built with base class methods and data members. The herbivore and carnivore classes will both need additional methods to handle movement and sensing the presence of animals or plants in the immediate proximity. For example Carnivores may have a chase behavior built in, or preferably, chasing will be an emergent result of other methods.

[edit]