|
54 | 54 | | 43 | Delete Issue | All users | On the bottom right of the edit issue modal (#42), a button named "Delete Issue" is located. Click it and this issue will be deleted from this task's list of issues. This has to be the best action of every developer using this application!!! |
|
55 | 55 | | 44 | Go back to Homepage (#11) | All users | Click the "DEVils-Scrum-Tool" logo on the top left of the navigation bar. |
|
56 | 56 |
|
| 57 | + |
57 | 58 | ## Non-Functional Requirements
|
58 | 59 |
|
59 | 60 | | # | Category | Title | Description |
|
|
72 | 73 | | 12 | Usability | Minimalistic Design | The user interface follows minimalistic design: 1. The interface is easy to get used to. 2. Lots of text is avoided. 3. Easy and straightforward navigation between main pages. |
|
73 | 74 | | 13 | Maintainability | Modularity | The code is built in modules, so that independent parts accomplish independent tasks. This is accomplished through the use of spring boot framework on back-end, while lots of components have been implemented on front-end, using Vuejs. |
|
74 | 75 | | 14 | Maintainability | Layered Application Design | Application consists of different layers like Presentation Layer (front-end, Vuejs), Business Layer (back-end, Spring Boot) and Data Layer (JPA-Hibernate on a PostgreSQL Database). (3-Tier) |
|
75 |
| -| 15 | Testability | Unit & Integration Testing | Both on front-end (Jest) and back-end (JUnit & Mockito) testing is implemented. On back-end, integration tests are implemented using an In-Memory embedded database with preloaded data. | |
| 76 | +| 15 | Testability | Unit & Integration Testing | Both on front-end (Jest) and back-end (AssertJ & Mockito) testing is implemented. On back-end, integration tests are implemented using an In-Memory embedded database with preloaded data. | |
76 | 77 | | 16 | Reliability | Free of Bugs with Safe Operations | During development, extensive testing and fixes on bugs have taken place, so as we are convinced that there will not be any problems during application usage. Moreover, a special care has been given on safe database operations, as use of transactions and foreign keys eliminate the possibility of a fatal data error. |
|
77 | 78 | | 17 | Performance | AJAX Calls | AJAX-based asynchronous model is used for client - server communication, minimizing the pages reloads. |
|
78 |
| -| 18 | Portability | Environment Independence | The prerequisites that the application needs to run is Java 11 for back-end and nodejs for front-end, as a result, a great portability is secured. Moreover, by using docker, our application's portability is even more extensive, as there are Dockerfiles (along with instructions) to deploy front-end, back-end and database into independent containers. | |
79 |
| -| 19 | Extensibility | RESTful Architecture | A RESTful API has been created (and documented), which could be used in a future extension of our platform to a mobile application (Android, IOS) without many changes. | |
80 |
| -| 20 | Extensibility | Documentation | A complete documentation comes with this application, which helps developers to understand and develop even more the application's code. Design diagrams, Requirements Specification, Site Map and REST API are provided along with source code. | |
81 |
| -| 21 | Deployment | Deploy on (remote) server | The application is deployed for production in Heroku. For development an embedded Tomcat server (coming with Spring Boot) is used, while also containerization is another available option, with the use of docker. Both files and deploying instructions are given in client and server README files. | |
82 |
| -| 22 | Availability | Percentage of Accessibility | As this application is deployed on a free (hobby) Heroku host, the availability is not the best possible. Heroku servers go to idle 20 minutes after the last AJAX request, so it will be a bit slow on the first access. Also there is usual database maintenance, so the server may be off for some minutes. | |
83 |
| -| 23 | Cost | Total Free!! | It is strongly suggested that if a developers team wants to use this application, to fork it and deploy it on their own Heroku account, using a hobby account. In this way, not only they will have their private online tool, with no other users (improving the performance), but also use a simple yet powerful open source Scrum tool application totally FREE OF CHARGE!! | |
| 79 | +| 18 | Performance | Pagination | On index page, the project that user participates in are presented (both current and done). To avoid loading all projects together, pagination is used, as both current and done projects are retrieved from database by groups of 4 each time by increasing deadline order (depending on the page loaded each time). | |
| 80 | +| 19 | Portability | Environment Independence | The prerequisites that the application needs to run is Java 11 for back-end and nodejs for front-end, as a result, a great portability is secured. Moreover, by using docker, our application's portability is even more extensive, as there are Dockerfiles (along with instructions) to deploy front-end, back-end and database into independent containers. | |
| 81 | +| 20 | Extensibility | RESTful Architecture | A RESTful API has been created (and documented), which could be used in a future extension of our platform to a mobile application (Android, IOS) without many changes. | |
| 82 | +| 21 | Extensibility | Documentation | A complete documentation comes with this application, which helps developers to understand and develop even more the application's code. Design diagrams, Requirements Specification, Site Map and REST API are provided along with source code. | |
| 83 | +| 22 | Deployment | Deploy on (remote) server | The application is deployed for production in Heroku. For development an embedded Tomcat server (coming with Spring Boot) is used, while also containerization is another available option, with the use of docker. Both files and deploying instructions are given in client and server README files. | |
| 84 | +| 23 | Availability | Percentage of Accessibility | As this application is deployed on a free (hobby) Heroku host, the availability is not the best possible. Heroku servers go to idle 20 minutes after the last AJAX request, so it will be a bit slow on the first access. Also there is usual database maintenance, so the server may be off for some minutes. | |
| 85 | +| 24 | Cost | TOTAL FREE!! | It is strongly suggested that if a developers team wants to use this application, to fork it and deploy it on their own Heroku account, using a hobby account. In this way, not only they will have their private online tool, with no other users (improving the performance), but also use a simple yet powerful open source Scrum tool application totally FREE OF CHARGE!! | |
0 commit comments