🔒 Locked

design documents for games help needed

Started by Ultimate_Fusion Dec 22, 2006 at 5:12 AM 3 replies 1.2k views

Original Post

Dec 22, 2006 at 5:12 AM

I didn't know where to post this so but this had softwre engineering design on the info. I am doing my final year project and need to do some design documents for my programme. I say programme, its more of a game/simulation. I need help on which UML diagrams I should include (listed below) e.g. I normally do activity diagrams with a simple start finsh and some stuff happens in the middle, where my program starts anything could happen and there isn't a definate finish. Should I invent my own diagrams to get my point across? and any advise on other documents or comments needed in the design would be gratefull. cheers UF UML diagram types Structure Diagrams emphasize what things must be in the system being modeled: -Class diagram -Component diagram -Composite structure diagram -Deployment diagram -Object diagram -Package diagram Behavior Diagrams emphasize what must happen in the system being modeled: -Activity diagram -State Machine diagram -Use case diagram Interaction Diagrams, a subset of behavior diagrams, emphasize the flow of control and data among the things in the system being modeled: -Communication diagram -Interaction overview diagram (UML 2.0) -Sequence diagram -UML Timing Diagram (UML 2.0)

Ultimate_Fusion

Dec 22, 2006 at 8:02 AM

thanks that was a big help.
justa quick question about DFD.

I have done them on systems beforeand have had multiple levels 1,0 etc.

I have 2 opponents who fight each other.
one can move attack, die
the other can runaway, hide, attack and protect.

the data flow is mostly internal. Is it worth doing one?
how would I go about doing it.

thanks in advance

huahsin68

Jan 8, 2007 at 11:34 PM

To Ultimate_Fusion:

By replying your question, I think U probably need a UML instead of DFD in this scenario.

My recommendation to UML:

In this scenarion, U need a class and sequence diagram. Class diagram helps U describe in detail about your object. E.g. attack, hide, protect, etc. Whereas sequence diagram helps U describe about what will happened for an object after an event is trigger. E.g. If component A attack component B, component B lose 1 point. It is more presentable in front of U.

My recommendation to DFD:

It is not suitable to use DFD in this scenario as it is too complex to describe in details. As U are require to describe every single data that pass through each object.

Conclusion:

U can use both UML and DFD together. U can use UML for the "first" view (summary) on this scenario. If U require "second" view (detail), and U have more time to develop one, then U go ahead to DFD.

THanks @!

Emmanuel Deloget

Jan 9, 2007 at 10:22 AM

I usually begin my designs with "use case diagrams" (UCD), because every other thing directly come from these. UCD usually tells you some basic informations about the program flow and data flow. When UCDs are completed, I typically detail things in Sequence Diagrams (because they are quite simple; to be honnest, that's pretty much the only dynamic diagram I use often), then I do some static analysis (most of the time, Class Diagrams with little details (c'mon, I have no time to waste on giving the full interface of every single method at this point; classes and main methods names are enough (what? why do you say I'm lazy?))).

By anything could happen, is there any chance that you speak about marrying Hulk? [grin]

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.