OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs-dex message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Minor Dexlib infrastructure issues


All,
 
Currently, it is difficult to see that there may be an issue raised against part of a template in dexlib. The following issues have been raised (under the TLSS program) to treat issues for templates in a consistent manner as other issues.
 
regards,
Tim.
NB to see infrastructure issues in Dexlib go to the menu items and click on "Tools", then (under Issue logs) click on "Infrastructure Issues",
 
 
TJT-2: Within the templateX/dvlp/issues.xml body, the list of possible field types available for an issue is not synchronised with the sections found within a template. Hence it is not possible to target the respective section where the issue arises; e.g. the fields such as Model Diagrams, Input Parameters, Reference Parameters, Instantiation path, Instance Diagrams and Characterizations. Those supported field sections which are available within templates (e.g. Cover and Contents) do not appear to load the respective issue when one of those fields is targetted.
 
TJT-3: Given that a template may be placed "in situ" (inside the capability whose functionality is supported by the template), it would seem natural that any issues within a template that was shown "in situ", would also be visible "in situ". Hence the capability should also refer (or collect) the template issues as well as the template(s).
 
TJT-4: Issues defined against a template (within templateX/dvlp/issues.xml), do not appear within the list of issues returned from the DEXLIB menu item "Tools",  "All issues" option. I assume that template issues are equally valid issues and should be visible here.
 
TJT-5: Issues defined against a template (within templateX/dvlp/issues.xml), do not appear to be accounted for in the Dexlib masterlist of capabilities (dexlib menu Tools/Capabililty Summary), where the table provides a total of all the issues for a specific capability. Given that the templates are visible "in situ" for a capability, should not the template issues also form part of the overall issues for that capability? If not, should the table have additional rows/columns to provide a place for the fact that a template (which implement the functionality of a capability), may have an issue?
 
 
 
*************************************************************************
*
* Mr. Timothy J. Turner BSC(Hons) MSc, MBCS
* Executive Consultant, System Integration Dept
* LSC Group, Lincoln House, Wellington Crescent, Fradley Park, LICHFIELD, Staffordshire WS13 8RZ, ENGLAND
* UK Switchboard: +44-1543 446800 Fax: +44-1543 446900
* US Mobile telephone: +1-843-4759179
* Mobile (UK) telephone: +44-7885-393225
* e-mail: tjt@lsc.co.uk <mailto:tjt@lsc.co.uk>  or timturner11@bellsouth.net  Internet: <http://www.lsc.co.uk/>
*
*************************************************************************
 


DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]