OpenPunk/citra
1
0
Fork 0
mirror of https://github.com/citra-emu/citra.git synced 2024-11-26 10:50:06 +00:00
Code Issues Projects Releases Wiki Activity

Update

Browse Source
This commit is contained in:
ruimoliveira 2016-10-30 17:43:29 +00:00 committed by GitHub
parent 986b9b1d29
commit ffe22ef486
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
ESOF-docs/Assignment 2.md
View File

@ -43,11 +43,15 @@ Non-functional requirements, as the name suggests, are requirements that are not
**Use Cases** **Use Cases**
An use case diagram represents the user's interactions with the system, identifying the different users of the system and different use cases. An use case lists the action/s for a user to achieve a certain goal. This should be as simple as possible, capturing all requirements from a user's perspective in order to facilitate understanding. The use cases describes what Citra does from a user’s perspective. Since we are not dealing with a game, but an actual emulator, the nuances of certain game features are not the concern of this model. Although very simple, these are the uses cases for Citra Emulator.
Below, there is a simple way to demonstrate use cases for Citra Emulator:
![alt tag](http://i.imgur.com/deDgtE4.png) ![alt tag](http://i.imgur.com/deDgtE4.png)
| Actor(s) | Use Case(s) | Brief Explanation |
| --- | --- | --- |
| Indie Developer & Gamer | Emulate Game | This is the core feature of an emulator, no explanation required. |
| Indie Developer | Debug | A developer should be able to debug his game on Citra. |
| Gamer | Save Game & Load Game | Although some (if not all) games already come with a save/load game feature, some emulators allow users to save the state of the emulation. |
**Domain Model** **Domain Model**
Domain model is a conceptual model of the domain that incorporates both behavior and data. Its purpose is to connect Use Case Model with Software Design Model. Since this emulator is such a simple concept, and the problem domain is rather small, there really isn't the need for real world classes. With this in mind we decided, that this would be the domain model for the project: Domain model is a conceptual model of the domain that incorporates both behavior and data. Its purpose is to connect Use Case Model with Software Design Model. Since this emulator is such a simple concept, and the problem domain is rather small, there really isn't the need for real world classes. With this in mind we decided, that this would be the domain model for the project: