/    Sign up×
Community /Pin to ProfileBookmark

Application Lifecycle Management

Copy linkTweet thisAlerts:
Mar 27.2006

Attention all Developers and Project Managers

I’ve been hearing the buzzword “Application Lifecycle Management” to describe the range of development tools including 1. requirements management, 2. modelling, 3. coding/building (IDE) 4. tracking (Configuration and change management) 5. Testing (ASQ) and 6. Deployment and post deployment management.

A couple of questions for all you developers and project managers out there:

  • 1.

    How important is it that you have dedicated software to do requirements management and modeling vs. just using excel or something not so fancy?

  • 2.

    How important is it that all of the various applications that might be used during the development process (IDE, SCM, ASQ) be integrated and be able to interact with each other.

  • 3.

    Is there a preference for having softward provided by one vendor (i.e. IBM vs. using best of breed)?

    • Thanks!

    DevelopWiz

    to post a comment
    Full-stack Developer

    3 Comments(s) ↴

    Copy linkTweet thisAlerts:
    @ray326Mar 28.2006 — 
  • 1. It certainly makes life simpler to have a requirements management system but a spreadsheet will do as long as you have the process in place. Modeling really needs to be done with a modeler. The simpler UML diagrams can be done with drawing tools like Dia but some of them like sequence diagrams really need the sophistication of the dedicated editor.


  • 2. I prefer having the SCM integrated with the IDE but external is fine as long as everyone knows what to do with it. ASQ can be even less coupled. The nice thing about integrated SCM is it will know exactly what needs to be versioned and what will be built on the fly. Otherwise the developer has to know that and it's not always a trivial undertaking.


  • 3. Not as long as the IDE is beefy enough. Eclipse for instance can pull a huge number of disparate technologies together.
    • Copy linkTweet thisAlerts:
    @DevelopWizauthorMar 28.2006 — Thanks Ray! I really appreciate you taking the time to pass along your thoughts.

    Is there any benefit to having the modeler or requirements management tool linked up with the IDE (or other components)?

    Thanks!

    DevelopWiz
    Copy linkTweet thisAlerts:
    @ray326Mar 28.2006 — I personally prefer a development method like RUP. In that kind of environment the modeler sort of becomes the central point of view with (functional) requirements in use cases. When the overall model is version controlled then, poof!, you've got pretty decent requirements traceability. Of course [B]managing [/B]requirements is really a process outside the tools. The tools just manage the artifacts that represent the requirements. If you've got an idiot project manager then you're screwed no matter what you do. ?
    ×

    Success!

    Help @DevelopWiz spread the word by sharing this article on Twitter...

    Tweet This
    Sign in
    Forgot password?
    Sign in with TwitchSign in with GithubCreate Account
    about: ({
    version: 0.1.9 — BETA 5.19,
    whats_new: community page,
    up_next: more Davinci•003 tasks,
    coming_soon: events calendar,
    social: @webDeveloperHQ
    });

    legal: ({
    terms: of use,
    privacy: policy
    });
    changelog: (
    version: 0.1.9,
    notes: added community page

    version: 0.1.8,
    notes: added Davinci•003

    version: 0.1.7,
    notes: upvote answers to bounties

    version: 0.1.6,
    notes: article editor refresh
    )...
    recent_tips: (
    tipper: @AriseFacilitySolutions09,
    tipped: article
    amount: 1000 SATS,

    tipper: @Yussuf4331,
    tipped: article
    amount: 1000 SATS,

    tipper: @darkwebsites540,
    tipped: article
    amount: 10 SATS,
    )...