W9: Gantt Chart

necoproject5 Comments

Hi there,

this week we worked on our Gantt Chart showing all the work we have done so far. Because we are using Jira for issue tracking, we could export the task list as a comma-separated values (CSV) file quite intuitive. However, we failed at importing this file into MS Project, as it doesn’t recognizes the file’s format.

Furthermore we started working with Jira quite at the mid of our projects first part, therefore we had to add tasks, that we did before we used Jira.

The export of the Gantt Chart was also quite unhandy, because fitting it into an A4 PDF file was possible, but you need to zoom in realy deep. So if you have MS Project installed, it is better to take a look at our original MPP file, which you can download here.

Otherwise, you can find the PDF version here on our Github, preferably you download it to be able to zoom in properly.

For us a Gantt Chart isn’t quite good at telling us how long we spent on what task or phase. As we are not using any time tracking tool, therefore we depend on our Jira Sprints for time management. Logging work in Jira is for us a good overview of our workload. At the sprint overview you can also see how long you spent on an issue and what you were doing in the past, and are currently doing.

Best regards,
Team NeCo

W9: Gantt Chart

W7: Class Diagram

necoproject10 Comments

Hi everyone,

this week we created a first version of our class diagrams.

The class diagram uses Visual Studios class diagram creation tools. First we created the C# code and then generated a diagram. We used as mentioned the Visual Studio toolkit for generating it automatically.
These diagram is a first versions, we will adapt and improve it while working at our project, so it will change in time. You can inform about the progress at our Software Architecture Document which also describes our project more in detail.

We also added our class diagram to our Software Architecture Document.


Best Regards

The NeCo Team

W7: Class Diagram

W6: Gherkin .feature files

necoproject7 Comments

Hi there,

this week we advanced a step further into Behavior Driven Development, therefore we wrote .feature files for some of our Use Cases.

You can find those files right here:

  1. Feature “Chat“
  2. Feature “Chat Local“

Furthermore we added these feature files in our Use Case Specifications.

  1. Use Case “Chat“
  2. Use Case “Chat Local“

For a better syntax highlighting in Visual Studio we used the plugin “SpecFlow VsIntegration”. The screenshot below shows additionaly the autocompletion.

Bild1

W6: Gherkin .feature files

W5: Scrum & Prototype

necoproject5 Comments

This week we dealt with project management tools and scrumming.

For our project, we decided to use the tool Jira from Atlassian.

We’ve also created our first sprint , which you can see on our Jira scrumboard or on the screenshot below. Here you can see the actual status of our sprint.

s

 

The contains 5 basic tasks, assigned to a member of our team for processing.

Therefore we also defined our sprint length to 2 weeks.

 

We’ve also uploaded our first prototype of the NeCo App this week. You may look into it on our GitHub repository. The screenshot might give you a feeling, of how the app will look like.

s

You can find our prototype here

And our Scrumboard here

If you have any ideas or thougts on our process on the project, feel free to comment here.

W5: Scrum & Prototype

W2: Team Roles & Technologies

necoproject5 Comments

Team Roles

Here are our Team Roles defined, according to the RUP Model.

Each role comes with certain responsibilities.

Front-End-Developer: Maurice Heumann

  • Responsible for
    • Client development
    • UI/UX development

Server-Administrator: Mirko Müller

  • Responsible for
    • Server- and Infrastructure security

Project Manager: Alexander Rengers

  • Responsible for
    • Creating business cases
    • Planing, tracking and managing risks

Business Process Analyst: Alexander Rengers

  • Responsible for
    • Discovering all business use cases

Software Architect: Mirko Müller

  • Responsible for
    • Deciding on technologies for the whole solution

Test Manager: Mirko Müller

  • Responsible for
    • Implementation of automated portions of the test design
    • Testexecution

Responsible for Blog posts: Alexander Rengers

Technologies

Our App is going to be a Xamarin App, developed using C#. Therefore we use the Visual Studio IDE for development and, Git for version control.

For continous integration we use Jenkins CI.

For UI-Tests we use the SpecFlow plugin vor VS.

For project management we’re going to use Jira.

 

W2: Team Roles & Technologies

W1: NeCo Project – Vision

necoproject5 Comments

We are a group of three students studying B. Sc. Computer Science at the DHBW Karlsruhe. During our lecture of Software Engineering we have to implement a program. On this website we will inform you about the progress of our project.

Our idea is to develop a Xamarin App for chatting with strangers around you.

The basic idea behind NeCo is to use localization technologies to create chatrooms with people around you, similar to the popular app “Jodel”.  The difference is that you chat with random people in your local area, to meet, to party, or just to have fun.

For security reasons we’ll use latest encrypting technology like RSA&AES-Encrypting.

Ideas for future features could be:

  • A friend list to keep in contact.

 

We will publish parts of our source code here and hope to get your comments to help us create our app the best way possible.

Thank you for reading our blog!

 

W1: NeCo Project – Vision