The Business of Software

For several years the SWEBOK project exists. It is the
"Guide to the Software Engineering Body of Knowledge". See www.swebok.org.

"The purpose of the Guide to the Software Engineering
Body of Knowledge is to provide a consensually
validated characterization of the bounds of the
software engineering discipline and to provide a
topical access to the Body of Knowledge supporting
that discipline."

"WHAT ARE THE OBJECTIVES OF THE SWEBOK PROJECT?
The Guide should not be confused with the Body of
Knowledge itself, which already exists in the published
literature. The purpose of the Guide is to describe what
portion of the Body of Knowledge is generally accepted, to
organize that portion, and to provide a topical access to it.
...
The Guide to the Software Engineering Body of Knowledge
(SWEBOK) was established with the following five objectives:

1. To promote a consistent view of software engineering
worldwide.

2. To clarify the place—and set the boundary—of
software engineering with respect to other disciplines
such as computer science, project management,
computer engineering, and mathematics.

3. To characterize the contents of the software engineering discipline.

4. To provide a topical access to the Software Engineering
Body of Knowledge.

5. To provide a foundation for curriculum development
and for individual certification and licensing material."

According to Steve McConnel -
"The main contribution of the SWEBOK is to bring clarity to software development research, discussions, and application."

"To organize something is to understand it." – Aristotle.

I think, Micro ISVs need to have "Software Business Body of Knowledge" - SBBOK, or "Business of Software Body of Knowledge" - BOSBOK.

What do you think?

Business of Software FAQ and Business of Software Wiki are good candidates for this.

As both a software developer and a software engineering graduate student, you're "reasons for the existence" of this project just don't mean anything to me. Why would I want to develop a universal consensus of SE? define the boundaries of what is and is not SE? what's next - organizing the union of software engineers? The simple truth is software engineering is not an engineering discipline like mechanical, civil, electrical, etc - despite what certain schools of thought try to promote. We're not bound by the same physical laws and we can't possibly consistently perform to the same standards. Our medium is infinitely more complex and we're going to make mistakes - perhaps software craftsman instead?

I think the "SWEBOK" is one company's view of what should be in the Software Engineering Body Of Knowledge.  It is NOT a consensus view, no matter how hard they pretend it's supposed to be.

There's LOTS of different views of what Software Engineering is.  EVENTUALLY a consensus will evolve out of many different organization's attempts to create one, IF such a consensus was useful.

Creating another 'pretend' consensus in another area has questionable value, as far as I can tell.

OK, I'll bite.

How is the Software Business different from any other Business?

A couple of differences that come to my mind right away:

1. Software products are intangible as opposite to most other products. It requires special preparation (analysis, specifications, etc) and EULAs

2. Software products are easily multiplicative as opposite to other products. It requires specific distribution and support mechanisms.

In fact, from a business point of view there is a big difference if you make a software product for yourself, for a particular customer, or for the whole world. I think most of the people involved in software development think like programmers, not like businessmen, and don't make the difference, which is the main reason for all software failures.

Do you want to see some comic answers about SWEBOK?
Take a look on "10 Most Important Ideas in Software Development" whitepaper from Construx company.
Idea #10.