Reverse-Engineering an old software into JIRA

[Oliver Gindlhumer]

Hi, 

I am interested in switching our very old fashioned SW-development process to JIRA and according to what I have already learned, I would best do this using JIRA Software, Confluence and Bitbucket, as well as some JIRA-addon for testing. I generally am convinced, that this is pretty much precisely what our development process needs, as our software is a medical product and requires compliance with the standard IEC 62304.

However, what I am concerned about, is the process of integrating our software into the system and kind of reverse-engineer the link between software-requirements and specifications, as well as tests and their results.

I am yet to try this and the solution might be very simple, however I wanted to get a professional opinion about this, before I blow hours of work, that wasnt even necessary.  

In fact, the software, we are speaking about is over 20 years old and has constantly grown into countless numbers of different functions.

THanks in advance and best regards,

Oliver

[Aron Gombas _Midori_]

Oliver, I think you should ask more concrete questions to expect more useful answers.

To integrate your old software with JIRA (if this is what you mean), you can use the REST API or the Java API (P2 plugins) offered by JIRA. Both are proven, so you can rely on those.

[Oliver Gindlhumer]

Thank you for your answer.

Apologies for the lack of detail in my question. I thought it was clear enough to make sense, but youre right here.

Here is a more concrete attempt:

The software, we speak about is a medical device, hence complies with the standard IEC 62304 (Lifecycle of medical device software). Since I do have separate (non-JIRA) processes for tasks such as Risk-management and change/correction-management, I do want to use JIRA for planing, integrating, testing and documentation of SW-development-processes from now on.

What the standard generally asks for is some traceability between SW-requirements, specifications including acceptance criteria and documentet testing of components for these specifications. 

While I have a general idea of how to design my workflows and issues in order to live that process, I am not sure yet, how to recreate these links between SW-requirements and specifications (components and units in my code) for all the parts of the software, that was created without JIRA.

Is there a way, to minimize the effort in creating all SW-requirements and connect them with components and units in the my repository?