...

Page info
title title

...

• The AIM principle investigator under supervision from NCI imaging leaderships maintains the AIM model.
• A requestor for any AIM improvements must create an account with NCI JIRA, https://tracker.nci.nih.gov/secure/Dashboard.jspa, and participate in the imaging community activities. See Figure 3, which follows.

Image Modified

Figure 3. Requesting a JIRA Account

• Enhancements to and new requirements for the AIM model must be submitted to NCI JIRA at https://tracker.nci.nih.gov/browse/AIM. A requestor shall provide Do the following to request an enhancement or new requirement.
  
  • Create an issue as a User Story issue type, Figure 4.

Image Modified

Figure 4. A Request Type of "User Story"

Use
• • Describe the use case and examples.
  • Identify what needs to be added or changed or suggest a solution.
  • The requestor must be willing to communicate with and provide sufficient information to the AIM team members in order to clarify, if any, requirements and use cases.
  • The requestor shall provide contact information such as e-mail address and telephone number.
• Approval and rejection process – see the Acceptance Policy

...

• A requestor for any toolkit and software products improvements must create an account with NCI JIRA at https://tracker.nci.nih.gov/secure/Dashboard.jspa and participate in the imaging community activities.
• A requestor must enter new requests in an appropriate AIM project. There are three related AIM projects:
  
  • Annotation and Image Markup – Information Model (AIM)
    
    • AIM library and ANIVATR
    • https://tracker.nci.nih.gov/browse/AIM
  • Annotation and Image Markup – Enterprise Service (AIMES)
    
    • AIM Template Builder (ATB)
    • AIM Template Service (ATS)
    • https://tracker.nci.nih.gov/browse/AIMES
  • Annotation and Image Markup – Workstation (AIMWS)
    
    • AIM Workstations
    • https://tracker.nci.nih.gov/browse/AIMWS
  • Create an issue as "New Feature", "Bug" or "Improvement"
    • Select "New Feature", Figure 5, to recommend a new capability to an AIM-related software.

Image Added
Figure 5. A Request Type of "New Feature"

• • • Select "Bug", Figure 6, to report software defect.

Image Added
Figure 6. A Request Type of "Bug"

• Select "Improvement", Figure 7, to request an enhancement to the existing software feature.

Image Added

Figure 7. A Request Type of "Improvement"

• A requestor must be willing to communicate with and provide sufficient information to the AIM team members in order to clarify, if any, requirements and use cases.
• The requestor shall provide contact information such as e-mail address and telephone number.
• Software contributions to the existing software products are welcomed and encouraged. Contributors must register for an NCI JIRA account.
  
  • A new contribution to be considered for inclusion to an existing software product must be entered into the respective AIM JIRA. The AIM development team will review and approve it.
  • The contributor must be willing to communicate with and provide sufficient information to the AIM team members in order to clarify, if any, requirements, use cases and quality assurance process.
  • Any software contribution must be released under BSD 3 license
• Approval and rejection process – see the Acceptance Policy

...

The imaging community brings imaging experts and users of in vivo imaging together to address requirements and AIM usage. Community members use AIM library and derived AIM software products and provide feedback to the AIM team. The diagram, Figure 8, depicts the procedures of the AIM project. Any requests for improving, enhancing, and bug fixing must be entered into NCI JIRA as described in section 1.2. There are three sub-projects under the AIM project: AIM Model, AIM Enterprise Service, and AIM workstation.

New inquiry and enhancement requests for the AIM model or "AIM Model Use Cases Requirements" must be submitted to https://tracker.nci.nih.gov/browse/AIM. Once the AIM team accepts a new request to be included in AIM model, the model and accompanying documentation describing any additions and changes are released for public review and comment. The AIM team and its advisors review incoming feedback and work with requested parties who provide comments and suggestions. If need be, the AIM team releases a revised AIM model and repeats a public review process. All corresponding messages of a JIRA issue shall be entered in the NCI JIRA. After a model has been finalized, the AIM team performs the SIW [1] process and submits the model to the EVS team for review and approval. Once the model is approved, it is submitted to the EVS team to be published to the caDSR [2]. At the same time, the AIM team makes a request to release a new AIM model from the NCI program officer before a public announcement can be released to the public. While the new AIM model is being submitted to caDSR, the AIM team also works on a new version of the AIM C++ software library as well as an AIM XML schema for public use. Changes to the library are also incorporated to ATB, ATS and the AIM workstation. Both the AIM library and AIM XML schema will have to go through a software quality assurance (QA) process. After they pass the QA process, the AIM team makes a request to the NCI program officer for public release of the library and schema. Once approved, the library and schema are uploaded to NCI AIM GitHub for public use. A software and schema releases will be publicly announced.

Any new software features, improvements, and bug reports must be submitted to NCI JIRA under the appropriate software products per the policy explained in "AIM Toolkits and Related Software Products Policy" in section 1.2. The AIM team and its advisors review incoming requests. The AIM team works with interested parties who provide requests and suggestions. All corresponding messages of a JIRA issue shall be entered into NCI JIRA. Accepted requests are scheduled for implementation according to available resources and time allowed for each software development cycle. Each request is associated with a version of a software release. Once a software version is ready for a release, it must go through a QA process until all identifiable software bugs have been resolved. After a software version passes the QA process, it is uploaded to the NCI SFTP. At the same time, the AIM team makes a request for software release with the NCI program officer. An announcement is issued after an approval has been granted.

Image Added
Figure 8. Procedures for the AIM Project

References

1. Semantic Integration Workbench. URL: https://wiki.nci.nih.gov/x/QYEI Access 2013-09-30.
2. Cancer Data Standards Registry and Repository. URL: https://wiki.nci.nih.gov/display/caDSR/caDSR+Wiki#caDSRWiki-AboutcaDSR Access 2013-09-30.

...