|
Main |
|
Client list |
|
Usability Samples |
|
About |
|
Contact Info |
Usability Samples
|

Before:
|
After:
|
Result:
|
|
The new slide is clearer, simpler, and easier to brief and to learn. |
|
Example 1: Briefing Materials |


|
The checklists were developed based on experience gained through the development of several specific federation applications. To this extent, the checklists represent accumulated experience from several case studies. Each experience was unique in that it involved different application domains, different goals, different federates, and different participants. In general the items in the checklists are applicable to all federation efforts, it is however, expected that some amount of tailoring is required to meet specific federation constraints and objectives. Indeed, the checklists may not be complete, additional items may be needed. |
|
The checklists are based on case studies of federation applications. The case studies covered a wide variety of domains, goals, federates, and participants. In general, the items in the checklists apply to all federation efforts. However, the checklists may require some tailoring, or even new items, for specific federations. |
|
The checklists are organized along the seven steps of the IEEE FEDEP model (Annex A). The checklist for each FEDEP step begins with the definition of that step and includes the likely participants in the activities. Checklist items represent management and technical decisions and tasks that are acted upon by members of the federation team. Both the managerial and technical checklists may be composed of subcategories of related activities. The placement of these groupings within the checklist may indicate sequential activities, but more often represent activities being accomplished in parallel or perhaps in a repeated or cyclic manner, as the teams understanding of the problem space is refined. Managerial activities for each step are in a grouping separate from the technical activities, Program Management, to aid management and technical team members in focusing on activities relevant to their responsibilities. Within each FEDEP step, checklist items that generally apply to all federations are listed. Following the general checklist items are additional sets of items that are more closely aligned with a specific application area. These application areas are those in the case studies mentioned above: Experimentation and Analysis, Training, and Test and Evaluation. The reader is encouraged to consider the checklist items as a touchstone and to tailor the items (add, modify, substitute, or ignore) as appropriate for the individual circumstances of the federation development project. The checklists are intended as an additional input to the systems engineering process. To further encourage the tailoring of the checklists, two columns follow the checklists. The columns are labeled "A" for applicable, and "C" for completed. |
|
The checklists are designed to be tailored to support the engineering process. Items can be added or removed as applicable. The checklist items are presented in a sequential list but the activities may be completed in any order. For example, activities may be completed in parallel or they may be repeated over several iterations. The checklists include both technical and management tasks. Each task list may be composed of subcategories of related activities. The checklists are organized along the 7 steps of the IEEE FEDEP model (Annex A). The checklists for each step have three main elements as follows: Introduction Name of the step Definition of the step Participants in the activities Checklist Category Types General (Items that apply to all federations) Program Management Specific Applications Experimentation and Analysis Training Test and Evaluation Columns A and C (Tailoring aids) Column A: Applicability Column B: Completeness |
Before:
|
After:
|
Before:
|
After:
|
|
The new paragraph has the following features: Shorter Logically arranged Simpler language Clearer Covers all of the salient points |
Result:
|
Result:
|
|
The revised version has the following features: No longer a large block of text Points can be seen easily The text can be easily scanned Bullet format Simple sentences Organized into categories and sub-categories No loss of information |
|
Example 3: Writing a Manual |
|
Example 4: Writing a Manual |

Before:
|
After:
|
|
Key benefits Excess information removed The essential information is understandable at a glance The amount of time to train the users was reduced Play of the game improved |
Result:
|
|
Example 2: “ The Right Stuff ” |

|
E-mail Us |