Code: Select all
\documentclass[12pt]{article}
\usepackage{graphicx}
\usepackage{verbatim} %for commenting
\usepackage[hyphens]{url}
\usepackage{xcolor}
\usepackage[urlbordercolor=blue]{hyperref}
\usepackage{breakurl}
\title{SRS}
\author{Peter Cao}
\begin{document}
...
\section{Performance Levels}
\begin{enumerate}
\item It should be very fast light-weight program, which shows changes in real-time and incurs no waiting on the part of the user.
\item Given the real-time role of MathJax in reflecting changes by the user, a careful study of MathJax's processes will be necessary, particularly loading behaviour. The MathJax engine is known to take a long time to start up. Speed would be abysmally implicated if the MathJax engine has to reload from scratch every time it is invoked; this would be entirely unnecessary. A way would need to be found to maintain MathJax on standby, rather than have its engine restart for every mark-up change that is made. In other words, new information would need to be retrieved in Ajax fashion, so that previously loaded information need not be reloaded unnecessarily.
\item Buttons should function asynchronously to keep up with dexterous, practised users.
\item It should require very little resources and have the fewest software pre-requisites on the client end, thereby ensuring the widest accessibility. It should run efficiently on the widest spectrum of operating environments and situations as possible.
\item To the extent that we are recruiting MathJax, the availability of JavaScript support seems unavoidable.
\item MathJax can either be sourced from my hosting server or MathJax CDN \url{http://cdn.mathjax.org/mathjax/1.1-beta/MathJax.js}. See \url{https://sites.google.com/site/mathjaxproject/design-documents/cdn-hosting-plan} for more information.
\end{enumerate}
\section{Data Structures/Elements}
...
Code: Select all
\documentclass[12pt]{article}
\usepackage{graphicx}
\usepackage{verbatim} %for commenting
\usepackage[hyphens]{url}
\usepackage{xcolor}
\usepackage[urlbordercolor=blue]{hyperref}
\usepackage{breakurl}
\title{SRS}
\author{Peter Cao}
\begin{document}
...
Protectionist measures:
\begin{enumerate}
\item Appropriate licensing. The programmer should inform me about the best options, as I am unfamiliar with the various licence classes and their implications for use by third parties.
\item Originally, it was entertained that the script could be concealed from users. To the extent JavaScript will be used for the front-end interface, this seems unlikely, since JavaScript is an inherently revealing mode of coding. Perhaps alternative means of delivery could be used, but it seems an unjustifiable length to go to just to have the script concealed.
\end{enumerate}
\section{Other required forum functions}
...