<?xml version="1.0" ?>
<rss version="2.0">
	<channel>
		<title><![CDATA[ Aerospace and Electronic Systems Magazine, IEEE - new TOC ]]></title>
		<link>http://ieeexplore.ieee.org</link>
		<description>TOC Alert for Publication# 62 </description>
		<year>2009</year>
		<month>November </month>
		<day>23</day>
		<item>
			<title><![CDATA[IEEE Aerospace and Electronic Systems Magazine]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317768]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317768]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>c1</startPage>
			<endPage>c1</endPage>
			<fileSize>483</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[This month's covers ...]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317766]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317766]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>c2</startPage>
			<endPage>c2</endPage>
			<fileSize>453</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[In this issue - technically]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317770]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317770]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>2</startPage>
			<endPage>2</endPage>
			<fileSize>806</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[From the editor-in-chief [Society News & Information]]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317772]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317772]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>3</startPage>
			<endPage>3</endPage>
			<fileSize>662</fileSize>
			<authors><![CDATA[Pace, T.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Systems engineering execution and knowledge management]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317774]]></link>
			<description><![CDATA[The purpose of this is to refocus programs back to the basic objectives of systems engineering execution and capturing key domain knowledge during the time when organizations are adopting new processes, procedures, or technology. While change is necessary, the discipline of the systems engineering and development process (requirements, design, implementation, test, delivery, product feedback, and sustainment) can be adversely impacted in the predicament of checking the updated process and/or procedure compliance box. Simplified approaches will be provided to better manage products and teams including discussion of web and database tools. These approaches provide the ability to better understand and manage products in an age of, sometimes, overwhelming circumstances. This identifies simplified solutions, improvement suggestions, and work flow diagrams with key entry points (framework) for new and legacy programs that include: appointment of improvement focals; maximum use of web portals (one-stop shopping); maximum focus on information that is "need to know," and is provided in a simple, database-driven manner (project domain knowledge management); minimum focus on information that is "nice to know" but is provided for career advancement; common sense entry points for existing programs by utilizing data obtained from quick assessments and Peer Reviews including standard meeting agendas, intergroup coordination meetings, and common status report templates.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317774]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>4</startPage>
			<endPage>9</endPage>
			<fileSize>3767</fileSize>
			<authors><![CDATA[Head, S.;Virostko, B.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Optically tuneable photonic crystal waveguides]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317777]]></link>
			<description><![CDATA[Incorporation of DNA into nanoscale wells in a silicon substrate has been demonstrated to show fabrication feasibility for optically tunable photonic crystal waveguides. A change in propagation characteristics due to DNA incorporation has been observed for a silicon-on-insulator photonic crystal waveguide.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317777]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>10</startPage>
			<endPage>11</endPage>
			<fileSize>1107</fileSize>
			<authors><![CDATA[Masturzo, S.;Jackson, H.;Boyd, J.;Ewing, R.;Abdel-Aty-Zohdy, H.;Yarrison-Rice, J.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Spacecraft engineering and research at Saint Louis University]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317779]]></link>
			<description><![CDATA[Parks College of Engineering and Aviation of Saint Louis University [1i] has a tradition of offering an outstanding aerospace engineering education to prepare students at the undergraduate and graduate level for careers in commercial aviation, defense systems, and space systems fields. Courses are offered across the engineering spectrum (aerospace, electrical and computer engineering, and physics departments) ranging from an introduction to aerospace engineering to spacecraft design, spacecraft communications, and space physics. Students participate in courses that include orbital mechanics, space dynamics, spacecraft engineering, and space systems. Senior capstone project work is also included. A separate Astronautics Engineering track as well as a Minor in Space Systems Engineering for non-aerospace engineering students is currently being developed. A, number of student-driven space systems projects are in process that involve design, development, and test of small satellites similar to those recently highlighted in the March 2009 Systems article entitled The First one Hundred University-Class Spacecraft 1981 - 2008. Reference [4] identifies student spacecraft launched over the past 27 years.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317779]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>12</startPage>
			<endPage>16</endPage>
			<fileSize>2530</fileSize>
			<authors><![CDATA[Jayaram, S.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Techniques for building excellent operator machine interfaces (OMI)]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317781]]></link>
			<description><![CDATA[Establishing a process to continually improve understanding of operator requirements - the why as well as the how - is key to developing an optimal Operator-Machine Interface (OMI) for a large program. The P-8A program is one example of a complex software development, with over 2 million lines of code and a unique and complex OMI. The OMI itself is used as a tool for achieving and is designed in parallel with understanding end goals, operator decision making chains, and thought processes. The OMI can be designed to support and anticipate information needs and alert operators to unusual occurrences. Operator actions and decision-making techniques can be discovered by using expert operators and capturing their knowledge through the use of multiple tools to identify the problem set: storytelling, decision mapping, and is/is not matrices. When a solution set has been identified and agreed to by the customer, resources allocated, and schedule set, a standard process captures and prioritizes further changes, identities their impact, and decides on implementation. Documents describing design and processes and a Design Description Document describing the current version of OMI are made accessible to stakeholders at all times. "What's important is not that we can conceive the idea, but flail when eve actually test it on people You discover it doesn't work ...yo ur intuition is wrong."]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317781]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>17</startPage>
			<endPage>22</endPage>
			<fileSize>4031</fileSize>
			<authors><![CDATA[Gorman, P.;Pappas, N.;]]></authors>
		</item>
		<item>
			<title><![CDATA[SVSS: Intelligent video surveillance system for aircraft]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317783]]></link>
			<description><![CDATA[Safety and security are the most discussed topics in the aviation field. The latest security initiatives in the field of aviation propose [1I] the aircraft carriers to implement video surveillance within the aircraft at strategic locations. The current proposals allow the video surveillance data to be stored within the aircraft and monitored by one of the flight crew. The monitoring crew will be responsible for identifying the anomaly within the aircraft and take necessary preventive actions. With the introduction of additional technology within the aircraft, mere human perception may not be sufficient to make a decision. In this research work, the authors explore the possibility of implementing a smart video surveillance system (SVSS) within the aircraft that is tuned toward detecting the behavioral anomaly within the aircraft. The SVSS will generate security triggers when it detects an anomaly within the aircraft. These triggers could be combined with other triggers generated by different aircraft components (possible alarms from the flight crew, data traffic anomaly, or alarm generated by one of the avionics components) to provide a better understanding of the situation to the monitoring crew.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317783]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>23</startPage>
			<endPage>29</endPage>
			<fileSize>3744</fileSize>
			<authors><![CDATA[Thanthry, N.;Emmuadi, I.P.;Srikumar, A.;Namuduri, K.;Pendse, R.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Design considerations for systems hosted on integrated modular avionics]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317784]]></link>
			<description><![CDATA[System architects are accustomed to developing systems hosted in federated environments that allow for developmental independence. However, the system boundaries are different when systems are hosted in an Integrated Modular Avionics (IMA) platform. The boundaries lie within shared resources, and thus lead to greater dependencies between systems. This drives new design considerations for system architects. The natural tendency is to leverage traditional federated design concepts when building systems for IM1A environments, but this can lead to inefficient use of system resources, and a lack of preparedness for the inevitable change that will occur within the integrated set of systems. NMA has become a standard in the civil and military aviation industries, so it is important to understand these new design considerations. The question addressed by this paper is "What unique design considerations are there for systems hosted on an IMA platform ?" All of the considerations can be attributed to three main drivers present in the IMA environment: * 1) optimization of system resources across the integrated set of hosted systems, * 2) change containment when hosted systems change, and * 3) change containment when the NMA platform elements change (technology insertion). These three factors impact the traditional developmental independence between systems since it requires the architect to consider their system's role within the integrated set of systems. They must now consider how they will tolerate changes that are out of their control, such as changes to other hosted systems or the IMA platform that affect the shared resource performance. They must now consider how they contribute to the efficient use of system resources as part of the greater system-wide optimization strategy. If these factors are not addressed, then it can lead to wasted system resources, increased development costs, and high costs-of-change. Therefore the incentive to ensure that these new design consi-
