Posts tagged ‘Babok’

Creating an Overview of BABOK Knowledge Areas with LaTeX

Last week I attended a CBAP preparation course (materials from http://www.watermarklearning.com/cbap, held by http://www.masventa.eu). To prepare myself for the exam I created an overview of all knowledge areas using TikZ’s magnificient graphics functions. Together with a little ifdraft magic I got a nice file.

Area_Summary_landscape (PDF, DIN A4 landscape)

\documentclass[fontsize=10pt]{scrartcl}
\usepackage[a4paper,landscape,left=1cm,right=1cm,top=1cm,bottom=1cm]{geometry}
 
\usepackage[]{ifdraft}
\usepackage[]{attachfile}
\usepackage[]{eso-pic}
 
\usepackage[english]{babel}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
 
\renewcommand{\familydefault}{\sfdefault}
\RequirePackage[scaled=0.9]{helvet}
\usepackage{tikz}
\usepackage[right]{showlabels}
\usetikzlibrary{positioning}
\pagestyle{empty}
 
\usepackage{xcolor}
 
\ifdraft{
\definecolor{mycol}{RGB}{255,255,255}
}{%
\definecolor{mycol}{RGB}{0,0,0}
}
 
\usepackage{hyperref}
\usepackage[]{url}
 
\hypersetup{% 
  pdftitle={CBAP Knowledge Areas},
  pdfauthor={Uwe Ziegenhagen, uwe.ziegenhagen@db.com	},
  pdfsubject={Babok Knowledge Areas},
  pdfkeywords={Babok, CBAP, Knowledge Areas}
}
 
\newcommand{\file}[1]{\textattachfile{#1}{\textcolor{blue}{\LaTeX\ Sourcecode}}}
 
\begin{document}  
 
\AddToShipoutPictureFG*{
  \put(35,25){\footnotesize Uwe Ziegenhagen, uwe.ziegenhagen@db.com, \file{\jobname.tex}	
}
}
 
\begin{center}
\begin{tikzpicture}
[
    x=40mm,y=25mm,
    mybox/.style={rectangle,rounded corners,xshift=1cm,yshift=1cm,minimum width=35mm, minimum height=22.5mm},
    topline/.style={mybox,mycol,align=center,draw=red,very thick,font=\bfseries},
    botline/.style={mybox,mycol,align=center,draw=orange,very thick,font=\bfseries},
    yelline/.style={mybox,mycol,align=center,draw=cyan,very thick,font=\bfseries},
    pinkline/.style={mybox,mycol,align=center,draw=violet,very thick,font=\bfseries}
]
\node at (0,0) [topline] {Business Analysis \\ Planning  \& \\ Monitoring};
\node at (1,0) [topline] {Elicitation};
\node at (2,0) [topline] {Requirements \\ Management \&  \\ Communications};
\node at (3,0) [topline] {Enterprise Analysis};
\node at (4,0) [topline] {Requirements \\ Analysis};
\node at (5,0) [topline] {Solution Assessment \\ \& Validation};
\node at (6,0) [topline] {Underlying  \\ Competencies};
 
\node at (0,-1) [botline] {Plan BA Approach};
\node at (0,-2) [botline] {Conduct \\ Stakeholder \\ Analysis};
\node at (0,-3) [botline] {Plan BA Activities};
\node at (0,-4) [botline] {Plan BA \\ Communication};
\node at (0,-5) [botline] {Plan Requirements \\ Management \\ Process};
\node at (0,-6) [botline] {Manage BA \\ Performance};
 
\node at (1,-1) [yelline] {Prepare for \\ Elicitation};
\node at (1,-2) [yelline] {Conduct \\ Elicitation \\ Activity};
\node at (1,-3) [yelline] {Document \\ Elicitation \\ Results};
\node at (1,-4) [yelline] {Confirm \\ Elicitation \\ Results};
 
\node at (2,-1) [botline] {Manage Solution \\ Scope \& \\ Requirements};
\node at (2,-2) [botline] {Manage \\ Requirements \\ Traceability};
\node at (2,-3) [botline] {Maintain \\ Requirements \\ for Re-Use};
\node at (2,-4) [botline] {Prepare \\ Requirements \\ Package};
\node at (2,-5) [botline] {Communicate \\ Requirements};
 
\node at (3,-1) [yelline] {Define \\ Business \\ Need};
\node at (3,-2) [yelline] {Assess \\ Capability \\ Gaps};
\node at (3,-3) [yelline] {Determine \\ Solution \\ Approach};
\node at (3,-4) [yelline] {Define \\ Solution \\ Scope};
\node at (3,-5) [yelline] {Define \\ Business \\ Case};
 
\node at (4,-1) [botline] {Prioritize \\ Requirements};
\node at (4,-2) [botline] {Organize \\ Requirements};
\node at (4,-3) [botline] {Specify \& \\ Model \\ Requirements};
\node at (4,-4) [botline] {Define \\ Assumption \& \\ Constraints};
\node at (4,-5) [botline] {Verify \\ Requirements };
\node at (4,-6) [botline] {Validate \\ Requirements};
 
\node at (5,-1) [yelline] {Assess \\ Proposed \\ Solution};
\node at (5,-2) [yelline] {Allocate \\ Requirements};
\node at (5,-3) [yelline] {Assess \\ Organizational \\ Readiness};
\node at (5,-4) [yelline] {Define \\ Transition \\ Requirements};
\node at (5,-5) [yelline] {Validate \\ Solution};
\node at (5,-6) [yelline] {Evaluate \\ Solution \\ Performance};
 
\node at (6,-1) [pinkline] {Analytical \\ Thinking \& Problem \\ Solving };
\node at (6,-2) [pinkline] {Behavioral \\ Characteristics};
\node at (6,-3) [pinkline] {Business \\ Knowledge};
\node at (6,-4) [pinkline] {Communication \\ Skills};
\node at (6,-5) [pinkline] {Interaction \\ Skills};
\node at (6,-6) [pinkline] {Software \\ Applications};
\end{tikzpicture}
\end{center}
 
\ifdraft{%
}{%
\definecolor{mycol}{RGB}{255,255,255}
\begin{center}
\begin{tikzpicture}
[
    x=40mm,y=25mm,
    mybox/.style={rectangle,rounded corners,xshift=1cm,yshift=1cm,minimum width=35mm, minimum height=22.5mm},
    topline/.style={mybox,mycol,align=center,draw=red,very thick,font=\bfseries},
    botline/.style={mybox,mycol,align=center,draw=orange,very thick,font=\bfseries},
    yelline/.style={mybox,mycol,align=center,draw=cyan,very thick,font=\bfseries},
    pinkline/.style={mybox,mycol,align=center,draw=violet,very thick,font=\bfseries}
]
\node at (0,0) [topline] {Business Analysis \\ Planning  \& \\ Monitoring};
\node at (1,0) [topline] {Elicitation};
\node at (2,0) [topline] {Requirements \\ Management \&  \\ Communications};
\node at (3,0) [topline] {Enterprise Analysis};
\node at (4,0) [topline] {Requirements \\ Analysis};
\node at (5,0) [topline] {Solution Assessment \\ \& Validation};
\node at (6,0) [topline] {Underlying  \\ Competencies};
 
\node at (0,-1) [botline] {Plan BA Approach};
\node at (0,-2) [botline] {Conduct \\ Stakeholder \\ Analysis};
\node at (0,-3) [botline] {Plan BA Activities};
\node at (0,-4) [botline] {Plan BA \\ Communication};
\node at (0,-5) [botline] {Plan Requirements \\ Management \\ Process};
\node at (0,-6) [botline] {Manage BA \\ Performance};
 
\node at (1,-1) [yelline] {Prepare for \\ Elicitation};
\node at (1,-2) [yelline] {Conduct \\ Elicitation \\ Activity};
\node at (1,-3) [yelline] {Document \\ Elicitation \\ Results};
\node at (1,-4) [yelline] {Confirm \\ Elicitation \\ Results};
 
\node at (2,-1) [botline] {Manage Solution \\ Scope \& \\ Requirements};
\node at (2,-2) [botline] {Manage \\ Requirements \\ Traceability};
\node at (2,-3) [botline] {Maintain \\ Requirements \\ for Re-Use};
\node at (2,-4) [botline] {Prepare \\ Requirements \\ Package};
\node at (2,-5) [botline] {Communicate \\ Requirements};
 
\node at (3,-1) [yelline] {Define \\ Business \\ Need};
\node at (3,-2) [yelline] {Assess \\ Capability \\ Gaps};
\node at (3,-3) [yelline] {Determine \\ Solution \\ Approach};
\node at (3,-4) [yelline] {Define \\ Solution \\ Scope};
\node at (3,-5) [yelline] {Define \\ Business \\ Case};
 
\node at (4,-1) [botline] {Prioritize \\ Requirements};
\node at (4,-2) [botline] {Organize \\ Requirements};
\node at (4,-3) [botline] {Specify \& \\ Model \\ Requirements};
\node at (4,-4) [botline] {Define \\ Assumption \& \\ Constraints};
\node at (4,-5) [botline] {Verify \\ Requirements };
\node at (4,-6) [botline] {Validate \\ Requirements};
 
\node at (5,-1) [yelline] {Assess \\ Proposed \\ Solution};
\node at (5,-2) [yelline] {Allocate \\ Requirements};
\node at (5,-3) [yelline] {Assess \\ Organizational \\ Readiness};
\node at (5,-4) [yelline] {Define \\ Transition \\ Requirements};
\node at (5,-5) [yelline] {Validate \\ Solution};
\node at (5,-6) [yelline] {Evaluate \\ Solution \\ Performance};
 
\node at (6,-1) [pinkline] {Analytical \\ Thinking \& Problem \\ Solving };
\node at (6,-2) [pinkline] {Behavioral \\ Characteristics};
\node at (6,-3) [pinkline] {Business \\ Knowledge};
\node at (6,-4) [pinkline] {Communication \\ Skills};
\node at (6,-5) [pinkline] {Interaction \\ Skills};
\node at (6,-6) [pinkline] {Software \\ Applications};
\end{tikzpicture}
\end{center}}
 
\end{document}

Uwe

Uwe Ziegenhagen mag LaTeX und Python, auch gern in Kombination. Hat Dir dieser Beitrag geholfen und möchtest Du Dich dafür bedanken? Dann unterstütze doch vielleicht die Dingfabrik Köln e.V. mit einem kleinen Beitrag. Details zur Bezahlung findest Du unter Spenden für die Dingfabrik.

More Posts - Website

Business Requirements Documents mit LaTeX erstellen

Teil meiner Arbeit als Business Analyst ist die Aufnahme von fachlichen Anforderungen, die dann zu neuen Funktionen führt.

Hier ein Template, wie ein solches Dokument aussehen kann:

Business Requirements Document (PDF)

\documentclass[english,12pt]{scrartcl}
 
\usepackage[]{babel}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[]{palatino}
\usepackage[]{lastpage}
\usepackage[]{booktabs}
\usepackage[]{scrpage2}
\usepackage[]{blindtext}
 
\setlength{\parskip}{.333em}
 
\usepackage{colortbl}
\usepackage[table]{xcolor}
 
% Definition of colors for tables
\definecolor{cell}{RGB}{220,230,240}
\definecolor{line}{RGB}{80,130,190}
 
\renewcommand{\arraystretch}{1.25}
 
\renewcommand{\familydefault}{\sfdefault}
\usepackage{helvet}
 
\newcommand{\comment}[1]{\textless\textit{#1}\textgreater\vspace*{1ex}}
\newcommand{\project}{\textless Project 123\textgreater}
 
\title{Business Requirements Document (BRD) for \project}
\author{My name}
 
\pagestyle{scrheadings}
\setheadsepline[\textwidth]{1pt}{}
 
\ihead{\today}
\chead{}
\ohead{\project}
 
\ifoot{}  
\cfoot{}
\ofoot{\pagemark}
 
 
\usepackage{hyperref}
\hypersetup{%
  colorlinks=true,   % color references
  linkcolor = blue,  % Linkcolor blue
  citecolor = blue,  % cite-color  blue
  urlcolor = blue,  % cite-color blue
  pdfpagemode=UseNone,  % PDF-Viewer startet ohne Inhaltsverzeichnis et.al.
  pdfstartview=FitH} % PDF-Viewer benutzt beim Start bestimmte Seitenbreite
 
\begin{document}
\maketitle
 
\vfill
 
{\large
\begin{description}
\item [Status:] Draft 
\item [Version:] 0.1
\item [Authors:] AA
\end{description}}
 
\clearpage
 
\tableofcontents
 
\section{Document Change Control}
 
\subsection{Document Scope}
 
The scope of this requirements document will be to \comment{Describe high level goal of document}, and will include the following detail:
 
\begin{itemize}
\item \comment{Add Detail of what document will include}
\item 
\item 
\end{itemize}
 
\subsection{Document History}
 
\begin{tabular}{p{0.1\textwidth}p{0.3\textwidth}p{0.15\textwidth}p{0.15\textwidth}p{0.15\textwidth}    }\toprule
Version	& Change Description	&Author	&Date & Released \\ \midrule
1.0 & 	Initial Document Creation	& My Name & 09.06.2012 & 09.06.2012 \\ \bottomrule
\end{tabular}
 
\subsection{Document Approvers}
 
\begin{tabular}{p{0.25\textwidth}p{0.15\textwidth}p{0.125\textwidth}p{0.125\textwidth}p{0.2\textwidth}} \toprule
Role&Name&Signed Off& Date & Signature \\ \midrule
Business Approver & & 05.02.2012 & \\ \bottomrule
\end{tabular}		
 
 
\subsection{Document Guidelines}
 
Requested Delivery Date: \comment{Enter Target Date for Final Version} 
 
 
\begin{itemize}
\item Draft or Final Version: \comment{xx.xx}
\item Approvals via email will be stated as such under Signature column
\item Above list of people will also approve the deployment of the system into production
\end{itemize}
 
\subsection{Document References}
 
Documents below, related to the current initiative, have been created prior to or in conjunction with the Functional Requirements document and can be referenced for further detail:
 
\begin{tabular}{p{0.2\textwidth}p{0.125\textwidth}p{0.12\textwidth}p{0.15\textwidth}p{0.2\textwidth}} \toprule
Name &Date&Version & Author & Location \\ \midrule
Dok1 & 05.02.2012 & 1.0 & AA & \\ \bottomrule
\end{tabular}		
 
\comment{Documents can include the PID, PAD, workshop material, workflows, etc.}
 
 
\subsection{Abbreviations/Acronyms}
 
\comment{List of terms worth to be explained}
 
\begin{tabular}{p{0.2\textwidth}p{0.7\textwidth}} \toprule
Abbreviation &  Explanation \\ \midrule
$\alpha$ & The first letter in the Greek alphabet  \\ \bottomrule
\end{tabular}	
 
 
\section{Introduction}
 
\subsection{Background / Business Problem}
 
\comment{Provide business background and narrative around the issue the project is targeting.  Describe the business area clearly, how the business operates, what region is impacted, and provide a description of the current processing environment for which the project is directed at.  Talk about the current drawbacks of the current process and its impact on the business, IT, or Operations}
 
\subsection{Purpose and Benefits}
 
\comment{Discuss the project, its goals, and who is undertaking the effort.  Give a clear understanding of what the project benefits are and what will be accomplished.  If possible, include measurable benefits}
 
\subsection{Project Scope}
 
\comment{Detail what processes will be impacted by this project, how the project or process is being broken down (by phase or component if possible), and what applications might be involved.  A diagram can be included to provide further explanation or transparency.  Also clarify any items that are Out of Scope for this initiative}
 
\subsection{Critical Success Factors}
 
The following Critical Success Factors represent business driven criteria that, if met, will measure the success for the delivery of this initiative. 
 
\begin{itemize}
\item \comment{Add Criteria details}
\item 
\item 
\end{itemize}
 
\subsection{Requirements Governance}
The following organizational chart displays the Steering Committee, the Core Project Team, and Subject Matter Experts assembled to achieve stated objectives:
 
\comment{Provide a project org chart depicting the business, IT and Operations project leadership structure which will include groups/key individuals involved or directly impacted by the project, and any subject matter experts or oversight committee that are involved.  Org charts can be created in MS Visio or MS PowerPoint and pasted into the document}
 
 
\subsection{User Groups Impacted}
 
The primary users impacted by this initiative are listed below: 
 
\begin{tabular}{p{0.25\textwidth}p{0.25\textwidth}p{0.35\textwidth}} \toprule
User Group &	Location &	Role \\ \midrule
aaa & bbb & ccc \\ \bottomrule
\end{tabular}
 
 
\subsection{Requirement Assumptions and Constraints}
 
 
\comment{Requirement Assumptions and Constraints are future situations beyond the control of the requirement, whose outcomes influence the success of requirement. Examples of assumptions include: availability of a technical platform, legal changes and policy decisions, operations performing a necessary task in conjunction with the process change, etc.}
 
\subsection{Open Issues}
 
\comment{Section is used to show open issues at the time of signoff only (i.e. the document is being signed of with the knowledge of the open issues). The section can be used as a working area as the document is developed but all closed issues should be deleted before the quality gate.}
 
\begin{tabular}{p{0.05\textwidth}p{0.35\textwidth}p{0.5\textwidth}} \toprule
ID & Issue	& Resolution \\ \midrule
1 & & 	\\ \bottomrule
\end{tabular}
 
 
\subsection{Dependencies and Risks}
 
\comment{Dependencies and Risks are conditions that can create an impediment to the delivery and or implementation of the desired requirement.  These can be internal or external.  Examples include: legal requirements, technical standards, strategic decisions, external entities (e.g. a 3rd party supplier of data).  These can exist because of real business or IT conditions.}
 
\section{Business Requirements}
 
\subsection{Description of Current Business State}
 
\comment{Include a high level business state diagram illustrating the current business processing environment.  Depending on the project this can include an accounting state or process state (will include user groups and systems).  Below the diagram include a narrative of the state}
 
 
\subsection{Description of Proposed Business State}
 
\comment{Include a high level business state diagram illustrating the proposed business processing environment.  Depending on the project this can include an accounting state or process state (will include user groups and systems).  Below the diagram include a narrative of the state}
 
 
\subsection{Specific Business Requirements}
 
 
\begin{tabular}{p{0.1\textwidth}p{0.25\textwidth}p{0.4\textwidth}p{0.1\textwidth}} \\ \toprule
BR ID &	BR Name	&BR Description &	Priority \\ \midrule
1 & & & \\ \bottomrule
\end{tabular}
 
 
\section{GAP Analysis (Current State vs. Future State)}
 
\subsection{Current State}
 
\comment{Include a state diagram illustrating the current processing environment.  Depending on the project this can include an accounting state, data state, system diagram, process state (will include user groups and systems), etc.}
 
\subsection{Future State}
 
\comment{Include a state diagram illustrating the current processing environment.  Depending on the project this can include an accounting state, data state, system diagram, process state (will include user groups and systems), etc.}
 
\subsection{GAP Analysis}
 
\comment{A list of gaps identified can be provided within a table in this section.}
 
 
\section{Non-Functional Requirements}
 
\comment{The following are examples of non-functional requirements: Language, Security, Compliance, etc. Within this section, also include Current Volumes and Potential Growth, Performance Requirements and Availability Requirements}
 
\subsection{Current Volume and Potential Growth}
 
\blindtext
 
\subsection{Performance Requirements}
 
\blindtext
 
\subsection{Availability Requirements}
 
\blindtext
 
\subsection{Security Requirements}
 
\blindtext
 
\section{Specific Functional Requirements}
 
The following are the Functional Requirements for Attachments. Each requirement has a unique identifier for tracking and traceability purposes.
 
\begin{tabular}{p{0.1\textwidth}p{0.1\textwidth}p{0.6\textwidth}p{0.1\textwidth}} \\ \toprule
FR ID &	BR ID & FR Description &	Priority \\ \midrule
1 & & & \\ \bottomrule
\end{tabular}
 
 
 
 
\subsection{FR 1 - \comment{Title of FR1}}
 
Provide functional details of FR1
 
\subsection{FR 2 - \comment{Title of FR2}}
 
Provide functional details of FR2
 
\subsection{Usability Requirements / User Experience}
 
Usability Requirements, including Screen Shots and Screen Maps, to be included within this section.
 
\section{Planning Criteria}
This chapter describes the planning criteria specific to the <name> system.
 
\comment{Identify plans associated with the development of the new requirements, user acceptance testing, taking into consideration various activities involved right from the requirement development through development and testing, till the implementation. Interaction with other stakeholders should also be considered.}
 
\subsection{Specific Testing Requirements}
 
\comment{Summarise the specific requirements, which should be tested from a business perspective (for example, Industry-wide testing, Customer (external to DB) Acceptance testing, End-to-End testing, and so on.)}
 
\subsection{Implementation Requirements}
 
\comment{Describe the implementation requirements such as which requirement needs to be implemented in which region(s) and when, training, data migration, deployment related requirements, release schedule, and so on.}
 
\comment{Identify the extent of training and communication (for example, circulars, brochures, memos) to be imparted to the impacted groups.}
 
 
\section{Use Cases}
 
\subsection{UC1 - \comment{Title of UC1}}
 
\begin{enumerate}
\item Brief Description \newline The use case details the steps to be performed by users to <enter the purpose of UC1>
\item Actors
 
\begin{itemize}
\item <Enter name of application> User 
\item <Enter name of application> System
\end{itemize}
 
 
\item Preconditions
 
\begin{itemize}
\item The user should be entitled to act on the case.
\item Enter any other preconditions
\end{itemize}
 
 
\item Business Rules
 
\begin{itemize}
\item Add any specific business rules
\end{itemize}
 
\item Trigger 
 
\begin{itemize}
\item Enter the trigger for the use case to occur
\end{itemize}
 
\item Basic Flow of Events
 
\begin{tabular}{p{0.2\textwidth}p{0.7\textwidth}} \toprule
Step &	Description \\ \midrule
1	&    \\ 
2	&    \\ 
3	&    \\ \bottomrule
\end{tabular}
 
\end{enumerate}
 
\section{Appendix}
 
\subsection{Appendix Item1 }
 
\comment{Enter Details Here}
 
\subsection{Appendix Item 2}
 
\comment{Enter Details Here}
 
\arrayrulecolor{line}
\rowcolors{2}{cell}{white}
\begin{tabular}{p{0.2\textwidth}p{0.15\textwidth}p{0.25\textwidth}p{0.2\textwidth}} \toprule
Name &Date&Version & Author \\ \midrule
Line1 & 05.02.2012 & 1.0 & AA \\ 
Line2 & 05.02.2012 & 2.0 & BB \\ 
Line3 & 05.02.2012 & 3.0 & CC \\ 
Line4 & 05.02.2012 & 4.0 & DD \\ 
Line5 & 05.02.2012 & 5.0 & EE \\ \bottomrule
\end{tabular}		
\end{document}

Uwe

Uwe Ziegenhagen mag LaTeX und Python, auch gern in Kombination. Hat Dir dieser Beitrag geholfen und möchtest Du Dich dafür bedanken? Dann unterstütze doch vielleicht die Dingfabrik Köln e.V. mit einem kleinen Beitrag. Details zur Bezahlung findest Du unter Spenden für die Dingfabrik.

More Posts - Website