Push of last edits

AADLSecPaper.tex

@@ -309,8 +309,8 @@ Extensions to the security-centric aspects of the AADL language have been recent
 
 The new security framework that this paper proposes would require the following steps to take place:
 \begin{enumerate}
-	\item Creation of a low-level component library that would contain normal and secure version implementations of each base component within the architectural space used for model generation.
-	\item Formalized description and definition of higher level security requirements that may come from user-defined needs or from the experience of knowledge of security experts.
+	\item Creation of a low-level component library that would contain normal and secure version implementations of each base component within the architectural space used for model generation.  (Example: Listing~\ref{lst:AADLSecEncryption})
+	\item Formalized description and definition of higher level security requirements that may come from user-defined needs or from the experience of knowledge of security experts. (Example: Listing~\ref{lst:AADLSecLevels})
 	\item Creation of a mapping process by which security requirements and secure component specifications can be uniformly compared to allow for the generation of potential secure architectural system model solutions to the given inputs.
 	\item Verification tools to validate mapping implementation solutions.
 	\item Implementation of automated tools for the purpose of thoroughly exploring the entire design space for optimizing generated designs while minimizing the amount of time spent developing said design models.