Displaying items by tag: requirements traceability,

Capturing and communicating business needs as requirements is a critical task of a Business Analyst.

Requirements Repositories allows capturing those requirements once, then have them available to you and your team for the projects lifetime and beyond. Using Requirements Management tools like Enterprise Architect, the captured business requirements can then be transformed to a formal requirements specification according to the business information needs and views of every relevant stakeholder. Also validating these specifications by tracing from the requirement specification and solution components at every level directly back to the business requirements helps you create the most accurate solutions imaginable. This webinar shows how to use Enterprise Architect for building and managing a requirements repository. You will also learn how to establish requirements traceability in Enterprise Architect thereby documenting the lineage of the requirement to its solutions.

We encourage you to register for the webinar using the link below:

https://sparxsystems.com/resources/webinar/businessanalysis/requirementsmanagement/index.html 

Requirements in Context

Thursday, September 13th, 2018 at 10:00 AM Pacific (1:00 PM Eastern)

Register: https://www.modernanalyst.com/Webinars/tabid/207/ID/5074/Requirements-in-Context.aspx

Scott Ambler, a key founder of the Agile movement accurately stated:
"If a requirement was misunderstood, all modeling decisions based on that requirement are invalid,

the code written is also in question, and the testing efforts are now verifying the application under the wrong conditions".

Topics covered include:

• Requirements across the entire landscape
• The semantics of Requirements
• Reuse Requirements
• Requirements traceability
• Requirements Management tools

Featured Speaker: Ramsay Millar, Business Architect

Updated 9th June, 2016: Covering all new features available in Enterprise Architect 12.1

Enterprise Architect integrates Requirements Management with other software development disciplines, by creating requirements directly in the model. Requirements Management is built into the core product, solving many of the issues of traceability, interdisciplinary team divisions, integration with change and configuration management systems.  Read the following whitepaper for more information:

As practicing Enterprise Architect consultants, we have the opportunity to interact with various corporates for training, consulting and providing Enterprise Architect demonstrations. We encounter the following standard queries:

“We have lots of Requirements and Use Cases in Microsoft Word ™ documents. Can we import them into Enterprise Architect “?

“Can our Business Analysts continue to work in Microsoft Word™ which they are familiar with and then have the artifacts imported into EA?

These queries highlighted the need for a standard Word importer that helps the Enterprise Architect users to

Import the existing Requirements and Use Case Models in Microsoft Word ™ format into Enterprise Architect as elements.

Enable the Business Analysts to work with the Microsoft Word Documents™ and still leverage the power of Enterprise Architect for Traceability, Impact analysis, Version control and much more……

EAWI (Enterprise Architect Word Importer) is here to address the above challenges.

*EA Word Importer lets you import your requirements, Use Cases and other information from your Word documents into Enterprise Architect as model elements.*

      What do we solve?

How does it work?

Check out the listing on the Sparx Systems website:
 
http://www.sparxsystems.com/products/3rdparty.html#WordImporter

or Visit:

www.eamwordimporter.com

Imagine that a group of people are putting together a jigsaw puzzle whose pieces continually change shape as do the spaces that they must eventually fill. Each group has responsibilities to the completion of the overall puzzle but more importantly must develop their own respective piece of this puzzle and ensure that ultimately, that piece seamlessly complements those shared boundaries created by the relationships of others. This scenario of mutual dependencies and volatility could be analogous of any organisation in the current hyper-competitive business environment.

Of course each team can communicate with others throughout the project, but without a fully shared vision, collaboration will be sub-optimal. Ideas and innovations will remain siloed within each group and should the puzzle ever be completed on time and to budget, it will have many disconnects, repetitions, gaps, and missing pieces. Some groups will produce excellence, but no group can fully share its value with the others.

Ultimately, someone must have overall responsibility for coordination of the effort and more importantly management of inherent risk, resources and timelines, all of which demands access to technology solutions. Each piece, complementary space and multi-shared relationship in the puzzle requires collaboration between many different stakeholders.

The plan and co-ordinated approach shared by each team responsible for each piece must be captured at the beginning and the ability to communicate and share progress at the individual, team and organisational level must be made transparent, simplified, and accessible to everyone.

The responsibility for Enterprise Architecture falls to the Chief Enterprise Architect. However, the creation of the architecture is a shared task. Stakeholder equity of access to enabling technology is imperative - and it must be affordable. Every role, including managers, analysts, systems architects, and engineers must have sufficient understanding of the strategy detail, allowing them to make informed decisions and to execute the plan that leads to realization of the shared vision.

Enterprise Architect provides the ultimate collaboration solution, transparently interlinking all of the individuals and groups in a shared vision, while enabling an inclusive and contextual decision history across the local and global locality of the project teams. Enterprise Architect is an enterprise requirements definition and management platform, with full support for collaboration including authoring, validating, and managing requirements, and communicating those requirements to the broader team through seamless integration.At any future time, and as the delivered solution evolves to meet changing business objectives, the thread of those original decisions can be continually reviewed, tracked and monitored to ensure complete traceability.

For more information on requirements management in Enterprise Architect, please visit: http://www.sparxsystems.com/resources/demos/requirements-management.html

To learn more about tools for traceability in Enterprise Architect, please refer to the following webinar:

http://www.sparxsystems.com/resources/demos/traceabilitytools/webinar-tools-for-traceability.html

This article (which actually represents the third incarnation of the ICONIX Business Modeling Roadmap), leverages two new capabilities from Sparx Systems, now available in Enterprise Architect. These are the Structured Scenario Editor and the Business Rule Composer. The article describes how these two quantum leaps in technology combine synergistically to enable a new process by combining business process modeling with behavioral code generation for business rules.