So I'm writing on my big final school report, about a system I'm writing. And I have to do a damn analysis about the possibilities of using the perl app I'm writing in a business kind of way (and oh sweet lord, I hate theory).

The system is a CGI that processes form input & puts it in a database. The data being similar to M$' SmartTags - ie. adding links to pages, so that when run through the system, the links are added.

Anyway, I have come up with a model where I could lease out access to the database (remember, this is theory, so that prolly won't happen), to search engines, so they could use the link data for their result.

But I also have to write a SWOT-analysis (Strengths, Weaknesses, Opportunities, Threats of/to the model). And I can't think of a single.

I want to die. I hate school. I quit.

Does any of you have any suggestions?

Replies are listed 'Best First'.
Re: SWOT-analysis
by osfameron (Hermit) on Oct 31, 2001 at 17:05 UTC
    Don't give up: sure it seems like a business-theory waste of time but there are some useful benefits: like being able to persuade people to actually use your code, and give you jobs!

    Strengths

    You know this! - What does your app do? You gave some details above. Now expand on why that's useful, and how well your application does it.

    Weaknesses

    You know this! - Where could your code be improved? How does it fail to leverage CPAN modules? Look at what other options exist (MS Smart Tags that you mentioned for example) and see what that does better.

    Opportunities

    You know this! - Sell/lease the code to Search engines, as you said above. Now think some more: who else would want this? Could a content based site like perlmonks use it? Could you integrate it into a "Site builder" type application for free web hosting?

    Risks/threats

    This is the hard one (for me anyway). What will prevent you from using (and making profit from the code). Does MS have a patent on Smart Tags? Assess this: how similar is it to the competition? Does the competition already have a loyal user base? Will it be difficult to persuade them to switch.

    Then you should go back and see how these things link: e.g. Risks: It will be difficult to persuade clients to use my system instead of another, so... what were those Strengths again?

    Hope this helps

    Cheerio!
    Osfameron
[reply]
      Thanks, that does help indeed. I've been stuck for a while, but I definitely have something to work with there!
[reply]
Re: SWOT-analysis
by davorg (Chancellor) on Oct 31, 2001 at 17:16 UTC

    Also under risks it's probably worth looking at security risks. How secure is your app? Do you use taint mode? Will installing your app compromise a site's security?

    --
    <http://www.dave.org.uk>

    "The first rule of Perl club is you don't talk about Perl club."

[reply]
      As often davorg is right, common spots to examine when talking about security are :
      • Possible denial of service
      • Access control
        How to restrict/setup rights to access/modify/delete data or resources.
      • Authentication
        Especially way to bypass it or impersonate someone.
      • Data integrity
        Protect your data againts corruption deletion...
        I'm not only talking about physical integrity but also about logical one (to prevent injection of fake data or the creation of an incoherent state in your data)


      "Only Bad Coders Code Badly In Perl" (OBC2BIP)
[reply]

Back to Meditations