Hi Frank,

>
>
>    1. create_chevron:
>       1. Is the list of properties of a chevron fixed?  Or does "add
>       properties" mean that I can add more properties? I suspect that the 
> list of
>       property types of a chevron is pre-defined...
>
>
   -  Yes, the property list is fixed. Here 'add properties' mean that the
   user can add the values for the provided properties.

                    2.What is the purpose of the Thumbnail?

>
>    - do we support to change the graphical appearance of a chevron?
>       Especially supporting to change the color of individual chevrons will be
>       helpful in practice.
>
>
   - Thumbnail image will be displayed for that respective chevron diagram
   in the list page. ( as shown in the list_chevron screenshot)  Currently we
   do not support change for the graphical appearance of a chevron.  If it is
   to be implemented , how would you suggest it to be ?( ex: user selects a
   color from a provided list)

                   3. Do we support multiple predecessors and successors?

   -  For the initial requirements we did not support multiple
   predecessors/successors, but this will be implemented in the next phase.

                   4.Is a value of the Process property a link? If it is
only a name, what is the scope of its uniqueness (aka namespace)?

   - Yes, a value of the process property is linked to that relevant
   process model.

                  5.Do we support drawing vertical chevron diagrams, i.e.
diagrams the arrows of which point from top to bottom?

   - Currently only horizontal diagrams are supported.

                 6.Do we support annotations of individual chevrons that
are shown on the canvas?

   - Yes, if a user clicks on an individual  chevron  that is placed on the
   canvas, those annotations will be listed. ( as shown in create_chevron
   screenshot).

          2.list_chevron:

>
>    1. Please call the type "Chevron Diagram" (instead of just "Chevron"):
>    A chevron is a single "arrow" in a chevron diagram.
>
>
   -  +1.Will change the type name to chevron diagram instead of chevron.

                    2.What's the purpose of the "Statistics" button?

   - 'Statistics' page comes by default for an asset type that is created
   in ES. It contains charts that display rated assets, top assets etc.

          3.edit_chevron:

>
>    1. Can we change "Edit Asset" into "Edit Chevron Diagram"?
>
>
   -    +1.Will change the title to Edit Chevron Diagram instead of Edit
   Asset.

                   2.The properties now contain an "owner" and a
"description" property, i.e. more properties than you show in
create_chevron; and the                             "process"  property is
now missing:  why?

   -   There are two sets of properties that a user should fill. A property
   list for the entire diagram as well as  properties for each chevron.

  For the entire chevron diagram ( ex : product payment) following
properties[1] will be included.
(name,owner,predecessor,successor,provider,version,description)

Whereas for each individual chevron (ex:check payment type etc)  ,
following properties[2] will be included.
(name,owner,predecessor,successor,process) Therefore in chevron_edit page,
if the user clicks on the canvas, properties for the entire diagram will be
displayed.while if the user clicks on a specific chevron that relevant
properties will be listed. This is the same mechanism followed in
create_chevron page.

          4.store_view:

>
>    1. Again, I recommend to speak about Chevron Diagrams and not only
>    about "Chevron".  Btw the same holds for "Process Model" instead of just
>    "Process"
>
>
   -  +1 .Will change chevron into chevron diagram and process into process
   model.

[1] chevron_diagram_properties
> <https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKS0czei1OQWtqekU/view?usp=sharing>
>
    [2] individual_chevron_properties
<https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKcjBaOW5EcUI0Y28/view?usp=sharing>

Thanks & Regards,
Himasha

On Sun, Nov 30, 2014 at 10:19 PM, Frank Leymann <[email protected]> wrote:

