Last modifications and corrects.

Author: lukmdo

Chapter_02.tex

@@ -1,7 +1,7 @@
 \chapter{System Concept}\label{chap:concept}
 The following chapter will cover the system concept, the functionality it offers and the general functional system description. Also, the following sections should clarify how the SmartNotes application can be used, illustrate its design using the UML diagrams and prepare the reader for more detailed system description included in the Chapter~\ref{chap:sys_description}.
 
-The motivation and idea for creating SmartNotes application was described in Chapter~\ref{sec:Introduction}.The core idea is to deliver a scalable note taking application that could be used disregarding network connectivity and make the notes synchronized just when the user plugs in. This model combines the idea of web-based interface with offline access to fully functional notebook application. It remains exposed for future feature expansion both for the web-based SmartNotes and the client application iSmartNotes.
+The motivation and idea for creating SmartNotes application was described in Chapter~\ref{sec:Introduction}. The core idea is to deliver a scalable note taking application that could be used disregarding network connectivity and make the notes synchronized just when the user plugs in. This model combines the idea of web-based interface with offline access to fully functional notebook application. It remains exposed for future feature expansion both for the web-based SmartNotes and the client application iSmartNotes.
 
 \section{Functionality description}\label{sec:functionality_descr} 
 Detailed description of how a system may be used should by of utmost importance both to the developer and to the end user, as it helps gain a general perspective, called 10,000-foot view~\cite[page 49]{uml_use_case}, of the system and make useful observations. The implementation as well as the conceptual and system design decisions become a side issue, as the foreground is always occupied by the functionality  the application is to offer. For that reason, the use of case scenarios and flow charts will be very helpful in describing the efficient way of using the SmartNotes application.
@@ -40,7 +40,7 @@ \section{Functional description}\label{sec:functional_descr}
 
 Admittedly, in order for the application to gain popularity, users should be well informed about the application and its functionality; also, it is vital to provide availability of instructions on how to get started. For these reasons, the landing page should be not only informal and practical, but also international to reach greater group of users.
 
-From the architectural point of view, SmartNotes is a simple client-server application, the only difference being the usage of DVCS, which allows the machines to access the same set of commands and make their hard disks hold the entire repository with its history. Yet, it may be confusing that it still remains a client-server architecture, but just as the centralized VCS do not recognize any other architecture than the client server, the distributed VCS uses it as one of possible use cases. In the following scenario one of the machines fulfills a role of the reverential server to which all remaining machines direct their requests, at the same time being a for of public repository with the most recent version that should be always available to users. In consequence, each client requires the installation of DVCS as one of the main components, while the size of the chosen VCS matters as much as its performance, which all in all has significant impact on the final performance of iSmartNotes. For optimum user experience, the iSmartNotes application provides an easy-to-install package that could be downloaded from the server serving static content, which is not only a faster solution from dynamically served content, but also allows to save system resources, costing a minimum of CPU time.
+From the architectural point of view, SmartNotes is a simple client-server application, the only difference being the usage of DVCS, which allows the machines to access the same set of commands and make their hard disks hold the entire repository with its history. Yet, it may be confusing that it still remains a client-server architecture, but just as the centralized VCS do not recognize any other architecture than the client server, the distributed VCS uses it as one of possible use cases. In the following scenario one of the machines fulfils a role of the reverential server to which all remaining machines direct their requests, at the same time being a for of public repository with the most recent version that should be always available to users. In consequence, each client requires the installation of DVCS as one of the main components, while the size of the chosen VCS matters as much as its performance, which all in all has significant impact on the final performance of iSmartNotes. For optimum user experience, the iSmartNotes application provides an easy-to-install package that could be downloaded from the server serving static content, which is not only a faster solution from dynamically served content, but also allows to save system resources, costing a minimum of CPU time.
 
 The next two sections state certain problems related to synchronization scenarios using VCS and the application activation. They will be analyzed focusing on the evaluating of a number of possible solutions and the argumentation will lead to the choice of the most optimal solution.  
 
@@ -112,6 +112,6 @@ \subsection{iSmartNotes activation process}\label{subsec:ismartnotes_activation}
 \end{center}
 \end{figure}
 
-Therefore, no matter if the user decides to use iSmartNotes for the first time or has just changed the machine, they will only be required to login to SmartNotes using their Google Account, download the application and pass the activation code. To make an even more conspicuous comparison between this idea and its performance based on a classical account system, Figure~\ref{} demonstrates the actions that the user has to follow to use the systems. 
+Therefore, no matter if the user decides to use iSmartNotes for the first time or has just changed the machine, they will only be required to login to SmartNotes using their Google Account, download the application and pass the activation code. To make an even more conspicuous comparison between this idea and its performance based on a classical account system.%Figure~\ref{} demonstrates the actions that the user has to follow to use the systems. 
 
 Yet, the fact that it becomes a standard for network applications and more and more users know this procedure does not make it a perfect solution. In this case, just like for choosing the best synchronization scenario, there will be chosen the optimal concept in terms of its implementation; specifically, the activation code seems to be the best compromise between low user complication level and system complexity and cost.