{"id":364,"date":"2015-10-04T12:14:11","date_gmt":"2015-10-04T10:14:11","guid":{"rendered":"http:\/\/www.medtech-ingenieur.de\/?p=364"},"modified":"2021-08-06T15:07:30","modified_gmt":"2021-08-06T14:07:30","slug":"requirements-engineering-mit-enterprise-architect","status":"publish","type":"post","link":"https:\/\/medtech-ingenieur.de\/en\/requirements-engineering-mit-enterprise-architect\/","title":{"rendered":"Requirements Engineering with Enterprise Architect"},"content":{"rendered":"

This blog post is intended to help anyone who still creates requirements specifications with Word and Excel. I myself have long used the "market leader" for requirements engineering and can only recommend switching to a tool. But why are tools useful, and what are the disadvantages of Word and Excel?<\/p>\n

As long as you're developing small, manageable systems, Word is certainly manageable. It becomes problematic when you have several hundred or thousand requirements and want to map different levels (system, hardware, software, mechanics). Then you reach your limits with Word. And I've experienced this myself several times. Problems that can arise include:<\/p>\n

    \n
  1. A customer requirement changes. What impact does this requirement have?<\/li>\n
  2. Have we derived all design requirements from the specifications?<\/li>\n
  3. Does each requirement have a test case and does it pass or fail?<\/li>\n
  4. How can I find out who changed what and when?<\/li>\n
  5. Can I create the traceability matrix automatically or do I have to fill out an Excel spreadsheet manually?<\/li>\n<\/ol>\n

    If these problems sound familiar to you, then I recommend using a requirements engineering tool. There are various tools on the market and you should take your time to find the right tool for your company. In this blog article, I would like to introduce a tool that is often not recognized as such at first glance. It is Enterprise Architect from Sparx Systems. The tool is particularly widespread in software engineering and is used for UML modeling. The tool also supports SysML, which makes it possible to manage requirements in a model. The cost of the tools plays a key role, especially for small and medium-sized companies. Enterprise Architect has the advantage that its prices, at around \u20ac200-600 per license, are very reasonable compared to other tools. Many companies already use the tool for modeling. In this case, it only makes sense to also utilize its requirements engineering capabilities.<\/p>\n

    How does requirements engineering work with EA?<\/h3>\n

    This functionality will be demonstrated using an example. The following image shows Enterprise Architect.
    \n

    \r\n\r\n\r\n\r\n\r\n\r\n
    \r\n

    Your contact person:<\/strong><\/center><\/h4>\r\n<\/td>\r\n<\/tr>\r\n

    Dipl.-Ing. Goran Madzar<\/span><\/strong>, Partner, Senior Systems Engineer\u00a0<\/span>
    E-mail: madzar@medtech-ingenieur.de<\/a>
    Phone:\u00a0\u00a0    +49 9131 691 240<\/a><\/td>\r\n    		\u00a0<\/td>\r\n<\/tr>\r\n

    Do you need support with the development of your medical device? We're happy to help! MEDtech Ingenieur GmbH offers hardware development, software development, systems engineering, mechanical development, and consulting services from a single source. Contact us.<\/p>\r\n

    make contact<\/a><\/center><\/center><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/div>
    \n    \"Enterprise<\/a><\/p>\n

    The model is located in the top right of the Project Browser. This is where elements, diagrams and data are located. The folder structure is used to separate levels hierarchically or to create chapters within documents. A document (e.g. a specification or test specification) can be derived from a folder or package in the Project Browser. The diagrams (shown in the middle) represent a view of a model. In this example, requirements are linked to one another. The requirement is documented in the Notes field. Each requirement has a unique ID and a title. In the Toolbox (left-hand side), elements or links can be dragged into a diagram to create them. The traceability of the selected requirements is visible on the right-hand side. Here you can quickly see where the requirement comes from, what it leads to and how it is tested.<\/p>\n

    What are the benefits of Enterprise Architect?<\/h3>\n