Simple Tutorials

[aparry]

Afternoon All,

My business has purchased EA for our very small team of developers and require EA for requirments gathering and code generation. I have spent 2 days now going through tutorials and examples and (could just me!) they seem to take you through each of the different views, but not how they all connect so that i can implement a 1 click requirments to code workflow.

My question is, is there a tutorial that anyone knows of that will step through,

• Record User Requirments
• Generate Classes
• Generate the Database
• UAT list

I can create these views & diagrams individually, but it is the one click generation from 1 view to the next that i am looking for. Am i missing something in the linking of the elements?

Our attraction to EA was for rapid development of applications, however at the moment we seem to be spending more time dragging and creating elements than we do code?

Thanks!

[Sebastian Gliss]

You cannot generate Code on the basis of requirements - how should that work??

First, you have to notice if a tutorial does not match your interest.
Second, you will have to think about, if code generation is what you really want / need.

Code generation is overrated, often.
I would suggest: use EA for gathering the requirements. Then define some usecases and link the requirements to them.
You can refine usecases by making them composite and define an underlying activity chart to describe the exakt behaviour of the system.

You are doing such kind of work to get a clear picture of the system beeing developed to discuss it with your customer and team.

For the database: well, there has to be a tutorial on database generation in particular, you will have to work through.

If you and your team has never used modeling before, I would suggest stop thinking everything goes into the right place by itself :-)

Learning curve is steep when modeling, the decision to do it is up to you. It always helps to make an EA course in order to clarify what EA can do, and not.

I had expected to be led one step to another and had to learn, that you have to find your own working process.
For instance: gather requirements, link them to use cases, create domain classes, generate code stubs, refine usecases with activity charts and implement that activities in your class stubs...
There is no agent, leading you from one step to the next.


Kind Regards

[AndyJ]

If you're really new to this, you may not have found domain models yet.

A domain model is a class diagram showing the information in the system, aggregated into clusters that are meaningful to the end user of the system.

I recommend that domain models are developed side-by-side with your use cases.

For example the use case may include a line like: The Customer enters their Billing Address .

I would expect a class on the domain model that shows the attributes for a Billing Address, or at the very least sub-type (class) that shows that Billing Address shares all the characteristics of Address.

 

While the domain model doesn't design your database, it contains a wealth of information that is valuable to the database designers.

[aparry]

Thanks AndyJ, I have seen these tutorials, and i think they might be the missing link in our SDLC.

-Thanks