Pitching AlphaSimple

Not clear on what AlphaSimple is about? Isn’t the value we aim to provide clear?

Does this 7-slide pitch deck (including title) help you understand it?

If not, please let us know. Or if it is clear, but you don’t think it would work, please help us understand why. Or even if you think it is right on the money, some reassurance is always welcome.

Note that the web site hasn’t yet changed to reflect the more recent focus on code generation that the slide deck hints at (in addition to the existing focus on requirements and solution design validation). That is on our to-do list. Expect significant changes (messaging and service features) this Spring.

This is the inaugural post on the “business of software” category. Expect many more in the future as we work on turning AlphaSimple into a product that fulfills our mission: to bring model-driven development to the masses, and stopping hordes of developers from writing so much code. Stay tuned.

Email this to someoneShare on FacebookShare on LinkedInShare on Google+Tweet about this on Twitter

5 thoughts on “Pitching AlphaSimple

  1. Vincent Hanniet

    May 7, 2011 at 2:12am

    Hi Rafael,
    Some comments:
    - requirements are not only business requirements. How do you manage technical or enterprise requirements? (e.g. security, performance, urbanization…)? Everything that is not directly related with the business domain… But matters!
    - the pitch deck talks about why and goals of AlphaSimple, not about AlphaSimple itself. So at the end we don’t know what it is exactly
    - I went on http://alphasimple.com and didn’t find what is in the pitch. Found a technical prototyping tool. Fine but: what if I want to build the real application? Where is the “user” view?

    I fully adhere to the mission: to bring model-driven development to the masses. Still to precise what part of the mission AlphaSimple fulfills.

  2. rafael.chaves

    May 11, 2011 at 12:33am

    Hi Vincent, thanks for stopping by and taking the time to comment.

    On business domain vs. technical requirements:

    AlphaSimple is strongly biased towards business domain requirements, and for a good reason. They are the kind of requirements developers need the most help with BAs and users, they are very communication intensive. Nailing those down as early as possible is key for the project success.

    In my view, technical requirements pose less of a challenge. Developers are familiar with them (as they occur repeatedly across domains), and solutions are well understood. Even though AlphaSimple doesn’t help with eliciting or validating technical requirements, it does provide an efficient approach for addressing them (with code generation). I do mention that when presenting it, maybe should have something in that regard on a slide.

    On goals of AlphaSimple: note taken, will try to improve that.

    On AlphaSimple being a prototyping tool. Yup, that is currently the fact that is currently available/promoted. We are working hard on the side of the equation: building (generating) the application code from a solid model.

    “Where is the “user” view?”

    Sorry, not sure I understand this question. Are you talking about the user interface of the application? If so, at this point that is out of scope, and users can use tools like Balsamiq for sorting that out.

    Thanks again for the feedback, Vincent, really appreciated.

  3. Vincent Hanniet

    May 11, 2011 at 3:46am

    Hi Rafael,
    “User view”:
    From a user standpoint I’d like to work on the GUI. That is often the more meaningful way to “touch” the news application. And it’s surprising not to be able to do it as AlphaSimple home page tell “Simply design the domain model… and the user interface is ready to test”. I so understand that the way the GUI is designed is not reachable by users… Hum…
    And also, working on UI mockups with users
    is a way to work on business needs (at least for the front-end).

    How do you compare AlphaSimple to, say, bonitasoft (http://www.bonitasoft.com/)?

    My thought for today: Simple business with simple solutions is not that simple! ;D
    Sounds good. I will twitt it!
    Go on Rafael!

  4. rafael.chaves

    May 11, 2011 at 8:28am

    Hi Vincent,

    Actually, AlphaSimple generates a generic UI for users to interact with the prototype. Did you see that? (a BA or end user would be given a URI that showed the left pane only)

    If you didn’t see it, that would show the pitch slides could give a bit more info on the “how”. I tried intentionally to focus on benefits and not on the technicalities, but I guess I went too far.

    I am for using UI mockups, they do have a valid purpose, but I don’t think they are effective in getting the details in the requirements right, nor help significantly with the solution, which are the areas AlphaSimple means to serve.

    Re: BonitaSoft, I will need some time to read about it before replying.

    Thanks again for your help!

  5. rafael.chaves

    May 11, 2011 at 11:50pm

    Took a look at Bonita Open Solutions. I don’t think they are in the same area. BOS has impact on runtime, AlphaSimple is a development time only tool (prototyping and code generation).

Comments are closed.