Older version (refer to this if the above version is too messy; both the System Administrator and the Manager have access right to all the funtion in the system)
Hey. i think for use case, more think can be included. like for example, generate report.. maybe we could type in the book entity coz all report will have different format in pior to what the manager have chosen. can someone verify whether this entity should be extend or include? another is manage user.. let include add, delete and edit entity. anything else that we can include?
*Add new use case: - Manage shelving plan: - ((in)) Print shelving plan - ((in)) View shelving plan
-----------------------------------
For the refined system specs, There's some more detailed stuff to include for each section:
Sales Report: - able to generate according to wkly, mthly n yearly report.
erms, i dunno whether should we put the refined sys specs as a one whole paragraph or section them. So do post ur view. And i think tt's all i can think of.
From friday's tutorial i got an idea that the refined system is actually the use-case description of the system. So for like add user we include in to the use-case. we got to explain it in our refined system specs.
Section by section is easier for tutor to read ba.. i vote for section~ =]
Should there be a use case "shelve replenishment" in the inventory system? Cos u guys say, there'll be a low stock alert n how the manager or supervisor can stop the alert? so u guys say the clicking of btn n stuff to deactivate the alert rite? but there need to be a used case to deactivate rite? so wat should be name the use case?
Refined Version
Older version (refer to this if the above version is too messy; both the System Administrator and the Manager have access right to all the funtion in the system)
6 comments:
Hey. i think for use case, more think can be included. like for example, generate report.. maybe we could type in the book entity coz all report will have different format in pior to what the manager have chosen. can someone verify whether this entity should be extend or include? another is manage user.. let include add, delete and edit entity. anything else that we can include?
- YQ`
we have to include the shelving use case too..
so use case diagram:
Manage User
- ((in)) add user
- ((in)) delete user
- ((in)) edit user
Generate Sales Report:
- ((in)) print report
- ((in)) view report
*Add new use case:
- Manage shelving plan:
- ((in)) Print shelving plan
- ((in)) View shelving plan
-----------------------------------
For the refined system specs,
There's some more detailed stuff to include for each section:
Sales Report:
- able to generate according to wkly, mthly n yearly report.
erms, i dunno whether should we put the refined sys specs as a one whole paragraph or section them. So do post ur view. And i think tt's all i can think of.
From friday's tutorial i got an idea that the refined system is actually the use-case description of the system. So for like add user we include in to the use-case. we got to explain it in our refined system specs.
Section by section is easier for tutor to read ba.. i vote for section~ =]
-YQ`
Should there be a use case "shelve replenishment" in the inventory system? Cos u guys say, there'll be a low stock alert n how the manager or supervisor can stop the alert? so u guys say the clicking of btn n stuff to deactivate the alert rite? but there need to be a used case to deactivate rite? so wat should be name the use case?
oh.. need to add "system admin" actor, this is for maintain system.
The direction of Check Low Stock arrow connecting to Login usecase is wrong. Please edit accordingly Supei.
Post a Comment