\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={Improving Software Quality Attributes of PS using Stylecop},
 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{2013-01-15 (revised: 15 January 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-01-15}
\title{Improving Software Quality Attributes of PS using Stylecop}
\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]{Rajesh  Kulkarni}

             \author[2]{  P.Padmanabham}

             \author[3]{  M.S.Namose}

             \affil[1]{  BSCOER Engg. College affiliated to Pune University, India}

\renewcommand\Authands{ and }

\date{\small \em Received: 10 December 2012 Accepted: 4 January 2013 Published: 15 January 2013}

\maketitle


\begin{abstract}
        


Software product quality improvement is a desired attribute and a strenuous effort is required to achieve that. Static Code Analysis (SCA) is used to find coding bugs. Stylecop is an SCA tool from Microsoft. In this paper SCA and stylecop usages are discussed. Also a comparison of Software Testing, software Metrics & Source Code Analysis (SCA) is done. Product PS designed by author1 and author2 is introduced. PS application is analyzed using static SCA tool Stylecop. After analysis recommendations were applied to PS. The results showed improved software quality attributes.

\end{abstract}


\keywords{SCA, PS, stylecop, software quality.}

\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[{Introduction}]{Introduction}\par
oftware quality improvement is of foremost importance for product success. Techniques such as software testing, Usability testing and source code analysis are prevalent. Also secure programming to tackle code-based vulnerabilities is in vogue nowadays \hyperref[b1]{[2]}. Our work focuses on evaluation of PS product designed by author 1 and author 2 using static source code Analysis (SCA) tool  {\ref Stylecop.} In this paper overview of SCA, comparison of SCA with software testing and software metrics \hyperref[b0]{[1]} is done. Also introduction to PS product \hyperref[b6]{[8]},  {\ref [9]} and Stylecop \hyperref[b0]{[1]}, \hyperref[b4]{[5]}, \hyperref[b5]{[6]},  {\ref [7]} is given. The organization of the paper is as followed: section I which is the current section introduces SCA, section II distinguishes SCA with testing and metrics along with that evaluation criteria of SCA tool selection is also done, section III gives the introduction to PS, section IV details stylecop tool, section V discusses evaluation of PS product using stylecop and section VI lists results of analysis of PS using stylecop. The static analysis approach is meant to review the source code, checking the compliance of specific rules, usage of arguments and so forth. Static code analysis is the analysis of computer software which is performed without the actual execution of the programs built from that software, as opposite of dynamic analysis (testing software by executing programs) \hyperref[b5]{[6]}. The output of static analysis tools still requires human evaluation \hyperref[b5]{[6]}.\par
The BCS SIGIST defines static analysis of source code as the "analysis of a program carried out without executing the program" \hyperref[b1]{[2]}. This definition emphasizes the contrast to dynamic analysis, where the behavior of program is observed while it is executed. Static analysis can be used for varied purposes such as software quality improvement, code optimizations and identifying vulnerabilities \hyperref[b1]{[2]}. Manual reviewing of code is a form of static code analysis, it is a time consuming process and it should be done at the very early stage of design \hyperref[b5]{[6]}. Manual review kind of static code analysis can be either a self-review or a third party review \hyperref[b5]{[6]}.II. 
\section[{SCA vs Testing and Metric}]{SCA vs Testing and Metric}\par
Software Testing is the process of executing a program or system with the intent of finding errors  {\ref [10]}. Software testing tools are programs that are trying to find errors, defects, bugs, failures, etc in the software \hyperref[b0]{[1]}. Test cases are generated and results are compared with expected results. Nonconformance leads to debugging the program. Correctness is the minimum requirement of software, the essential purpose of testing. Correctness testing will need some type of oracle, to tell the right behavior from the wrong one  {\ref [10]}. While according to [11] software metrics is defined as the continuous application of measurement-based techniques to the software development process and its products to supply meaningful and timely management information, together with the use of those techniques to improve that process and its products. Software metrics are programs or tools that collect information about the software regarding its characteristics for example metrics such as Lines Of Code (LOC), size, complexity, Number of functions per class, etc \hyperref[b0]{[1]}. While the high level goal of software metrics is similar to software testing in improving the overall quality of the software, there are several differences between software testing and metric tools \hyperref[b0]{[1]}. Software metrics are usually collected after testing and after making sure that program is free from errors (at least syntactic errors) \hyperref[b0]{[1]}. 
\section[{III.}]{III.} 
\section[{PS Product}]{PS Product}\par
The PS (personal Secretary) web application is targeted for online users who has many email ids, other site ids, does online banking and online transactions. Presently he stores his email ids and passwords, ATM pins as emails or in written form on a paper which he keeps in his wallet. His constant fear is if he loses his wallet there may be misuse of his ids and pins. He also faces the problem of recollecting the ids, passwords Year complete solutions for the above vulnerabilities through a single get way using the internet as the sole medium. It will enable the online user to retrieve ids, passwords and ATM pin numbers at will 24/7. The administration module will enable a user to allow addition, deletion and updating of ids, passwords and documents.\par
The target user also requires documents frequently such as Copies of mark memos, certificates and updated resume for applying for jobs. Copies of documents such as form 16s, salary slips, ids for loan application. Insurance policy numbers PS was designed using TEIM(The Evolved Integration Model) of software engineering and human computer Engineering proposed by us \hyperref[b6]{[8]}.This paper is a continuation of efforts for validating the utility of TEIM and acceptance from peers [9].  
\section[{Stylecop}]{Stylecop}\par
StyleCop is an open source SCA tool from Microsoft that checks. NET code for conformance of several design guidelines defined based on Microsoft's .NET Framework \hyperref[b0]{[1]}[7]. StyleCop evaluates the style of C\# source code in order to enforce both a set of style and consistency rules. Style guidelines are rules that specify how source code should be formatted and dictate whether spaces or tabs should be used for indentation and the format of for loops, if statements and other constructs \hyperref[b4]{[5]}. The goal is to define guidelines to enforce consistent style and formatting and help developers avoid common pitfalls and mistakes. StyleCop contributes to this maintainability by encouraging consistency of style, which in turn makes it easier for developers to pick up existing code and work with it productively, and by encouraging plenty of documentation for future developers to read thereby improving the long term maintainability of the source. \hyperref[b5]{[6]} Historically, different development groups have used drastically different coding styles. Many teams have used inconsistent coding styles within a single product or even a single source file. StyleCop was originally written to provide a simple and efficient way to enforce a common coding style for C\# code throughout Microsoft. Over time, StyleCop evolved to include new rules that go beyond style checks. \hyperref[b5]{[6]} V.\par
Evaluation of PS using Stylecop PS application was developed using .NET. Stylecop was configured with .NET during installation. Each of the file of PS was evaluated using Stylecop. Stylecop issued warnings and errors in the following categories: Naming, maintainability, documentation, ordering, readability, spacing, and layout  {\ref [1] [7]}. Except maintainability all the categories belong to refactoring. Refactoring indicates cosmetic improvement in software without changing its functionalities \hyperref[b0]{[1]}.Priority numbers assigned are based on the importance and impact of its program \hyperref[b0]{[1]}.Some sample warnings are shown in TABLE  {\ref I}. PS Screenshots showing Evaluation by Stylecop are shown in in Figure \hyperref[fig_3]{2} and Figure 3. After evaluating PS with stylecop manual corrections were made in the code of PS. These corrections led to improvement in software quality attributes of PS as shown in TABLE  {\ref II}.    
\section[{Conclusion}]{Conclusion}\par
In this paper we analyzed product PS designed by author1 and author2 using stylecop-a static source code analysis (SCA) tool. Manual corrections in code of PS as per recommendations of stylecop were done. The results showed  Manual review was found to be a tedious process in terms of time and planning. As our product is being targeted as a client-server program security was not an issue and so our focus was less on security and more on styling and usability. 
\section[{Global}]{Global}\par
VII.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_1}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-3.png}
\caption{\label{fig_2}Improving}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-4.png}
\caption{\label{fig_3}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-5.png}
\caption{\label{fig_4}}\end{figure}
  \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.6073322932917317\textwidth}P{0.09812792511700467\textwidth}P{0.019890795631825272\textwidth}P{0.08884555382215288\textwidth}P{0.022542901716068642\textwidth}P{0.01326053042121685\textwidth}}
