Book a Demo

Author Topic: Extending an existing project  (Read 5697 times)

Jesmond

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
  • Where there is a will there is a way!
    • View Profile
Extending an existing project
« on: August 26, 2007, 12:02:45 am »
Dear all,

I have a contract assignment to analyse and subsequently modify/recommend an existing web based application (small add-in application).

I have reverse engineered the models into EA professional (as mush as possible), and a next step I plan to add/modify the model in order to reflect the changes required for the new requirements.

I am note familiar what proper UML discipline I should use in order to modify functional requirements, modify business processes, use case models, etc.

Should I just create new views/diagrams, or just modify the structure (I would loose the history, since I do not have version control enables). I could copy/clone the project, and use a "two copy".

Note: This project scope is limited to the business analysis / inception stage only (possible more if the customer decides to use EA for the whole project lifecycle).

I would appreciate any point of views from experience users how would this be tackled.

Best regards,

Jesmond

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: Extending an existing project
« Reply #1 on: August 26, 2007, 10:32:48 am »
Quote
[SNIP]
I have reverse engineered the models into EA professional (as mush as possible), and a next step I plan to add/modify the model in order to reflect the changes required for the new requirements.
[SNIP]
Should I just create new views/diagrams, or just modify the structure (I would loose the history, since I do not have version control enables). I could copy/clone the project, and use a "two copy".

Note: This project scope is limited to the business analysis / inception stage only (possible more if the customer decides to use EA for the whole project lifecycle).
[SNIP]

It depends upon several things
  • Did the reverse engineering produce a model at the same level of abstraction as the one you need to produce?
  • Do the new features <<include>> or <<extend>> existing Use Cases or do they introduce new Use Cases?
  • Does your definition of Business Analysis include or exclude the work of a Solutions Architect?
  • How well can your stakeholders read UML Diagrams?

Verbal Use Cases aren't worth the paper they are written upon.

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: Extending an existing project
« Reply #2 on: August 31, 2007, 07:09:19 pm »
Is this thread dead?  :-/
Verbal Use Cases aren't worth the paper they are written upon.

Jesmond

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
  • Where there is a will there is a way!
    • View Profile
Re: Extending an existing project
« Reply #3 on: August 31, 2007, 08:04:33 pm »
Hi Jes,

Sorry for not following up, and thanks for your interest.

Following up on the project I imported the existing requirements, and used EA custom model to express the underlying relationships. Additionally I split then into three separate packages. Then I created a separate package to contain the new and/or changed/extended requirements. I am not quite sure how to you express a change" or "extension" using EA requirements custom diagrams though.

As far as the use cases, unfortunately the were not re-usable, since the previous project had actually (perhaps inadvertently) performed functional decomposition, and actually express functions rather than a use case! So I am re-defining the use cases.

At the moment I am concluding the documentation for the inception phase of the project, for which I have been following the OpenUP guide (http://www.eclipse.org/epf/) that I found quite useful.

Regards,

Jesmond