The role of schedule is fundamental to the acquisition of a particular system. This topic is of even more importance to acquisition in a system-of-systems environment. This report examines the issue of schedule considerations for interoperable acquisition. First, a Gedanken red team project is used to explore concerns about schedule in interoperable acquisition. Then, those concerns are examined in light of current requirements regarding schedule. From that examination, several research questions are proposed.
Technical Note
CMU/SEI-2006-TN-035
November 2006
SEI:
Meyers, B.; & Sledge, Carol. Schedule Considerations for Interoperable Acquisition (CMU/SEI-2006-TN-035). Software Engineering Institute, Carnegie Mellon University, 2006. http://www.sei.cmu.edu/library/abstracts/reports/06tn035.cfm
IEEE:
B. Meyers, and C. Sledge, "Schedule Considerations for Interoperable Acquisition," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Note CMU/SEI-2006-TN-035, 2006. http://www.sei.cmu.edu/library/abstracts/reports/06tn035.cfm
APA:
Meyers, B., & Sledge, C. (2006). Schedule Considerations for Interoperable Acquisition (CMU/SEI-2006-TN-035). Retrieved June 19, 2013, from the Software Engineering Institute, Carnegie Mellon University website: http://www.sei.cmu.edu/library/abstracts/reports/06tn035.cfm
CHI:
Meyers, B., and Carol Sledge. Schedule Considerations for Interoperable Acquisition (CMU/SEI-2006-TN-035). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2006. http://www.sei.cmu.edu/library/abstracts/reports/06tn035.cfm
MLA:
Meyers, B., & Sledge, C. 2006. Schedule Considerations for Interoperable Acquisition (Technical Report CMU/SEI-2006-TN-035). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://www.sei.cmu.edu/library/abstracts/reports/06tn035.cfm
For more information