\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Software as a Service Model},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2011-12-29 (revised: 29 December 2011)}
\def\TheID{\makeatother }
\def\TheDate{2011-12-29}
\title{Software as a Service Model}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Dr. S.R.  Suresh}

             \affil[1]{  BHARATH UNIVERSITY}

\renewcommand\Authands{ and }

\date{\small \em Received: 24 November 2011 Accepted: 14 December 2011 Published: 29 December 2011}

\maketitle


\begin{abstract}
        


The  prime  objective  of  various  Software development  methodologies  is  to  formulate  a  well  defined framework  to  develop  the  intended  software  product.  The framework should address   various  levels  in  the development cycle.  The  intended  software  product  should  be  developed with  limited slack  time and with high degree of quality within various  levels,  without  draining  the  resources  available  at hand. This paper addresses a new method to develop quality oriented  software  and  without  compromising  the  budget parameter.   Quality is a major factor defining the demand for the product,  customers  look  for quality at a demanding cost. So designing software at a reasonable cost with a high  degree of quality  will  always  conquer  the  software  market.  The  term quality  in software development  sector  is  to design a system to address the requirements of the customer and the needs of the user.  Some software fails during the implementation phase due  to  the  lack of  information  from  the users.  In  usual cases the buyer might not be  the user. A clear documentation must be prepared by combining  the  requirements of  the customer with  the  needs  of  the  customer.  The  requirements  of  the customer  usually address the logical and business parts of the software. But the needs for the user may vary from  the color of the frame to the shortcut keys.   

\end{abstract}


