Discussion Locked

The road to be software engineer

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear all

I am a programmer (BS in Computer Science). I want to learn Software Engineering in the best way (regardless of the platform) as a self learning.

What books do you suggest for me?
Which book to start with and the second ... etc?

Someone suggeted to me the following two books in order:
1-Practical software Engineering "The Case Study Approach" by Leszek Maciaszek, Bruc Lee Liong
http://www.amazon.com/exec/obidos/tg/detail/-/0321204654/ref=ord_cart_shr/104-2616448-6850358?%5Fencoding=UTF8&v=glance

2-Patterns of Enterprise Application Architecture -by Martin Fowler
http://www.amazon.com/exec/obidos/tg/detail/-/0321127420/ref=ord_cart_shr/104-2616448-6850358?%5Fencoding=UTF8&m=ATVPDKIKX0DER&v=glance

Do you have any other tips ?

Best Regards

4 replies

by tony hopkinson

What a software engineer is, is quite fuzzy.
Essentially it's a high level developer, some one who can not only translate into useful code, but come up with or contribute to the design itself.
It you look at System Architect as a strategist, say choosing service oriented architecture, then the software engineer is the tactician.

The Design Patterns in (C++, C#, Java, etc) books are good, but there is more to being an engineer than this, I'd recommend the Pragmatic programmer as well.

One thing you should note if you learn this stuff you'll be a programmer with design potential, you need to get some code in the real world under your belt.

It's good application of the theories that make a software engineer. When I read design patterns, a lot of them I'd already done, or considered, even though I didn't know the buzzwords.

You would have to be deity's gift to IT, to convince me that you could be a software engineer without senior programmer / developer experience in some complex projects , at least three years I would, say perhaps more.

by drray

Do a Google search on SWEBOK for the Software Engineering Body of Knowledge. This "approved" list of required concepts will define the discipline for you.This was the body of knowledge I used as a guide when I created an undergraudte degree in Software Engineering.

Dr Raymond Carpenter

by pioneering

The latest "SWEBOK" document outlines, in general terms, the entire discipline of Software Engineering. This includes the "SDLC" (Software Development Life Cycle) from requirements generation to testing and deployment. But this is not the whole story. There is also domain-specific knowledge you should have as well as being well versed in Computer Science. You may also want to jump into the deep end of the pool by visiting: http://www.sei.cmu.edu/

by jslarochelle

to be a good software engineer.
Reading on patterns is good. The best starting point for this is a book that covers the most fundamental patterns. This can be the classic by the "four amigos": Design Patterns by E. Gamma, R. Helm, R. Johnson, J. Vlissides.
For a more pedagological approach at those patterns check out: Head First Design Patterns by Eric Freeman and Elizabeth Freeman. Some people find this last book childdish but I don't agree with them. It is an excellant book that gives you the equivalent of some practice (more on that later) if you do complete the exercises.
The book by Martin Fowler is good for enterprise application development. I will recommend at least another one: "A system of patterns" by Buschman, Meunier, Rohnert, Sommerlad and Stal. This one is very good because of its presentation of architectural patterns like "Layers", "Blackboard" and others.
Because books on pattern are the equivalent of condensed experience you should prepare to read other books on the subject.
Because most software development is "Object Oriented" development these days you should prepare to perfect your OOD (or OOP) skills. If you have not already read a good bood on OO development I suggest: Object-oriented Analysis and Design by Grady Booch. The second edition that I have dates back to 1994 however it is still a very good book. Other good books on the subject include:
"Object-Oriented Design Heuristics" by A. J. Riel
"Object Design" by R. Wirfs-Brock and A. McKean
The books I have listed are complementary. They present different aspect or approach to OOD.
As if this was not enough, you will need to read books on other aspect of development and different technologies. If you plan to work on large project you will need a good knowledge of the development cycle as well as the different skills involved. If you don't already have a good book on Software Engineering I recommend "Software Engineering" by Roger S. Pressman. This will give you a birds eye view of every aspect of the process. It is also a good reference when you need to refresh a concept or specific aspect of software development.
I agree with others on this thread that have mentioned that there are limits to what you can learn in books. You will have to do your howework: design a lot, program a lot, make errors, fix your errors, ...
However, I also think that software development is one domain where book-learning is important and unavoidable.
Be patient and good luck!
JS

This discussion is closed to new replies.