Recent Posts

Pages: [1] 2 3 ... 10
1
General Board / Re: Make EA<->C Code synchronization more "intelligent"?
« Last post by qwerty on Today at 07:17:09 am »
One more historical remark: around 2000 I used RR to generate code. They did put a lot of tags (within comments) in the code and used that to synch changes. Of course you better left these tags untouched or you were in trouble. At that time IDEs were not that common so I edited the code within RR. That worked. Somehow. But with todays IDEs it would be just a PITA. Some of the IDEs offer UML diagram creation, but thise simply suck (if not being wrong in many places). UML tools (like EA) on the other hand are a joke when it comes to IDEs capabilities. So what I learned: there's a media break between UML (which is excellent to model customer views up to a technical design) and IDEs (which support coding in all directions like code intellisense, debugging, etc.). Give the modelers/architects a good UML tool and gibe the coders a good IDE. And the real issue to get the technical part (SDs upward) being documented by coders EASILY. EA is not the best for the latter, unfortunately. They better like to implement a new gizmo each release which usually is half baken or completely useless (rare case where they are actually useful).

Enough for today.

q.
2
A workflow script tested and working since v 13.0 to 15.2 doesn't work in EA v 16. It seems the workflow event is not triggered in v 16.

You can reproduce the issue with this simple code in a workflow script:

Code: [Select]
option explicit

public function CanEditTag( TagName )
Session.Output("TagName="&tagName)
Session.Output("MetaType=" & WorkflowContext.MetaType)
CanEditTag = true
end function

Public Function PreAllowTagUpdate(TagName, OldValue, NewValue)
PreAllowTagUpdate = ""
End Function

You can note in previous versions the event is triggered and you can see the output in the System Output window. Now, you don't see any output. The event is not triggered anymore.
3
General Board / Re: Make EA<->C Code synchronization more "intelligent"?
« Last post by EAabecedarian on May 24, 2022, 11:01:53 pm »
Hi Takeshi.

In the User Preferences, Attribute/Operations Group, enable 'On forward synch, prompt to delete code features not in model'

Thanks! At the first glance this seems to solve my problem. Even existing code in the function body is kept.

Quote
Since EA does not add tool-specific marks in source files, EA cannot distinguish changes from additions/deletions.

Yes, but it could do - and when checking the option you mentioned it obviously does - some "intelligent" code parsing.

BR,

EAabecedarian
4
General Board / Re: Make EA<->C Code synchronization more "intelligent"?
« Last post by Takeshi K on May 24, 2022, 06:49:16 pm »
Hello EAabecedarian,

The following option might be help in your situation.

In the User Preferences, Attribute/Operations Group, enable 'On forward synch, prompt to delete code features not in model'

Since EA does not add tool-specific marks in source files, EA cannot distinguish changes from additions/deletions. By enabling this option, EA asks you when there are unknown functions in the codes. You can select changed functions, and specify them as deleted.

HTH,

5
General Board / Re: Make EA<->C Code synchronization more "intelligent"?
« Last post by Geert Bellekens on May 24, 2022, 04:34:17 pm »
To key to this, in my opinion is to not keep the same information in multiple places.

There is little added value in having a model at the same abstraction level of the code. It's the exact same information, but in two places and two different formats.

What you want to model is those the information you can't get from reading the code.

- Business Models
- Logical data model
- Use Cases
- Architecture

These models are often much more stable than the code, but in order to keep things consistent, you need to check your processes.
Each change should pass through the hands of the Business/Function analyst and Architect. They have the responsibility to update their part of the model is required.
Only then the code should be changed.

All these roles could be played by the same person. You don't necessarily need different people.

Geert
6
I don't know what you mean by "adding to version control without an external file".

AFAIK there is no such thing. How would it work? How does your version control system know the contents of your package?

You don't need EAB file, that's true, but you do need .xml files for each controlled package, whether you do it manually, or with a script.

Geert
7
Thanks Geert
Do you mean there is no way to add a package to version control without creating an external file using a script?
It should be possible since when I do add to version control manually, I have the option not to create an external file in the dialog.

As a secondary question - maybe my approach is wrong - I have a large package hierarchy which models my C code directory hierarchy (e.g. directory per systems, subsystems, packages, module). I put every package under version control explicitly so that it can be checked out individually - but as far as I know - I have no need for the EAB files - so I should be able to add a package to version control with an external file - what am I missing ?
8
General Board / Re: Make EA<->C Code synchronization more "intelligent"?
« Last post by EAabecedarian on May 24, 2022, 03:26:50 pm »
Nothing you would like to hear, but I tell it anyway: code generation is a Fata Morgana. It does not bring any value to generate code.

q.

Thanks for your input. Maybe you are right. But what I've experienced is that once the SW design is done (if it is at all), developers don't really care any longer.
However, there usually isn't just one iteration. In the end you have a code that doesn't match the design and/or architecture because of changed parameters, added or deleted functions, etc.
Code review is tedious and nobody has really time for it.
Of course, discipline and a dedicated software architect having time to track would help.
But I thought it would be beneficial if there could be at least some automated process for all that interface stuff:
Let the code generator run, and if afterwards the build won't work anymore the developer MUST take care of updating the design - or stick to it.

BR,

EAabecedarian
9
Suggestions and Requests / Roadmap diagrams - adjusting "timeline" heading
« Last post by skiwi on May 24, 2022, 01:54:06 pm »
Roadmap Diagrams | Enterprise Architect User Guide (sparxsystems.com)


Anyone know if it is possible, and how, to disable  the "Units: ..." in the title line?
10
Bugs and Issues / Re: Project Transfer Fails DBMS to JET
« Last post by qwerty on May 24, 2022, 07:37:19 am »
Make a local copy and remove the baselines. Then issue the project transfer. Probably not the fastest way, but you get the copy (without the baselines).

q.
Pages: [1] 2 3 ... 10