LERUKA     

LERUKA  Use­Case Specification: View public highscore    Version <1.6>           

  Confidential 

 

 

©​ LERUKA, 2015 

Page 1 

   

LERUKA     

Revision History  Date 

Version 

Description 

Author 

23/10/2015 

1.0 

Erstellen des UC­Dokuments 

Ruth W. 

27/10/2015 

1.1 

Use Case geändert, zeigt “user”/”server”  nicht an 

Ruth W. 

01/11/2015 

1.2 

Hinzufügen der Feature­Narration  Beschreibung 

Leif B. 

08/11/2015 

1.3 

Feature­Narration geändert 

Ruth W. 

19/12.2015 

1.4 

Feature­Narration aktualisiert 

Ruth W. 

15/04/2016 

1.5 

Hinzufügen der Function Points 

Ruth W. 

01/06/16 

1.6 

Anpassungen 

Ruth W. 

   

  Confidential 

 

©​ LERUKA, 2015 

Page 2 

   

LERUKA     

Table of Contents  Use­Case Name  Brief Description  Mockup  Flow of Events  Basic Flow  Narration  Alternative Flows  Special Requirements  Preconditions  Postconditions  Extension Points  Function Points   

  Confidential 

 

©​ LERUKA, 2015 

Page 3 

   

LERUKA     

Use­Case Specification: View public highscore      

1.

Use­Case Name  

1.1

Brief Description  “Öffentlicher Highscore” should show guests and members the public highscore. 

1.2

Mockup 

     

  Confidential 

 

 

©​ LERUKA, 2015 

Page 4 

   

LERUKA     

2.

Flow of Events 

2.1

Basic Flow   The user and also the guest can view the public highscore. 

             

  Confidential 

 

©​ LERUKA, 2015 

Page 5 

   

LERUKA      2.1.1

Narration  View public highscore feature file 

 

  Total test result   

2.2

Alternative Flows  n/a   

3.

Special Requirements  n/a   

4.

Preconditions  There has to be a connection to the server.   

5.

Postconditions  n/a 

  Confidential 

 

©​ LERUKA, 2015 

Page 6 

   

LERUKA       

6.

Extension Points  n/a 

7.

Function Points  We calculated the function points with the following table from TINY TOOLS. The Use Case “View 

public  highscore” has 39,6 points. 

 

  Confidential 

 

©​ LERUKA, 2015 

Page 7 

LERUKA LERUKA UseCase Specification: View public ... - GitHub

UseCase Name. Brief Description. Mockup. Flow of Events. Basic Flow. Narration. Alternative Flows. Special Requirements. Preconditions. Postconditions.

254KB Sizes 1 Downloads 237 Views

Recommend Documents

leruka - GitHub
Erstellen des UCDokuments. Ruth W. 02/11/2015. 1.1. Mockup und Activity Diagram eingefügt. Ruth W., Kassandra F. 06/04/2016. 1.2. Allgemeine Änderungen.

Devicetree Specification - GitHub
Apr 30, 2016 - Companies ... A piece of software may be both a client program and a boot ..... defined by the DTSpec. 2.2. Devicetree Structure and Conventions. 10 ...... dtc-paper.pdf), An overview of the concept of the device tree and device ...

Architectural Requirements Specification - GitHub
cumbersome tool to have to port to mobile application clients. 4. Page 7. Description of Components .1 Odin-CLI .1.1 Technologies. The command line interface will be implemented in Python 3, using built-in classes and libraries to provide a usable in

System Requirements Specification - GitHub
This section describes the scope of Project Odin, as well as an overview of the contents of the SRS doc- ument. ... .1 Purpose. The purpose of this document is to provide a thorough description of the requirements for Project Odin. .... Variables. â€

StackMap API Specification - GitHub
domain is the specific StackMap installation for your library. POST Data. The POST ... A node with the name of the library to search for the holding. ▫ Attributes.

Architectural Requirements Specification - GitHub
porchetta tri-tip kielbasa kevin chicken hamburger sirloin. Cow pastrami short ribs shank. Sirloin spare ribs jowl, beef ham hock kielbasa ribeye prosciutto cow. Capicola pork chop landjaeger jowl venison beef ribs sirloin tri-tip tenderloin pastrami

