h <  HOME >  created October 21, 2019


https://searchapparchitecture.techtarget.com/definition/object-oriented-programming-OOP < Description of OOP 

  flaw>   "Data modeling" is the process of documenting a complex software system design as an easily understood diagram,
 using text and symbols to represent the way data needs to flow.
  flaw> The diagram can be used to ensure efficient use of data,
     as a blueprint for the construction of new software or for re-engineering a legacy application. 

 OOP modeling tools "... Four major principles underlie OO modeling. These are: 
1) abstraction, 
2) encapsulation, 
3) polymorphism, 
4) and inheritance. 

Although not specific to OO modeling, abstraction is a key principle.Jan 3, 2013 ..." :
modeling tools such as Cameo and Rhapsody  https://en.wikipedia.org/wiki/No_Magic 
Cameo ::  https://www.nomagic.com/mbse/overview/technical-overview.html  
Rhapsody ::  https://en.wikipedia.org/wiki/Rational_Rhapsody#targetText=Rational%20Rhapsody%2C%20a%20modeling%20environment,or%20embedded%20systems%20and%20software.&targetText=The%20product%20contains%20a%20server,been%20developed%20in%20Rational%20Rhapsody. 
"... Rational Rhapsody, a modeling environment based on UML, is a visual development environment for systems engineers and software developers creating real-time or embedded systems and software. Rational Rhapsody uses graphical models to generate software applications in various languages including C, C++, Ada, Java and C#. Developers use Rational Rhapsody to understand and elaborate requirements, create model designs using industry standard languages (UML, SysML, AUTOSAR, DoDAF, MODAF, UPDM), validate functionality early in development, and automate delivery of high structured products.[1] ..."



 Prognostics and Health Management (PLTM) system   
  SOURCE: https://www.ziprecruiter.com/c/Lockheed-Martin/Job/Data-Architect/-in-Orlando,FL?jid=DO249099cd7c3d4d4d0fdbfcbbb577edf7
"...   Data Architect Lockheed Martin Orlando, FL :: Posted: September 09, 2019
Full-Time **Description:** This position is for a senior level Data Architect within the Lockheed Martin Chief Data and Analytics Office \(CDAO\), reporting to the Data Strategy Senior Manager\.

The successful candidate will operate at the intersection of systems architecture, business process architecture, and information architecture to ensure the implementation of LM data strategy aligns to and enables the LM business strategy\.
Responsibilities include:
\- Data architecture for the Digital Transformation Program \(DTP\) Data Strategy Value Stream, working in concert with the DTP Systems Engineering, Integration & Test \(SEIT\) organization and the business area CDAO teams\.
\- Drive enterprise\-level data architecture standards, including partnership with the Big 4 program, to support business process transformations in areas such as Enterprise Resource Planning \(ERP\), Product Lifecycle Management \(PLM\),
Manufacturing Execution Systems \(MES\), and Human Resources Management Systems \(HRMS\)\.
\- Define and develop enterprise\-wide data domains, enable data domain stewards, and consult across the enterprise on federated data architecture solutions\.
\- Apply systems engineering and systems architecture disciplines to data strategy implementation and operations
\- Support data strategy activities such as data governance, data sharing/rights, data quality, data exchange, etc\.
**Basic Qualifications:**
\- Proven experience with data and information architecture
\- Proven experience with systems engineering and systems architecture
\- Proven experience with business process architecture and process transformation
\- Proven experience leading a distributed technical team to implement and operationalize a strategic goal
\- Proven experience harmonizing systems, processes, and/or data across business areas and functions
\- Proven experience building and communicating technical and functional roadmaps
**Desired Skills:**
\- Experience with model\-based systems engineering \(MBSE\) methodology
\- Experience with System of Systems \(SoS\) architecture
\- Experience with Systems Modeling Language \(SysML\) and/or Unified Modeling Language \(UML\)
\- Experience with frameworks and standards such as Department of Defense Architecture Framework \(DoDAF\), Open Applications Group Integration Specification \(OAGIS\), and APQC process classification frameworks \(PCF\)
\- Experience with modeling tools such as Cameo and Rhapsody
\- Working knowledge of the LM Digital Transformation Program
**Lockheed Martin is an Equal Opportunity/Affirmative Action Employer\. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, pregnancy, sexual orientation, gender identity, national origin, age, protected veteran status, or disability status\.**
Join us at Lockheed Martin, where your mission is ours\. Our customers tackle the hardest missions\. Those that demand extraordinary amounts of courage, resilience and precision\. They're dangerous\. Critical\. Sometimes they even provide an opportunity to change the world and save lives\. Those are the missions we care about\.
As a leading technology innovation company, Lockheed Martin's vast team works with partners around the world to bring proven performance to our customers' toughest challenges\. Lockheed Martin has employees based in many states throughout the U\.S\., and Internationally, with business locations in many nations and territories\.
Experienced Professional

Lockheed Martin
Orlando, FL
32806 USA  ..."






 https://ieeexplore.ieee.org/document/6231471    "... Abstract:
Prognostic health management (PHM) is a method for assuring the reliability of a system by monitoring the system in real time as it is used in the field. As the system wears out, but before failure, information that facilitates decision making about the future use of the system is delivered to the user. In this paper, a cost justification has been developed for incorporating the additional circuitry needed to enable prognostics for electrical components directly onto a functional circuit board. Implementing PHM capability for circuit boards will add additional cost to a system, so high reliability systems where the cost of failure is high are easiest to cost justify for prognostics. Aerospace, defense and automotive, applications qualify as high reliability systems. Application domains that require high uptime, minimal amounts of unplanned maintenance, and controllable operating costs can also be cost justified for prognostics since they can benefit from the pro-active management of failures facilitated by PHM. Intangible criteria such as safety or the cost of human life also motivated the need for PHM, so often times projects are labeled strategic, and not subjected to the discipline of a financial analysis. This paper will show rigorous methods for assessing the decision to invest in PHM for electronics. The uncertain nature of research and development (R&D) and difficult to predict future economic conditions is not well captured by traditional discounted cash flow (DCF) methods. An approach known as the Datar-Mathews (DM) method will extend the DCF methods to be equivalent to a real options analysis and the Black-Scholes formula. The DM method is intuitive and uses concepts familiar to most engineers and technical managers. Published in: 13th InterSociety Conference on Thermal and Thermomechanical Phenomena in Electronic Systems
Date of Conference: 30 May-1 June 2012 : Date Added to IEEE Xplore: 05 July 2012
 ISBN Information:  ISSN Information:
INSPEC Accession Number: 12849576
DOI: 10.1109/ITHERM.2012.6231471
Publisher: IEEE Conference Location: San Diego, CA, USA ..." 
Document Sections
1. Introduction
2. F-35 PHM System Development
3. F-35 PHM System Operation
4. Abstract: F-35 "Lightning II" Joint Strike Fighter (JSF) Program is developing a
comprehensive and industry-leading Prognostics and Health Management (PLTM) system.

This system, which is central to the program's Performance Based Logistics (PBL) approach, is built on incremental capability deployment and a careful balance of on-aircraft and off-board software, systems, and processes. The breadth of capability development and timing of deployment is unprecedented for a combat aviation system.

The initial set of F-35 PHM capabilities is currently deployed and actively supporting the flight test program.

This paper will provide a top level overview of the F-35 PHM concept and architecture, the incremental design approach, and discuss overall program status. Some specific examples of long-term system benefits, in relation to sustainment and PBL business decisions, will be discussed.  Published in: 2011 IEEE Conference on Prognostics and Health Management

 "data modeling" "F-35" "objects"

 Experience in maintaining, troubleshooting, or Prognostics & Health Management (PHM) capability development for the F-35 aircraft


 "... The first step in OOP is to identify all of the objects a programmer wants to manipulate and how they relate to each other, an exercise often known as data modeling. ..."



 https://pl.cs.jhu.edu/  The Programming Languages Laboratory at The Johns Hopkins University

https://en.wikipedia.org/wiki/Object-oriented_programming   < History 

 A Programming  methodology which enables a "system" to be modeled as a set of objects which can be controlled and manipulated in a modular manner.

"object-oriented" projects
"... An OO project is a sequence of unique, complex and connected activities having one goal or purpose that must be completed by a specific time, within budget and according to specification, that uses Object Technology to help reach its goal. ..."

 Computer History ::  https://www.computerhistory.org/timeline/computers/ 



 DoDSTD-2167 4 JUNE 1985
MILSTD-1644B (TDl) 2 MARCH 1984

  https://en.wikipedia.org/wiki/Waterfall_model  :::  https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm


binary logic numbers  :: https://www.electronics-tutorials.ws/binary/bin_1.html 


computer state logic ::  https://en.wikipedia.org/wiki/Three-state_logic

Very often, when referring to the word size of a modern computer, one is also describing the size of address space on that computer

 It denotes the number of bits that a CPU can process at one time.  

 SOURCE: https://en.wikipedia.org/wiki/MIL-STD-498 :::: https://en.wikipedia.org/wiki/MIL-STD-498 

Addressable memory locations digital software


 SOURCE: https://en.wikipedia.org/wiki/DOD-STD-2167A 
"... Criticism
One criticism of the standard was that it was biased toward the Waterfall Model. Although the document states "the contractor is responsible for selecting software development methods (for example, rapid prototyping)", it also required "formal reviews and audits" that seemed to lock the vendor into designing and documenting the system before any implementation began.[citation needed]

Another criticism was the focus on design documents, to the exclusion of Computer-Aided Software Engineering (CASE) tools being used in the industry. Vendors would often use the CASE tools to design the software, then write several standards-required documents to describe the CASE-formatted data. This created problems matching design documents to the actual product.[citation needed]

One result of these criticisms was to begin designing a successor standard, which became MIL-STD-498.[5] 

Another result was a preference for formal industry-designed standards (such as IEEE 12207) and informal "best practice" specifications, rather than trying to determine the best processes and making them formal specifications.

