Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Bryce Day on April 26, 2007, 08:22:15 pm
-
The team at Screen Architect are pleased to announce the release of Screen Architect version 1.0.
Screen Architect is a prototyping tool that plugs into EA and has been specifically developed to allow rapid prototyping of user interfaces.
For further information please visit the website www.screenarchitect.com
Regards
The Screen Architect Team
-
I installed the add-in and have just started looking at it...
I do notice that the response time on the add-in seems to be pretty slow on my laptop (P4 2.1, 1 GB mem, 256MB graphics card... maximum performance mode)...
So far, it appears interesting and worth me spending a little bit of time exploring it for a little bit...
Anyone else checking this out yet?
-
You can launch and run the Screen Architect plugin either from within EA, or natively from your desktop. Using it natively performs a lot better ;)
-
but that kinda negates the whole point of integrating it within EA?
Unless you mean launch it first, then EA?
-
Well the integration is still there - it still uses your EA model. It means that you can use the outputs from Screen Architect in your EA diagrams.
I've tried it (just a few minutes) and I like it, so far. It misses some quite frequently-used GUI elementes (eg. tabs) or element features (not active elements, checked check box or radio button), but i thing that the basic idea is cool.
-
I guess apart from integration with EA, the really cool thing about Screen Architect is that one can generate HTML prototypes that can be walked / navigated through with end users.
-
It is cute tool.
The prototyping is a very good feature, but it laks of controls or avility to "create" them and it works very slow.
Right now we model our UI in EA (which does sertainly a good enough job) if SA had all .NET controls or avility to some how create them (and worked a little faster) no doubt it would be a tool with grate ROI (like EA is).
lookig foward to see it evolve.
-
Yes... having the UI components that we are used to, and increasing it's speed, would do a lot to reach a a purchase tipping point...
The one feature that stands out is the creation of an interactive "proto-type" with the integration into the EA project...
Good effort, but just not ready yet... IMO
DO NOT GIVE UP... (as I know you won't!), just consider the feedback (as I know you will!)
Best wishes, and I will keep the website on my Fav ToVisit list...
-
Thanks for all the feedback, it is appreciated.
I have spoken/emailed with several of you since the release of Screen Architect about some of the improvements you would like to see.
Over this period we have been working on increasing the performance and are looking to release another version with this and a couple of minor enhancements to you shortly.
Seveal areas the team is interested in understanding more about are:
1. Types of controls - we have tabs, panels, grids and tables on the radar - are there others that are a must have?
2. Our aim has been to provide an integrated tool to allow wireframes and screen designs to be developed and prototyped quickly by the business analyst/interaction designer for use in the analysis & design phases. Several emails would like us to add enhancements in the code generation space.
How you see the Screen Architect being used? e.g. Screen design verses code generation and where is the greatest value to you and your organisation?
Thanks again and I look forward to the continued feedback
The Screen Architect Team
-
How you see the Screen Architect being used? e.g. Screen design verses code generation and where is the greatest value to you and your organisation?
I normally work in the realm of CIM & PIM models with stakeholdrs. When working with stakeholders, I am concerned about describing the look and feel of a System. What you have is a good start on the look of a GUI, but I've not yet found the feel part.
At the risk of promoting Executable UML (a disciplined place I'm not currently ready to go with Business & Requirements Analysts), I might suggest that you think about finding a way to:- integrate into the mix a Protocol State Chart--as a link back to the Use Cases partially realized by the GUI; and
- provide a way to incorporate scenario demonstration with representative domain data, all under control of the Use Case Protocol.
This provision of the feel would of great value in driving out heretofore unarticulated Requirements.
-
How you see the Screen Architect being used? e.g. Screen design verses code generation and where is the greatest value to you and your organisation?
The best benefit is the ability to create prototype by business analyst very quickly. The "feel" part of application is very often defined by design manual of our customer - so that I don't need improvements in this way.
It would be great if the screen architect could generate screen flow from links defined between screens (lets say buttons only for example).
Regarding code generation features - we don't need it. :-)
-
Seveal areas the team is interested in understanding more about are:
1. Types of controls - we have tabs, panels, grids and tables on the radar - are there others that are a must have?
My thoughts would be:- A named Element group to associate/differentiate/contain multiple sets of radio buttons;
- Menu bar & drop down Sub menu;
- Window boarder & title bar
- Frame sets for web enabled forms (perhaps as a specialization of panel?)
- Hot spot buttons (transparent buttons with dotted or dashed outlines that sit over interesting points on an underlying/background image. Not all stakeholders on a manufacturing shop floor are able to read. What would be really cool would be the ability to draw a polygon shaped button, but I don't know how to implement that in code. :(
- Element attributes such as isLocked, isVisible, default value, etc. This would feed into the state diagram transition logic.
I'm excited about the ability to link/embed your screen designs to EA models, but I need more to pull me away from the type of tools I currently use. At present I use a mix of: - Story boarding to demonstrate state changes, followed by
- a proof of concept mock up using the forms capability and simple scenario tables in MS Access (just enough to give a feel of the form's behavior), and finally
- the IDEs provided by Visual Studio and/or Net Beans.
For me, the priority is with the client facing aspects of Requirements Specification rather than with the speedy generation of code that provides incorrect behavior. While our developers have input on tool selection, it is the Project Managers and Technology Managers that make the final tool selections; and, they do that work at the front end of the project, not in the middle where the development team kicks in on a project.
Another big factor in tool selection are the concerns of IT Business Analyst and Solution Architects (both of whom probably have programming as a distant career base) who will be the first on the project to use these tools. They will be most concerned with a system's Cognitive Design, Navigational issues, and Use Case Protocols. I'm looking first for tools to support resolution of those issues, and when we get that correct, then I'll be happy to talk you about code generation. 8)
Good luck. You've got a great start on a great idea! Keep on slogging.
Jim
-
The scope of this is snowballing very quickly, so
my vote is to try and contain it with Jan's view of the world.
Perhaps 1.x releases can concentrate on streamlining the prototyping aspect including the ability to navigate between screens, and version 2.0 can start the code generation side of things
-
The scope of this is snowballing very quickly, so
my vote is to try and contain it with Jan's view of the world.
I agree... don't try to be EVERYTHING... focus on one aspect of your vision for this project, then make it robust (through small interations in my opinion...)
I think the prototyping aspect has the most bang for your development buck... as there are other tools for doing the code generation... and besides, if I can't prototype the screens to reflect WHAT I want them to be... then WHY would I spend the time turning them into code so I can execute screens that does not meet my customer's needs?
Looking forward to future releases...
-
1. Types of controls - we have tabs, panels, grids and tables on the radar - are there others that are a must have?
Whatever is in VS
2. Our aim has been to provide an integrated tool to allow wireframes and screen designs to be developed and prototyped quickly by the business analyst/interaction designer for use in the analysis & design phases. Several emails would like us to add enhancements in the code generation space.
How you see the Screen Architect being used? e.g. Screen design verses code generation and where is the greatest value to you and your organisation?
I'm the system architect (not technical architect) and my main concern is to fit customers functionality request, so code generation for me is less important, yet I do work tightly with the technical architect and in order to have full traceability from design to code I would like your tool to create from my design in the tool the relevant objects in EA(EA does have UI objects I use to design the UI) so all the design indeed stays in the same repository and maybe in the future I'll be able to generate ALL code from within EA (both EA part and SA part).
Also I agree that whatever is goign on here had turn in to a snow ball...
thanks for letting us participate.
-
Thanks for all the great suggestions.
We have just released a new version of the software that significantly improves the performace, adds some minor functionality and enhances the integration between Screen Architect and EA.
The new release and the release notes for it can be accessed via www.screenarchitect.com
We are looking to add further controls in the next release.
We look forward to the continuing feedback
Regards
The Screen Architect Team
-
Since I will not buy this product until I experience a Trial version that meets my need, we have a problem here.
The first version trial did not convince me to buy. Having only 3 days left on the trial, I "un-installed" the version I had, downloaded the latest trial (#2) and installed it. I still only have 3 days left for evaluation! Ridiculous!
Given the minute enhancements in the second trial, I think I'll not have a chance to evaluate an industrial strength version; and, that's too bad.
Guess I'll stay with Visual Studio, Eclipse, or Net Beans to articulate UI requirements to my Stakeholders.
-
I'm facing the same problem. But I think that $50 isn't too much so I told our IT to buy one licence just to be able to see progress.
-
Thanks for pointing the trial expiry issue out, it is not our intention to exclude anyone from reviewing the latest release features.
We are working to sort this out as soon as possible.
If you have any further enhancements or find any issues, please feel free to contact us directly on [email protected]
Bryce
-
Well there has to be some protection against an uninstall/reinstall of the trial version otherwise no-one would ever have to buy it, but I agree trying a later version should give you another full trial period.
-
Quote: Well there has to be some protection against an uninstall/reinstall of the trial version otherwise no-one would ever have to buy it, but I agree trying a later version should give you another full trial period....
I understand and agree, but I was wondering HOW you would implement something like that? Have the trial time limited in the minor releases, and reset in the major? Or track re-install churning by forcing a new registration with the website? Track CPU ID as part of the registration process?
Don't really understand how the re-install churning could be prevented? suggestions?
-
Don't really understand how the re-install churning could be prevented?
I would assert that if their software can detect a usage count/period, it can also reset it. That would be done in accordance with their trial release policy.
-
OIC! Doink!!
Thanks from the <No Eyed Man>
-
I guess the version number would be needed along with the usage count/trial period so that the reset can be applied if a later version is installed
-
I guess the version number would be needed along with the usage count/trial period so that the reset can be applied if a later version is installed
Eazy Peezy ;)
-
Thanks again for the feedback.
We have just released an updated version of Screen Architect Version 1.0 Build 229. This new version resets the trial version period on the installation of a new release.
We look forward to your further comments and improvements
The Screen Architect Team
-
Thanks again for the feedback.
We have just released an updated version of Screen Architect Version 1.0 Build 229. This new version resets the trial version period on the installation of a new release.
We look forward to your further comments and improvements
The Screen Architect Team
A compnay that listens to their POTENTIAL customer base... Imagine that! <grin> May bode well!
I will be finishing some of my current project tasks soon, and look forward to walking through the tools functionality. I have a small project I am reverse engineering the requirements for (don't ask why... but the solution is in production, but they never got the requirements approved by the customer?!!!) and I am going to use it as my test case for the screen prototyping... Web Based application...
-
Thanks for all the feedback, it is appreciated.
Seveal areas the team is interested in understanding more about are:
1. Types of controls - we have tabs, panels, grids and tables on the radar - are there others that are a must have?
2. Our aim has been to provide an integrated tool to allow wireframes and screen designs to be developed and prototyped quickly by the business analyst/interaction designer for use in the analysis & design phases. Several emails would like us to add enhancements in the code generation space.
How you see the Screen Architect being used? e.g. Screen design verses code generation and where is the greatest value to you and your organisation?
I just downloaded the trial version and started it from an existing ea project.
I miss the ability to use existing screen prototypes from ea.
And i don't see any of the objects from my ea project in sa.
What's wrong?
Ralph
-
Also missing:
- formatting background and colors of objects
- panels, group boxes, lines as separators
- mixture of ea screen objects in sa screens
- generating forms from wsdl input
- generating froms from xsd-input
- ... to be continued ...
-
Also missing:
- formatting background and colors of objects
- panels, group boxes, lines as separators
- mixture of ea screen objects in sa screens
- generating forms from wsdl input
- generating froms from xsd-input
- ... to be continued ...
a)Formatting backgrounds and colors can be achieved via the properties of most objects;
b)Panels and group boxes are missing at this stage but line and separators could be substituted with H & V lines under Shapes;
Not sure about the rest. Perhaps the SA technical team could respond...Not sure why you'd want EA Screen objects or any other EA objects in SA? I suppose one could cut existing EA wireframes into SA screens as images.
-
a)Formatting backgrounds and colors can be achieved via the properties of most objects;
Well, I tried it, but there were no properties for backgrund color of an object (i.e. screen) or object coler itself.
b)Panels and group boxes are missing at this stage but line and separators could be substituted with H & V lines under Shapes;
How?
As I try to have a complete documentation of dependencies between User interface, model and technical inetrfaces and services, I need all typical dialog objects and the possibility to creat a relation between the dialog and the model objects.
The other point is, that the re-use of existing html-code (snippets, css) should be possible, so that we can create a prototype for the experts (endusers) which gives them a feeling of the planned application.
Not just only a few grey buttons and pages without any corporate style.
btw: A big point for me in the trial version is, that there will is generated a trial wallpaper and this is also in EA visible.
Ralph
-
Ralph,
Are you using the current trial version. They released an update not too long ago, and you could still be in the original trial window.
Apparently the next version - which might be the one currently on trial - detects a current trial version and extends the evaluation period. There was a point where this did not work, and your original period would expire leaving you without a working trial version. Best to check this before updating.
David
-
Ralph,
Are you using the current trial version.
David
I downloaded it yesterday. So I would assume that new features are in it - but the proposed new dialog elements are definitely not available.
-
Perhaps next release.
Sigh...
-
Does anybody have any information about further development? Is this project still alive or is it already dead? ???
Such a tool as Screen Architect seems very useful to me, but current release is still some important functionality missing.
-
Catch, the makers of Screen Architect have a 2 day Symposium in New Zealand with Sparx at the end of the week, so maybe there will be some new announcements?
It is an interesting tool but looking forward to the next version...
-
I agree. Hope that new release will be announced...
-
Apologies for the delay in releases. Although you haven't seen much action externally, we have been working very hard to get the next release up to scratch.
One of the major delays in getting the next release out is due having to rewrite the HTML generation so that in the future it will support .css properly and behind the scenes build in support of layering.
In the next release you should expect to see;
1. Better HTML generation
2. Greater support for MS Sql data repositories
3. New controls including panels which enable you to have richer functionality controls & tables.
Internally we are still testing the next version but symposium attendees will get a sneak peak of this new functionality. We also intend to present and release a roadmap for SA into the future at the symposium which will then be placed on the website for everyone to access.
Please be assured that Screen Architect is still actively being developed and will continue to improve.
Bryce
-
Bryce,
thanks for the update.
It's a little too far to come to the symposium...
Looking forward to the website update for the rest of us ;D
All the best with the next release,
Matt
-
Hi Bryce
Waiting every day for the next release.
I know it will be a good one.
Good luck
Jose
-
Thanks for update. :-)
-
When I wanted to download trial version of this plug-in, I was requested to register and on registration form there's way too much required fields, personal information - instant first turn off. Second one, .NET framework is a system requirement. Two thumbs down, and I haven't installed it yet.
-
Another, and final thumb down - for additional $75 this plug-in offers nothing essentially new that isn't already present in EA user interface diagrams.
-
On of the benefits is that you can easily generate HTML prototype.
-
Another, and final thumb down - for additional $75 this plug-in offers nothing essentially new that isn't already present in EA user interface diagrams.
Have to say that for someone who hasn't yet loaded SA and tried it (see previous post),its a pretty big call to state that it doesn't essentially offer anything more than what is already in EA. For example, I've never been able to generate UI prototypes from EA that I can walk users through and leave them to play with, among other pretty hot features. I believe the next release of SA will include tables, grids, panels, tab controls etc. all of which aren't available in EA...
-
I definitely agree. But we can only hope that there will ever be a new version... They said thay will inform as about new release at the end of November (at the beginning of December at latest). But no new information is available by now. :(
-
Hi all,
Thanks for your patience with the release. We demonstrated panels and tables at the symposium and are just rejigging the release notes prior to releasing this version. It has been delayed, but hopefully you should find a quick suggestion of releases occuring over the next little while.
Additionally, we will be posting a road map for the product so you can get an idea of what we are trying to achieve.
Bryce
-
Great to read good news. I'm looking forward to seeing a new version. :)
-
All
If you haven't already seen a new release of Screen Architect has been posted and ready for you to download.
This new release has the following functionality:
Added Panel Control.
Added GroupBox Control.
Added Grid Control.
Added Table Control.
Added support for Anchors property (used to align controls inside Table Control).
Added support for Text property values of lengths greater than 126 characters.
Full support for DBMS EA Repositories.
Most Recently Used Project list added to File menu.
Implemented fix to prevent user from being able to delete root model.
Fixed issues with designer surface positioning and resizing.
Added more informative error message when EA is not installed/damaged.
Fixed a number of bugs preventing SA from loading if windows layout configuration was corrupted.
Debug Info added to Help About dialog box.
Progress indicator added when saving multiple screens.
Fixed bug related to EA crashing on exit when SA installed.
We look forward to your continued feedack and all the best for Christmas and the New Year
Bryce
-
I've just downloaded a new version and tried it very quickly. It seems to me that new features are really useful - grids, groupboxes... I missed these elements very much. Good work.