This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Practitioner's Cycles, Part 3: Implementation Opportunities
September/October 2010 (vol. 25 no. 5)
pp. 77-81
Steven V. Deal, Deal Corporation

The Practitioner's Cycle approach has developers begin system design and development with cognitive task analysis to understand the current work and then continue investigating the envisioned world as new technologies and work methods are created and tested. In the real world, the Practitioner's Cycles concept can serve as a solution to the simultaneous problems of maturing new technologies and rapidly transitioning those technologies into new products.

1. S. Deal and R.R. Hoffman, "The Practitioner's Cycles, Part 1: The Actual World Problem," IEEE Intelligent Systems, vol. 25, no. 2, 2010, pp. 4–9.
2. R.R. Hoffman et al., "The Practitioner's Cycles, Part 2: Solving Envisioned World Problems," IEEE Intelligent Systems, vol. 25, no. 3, 2010, pp. 6–11.
3. T. Hatton, Small Business Management, Entrepreneurship and Beyond, Houghton Mifflin, 2003.
4. D.K. Sobek II, A.C. Ward, and J.K. Liker, "Toyota's Principles of Set-Based Concurrent Engineering," Sloan Management Rev., vol. 40, no. 2, 1999, pp. 67–83.
5. "Integrated Modular Avionics (IMA) Development Guidance and Certification Considerations," RTCA DO-297, RTCA Inc., 2005.
6. S. Welby, "DoD Systems Engineering Update," presentation at the Nat'l Defense Industrial Assoc. Systems Eng. Division Meeting, June 2010; www.ndia.org/Divisions/Divisions/SystemsEngineering Pages.
7. D. Honey, "Address from the Research Office of the Director, Defense Research and Engineering, United States Air Force," presentation at the Wright Dialogue with Industry, Dayton Area Defense Contract Assoc., June 2010.
8. A. Vu, "Small Business Innovation Research/Small Business Technology Transfer Program," presentation at the Wright Dialogue with Industry, Dayton Area Defense Contract Assoc., June 2010.
9. J. Cleveland, "Toyota's Other System—This One for Product Development," Automotive Design and Production, Feb. 2006, pp. 18–22.
10. US Dept. of Defense, "Acquisition Documentation Streamlining Task Force," memorandum from principal deputy under secretary, Acquisition Technology and Logistics, 2010.
11. Acquisition Community Connection, "What Exactly Is 'Rapid Acquisition Authority'?" Defense Acquisition Univ., 2010; https://acc.dau.milCommunityBrowser.aspx?id=22114.

Index Terms:
Software engineering, requirements engineering, rapid prototyping, DoD, Toyota, practitioner's cycle approach
Citation:
Steven V. Deal, Robert R. Hoffman, "The Practitioner's Cycles, Part 3: Implementation Opportunities," IEEE Intelligent Systems, vol. 25, no. 5, pp. 77-81, Sept.-Oct. 2010, doi:10.1109/MIS.2010.129
Usage of this product signifies your acceptance of the Terms of Use.