mirror of
https://github.com/st-tu-dresden-praktikum/swt23w23
synced 2024-07-19 21:04:36 +02:00
Adjust headlines to match a single style
This commit is contained in:
parent
99b2f4aaf4
commit
80b36f792b
|
@ -7,9 +7,9 @@
|
|||
|
||||
= Developer documentation
|
||||
|
||||
== Introduction and Goals
|
||||
== Introduction and goals
|
||||
|
||||
== Task Definition
|
||||
== Task definition
|
||||
|
||||
As our client Mr Wurst has built up the large catering service Mampf over the years, he now needs a system that will simplify planning for him and his customers. The catering service should enable him to process all billing, ordering and administrative tasks in a standardised way. Previously, Mr Wurst used various programmes for this and was always annoyed by their incompatibility with each other and the additional work involved in separate data storage. He gave us the following description of his small company as a basis for the system development:
|
||||
|
||||
|
@ -21,7 +21,7 @@ The client made the following statements verbally on request:
|
|||
|
||||
Customers must be able to register themselves, book orders and delete their account if necessary. The latter should also be possible for the administrator for any customer. The administrator also has special overview pages for managing the business. Orders can only be paid for in cash. The allocation of resources to an order must take place without manual intervention. As part of the special promotions mentioned above, certain offers should have a promotional price and be specially labelled. Bookings for Mobile Breakfast are made on a monthly basis at fixed time slots. There are several menus to choose from. Invoice means an informal list of order items in PDF format and on the website. Billing refers to an informal statement of the actual hours worked by employees each month. In technical terms, passwords for user accounts should be stored securely in accordance with current standards.
|
||||
|
||||
== Quality Demands
|
||||
== Quality demands
|
||||
|
||||
Functional Suitability::
|
||||
|
||||
|
@ -84,7 +84,7 @@ constraint.
|
|||
Use-time constraints can be separated into customer (c) and administration (a),
|
||||
each denoted by having their letter prefixed with `u.`.
|
||||
|
||||
=== Hardware Specifications
|
||||
=== Hardware specifications
|
||||
|
||||
* r: server computer
|
||||
* b: mid-range computer
|
||||
|
@ -99,7 +99,7 @@ each denoted by having their letter prefixed with `u.`.
|
|||
** u.a: screen with a resolution of at least 1920×1080 at a DPR of 1 (= 96 dpi)
|
||||
** u.c: screen with a resolution of at least 360×640/640×360 at a DPR of 1 (= 96 dpi)
|
||||
|
||||
=== Software Specifications
|
||||
=== Software specifications
|
||||
|
||||
* r: JRE 17
|
||||
* b: JDK 17
|
||||
|
@ -109,7 +109,7 @@ each denoted by having their letter prefixed with `u.`.
|
|||
** WebKit 605.1.15
|
||||
** Explicity not supported are any browsers based on Trident/EdgeHTML
|
||||
|
||||
=== Product Usage
|
||||
=== Product usage
|
||||
|
||||
The system is going to to be used as a website for administration and handling of orders for the catering service operated by Hannes Wurst.
|
||||
|
||||
|
@ -127,7 +127,7 @@ so common patterns that are easily learned should be used.
|
|||
image:models/design/systemContextDiagram.svg[]
|
||||
|
||||
== Solution strategy
|
||||
=== Quality Demand Fulfillment
|
||||
=== Quality demand fulfillment
|
||||
[options="header"]
|
||||
|===
|
||||
|Quality Demand |Solution approach
|
||||
|
@ -276,7 +276,7 @@ image:models/design/staff.svg[class design diagram - Staff]
|
|||
|
||||
|
||||
=== Link between analysis and design
|
||||
_Die folgende Tabelle zeigt die Rückverfolgbarkeit zwischen Entwurfs- und Analysemodell._
|
||||
|
||||
|
||||
[options="header"]
|
||||
|===
|
||||
|
|
Loading…
Reference in a new issue