Home

 

 Stakeholders Stakeholder Roles Goals System Context Glossary Domain Models

 

 Personas Scenarios

 

 Functional Requirements Non-functional Requirements Priorization

 

 Use Case Diagrams Use Cases User Stories

 

 Formal Reviews Overview Authors (with Artefacts)

 

 Interviews Workshops Surveys Documents & Literature

 

 FAQ Tutorial Version

Author »Stefan Steinhauer«

"I work at Kunstwerk and I am part of the fictional development team "CodingPandas"."

All Artifacts

All artifacts (co-)created by Stefan Steinhauer are listed below. If there are co-authors, they are listed as well.

ID Artifact Co-Author(s)
  DOM-2 Food State Diagram Marc Kevin Zenzen
  DOM-1 All business objects of YumShare Marc Kevin Zenzen
  FR-1 Adding a product to an order Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-13 Place advertisings in the app. Marc Kevin Zenzen und Tristan Schmele
  FR-2 Checking personal information provided by the user during account creation Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-3 Comment on a supplier profile Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-4 Creating a new offer as a supplier Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-5 Creating posts in the community area Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-7 Deleting posts in the community area Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-8 Editing personal information on a user profile Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-9 Estimate time for delivery Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-10 Fill in the address for delivery Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-11 Logging out a logged in user Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-12 Open Communityaccess for all users Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-16 Providing personal information on account creation Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
FR-14 Provide an address for delivery Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-17 Rate the supplier after a successful delivery Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-18 Removing a product from an order Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-19 Resetting a forgotten password Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-20 Select a desired time for delivery Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-21 Select a payment provider to complete an order Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-15 Providing a summary of an order Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-0 Add a new warehouse to the delivery network Marc Kevin Zenzen
FR-0 Available subscriptions for users to get access to more content. Marc Kevin Zenzen
  FR-22 Updating posts in the community area Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-23 Validating login data entered by the user Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  FR-24 View the public profile of a supplier Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
  GO-1 Account Management
  GO-2 Community functionality Marc Kevin Zenzen
  GO-3 Delivery Network Marc Kevin Zenzen
  GO-4 Distribute food products Marc Kevin Zenzen
  GO-5 Food Search and Order Marc Kevin Zenzen
  GO-6 Prompt delivery Marc Kevin Zenzen
  GO-7 Quality Assurance Marc Kevin Zenzen
  GO-8 Raising Awareness Tristan Schmele und Marc Kevin Zenzen
  GO-9 Revenue stream Marc Kevin Zenzen
INT-1 Interview with »YumShare« Tristan Schmele, Marc Kevin Zenzen, und Marius Scherff
LIT-2 Team C (2022-04-29): Requirement Text Marc Kevin Zenzen
  PRS-1 Akua Botha Marc Kevin Zenzen
  PRS-3 Bob Hofmann Marc Kevin Zenzen
  PRS-5 Julia Milovic Marc Kevin Zenzen
  PRS-6 Peter Lance Marc Kevin Zenzen
  PRIO-1 Selecting a small number of functional requirements to start a first pilot project Marc Kevin Zenzen
  SCN-3 Looking for a solution to not waste leftovers Marc Kevin Zenzen
  SCN-5 Save false orders from being wasted Marc Kevin Zenzen
  SCN-7 Using YumShare App to offer leftovers easily Marc Kevin Zenzen
  SCN-6 Saving natural vegetables with a short lifecycle Marc Kevin Zenzen
ST-1 Alex Fischer Marc Kevin Zenzen
ST-2 Cologne Marc Kevin Zenzen und Marius Scherff
ST-3 Cologne Marc Kevin Zenzen und Marius Scherff
ST-0 Lieferando (group) Marc Kevin Zenzen
ST-0 Team B (group) Marc Kevin Zenzen und Marius Scherff
ST-4 YumShare (group) Marc Kevin Zenzen
  STR-1 Administrator Marc Kevin Zenzen
  STR-2 Business Administrator Marc Kevin Zenzen
  STR-4 Investor Marc Kevin Zenzen