System Requirements Specification - GitHub
System Requirements Specification. Project Odin. Kyle Erwin. Joshua Cilliers. Jason van Hattum. Dimpho Mahoko. Keegan Ferrett. Note: This document is constantly under revision due to our chosen methodology, ... This section describes the scope of Pro

Orc Protocol Specification - GitHub
Jun 7, 2017 - RPC message format changed (4.1 Structure and Authentication). • New CLAIM .... signature to authenticate the payload. Positions 3 and ..... Kademlia (http://www.scs.stanford.edu/~dm/home/papers/kpos.pdf). • S/Kademlia ...

Orc Protocol Specification - GitHub
Aug 15, 2017 - This specification documents the Orc network protocol in its entirety for the purpose of enabling .... services and authentication is performed by the nature of Tor's routing. Each Orc node ... associated with held contracts (5. Data T

Requirement Specification - GitHub
The former one focuses on understanding and stating ... Controller Area Network ... Clearly, the services of DIL can be categorized in two groups, one bus the ...

StackMap JSON API Specification - GitHub
o The text of the call number of the holding. ▫ “library” o The text ... o An decimal, the x position of the center of the range on the map, in pixels. ▫ “y” o An decimal ...

ActionScript® 4.0 Language Specification - GitHub
Dec 13, 2012 - Computer Software Documentation,'' as such terms are used in 48 C.F.R. §12.212 ... Dec 5 2012 Added syntactic support for variable-length unicode escape ...... 365. Expression. 366. ReferenceExpression = Expression. 367.

View PDF - GitHub
There is a set of methods proposed for regression in which the target value is likely to be a linear combination of the input variables. In mathematical notion, if Y is the predicted value, then its value can be obtained from equation 2 as h(x). Ordi

Hypervisor Top Level Functional Specification - GitHub
100. HvSendSyntheticClusterIpiEx . ...... That is, the hypervisor is free to deliver the interrupt ..... When a message is sent, the hypervisor selects a free message buffer. ...... The Flags field included an invalid mask value in the proximity doma

Specification on Image Data File Version - GitHub
5.4.10 ShootingRecord heap ... the JFIF file format[1], as described below), sample software shall be provided openly to player vendors. ... In the separate "Decisions Concerning Extension" section, we define how various companies.

Anonymous Go-Kart: Specification Report Supervisor - GitHub
May 9, 2011 - [email protected] (83238549). Wim Looman ... Department of Computer and Electrical Engineering. University of ... kart, so that it can be easily controlled by a laptop. The second is to ..... BostonDynamicsTRQ6Sep09.pdf.

Cosmos​​IBC​​Specification - GitHub
access​​to​​only​​part​​of​​the​​state​​space.​​This​​can​​increase​​throughput,​​but​​also makes​​any​​transaction​​that​​touches​​multiple​​shards​​extremely​​diffi

The Quick Chart File Format Specification 1.01.pdf - GitHub
Page 1. The Quick Chart (.QCT). File Format Specification. Revision 1.01. 07 MAR 2009. Craig Shelley [email protected]. Disclaimer. THIS DOCUMENT ...

Zcash Protocol Specification, Version 2017.0-beta-2.7 - GitHub
T. The domain of a randomized algorithm may be (), indicating that it requires no ...... 32. 100. PoWMaxAdjustUp ◦. ◦ Q := 16. 100. PoWDampingFactor ◦. ◦ N := 4 .... The language consisting of the following encoding possibilities is pre x-fre

High level Functional Specification of the FlexiblePower ... - GitHub
2 / 14. Summary. This document provides a high level functional description of the .... Smart grids are used to better incorporate renewable energy sources. ..... http://www.broadband-forum.org/technical/download/TR-069_Amendment-4.pdf).

The Quick Chart (.QCT) File Format Specification - GitHub
Feb 13, 2011 - ALL BRANDS AND PRODUCT NAMES MAY BE TRADEMARKS OR REGISTERED TRADEMARKS OF ..... painstakingly viewing and attempting to interpret the content of freely available .... Partial URL to QC3 map file ..... In order to find the start of the

The Quick Chart File Format Specification 1.02.pdf - GitHub
Jul 12, 2009 - OF THE DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-. INFRINGING. .... The Quick Chart File Format Specification V1.02. 3 ..... Example sub-palette mapping;. Palette.

The Quick Chart (.QCT) File Format Specification - GitHub
Nov 1, 2008 - COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL .... The information contained within this document was NOT obtained by means.