Documente Academic
Documente Profesional
Documente Cultură
ST1:
ST2:
ST3:
ST4:
ST5:
name
name
name
name
name
student
student
student
student
student
1:
2:
3:
4:
5:
Jeremy De Wit
Ronald Michiels
Geert Van De Abbeele
Glenn Lorenzet
/
Max Score ST1 ST2 ST3 ST4 ST5
scor
e
2
1
1
0
/
Assignme Scope/Probl
5
nt 1
em/busines
s analysis
1
2
1
1
/
Assignme Requireme
5
nt 2
nt analysis/
context
2
2
2
0
/
Assignme Requireme
5
nt 3
nt
analysis/Us
e case
description
1
2
1
0
/
Assignme
Usecase
5
nt 4
realisation
Datamodelli
ng
Total group score
20
% time allocation per
student
Student score
30%
40%
30%
0%
20
Assignment1
Finishing date assignment: 26/11/2015
Tasks performed
ST1
Problem Statement Matrix
Problem Description (PIECES): one
Business Use Case Diagram
Activity Diagram
ST2
Problem Statement Matrix
Problem Description (PIECES): two
Business Use Case Diagram
Activity Diagram
Business Class Diagram
ST3
The Product Vision
Problem Description (PIECES): one
Business Use Case Diagram
Activity Diagram
ST4
ST5
Assignment2
Finishing date assignment: 3/12/2015
2
Tasks performed
ST1
List Of Stakeholders and Actors
List of Business Rules
List of Quality Attributes (non-funcitonal requirements)
Main Use Case Diagram
ST2
Event Response List
Context Diagram
List of Stakeholders and Actors
List of business Rules
List of Quality Attributes (non-funcitonal requirements)
Main Package Diagram
Main Use Case Diagram
ST3
Event Response List
List of Business Rules
List of Quality Attributes (non-funcitonal requirements)
Use Case List with Ranking
Main Package Diagram
ST4
ST5
Remarks (which parts of the assignment are not finished
or partly finished)
We finished all parts of assignment 2.
Assignment3
Finishing date assignment: 10/12/2015
Tasks performed
ST1
3
ST5
Assignment4
Finishing date assignment: 17/12/2015
Tasks performed
ST1
Operation Contacts
4
ST5
Table of Contents
1. Assessment Sheets
............................................... 1
5
2. Table of Contents
6
3. Product Vision Document (Assignment 1)
. 7
4. Problem Statement Table (Assignment 1)
. 8
5. Problem Description PIECES (Assignment 1)
9
6. Business Use Case Diagram (Assignment 1)
. 11
1. Activity Diagram Business Use Case (Assignment 1)
.. 12
7. Business Class Diagram (Assignment 2)
.. 13
1. Event response list (use case list) (Assignment 2)
14
8. Context Diagram (Assignment 2)
.. 17
9. Description data flows (Assignment 2)
. 18
10. List stakeholders/actors (Assignment 2)
. 19
11. List business rules (Assignment 2)
20
12. List quality attributes (non-functional requirements) (Assignment 2) ..
21
13. Use case list with ranking (Assignment 2)
.. 22
14. Main use case diagram (package diagram) (Assignment 2)
23
15. System use case diagram for one package (Assignment 2)
. 24
16. Flow of Events for Order meal from Cafeteria (word) (Assignment 3)
25
17. Flow of Events for Order meal from Cafeteria (Vis. Par.) (Assignment 3).
27
18. User stories (4 phases) + mock ups UeXceler screen shots (Assignment 3)
30
19. Activity diagram for use case order meal from cafeteria (Assignment 3)
40
20. Domain class diagrams for order meal from cafeteria (Assignment 3)
..41
21. CRUD-Matrix (Assignment 3)
41
22. State chart diagram for domain class Order (Assignment 3)
. 43
23. System sequence diagram for order meal from cafeteria (Assignment 3)
.. 44
6
Product
Value
Urgen
cy
Visibilit
y
Priorit
y or
Rank
Proposed
Solution
ASAP
High
New Development
2
month
s
Medium
After New
Development
provide tracking
abilities to the
program so that
we know what the
employees want
most.
2
month
s
Medium
After New
Development
provide tracking
abilities to the
program so that
we know how
many mployees
buy what product.
Future ability for employees to order meals for
delivery from local restaurants would make a
wide range of choices available to employees.
8
month
s
Low
New Development
8
month
s
Low
Van De Abbeele)
Employees at the company Process Impact presently spend an average of 65 minutes per
day going to the cafeteria to select, purchase and eat lunch.
Cause: A lot of choice, too busy, has to be "prepared" immediately after order.
Effect: Bad time-efficiency, could go faster. Ordering and purchasing
Cause: Combination of too much orders for certain food-items and the cafeteria staff not
knowing how much ingredients to order beforehand .
Effect: Certain employees are unable to order their desired food.
Opportunity: Better regulating the ordering of meals.
Benefit: Employees being able to order their desired food.
Constraint: Ordering time-gap will have to be implemented.
Possible Improvements: Better served customers and the cafeteria not running out of food.
10
11
12
13
Trigger
Source
1.Employee
wants to log in
COS Login
Request
Employee
2.Employee
wants to view
past
transactions
COS View
transactions
request
Employee
3. Employee
wants to place
order
COS Order
request
Use Case
Response
Destinatio
n
Order food
Account details
Employee
View
transactions
Transaction
Employee
Employee
Order food
details
Order
confirmation
Employee
Order details
Payrolldepartment
Transaction
Stock
Order details
4. Employee
wants to
change placed
order
Cos Change
order request
Employee
Employee
Change/Cancel
order
Change
confirmation
Payroll
14
Event
Trigger
Source
Use Case
Response
Destinatio
n
department
Updated order
details
Stock
Order details
5. Employee
wants to cancel
placed order
Cos Cancel
order request
Employee
Employee
Change/Cancel
order
Cancel
confirmation
Updated
transactions list
6. Staff selects
meal(s)
Cos Select
Top Priority
meals request
Cafeteria Staff
Select Priority
meals
List of most
urgent meals
Payroll
department
Stock
Cafeteria
Staff
Stock
7. Staff cooks
meal(s)
Priority meals
Cafeteria Staff
Cook time
Cafeteria
Prepared meal
Delivery
Staff
Prepare meals
Stock changes
8. Staff delivers
meal(s)
Prepared Meals
Address
Cafeteria
Distance
Employee
Cafeteria
Deliver meals
Delivery-time
Delivery
15
Event
9. Management
assigns staff
Trigger
COS Assign
Staff
Source
Management
Use Case
Assign Cafeteria
Staff
Response
Destinatio
n
Staff member
Cafeteria
Role
Cafeteria
Staff
Place
Workhours
Season
10.
Management
changes menu
Ingredient
prices
Day / Week
Cafeteria
New menu
Cafeteria
staff
Management
Change menu
Employee
complaints
Changes
Online
menu
Season
11.
Management
adjusts prices
Ingredient
prices
Menu
Cafeteria
Old price
Cafeteria
staff
Management
Adjust Prices
Employee
complaints
Sales
New price
Corporate
policies
Online
menu
Reason
12. Corporate
Management
changes
policies
Sales
Employee
happiness
Social pressure
Corporate
Management
Change policies
Old policies
Employees
New policies
Cafeteria
Staff
Changes
16
Context Diagram
17
18
List of Stakeholders/Actors
Stakeholder/Actor
Role
Intrests
Major Values
Employee
Customer
Ordering food
Cafeteria Staff
Supplier
Preserving jobs
Cafeteria Management
Planner
Increasing sales
Corporate Management
Decision maker
Reducing wasted
time
Improving employee
satisfactory
Payroll Departement
Payment dealer
No real intrests
No benefits
19
Rule Definition
Type
Static/Dynamic
Source
BR-1
Fact
Dynamic
Cafeteria
Manager
BR-2
Constraint
Dynamic
Cafeteria
Manager
BR-3
Constraint
Static
Cafeteria
Manager
BR-4
Constraint
Static
Cafeteria
Manager
BR11
Constraint
Dynamic
Cafeteria
Manager
BR12
Computation
Dynamic
cafeteria
policy; sta
tax code
BR24
Constraint
Static
cafeteria
policy
BR33
Constraint
Static
corporate
security
policy
BR86
Constraint
Static
Corporate
Accounting
Manager
BR88
Constraint
Dynamic
Corporate
Accounting
Manager
20
Priority
(M,S,C,
W)
Releas
e (1,2
or 3)
Create account
Place order
Update/change
order
Motivation priority
View
transactions
View orders
22
Moscow priorities
M - must haves: these use cases must be implemented in the end product;
S - should haves: these use cases should be implemented but the product
should work without them;
C - could haves: these use cases could be implemented, but are not necessary;
W - Wont haves: these use cases won't be implemented, but maybe at a later
stage in the process (update for example.).
23
24
Basic flow:
1. The use case begins when the user surfs to the COS-website.
3. The user is logged in and can now make a new order, view a list of past
transactions or edit a placed order.
4. The user chooses to place a new order.
5. The system displays the menu for that day.
6. The user selects one or more meals and their quantities as a order, and
the location where the order should be brought to.
A2: The stock has run out of ingredients to prepare one or more
meals
25
11. The order is added to the batch of orders for that day.
12. The cafeteria staff selects the order.
13. The cafeteria staff starts preparing and cooking the meal(s).
14. Once the order is ready, The delivery staff takes over. The order is
labeled "cooked"
15. The delivery staff delivers the order to the delivery-address.
16. The user receives their meal and signs the reception confirmation.
17. The order is now labeled "done"
18. The use case ends.
Alternative flows:
2. The stock has run out of ingredients to prepare one or more meals
3.
Redirect to basic 6
26
5.
The staff returns the order to the cafeteria for the user to pick up
Error flows:
27
Primary Flow
1. The user surfs to the COS-website.
1.1. E1: The COS-website is down.
2. The user logs in with his/her username and password.
2.1. A1: The user entered an incorrect username or password.
3. The user is logged in and can now make a new order, view a list of past transactions or ed
4. The user chooses to place a new order.
5. The system displays the menu for that day.
6. The user selects one or more meals and their quantities as an order, and the location whe
6.1. A2: The stock has run out of ingredients to prepare one or more meals
6.2. A3: the user chooses to save the order.
6.3. A4: The user tries to place an order on an invalid day or past 11:00 PM.
7. The system shows the total amount to pay.
8. The user clicks on "confirm" to confirm the order. The order is labeled "pending"
8.1. A5: The user chooses to cancel the order.
9. The COS-system sends the fee to the Payroll-Department, who will deduct the fee from the
9.1. A6: The user's remaining salary is too low to accommodate for the purchase.
10. When the COS-system receives a response from the Payroll - Department, the order is la
10.1. E2: The COS-system does not receive a response.
11. The order is added to the batch of orders for that day.
12. The cafeteria staff selects the order.
13. The cafeteria staff starts preparing and cooking the meal(s).
14. Once the order is ready, the delivery staff takes over. The order is labeled "cooked".
15. The delivery staff delivers the order to the delivery-address.
15.1. A7: The patron is not present at the delivery-address.
16. The user receives their meal and signs the reception confirmation.
17. The order is now labeled "done".
18. The use case ends.
28
Alternative Flow
1. A1: The user entered an incorrect username or password.
1.1. Show error message "Incorrect username/password".
1.2. Redirect to Primary Flow step 2.
2. A2: The stock has run out of ingredients to prepare one or more meals
2.1. Gray out the meals for which there are insufficient ingredients.
2.2. Display alternatives to the user.
2.3. Redirect to Primary Flow step 6.
3. A3: The user chooses to save the order.
3.1. The system saves the order for the user.
3.2. Redirect to Primary Flow step 6.
4. A4: The user tries to place an order on an invalid day or past 11:00 PM.
4.1. Display error message "unable to order: Invalid date/time".
4.2. The system proposes to save the order.
4.3. Redirect to Primary Flow step 3.
5. A5: The user chooses to cancel the order.
5.1. The system asks to confirm the cancellation
5.2. Redirect to Primary Flow step 3.
6. A6: The user's remaining salary is too low to accommodate for the purchase
6.1. The system notifies the user that his/her salary is insufficient
6.2. The system saves the order
6.3. The system cancels the order
6.4. Redirect to Primary Flow step 3.
7. A7: The Patron is not present at the delivery - address
7.1. The delivery staff notifies the user.
7.2. The staff returns the order to the cafeteria for the user to pick up.
Error Flow
1. E1: The COS-website is down.
1.1. The system displays an Error-message and recommends the retry within an hour.
2. E2: The COS-system does not receive a response
2.1. Redirect to Primary Flow step 11.
29
Login
31
32
Register
33
35
View Transactions
36
Cancel Order
37
Update Order
38
39
40
CRUD Matrix
Activities
Entities
Employe COS
e
Cafeteria
staff
CR
CU
RUD
Update existing
order
Delete existing
order
View transactions
RU
RU
RU
RD
RUD
RD
Change menu
Adjust price
Get orders
Prepare meal
RUD
CRUD
RU
RUD
RUD
RUD
RU
Deliver meal
UD
CRU
D
Corp.
Manag.
Payroll
Department
RU
CRU
D
RUD
Assign staff
Change policy
Caf.
Manag.
RU
UD
CRUD
C = Create new Data | R = Read data| U = Update existing data| D = Delete data
43
Operation Contracts
Subject: COS-System
Name
Ask for login
Responsibilities
Responding to the users request with the login-page. On this page, the user can
identify by logging in.
References
The create new order use case.
Pre conditions
44
Pre conditions
The user must be logged in
The user selected his/her food items
The user specified his/her delivery address and date/time.
Post conditions
The user can make a decision based on this information
Name
Response from Payroll-Department
Responsibilities
Process the payment of the order and report to COS-system
References
The create new order use case.
Pre conditions
The user must be logged in.
The user selected his/her food items.
The user specified his/her delivery address and date/time.
The user must have confirmed the order.
The COS-system must have sent the order details to the Payroll-Department
Post conditions
The COS-system received an answer and can proceed with the order.
The COS-system can now notify the user.
Name
Feedback: Order successfully placed
Responsibilities
Alert the user that his/her order was successfully processed.
References
The create new order use case.
Pre conditions
The user must be logged in.
The user selected his/her food items.
The user specified his/her delivery address and date/time.
The user must have confirmed the order.
Post conditions
The user received the information that his/her order is completed
The user can now return to the home-page.
Name
Respond with list of orders.
Responsibilities
Show the list of placed orders for that day.
References
The create new order use case.
Pre conditions
The Cafeteria staff must request the list
There have to be placed orders.
Post conditions
The Cafeteria staff can now select orders to prepare
Name
Change status of selected order to pending
46
Responsibilities
Update the state of the selected orders
References
The create new order use case.
Pre conditions
The orders must to be selected by the cafeteria staff
The orders must be prepared
Post conditions
The order is prepared and the state is changed to ready.
Name
Notify delivery staff
Responsibilities
Notify the delivery staff when orders are ready to transport
References
The create new order use case.
Pre conditions
The orders must be prepared
The orders must be ready for transport
The orders date has to match todays date
Post conditions
The Delivery Staff picked up the orders
Name
Confirm (successful) delivery
Responsibilities
Change the state of the delivered orders to done or revoked
References
The create new order use case.
Pre conditions
The orders must be delivered
The orders must be either accepted or declined
Post conditions
The delivered orders are marked done in case of successful delivery
The delivered orders are marked revoked in case of unsuccessful delivery
47
48
49