creating a software product

Question

4.40/5 (4 votes)

See more:

Dear All,

I have mostly work on the projects where the requirements are provided by the clients and we implement those into predefined architecture / solution.

I want to learn the way to create a software solution that can be marketed as a product and not as a framework. For example, MySQL, .Net, Oracle e-business suite etc are products, they have their release plans, upgrade-downgrade methodology etc.

Could anyone guide me from where to start, and what approach should I take to achieve this ?

Any site reference, tutorials, e-books etc would also be helpful.

(In short, need to learn and implement the end-to-end life cycle of the software as a product)

Thanks & Regards,
Niral Soni

Posted 2-Sep-11 6:26am

Niral Soni

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Answer 1 · 2011-09-02T06:52:00

Intially, I don't think there would be too much difference between a product and a solution (client).
The only thing perhaps is, you need to know what product you are building. So you could pick up, say, an online shopping website as your product.

The way you architect it or design it would be fairly similar to the client solution.
The difference would be in marketing and also in the enhancement / service pack / next release cycle.
Remember, your product has no client and you intend to generate revenue from it, so that part is not easy.

You then would need to know what you need to put into it for the next release.

There would be other minor details you would need to look at during the full implementation cycle but the basic concepts would be similar.