> Hi Himasha,
>
> please allow for a few questions/comments:
>
>
>    1. create_chevron:
>       1. Is the list of properties of a chevron fixed?  Or does "add
>       properties" mean that I can add more properties? I suspect that the 
> list of
>       property types of a chevron is pre-defined...
>       2. What is the purpose of the Thumbnail?
>          - do we support to change the graphical appearance of a chevron?
>          Especially supporting to change the color of individual chevrons 
> will be
>          helpful in practice.
>       3. Do we support multiple predecessors and successors?
>       4. Is a value of the Process property a link? If it is only a name,
>       what is the scope of its uniqueness (aka namespace)?
>       5. Do we support drawing vertical chevron diagrams, i.e. diagrams
>       the arrows of which point from top to bottom?
>       6. Do we support annotations of individual chevrons that are shown
>       on the canvas?
>    2. list_chevron:
>       1. Please call the type "Chevron Diagram" (instead of just
>       "Chevron"): A chevron is a single "arrow" in a chevron diagram.
>       2. What's the purpose of the "Statistics" button?
>    3. edit_chevron:
>       1. Can we change "Edit Asset" into "Edit Chevron Diagram"?
>       2. The properties now contain an "owner" and a "description"
>       property, i.e. more properties than you show in create_chevron; and the
>       "process" property is now missing:  why?
>    4. store_view:
>       1. Again, I recommend to speak about Chevron Diagrams and not only
>       about "Chevron".  Btw the same holds for "Process Model" instead of just
>       "Process"
>       2. Showing an individual chevron in ES is not the right granularity
>       (just as you don't show individual activities of a process model in ES 
> but
>       the complete process model itself).
>
>
>
> Best regards,
> Frank
>
> 2014-11-28 13:09 GMT+01:00 Himasha Guruge <[email protected]>:
>
>> Hi All,
>>
>> Chevron diagram editor initial requirements are completed, and following
>> are few screenshots from publisher/store end of Enterprise Store. Currently
>> the chevron asset is created as an extension of ES.
>>
>> *publisher: create chevron page ​​​​​​​​- *This page will enable the
>> user to draw the related chevron diagram and view the properties added. The
>> predecessor/successor fields are read only ,therefore the values will be
>> dynamically updated.
>> *​*
>>  create_chevron.png
>> <https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKMllDRXc4SlczaGM/edit?usp=drive_web>
>> *​*
>>
> *publisher: list chevron page - *The created chevrons will be listed in
>> this page as below.
>> ​
>>  list_chevron.png
>> <https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKMTBpRldNVFRhZ3M/edit?usp=drive_web>
>> ​
>> *publisher: edit chevron page* - This page will enable the user to edit
>> any existing properties as well as to update the diagram ( add new chevron
>> icons/ change order of existing icons etc)
>>
>> ​
>>  edit_chevron.png
>> <https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKT1VXcXNIRExBMDg/edit?usp=drive_web>
>> ​
>> *store end view page - *Once a created chevron is published, it will
>> appear in ES(Enterprise Store) store end, and will contain the following
>> view. Each chevron in the diagram can be clicked and the relevant
>> properties will be displayed.
>> ​
>>  store_view.png
>> <https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKNkdHdjJEQ04ydGc/edit?usp=drive_web>
>> ​
>> Thanks & Regards,
>> Himasha Guruge
>>
>> On Mon, Nov 3, 2014 at 9:36 AM, Himasha Guruge <[email protected]> wrote:
>>
>>> Hi Chathura,
>>>
>>> Import functionality noted.
>>>
>>> Thanks & Regards,
>>> Himasha
>>>
>>> On Mon, Nov 3, 2014 at 9:17 AM, Chathura Ekanayake <[email protected]>
>>> wrote:
>>>
>>>> Hi Himasha,
>>>>
>>>>
>>>>> Current requirements did not include the import functionality of the
>>>>> xml document,will discuss with the stakeholders regarding it so that we 
>>>>> can
>>>>> add it in the future.
>>>>>
>>>>>
>>>> We persist chevron diagrams (logic and formatting) in XML format in
>>>> GReg. So when a persisted chevron is opened we have to read the XML and
>>>> display the corresponding chevron. Therefore, we have to support XML import
>>>> functionality as well.
>>>>
>>>> Regards,
>>>> Chathura
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Himasha Guruge
>>> *Software Engineer*
>>> WS*O2* *Inc.*
>>> Mobile: +94 777459299
>>> [email protected]
>>>
>>
>>
>>
>> --
>> Himasha Guruge
>> *Software Engineer*
>> WS*O2* *Inc.*
>> Mobile: +94 777459299
>> [email protected]
>>
>
>


-- 
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
[email protected]
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to