I really don't like using the word "engineer" to describe a programmer, largely because I don't want the engineering accreditation/licensing bodies to start thinking they have a claim on what I do.

Trust me, the engineering institutions wouldn't touch 99% of software with a bargepole.

Software engineering to me has always meant the software part of an engineered system, e.g. the software flying on an airliner or controlling a power station.

There's nothing wrong with being a programmer, it's an honest trade. Certified Java Enterprise Solutions Architects, on the other hand...

Well, the problem is that licensing often morphs into cartel building over time. The ABA and state bar associations are notorious for this, but they're hardly the only ones. Read about how various bar associations have pursued "cease and desist" injunctions against "We The People" (a company that fills out legal forms for a fraction of what a lawyer would charge) for a sense of how far this can go.

If engineers want to include a software component in their licensing of, say, civil engineers, that's fine by me. But it needs to be clear that they are licensing civil engineers who write software as part of their civil engineering work, not software engineers per se. Once they get their hands on software engineering, and discover how lucrative the newly formed cartel (er, profession) can be, you'd be surprised with how broad the scope of work that needs to be licensed can become.