Web interface into repository

[spirax]

It would be great if there was a standard web interface into an EA repository, so that diagrams can be viewed just within a web browser, and perhaps minor text changes made.
Ideally, each diagram should be able to be found with a unique URL.

[Hans Olthof]

Isn't that served by the project/documentation/html report function?
Or are you after a standard web-server function that dynamically serves content from a database?

Hans

[spirax]

The latter.  Generating html reports creates another static view of the models (which is quickly out of date).

There's really two things here. Firstly a web client for viewing the repository, with a simplified version of the project browser or model views window.

Then, the ability to view any diagram via a unique URL, ie the diagram has a unique identifier which is included in the url.

Both of these views should not be pictures (like the html report) but contain objects which can be interacted with (to a limited extent obviously).

This would make it much easier to integrate with corporate intranets/wikis etc.

[Sunshine]

Sounds like you want to provide some kind of limited editing capability via the web browser rather than a simply publish the model on the intranet. Presumably this is to have a wider participation by the organisation. At present there isn't really any way to do this unless your prepared to develop it your self.
You might be able to customizes the HTML generated report with some java/.net forms that access the database. If your not a developer you'll probably need to hire one. Perhaps create a batch process that publishes the model everynight with some java/.net forms that update the database. Suggest if you do go along that path you implement version control too so you can undo any changes should they not be desirable.
I publish using the HTML report generator and get people to provide feedback using the feedback mechanism described on the community site. http://community.sparxsystems.com/resources/document-templates/add-diagram-feedback-and-comment-link-html-report. I've added this to element descriptions too. The advantage is I can control what goes into the model. The disadvantage is can get a lot of emails.

So it sounds like a good suggestion. I guess what Sparxs have to consider is it worth going down that path as its a new architecture. For instance a n-tiered web as opposed to a rich client server. It all costs money to do and support.

[spirax]

This is something that some of EAs competitors already do - provide both a "rich client" executable, and a limited capability web client (eg ProVision).

The basic problem with the web report is that it creates pictures of diagrams. Whereas the web client would allow a user to double-click an element and read its notes and look at its properties and know that it is the latest (current) version.

I know EALite could do this, but that requires installation onto users pcs (not popular in corporate environments) and configuring to connect to the repository.

[Sunshine]

The basic problem with the web report is that it creates pictures of diagrams. Whereas the web client would allow a user to double-click an element and read its notes and look at its properties and know that it is the latest (current) version.

mmh? the last time I generated an HTML report I'm pretty sure I could navigate to the notes of an element by clicking on the element in a diagram. Granted its a snapshot of the model at that time but you could keep it up to date by generating the HTML report on a regular basis. i.e. daily is probably good enough.

[salayande]

An interesting request.

Last week, I was asked by someone within operations if a web interface with limited functionality exists for EA. They seem to want to interactively modify EA content. I did'nt know what to say as it appeared a strange request and coming from non-IT folks.

It seems like the consumerism of IT is influencing requirements from non-IT staff faster than IT departments can cope with.