STR-6 Technical Administrator Marc Kevin Zenzen
ST-0 PayPal (group) Marc Kevin Zenzen
ST-0 Health Department (group) Marc Kevin Zenzen
ST-0 TooGoodToGo (group) Marc Kevin Zenzen
UC-1 Add item to shopping cart
UC-2 Choose a desired time for delivery
UC-3 Complete Checkout
UC-7 Select a payment provider for online payment
  UCD-1 Use case diagram for functional requirement »Open Communityaccess for all users« Marc Kevin Zenzen
UCD-2 Use case diagram for functional requirement »Adding a product to an order« Marc Kevin Zenzen
WS-1 Collecting ideas for YumShare app from sponsor and supplier perspective Marc Kevin Zenzen und Tristan Schmele
GL-1 Area Marc Kevin Zenzen
GL-2 Blog Marc Kevin Zenzen
GL-3 Community Marc Kevin Zenzen
GL-4 Customer Marc Kevin Zenzen
GL-5 Delivery Marc Kevin Zenzen
GL-6 Donation Marc Kevin Zenzen
GL-7 Driver Marc Kevin Zenzen
GL-8 Fee Marc Kevin Zenzen
GL-9 Food Marc Kevin Zenzen
GL-10 Post Marc Kevin Zenzen
GL-11 Price Marc Kevin Zenzen
GL-12 Quality Marc Kevin Zenzen
GL-13 Route Marc Kevin Zenzen
GL-14 Supplier Tristan Schmele und Marc Kevin Zenzen
GL-15 User Marc Kevin Zenzen
GL-16 Warehouse Marc Kevin Zenzen
GL-17 Waste Marc Kevin Zenzen

30 Error messages für Stefan Steinhauer

Error messages Artefakt
e052: There is no reference for customerOrginsation. ST-2
e091: Illegal SourceType. The source format is [sourceType, sourceRef, comment]. SourceType can be 'literatureReference', 'interview', 'workshop' or 'survey'. ST-2
e092: There is no reference for Min. 00:03:07. ST-2
e532: Invalid subtype found (allowed are 'person' and 'group'): ST-2
e091: Illegal SourceType. The source format is [sourceType, sourceRef, comment]. SourceType can be 'literatureReference', 'interview', 'workshop' or 'survey'. ST-3
e092: There is no reference for Min. 00:03:07. ST-3
e532: Invalid subtype found (allowed are 'person' and 'group'): ST-3
e052: There is no reference for compeditor. ST-0
e052: There is no reference for developer. ST-0
e052: There is no reference for paymentserviceProvider. ST-0
e052: There is no reference for legalRegulations. ST-0
e052: There is no reference for compeditor. ST-0
e052: There is no reference for developer. WS-1
e052: There is no reference for developer. GL-1
e052: There is no reference for developer. GL-2
e052: There is no reference for developer. GL-3
e052: There is no reference for developer. GL-4
e052: There is no reference for developer. GL-5
e052: There is no reference for developer. GL-6
e052: There is no reference for developer. GL-7
e052: There is no reference for developer. GL-8
e052: There is no reference for developer. GL-9
e052: There is no reference for developer. GL-10
e052: There is no reference for developer. GL-11
e052: There is no reference for developer. GL-12
e052: There is no reference for developer. GL-13
e052: There is no reference for developer. GL-14
e052: There is no reference for developer. GL-15
e052: There is no reference for developer. GL-16
e052: There is no reference for developer. GL-17

13 für Stefan Steinhauer

Artefakt
w090: There are no sources for this artefact! FR-0
w005: More than 3 authors (field 'author') - is that on purpose? INT-1
w534: Is there no interview for this stakeholder? ST-1
w007: The acronym should match the filename - that is not the case. Acronym: foodsorescologne, Filename: foodstoresCologne.md ST-2
w534: Is there no interview for this stakeholder? ST-2
w007: The acronym should match the filename - that is not the case. Acronym: cityogcologne, Filename: inhabitantsCologne.md ST-3
w534: Is there no interview for this stakeholder? ST-3
w534: Is there no interview for this stakeholder? ST-0
w534: Is there no interview for this stakeholder? ST-0
w554: For this stakeholder role, there is no stakeholder! STR-6
w534: Is there no interview for this stakeholder? ST-0
w534: Is there no interview for this stakeholder? ST-0
w534: Is there no interview for this stakeholder? ST-0

