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

Update Assignment 1.md

Browse Source 
process description #1
This commit is contained in:
teresa-Guilherme 2016-10-12 11:26:39 +01:00 committed by GitHub
parent 7f949e8c99
commit fd98a494dd
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
ESOF-docs/Assignment 1.md
View File

@ -6,14 +6,8 @@ As described in the Read Me file, Citra is an open-source and passion driven Nin
**Development Process**
Incremental development and delivery
• Develop the system in increments and evaluate each
increment before proceeding to the development of the
next increment
• Evaluation done by user/customer proxy
• Some of the increments can be deployed to end-users
• The waterfall model can be followed in each increment
• Normal approach used in agile methods
>Citra is being developed as an hobby for several programmers and their work schedule on this Open Source Software Project is not very consistent. They are not supported by any company, therefore they don't have a deadline to implement features. Citra has a team of experiences developers that help (begginer/intermediate level) new contributtors with the standard level of code that is to be commited. They take a while to accept pull requests, so that they are certain that the pull has the quality they require, in order to avoid bugs or setbacks.
>Since the contributes frequency is inconsistent, they can't use any industrial-standard engeneering process. They "are constantly working on new features" (said by one of the project leaders) so it would be considered an Incremental development process. However as they don´t have any kind of deadlines and they only merge when they are sure the feature is operating correctly, we think they are also using a Slow programming process.
**Opinions, Critics and Alternatives**