REQ3.1: Any registered user can create a new auction.
REQ3.2: When creating an auction, the system registers the following information:
• The user that creates the auction (this user is also called the seller).
• The title of the auction
• The description of the item(s) to sale.
• The minimum price. (Other users should bid an amount higher than the minimum price.)
• The deadline: the end date and time for the auction. The minimum duration of an auction is 72 hours from the moment it is created. The expected format for the date should be clearly specified in the above deadline input field.
REQ3.3: the user must be asked for a confirmation before creating a new auction.
REQ3.3.1: a confirmed auction will be stored in the system
REQ3.3.1: an unconfirmed auction will NOT be stored in the system
REQ3.4: The system must confirm by email to the seller that an auction has been created.
REQ3.5 (optional): the email message includes a special link which would allow the seller to modify the description of the created auction without logging.
The lifecycle of an auction is as follows:
• Active: Once an action has been created, it becomes active until its deadline or until it is banned.
REQ3.6 A user (not the seller) can bid on an active auction.
REQ3.7 An administrator can ban an active auction.
REQ3.8 The seller can update the description of the auction.
• Banned: An active auction can be banned by an administrator as described by UC7.
• Due: After the auction end date, the auction is due for adjudication.
• Adjudicated (see UC8): A due action has been processed by the system and the winner has been selected from all the bidders.
[x] REQ3.3: the user must be asked for a confirmation before creating a new auction.
[x] REQ3.3.1: a confirmed auction will be stored in the system
[x] REQ3.3.1: an unconfirmed auction will NOT be stored in the system
[ ] REQ3.4: The system must confirm by email to the seller that an auction has been created.
[ ] REQ3.5 (optional): the email message includes a special link which would allow the seller to modify the description of the created auction without logging.
REQ3.1: Any registered user can create a new auction. REQ3.2: When creating an auction, the system registers the following information: • The user that creates the auction (this user is also called the seller). • The title of the auction • The description of the item(s) to sale. • The minimum price. (Other users should bid an amount higher than the minimum price.) • The deadline: the end date and time for the auction. The minimum duration of an auction is 72 hours from the moment it is created. The expected format for the date should be clearly specified in the above deadline input field. REQ3.3: the user must be asked for a confirmation before creating a new auction. REQ3.3.1: a confirmed auction will be stored in the system REQ3.3.1: an unconfirmed auction will NOT be stored in the system REQ3.4: The system must confirm by email to the seller that an auction has been created. REQ3.5 (optional): the email message includes a special link which would allow the seller to modify the description of the created auction without logging.
The lifecycle of an auction is as follows: • Active: Once an action has been created, it becomes active until its deadline or until it is banned. REQ3.6 A user (not the seller) can bid on an active auction.
REQ3.7 An administrator can ban an active auction.
REQ3.8 The seller can update the description of the auction. • Banned: An active auction can be banned by an administrator as described by UC7. • Due: After the auction end date, the auction is due for adjudication. • Adjudicated (see UC8): A due action has been processed by the system and the winner has been selected from all the bidders.