From fd98a494ddcc805faa560357e111453dedc03034 Mon Sep 17 00:00:00 2001 From: teresa-Guilherme Date: Wed, 12 Oct 2016 11:26:39 +0100 Subject: [PATCH] Update Assignment 1.md process description #1 --- ESOF-docs/Assignment 1.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/ESOF-docs/Assignment 1.md b/ESOF-docs/Assignment 1.md index 7a8fd7f65..cacf8116d 100644 --- a/ESOF-docs/Assignment 1.md +++ b/ESOF-docs/Assignment 1.md @@ -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**