In a UML use case diagram, an 'actor' represents a user or any external system that interacts with the system being modeled. In this scenario, the 'employee' is the user interacting with the system, making them the actor. A 'use case' describes a specific functionality or goal that an actor can accomplish using the system. The action 'enter time details' is the specific goal the employee wants to achieve. The 'computerised project reporting system' itself is represented by the system boundary, which is a box drawn around the use cases. Therefore, the employee is the actor and entering time details is the use case.

A. An employee is an actor, not the system boundary. Time details are data being entered, not an external entity (actor) interacting with the system.

B. The project reporting system is the system under analysis, not an actor. The employee is the actor performing an action, not the action (use case) itself.

C. The project reporting system defines the system boundary, it is not a use case. A use case is a function within the system.

1. Object Management Group (OMG). (2017). OMG Unified Modeling Language (OMG UML)

Version 2.5.1. OMG Document Number formal/2017-12-05.

Section 18.1.3

"Notation" (p. 639): Defines an Actor as "a user or any other system that interacts with the subject." It defines a UseCase as "a specification of behavior." This directly supports identifying the 'employee' as the actor and 'enter time details' as the use case.

Section 18.1.3 (p. 641): Shows the system boundary as a rectangle enclosing the use cases

separating the system from the external actors.

2. Dennis

A.

Wixom

B. H.

& Tegarden

D. (2015). Systems Analysis and Design: An Object-Oriented Approach with UML (5th ed.). Wiley.

Chapter 5

"Use-Case Modeling

" p. 136: "An actor is not a specific user but a role that a user can play... An actor is external to the system." This confirms the 'employee' is an actor.

Chapter 5

"Use-Case Modeling

" p. 138: "A use case is a formal way of representing how a business system interacts with its environment... It depicts a set of activities that the system performs to produce some output result." This confirms 'enter time details' is a use case.

3. Fowler

M. (2004). UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd ed.). Addison-Wesley.

Chapter 9

"Use Case Diagrams

" p. 101: "Actors are roles that people (or things) play... A use case is a summary of scenarios for a single task or goal." This clearly distinguishes the 'employee' (actor) from their goal

'enter time details' (use case).