Enterprise Architect Visual Studio (VSTS) Integration

Transcription

1 Enterprise Architect Visual Studio (VSTS) Integration Model and gather requirements in Enterprise Architect Integrate EA with Visual Studio / TFS Theresa Ruhnke Team Leader Microsoft Technology Centre Statistics Canada

2 Be able to answer these questions What features, use cases, fixes are included with every application release? Is the work we are planning the highest priority? Does that bug apply to more than one use case? When was that approved? Is that object reusable for this other use case? and so on...

3 Trace and share work, from start to finish

4 Use these 3 tools together to be able to answer those questions on any given day. Key: Get buy in from your team EA Team Buy In TFS VS

5 Topic Overview Use Case modelling approach Requirements Generating a test suite Integrating with Team foundation server Customizations & Add-in TFS Query Research possibilities

6 Use Cases with Structured Scenarios Model your Use Cases, gather requirements Build a quick Use Case diagram

7 Linking Requirements Categories of requirements (business, functional, supplementary, custom) Linking capability (matrix view, model view)

8 Structured Specification Its a more formal version of the User story Describes the flow of a Use case in a step-by-step fashion Explores alternate and exception paths Tip: Helpful tool to manage the scope of the Use Case Let s look at the structured scenario for Display Account Balance

9

10 Why create an Activity Diagram? Facilitate discussion between subject matter experts and system analysts Can be used to generate test cases that cover Basic path Alternative path Exception path So simple and fast to generate

11 Use your activity diagram to generate your test suite Test cases can be as detailed as needed by your work unit quality assurance needs Freedom to customize the test suite apart from the UC Tip: if the UC goes through a major revision, your Test suite will also have to be revisited. My project approach: Emphasis was on testing each alternate path Organize and group the individual test cases under a parent test suite. One test suite per Use case.

12 Create a test suite from the Activity Diagram Open your UC to the structured scenario tab and choose external test case. Change the stereotype to test suite Import the steps using the activity diagram Generate more test cases. Generally, we created one test case per path.

13 Example of test suite In the Display account balance UC example, there were 4 paths we chose to test in the activity diagram.

14 Summary Use Case & Test workflow Use Case Model Structured Scenarios Activity Diagram Generate Test Suite Test Cases Useful tools for tracking, organizing, monitoring and planning work for software development Team Foundation Server Jira Etc. Let s integrate them with our EA repository

15 Query the EA repository The EA repository can be queried by a knowledgeable t-sql programmer Tip: <control> + <space> Blog tutorial: Harvesting the power of EA s SQL searches

16 EA custom add-in with V9.3 of EA The user forums are a great resource A question posted here was answered by a fellow EA developer that night Tutorial: Create your first C# Enterprise Architect addin in 10 minutes The complete Enterprise Architect C# add-in template Testing and debugging your Enterprise Architect C# Add-In Tutorial: Deploy your Enterprise Architect C# add-in with an MSI package

17 Our add-in We created an add-in that would export test cases from the approved package within our EA repository, including the steps We then imported the test cases into our Team Foundation Server project EA repository Test Cases with steps MS Excel Worksheet with test cases TFS Test Cases With steps

18 Team Foundation Server Create customized Work Item Types My team created the following Use Case workflow In the beginning, when we were learning each stage took longer. Each stage shortened as we gained experience Tip : don t go overboard!

19 Linking TFS work items Organize your work Know what is in every deployment Powerful linking, traceability of work to requirements Use Case Test Case Bug/ Enhancement Build

20 Example Link a Test Case to a Use Case Link a Bug to a Test Case

21 Traceability report Parent/child power of linking

22 Team Buy In Lessons learned This solution works well if everyone on the team participates Do demos early on to make sure everyone is comfortable Reports are only valid if the team uses the tool to report their updates Tip: Keep your tracking as light as possible the bare minimum needed for communication and planning

23 Version control of EA with TFS Version control settings, viewing the history of an element. vs. built in baseline Best practice: force a comment, make sure its descriptive

24 Research possibilities Change the add-in so that the source package isn t hardcoded Make an add-in that exports Use cases to the TFS user story to see how they align Install MDG plug-in, which allows to browse EA repository from within Visual Studio Experiment with more custom templates

25 Big Thank You to my Team Thank you to my teammates, who contributed many pieces of this research: Jen MacDonald, Li Wang, Eric Chowns, Martin Brière Marc Bryar, Stephanie Lansbergen, Steeve Mallet, Harold Craswell, James Mullins, and all of the Cygnus section

26 Demo EA TFS

27 Statcan EA User Group Interested in creating an EA User group here at statcan? Theresa.Ruhnke@statcan.gc.ca

28 Questions TFS portal created as a reference material for this demo tdashboard_wss.aspx (available to statcan employees only as it is on an internal nework)