Warnings\tabcellsep Category\tabcellsep Priority\tabcellsep File name\tabcellsep Line\tabcellsep Col\\
The field must have an access\tabcellsep Maintainability\tabcellsep 1\tabcellsep DAL.cs\tabcellsep 16\tabcellsep 1\\
modifier\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
names must start with a lower-\tabcellsep Naming\tabcellsep 2\tabcellsep DAL.cs\tabcellsep 16\tabcellsep 1\\
case letter\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
The call to\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
Initialize\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
Component must\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
begin with the 'this.' prefix to\tabcellsep Readability\tabcellsep 3\tabcellsep Login.cs\tabcellsep 19\tabcellsep 1\\
indicate that the\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
item is a\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
member of the\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
class.\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
The file has no\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
header, the\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
header Xml is invalid, or the\tabcellsep Spacing\tabcellsep 4\tabcellsep Login.cs\tabcellsep 1\tabcellsep 1\\
header is not\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
located at the top\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
of the file.\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
The field must have a documentation\tabcellsep Ordering\tabcellsep 5\tabcellsep Login.design er.cs\tabcellsep 37\tabcellsep 1\\
header.\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
The body of the\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
if statement must\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
be wrapped in opening and\tabcellsep Layout\tabcellsep 6\tabcellsep DAL.cs\tabcellsep 32\tabcellsep 1\\
closing curly\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
brackets.\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
The class must\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \\
have a documentation\tabcellsep Documentation\tabcellsep 7\tabcellsep DAL.cs\tabcellsep 13\tabcellsep 1\\
header.\tabcellsep \tabcellsep \tabcellsep \tabcellsep \tabcellsep \end{longtable} \par
 
