Toolset pros and cons: Drupal

[Jay Collier]

As we're envisioning the attributes of an IKE, it makes sense to be
considering the various toolsets that might be evaluated to support
our master plan.

Since Drupal came up first, why don't we start there? Jeff wrote this
in another thread:

"One of the biggest struggles Smith College has with cms products such
as drupal is on the design side. PHP templating is not as easy as
dreamweaver html so there is a learning curve there.

"Also, if you lose your database for any reason you loose your whole
site whereas with individual pages you are fine unless the server goes
down.

"So I am still wondering what the best solution is to offer the
easiest
way for departments across campus to create and update pages on their
own without disturbing menu and navigation look and feel.

Other general observations with Drupal?

[Steve Moitozo]

I would suggest that to evaluate tool sets at this point (before developing the
software architecture) would be premature. It's the software architecture that
provides the standard against which tool sets can be evaluated.

To do it the other way round would be to embrace the notion that if all that
mattered was functionality any software architecture would do, including a
single script with ten million lines of code. In other words if all that
mattered was the ability to create, manage, and publish content via HTML and RSS
than everyone should use Drupal. Drupal is a great solution for the
organizations whose quality attribute requirements match what Drupal provides.
But if you don't know what your quality attribute requirements are how can you
know whether Drupal is right for your environment? You could grab Drupal and
take your chances or you could figure out what your quality attribute
requirements are and then evaluate different solutions, including Drupal.

That being said, I do understand the need to evaluate what is possible with
current technology in order to give appropriate input in the process of
developing requirements and the software architecture. However, there is a
temptation to jump into the evaluation of solutions before doing the proper up
front analysis. When this happens the draw to implement something before fully
understanding the impact of the solution becomes great and many organizations
lack the discipline to resist. I argue that this is a large reason why these
kinds of software solutions fail.

-S2
--
Steve Moitozo II
Software Architect and Manager of Internet Software Services
Bates College

"Opportunity is missed by most because it is dressed in overalls and looks like
work." --Thomas Edison

Are you an Outlook user having problems replying to my messages? Read this:
<http://www.geekwisdom.com/dyn/outlookusers>

> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "IKE Project Forum" group.
> To post to this group, send email to ikepr...@googlegroups.com
> To unsubscribe from this group, send email to ikeproject-...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/ikeproject?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>

[Jay Collier]

Good points, Steve.

I was, indeed, suggesting that there is a benefit to understanding the
broad realms as well as experiment with actual experiences, as they
are demonstrated. For example, I am interested in the ways online
experiences are faciliated through Google Sites and Groups. That
doesn't mean that it's time to jump to a detailed analysis. I fully
agree that evaluation of specific functions shouldn't happen now.

I think we can stay at the vision level and your message clearly
reinforces the reasons why.

-Jay

> smoitozo.vcf
> 1KDownload
>
> smime.p7s
> 7KDownload

[Jay Collier]

It just occurred to me that the title of this thread didn't fully
capture my intention.

What phrase should we use to describe our overall impressions and
experiences provided by major kinds of environments that are already
deployed?

Perhaps its just me, but I find it helpful to demonstrate existing
experiences to skeptical constituents, and then describe the direction
from there toward a larger vision.

Suggestions welcome.

-Jay

[Jim Hart]

Interesting conundrums, and ones vary by individual. Abstract?
Concrete? Which comes first for you? And at what point in the
process? How can we make current technology inform but not limit our
thinking?

> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "IKE Project Forum" group.
> To post to this group, send email to ikepr...@googlegroups.com
> To unsubscribe from this group, send email to ikeproject-

> unsub...@googlegroups.com