Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 6 (FUNCTIONAL MODEL) (USE CASE (CRUD (READ, UPDATE, CREATE, DELETE…
CHAPTER 6 (FUNCTIONAL MODEL)
USE CASE
def use case: an activity that the system performs, usually in response to a request by a user
functional requirements
technique
Event decomposition technique
(Comprehensive and Complete)
Event– something that occurs at a specific time and place, can be described, and should be remembered by the system
3 type :
External Event (an event that occurs outside the system, usually initiated by an external agent or actor)
checklist
External agent or actor wants something resulting in a transaction
External agent or actor wants some information
External data changed and needs to be updated
Management wants some information
Temporal Event(an event that occurs as a result of reaching a point in time)
Internal outputs needed at points in time
External outputs needed at points of time
State Event (an event that occurs when something happens inside the system that triggers some process)
benefits :
Events are broader than user goal: Capture temporal and state events
Help decompose at the right level of analysis: an elementary business process (EBP)
EBP is a fundamental business process performed by one person, in one place, in response to a business event
Uses perfect technology assumption to make sure functions that support the users work are identified
user goal technique
7 step :(simple and effective)
Review the completed list with each type of user and then with interested stakeholders
Identify where different types of users need the same use cases
Look for duplicates with similar use case names and resolve inconsistencies
Create a list of preliminary use cases organized by type of user
For each type of user, interview them to find a list of specific goals
Further classify potential users by organizational level (e.g., operational, management, executive)
Classify the potential users in terms of their functional role (e.g., shipping, marketing, sales)
Identify all the potential users for the new system
CRUD
READ
UPDATE
CREATE
DELETE
create a matrix of use cases and domain classes
Brief Use Case Descriptions
UCD (a UML model used to graphically show uses cases and their relationships to actors)
STEP :
Identify all the stakeholders and users who would benefit by seeing a use case diagram
Determine what each stakeholder or user needs to review in a use case diagram
For each potential communication need, select the use cases and actors to show and draw the use case diagram
Each use case diagram and then note how and when the diagram should be used to review use cases with stakeholders and users