Week 4

Monday – Nov. 25th

The App Dev team decided it would be in everyone’s best interest if no coding took place the day after the University’s deadline. Instead, the team looked ahead to the second deadline three weeks away. Wiki resources were updated, Milestone 2 requirements were read and understood. Finally, we presented our client with a possible survey to be used for data gathering / analytics.

Tuesday – Nov. 26th

Per our client’s wishes, the dataset has been reduced to 60 fields from 130 fields. The team first fleshed out how these reduced dataset would interact within the application. Abstraction was taken into account as all most of these fields would require alike functionality.

After separating the fields into logical “pages,” the meeting focused on the transition from Java coding to integrating SQL and XML into the product’s code.

Wednesday – Nov. 27th

The team reviewed extra documents from client that further helped with dataset rules. Sample decisions trees were sketched as per the new validation logic. Meeting was adjourned after an email to client with some questions for clarifications was sent.

Thursday – Nov. 28th

The client’s reply cleared all questions from previous meeting. After discussing this new information, the team focused on University tasks, namely the GC02 poster that would be due next Wednesday (the 4th).

After a brief discussion. It was decided that meetings for Friday and the weekend (the 29th through Dec 1st) would be unnecessary. As such, the team divvied up work packages to clear during these days including:

  • Making sure Java validation works on a command line level
  • Making sure XML parsing works on a command line level
  • Making sure SQL connection / read / write capabilities work on a command line level
  • Further insight into Android programming, HCI requirements

Week 3

Monday – Nov. 18th

As the first milestone draws close, the team started the meeting with a review of the project’s specifications both from the client and from the University. We then moved to advance the parts that were lacking. Use cases were tabulated. Further git run-throughs were underway. Finally, our latest meeting with our client was transcribed and questions and answers were extracted from it.

Tuesday – Nov. 19th

The entire team concentrated on coding.

It was deemed one more client meeting was needed before sending in the project for marking. The team wrote down all questions that may have been left out of previous communications as well as drafting out a survey prototype per client’s suggestion.

Meeting was adjourned after considering a Gantt chart for drafting out the schedule of the work packages.

Wednesday – Nov. 20th

Our meeting with our client and the web application’s developer went as expected. We followed up with the developer on some clarification due to the complexities of both our project and the existing web app.

Once again, the team checked the project’s specifications and listed the yet unfinished sections.

Thursday – Nov. 21st through Sunday Nov. 24th

The team worked throughout the rest of the week on any and all missing sections of the project.

Coding took place throughout most of these four days. During coding breaks, the team worked on the project report, Gantt chart, data dictionary, or UML specifications.

On Sunday, November 24th, at 4:52 P.M., the team gathered all it sources and turned the project in for marking.

Week 2

Monday – Nov. 11

The entirety of today’s meeting was given to the development of an XML structure for the application. While an XML schema was previously designed, actual coding proved problematic.

Tuesday – Nov. 12

As with yesterday’s meeting, the team continued to work on an XML solution.

On a brighter note, there may be a different way to get the Domino side of the client’s application to the product.

Wednesday – Nov. 13

Today’s meeting was less formal. XML continues to be worked on. The team requested a meeting with the client in order to present early GUI designs and, if possible, speak to the current application’s developer. The client soon set a meeting for Friday 15th.

Thursday – Nov. 14

XML was set aside for this meeting as the team focused on getting a better grip on the GUI designs as well as developing questions and talking points for tomorrow’s meeting with the client.

Friday – Nov. 15

Meeting with client.

While the majority of the GUI design was deemed appropriate, a navigation screen will likely have to be entirely redesigned as it could prove unwieldy for handheld platforms.

The client also provided further insight to the processes behind the current application in use as well as the background of the client’s company. Unfortunately, the current application’s developer was not able to join the team. A meeting has been set for Tuesday 19th.

The team also agreed to help develop a survey to find the extent of the usefulness of the proposed product as well as to provide further information about use cases for the current application.

The app dev team will complete University tasks for the product during the weekend and start the coding process on Monday 18th.

Week 1

Monday – Nov. 4

Working off Friday’s rough sketch, the app dev team fleshed out the specifications for the product. Architectural Decisions were put in place as well as a Client – Server interaction diagram.

The team then moved on to decide the structure of the XML files that will be used in the product’s backend SQL Database. The frontend was also touched upon as GUIs were sketched and then integrated into the model.

Tuesday – Nov. 5

The software Domingo was seen as a plausible option to network the client’s Domino server to the app team’s Java product. A short run-through at the beginning of this day quickly showed that more information would be needed.

The app dev team then proceeded to install and familiarize themselves with GitHub and its workings related to both Eclipse and other application.

The bulk of the meeting was then spent on converting Monday’s sketches into classes and deciding how these mock Classes would interact with each other based on the current software’s documents provided by the client. Along the way, the team encountered some unclear points that were, at the end of the meeting, communicated to the client asking for clarification.

Wednesday – Nov. 6

Today’s meeting started with a discussion of the requirements for this project as outlined in the University’s email. It was deemed that the app dev team was on the right track as per said requirements. This was followed by discussing the client’s reply to the previous meeting’s questions.

Clarifications noted, the team moved on to set up a collaborative coding environment. The applications Trello, WeChat and WindowBuilder for Eclipse were installed on the necessary terminals for each team member. Team roles were also assigned.

Class construction followed. Possible methods for classes were discussed and written down. Inheritance was discussed and XML configuration was delved further into.

Thursday – Nov. 7

The meeting started with some further discussion into Domingo and the possible limitations of it. The JDBC Java library was then seen into as a possible way to have the XML configuration files “talk” to the SQL end of the product.

Logical steps for the product were then discussed; from communication with the Domino server, to the display of a GUI on the chosen platform and back to the Domino server as a write operation.

Friday – Nov. 8

Domingo has proven to be unrealiable as a solution to the team’s need for a way to communicate with the client’s Domino server. A different way to meet this goal must be found.

The app dev team then agreed to hold the next meeting on Monday the 11th

First Steps

First blog post! We will hopefully be documenting here how we work our way to developing a (hopefully) successful mobile medical data collection app. Stay tuned…