\keywords{Quality, Software, Cost, Framework, SaS, Service}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Software as a Service Model}]{Software as a Service Model}\par
Dr. S.R. Suresh A Abstract -The prime objective of various Software development methodologies is to formulate a well defined framework to develop the intended software product. The framework should address various levels in the development cycle. The intended software product should be developed with limited slack time and with high degree of quality within various levels, without draining the resources available at hand. This paper addresses a new method to develop quality oriented software and without compromising the budget parameter.\par
Quality is a major factor defining the demand for the product, customers look for quality at a demanding cost. So designing software at a reasonable cost with a high degree of quality will always conquer the software market. The term quality in software development sector is to design a system to address the requirements of the customer and the needs of the user. Some software fails during the implementation phase due to the lack of information from the users. In usual cases the buyer might not be the user. A clear documentation must be prepared by combining the requirements of the customer with the needs of the customer. The requirements of the customer usually address the logical and business parts of the software. But the needs for the user may vary from the color of the frame to the shortcut keys.\par
Keywords: Quality, Software, Cost, Framework, SaS, Service his paper presents a method where we provide software as a service rather than product. This era has made more advancement in the area of information technology and communication systems. Statistics show about 80\% of the world is connected through internet. In this modern age, we adapting to the new system of SaaS (Software as Service) technology is not an issue. SaaS provides a constant improvement in quality through various quality appraisal systems thus providing software with high degree of quality in a limited cost model. Here we address the model through which how this system can be implemented efficiently. The core objective of designing a software system is to customize the operations of end users in achieving their core-target in minimum usage of recourses. The core target varies based on the assignment designated to the end-user.\par
The banker who uses a banking application may use a software system to register all the transactions between clients and the bank, an application programmer uses a compiler for creating new software applications. Well performing software uses minimal recourses to reach the target with high degree of precision.\par
In this paper, a new method through which we can achieve a best performing and highly reliable software through the concept of SaaS (Software as a Service) Modeling is briefed. This paper provides an insight of what a SaaS model is and the advantages of using this model in developing this kind of software. SaaS model provides a structural approach in designing a reliable software application. IEEE 610.12-1990 defines reliability as "The ability of a system or component to perform its required functions under stated conditions for a specified period of time. SaaS model provides a highly reliable system and with a longer lifespan since, the development and up gradation process is a continuous procedure through the concept of Quality through Intelligence (QTI).\par
Various software development framework models have been framed for designing reliable software at a competitive time and with limited recourses. The paper presents here an evolving system that has been adopted in major technological giants to enhance their service to their clients. SaaS concept was published in February 2001 by the Software \& Information Industry's (SIIA) eBusiness Division.\par
The SaaS model provides a waypoint to design a software application through the concept of software as a service. SaaS concept is widely accepted concept and various design models are used to provide a solution for the identified service. By adapting SaaS model the system become more reliable than that of other building models.\par
The core concept to this architecture is the "Quality Through Intelligence". This is a very special phase introduced in this model with gives a more advantageous background than that of the other models.\par
Since quality has a broad range of identification with respect to the end user, this system is very suited for creating software as service, since this provides an analyzing environment for continual quality improvement at various levels of usage.\par
The primary objective of SaaS model is to design a feasible environment to develop software which meets the phrase "Give what the Customer Wants".\par
Quality: To achieve this objective a new environment is designed parallel to the implementation T and Maintenance phase, "Quality through Intelligence", this phase is a specialized zone where we design a system to learn the user. Automatic feedback is generated based on usage of the end user. Various parameters are analyzed and the system generates a feedback file which is then compared with the other files generated by other users and the resulting information is used to generate useful code to improve the operational quality of the system.\par
Budget : Since this an automated feedback system, no specialized research and development team is required after implementation. This reduces the budget parameter to a large extent, since almost 40\% of the allotted budget is spent on research and development\par
The various stages of SaaS model are market research, problem definition, implementation plan, QA feedback and testing, customer feedback and Quality through intelligence.\par
This model introduces a specialized phase "Quality through Intelligence". The other phases are similar to that of the conventional software development scenario with slight modification the procedural structure. The various stages and the control flow are presented in Fig1. It is a very important component of business strategy. Market research involves preparing a list of services that are being utilized by various organizations and the depth of service provided is estimated through various management tools. Services involve accounting service, logistic service, HR service, etc.. The depth of service is the degree to which the user is able to utilize the service and decide upon its output. Tabulation is prepared based upon the service's degree of intensity. Benchmarking is also done with leading service providers of similar service. Upon deriving to a service criterion the system moves to the next stage of problem definition. 
\section[{b) Problem Definition}]{b) Problem Definition}\par
This is the stage where the system starts getting into shape. After analyzing various possibilities in the previous stage of market research, the problem is put forth for a proper and structural definition. The identified service through the market research is studied and analyzed the following components are defined.\par
1) Functionality: What the service does 2) People: Trained human resource required for designing the service. 3) Systems: higher and lower level system goals, interfaces 4) Components -various parts and purposes involved in formulating the service.\par
After structurally formulating the problem for the defined components, the system moves on to the phase of implementation plan. 
\section[{c) Implementation Plan Fig 2 : Time line of SaaS model}]{c) Implementation Plan Fig 2 : Time line of SaaS model}\par
The time line and the hierarchy of the various stages of SaaS model is depicted in Fig.  {\ref 2}. A road map for achieving the desired goal is laid prior to the actual implementation procedure. The road map shows the various milestones and resource utilization as per the requirement specified in the problem definition. Slack time between levels is also specified in the current zone.\par
The milestones denote the end of a particular phase and the beginning of a new phase. The arrow indicates a continuous process. 
\section[{d) Implementation Procedure}]{d) Implementation Procedure}\par
Once the road map for implementation is clearly laid out based upon the timeline required for each phase, the control is transferred to the implementation procedure. This phase of the SaaS model defines how the total service system is to be integrated into one common service providing unit.\par
The implementation plan provides documents about the services to be provided and the resources that would be required during the implementation sequence. The implementation documents provide details about the development and integration procedure for implementing the service. It consists of the business logic, class structures, control flows, Use Cases and other details required for the actual development of the system.\par
The details prepared in the implementation procedure document are utilized during the coding and testing sequences. Without proper documentation of implementation procedure further quality improvement procedures based on the inputs from the quality through intelligence will not be viable in this model. The whole system should be designed to function and learn at the same time. 
\section[{e) Code Design}]{e) Code Design}\par
The coding phase encompasses the core part of designing the operational part of the system. Initially a desired language is chosen from the broad array of available programming languages. Selection of a programming language is a very essential part in designing a system. Since there is no universally superior language, each programming language has to be analyzed for its strengths and weaknesses. Selection of the programming language has a long term implications including those of the business capability, cost and technology. Therefore selection of programming language is a management cum technological decision.\par
Various dimensions for selection of a programming language are capability, productivity, ramp up, extraneous factors and cost. Parallel to the coding procedure the testing teem start their testing work by preparing the test documents for the opted service. Since error free and good quality software service always takes a lead in the highly competitive software market, it is always better to have a good testing document prepared ahead of the testing procedure. To be useful, software testing procedures must encompass all aspects of the software testing process. The steps involved in testing procedures are described in Fig. \hyperref[fig_2]{3}.\par
It's vitally important that the procedures define the people who will be involved in the testing process, the skill set of each team member, and their availability for the duration of the testing cycle. For the software cycle to remain on track, the software testing procedure must also delineate a carved-in-stone testing schedule including dates of important milestones.\par
Software testing is a critical component of the software development cycle. And software testing procedures are critical to the success of the testing phase. Software remains in a perpetual state of change which is why software testing, whether manual or automated, is so vital to a software product's success. Typically, 30 -40\% of the software engineers employed at larger software development companies work on software testing and each of these individuals needs to understand his or her role in this ongoing process. The quality assurance teem keep in track the progress of the development process with accordance to the study conducted during the market research phase. Since the quality parameter varies based on the various levels of users of the service, a clear document is prepared as to monitor that the software service meets the demands without compromising the feasibility of the system.\par
The following are factors are measures while testing the quality of the system. \hyperref[b0]{1)} Correctness: extent to which a program satisfies its specification and fulfills the client's objective.\par
2) Reliability: extent to which a program is supposed to perform its function with the required precision.\par
3) Efficiency: amount of computing and code required by a program to perform its function.\par
4) Integrity: extent to which access to software and data is denied to unauthorized users. 5) Usability: labor required to understand, operate, prepare input and interpret output of a program 6) Maintainability: effort required to locate and fix an error in a program. \hyperref[b5]{7)} Flexibility: effort needed to modify an operational program. 8) Testability: effort required to test the programs for their functionality. 9) Portability: effort required to run the program from one platform to other or to different hardware. 10) Reusability: extent to which the program or its parts can be used as building blocks or as prototypes for other programs. 11) Interoperability: effort required to couple one system to another g) Customer Feedback\par
The goal of designing software service through SaaS model is to achieve a high degree of customer satisfaction. This can be achieved by understanding the customer's needs which can be done through customer feedback system. The feedback from the customers allows the quality assurance team to provide the development team with new solutions to be provided by the services so as to boost the market capability of the software service.\par
Providing customers with free trail service packages will boost the number of feedbacks, of which the quality team can verify the quality by analyzing the inputs obtained from the customers. By fine tuning the services based upon the customer inputs, we can further enchase the market share of our service software.\par
Customer feedbacks increases the market potential of the service, because of the useful information provided by the customers the development team know what the customer want and the service is designed to the needs of various levels of service users.\par
Customer feedback is obtained initially during the release of the alpha version of the software. Since the probability of getting errors is high, usually the feedback is obtained from in-house consultants or experts. Once the beta version is released after the fine tuning of the system, it is delivered to selected community of users for feedback. These stage by stage testing results in bringing more positive feedback stating about the additional features required rather than faults found in the service. After completion of testing of beta version, the final service is released for general usage of customers.\par
Since we design service oriented software a constant update must be kept in recent advancement in the services. This can either be obtained though customer feedback or through in-house domain experts. The service is modified based upon the inputs obtained from analyzing the customer feedback and expert opinion. 
\section[{h) Quality through Intelligence}]{h) Quality through Intelligence}\par
This is a phase unique to SaaS model. This is phase where we design a intelligence system which learns the operations of the system form the users end. This is similar to that of business intelligence. Based upon the customer feedbacks and overall functionality of the system a special module is designed which runs in parallel to service learning the operational mode of various functions. Based on the reports generated by the module the quality assurance team generates solution structure for the desired requirement specified by the learner module. Various types of specifications provided by the learner module are the time reduction specification, entry reduction specification, frequently used specification and user environment specification. 1) Time Reduction Specification: this functionality learns the time taken to complete each functionality available in the service for various users and identifies the minimum time taken to complete an operation. Based upon the identification it identifies the operational mode of that particular user and reports it to the quality assurance team.\par
2) Entry Reduction Specification: this functionality learns the entry structure and identifies the correlation between each entry and when a similar entry is encountered it automatically completes the form with minimal entry time.\par
3) Frequently used: this functionality identifies frequently used functions and creates a short in the main screen to enable quick access to the user. 4) User Environment: this functionality modifies the working environment based on certain parameters like time, gender etc.. this enables the user to work with ease. SaaS is an emerging concept which is being adopted by numerous software firms to hold their ground in this highly customer oriented market. SaaS model will definitely bring out a software system with high degree of quality without compromising the cost factor, since its lower levels of production and the specialized learning module in the Quality through Learning concentrates on delivering a customer oriented quality service.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Fig 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-3.png}
\caption{\label{fig_1}1 )}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Fig 3 :}\end{figure}
 			\footnote{December} 			\footnote{( J ) 2011 December} 		 		\backmatter  			 
