On Tue, Jul 16, 2013 at 12:44 PM, Samisa Abeysinghe <[email protected]> wrote:

> This should be the highest priority other than the data mapping work we
> are doing in the tooling space.
>
> I think, the most productive is to go about this with user story
> implementations. Else, it is so hard to surface real bugs.
>
> WDYT?
>
User stories will be a good way test the usability. IMO, graphical editor
works pretty well in the happy path, but when user tries to do something
strange then its failing apart.

>
> If we are in agreement, can we figure out some projects that we should
> carry out to cover this ground?
>
>
>
> On Tue, Jul 16, 2013 at 11:31 AM, Kasun Indrasiri <[email protected]> wrote:
>
>> Hi,
>>
>> The graphical editor for ESB has improved quite a lot, but still there
>> are a lot of cases that we need to improve the user experience perspective.
>> So, I think we need to focus on stabilization of the editor and giving a
>> smooth user experience with designing of message flows. Almost all the ESB
>> features are supported with the latest Dev Studio 3.2.0, so this will be a
>> good point to concentrate on the $subject. I think all ESB folks should own
>> this and help the tooling team to improve it.
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>



-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to