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

Merge pull request #6 from ruimoliveira/teresa-Guilherme-patch-3

Browse Source 
Update Assignment 2.md
This commit is contained in:
ruimoliveira 2016-10-30 16:57:23 +00:00 committed by GitHub
commit 23d906ddfe
1 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
ESOF-docs/Assignment 2.md
View File

@ -24,17 +24,21 @@ They implement features when they want or when the contributors have a feature t
In future they intend to implement features like cheat code support, improve speed of cut scenes and support for smartphones. In future they intend to implement features like cheat code support, improve speed of cut scenes and support for smartphones.
Given the circumstances of this project (hobby, volunteers, low amount of time that developers have to work and inconsistent frequency of commits, specific knowledge about console hardware, emulation, among other areas) the reality of the new features is contributors of Citra contribute what they like and not always what is ideal. Given the circumstances of this project (hobby, volunteers, low amount of time that developers have to work and inconsistent frequency of commits, specific knowledge about console hardware, emulation, among other areas) the reality of the new features is contributors of Citra contribute what they like and not always what is ideal.
** Specific Requirements and Features ** ** Specific Requirements and Features **
Specific Requirements and Features (Functional and Non-Functional requirements)
>Grade: 5pts As stated above, a functional requirement specifies something the system should do (describes how a function should behave). For example: the box of a game must be able to contain the pieces of the game without losing them.
On the other hand, a non-functional requirement describes how the system behaves (a constraint on the system behaviour).
For example: the box of a game must be made of leather.
//to be completed
**Use Cases** **Use Cases**
These are the uses we could figure out for both the application. These are the uses we could figure out for both the application.
![alt tag](http://i.imgur.com/deDgtE4.png) ![alt tag](http://i.imgur.com/deDgtE4.png)
Domain Model **Domain Model**
>Grade: 6 pts
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:
![alt tag](http://icecream.me/uploads/d3285a245af38b0a7e8def42c7fe5cb0.png)