Download User's Manual
Transcript
User’s Guide add4Q 7 Working with single plug-ins In the following chapter, a possible approach to project work with the add4Q Toolkit is described by way of examples. add4Q does not force you to do things in a certain order or work in rigid sequences. However, it clearly shows you at any time what remains to be done. You are free to do it according to your "bestpractice" experience, the V model approach or with methods of agile development. 7.1 Document processing (add4Q||editor) The central application from which everything proceeds and where in the end everything reconvenes, is the add4Q||editor. 7.1.1 Representation of documents in the EA repository The add4Q plug-ins manage documents in the repository under a fixed structure and with defined EA artifacts. Document root: A package that can be stored anywhere in the repository. This package contains a number of "tagged values" with document properties such as author, version etc. of the document. Document content: Subchapter: Packages that are arranged hierarchically under the root package, containing notes as well as linked documents. Requirements: EA requirement objects with notes and linked documents. Diagrams: EA diagram objects which are displayed in the add4Q||editor but cannot be edited. Document artifacts: EA document artifacts that can be created under packages. additional Objects: Change, Class, Feature, Issue, Task, Test case Note: contrary to normal text, artifacts can be linked, for example, with requirements or realizing classes. Note: in order to ensure consistent object sorting between the EA project browser and add4Q, "Allow Free Sort" should be enabled in the EA options dialog ([Tools / Options / General]). 7.1.2 add4Q||editor window structure To start editing documents, select the EA menu item [Extensions/add4Q/editor]. Page 20 of 42