OpenPunk/citra
1
0
Fork 0
mirror of https://github.com/citra-emu/citra.git synced 2024-11-29 17:00:05 +00:00
Code Issues Projects Releases Wiki Activity

(incomplete) Cleanup, cont. of Spec. Req. & Feat.

Browse Source
This commit is contained in:
PORShoterxx 2016-10-30 20:20:15 +00:00 committed by GitHub
parent ffe22ef486
commit 22a0e8eef2
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
ESOF-docs/Assignment 2.md
View File

@ -1,8 +1,8 @@
**Requirements**
Before we can start building a project it is essential that the team study the costumers and user needs so the team can have a clear statement and understanding of required properties of a solution to solve the problem.
The requirements for a system are the descriptions of what the system should do, the services that it provides and the constraints on its operation.Some of the problems that arise during the requirements engineering process are a result of failing to make a clear separation between these different levels of description.
Before starting building a project, it is essential that a team studies it's costumers and user needs, so it can have a clear goal and understanding of required properties of a solution.
System requirements are descriptions of what a system should do, the services that it provides and its operation constraints. Some of the problems that arise during the requirements engineering process are a result of failing to make a clear separation between these different levels of description.
We can divide them in two: user requirements and system requirements.
User requirements are statements of what services of the system is expected to provide to system users and the constraints under which it must operate.
@ -33,11 +33,10 @@ The only hard requirements for the official version of Citra is a graphics chip
**Specific Requirements and Features**
As we said in the introduction,software system requirements are often classified as functional requirements or non-functional requirements.
The functional requirements for a system describe what the system should do.In this case a functional requerimet is having the emulator running smoothly and with no crashes.It will also include emulating the hardware spec - as the purpose of the emulator is to
to duplicate the functionality of hardware.
As previously mentioned, software system requirements are often divided into functional and non-functional.
A system's functional requirements describe what the system should do. With Citra, they include having the emulator running smoothly, with no crashes nor visible glitches. Another one is Hardware Specifics emulation - as the purpose of the emulator is to emulate the hardware's functionality.
Non-functional requirements, as the name suggests, are requirements that are not directly concerned with the specific services delivered by the system to its users.Their non-functional requirement are adhering standarts to their code and following their design process.
Non-functional requirements, as the name suggests, do not concern the actual workings of the system. In Citra's case, they manifest as code standards and matching a specific design process.