Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

View file
nameAgile Process 3.2 with AIP Console V1.0.docx
pageAgile Onboarding Process with AIP-Console
spaceFBP
height250

Agile Onboarding Process Overview

...

  1. Gaps Addressed:
    1. Check whether the open questions as identified in the transaction report has been addressed by the customer?
    2. Ensure that the missing software components are delivered by the application team
    3. In case of gaps that are still open, contact the application team to receive the inputs Or take an Informed exception
    If yes, handover to AO: The Expert has to handover all the application related information along with the relevant report (Rapid Discovery Report)
  2. Upload the new zip again
    1. Reject the current version
    2. Upload the zip code again with the gaps addressed . Best Practices for zip folder:
      1. For Java

        • The folder structure should be the same as it is there in the SCM which project team is using. Including complete hierarchy of ALL .pom and parent .pom files. These files will allow the automated discovery and analysis configuration.

        • In the case of maven project: a copy of the local maven repository should be provided in the zip

        • Library files for Java technology should be present in the zip folder

      2. For .NET
        • Usually, the source code is versioned using tools like SVN or Git. 
        • The best way to deliver source code is to use the CMS and check out the source code of the version that has been selected for analysis. Make sure to NOT include the ".git" or ".svn" folders
        • Include the "bin" folders that contain binaries (debug and/or release assemblies) that are created at build time. They should also contain third-party assemblies.
      3. For Mainframe
        • PDS can not be included in case of AIP console
        • Each application must be delivered in a single folder. 1 file per object type.
        • 1 file per program, 1 file per copybook, 1 file per JCL job, etc in the folder structure as shown in the image below
        • Image RemovedImage Added
  3. Modify the zip file/folder and upload, Run analysis again 
    1. Follow all the steps that identified as applicable in step-6 (Setup CMS, Run analysis and snapshot) of Discover phase
    2. Setup Environment & Analysis configuration 

      1. Source code “File Adjustments” (Optional)

      2. “Preprocess” Source Code (Optional) - In some situations, the source code cannot be parsed and must be pre processed. A study should be done first to identify the pre processing rules which must be applied to the source code. Add Pre processor batch file ‘Tools Before Analysis’ under Content Enrichment tab

    3. Verify Framework Settings if there is any issue identified during log / result validation.

      1. Ensure that correct versions of technologies and frameworks are selected

    4. Adding dependencies – add the dependencies between analysis units (if required)

    5. Fine-tune  settings

      1. Choose an Environment Profile if needed (Only Product supported profiles)

      2. Configure include/classpaths according to the technology

      3. Enable User Input Security if it is within the scope of the analysis

  4. KB Inventory Validation (FEAC):
    1. Check if all the technologies/frameworks have been analyzed properly
    2. Check if all the files have been analyzed properly ( Files in DMT vs files in KB )
    3. Validate for the check on 'Unexpected Objects Count' 
  5. Log Validation :
    1. Follow the troubleshooting process to remediate warning and errors by referring to product documentation available at https://doc.castsoftware.com/display/DOC83/Validate+analysis+based+on+log+messages
    2. Document the log validation results: Number of alerts, type of alerts, and tickets raised (if any). In case if any alert is remediated, put up the process of remediation of the alert.
  6. Review Dynamic Links: ( AALV )
    1. Create application-specific DLM rules to resolve the dynamic links
    2. Guidelines to validate the dynamic links are available in https://doc.castsoftware.com/display/DOC83/Validate+Dynamic+Links
  7. Module Configuration : 
    1. Set up the module content according to the client’s requirement
    2. Validate the check on 'Overlapping Objects count'
    3. If no recommendation, retain the Full Content
    4. Guidelines to create user-defined modules are available in https://doc.castsoftware.com/pages/viewpage.action?pageId=200409226
  8. Health Measures Configured :

    1.  In AIP Console, validate all the checks which fall under category - Quality Measures in the snapshot indicators
  9. Architecture Checker Flow:
    1. If the app team has provided the information then configure the Architecture Flows
  10. Security Configuration:
    1. Validate the security settings and results for JEE and .Net applications Dataflow onboarding process for AIP 8.3.3+ ( if it is in scope )
  11. Transaction Configuration (FERC):

    1. Entry point configuration / Data Entity configuration / End of transaction configuration

      1. Trace the transactions based on the entry and endpoints given rapid discovery report

      2. Validate the empty transactions under Incomplete transactions report which will help in the identification of missing links. Document any broken transactions and missing links in Confluence

      3. Create specific entry/endpoints for transactions which have not been identified in the Rapid Discovery Report 

    2. Review Transactions

      1. Verify if there are artefacts with high Data Element Types (DET) / Record Element Types (RET) values. If there are then check the objects with issues and remediate them - Use Snapshot indicator Large SCC count to identify large SCC group. (If the issue still exists, raise a support ticket)

      2. Check the code coverage i.e., validate that all artefacts are covered in the transactions - Use Snapshot Indicator Artefacts in transactions to validate the artefact coverage

      3. If there are a few artefacts which do not belong to any transaction, investigate if they are in scope of module definition

  12. Perform the Function Point validation checks
    1. Transaction Completeness Report: Following will help you to decide whether transaction configuration is complete . 
      1. In AIP Console, validate all the checks which fall under categories Transactions , Functional Size & Enhancement in the snapshot indicator 
    2. Transaction Complete: Verify the above checks to ensure that the transactions are configured properly and complete 
      1. If empty transactions exist, follow the steps below, 

        1. If this is a configuration issue, go back to analysis configuration

        2. If this is a standard framework supported by CAST, raise a Support ticket

        3. Add links between objects that are not recognized by AIP out of the box only if there is an approved workarounds from support and R&D (through the Reference Pattern process, Knowledge Base (KB) update queries, and supported extensions to create missing objects/links)

        4. Once the link is completed in Enlighten, compute in the Transaction Configuration Center (TCC), validate the flow, and continue with activity in Step b.

  13. If FP is enabled, then in AIP Console, validate all the checks which fall under categories - Transactions , Functional Size & Enhancement in the snapshot indicator and FEFC to validate additional transaction configurations and calibrations
  14. Run Snapshot and Validate results:
    1. Run Baseline snapshot
    2. UI validation
      1. Launch dashboard via AIP console
      2. Validate if Engineering Dashboard pages are displaying data correctly e.g., Transaction-wide Risk Index (TwRI) page, Risk Indicator pages, Critical Violation pages, Compare Version pages
      3. If there is an issue with the above step, follow the Troubleshooting Process
    3. Inventory Validation
      1. In AIP Console, validate all the checks which fall under categories - Source Code and validate with the inventory
      2. Validate the number of files, classes, tables, and artefacts per technology. If the numbers are not as expected, follow the Troubleshooting Process
      3. If this check is for maintenance, validate the variation in data from Snapshot Comparison view on HD
    4. Engineering Dashboard Metrics validation:
      1. Check the number of critical violations and validate few of them to see if there are any false positives. If there is any false positive, follow the Troubleshooting Process
      2. Check the other metrics such as Technical Debt, Cyclometric Complexity
      3. If this process is for maintenance, check the evolution
      4. FP count must match with FP count in TCC
    5. Analytics Dashboard Metrics validation:
      1. Consolidate Engineering Dashboard with Health Dashboard , if application is not visible on Health Dashboard ( In case if Integrated dashboard is used, this step will not be required )
      2. Link HD to ED if the navigation from HD to ED is not working ( In case if Integrated dashboard is used, this step will not be required )
      3. Validate that the numbers displayed on Health Dashboard must match with Engineering Dashboard
  15. Verify Analysis Completion Report: Use FEDC reports to ensure that the quality of analysis is good
  16. All Checks Passed: A list of checks are executed at this step to ensure the quality of results - if any check fails then it will lead to a exception review
  17. QA - Onboard phase:
    1. Review the Analysis results, entry and endpoints as defined in the transaction report, validate the smell test results justification, dashboards and delivery report as per the checklist
    2. QA checks to review the process followed so far and give the go-ahead to deliver the refined dashboard to the customer
  18. Consumption Report: ( PRRC and FENF)
    1. Upon the go recommendation ,  the refined measurement and Consumption Report is delivered to the application team
    2. Extensions PRRC and FENF can be used for preparing consumption report

...