Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- \documentclass{scrreprt}
- \usepackage{color}
- \usepackage{float}
- \usepackage{graphicx}
- \usepackage{listings}
- \usepackage{underscore}
- \usepackage[bookmarks=true]{hyperref}
- \usepackage[utf8]{inputenc}
- \usepackage[english]{babel}
- %\setcounter{tocdepth}{3}
- \setcounter{secnumdepth}{3}
- \hypersetup{
- bookmarks=false, % show bookmarks bar?
- pdftitle={Software Requirement Specification}, % title
- pdfauthor={Alistair Bahr}, % author
- pdfsubject={Malware}, % subject of the document
- pdfkeywords={malware, virus, worm, phishing, trojan, malicious}, % list of keywords
- colorlinks=true, % false: boxed links; true: colored links
- linkcolor=blue, % color of internal links
- citecolor=black, % color of links to bibliography
- filecolor=black, % color of file links
- urlcolor=purple, % color of external links
- linktoc=page % only page is linked
- }%
- \def\myversion{2.0 }
- \date{27.11.2019}
- %\title{%
- %}
- \usepackage{hyperref}
- \begin{document}
- \begin{flushright}
- \rule{16cm}{5pt}\vskip1cm
- \begin{bfseries}
- \Huge{SOFTWARE REQUIREMENTS\\ SPECIFICATION}\\
- \vspace{1.9cm}
- for\\
- \vspace{1.9cm}
- Tennis Club Application\\
- \vspace{1.9cm}
- \LARGE{Version \myversion }\\
- \vspace{1.9cm}
- Prepared by Alistair Bahr\\
- \vspace{1.9cm}
- \today\\
- \end{bfseries}
- \end{flushright}
- \tableofcontents
- \chapter*{Revision History}
- \begin{center}
- \begin{tabular}{|c|c|c|}
- \hline
- Date & Reason For Changes & Version\\
- \hline
- October 25, 2019 & First Version & 1.0\\
- \hline
- \today & General improvements & 2.0\\
- \hline
- \end{tabular}
- \end{center}
- \chapter{Introduction}
- \section{Purpose}
- In this document, which follows the IEEE SRS document standard, the requirements of the Tennis Club Application are described. This software will replace the current system of archiving data about the matches, as well as providing additional features, like a live score which can be viewed and easier access to player data. In the current system, which relies solely on paper, it is very time-consuming, to access or store data in the archive. Also there are big problems with the current system, because data can get lost or fraudulently altered.
- \section{Document Conventions}
- There are no specific document conventions used.
- \section{Intended Audience and Reading Suggestions}
- This document is intended for the shareholders of the tennis club, as well as the developers of the application.
- Following after this heading are the product scope, an overall description and definitions about the tennis club application. Afterwards more information about the user interface’s requirements and the software’s features in correlation to their requirements. In the end non-functional requirements will be described.
- \section{Project Scope}
- The aim for this software project is to replace the current way of archiving data about players and matches, as well as granting specific groups of people differing amounts of access to the data.
- There are three main parts of the application. First the archive, the referee UI and lastly the live match view.
- The archive in its limited version is intended for everyone, even without a user account, and shows all match information but only non-sensitive data about the players. But there is also a non-limited version of the archive which is only intended for shareholders. This version gives access to sensitive data about the players, like a home address.
- After logging in with a referee account, the user gets access to a referee user interface, which allows setting the score of a particular match, while it is going on. The data of this is also viewable via the live match view.
- The live match view is also accessible to everyone, even without an account, and reflects the data, the referee enters while a match is running.
- \chapter{Overall Description}
- \section{Product Perspective}
- This software replaces an existing analogue system. It is designed from ground up. The software itself is part of a system, which allows storage of data about matches and access to previously saved matches and players.
- \subsection{External interface requirements}
- \subsubsection{User interface requirements}
- \noindent
- \begin{tabular}{|p{0.2\textwidth}|p{0.2\textwidth}|p{0.5\textwidth}|}
- \hline
- \textbf{Requirement No.} & \textbf{Title} & \textbf{Description} \\ \hline
- UI.1 & Log in & The software shall allow log in, for the access to some parts of the software \\ \hline
- UI.2 & Create account & The software shall allow the possibility to create a player account, in case a player did not register yet. \\ \hline
- UI.3 & Links & The software shall present links to the archive and the live score view on the start page and a link to the start page on all other pages. \\ \hline
- \end{tabular}
- \subsubsection{Hardware interface requirements}
- The application shall support all commonly used web browsers for pc’s and smartphones.
- \section{Product Functions}
- The software incorporates the following use cases:\newline\newline
- \begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.1} \\
- \hline
- \textbf{Use case name} & Update score \\
- \hline
- \textbf{Actor} & Referee \\
- \hline
- \textbf{Description} & Referee updates a live score \\
- \hline
- \textbf{Pre-condition} & The Referee needs to be logged in, An active account is required, An ongoing match session is required \\
- \hline
- \textbf{Scenario} & 1. The system displays the current score\newline
- 2. The referee decides to alter the current data \newline
- 3. The referee uses the interface to alter the current score line \newline
- 4. The system displays and saves the new altered score line \\
- \hline
- \textbf{Result} & The live score is altered \\
- \hline
- \textbf{Exceptions} & None \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.2} \\
- \hline
- \textbf{Use case name} & Finalize match \\
- \hline
- \textbf{Actor} & Referee \\
- \hline
- \textbf{Description} & Referee finalizes the match \\
- \hline
- \textbf{Pre-condition} & The Referee needs to be logged in, An active account is required, An ongoing match session is required \\
- \hline
- \textbf{Scenario} & 1. The system displays the current score line \newline 2. The referee opts to end the match \newline 3. The system persists the final score \newline 4. The system locks the interface \\
- \hline
- \textbf{Result} & The match ends \\
- \hline
- \textbf{Exceptions} & None \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.3} \\
- \hline
- \textbf{Use case name} & Set up match information \\
- \hline
- \textbf{Actor} & Administrator \\
- \hline
- \textbf{Description} & The Administrator sets up the match information \\
- \hline
- \textbf{Pre-condition} & A user with an active Administrator account needs to be logged in \\
- \hline
- \textbf{Scenario} & 1. The Administrator opts to create a new match session \newline 2. The System redirects the administrator to the match creation page \newline 3. The Administrator enters the appropriate match data \newline 4. The Administrator opts to finalize the match creation process \newline 5. The System checks the inserted data \newline 6. The System persists the new match data \\
- \hline
- \textbf{Result} & The User views the live score \\
- \hline
- \textbf{Exceptions} & 5.\newline System message “Invalid message” 5.1~ Return user to step 4 \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.4} \\
- \hline
- \textbf{Use case name} & Create Referee and Admin Accounts \\
- \hline
- \textbf{Actor} & Administrator \\
- \hline
- \textbf{Description} & The administrator creates a referee or administrator account \\
- \hline
- \textbf{Pre-condition} & A user with an active Administrator account needs to be logged in, An ongoing match session is required, Active internet connection is needed \\
- \hline
- \textbf{Scenario} & 1. The Administrator opts to create a high-access account \newline 2. The system redirects the administrator to the account creation page \newline 3. The Administrator enters the intended user’s details \newline 4. The Administrator chooses to finalize the account creation \newline 5. The System checks if the filled information is valid \newline 6. The System persists the new account and sends an email to the intended user \\
- \hline
- \textbf{Result} & The User views the live score \\
- \hline
- \textbf{Exceptions} & 1. System message “Invalid credentials” 1.1~~ Return user to step 4 \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.5} \\
- \hline
- \textbf{Use case name} & Retrieve sensitive information \\
- \hline
- \textbf{Actor} & Tennis Board/Administrator \\
- \hline
- \textbf{Description} & A member of the Tennis Board chooses to retrieve sensitive information \\
- \hline
- \textbf{Pre-condition} & An account with elevated privileges is needed, The member needs to be logged in, Active internet connection is needed \\
- \hline
- \textbf{Scenario} & 1. A board member navigates to the club’s webpage \newline 2. The System displays the member with options \newline 3. The member opts to retrieve sensitive data about a player (e.g. a player's profile) \newline 4. The system displays the sensitive information to the member \\
- \hline
- \textbf{Result} & A member of the board retrieves some desired sensitive data \\
- \hline
- \textbf{Exceptions} & None \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.6} \\
- \hline
- \textbf{Use case name} & View live score \\
- \hline
- \textbf{Actor} & No particular Actor everyone has access to this use case \\
- \hline
- \textbf{Description} & A user views the live score \\
- \hline
- \textbf{Pre-condition} & At least one ongoing tennis match session is required, Active internet connection is needed \\
- \hline
- \textbf{Scenario} & 1. The User navigates to the club’s website \newline 2. The System displays the user with the options \newline 3. The User opts to view the live score development \newline 4. The System redirects the user to the appropriate page where the current live scores are displayed \\
- \hline
- \textbf{Result} & The User views the live score \\
- \hline
- \textbf{Exceptions} & None \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.7} \\
- \hline
- \textbf{Use case name} & Retrieve non-sensitive data \\
- \hline
- \textbf{Actor} & Everyone no user restriction \\
- \hline
- \textbf{Description} & A user retrieves sensitive data \\
- \hline
- \textbf{Pre-condition} & Active internet connection is needed \\
- \hline
- \textbf{Scenario} & 1. The interested user navigates to the club’s page \newline 2. The system displays the user with the available options \newline 3. The user opts to retrieve information about some non-sensitive information (e.g. match details) \newline 4. The system redirects the user to the page with the desired information \newline 5. The system displays the desired chosen information \\
- \hline
- \textbf{Result} & The User views the live score \\
- \hline
- \textbf{Exceptions} & 4. The user opts to see sensitive data \newline 4.1 System message “You are not authorized to access this page” \newline 4.2 Return to step 3 \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.8} \\
- \hline
- \textbf{Use case name} & Register account \\
- \hline
- \textbf{Actor} & Tennis Player \\
- \hline
- \textbf{Description} & A user registers a normal account in the web page \\
- \hline
- \textbf{Pre-condition} & Active internet connection is needed \\
- \hline
- \textbf{Scenario} & 1. The interested user navigates to the club’s page \newline 2. The system displays the user with the available options \newline 3. The user opts to register an account \newline 4. The System redirects the user to the registration page \newline 5. The user fills in the appropriate information \newline 6. The System checks the inserted information \newline 7. The System persists the data and send an email to the user \\
- \hline
- \textbf{Result} & The User views the live score \\
- \hline
- \textbf{Exceptions} & 6. System message “Invalid Data” \newline 6.1 Return to step 5 \\
- \hline
- \end{tabular}\newline\newline
- \noindent\begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- \textbf{Use Case ID} & \textbf{UC.9} \\
- \hline
- \textbf{Use case name} & View profile \\
- \hline
- \textbf{Actor} & Tennis Player/Board Member/Administrator \\
- \hline
- \textbf{Description} & A user decides to view their profile \\
- \hline
- \textbf{Pre-condition} & Active internet connection is needed, A registered account is required, The user needs to have logged in \\
- \hline
- \textbf{Scenario} & 1. The user opts to view their profile \newline 2. The System redirects the user to their profile page \newline 3. The System displays the user’s information \\
- \hline
- \textbf{Result} & The User views the live score \\
- \hline
- \textbf{Exceptions} & None \\
- \hline
- \end{tabular}\newline\newline
- \section{User Classes and Characteristics}
- \subsection{Third Parties / Media}
- As third parties or media users are meant, who represent the biggest number of overall users. The users do not need a user account and have quite limited access to the application. They have only access to non-sensitive data on user profiles, they can watch the live score during a game and look into the archive.
- \subsection{Tennis club members / Players}
- This user group represents the biggest amount of user accounts. They have only a few more rights than a non-registered person. Namely viewing non-sensitive parts of other profiles and the entirety of theirs.
- \subsection{Referee}
- A referee has an user account, which is prepared by an administrator. It can’t be created directly. With this account you have access to the referee user interface, which allows the modification and finalization of a current tennis match.
- \subsection{Administrator}
- As an administrator you have full access to the software and its data. Even to the database itself.
- \subsection{Board members/Shareholders}
- Shareholders and board members get elevated access to all the parts of the software’s interface, although they don’t have direct database access.
- \section{Operating Environment}
- \begin{tabular}{|p{3cm}|p{4cm}|p{7cm}|}
- \hline
- \textbf{REQNR.} & \textbf{Title} & \textbf{Explanation} \\
- \hline
- \textbf{NONF-OPERENV.1} & Device Support & The application shall be usable from a range of devices. Most notably PC’s and smartphones \\
- \hline
- \textbf{NONF-OPERENV.2} & Internet connection & Because of the remote data storage and the application being a website, an internet connection will be required in order to use it. \\
- \hline
- \end{tabular}
- \section{Design and Implementation Constraints}
- \begin{tabular}{|p{3cm}|p{4cm}|p{7cm}|}
- \hline
- \textbf{ Constraint ID } & \textbf{ Title } & \textbf{ Explanation } \\
- \hline
- \textbf{ CONSTR.1 } & Data safety laws & The application shall abide latest policies regarding storage, usage, processing and deletion in relation to the GDPR. \\
- \hline
- \textbf{ CONSTR.2 } & Maintenance & The maintenance shall be handled by a non-biased (in regards to tennis matches) administrator \\
- \hline
- \textbf{ CONSTR.3 } & Data Access & Full data access via the database is only granted to the administrator. \\
- \hline
- \end{tabular}
- \section{User Documentation}
- No specific documentation is provided.
- \section{Assumptions and Dependencies}
- It is assumed, that the software is maintained by an administrator. Other than that, there are no further factors that influence the requirements stated in this document.
- \section{Apportioning of requirements}
- There are no requirements, that are delayed until future versions.
- \chapter{Specific Requirements}
- \section{External Interface Requirements}
- \subsection{User Interfaces}
- Every user class has the same interface with a differing amount of options and data. This is done in order to ensure security and data integrity. For example, a referee only has a view like shown in Fig. 3.1.\newline
- \begin{figure}[h]
- \centering
- \includegraphics[width=0.7\textwidth]{images/refeere-ui.png}
- \caption{the referee UI}
- \end{figure}
- \begin{figure}[hbt!]
- \centering
- \includegraphics[width=0.7\textwidth]{images/startpage.png}
- \caption{start page}
- \end{figure}
- \subsubsection{Public}
- Every user first has to log in. For that, there are fields for username and password in addition to a login button in the top right of the website (Fig. 3.2).
- If someone who isn’t logged in opens the profile of a player only public information is shown. Sensitive data is only shown to those user groups who are allowed access to such data.
- \subsubsection{Tennis Member/Player}
- Normal users can view the live score of the current match. They can also view their profile with all data, other profiles only with non-sensitive data.
- \subsubsection{Tennis Board}
- User accounts of board members have access to all sensitive and non-sensitive data from all players. For that they have to choose a specific account from the members list.
- \subsubsection{Administrator}
- Administrators, like board members can also view sensitive data. But in addition, they are able to create referee and other admin accounts. Also, they can set up match information via the match creation page.
- \subsubsection{Third Parties}
- Have the same rights as any user without an account.
- \subsubsection{Referee}
- Is able to update the live score.
- \subsubsection{Tennis association}
- Has the same rights as any user without an account.
- \section{Hardware Interfaces}
- The software is not dependent on any specific hardware. It can be run from a smartphone browser as well as from a notebook / pc.
- \section{Software Interfaces}
- A web interface is used, to ensure that it is runnable on all devices. That means a smartphone as much as it means a desktop pc. Necessary is only a web browser and an active internet connection.
- \section{Communications Interfaces}
- The software uses HTTPS as its only communication interface.
- \chapter{System Features}
- \begin{tabular}{|p{3cm}|p{3cm}|p{7.4cm}|}
- \hline
- \textbf{ ID } & \textbf{ Hierarchy } & \textbf{ User Class } \\
- \hline
- C1 & 1 & Public \\
- \hline
- C2 & 2 & Player \\
- \hline
- C3 & 3 & Referee \\
- \hline
- C4 & 4 & Tennis Board \\
- \hline
- C5 & 5 & Administrator \\
- \hline
- \end{tabular}\newline\newline\newline
- \begin{tabular}{|p{1cm}|p{2cm}|p{3cm}|p{7cm}|}
- \hline
- \textbf{ID} & \textbf{User Class} & \textbf{ Function } & \textbf{ Description } \\
- \hline
- UC.1 & C3 & Update score & The referee has to update the score of each player after they scored a point, so that in the end the proper result can be archived and sent to the tennis association, but also to enable people to view the live score. \\
- \hline
- UC.2 & C3 & Finalize match & After a match the referee has to finalize the match. After that it can’t be altered anymore and will automatically be archived. Also, the results are sent to the tennis association. \\
- \hline
- UC.3 & C4 & Set up match information & Before a match an administrator has to set up the matches information in the system i.e. the player’s names. Only afterwards can the referee do their job. \\
- \hline
- UC.4 & C4 & Create Referee and Admin Accounts & Accounts with elevated rights can only be created by already existing administrators. \\
- \hline
- UC.5 & C4, C5 & Retrieve sensitive information & Elevated user accounts have access to sensitive information about players. \\
- \hline
- UC.6 & C1, C2, C3, C4, C5 & View live score & Everyone can view the score of a game while it is running. \\
- \hline
- UC.7 & C1, C2, C3, C4, C5 & Retrieve non-sensitive data & Everyone can access information about past matches. \\
- \hline
- UC.8 & C2 & Register account & New players or those without an already existing account, can create it. \\
- \hline
- UC.9 & C2, C3, C4, C5 & View profile & All registered users have access to basic information about any other user. \\
- \hline
- \end{tabular}
- \section{System Feature 1 - Archive}
- \begin{figure}[h!]
- \centering
- \includegraphics[width=0.5\textwidth]{./images/navigate.png}
- \caption{user profile}
- \end{figure}
- \subsection{Description and Priority}
- In the archive data about all players and past matches is saved. Non-sensitive player data consists of country of origin, gender and name in addition to stats about earlier matches. When logged in with an account with sufficient rights, i.e. board member/administrator/player themselves, sensitive data will be shown in addition. Sensitive data consists of the home address of the player. \textbf{\newline priority: high \newline cost: high}
- \subsection{Functional Requirements}
- \begin{tabular}{|p{0.2\textwidth}|p{0.2\textwidth}|p{0.1\textwidth}|p{0.4\textwidth}|}
- \hline
- \textbf{Requirement ID}&\textbf{Title}&\textbf{Use case relation}&\textbf{Explanation}\\
- \hline
- FREQ.AR.1 & Finalize Match & UC.2 & In order for match data to be saved in the archive, it has to be entered and then finalized by a referee. \\
- \hline
- FREQ.AR.2 & Set up match information & UC.4 & The match information has to be set up by an administrator, so that a referee can update the scores.\\
- \hline
- FREQ.AR.3 & Register account & UC.8 & A tennis player must register an account, otherwise they will not show up in the archive\\
- \hline
- FREQ.AR.4 & View profile & UC.9 & To make use of the archive saving player data, the system must allow a way to view the profiles\\
- \hline
- FREQ.AR.5 & Retrieve non-sensitive data & UC.7 & To make use of the archive saving match data, the system must allow a way to view past matches\\
- \hline
- FREQ.AR.6 & Retrieve sensitive information & UC.5 & Board members and administrators shall have access to sensitive about players like their home address.\\
- \hline
- \end{tabular}
- \section{System Feature 2 - Referee interface}
- \begin{figure}[h!]
- \centering
- \includegraphics[width=0.7\textwidth]{./images/refeere-ui.png}
- \caption{Referee's user interface}
- \end{figure}
- \subsection{Description and Priority}
- The referee interface allows the referee to note down the score of a match while it is running. The data about the match, like who plays whom, is setup in advance by an administrator. After the match is complete, the referee finalizes the data, after which it is saved to the archive. \textbf{\newline priority: high \newline cost: low}
- \subsection{Functional Requirements}
- \begin{tabular}{|p{0.2\textwidth}|p{0.2\textwidth}|p{0.1\textwidth}|p{0.4\textwidth}|}
- \hline
- \textbf{Requirement ID}&\textbf{Title}&\textbf{Use case relation}&\textbf{Explanation}\\
- \hline
- FREQ.RI.1 & Update score & UC.1 & The referee must be able to update the score in their interface in order for the live score to change or be visible at all. \\
- \hline
- FREQ.RI.2 & Set up match information & UC.3 & The match needs to be set by an administrator, so that on the live score the player's names can be displayed. \\
- \hline
- \end{tabular}
- \section{System Feature 3 - Live score}
- \begin{figure}[h!]
- \centering
- \includegraphics[width=0.7\textwidth]{./images/livematches.png}
- \caption{live matches}
- \end{figure}
- \subsection{Description and Priority}
- The live score is a way for people to follow a match without needing to attend it personally. All updates to the score done by the referee are directly visible in the live score.\textbf{\newline priority: low \newline cost: low}
- \subsection{Functional Requirements}
- \begin{tabular}{|p{0.2\textwidth}|p{0.2\textwidth}|p{0.1\textwidth}|p{0.4\textwidth}|}
- \hline
- \textbf{Requirement ID}&\textbf{Title}&\textbf{Use case relation}&\textbf{Explanation}\\
- \hline
- FREQ.LS.1 & View live score & UC.6 & The live score must be able to be viewed by the user. \\
- \hline
- FREQ.LS.2 & Update Score & UC.1 & In order to display the score as the match progresses, the referee must be able to update the score. \\
- \hline
- FREQ.LS.3 & Set up match information & UC.3 & The names of the players can only be shown if the match is properly set up by an administrator. \\
- \hline
- \end{tabular}
- \chapter{Other Non-functional Requirements}
- \section{Performance Requirements}
- There are no performance requirements for this project.
- \section{Safety Requirements}
- There are no specific safety requirements.
- \section{Security Requirements}
- \begin{tabular}{|p{0.2\textwidth}|p{0.2\textwidth}|p{0.5\textwidth}|}
- \hline
- \textbf{Requirement ID}& \textbf{Title} & \textbf{Explanation}\\
- \hline
- NFREQ.SE.1 & User authentication & the actor shall authenticate themselves via username and password in order to access anything not available to the public. \\
- \hline
- NFREQ.SE.2 & Access restriction & certain parts of the application are only accessible to certain user groups.\\
- \hline
- NFREQ.SE.3 & Data protection & The application shall comply with the GDPR.\\
- \hline
- \end{tabular}
- \section{Software Quality Attributes}
- The application has to be very reliable, because without it the referee is not able to properly mark down scores in a match. Also, interested fans would not be able to follow matches otherwise.
- \section{Business Rules}
- There are no additional business rules.
- \chapter{Appendix}
- \section{Glossary}
- \subsection{References}
- https://connect.fontys.nl/instituten/fhtenl_studies/studies/INF/PRJ3/StudyMaterial/IEEE_Standard_IEEE\%20Recommended\%20Practice\%20for\%20Software\%20Requirements\%20Specifications.pdf
- \subsection{Definitions}
- \begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- Player & A person, who plays tennis in the tennis club\\
- \hline
- Referee & A person, usually not part of the tennis club, who acts as a judge for a match of tennis. They enter the data about the match while it occurs and afterwards submit it to the archive.\\
- \hline
- Archive & A section of the software, which saves data about matches and players, as well as granting access to them.\\
- \hline
- Administrator & A person, with full access to all systems. This includes the database itself.\\
- \hline
- \end{tabular}
- \subsection{Abbreviations}
- Abbreviations for unique identifiers are used in this document. Here’s a list of them, with “.X” representing a number: \newline\newline
- \noindent
- \begin{tabular}{|p{3cm}|p{9cm}|}
- \hline
- UC.X & Use Case \\
- \hline
- UI.X & User Interface \\
- \hline
- NONF-OPERENV.X & Non-functional operating environment \\
- \hline
- CONSTR.X & Constraint \\
- \hline
- FREQ.AR.X & Functional requirement for the archive\\
- \hline
- FREQ.RI.X & Functional requirement for the referee interface \\
- \hline
- FREQ.LS.X & Functional requirement for the live score \\
- \hline
- NFREQ.SE.X & Non-functional requirement for security \\
- \hline
- \end{tabular}
- \end{document}
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement