Relation between Use Case Model & Component Mo

[sbarkeruk]

When generating Use Case models, this is what you would then use to base your Component Model on.

However, if I create my Use Case model (and others) and then eventually generate code template from the Component Model, this is great.

However, if I now change the code and synchronise the model, so that the component model updates itself to my code changes, my Use Case model may not necessarily be up to date with this change (Especially if the change required adding a new function that was not seen during requirements ilicitation).

So is there a way of either a) Being warned that the Use Case model (and perhaps others) now need to be updated or b) Some more automated method of controlling this.

If this has to be controlled manually, then there is potential for the entire project to get messy and out of sync quickly, especially if you are a company that rolls out a lot of variants of software!!

Please comment on solutions to this, or if I have got this completely wrong!!

[mikewhit]

(Especially if the change required adding a new function that was not seen during requirements elicitation).

You have answered the point yourself - if you need to change the requirements then that change should go into your Analysis model first [and then work through the design], before modifying code !

Sorry, not the most helpful answer - but since the Analysis levels do not participate in the Code Engineering process, I would say it's a method of working that you should get used to.

You will also then be certain (!) to update any Test Cases on the way back down to the code.

Sometimes, so-called "agile" methods just need to sit down and do the job properly ;-)

[mikewhit]

When generating Use Case models, this is what you would then use to base your Component Model on

Another thought - experience seems to suggest that Use Cases are not ideal for generating a component model from, although they are good at capturing how the user sees his processes and procedures, and for generating System and Acceptance tests from.

Identifying domains, objects and classes would seem to be a good first step in moving from Analysis to Design.

[thomaskilian]

I myself learned a lot by studying the ICONIX process. You may search this forum using this keyword.

[Martin Terreni]

Hi
I consult some SW development teams about development processes and I can tell you that I work two ways:
1) if the team is at the beggining of the project then I woudnt advise them to get any further then use case untill requirments are fully understood and closed.
2) if the program is one that is already running at costumer site and the team is only supporting it and doing new versions then either , if it is a major infrestuctural change, I tell them to remake usecase, if not then we just ignore use case and only go back to design.