by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
FCW : July 15, 2014
ter schedule as a necessary ingredient to program success. One important but too often over- looked aspect of prototyping is per- formance load testing. Checking how a system performs under anticipated loads early in the program s develop- ment can save a lot of rework later. If subsystems can be bought or repurposed from other systems that meet requirements, the government ought to do so. Buying rather than building lowers risk substantially. Agencies should use off-the-shelf software components when appro- priate, whether they are offered by traditional software vendors or based on open-source technology. And from a design perspective, the program ought to look at the appropri- ate leverage and use of application pro- gramming interfaces to simplify integra- tion. One of the burgeoning commercial trends is much greater use of APIs to rapidly develop and eld functionality. Finally, program leaders should strive for overall simplicity in the tech- nical architecture. Integrating dozens of off-the-shelf components creates its own set of technical complexities. Simplicity is essential because prob- lems with a technical architecture tend to show up late in the develop- ment life cycle, often during integra- tion and end-to-end testing, and they typically result in performance and scalability problems. Having to recast even small parts of a technical architecture late in the development cycle is very costly and time-consuming and can even doom a program. ■ July 15, 2014 FCW.COM 31 FCW Has Gone Mobile. Go to fcw.com/tablet to download the tablet app today! Your mobile fcw.com experience --- optimized. sit fcw.com from your smartphone and enjoy the easier avigation and new sharing options Y e Vi na There should be an effort to simplify the business processes...and determine the minimum required capabilities for an initial system launch.
June 15, 2014
July 30, 2014