MIL-STD-2167A with MIL-STD-498 eventually became the basis for DO-178 in the early 1980s,[6] the latter followed by subsequent revisions. MIL-STD-2167 and MIL-STD-498 together define standard software development life cycle processes that are expected to be implemented and followed as well as defining standard document format and content. In contrast, DO-178B/C defines objectives that should be accomplished as acceptable means[7] of demonstrating airworthiness, permitting relative flexibility in the life cycles and processes employed to accomplish those objectives.[8] ..."


 identical demilitarized version EIA J-STD-016[1] [2] as a process example guide for IEEE 12207. S

 DoDSTD-2167   DoDSTD-2167

https://dokumen.tips/documents/dod-std-2167.html  >> https://dokumen.tips/download/link/dod-std-2167

 https://dokumen.tips ::  https://dokumen.tips/download/link/dod-std-2167


 https://calhoun.nps.edu/bitstream/handle/10945/8896/reengineeringofm00hirs.pdf?sequence=1 <189 pages 

 Re-engineering of a mission critical satellite  communications component TD-1271B/U photos
 http://www.navy-radio.com/ships/bb61-3.htm < Photos < USS Iowa BB-61 Radio Room Photos - August 2017 

 "pdf" DOD-STD-1679A "DOD-STD-1679" A  :: 

 SOURCE: https://media.defense.gov/1992/Mar/04/2001714626/-1/-1/1/92-056.pdf

 "... The program office did not insert DOD-STD 1679 or 1679A in lieu of DOD-STD 2167A.
The initial software development took place well before DOD-STD 2167 even existed. DOD-STD-2167 came into existence in 1985 and
was revised again in 1988 (DOD-STD 2167Al . It was determined that the expense associated with forcing the contractor to comply in full with the guidelines of 2167A was not worth the advantages. Instead, a phased-in approach was chosen which is more practical and cost effective. Currently, in Lots IV, V and beyond, the contractor is required to deliver all data items (software and documentation) per the guidelines of 2167A. ..."



 "Perry Memo" ::  William Perry :: https://en.wikipedia.org/wiki/William_Perry 

 SOURCE: https://en.wikipedia.org/wiki/United_States_Military_Standard 
"...  In the U.S. during the 1980s and early 1990s, it was argued that the large number of standards, nearly 30,000 by 1990, imposed unnecessary restrictions, increased cost to contractors (and hence the DOD, since the costs in the end pass along to the customer), and impeded the incorporation of the latest technology. 

 [ Responding to increasing criticism ... SUSAN SAYS ]

Responding to increasing criticism, Secretary of Defense William Perry issued a memorandum in 1994 that prohibited the use of most military specifications and standards without a waiver.[3] This has become known as the “Perry memo”. 

Many military specifications and standards were canceled. In their place, the DOD directed the use of performance specifications and non-government standards. 

“Performance specifications” describe the desired performance of the weapon, rather than describing how those goals would be reached (that is, directing which technology or which materials would be used). 

In 2005 the DOD issued a new memorandum[4] which eliminated the requirement to obtain a waiver in order to use military specifications or standards. 
The 2005 memo did not reinstate any canceled military specifications or standards. ..."






 MIL-STD-1530 Aircraft Structural Integrity Program (ASIP)



"... Defendant Lockheed Martin Corporation (“Lockheed” or “Defendant”) is a
Maryland corporation with its principal place of business at 
6801 Rockledge Drive, Bethesda, MD 20817. software 

More relevant to the events herein, is the Lockheed Martin
Corporation offices located at

 1 Lockheed Street, Fort Worth, Texas 76108. software 
Through such offices, the relevant Joint Strike Force Program and other similar programs were managed in relevant part.

 The software development process, its quality control and its compliance
evaluations for the F-35 and other programs occurred under the auspices of these offices.

Lockheed’s agent for service of process is Frances J. Frizzell, 6801 Rockledge Drive,
Bethesda, MD 20817.  ..."

Design Integration Systems Engineering Test FORCE Cost Earned Value  Interoperability SAIT Business Fiance Air Worthiness  International


 Lincoln Law : https://en.wikipedia.org/wiki/False_Claims_Act :: https://en.wikipedia.org/wiki/False_Claims_Act



 Military Software Development Specifications  https://en.wikipedia.org/wiki/MIL-STD-498
          It was meant as an interim standard, to be in effect for about two years until a commercial standard was developed.
 it was canceled on May 27, 1998 and replaced by the essentially identical demilitarized version EIA J-STD-016[1]


  ISO/IEC/IEEE 15288:2015 ::  


SYLVESTER DAVIS Lockheed "flight control software" Houston-based lawyer Samuel Boyd 



 https://en.wikipedia.org/wiki/Joint_Strike_Fighter_program  <History - The Beginning ::  

Joint Advanced Strike Technology (JAST) Common Affordable Lightweight Fighter (CALF) project to make the Joint Strike Fighter program.

 JAST  ::  
Joint Advanced Strike Technology (JAST) project was merged