Sparx Systems Forum

Enterprise Architect => Suggestions and Requests => Topic started by: NickBs on August 13, 2018, 09:12:12 pm

Title: A lot of text in doc convert in requirements
Post by: NickBs on August 13, 2018, 09:12:12 pm
Someone know scripts or add-in for parse doctype? I'm have a lot of requirements and do it by hands is bad idea.
Example of text:
1. Test
1.1 req1 text:
-text;
-text;
1.2 req2 text
Title: Re: A lot of text in doc convert in requirements
Post by: qwerty on August 13, 2018, 09:46:49 pm
In my old days we used DOORS for that. I'd guess it's still used. And looks the same as in the 90's...

q.
Title: Re: A lot of text in doc convert in requirements
Post by: NickBs on August 13, 2018, 10:31:47 pm
Oh, i check it. It's kinda pretty but... not EA.  :-\
Title: Re: A lot of text in doc convert in requirements
Post by: Uffe on August 13, 2018, 11:45:27 pm
Hi Nick,

eaDocx might be worth checking out, they might be able to do something along those lines.

/Uffe
Title: Re: A lot of text in doc convert in requirements
Post by: qwerty on August 14, 2018, 02:00:43 am
Yes. DOORS is not EA. But it's designed for handling requirements. And you can use either the DOORS MDG or a simple script (I preferred that) to get the requirements into EA.

q.
Title: Re: A lot of text in doc convert in requirements
Post by: steen.jensen on August 14, 2018, 06:16:51 am
The Office MDG can parse word-doc if there is some structure.
I use it time to time to convert word-doc to EA requirement
Title: Re: A lot of text in doc convert in requirements
Post by: NickBs on August 14, 2018, 05:57:52 pm
Thanks, but DOORS too massive solution for our integration. Also, it's no small script for this... i'm examine the features of the structure of word files and realized that this is a Pandora's box.  :-\

I looked at MDG, good software but not suitable for our document structure.

Thankyou evryone!  ;D
Title: Re: A lot of text in doc convert in requirements
Post by: qwerty on August 15, 2018, 05:12:55 am
Guess why DOORS is such a monster xD

q.
Title: Re: A lot of text in doc convert in requirements
Post by: Sunshine on August 15, 2018, 07:20:30 am
Thanks, but DOORS too massive solution for our integration. Also, it's no small script for this... i'm examine the features of the structure of word files and realized that this is a Pandora's box.  :-\
Yep spent a long time using DOORS back in 1997 - it was a beast then.

I looked at MDG, good software but not suitable for our document structure.
Why is that ?

Looking at your example text
Quote
Example of text:
1. Test
1.1 req1 text:
-text;
-text;
1.2 req2 text
I can state categorically that I've had very similar structured documents and managed to import successfully using the Office MDG. Takes a bit of experimentation but it works.

Is the document inconsistent/ badly structured? I've found I've been able to import a lot of MS word docs using the Office MDG by pre-processing the doc using search and replace or scripts to fix that type of problem before importing using the Office MDG.
Remember MS word has some very powerful text manipulation built in so you could reformat the doc so its easier to import into Sparx EA.

Alternatively you could save the doc as Word XML and use XSTL to transform into a CSV then import that.

The last option is to go through the doc and manually reconstructed it in Sparx EA using cut and paste. But that would be tedious.

Well there are some alternative approaches  on tackling your problem for you to investigate further. However I'd be tempted to investigate the Office MDG further.
Title: Re: A lot of text in doc convert in requirements
Post by: NickBs on August 17, 2018, 07:09:35 pm

Looking at your example text
Quote
Example of text:
1. Test
1.1 req1 text:
-text;
-text;
1.2 req2 text
I can state categorically that I've had very similar structured documents and managed to import successfully using the Office MDG. Takes a bit of experimentation but it works.

Is the document inconsistent/ badly structured? I've found I've been able to import a lot of MS word docs using the Office MDG by pre-processing the doc using search and replace or scripts to fix that type of problem before importing using the Office MDG.

We cannot use headings to indicate our requirements. And so they were reserved for the Chapter. Although, there are some ideas, but it adds to the work. But well, i think it's good idea to test MDG. Maybe maybe. ???

No, we can't import tables because of different languages, EA just throws garbage, and you can't change UTF when importing CSV. But if someone knows how it can be organized, I will be glad.

Title: Re: A lot of text in doc convert in requirements
Post by: Geert Bellekens on August 17, 2018, 07:31:40 pm
I would probably write a bit of code (either C#, VBA or VBscript) to get the data out of the Word document.

I've done something similar in the past to get descriptions from a word document into EA (to be able to generate the whole document from EA)

Geert
Title: Re: A lot of text in doc convert in requirements
Post by: Sunshine on August 18, 2018, 09:08:38 am
We cannot use headings to indicate our requirements. And so they were reserved for the Chapter. Although, there are some ideas, but it adds to the work. But well, i think it's good idea to test MDG. Maybe maybe. ???

No, we can't import tables because of different languages, EA just throws garbage, and you can't change UTF when importing CSV. But if someone knows how it can be organized, I will be glad.
Okay so it sounds like you haven't given us enough info to help you.  The example you provided looks like headers were being used for requirements. Don't you what your reference to chapters are. I'm total confused and have no idea what your MS word doc looks like now so your going to have to explain further.
Sounds like your requirements maybe written in a language other than english is that correct?
Do you have any programming/scripting skills ?
Title: Re: A lot of text in doc convert in requirements
Post by: NickBs on August 20, 2018, 06:24:30 pm
I would probably write a bit of code (either C#, VBA or VBscript) to get the data out of the Word document.

I've done something similar in the past to get descriptions from a word document into EA (to be able to generate the whole document from EA)

Geert

I also thought so at first, but after examine the structure of word, I realized that it is quite difficult.

We cannot use headings to indicate our requirements. And so they were reserved for the Chapter. Although, there are some ideas, but it adds to the work. But well, i think it's good idea to test MDG. Maybe maybe. ???

No, we can't import tables because of different languages, EA just throws garbage, and you can't change UTF when importing CSV. But if someone knows how it can be organized, I will be glad.
Okay so it sounds like you haven't given us enough info to help you.  The example you provided looks like headers were being used for requirements. Don't you what your reference to chapters are. I'm total confused and have no idea what your MS word doc looks like now so your going to have to explain further.
Sounds like your requirements maybe written in a language other than english is that correct?
Do you have any programming/scripting skills ?

Yes, right now i'm writing a bunch of scripts for EA. I looked into the script to import CSV files, but it looks like it is only for the rules of building tables.

There how look architecture. I had to cover the data. If that's not enough, I'll think of something else.

(https://i99.fastpic.ru/thumb/2018/0820/a5/_100e888d53fbae0c74da3b61a001e4a5.jpeg) (https://fastpic.ru/view/99/2018/0820/_100e888d53fbae0c74da3b61a001e4a5.png.html)
Title: Re: A lot of text in doc convert in requirements
Post by: Geert Bellekens on August 28, 2018, 12:35:15 am
Hi Nick,

You might want to use a different image hosting site like imgur.com

The one you are using is not exactly safe for work. A bit annoying for those of us using the forum at work  ;)

Geert