Sofware Engineering

[LeonX]

Hi everyone ...

1. Why there is no topic about this in here?
2. Anybody here can help me in this?
3. Usually I made a program without designing first, I know this bad, and I like to start doing this, and maybe I'd like to use UML in Microsoft Visio for this. The problem is where should I start? Anybody here have the e-books or tutorial about UML but with a lot of examples (in practice examples, you know ..., a sample system and the UML design).

Thanks a lots.

Regards,
Ferry

[LeonX]

hi ... dglienna ... robdog888 ... martinliss ... everyone ...
anyone can help me about this?

[baviskarmitesh]

bad practice

[Joacim Andersson]

hi ... dglienna ... robdog888 ... martinliss ... everyone ...

Well, I'm not dglienna, RobDog888, nor MatinLiss so I guess I fall in the everyone group

1. Because nobody has started one
2. I'm pretty sure someone can. However you should ask more specific questions about it.
3. UML is a huge topic, I don't know of any e-books but you can obtain all information about it here.

[szlamany]

I personally question whether you can be taught a methodology about program design.

Maybe that's because I've been doing this for over 25 years.

I was lucky enough to be part of a large development team back in the 1980's that produced a nationally sold product. The R&D techniques learned there shaped my career. When that business was purchased by a larger, more structured company, the "methodologies" they implemented killed the creativity and originality of the developers.

I've owned my own software house since the late 1980's and have had many junior programmers come through the shop. What we have taught them was lightyears ahead of what they learned in high school or college classes.

When we left the mainframe world 4 years ago and jumped into VB and MS SQL server, we spent over a full year developing and throwing away prototypes until we landed on a proper design that we could develop, support and enhance.

I do not think there is an easy answer to your question.

[LeonX]

so, what is your suggestions for me, szlamany?

[dglienna]

Practice, and study. Let others see your methods, and pay attention to their comments. I have always been able to see an app before starting to develop it. I often "program in my sleep" and wake up with a solution that had been bugging me the night before.

I've gone thru classes that reqired flowcharts for everthing, and even graded them. Just having them was enough, as long as your design followed the flowchart and did the task. No better grade was given if it was better or worse.

I always got straight "A"'s in computer classes (with the exception of C++ the first semester ), but was surprised that back in the day, anybody that tried to do the work usually passed. Just passing classes doesn't make you good at design. I agree that it may not be possible to teach good design.

You will know if you are good based on the amount of times you have to through everything away and start again. It happens very rarely to me, and never once I've started coding.