1. Team Members: William Busby, Lindsey Gray, & David Meffe
Sponsor: Lockheed Martin Reconnaissance Systems
Bill Rawlings and Marvin Kleine

2. Basic Definitions/Concepts
SAR – Synthetic Aperture Radar
Metadata – Data describing the SAR image
Information is gathered by an airplane flying over an area and taking a series of measurements/readings
HTML – Hyper-Text Markup Language
A predefined set of tags understood by a web browser for the formatted display of information
XML – Extensible Markup Language
Custom defined tags to encapsulate information
XSL - Extensible Stylesheet Language
Used to define formatting of XML tags
Relational Database – Collection of data items organized as a set of formally described tables
Lindsey Gray

3. Brief Background
LMCO is a premier producer of Intelligence, Surveillance, and Reconnaissance (ISR) systems
Used by U.S. and allies for:
Fixed Target Imaging (FTI)
Moving Target Indications (MTI)
Automatic Target Recognition (ATR)
Battle Damage Assessment (BDA)
Lindsey Gray

4. Business Issues Need for web-based access and analysis of SAR metadata
Facilitate information dissemination
Need for improved data storage/retrieval
Current method
inadequate to support web-based access and analysis
platform dependant
New Method
Relational Database
Platform Independence
Lindsey Gray

6. Project Description
Provide web-based access to synthetic aperture radar (SAR) metadata
Storage and retrieval of SAR metadata in a relational database
Insert SAR metadata into database(s) using parsing routines
Use extensible markup language(XML) tags to describe the metadata
Query database(s) for SAR metadata
Must be user-friendly and extensible
David Meffe

7. Design Method Incremental approach Problem Statement
Process loops back to the requirements in the architectural, design, implementation and testing stages
Ensures the requirements are a part of each step in the procedure
Problem Statement
Requirements
Architecture
Design
Implementation
Testing
David Meffe

8. Design Approach Incremental approach has worked out well
Developed project in stages
Modular, self contained pieces
Parsing/Insertion module is stand-alone
Allowed for errors to be detected early on
David Meffe

9. Client/Server Architecture
Includes several clients, a web server and database server
Clients request info from the web server, which queries the DB
Result set is sent back to web server and XML/HTML is generated for clients
David Meffe

10. Architecture Lessons Learned
Client/Server was relatively simple to understand and implement
Dynamically Transforming result set information into XML document required research
Each component was built as stand alone modules and integrated later
Modularity allowed for rapid development
David Meffe

11. Implementation Transition from design to implementation was rough
Many hurdles to overcome
Spent too much time trouble shooting
Lacked understanding and detailed requirements
William Busby

12. Implementation: Lessons Learned
Expect problems when using new technologies
Build-in more research and learning time
More time spent on requirements & design translates into fewer problems & decisions to make during implementation
Have at least 2 team members working on new technology issues
William Busby

13. Testing Lessons Learned Overview Bottom-up approach
Tested functionality as it was added
Thorough testing done at unit level
Little testing after integration due to time constraints
Lessons Learned
Test early and test often
Identify problem areas as soon as possible
William Busby

14. Scheduling Original estimates were low & optimistic
Schedule created before allocating resources
Overconfidence in project
Filtering information is time intensive
William Busby

15. Scheduling: Lessons Learned
Allocate people to tasks as early as possible
Setup tasks for hidden cost items
Research
Learning
If scheduled cannot be maintained, readjust
No carrot, no stick…
no motivation to stay on schedule
William Busby

16. Other Issue Areas Small team problems
There were communication problems early on, but those were resolved and ultimately not a problem
Changes were made during integration to improve efficiency
Better code reviews would have identified these earlier
Needed a better understanding of information in the SAR domain
Lindsey Gray

17. Lessons Learned
Initiate and maintain good communication with sponsor and within team early on
Thorough code reviews and testing are important
Well defined requirements lend themselves to a well designed problem & solution
Ask Questions!!!
Lindsey Gray

18. Summary Valuable learning experience
Real Project
Interaction with sponsor
Complete Project: beginning through end
Insight into estimating and scheduling issues
Improved teaming skills
Lindsey Gray

19. ANY QUESTIONS ?