What does software engineering mean to you?

damnyanks

Just curious as to what peoples views on software engineering are? How do you view it ?

People and companies seem to have a different belief system on what it actually stands for. Some think its someone that actually develops software (A la software development why engineering eh).

Others have the belief that its the actual efficient engineering approach to software, specifications standarisation etc.

I know its not exactly the best example but it seems apparent through third level education that the matter is still confused. There exists many software engineering degree's in Ireland and the UK (UK specifically, think only 2 in Ireland) That are labelled Software engineering but if you look at the course content the courses differ quite a bit.

I study software engineering in the form that it is an actual engineering approachl. I read a book a few years ago by Steve McConnel which changed my view on software... that said I didn't really have a view at the time (First year at college )

RicardoSmith

Engineering - "The application of scientific and mathematical principles to practical ends such as the design, manufacture, and operation of efficient and economical structures, machines, processes, and systems."

How about that? From dictionary.com

In my experience. Most degree courses, in any discipline differ widely in content.

Same with software engineering, both the course and the job.

Hobbes

Developing the software is just one step to an engineer.

kenmc

Tricky one to pin down. I take it to mean that a software engineer understands how the design choices s/he makes affects the system they're working on and the interaction between components (by components it could be other sw modules, chips, even end users) in the system. Any coder if given a design spec can code, but may not necessarily understand the reason for doing it in a particular way.
In the same way that any brickie can build a wall, but the architect/engineer has specified it in a particular way for a reason which may not be obvious to the brickie.

Stuff like choice of OS, memory management model, priority of tasks - choices that need to be made by someone, but if you get it wrong will really make life difficult - those are the sort of things that the SW engineer should be able to do to differentiate him/herself from programmers.
My 2 cents anyway.

Hobbes

A software developer is just someone who creates software. They could design it, document it etc.

Software engineering tends to focus around processes, project management and planning as well as coding.

For example. Unit Testing would be more engineering side as it requires planning and development but does not go into the finished code project. However it is a system that can have huge benifits on coding.

Costing documents would be another. A developer can get by without ever knowing what this is, but all serious development should use them.

BizzyC

I actually study software engineering in DCU.
I find that the course is actually a bit of both.
Our subjects are split between those that specialise in the development of code, and programming languages/approaches, and those that specialise in planning and performance of programs.

scojones

Hobbes wrote:

A software developer is just someone who creates software. They could design it, document it etc.

Software engineering tends to focus around processes, project management and planning as well as coding.

For example. Unit Testing would be more engineering side as it requires planning and development but does not go into the finished code project. However it is a system that can have huge benifits on coding.

Costing documents would be another. A developer can get by without ever knowing what this is, but all serious development should use them.

Nail on head.