COMPUTER SCIENCE AND INFORMATICS

Running head: COMPUTER SCIENCE AND INFORMATICS
COMPUTER SCIENCE AND INFORMATICS
Name of the Student
Name of the University
Author Note

COMPUTER SCIENCE AND INFORMATICS
1
Table of Contents
1. Differences between domain class diagram and design class diagram:.............................2
2. Justification for a valid use case:...........................................................................................2
3. Use case diagram:..................................................................................................................3
4. Use case Specification:..........................................................................................................4
5. Sequence diagram:.................................................................................................................5
6. Domain Class diagram:..........................................................................................................6
Bibliography:..............................................................................................................................7

COMPUTER SCIENCE AND INFORMATICS
2
1. Differences between domain class diagram and design class diagram:
Domain class diagrams are the solution independent of a specific problem domain that
is produced in any project while it is in the analysis stage. Conceptual model is the name of
the domain model. A domain class diagram can describe the domain’s state and its purpose.
Basically, they are solution independent. These models are focused on the language and
domain. A domain model class diagram is used to develop in the dice game.
A design class diagram is the overview of a system. It can provide a static view of a
specific system. Design class diagram can describe the classes and objects inside of a system.
In many purpose, this diagram can be used. In this diagram, abstraction is one type of
relationship that can relate two elements. An association is a relationship that can specify the
relationship between two instances. Class diagram can provide an overview of a system by
using the name of the class and its attributes.
2. Justification for a valid use case:
All of this point can be a use case at a very different level. It is completely dependent
on the actors, system and their goals.
Place a bid:
Pass in the EBP test and boss is happy in this case.
Withdraw a bid:
Boss is not happy is this is all you can do in a day.
View Item Description:
EBP size is good in this step.
Negotiate a dispute: