Hi Chathura, Noted, will continue as we planned.
Thanks & Regards, Himasha Guruge *Software Engineer* WS*O2* *Inc.* Mobile: +94 777459299 [email protected] On Wed, Nov 12, 2014 at 8:24 PM, Chathura Ekanayake <[email protected]> wrote: > Hi Himasha, > > A chevron in a chevron diagram may refer to another chevron diagram or to > a process model. Therefore, we can't create an asset for a chevron until > the user has specified its type. I think we should not prompt user to enter > details like type of each chevron when modeling an abstract entity like > chevron diagram. Other issue is that user should be able to add chevrons to > a diagram, and some/all of those chevrons may not be modeled as a separate > process/chevron with next level of detail. Therefore, IMO creating an asset > for each chevron element in a diagram is not necessary. > > At this stage, let's avoid associating any details with individual > chevrons except the name and optional associated asset (i.e. process model > or chevron diagram). Later, we can improve this to load and display all > properties of associated asset when a chevron is selected. > > I think we can use the below xml format which is similar to the one we > discussed in the last meeting: > > <chevronDiagram> > <chevron id="c1"> > <name>Feasibility assessment</name> > <associatedAsset>processId</associatedAsset> > <chevron> > <chevron id="c2"> > <name>Recruitment</name> > <chevron> > <chevron id="c1"> > <name>Equipment procurement</name> > <associatedAsset>processId</associatedAsset> > <chevron> > > <flow source="c1" target="c2"/> > <flow source="c1" target="c3"/> > > <layout> > <position chevronId="c1"> > <x>120</x> > <y>200</y> > </position> > <position chevronId="c2"> > <x>250</x> > <y>120</y> > </position> > <position chevronId="c3"> > <x>250</x> > <y>280</y> > </position> > </layout> > <chevronDiagram> > > Note that the <associatedAsset> element is optional (chevron c2 doesn't > have an associated asset). As Sameera mentioned, we can support multiple > layouts for a chevron (by adding multiple layout elements in the xml). But > let's start with a single layout for now. > > Regards, > Chathura > > > > > > On Wed, Nov 12, 2014 at 10:19 PM, Sameera Medagammaddegedara < > [email protected]> wrote: > >> Hi , >> >> A small addition to the above: >> >> >> - A Chevron Workflow could have one or more layouts >> - The layout details need not be stored with the Workflow instance >> >> >> Thank You, >> Sameera >> >> On Wed, Nov 12, 2014 at 5:20 PM, Himasha Guruge <[email protected]> >> wrote: >> >>> Hi Chathura, >>> >>> After the meeting with Sameera, he suggested the following design model. >>> >>> Since every sub chevron element itself also represents a >>> process,suggestion was to create two asset types named chevron and chevron >>> workflow. >>> >>> 1.chevron.rxt : Includes all metadata >>> fields.(Name,Version,Provider,Predecessor,Successor,Process model) >>> >>> 2. chevron workflow.rxt: Includes following two fields. >>> >>> 2.1 *sequence*: This will hold all chevron ids that we draw on the >>> canvas. >>> >>> 2.2* layout:* This will hold the formatting data of chevron element >>> drawn on the canvas. Such as chevron id, positionX,positionY. >>> >>> Views for these 2 asset types will be as follows. Please refer [1]. >>> >>> 3.Create page for chevron asset type : User can enter metadata fields >>> listed, and on click of create button those values will be added to >>> chevron.rxt. >>> >>> 4. Create page for chevron workflow asset type: User can drag and drop >>> chevron icon can create their diagram. On click of create button, ids of >>> the chevron icons will be saved under sequence field, layout details in >>> layout field. An association will be made between the relevant chevron >>> asset and chevron asset workflow. >>> >>> 5. Chevron view page : Chevron related data (name, version etc) will be >>> loaded in a table while the associated diagram will be loaded in a canvas. >>> >>> The only catch is that all diagram related data ( layout and sequence) >>> will be saved in JSON format. Therefore no xml will be included. Are there >>> any restrictions such as the diagram should be maintained in xml format? >>> Please provide your feedback on this design suggestion. >>> >>> Please refer [1] for further reference. I will continue working on the >>> previous design model(with one asset type) until a decision is made. >>> >>> [1].chevron diagram editor design suggestion >>> <https://drive.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/view?usp=sharing> >>> >>> >>> >>> >>> Chevron diagram editor design suggestion.jpg >>> <https://docs.google.com/a/wso2.com/file/d/0B2gZ09XLMRjKTWZUU1g5X3RyRzA/edit?usp=drive_web> >>> >>> Thanks & Regards, >>> >>> Himasha Guruge >>> *Software Engineer* >>> WS*O2* *Inc.* >>> Mobile: +94 777459299 >>> [email protected] >>> >> >> >> >> -- >> Sameera Medagammaddegedara >> Software Engineer >> >> Contact: >> Email: [email protected] >> Mobile: + 94 077 255 3005 >> > > -- 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
