![]() The above ‘repeat on each relevant page’ approach may prove useful in situations where the generated specification does not include the whole system context and therefore it may not make sense to list them out separately Notes – adding extra detail to your specifications … and ‘Ticking’ the box displays the master as it appears within the page as if it was a normal widget on the page. Un-ticking the ‘Document Masters in Page Sections’ box displays a nice section at the bottom with all of your masters like the above. So that translates to the following rendering in the specification. The last option allows you to generate the master in each page that it appears, rather than the standard approach of generate once and reference it when it is used elsewhere. This could be useful if you are using a master in a different, possibly more dynamic way, than standard masters and wanted to differentiate it from the other masters in the list. Some masters can be set to behave like custom widgets and this allows them to removed from the master list if necessary. ‘The ‘Do Not Generate Masters Set as Custom Widgets’ does exactly that, funnily enough. If ‘All Pages’ is set on that tab by definition all masters will also all be displayed. ‘Only Generate Masters Used on Generated Pages’ only includes masters that are are used in the selected pages from the ‘Pages’ tab. The first option – ‘Only List Generated Masters’ is useful if there are masters in the project that are not being generated because of one of the other options in this screen (explained below, but useful for the iterative / modular spec approach). The interesting set (the other options are essentially the same as document above for ‘Pages’) are around which masters to generate and whether to generate them once or as they used per page. In your specification, you have the option to print out all or a select few masters as you did with pages, change section and heading titles. It’s a concept that is used in traditional manual specifications but is harder to manage – primarily because it relies on manual processes to apply changes to the relevant areas. ![]() Make a change for one master and its applied across them all. Masters in Axure are used to define common elements that appear across the system and allow a centralised governance. When generated in the specification, the following section of the spec is effected by the ‘Pages’ configuration options. This way you can flesh out the annotations / notes for the relevant pages and leave out those that are not finished. This is particularly useful when developing in an iterative approach where the specification is built a functional area or module at a time. Then the next section allows you to select what pages will be included in the generated spec. Starting with the first options, there is an option to include the pages section and give it a title and directly beneath that an option to specify whether to include a sitemap and change it’s title. So the first tab, ‘Pages’ allows you to select which of the pages within your project you wish to include in the generated specification. Pages – a blessing for BA’s working within an iterative project I want to explore the available options on each tab of the configuration window and show the effect each has on the generated spec. Lets assume you already have a project to work from that will generate a useful specification and press ‘F6’ or the ‘Generate Specification’ on the toolbar. This really only touched on one tab of the specification generation configuration and the idea of this post is to go over the remaining options and explore their usage. ![]() In the first part of this post, I went through the process of creating and refining a word template to suit a generated Axure specification. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |