Lockheed Martin Aeronautics Company Candidate Collaborative Projects for Net-Centric Application Michael F. Siok, PE Lockheed Martin Aeronautics Company.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University 1 Pittsburgh, PA Dennis Smith, David Carney and Ed Morris DEAS.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Review Questions List and describe the purpose of the four phases of Systems Analysis. The preliminary investigation phase quickly determines whether or.
Overview of Software Requirements
Iterative development and The Unified process
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Introduction to Systems Analysis and Design
Project phases and the life cycle
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 1.1.
What is Business Analysis Planning & Monitoring?
Chapter : Software Process
DPW BD&C Employee Performance Evaluation Guideline Discussion
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
A Methodology that is PROVEN PRACTICAL EFFECTIVELY INTEGRATED SCALABLE CUSTOMIZABLE.
Writing a Software Project Proposal
Module 3: Business Information Systems Chapter 11: Knowledge Management.
S/W Project Management
PO Box 1508, Vancouver, WA (360) THE COMMERCIAL & INDUSTRIAL BILLING SOLUTION.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Collaborative Work Package Criteria Suitable for accomplishing in a period of 90 days to 1 year. Work should fall within the expertise of one or more consortium.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Software Engineering Management Lecture 1 The Software Process.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Lockheed Martin Aeronautics Company Copyright ©2007 Lockheed Martin Corporation. All Rights Reserved. Empirical Study of Software Quality and Reliability.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Handbook for Developing a Transportation Management Center Operations Manual Sponsored by the TMC Pooled-Fund Study Single.
CLIC Implementation Studies Ph. Lebrun & J. Osborne CERN CLIC Collaboration Meeting addressing the Work Packages CERN, 3-4 November 2011.
MTBC Cloud Computing Initiative  Applications of cloud computing  Overview of the NSF Net-Centric Software and Systems (NCSS) I/UCRC  MTBC and NCSS.
Systems Analysis and Design in a Changing World, Fourth Edition
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Request for Proposal (RFP)
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Requirement Engineering
1 The ILC Control Work Packages. ILC Control System Work Packages GDE Oct Who We Are Collaboration loosely formed at Snowmass which included SLAC,
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Self-Configuring Wireless MEMS Network N-CSSC Net-Centric Software & Systems Consortium Planning Meeting February , 2008 Robert Akl UNT
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Sample Fit-Gap Kick-off
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Chapter 1 The Systems Development Environment
Introduction to Software Engineering
Implementing on a Limited Budget: Leveraging Existing Tools within Lockheed Martin Aeronautics Customer Support Centers Successful Collaboration and Knowledge.
Agile Process: Overview
X-DIS/XBRL Phase 2 Kick-Off
Project Lifecycle and IT Product Life Cycle
Presentation transcript:

Lockheed Martin Aeronautics Company Candidate Collaborative Projects for Net-Centric Application Michael F. Siok, PE Lockheed Martin Aeronautics Company P.O. Box 748, MZ 8604 Fort Worth, TX Tel: (817) FAX: (817)

