ERAGON is a CI/CD and reporting tool with the capabilities of using DOORS, JIRA and GIT at the same time.
It runs on a server computer and checks the code, requirements and test procedures for a period of time. It uses capabilities from Test Management Tool, Code Checker Tool, Requirement Checker Tool, DOORS Filter Tool, Folder Checker Tool.
** Earnings
- It reduced the License Cost at least fifty percent.
- It provided immediate cure for the pain in the test, code or requirements.
- The audits got easier and it is really liked by the audit team. Because we could show all the things in a linked hieararchy with reason and result.
- It also reduced the workload on teams.
----- CODE ----
- For code; it reads the code from the GIT repository and performs these checks:
- Coding Standard Check; (The coding standard of the company. It can be defined and changed at run time)
- Code - Requirement Traceability Check (In DO-178C, codes are tied to Low Level Requirements. We store LLRs and class definitions on DOORS as linked to each other. Thus we can query the tracability state of a class definition)
- Aged Code Files; ERAGON lists the files that are not commited or changed for a long time (user defined).
- TBD: Build and Logs; In the future, it will build the current code in main branch, and send e-mail to the person who did the related commit/merge.
----- TEST ----
- For test; it reads all the test procedures and sources from GIT repository and perform some checks like in TMT:
- Test Standard Check; (Used macros, sources and syntax are checked)
- Test - Requirement Check; (We store the requirements on DOORS and TMT can automatically fetch the related requirements of a test procedure. It logs the test procedures without requirements or requirements that are open)
- Open JIRA Issues on Tests; (Each fail on a test result are tied to a JIRA issue. TMT makes it compulsory to close these issues for the test author. ERAGON shows the open issues on test documents.)
- Open Review Items on Tests; (TMT can operate a review action for a test procedure document and stores it in a DB. ERAGON reads this DB and logs the open review items.)
- Aged Test Documents; ERAGON lists the test documents that are not commited or changed for a long time (user defined).
- NotRun Test Documents; It also lists the test documents that are not run and created test run results for a long time (user defined).
- Auto-Publish; It creates TMT Publish Catalog automatically on a web server.
- TBD: Auto-run and report (Some tests can run automatically without user prompt. These kind of tests can be run automatically on a certain time of the day)
----- REQUIREMENTS ----
- For requirements, ERAGON creates dxl scripts at run time and uses DOORS as a requirement DB.
- Requirement Standard Check; (Legal/illegal keywords, attributes, attribute values etc.)
- Requirement Change Log ; (ERAGON stores the last requirement document and whenever a change occurs, it finds the related code/test documents and creates notification)
- Traceability Check; (All requirements should be traced to code/tests and there must not be any open requirement. ERAGON lists the open requirements).
- Custom Filters/Checks; User can define any filter and target module set to be applied. ERAGON creates notification when any object occurs in the filter)
- JIRA Changes; Each baseline in a module is tracked with a JIRA Issue. ERAGON finds the change in related JIRA Issue and notifies the DOORS module to be reviewed.
----- FILE SYSTEM ----
- For disk drives and network drives, ERAGON can perform some checks in file system :
- File Duplication; (it creates a CRC-32 code for each files in the drive and finds the duplications using this code)
- Changes in a Directory; (it immediately notifies the user when a file is added/deleted/updated/renamed)
- File Storage; (it notifies the user when the capacity is about to reach to the maximum)