\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 :: Business Use-Case Specification}


\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.  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 Business Use-Case Specification should provide an
% overview of the entire document. It should include the purpose, scope,
% definitions, acronyms, abbreviations, references, and overview of this
% Business Use-Case Specification.  Note: If you are not using Requisite Pro
% then this document template should be used to capture the actual Business Use
% Case including the workflow, special requirements, and performance goals of
% the Business Use Case.  This file should be linked to the corresponding
% business use case in the Rose model.  If you use SoDA then this document is
% used as input to the business use-case report that combines this content with
% use-case diagrams from Rose.

\subsection{Cel}

% Specify the purpose of this Business Use-Case Specification

\subsection{Zakres}

% A brief description of the scope of this Business Use-Case Specification;
% what Use-Case model(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 Business Use-Case
% Specification.  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 Business Use-Case Specification.  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 Business Use-Case
% Specification contains and explain how the document is organized.

\section{<Nazwa use-case'a>}

\subsection{Krótki opis}

% The description should briefly convey the role and purpose of the business
% use case.  A single paragraph should suffice for this description.

\subsection{Cele}

% A specification of the measurable goals or objectives of the business use
% case.

\subsection{Wydajność}

% A specification of the metrics relevant to the business use case and a
% definition of the goals of using those metrics.

\subsubsection{<name of performance goal>}

% A brief description of the performance goal.

\subsection{Warunki wstępne}

\begin{itemize}
\item
\end{itemize}

\subsection{Czynności}

% A textual description of the workflow the business use case represents. The
% workflow should describe what the business does to deliver value to a
% business actor, not how the business solves its problems.  Only one level of
% workflow steps is indicated in the subsections below, but you may add more
% levels if necessary.

\subsubsection{Czynności podstawowe}

% A brief description of the workflow step.

\begin{enumerate}
\item
\end{enumerate}

\subsubsection{Czynności alternatywne}

% A brief description of the workflow step.

\begin{enumerate}
\item
\end{enumerate}

\subsection{Kategoria}

% Whether the business use case is of the category core, supporting, or
% management.

\subsection{Ryzyko}

% A specification of the risks of executing and/or implementing the business
% use case.

\subsection{Możliwe usprawnienia}

% A description of the estimated improvement potential of the business use
% case.

\subsection{Właściciel}

% A definition of who the owner of the business process is, the person who
% manages the changes and plans for changes.

\subsection{Inne wymagania}

% The special requirements of the business use case are included here. These
% are requirements not covered by the workflow as it has been described in the
% sections above.

\subsubsection{<name of special requirement>}

% A brief description of the special requirement.

\subsection{Możliwe rozwinięcia}

% Extension points of the business use case.

\subsection{<name of extension point>}

% Definition of the location of the extension point in the flow of events.

\section{Historia zmian}

\begin{verbatim}

$Log: $

\end{verbatim}

\end{document}