\caption{\label{tab_0}C}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{}
\end{longtable} \par
 
\caption{\label{tab_1}Table 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2} \par 
\begin{longtable}{P{0.08292682926829269\textwidth}P{0.39390243902439026\textwidth}P{0.37317073170731707\textwidth}}
Tool\tabcellsep Increase complexity\tabcellsep Increase usability\end{longtable} \par
 
\caption{\label{tab_2}Table 2 :}\end{figure}
 			\footnote{© 2013 Global Journals Inc. (US)} 		 		\backmatter   			 
\subsection[{Acknowledgements}]{Acknowledgements}\par
We sincerely thank staff and students of ME program of BSCOER College, Narhe, Pune, India for helping us in designing PS, installation of stylecop and analyzing PS using stylecop. 			  			 			 			  				\begin{bibitemlist}{1}
\bibitem[Gomes et al.]{b4}\label{b4} 	 		\textit{An overview on the Static Code Analysis approach in Software Development},  		 			Ivo Gomes 		,  		 			Pedro Morgado 		,  		 			Tiago Gomes 		,  		 			Rodrigo Moreira 		.  		 	 
\bibitem[Mic rosoft StyleCop ()]{b3}\label{b3} 	 		 \url{http://code.msdn.microsoft.com/sourceanalysis}  		\textit{Mic rosoft StyleCop},  				2008.  	 
\bibitem[Black (2007)]{b1}\label{b1} 	 		‘SAMATE and Evaluating Static Analysis Tools’.  		 			Paul E Black 		.  	 	 		\textit{ADA User Journal}  		September 2007. 28  (3)  p. .  	 
\bibitem[Zoubi et al.]{b0}\label{b0} 	 		\textit{Scanstud: A Methodology for Systematic, Finegrained Evaluation of Static Analysis Tools},  		 			Q Zoubi 		,  		 			I Alsmadi 		,  		 			B Abul-Huda 		.  		 \xref{http://dx.doi.org/Identifier:10.1109/CITS.2012.6220379PublicationYear:2012}{Identifier:10.1109/CITS.2012.6220379PublicationYear:2012}.  		 Identifier:10.1109/ICSTW.2011.32.  		p. .  	 	 (Digital Object) 	 (Study The Impact of Improving Source Code on Software Metrics. Publication Year: 2011, Page(s) 
\bibitem[Pressman ()]{b2}\label{b2} 	 		\textit{Software Engineering: A Practitioner's Approach},  		 			R Pressman 		.  		2005. McGraw-Hill.  	 
\bibitem[Kulkarni and Padmanabham ()]{b6}\label{b6} 	 		‘TEIM-The Evolved Integrated Model of SE and HCI’.  		 			R Kulkarni 		,  		 			P Padmanabham 		.  	 	 		\textit{Validating Utility of TEIM: A Comparative Analysis},  				 			Moritz Martin Johns,  			. R Jodeit 7,  			P Kulkarni,  			Padmanabham 		 (ed.)  		2012. 2 p. .  	 	 (IJACSA, To be Page(s) 
\bibitem[Stylecop and Codeplex (2011)]{b5}\label{b5} 	 		\textit{WebsiteAvailable at:http://style cop},  		 			Stylecop 		,  		 			Codeplex 		.  		October 8, 2011.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
