The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Software Engineering Approach

Hi all,

Can anyone suggest a good book on Software Engineering?

I completed my degree just a few months back and completely ignored this subject all through my degree. Moreover, the company I am working in is a small firm and there is no methodical approach for a project here either.

But I want to learn the basics of SE, and relate it to practical projects. A realistic meaning of Prouct, systems, project and the full understanding of Life Cycle.

I have Roger S. Pressman's SE book, but I was not able to relate all the concepts described in it to the real world.

So, I am looking for any other suggestions regarding this. Any ebook, paper book, ; or being more general - How to understand all these concepts?

Thanks 

VISHAL
Vishal Lamba Send private email
Tuesday, May 02, 2006
 
 
Everyone needs to read Software Tools ( http://tinyurl.com/nhxbn ).  It's not SE on a grand scale but the principles are indispensible.
Chris Nelson Send private email
Tuesday, May 02, 2006
 
 
God help you, but it sounds like you actually want to read the SWEBOK:

http://www.swebok.org/
Jeff Mastry Send private email
Tuesday, May 02, 2006
 
 
It might be more practical to focus on passing the first 10 items of the Joel Test and read books later.

http://www.joelonsoftware.com/articles/fog0000000043.html
Matt Brown
Tuesday, May 02, 2006
 
 
One of the project-oriented books by Steve McConnell would probably be good place to start.  Check the 'Books' link at his site:

http://www.stevemcconnell.com/
Herbert Sitz Send private email
Tuesday, May 02, 2006
 
 
Vishal, SE is more art than anything else right now and I've met few people who know what they are doing. Those who do place getting the best people much higher than following a methodology.

I would read Peopleware, Code Complete, and Slack to start out with and I would start a Friday book club at your work to discuss these and other books. Then, the team, being educated, can select their own methodology and will be intelliegent enough to figure out if it is actually working for them and if not what should be changed.
Art Wilkins
Tuesday, May 02, 2006
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz