Advanced Field Artillery Tactical Data System (AFATDS): - SSTC
Advanced Field Artillery Tactical Data System (AFATDS): - SSTC
Advanced Field Artillery Tactical Data System (AFATDS): - SSTC
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Advanced</strong> <strong>Field</strong> <strong>Artillery</strong> <strong>Tactical</strong><br />
<strong>Data</strong> <strong>System</strong> (<strong>AFATDS</strong>):<br />
A Government-Industry<br />
Team Success Story<br />
Cynthia Inteso<br />
PMO Intelligence and Effects<br />
April 21, 2004
What is <strong>AFATDS</strong>?<br />
<strong>AFATDS</strong> is a fully automated Command & Control (C2) system used<br />
by the Joints services (USA, USMC, USN) to prioritize targets and<br />
pair them with optimal Fire Support weapon systems. It gives<br />
commanders timely, accurate, coordinated fire support to prosecute<br />
high-value targets.<br />
<strong>AFATDS</strong> puts the right weapon on the right target, at the right time<br />
Cynthia Inteso - 1
Success: A Team<br />
Effort<br />
<strong>AFATDS</strong> success is as much about<br />
professionalism, expertise, discipline, and<br />
teamwork as it is about advanced processes<br />
and application of emerging technology.<br />
This is not a story of some gee-wiz silver bullet.<br />
Cynthia Inteso - 2
Alpha Contracting<br />
Partnership<br />
Quality<br />
Continuous Testing<br />
Tech Reviews Metrics<br />
Prototyping Technology<br />
User PM Contractor<br />
Success:<br />
A Team Effort<br />
<strong>AFATDS</strong><br />
SUCCESS<br />
Tailored Spiral Development Process<br />
Omnipresent<br />
Performance<br />
& Reliability<br />
Visibility /<br />
Measurement<br />
User buy-in /<br />
Optimized Benefits<br />
Managed Risk<br />
Right Sizing<br />
Trust<br />
Competence<br />
Cynthia Inteso - 3
Government-Contractor<br />
Partnership<br />
• Encourage communication, trust, and<br />
cooperation.<br />
• Discourage traditional adversarial mindset.<br />
• Maintain continual dialog.<br />
• Empower peer-to-peer interactions at all levels<br />
across all system disciplines.<br />
• Effective teamwork necessitates mutual<br />
respect.<br />
• Encourage innovation & creative approaches to<br />
traditional problems within a context of sound<br />
system and software engineering principles.<br />
Cynthia Inteso - 4
The Contractor –<br />
Raytheon, Ft Wayne, IN<br />
Raytheon is a Six Sigma company: Employment of the six principles<br />
(visualize, commit, prioritize, characterize, improve, and achieve)<br />
assists in a continuous process improvement cycle over the past 4<br />
years.<br />
• Management is responsive, cooperative, open, constructive, and<br />
innovative.<br />
• Software engineering staff is highly-qualified, motivated, open, and<br />
professional.<br />
• Engineering staff has unparalleled knowledge in Army Fire Support<br />
automation.<br />
• Contractor Performance Assessment Report (CPAR): Current CPAR<br />
rating from the government shows Exceptional in all categories of<br />
Technical, Schedule, Cost Control, and Management.<br />
• Award Fee is used as incentive and is based on performance<br />
assessment<br />
• Bottom Line priority: Teamwork between contractor and customer.<br />
Cynthia Inteso - 5
Customer<br />
Requirements<br />
Contractor<br />
TSM FATDS<br />
USMC<br />
ECP Ready for<br />
contractual<br />
action<br />
ALPHA CONTRACTING<br />
PM<br />
Requirements IPT<br />
Meetings -<br />
Other Agencies<br />
Government-<br />
Contractor<br />
Sizing<br />
Agreement<br />
Initial<br />
Requirements<br />
Alpha Contracting<br />
Process<br />
Contractor<br />
Develops<br />
Requirements<br />
Government<br />
Evaluation<br />
Working Draft<br />
Requirements<br />
IPT Meetings<br />
Contractor<br />
Estimates Software<br />
Sizing using<br />
SEER-SEM<br />
Tech<br />
Agreement<br />
Use Case &<br />
Function Point<br />
Analysis via IPT<br />
Cynthia Inteso - 6
Alpha Contracting<br />
Alpha Contracting, which has been used on the <strong>AFATDS</strong><br />
program for many years, is an Integrated Product Team<br />
(IPT) concept that joins the user, contractor, government<br />
program office and contracts personnel into a cohesive<br />
team to:<br />
• Eliminate lengthy proposal preparation<br />
• Provide concurrent technical definition and discussions<br />
• Highlight unnecessary or potentially unaffordable requirements<br />
• Promote alternative thinking and solutions<br />
• Provide coordinated and focused fact finding<br />
• Foster cooperative spirit<br />
• Provide more expeditious agreements on methodologies and<br />
estimating techniques for both technical and pricing venues<br />
• Bottom-Line Objective has been achieved: Right sizing that<br />
provides well-understood functional requirements coupled with<br />
realistic budget for effort and schedule.<br />
Cynthia Inteso - 7
Modified Spiral<br />
Development Process<br />
<strong>AFATDS</strong> software utilizes spiral development<br />
techniques for rapid turnaround deliveries (including<br />
Service Packs) of new features within 2.3 million lines<br />
of code in Ada, JAVA, C++, XML. The process:<br />
• Is responsive to requirements for early incremental capabilities to<br />
support parallel development of other Army systems.<br />
• Manages integration risk effectively, spreading integration into<br />
bite-sized pieces.<br />
• Optimizes staffing profile by spreading all development phases<br />
over time; minor fluctuation in personnel loading allows retention<br />
of expert team from one version to the next.<br />
• Includes Incremental Technical Documentation:<br />
Early incremental description of developmental products<br />
provided to customer and stakeholders<br />
Contractor format, replaces delivery of full development<br />
documentation.<br />
Cynthia Inteso - 8
HCI Prototyping<br />
Human Computer Interface Windows prototyping<br />
IPT effort provides:<br />
• Early insight into how the requirements are going to<br />
be implemented with time to react to directed<br />
changes<br />
• Early proof of concept of the requirements<br />
• Early User buy-in on HCI and associated capabilities<br />
• Streamlined execution of the follow-on phases –<br />
cost reduction<br />
• Reduction in requirements creep – control risk to<br />
schedule & cost<br />
Cynthia Inteso - 9
Technology<br />
<strong>AFATDS</strong> remains “state-of-the-art” -- Continuously evolving<br />
and incorporating emerging technology since its introduction<br />
7 years ago, thus expanding the <strong>AFATDS</strong> capabilities for the<br />
warfighter<br />
• Software designed to facilitate portability and insertion of newer hardware<br />
technology.<br />
• Computing hardware has become smaller, lighter, and higher performance at<br />
relatively low cost for software & integration.<br />
• Software reuse is practiced incorporating DoD-wide Common Operating<br />
Environment and Army Foundation products. In addition, commercial<br />
software products, such as C/JMTK are being used.<br />
• <strong>AFATDS</strong> has embraced client / server technology and has developed and<br />
fielded the Effects Management Tool as an <strong>AFATDS</strong> client.<br />
• Contractor developed automated code generation tools that provide better<br />
quality and cost controls by eliminating human error.<br />
• JAVA used instead of Ada for user interface software.<br />
• DBMS migrated from legacy product to Oracle.<br />
Cynthia Inteso - 10
Technical<br />
Reviews<br />
Technical Reviews are focused on the working<br />
level:<br />
• Used in place of traditional, expensive Mil-Std 1521<br />
design reviews where substance is often displaced by<br />
form<br />
• Meeting presentations cover both technical and<br />
programmatic aspects including overriding requirements,<br />
design, and test issues<br />
• Sidebar working sessions enable small groups of<br />
stakeholders and experts to focus on specific issues<br />
• Results in real solutions on the spot and minimizes the<br />
need for follow-on actions that can cause delays<br />
Cynthia Inteso - 11
Metrics<br />
Program success is aided by metrics activity vigorously<br />
supported by the Government and contractor:<br />
• Metrics tracked weekly: defect density, requirements<br />
integrated, fault correction progress, software changes<br />
initiated vs retested successfully, and tasks starts and<br />
completions.<br />
• Metrics IPT meets weekly to review status on collected<br />
metrics – government and industry team.<br />
• Metrics are tailored to meet the developmental paradigm<br />
(i.e., modified spiral) and current program phase – metrics<br />
are eliminated that no longer apply.<br />
• Early identification of weak areas that are detected through<br />
the use of the metrics reports aid in indicating current<br />
program process and identifying potential future issues.<br />
Cynthia Inteso - 12
Continuous Testing<br />
Testing begins with the first incremental software engineering<br />
release and continues until product release:<br />
• Off-site test events are scheduled as early as possible to<br />
address interfaces with other systems and interoperability.<br />
• Separate software and system test labs are used for<br />
integration and testing.<br />
• Simulators are used to allow testing with realistic interfaces to<br />
simulate actual usage.<br />
• Final integration & test includes both internal contractor-level<br />
checkout and Government oversight.<br />
• Independent Verification & Validation testing performed on all<br />
incremental releases.<br />
• <strong>Field</strong> testing and live fire demonstrations are conducted when<br />
requirements dictate.<br />
• Cooperative working relationships with Army test community<br />
have facilitated practical resolution of issues.<br />
Cynthia Inteso - 13
Quality Process<br />
Quality is critical since <strong>AFATDS</strong> is used during live-fire<br />
exercises as well as in war where personnel safety is<br />
essential.<br />
• Use of Apex and Encompass tools within an extensive configuration<br />
control system aids engineers in the development process<br />
• DOORS database used to track system (SSS) and software (SRS)<br />
requirements producing bi-directional traceability between documents<br />
and test cases – provided to PM IE for evaluation and validation of<br />
requirements<br />
• Engineering Change Requests (ECRs) used to control changes to<br />
system requirements; Change Orders (COs) provide authorization for<br />
working controlled software changes<br />
• Procedures audited by Product Quality Assurance to assure procedure<br />
adherence<br />
Cynthia Inteso - 14
Keys to Success<br />
• The program’s success is derived from a highly collaborative government and<br />
industry team.<br />
• Alpha Contracting process for developing program requirements<br />
- Government-Industry team including Raytheon, User, PM Intelligence and Effects<br />
• Requirements Definition and <strong>System</strong> Design phases<br />
- Early Windows prototype development<br />
- Government-Industry team reviews<br />
• Periodic Technical Reviews with all stakeholders - extremely beneficial<br />
• Raytheon has developed a comprehensive set of software engineering process<br />
requirements and guidance material to direct software development and to<br />
ensure high-quality software products.<br />
• <strong>AFATDS</strong> is a model acquisition program — within schedule and cost parameters,<br />
exceeding performance metrics, and which played a significant role in winning<br />
the ground war in Iraq.<br />
Cynthia Inteso - 15
<strong>AFATDS</strong> – <strong>Advanced</strong> <strong>Field</strong> <strong>Artillery</strong> <strong>Tactical</strong> <strong>Data</strong> <strong>System</strong><br />
C2 – Command and Control<br />
C/JMTK – Commercial / Joint Mapping Tool Kit<br />
CO – Change Order<br />
CPAR – Contractor Performance Assessment Report<br />
DBMS – <strong>Data</strong>base management system<br />
DoD – Department of Defense<br />
ECR – Engineering Change Request<br />
HCI – Human Computer Interface<br />
IPT – Integrated Product Team<br />
Mil-Std – Military Standard<br />
PM IE – Program Manager Intelligence and Effects<br />
RDD – Requirements Definition Document<br />
SISTIM – Simulation/Stimulation<br />
SRS – Software Requirements Specification<br />
SSS – <strong>System</strong>s/Software Specification<br />
TSM – TRADOC <strong>System</strong> Manager<br />
USMC – United States Marine Corps<br />
XML – eXtensible Markup Language<br />
Acronyms<br />
Cynthia Inteso - 16