innovation-bcosse.tex.svn-base

来自「远程学生作业提交系统,所用技术JSP,Servelet,Ajax,Web Ser」· SVN-BASE 代码 · 共 118 行

%%% Replace XXXXX with your login name
\section{Proposal from bcosse}

%%
%%	You may NOT change the LaTeX structure of this file.
%%
%%	Your work should be placed immediately under the commented
%%  instruction text, within the {description} area.  You may 
%%  delete the comments provided for neatness if you wish.
%%
%%  The following brief shows what you should produce:
%%
%%	\begin{description}
%%		\item[Brief description]
%%	
%%			I would like to write an innovation component which 
%%			can be used by a lecturer to check for cheating within
%% 		    student submissions.
%%
%%		\item[Benefit (or {\em why} this is an innovation]
%%			
%%			This would be of benefit to lecturers because it would
%%			provide an automated way of checking whether submissions
%%			contained text written by someone else.
%%
%%		\item[Services to be used]
%%			I would use the Login service to verify that a user
%%			is a staff member (students should not be able to
%%			use this component).  The VerifySubmission service
%%			would be used to retrieve the contents of a specified
%%			submission.  I would probably use the Google search
%%			API to check against outside resources (though how to
%%		   	do this is uncertain).  This component would be exposed
%%			as a service called something like {\tt CheckPlagiarism},
%%			which was given details of a project to check, as its
%%			input.
%%		    
%%		\item[Technologies]
%%			No new or fancy technologies, except possible Google (not
%%			sure if they use SOAP or REST).
%%
%%		\item[Barriers]
%%			I've never used Google before, and I don't know anything
%%			about plagiarism checking.  I can fix these by independent
%%			research
%%	\end{description}
 
\begin{description}
	\item[Brief description]

		I would like to develop a rich XML-based cross-platform user interface 
		for allowing students to handle effectively their submissions for a
		project.

	\item[Benefit]

		Using an HTML interface for allowing students to upload, download,
		delete some files of their submissions for a project is not the best
		solution. Indeed, an HTML interface has really limited features. For
		instance, it would be interesting to be able to drag and drop files,
		use copy and paste and shortup keys. This is the features I propose
		to include thanks to this new interface.
		

	\item[Services to be used/created]

		We would use the \textit{authenticateUser} service to verify that a user
		is really a student. Then we would probably use the \textit{verifySubmission},
		\textit{getSubmission}, \textit{getSubmissionList}, \textit{addSubmission} services 
		to retrieve and manage the submissions done by a student 
		for a project.
		Besides, a new service called something like \textit{deleteSubmission}
		could be add to allow a student to delete one of their submission
		files.

	\item[Technologies]

		The new technology, we would use, is called XUL. XUL (pronounced "zool") 
		stands for "XML User-interface Language" which is a cross-platform 
		language for describing user interfaces of applications.
		Basically, such a user interface is based on HTML, JavaScript and XML.
		
		There are several ways that XUL applications are created:
		\begin{itemize}
		\item \textbf{Firefox extension: } 
			An extension adds functionality to the browser itself, 
			often in the form of extra toolbars, context menus, 
			or UI to customize the browser UI.
		\item \textbf{Standalone XULRunner application: }
			XULRunner is a packaged version of the Mozilla platform 
			which allows you to create standalone XUL applications. 
			A browser isn't required to run these applications, as they 
			have their own executable file.
		\item \textbf{XUL package: }
			In between the other two are applications which are created 
			in the same way as an extension, but they act like a separate 
			application in a separate window.
		\item \textbf{Remote XUL application: }
			You can also just place XUL code on a web server and open 
			it in a browser, as you would any other web page.
		\end{itemize}

		We would try to develop our UI as a Firefox extension and for an interoperability
		purpose, as a the Standaline XULRunner application.

		If you want to read a little bit more about XUL, please refer to these links: \\
		\textit{http://developer.mozilla.org/en/docs/The\_Joy\_of\_XUL} \\
		\textit{http://www.xulplanet.com/tutorials/xultu/}

	\item[Barriers]

		Our team never used XUL before, but according to mozilla developper center,
		Web developers already familiar with Dynamic HTML (DHTML) can learn XUL 
		quickly and can start building applications right away. So, it should be possible
		to bypass this difficulty.

\end{description}