Enterprise Architect has a range of tools that can assist with planning, scheduling and conducting workshops. Depending how formal a workshop is, a plan might be required and an Agenda and Minutes might also be necessary. This can be achieved using a Document Artifact. A Calendar could be used to record the date, time and location of the meeting. Model mail could be used to invite people to the workshop and to let them know when the minutes have been completed. Links to important information in the model can also be added to a mail message. During the workshop Mind Maps could be drawn and Element Discussions posted, new concepts or Glossary terms recorded and Slide Shows presented.
Mind Mapping Diagram
A Mind Mapping diagram can be used to record the stakeholder's statements during an elicitation workshop. The statements are not categorized but simply recorded, and later during the analysis phase of Requirements development they can be converted to the appropriate elements or retained and the Requirements can be traced back to the topics, effectively creating a record of how the Requirement was derived. This is a powerful technique that shields the stakeholders from needing to know the modeling languages, and it allows them to concentrate on articulating their needs; it also frees the analyst up from concerns about which element to use to model the statements. The derivation of requirements from Mind Mapping topics is usually performed in the analysis phase of the Requirement's Development process.
Learn More: Mind Mapping Diagram
The Collaborate window is a convenient facility that allows commentary to be made on elements without contaminating the notes with discussions that ultimately don't contribute to the integrity of the model. Modelers often place notes on diagrams or write questions in the element notes fields and these are distracting and must be removed when formal documentation is generated from the model. The Collaborate window allows a modeler to initiate a discussion and others to reply. It is a perfect way for discussing requirements.
A Discussions summary window conveniently displays the Discussions for all elements in the repository.
Learn More: Informal Discussions
A Business Analyst will typically plan a workshop and define the approach, and if it is a structured interview a list of questions will be defined in advance of the workshop. A Document Artifact can be used as a place to store this information directly inside the model. A template could be specified for the document and the answers to structured or unstructured question recorded into the Document. Other model elements that exemplify some aspect of the workshop, such as topics of discussion, can be dragged into the document as links.
Learn More: Document Artifact
Model Views provide alternate views of the elements and diagrams stored in the Browser window. The Slide show is particularly useful for presenting a series of diagrams during a workshop and solves the problem of needing to remember the location of the diagrams in the Browser window. Any number of slide shows can be created and diagrams can be added regardless of their type or location in the Browser window. The progression from slide to slide can be automated or triggered manually.
Learn More: Model Views
A Concept Model will act as a guiding model for discussions with many stakeholders; ideally a skeleton model should be created prior to the commencement of any workshop. The Concept Model should be kept simple; domain elements should be given a name and a description or a responsibility, and initially only important connections should be made between elements. As the workshop progresses new elements will be uncovered that can be added directly to the model, giving the stakeholders confidence that their needs and concerns are being addressed and managed well. Enterprise Architect allows domain models to be created using the UML Class diagram.
Learn More: Class Diagram
Prior to a workshop, an analyst can populate the Project Glossary with the existing terms and their meanings that have been gleaned from reading project documentation such as a Business Case or Vision Document. During the workshops, as new terms are uncovered they can be added to the Glossary and their definitions can be discussed and entered or deferred until later in the analysis phase.
Learn More: Glossary
The Calendar provides a way to record and present important temporal information, such as events and meetings, in calendar format. Workshops can be entered into the Calendar and set up as recurring if needed. Event subtypes can be configured to add 'Workshop' as a Meeting Type.
Learn More: Calendar
Model Mail can be used to notify and remind people of a workshop and to inform them after the workshop about outcomes, decisions and required actions. Links to model elements, diagrams, Matrices, Team Library and a variety of other items can be added.
Learn More: Model Mail