Common Platform Basis: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
Note that only 2 of the above are actually development packages, and only 1 a really full featured one at that, but this is the way people currently shop for the basis for thier development needs, so we have to accomodate it. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative. | Note that only 2 of the above are actually development packages, and only 1 a really full featured one at that, but this is the way people currently shop for the basis for thier development needs, so we have to accomodate it. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative. | ||
<br><br> | <br><br> | ||
What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and had the properties listed in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with said achievement. Nonetheless, unless such a choice presents and full blown conflict with the attainment of our [Total Quality Management], we can accomodate it. | What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and had the properties listed in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with said achievement. Nonetheless, unless such a choice presents and full blown conflict with the attainment of our [[Total Quality Management]], we can accomodate it. | ||
Revision as of 17:39, 14 April 2007
In addition to the Domain Content Mgt. System (DCMS) variants, the following application development packages are 'standard' with us and can be used to initialize your Enterprise domain:
- Director MX (Flash Dev)
- JBoss (J2EE, Java, JSP, Tomcat, etc.)
- Joomla
- LAMP
- .Net/Visual Studio 8 (ASP, ASPX)
Note that only 2 of the above are actually development packages, and only 1 a really full featured one at that, but this is the way people currently shop for the basis for thier development needs, so we have to accomodate it. This focus is not without consequences but it cannot be helped because shopping for what you think you need instead of what you actually need is a buyer's prerogative.
What you actually want, and may not know it, is a system that achieves your functional goals (assuming these are reasonable and feasible) and had the properties listed in the Value Prop(osition). In general what you may have think is the 'platform' choice or package du Jour generally has little to do with said achievement. Nonetheless, unless such a choice presents and full blown conflict with the attainment of our Total Quality Management, we can accomodate it.
