Skip to content

Commit

Permalink
Move of bullet point from abstract section to conclusion section
Browse files Browse the repository at this point in the history
Signed-off-by: Paul Wortman <paul.mauddib28@gmail.com>
  • Loading branch information
paw10003 committed Jul 4, 2015
1 parent f738ce4 commit c7383e9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion PBDSecPaper.tex
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,6 @@
\begin{itemize}
\item PBD centers around minimzing the cost of development through a ``meet-in-the-middle'' methodology where successive refinements of specifications meet with abstractions of potential implementations. The goal being to obtain the same level of abstraction as is writtien into good coding functions.~\cite{Vincentelli2002}
\item Security centers around being able to gauge the trustworthiness of components as well as the larger system made of distributed components.
\item As with any new shift in design methodoloy the largest cost in this new system would be the need for rigorous documentation and standardization of the process, components, and communication elements of said components.
\item Lack of design/methodology for doing platform-based design of security elements, although conceptual use in mobile embedded systems.
\item Ground work for implementing security via PBD exists; this paper is centered around connecting the dots and laying the foundation for framework that will be built upon for creating security in a doucmented, rigorous, standardized way.
\end{itemize}
Expand Down Expand Up @@ -214,6 +213,7 @@ \section{Conclusion}
\begin{itemize}
\item Need for development of platform-based design for security elements of all types
\item Advantages: swap out old security modules with newer ones (re-use of base system), degree of system customization to meet system hardware/software needs
\item As with any new shift in design methodoloy the largest cost in this new system would be the need for rigorous documentation and standardization of the process, components, and communication elements of said components.
\end{itemize}
%references section
Expand Down

0 comments on commit c7383e9

Please sign in to comment.