\subsection[{Global}]{Global}			 			  				\begin{bibitemlist}{1}
\bibitem[Marks and Bell]{b4}\label{b4} 	 		\textit{},  		 			Eric A Marks 		,  		 			Michael Bell 		.  	 	 		\textit{Service-Oriented Architecture (SOA)}  		 	 
\bibitem[Mcconnell (2009)]{b3}\label{b3} 	 		\textit{10 most powerful ideas in software engineering},  		 			S Mcconnell 		.  		May 2009. Construx, WA.  	 
\bibitem[Rodriguez-Martinez et al. (2009)]{b1}\label{b1} 	 		‘A Descriptive/Comparative Study of the Evolution of Process Models of Software Development Life Cycles (PM-SDLCs)’.  		 			L C Rodriguez-Martinez 		,  		 			M Mora 		,  		 			F Alvarez 		.  	 	 		\textit{Comput. Sci}  		Sept. 2009.  		 			Univ. Autonoma de 		 	 
\bibitem[Xu (2007)]{b0}\label{b0} 	 		‘A Service Oriented Model for Role Based Global Cooperative Software Development’.  		 			Bin Xu 		.  	 	 		\textit{Zhejiang Gongshang Univ}  		Nov. 2007.  	 
\bibitem[Melvin and Greer]{b5}\label{b5} 	 		 			B Melvin 		,  		 			GreerJr 		.  		\textit{Software as a Service Inflection Point: Using Cloud Computing to Achieve Business Agility},  				 	 
\bibitem[Huo Verner et al. (2004)]{b2}\label{b2} 	 		‘Software quality and agile methods’.  		 			Ming Huo Verner 		,  		 			J Liming Zhu 		,  		 			M A Babar 		.  	 	 		\textit{Nat. ICT Australia Ltd}  		Sept. 2004.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
