Assessment 2 Digsram

ICT103 Assessment 2 Digsram
This file shows the example of the diagrams you need to prepare for

1. Use Cases:
Use case— an activity that the system performs, usually in response to a request by
a user. Use cases define functional requirements.
Use case diagram— a UML model used to graphically show uses cases and their relationships to
actors.
Use Case Diagrams Symbols
Use Case Example

2. Activity Diagram:
Activity Diagram– describes user (or system) activities, the person who does each activity, and the
sequential flow of these activities
a. Useful for showing a graphical model of a workflow
b. A UML diagram
Activity Diagram Symbols
Activity Diagram Example

3. Sequence Diagrams:
A UML sequence diagram
Special case for a sequence diagram
Only shows actor and one object
The one object represents the complete system
Shows input & output messaging requirements for a use case
Actor, System, object lifeline
Messages
System Sequence Diagram (SSD) Notation:
System Sequence Diagram (SSD) Examples:

4. Domain Model Class Diagram:
Class
A type of classification used to describe a collection of objects
Domain Class
Classes that describe objects in the problem domain
Class Diagram
A UML diagram that shows classes with attributes and associations (plus methods if it models
software classes)
Domain Model Class Diagram
A class diagram that only includes classes from the problem domain, not software classes so no
methods
Domain Model Class Diagram Notation
Domain Model Class Diagram Examples

5. State Machine Diagram:
State Machine Diagram – a diagram which shows the life of an object in states and transitions
Origin state – the original state of an object before it begins a transition
Destination state – the state to which an object moves after completing a transition
pseudostate – the starting point in a state machine diagram. Noted by a black circle.
action-expression – some activity that must be completed as part of a transition
guard-condition – a true/false test to see whether a transition can fire
5. User Interface:

User interface design must consider
the entire user experience
Good user interfaces are based on
good design principles – visibility,
affordance, feedback, etc.
Poorly designed user interface can
make the information system
unusable
Story boards are a powerful tool for
UI design
User Interface – inputs and outputs
that directly involve a human
user/actor
A dialog goes on between actor and
system
User interface design must focus on
entire User Experience (Human
Computer Interaction –HCI)
Called User-Centered Design
Focus early on users and their work
Evaluate designs to ensure usability
Use iterative development
Usability is the objective

User Interface Design

Is the system a custom application or
browser based?
What kinds of devices will the user-interface
need to support?
What operating systems will the user
interface run on?
Data Entry
Text box, list box, combo box, radio
buttons, check boxes
Include online editing to minimize
errors
Navigation and Visibility
Minimize, maximize, close, scroll
bars, resize

Use Case Description Details
Use case name
Verb-noun
Scenario (if needed)
A use case can have more than one scenario (special case or more specific path)
Triggering event
Based on event decomposition technique
Brief description
Written previously when use case was identified
Actors
One or more users from use case diagrams
Related use cases <<includes>>
If one use case invokes or includes another
Stakeholders
Anyone with an interest in the use case
Preconditions
What must be true before the use case begins
Post conditions
What must be true when the use case is completed
Use for planning test case expected results
Flow of activities
The activities that go on between actor and the system
Exception conditions
Where and what can go wrong
Dialogue, Storyboard
For each use case, think of the natural flow of a dialog between user and computer
Based on the flow of activities in use case description and/or the system sequence
diagram
Use natural language to emphasize feedback to user
Create a storyboard of the dialog, showing the sequence of sketches of the screen each
step of the dialog. (storyboarding)
Review the storyboard with users