Lockheed Martin Aeronautics Company Collaborative Research – Candidate Project Description WORK PACKAGE TITLE: Self-Configuring Wireless MEMS Network Problem Scope There is currently on-going research into MEMS device scale sensor packages with self-contained power generation. RE: Energy harvesting and storage, TCU, UC Berkeley. Given that device volumetric packaging is targeted for less than 5mm 3 with operations in hostile EMI and working environments, software needs to be small and efficient. Networking software should sense other compatible sensors in close proximity and establish a secure wireless communications environment. Assume sensor devices are all mobile all the time. Network should be adaptable to real-time changes in number of networked devices, changes in operational environment, etc., without loss of service Key Deliverables and Delivery Dates 1.Interim review of literature search and assessment activities. Deliver presentation and discussion with software development organizations within the consortium (3 months after go-ahead) 2.Perform incremental review of designs, tests, and prototype code using software tooling environment. Deliver final review in presentation form to consortium in net-centric manner. (6 months after go-ahead, incremental reviews to be coordinated separately by development team prior to presentation delivery) 3.Provide demonstration of network capability to deliver information to requesting system illustrating network reconfigurability with nodes dropping out and adding in, with loss of data due to ambient environmental noise, and independent mobility of all network nodes in same. Demonstration may involve actual equipment, prototypes, and/or simulations. (9 months after go-ahead) Case for Action Lockheed Martin Aeronautics has an interest in miniature, lightweight, self-powered, wireless sensors which can be installed in practically any location in the aircraft and left to function without requiring access panels for maintenance. Envisioned use in condition-based maintenance and flight-test and customer instrumentation applications. Given that small enough sensor packaging can be achieved, the ability of the sensors to configure themselves into a secure, viable, working network, and reconfigure the network at any time without loss of information (not necessarily data) is desired Large cost savings can be achieved in predictive maintenance rather than timed or reactive maintenance and also in configuring aircraft for instrumented tests. Major Tasks 1.Given that the MEMS mechanical and physical constraint problem can be solved separately, investigate, prototype, and test small networking software package that meets requirements of secure, viable, and adaptable communication for MEMS scale sensor devices delivering information packages to requesting systems also in secure, viable manner assuming all mobile devices. 2.Develop report that identifies and describes work, including requirements, designs, tests, and source. Deliver all items of software development lifecycle in electronic form only. 3.Provide demonstration. Leverage / Reuse / Collaboration This work will leverage existing standards, guidelines, and existing literature on the subject. The purpose is to learn how to apply what is known and scale it to new application. Use model-based engineering techniques for requirements and designs; use IDEs, automated Test and test generation tools The expertise of consortium members should be exploited and collaboration with consortium members is expected. Sponsor: M. F. Siok Principal Investigator: TBD

Lockheed Martin Aeronautics Company Collaborative Research – Candidate Project Description WORK PACKAGE TITLE: Net-Centric Scenarios in Domain-Specific Applications Problem Scope The number of elaborated examples of net centric application collected and presented by the net-centric consortium are at present few. Elaboration of the problem and potential available solution would lend credence to the consortium as well as provide a wealth of potential projects from which to develop, seek customers, and potentially develop. Since net-centric applications are potentially wide and varied, the consortium should choose a half-dozen or so domains of interest and develop one or more comprehensive scenarios that elaborate examples of problems that can be solved with net-centric solutions. Candidate domains of interest: Emergency Preparedness/Emergency Response Transportation and Transshipment Energy Distribution and/or Management Key Deliverables and Delivery Dates 1.Identify domains of interest (1 week after go-ahead) 2.Identify scenarios to be elaborated for each domain of interest (3 weeks after go-ahead) 3.Elaborate each scenario; document with detailed presentation. (2 weeks for each scenario – 3 months total) 4.Review each elaborated scenario with consortium members in a net-centric review fashion. (2 weeks for each review/correct cycle – 2 months to review all scenario packages) 5.Package reviewed scenarios and deliver to consortium for distribution and reuse as applicable. (one week following completion of last scenario). Case for Action The Net Centric Systems Consortium develops solutions for net centric systems application. These potential solutions address specific apparent problems that arise in domain-specific situations that can be identified and described completely. Specific cases for potential study should be elaborated and documented in presentation format at a minimum to begin a repository of potential project application. Customers and potential consortium members require concrete examples of net-centric applications in order to assess how the benefits of consortium membership can be leveraged within their companies. Documented cases, either completed projects or specific elaborated scenarios illustrating example application provide these concrete examples that can be leveraged by consortium industry members during key budgeting cycles. Major Tasks 1.Identify relevant domains of interest for the consortium for elaboration of scenarios. 2.For each domain of interest, identify at least 1, preferably 2 scenarios that can be elaborated to identify and describe net centric applicati8on and their utility 3.Elaborate chosen scenarios identifying the problems and net- centric solutions/features posed. Scope potential projects to develop potential solutions identifying resource requirements including engineering, capital, schedule, tests, etc. 4.Present each scenario for review to consortium members; package scenarios for delivery to consortium for follow-up action, if any. Leverage / Reuse / Collaboration It is expected that this work will leverage existing standards, guidelines, and research as well as all existing literature on the subject. The purpose is to learn how to apply what is known, and scale it to new application. The expertise of consortium members should be exploited and collaboration with consortium members is expected. Sponsor: M. F. Siok Principal Investigator: TBD