• Edit #SF_B5 Receive custom stop request
• Edit #SF_B8 Next stop
• Add SF Send Custom Status Update
• Add SF Respond to Custom Stop
• Add SF for completing Custom Stop
• Review above
• Add new Interaction Cases according to current functionality
• Update Screen mockups
• General rework on document (update 'Used in', ...)
• discuss format with other groups
• update traceability matrix
• update screen flow

• connection to server (REST-Interface)
• process jsons
• deliver to components
• send positioon to server
• create jsons according to the interface

With @pardypaddy @saskl

• Improve the GUI according to the guidelines.
• Style Stoplist
• introduce variables instead of text for e.g. numberPlate etc. (Language-dependent)

• integrate coverage tool.
• integrate Travis

• make a map component
• add current functions to it
• run without problems on android and ios and browser

As an outcome of the second iteration, you should present an integrated system running the client APPs with the server backend.

GSE-Project/SS2016-group1#36
GSE-Project/SS2016-group2#38

problems during communication with the server:

• solve conflicts with the interfaces
• test with group 1

• route and stops near TU KL
• APK of the latest version

I already list the tasks that should be done for the code phase
Please write your code according to the guidelines.

• Cast JSON to Typescript-object
• Map component
• Extend Service component
• Modify sending criteria
• Adapt the code to the guidelines
• GUI Improvements(especially the home page)
• Settings in sidemenue

Write Tests for the functions

Priority A:

• Merge Branch with the Development Branch(Maybe only transfer the necessary files: Test folder, package.json installs, karma config., gulp.js) and get it running as beforeDUE: 08.06.2016
  -> Send Email to Malte that task is done.
• write specs for Busses.ts as a prototype. Having Trouble with #49

Done:

• configure Karma
• integrate PhantomJS
• create wiki entries for Karma and Jasmine
• configure Karma
• integrate PhantomJS
• create wiki entries for Karma and Jasmine

• show map in application
• add route to the map
• show own position on the map

see Wiki for tutorial links.

• Native Google Maps #44
• "show next stop" and "receive customStop request" #47
• integrate travis #50
• add translations (will only be complete at the end of the implementation)

Anne Hess wrote an E-mail to us with comments what we should change.

https://docs.google.com/document/d/1E5iwka3XbtIlKH7SrMoKiDbxiYQo_cI9NPrwxsgaUqY/edit

• Read the coments and edit the document. (use everywhere same names and so on...)
• Review Document
  Should be done by the same people who edited an reviewed the document

• rework design for components
• rework SF to components traceability
• add GUI flow to the diagram

This Issue is related to #12.
When running busListSpec we encounter an Error, which we did not managed to work out. It would be nice, if you could have a look on it @maybeec.
Be sure to run npm install before running karma start

Safari 9.1.1 (Mac OS X 10.11.5) the process of getting available BusEntries from the Server should load Bus entries FAILED TypeError: undefined is not a constructor (evaluating 'new busses_1.Busses(http)') in /var/folders/s0/...... <- app/components/ServiceTests/bussesSpec.ts:57:39

The referenced line (57) is instantiating a mock of the Busses class by calling new Busses(http)

Erik writes down his notes from the workshop in the document in the google drive (where everyone can work simultanisly)

• GUI / Routing between Pages @ttmher
• REST
• embedding Google Maps and show route
• Interface to device-GPS
• JSON / process information @Charel92

so it seems native google maps was "working" but i couldn't see it.
( i zoomed in the first picture und after i clicked the back butten in the navbar the map showed up )

issue: #44

You should at least have some continuous running tests.

• @saskl @pardypaddy : review the mConcAppt document
• @Charel92: review Entwurf
• @erikgruener & @ttmher : review quality assurance
• @Charel92 : tracebility matrix anlegen

Found while emulating on iOS for #31

• Map is not loading. Simulator System Log shows:

Dropping -requestWhenInUseAuthorization from 'com.ionicframework.busdriveapp350137': NSLocationWhenInUseUsageDescription Info.plist key not available?
May 29 21:39:59 MyMac BusDriveApp[1615]: Lade die Karte/ started loading map

but map is not loading. This Bug is similar to SS2016-group2's (closed) issue #49.

• StopList screen style is broken, the dividing lines are messed up

• add alert
• add alert buttons
• stop sending if confirmed to leave

send if

• the position has moved by 75 meters

or

• 60 seconds has passed

TODO:

• Workshop on April 22
• Write System Test Cases
• Specify architecture

• Update Systemtests Template
• Perform System Tests
• Review System Tests

• fix issues with emulating our application on ios
• create wiki entry

Please check to have the following documents as well as link them in the readme.

• component diagram
• traceability matrix from system functions to component diagram
• system test specification
• traceability matrix from system functions to system tests

with @pardypaddy @Charel92

• Write System Test Cases

• digitalize mockups
• embed in document
• review document

• update according to GeoJSON
• update current functions

Plan for the week

Everyone should create an issue an self assigne it and resume what he will do and keep it up to date

• clarify Interface @Charel92
• rework Design for components @ttmher
• rework requirements document @saskl
• update Wiki (promises and tests) (for all of us)
• continiue writing tests/ find out how it works. @erikgruener @ChaosBanisher
• find out how to emulate on iOS @pardypaddy

Please read all the information for developers

• Additional implemented elements
• Adjust send data SF according to interface specifications
• Adjust request data SF
• Check on consistency
• Review

We need to discuss how we imagine the SFs "Receive custom stop request" and "Next stop" should work exactly and then propose the ideas to the customer to see what he thinks.

• come to an agreement about "Receive custom stop request"
• come to an agreement about "Next stop"
• send proposal

• consistent names
• glossary

The problem is similar to the one of group2. See GSE-Project/SS2016-group2#17

Please read the guidelines for the wiki entrys and edit your wiki entry.

• Guidelines

With the new settings menu the language isn't working anymore and there should be some additional translations added

• repair language change
• add new translations

• add SF NextStop
• add SF Receive CustomStop
• change the handling of the data from server
• improve map

You should finalize and communicate the interface specification with the other groups to be able to integrate in iteration 2.

GSE-Project/SS2016-group1#35
GSE-Project/SS2016-group2#37

• create a suitable MockBackend to use in every service test #56
• busses.ts
• lines.ts
• routes.ts
• stops.ts
• customstops.ts

I excluded provider.ts, since it is easier to test our http Posts for the server group @mbaniasad

• store selected language
• create aboutpage
• add some functionality to aboutpage
• expand settings ( new options )

Oliver with @ttmher and @saskl
Define architecture and interface.
Discuss interfaces with the server group

• Add new Links to the system tests

• add maps api key to index.html

• transfer post command to service component
• change interfaces
• add new post command for ./updateBusStatus

NextStop

• add functions for showing next ( previous ) stop
• add GUI elements

CustomStopRequest

• add functions for requesting and receiving custom stops
• add functions for accepting / rejecting a custom stop
• add alert when there are new custom stops
• add badges for the number of new custom stops
• add functions for complete / "noshow" a custom stop
• add functions for post command for "customStopStatus"

• test system according to the specified System Test Cases at /Doc/Quality Assurance
• reviewed

"Google Maps Javascript API v3 works perfectly in PhoneGap/Cordova, but the performance is not good when the app uses mobile network. Also, it's not as smooth as the native SDK."

reference: https://github.com/mapsplugin/cordova-plugin-googlemaps/wiki/How-different-are-the-JavaScript-APIs-%28web%29-and-the-mobile-SDKs-%28native%29