FINAL HANDIN

FINAL HANDIN

Hey Guys, here is our final handin: Requirements Use Cases General Overall Use Case Diagram UC: Add Visit UC: Edit User Data UC: Manage Favorites UC: Manage Visits UC: Get Information UC: Sign up UC: View Timeline UC: Searching Software Requirements Specification (SRS) SRS Blog post for SRS Test Cases  Feature Files see in section “Functional Test”. Test Log, testcoverage Blog for Testing (Week 4) Blog for Testing (Week 7) – Testcoverage Server Testcoverage Client Testcoverage Test Plan Test Plan Functional…

Read More Read More

Week 10: Installation

Week 10: Installation

Hi, After we developed for about 1 year now, there should also be away for other people to use and install our software. Normally our application is deployed on servers, so that everybody can use it without any installation. However, if you’re tech enthusiast, you may want to deploy our software to your own server. On the client side, you’re able to deploy our software to all tomcat 8 servers running JDK-8. For further explanation check our README on GitHub…

Read More Read More

Week 9: Deploy/CI

Week 9: Deploy/CI

Hi, As the project is going to end soon, we thought about the deployment of our Application. For the client, we had automatic deployment in our CI for a long time now. The process here is, that after a successfull build on Travis CI, we’re able to automatically deploy our application to any Apache Tomcat server out there, by using the Maven tomcat8-plugin. (In our case we deployed it to our own server but it doesn’t matter which tomcat-server we…

Read More Read More

Week 8: Test Coverage Tools

Week 8: Test Coverage Tools

Hi, It’s time to show you, how we optimized our development lifecycle. On both the server and client, we use Travis CI for continious integration. We configure Travis CI by using the .travis.yml file in our Git Repos. For both we automatically run tests after every push to the master branch. Therefore we also have a badge:  Server Badge  Client Badge After the tests are run, we send the test data to coveralls, which gives us information about test coverage….

Read More Read More

Week 7: Metrics

Week 7: Metrics

Hi guys, Today we want to show you our Metrics, which we tried to improve this week. For doing Metrics we use the online Tool coday. You’re able to access our whole Metrics online for the client and the server. Let’s start with the improvements we made on the client-side. Here you can see our Metrics before Refactoring:   As you can see we had a lots of issues, which was caused by codacy checking internal files of java and compiled files, which had…

Read More Read More

Week 6: Patterns

Week 6: Patterns

Hi, We are using several patterns in our project. First we seperate the whole logic from the actual front-end, by using a backend server, which contains logic and is handling data. On both sides we use the MVC-Pattern. Especially on the server side our Framework, Django, is based on MVC and forces the developer to strictly follow this pattern. Django also forces us to use the factory pattern, as we’re defining the properties of our objects by defining their structure…

Read More Read More

Week 5: Refactoring

Week 5: Refactoring

Hello, This week, we had to do refactoring steps on a sample project by reading the book “Refactoring: Improving the Design of Existing  Code” by Fowler. Below you find the links to our repositories. Franziska Marco Your BestPlaces Team

Testing

Testing

Hi, This week we started writing tests for our application to improve our applications by finding bugs in early stage of development. To get an Overview about how we want to use and implement different testing-techniques, have a look at our Test Plan on GitHub. It’s not completly finished yet, but the key features are explained. Generally, we want to test both of our components, the server and the client. On the server-side with Django, we’re able to use the…

Read More Read More

Week 3: Function Points

Week 3: Function Points

Hello, this week we calculated the Function Points for our Use Cases. In the following table, you can see in blue our done use cases and the time we needed for them. Here we suspended the warmup time, because of unrealistic estimations when estimating the new tasks depending on the done tasks. Additionally the warmup time can’t be assigned to a single Use Case. In red there are the new Use Cases and the estimation of time we will spend on…

Read More Read More

Week 1 + 2: New Scope, new Use Cases, Hours Spent and Risk Management

Week 1 + 2: New Scope, new Use Cases, Hours Spent and Risk Management

Hello, After a break of development, we defined a new Scope. We will do everything what has to do with the Search and the Timeline (orange). So this are our new Use Cases: GetInformation (Choose Place) https://github.com/anonfreak/bestplaces/blob/master/doku/PlacesView/UseCaseDocumentPlacesView.md View Timeline https://github.com/anonfreak/bestplaces/blob/master/doku/ViewTimeline/UseCaseSpecificationViewTimeline.docx.pdf Manage Visits https://github.com/anonfreak/bestplaces/blob/master/doku/ManageVisits/UseCaseSpecificationManageVisitsCrud.docx.pdf Add Visit https://github.com/anonfreak/bestplaces/blob/master/doku/AddVisit/AddVisit.md To be better prepared for the next Use Cases, we gather information about how much time we spent on which Use Case and for what, like documentation, development and so on. In this table…

Read More Read More