Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Steven Bos

Pages: [1]
1
Uml Process / Re: Requirements model vs User Stories in scrum to
« on: July 06, 2016, 06:08:38 pm »
We have the same challenge at the moment.  The agile coach has said that user stories only exist for the life of the project

I would just ignore that coach and just notify him that we will preserve the user-stories till the end of dawn.

We still have some architect requirements requirement and users stories we have documented as features/requirements. So a user story has a dependency with an architectural requirement for us. For now it works but it might evolve in something else if needed. Remember - it is SCRUM - something that migth work for one SCRUM-squad might not work for the others. It is a framework so use whatever works best for your team. But it helps if all the teams have a general standard way of using Sparx so it is easier to share information.

2
General Board / Re: AS-IS and TO-BE Modelling
« on: July 06, 2016, 05:11:42 pm »
the filter option is not helping if you want to see the same component in a state of AS IS and TO BE.
Then you are either stuck to version control and maybe you want to have a look at the versioneer tool from LieberLieber.

https://www.youtube.com/watch?v=PocUexhgW0E

We have chosen for now for two repositories --> the O (development) and the P (production) from OTAP (developement -> test -> acceptance -> production). Maybe later we go for whole OTAP process for EA as well.
Basically we are making an XMI-export as it was code and release an XMI file from the O (development environment) to the P (production environment).

in the end we hope it will result in repositories that represent their related environment in the real world. An advantage will be that we will follow and time the same procedures as the rest of the SCRUM squad so we increase our interaction with them. The other reason is now almost everybody is using EA within the SCRUM team so this release system has our preference. Also the programmers were not too happy about another version control system. It added to much documentation for them to do version control on code and to do version control on their diagrams.

3
General Board / Re: Usage of Version Control - opinion requested
« on: June 16, 2016, 05:40:32 pm »
I already had a feeling something was of with this Version Control.
That is why I asked the question. Arguments from experts on a forum like this do help me strengthen my case of not using Version Control. Now I am sure of it.

Yesterday we also had some discussion regarding backups/snap-shots to other repositories or usage of the Baseline to compare repositories. Also the whole configuration of Subversion or the cost from TFS are to steap to just give it a try.

I will try to convince them to go for the snapshot version for now and to store the snapshots on a server with backup functionality.

Thanks for the answers,

Steven

4
General Board / Usage of Version Control - opinion requested
« on: June 15, 2016, 06:45:25 pm »
Hello,

So we are looking at a current project on what we will or will not use for a Shared Repository to be used by multiple teams. One of the things that have to pass our decision tree is Version Control. Now we do understand how helpfull Version Control is but we now got stuck in finding/selecting the proper Version Control tools.
Questions from me to you.

1 - Are you using Version Control?

2 - What are you using for Version Control?

3 - How easy was Version Control for you to install?

4 - How many additional software packages did you have to install to get it all to work?

5 - How user friendly is the Version Control you are using?

Yes, it is a list but we want to make sure that it is easy to install, easy to use, easy to maintain and most of all does not cost us a suitcase full of money.
In the end - is it really worth all the money and trouble to get it installed?

5
Suggestions and Requests / Re: Add-In for TFS request
« on: November 04, 2015, 12:20:22 am »
Quote
Thanks qwerty :D

But yes indeed I would be happy to. As it so happens to be I'll be in Den Haag tomorrow :)

Geert
Damn - today in Utrecht. I will be in Den Haag on wednesday.

Guess I have to learn how to write add-in

6
Suggestions and Requests / Add-In for TFS request
« on: November 03, 2015, 03:04:48 am »
Yes, TFS - it is what a company decides but I have to work with it.

So the main question: can we have a TFS add-in again for V12 of EA so we can synchronise our requirements?

Many thanks in advance

7
General Board / Re: What to install to connect TFS and EA
« on: November 03, 2015, 02:51:51 am »
OK - the update with the GUID has annoying feature which I might have to post as a bug.

Situation is that I have 'root' package for the requirements.
- req1
- req2
- package1 with req3
- package2 with req4

If I am now 'refreshing' the requirement including the GUID for these four requirements the root package looks like this:
- req1
- req2
- req3
- req4
- package1 <-- empty
- pacakge2 <-- empty

Bit of annoying that all the requirements are moved from their packages to the root package.

8
General Board / Re: What to install to connect TFS and EA
« on: September 16, 2015, 09:00:36 pm »
OK - working with CSV import/export (for now)

Things to look at:
- make sure the same status from TFS are known within EA.
- replace the Work Item for Requirement - EA does not know what a work item is.

After that import of requirements is easy. Now I just have to see how synchronize without a load of doubles creation.

9
General Board / Re: What to install to connect TFS and EA
« on: September 04, 2015, 04:32:01 pm »
I have installed the Visual Studio Community version. This makes it possible to link with a Visual Studio project from EA.

At least now I can do:
- version control
- reverse engineering on code
- security with TFS

Still missing is getting the Work Items from VS linked to EA. Seems that you have to be a Project Administrator to config this in VS. Today a collegaue is going to give it a try for me to setup these Work Item Area's.

10
General Board / Re: What to install to connect TFS and EA
« on: August 24, 2015, 05:55:52 pm »
Quote
IIRC there's a free edition of VS that only contains the TFS part and not the developer part of Visual Studio.
Found one but that does not have the Project Explorer you need to setup TFS.
You got a link to this free VS package so I got the correct one?

11
General Board / What to install to connect TFS and EA
« on: August 21, 2015, 01:43:41 am »
Hello,

We have a nice amount of user stories stored in TFS. Now I want make a connection with TFS and trace the PBI from TFS with any artifact within EA. Now it seems I need to install Visual Studio and TFS and ... a lot.

Question: Due to cost and licensing I want to know what bare minimum do I have to install to make a connection between EA and TFS?

I use the EA12 Ultimate edition and have nothing regarding Visiual Studio installed (I am no programmer but the designer/requirements man).

12
General Board / Re: Requirements in TFS
« on: November 03, 2015, 02:58:16 am »
The older version of EA like Version 11 do have these feature with a TFS connection installed.

If you are using EA V12 then the TFS add-in is gone. This is a feature I also would love to have since companies are still not seeing the light and using TFS.

13
Bugs and Issues / Re: Import moves element from packages to root pac
« on: November 04, 2015, 12:47:22 am »
Somehow I have overlooked the Preserve Hierarchy option in the Import/Export setup. This seems to work now.

Next challenge is to merge an export from TFS and an export from EA into a new import for EA. Then the POC says I got it working.

After that - it is add-in creation study time.

14
Bugs and Issues / Import moves element from packages to root package
« on: November 03, 2015, 02:54:13 am »
OK - the update with the GUID has annoying feature which I consider a bug since it is moving an element from its package to the root package.

Situation is that I have 'root' package for the requirements.
- req1
- req2
- package1 with req3
- package2 with req4

If I am now 'refreshing' the requirement including the GUID for these four requirements the root package looks like this:
- req1
- req2
- req3
- req4
- package1 <-- empty
- pacakge2 <-- empty

Bit of annoying that all the requirements are moved from their packages to the root package.

Pages: [1]