53 Todos für Stefan Steinhauer

Todos Artefakt
(sb) Your FRs are pretty "fine-granular". This is a good example of this. I doubt that you can achieve "completeness" on such a detailed level. FR-14
(tsc) I am unsure about the issues with fine-granularity. Left unchanged due to time constraints. FR-14
add sources FR-0
add Additional Information INT-1
(sb) You quote this source many times. The author is listed as "Team C", but in other sources the team is called "YumShare". Please harmonize this (also in the stakeholder list). LIT-2
add sources ST-1
(sb) some more details, about the relevance? Does that person exist? ST-1
add sources ST-2
add profile ST-2
(sb) see inhabitantsCologne ST-2
add sources ST-3
add profile ST-3
(sb) This is really a little broad. You should rather restrict this to real groups or people you talked to. ST-3
add sources ST-0
add profile ST-0
(sbe) Per definition, a stakeholder is someone (or an organisation / group) who takes an interest in the system to be developed, or is a potential user. Both is not the case here - this belongs rather to the the system context. ST-0
add sources ST-0
add profile ST-0
(sbe) That is your team, right? You are business analysts. You don't appear at all here. You just write the stuff ;-) ST-0
add sources ST-4
add profile ST-4
(sbe) Aren't team C the founders? Not the investors? ST-4
(sbe) You should list the real names here (or use nicknames). You have 4 concrete people here. Or, alternatively, list the startup name as a group. ST-4
add Profile STR-6
add sources ST-0
add profile ST-0
(sbe) Per definition, a stakeholder is someone (or an organisation / group) who takes an interest in the system to be developed, or is a potential user. Both is not the case here - this belongs rather to the the system context. Interface to Paypal will be a classical B2B interface. ST-0
add sources ST-0
add profile ST-0
(sbe) Per definition, a stakeholder is someone (or an organisation / group) who takes an interest in the system to be developed, or is a potential user. Both is not the case here - this belongs rather to the the system context. ST-0
add sources ST-0
add profile ST-0
(sbe) Per definition, a stakeholder is someone (or an organisation / group) who takes an interest in the system to be developed, or is a potential user. Both is not the case here - this belongs rather to the the system context. ST-0
(sb) "Trigger" is the motivation to start the UC. Your trigger is rather a description of the overall process. Trigger would rather be "User is hungry" or similar. UC-1
(sb) Precondition - what does "User is located in the food products page." mean? UC-1
(sb) Please use user happiness test. Can the user walk away happily after just having placed the item in the cart? Why not completing the purchase? UC-1
(sb) "Trigger" is the motivation to start the UC. Your trigger is the first step! This is the case in more or less all UC, so I remark it only here - please check the others yourself. UC-2
(sb) Precondition - what does "User is located in the "purchase now" page" mean? UC-2
(sb) Please use user happiness test. Can the user walk away happily after the use case? IMHO too small. UC-2
(sb) Consider combining with "addToCart". UC-3
(sb) Step 4 is actually 2 steps. Should be an extension point to other use cases. UC-3
(sb) Again, a bit small. Consider combining with addToCart. UC-7
(sb) Exception 2 is like "changes his mind without reason". This is of course "always true", but also a bit trivial. Can you think of practical reasons why he changes his mind? Otherwise I recommend removing this exception. UC-7
(sb) Exception 1 - why no connection? Payment provider API not available? UC-7
functionalRequirement? UCD-2
(sb) diagram link broken UCD-2
cant say why the link doesnt work, tried different syntax but keeps not working UCD-2
add intention WS-1
add referenceGroupDefinition WS-1
add approachedBy WS-1
add description WS-1
add additionalDocuments WS-1
update content WS-1