derations are addressed lies with both the system integrator who owns the integrated set of systems and the architect of each hosted system. This is based upon the authors' experience in developing 11%A systems at GE Aviation. GE Aviation has developed open system 11%A architectures for commercial aircraft (Boeing 787 Dreamliner), as well as military aircraft (Boeing C-130) combat aircraft, and Boeing KC-767 Tanker).]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317784]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>30</startPage>
			<endPage>35</endPage>
			<fileSize>3868</fileSize>
			<authors><![CDATA[Watkins, C.B.;Waiter, R.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Trust and decision-making: An empirical platform (CCP 204)]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317785]]></link>
			<description><![CDATA[The trust literature emphasizes trust in automation, thus neglecting the interpersonal aspects of how distributed personnel develop trust. Interpersonal trust represents the willingness of individuals to accept vulnerabilities from the actions of others. Vulnerability is a critical aspect of trust research, yet few studies have manipulated vulnerability. Non-verbal cues may have an influence on the trust process, suggesting that features of collaborative tools may influence how individuals build trust. The present study will implement a 3 x 4 mixed design. Participants will select a convoy route based on: * 1) graphical displays of enemy zones and historical Improvised Explosive Device (lED) occurrences; * 2) route parameters (e.g., fuel required); and * 3) information from a local expert. Vulnerability will be manipulated by altering the frequency of TEDs and the location of "red forces" to create low, moderate, and high vulnerability conditions (within subjects factor). Information from local experts will be presented via one of four conditions: * 1) audio/video with low emotion; * 2) audio/video with high emotion; ,, 3) audio only; and * 4) chat (between subjects factor). Findings from this research will support the development of new collaborative tools for the Command and Control (C2) domain.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317785]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>36</startPage>
			<endPage>41</endPage>
			<fileSize>3587</fileSize>
			<authors><![CDATA[Lyons, J.;Stokes, C.;Garcia, D.;Adams, J.;Ames, D.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Data processing through optical interfaces]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317786]]></link>
			<description><![CDATA[Herein, we propose a physical process inspired routing that routes data from a high-bandwidth data port to multiple processing tiles. Our routing is named Magnetic Based Routing (MBR); data is "attracted" toward the processing tiles that need the data and is "repulsed" from other data flows.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317786]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>42</startPage>
			<endPage>43</endPage>
			<fileSize>1043</fileSize>
			<authors><![CDATA[Teller, J.;Ozguner, F.;Ewing, R.;]]></authors>
		</item>
		<item>
			<title><![CDATA[October 2009 Distinguished lecturers & tutorials - news & information]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317788]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317788]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>44</startPage>
			<endPage>44</endPage>
			<fileSize>559</fileSize>
			<authors><![CDATA[Huddle, J.R.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Space systems panel meeting in Italy - news & information]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317789]]></link>
			<description><![CDATA[On July 6, 2009, a meeting celebrating the IEEE's 125 1 year and the 5&~ year of the IEEE Italy Section was organized by the IEEE Italy GOLD, the AESS Space Systems Technical Panel, and the Italian Joint Chapter of Signal Processing & AES. The event was sponsored by AFCEA (Armed Forces Communications and Electronics Association) and the IEEE Italy Section.]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317789]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>45</startPage>
			<endPage>45</endPage>
			<fileSize>751</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[Directory of IEEE-AESS personnel]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317790]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317790]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>46</startPage>
			<endPage>46</endPage>
			<fileSize>599</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[IEEE aerospace & electronic systems society organization]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317792]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317792]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>47</startPage>
			<endPage>47</endPage>
			<fileSize>602</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[IEEE 2008 aerospace and electronic systems society - membership application]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317796]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317796]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>48</startPage>
			<endPage>48</endPage>
			<fileSize>508</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
		<item>
			<title><![CDATA[AESS meetings & conferences]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317800]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317800]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>c3</startPage>
			<endPage>c3</endPage>
			<fileSize>399</fileSize>
			<authors><![CDATA[Breen, B.C.;]]></authors>
		</item>
		<item>
			<title><![CDATA[Back cover]]></title>
			<link><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317801]]></link>
			<description><![CDATA[ ]]></description>
			<pubDate><![CDATA[Oct.  2009]]></pubDate>
			<guid><![CDATA[http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=5310328&arnumber=5317801]]></guid>
			<volume>24</volume>
			<issue>10</issue>
			<startPage>c4</startPage>
			<endPage>c4</endPage>
			<fileSize>573</fileSize>
			<authors><![CDATA[]]></authors>
		</item>
	</channel>
</rss>