Analysis

[carnaz]

Hi there, ;)

I don't know whether my topic is concerning to this forum (hope, admins will like it), but maybe it would be interesting for more rookies like me. I have serious problem with design of programming concept. ( I had to remake my last project twice since I started) I'm not experienced with any kind of analysis. But also, I can't bother too much with studium and pre-coding analysis.:( I don't work on huge projects, or in team, so I need a compromise between quick and simple application and optimal (analyse guided) design.

Does anybody know easy and simple standard or language to make pre-coding decisions easier? I allready started with UML, but till now I don't see a significant difference.

carnaz:cool:

[Kheun]

UML is a standard meant for documenting your design. It doesn't really influence how you design your software. However, if done properly, UML helps others to understand your design intention.

Here are some basic guidelines for good design.

- Coupling between classes are needed in order for software to work. However, we MUST reduce coupling as it reduces complexity, making it much easier to maintain.
- High cohesiveness. One class only do a set of related tasks. Can avoid producing a BLOB class.
- Providing good abstraction.
- Information hidding. It also helps to reduce coupling. If information are not hidden, other classes may know and directly using the content of your class. As a result, if there is a change in your class, the change will propogate to other class (a.k.a ripple effect).

It would be great if other could add to the list.

[Linenoise]

Microsoft put out a book called Code Complete about how to write concise, clear code. It's not so much on the high level design, but more on the code design side, but it's still a good read (even though it's by M$.. it's irony!).