\documentclass[12pt,a4paper,twoside]{article}
\usepackage{a4wide}
\usepackage{t1enc}
\usepackage[polish]{babel}
\usepackage[latin2]{inputenc}
\usepackage{graphicx}
\usepackage{amsfonts}
\usepackage{amsmath}
\usepackage{amsthm}


\RequirePackage[T1]{fontenc}
\RequirePackage{times}
\RequirePackage[latin2]{inputenc}
\RequirePackage[polish]{babel}

\RequirePackage{comment}

\RequirePackage{a4wide}
\RequirePackage{longtable}
\RequirePackage{multicol}
\RequirePackage{url}

\author{Autorzy}
\title{(io08-7X):: Plan testów}


\begin{document}

\maketitle

\newpage

\begin{abstract}
Streszczenie streszczenia.
\end{abstract}

\newpage

\tableofcontents

\newpage

% Note: The following template is provided for use with the
% Rational Unified Process. The following template is provided for use with the
% Rational Unified Process. Text enclosed in square brackets and displayed in
% blue italics (style=InfoBlue) is included to provide guidance to the author and
% should be deleted before publishing the document. A paragraph entered following
% this style will automatically be set to normal (style=Body Text).


\section{Wprowadzenie}

% The introduction of
% the Product Acceptance Plan should provide an overview of the entire
% document. It should include the purpose, scope, definitions, acronyms,
% abbreviations, references, and overview of this Product Acceptance Plan.

\subsection{Cel}

% Specify the purpose
% of this Product Acceptance Plan.

\subsection{Zakres}

% A brief description
% of the scope of this Product Acceptance Plan; what Project(s) it is
% associated with, and anything else that is affected or influenced by this
% document.

\subsection{Definicje}

% This subsection
% should provide the definitions of all terms, acronyms, and abbreviations
% required to properly interpret the Product Acceptance Plan.  This
% information may be provided by reference to the project Glossary.

\subsection{Załączniki}

% This subsection
% should provide a complete list of all documents referenced elsewhere in the Product
% Acceptance Plan.  Each document
% should be identified by title, report number (if applicable), date, and
% publishing organization.  Specify the
% sources from which the references can be obtained. This information may be
% provided by reference to an appendix or to another document.

\subsection{Omówienie reszty dokumentu}

% This subsection
% should describe what the rest of the Product Acceptance Plan contains
% and explain how the document is organized.

\section{Zakres odpowiedzialności}

% Explicitly identify
% the responsibilities of both the customer and the development team in preparing
% and performing the product acceptance activities.

\section{Kroki odbioru projektu}

\subsection{Kryteria odbioru}

% Identify the
% objective criteria for determining acceptability of the deliverable artifacts
% from this project.  These criteria
% should be formally agreed by the customer and the development team.

\subsection{Wstępny audit konfiguracji}

% Identify and list
% here the artifacts that are to be delivered to and accepted by the customer
% resulting from the work on this project.

\subsection{Audit funkcjonalności komponentów}

% For each artifact identified
% in the Physical Configuration Audit, identify the evaluation method(s) and the
% level of detail that will be used to determine if it meets the product
% acceptance criteria.

% Methods can include
% software execution testing, product demonstration, documentation reviews, etc.

\subsection{Plan}

% A schedule
% indicating the start and end times for each of the product acceptance tasks,
% including preparation and set-up activities.

\section{Potrzebne zasoby}

\subsection{Sprzęt}

% For example, hardware items, interfacing equipment,
% firmware items.

\subsection{Oprogramowanie}

% For example, operating systems, compilers,
% test drivers, test data generators.

\subsection{Dokumentacja}

% For example, test documentation, technical
% references.

\subsection{Personel}

% For example, development team members,
% customer representatives, third-party party authorities.

\subsection{Dane testowe}

% For example, size, type, and composition of
% data to support acceptance tests.

\subsection{Inne zapotrzebowania}

% For example, special equipment.

\section{Rozpoznawanie problemów i reakcja na problemy}

% This section
% describes the procedures for reporting and handling problems identified during
% the Product Acceptance activities. 
% Usually this is addressed by enclosing the Problem Resolution Plan
% artifact by reference.

\section{Środowisko odbioru produktu}

% Describe the plans
% for setting up the product acceptance environment.

\section{Wymagane kroki kontroli}

% Based on the
% Functional Configuration Audit description, identify each individual artifact
% evaluation that will be carried out. 
% For each one, list the type of evaluation (test, review etc), and its
% objective(s)

% Note: A Test Case
% artifact will be prepared for each test identified here.

\section{Narzędzia, technologia, metodologia}

% A list of any
% specific tools, techniques, and methodologies that are to be used when
% performing the Product Acceptance activities.

\end{document}

