Sprint 2 Reflection

Over the past two weeks our Scrum team has been working through the the sprint backlog. I was able to complete all of the tasks on the first day with the exceptions of rebuilding the login module. The tasks involved installing and setting up OpenMRS as well as AMPATH. The next task was to get the two systems to talk to one another. This task took a little bit of experimentation because the two sites did not want to interact at first. The issue was caused by cross-origin resource sharing. This error is a result of one site request content from a second site. In this case the origin, which consists of the domain as well as the scheme and port number. There were two solutions found, the first involved installing an extension in Google Chrome called Access-Control-Allow-Origin. The second options, the one I am currently using, required a small amount of XML be added to the Tomcat server’s configuration file web.xml with in OpenMRS. By the end of the sprint all these tasks were completed by each member. The one item that was not finished was rebuilding the login module for practice.

Over all I believe the team is working pretty well together. getting the two programs running took some a bit longer than others but with a little help all were successful. I think the team will grow stronger and work better together once we have a list of tasks we can split up. There was not too much motivation for rebuilding the login module because it was already working and there was no ore waiting on it. I look forward to the coming sprint as it looks like there will be some bugs that need fixing.

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Learning Reflection

Our group have reached the end of sprint 2 with a lot of accomplishments. We  are all connected to the AMPATH server and have completed our stories on Trello. This sprint period was a great one for my team.We received the result of our peer review  and it was pretty comforting to know that we’re all content with the team’s progress. We have improved individually and have manage to strengthen our teamwork and communication. During this period, Professor Wurst provide a set of diagrams that shows us how we can successfully manage version control. We forked the latest version of the AMPATH project and cloned it on our computers. One of us has created a remote repository for the AMPATH project so they can pull the latest version for the rest of the team. We also have a TeamOrganization repository where we will have our version of the project with the latest changes.Since we’ve connected to AMPATH, I have edited the project on WebStorm to get familiar with it however, i haven’t made any significant change. For the next sprint our team hope to be writing some Angular and dive into the project.

From the blog CS@Worcester – Adestin by adestinyblog and used with permission of the author. All other rights reserved by the author.

Capstone Project: Sprint 2 Reflections

Another sprint down! This sprint was much more exciting then previous sprints. This sprint we were finally able to get OpenMRS and Ampath running locally on our machines so we could fiddle with it! I have a tendency to probe things I don’t understand until I either 1, understand them or 2 break them. Luckily this time was the former over the latter. Part of our previous sprint was to re-write an Ampath module, specifically the authentication. This was to help us learn how the REST API works and to generally learn how Angular works. We broke our sprint down into a few steps.

  1. Remove all traces of an authentication module from the Ampath directory tree.
  2. Attempt to rebuild a basic html/css of the original Ampath login page.
  3. Creating the Authentication routing so when we visit localhost it will successfully show us the html page we had just created.
  4. Make sure the login button successfully authenticates the user.

These four basic steps were what we felt as a scrum team, each individual could finish in the time we had for the given sprint. Unfortunately for me, because I enjoying coding and learning new things so much, I finished this by day 3 of our approximately 8 day sprint cycle. This left me with nothing to do, but plenty of time on my hands. I took that time to start researching TDD inside of Angular and how to write Karma tests. I really like the Karma framework and the way you simply declare what a test should be doing. I feel that it makes your testing output extremely easy to read, which is especially nice when you are showing it off to your wife who is by no means a software developer. But in the case of the real world, it gives someone A LOT of insight into what your code is supposed to do by them simply running test.

Tomorrow we start Sprint 3. From my understanding we are going to become familiar with JIRA and Ampaths issue tracking, so we can start (hopefully) resolving some issues for them! I am very exciting to be finally diving deep into this project and I hope to make some significant changes!

From the blog CS@Worcester – Tyler Lundstrom by CS@Worcester – Tyler Lundstrom and used with permission of the author. All other rights reserved by the author.

Week 4 Reflections

Ok so I think that I have learned a bit this sprint as a lot
of things were new to me. I think the first thing is it feels like the Scrum
side of things is finally rolling to where it actually makes sense to me and I
can see the benefits of it now that I am putting it to use. I like how it all
works and it helps to keep me organized and on track. It feels good to be
putting the tools of the trade to use. Aside from the Scrum side of things I
have learned a lot about Angular and the project we will be working on. I am
still finding it challenging as I have never used Angular before and am really
not familiar with Javascript aside from the basics and I feel like that it is
making it harder for me to grasp not knowing it ahead of time. I am having to
not only look up Angular stuff, but also referring to J.S. docs as well. It isn’t
hindering me that much just a bit more work than I had originally thought.
I was excited to get the OpenMRS standalone running, thanks
to some of the other classmates help with code that needed changing, but it was
definitely a great feeling. I didn’t have much of an issue getting it up and
running. The NG2-amrs build was a little more frustrating to get up and
running. I spent a good deal getting help from classmates as well as the README
(who would of thought that would be helpful right?) but I did get it going and
did cartwheels. A bit was stupid mistakes and not taking a break when I should
have, but that is part of the learning process. Come to find out, that was the
easy part so far.
I am now actually into the code, well the login/auth code
side of things and digging into the meat and potatoes of what we will be
working on. The goal up until now was to re-write the auth/login module to get
a better understanding of how Angular works and how Ng2-amrs login is working.
We as a team ended up breaking the story down into smaller more manageable
tasks so it wasn’t so overwhelming. Initially we had committed to re-writing
the whole module on one card, but split into re-writing the HTML/CSS component
first then digging into the actual auth/routing side of things. That made life
a bit smoother for me. I basically copied the HTML/CSS taking note of things
that I didn’t grasp, such as the Angular additions (I have a good understanding
of HTML/CSS). The challenge is in the writing of the actual Angular. I had to
do a lot of peaking at the original code as well bouncing back to
DOCS/README/Tutorials and other help sites, but got it done. I am still far
from fluent and need a lot of help I think to further my understanding, but I
am persistent and have more help than I could ask for and am not afraid to ask.
That is why we are here in the first place. I am still not 100% up to par on
the RESTful architecture and routing but I am getting there. The more I am
exposed and the more I write and do the more comfortable I am.

I guess to wrap it up for this Sprint, I have to say I am
pleasantly pleased so far and look forward to what is to come and to see how my
blog grows and I grow in the process. I am looking forward to learning more
about the Ng2-Amrs project and collaborating with other developers via the MRS
wiki and forums and digging into the issue tracker on the JIRA server (another
thing I know zero about and am looking forward to learning) and just how
everything fits together. It is great actually seeing the process unfold and learning
new things. Until the next learning reflection blog…..

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 4 Reflections

Ok so I think that I have learned a bit this sprint as a lot
of things were new to me. I think the first thing is it feels like the Scrum
side of things is finally rolling to where it actually makes sense to me and I
can see the benefits of it now that I am putting it to use. I like how it all
works and it helps to keep me organized and on track. It feels good to be
putting the tools of the trade to use. Aside from the Scrum side of things I
have learned a lot about Angular and the project we will be working on. I am
still finding it challenging as I have never used Angular before and am really
not familiar with Javascript aside from the basics and I feel like that it is
making it harder for me to grasp not knowing it ahead of time. I am having to
not only look up Angular stuff, but also referring to J.S. docs as well. It isn’t
hindering me that much just a bit more work than I had originally thought.
I was excited to get the OpenMRS standalone running, thanks
to some of the other classmates help with code that needed changing, but it was
definitely a great feeling. I didn’t have much of an issue getting it up and
running. The NG2-amrs build was a little more frustrating to get up and
running. I spent a good deal getting help from classmates as well as the README
(who would of thought that would be helpful right?) but I did get it going and
did cartwheels. A bit was stupid mistakes and not taking a break when I should
have, but that is part of the learning process. Come to find out, that was the
easy part so far.
I am now actually into the code, well the login/auth code
side of things and digging into the meat and potatoes of what we will be
working on. The goal up until now was to re-write the auth/login module to get
a better understanding of how Angular works and how Ng2-amrs login is working.
We as a team ended up breaking the story down into smaller more manageable
tasks so it wasn’t so overwhelming. Initially we had committed to re-writing
the whole module on one card, but split into re-writing the HTML/CSS component
first then digging into the actual auth/routing side of things. That made life
a bit smoother for me. I basically copied the HTML/CSS taking note of things
that I didn’t grasp, such as the Angular additions (I have a good understanding
of HTML/CSS). The challenge is in the writing of the actual Angular. I had to
do a lot of peaking at the original code as well bouncing back to
DOCS/README/Tutorials and other help sites, but got it done. I am still far
from fluent and need a lot of help I think to further my understanding, but I
am persistent and have more help than I could ask for and am not afraid to ask.
That is why we are here in the first place. I am still not 100% up to par on
the RESTful architecture and routing but I am getting there. The more I am
exposed and the more I write and do the more comfortable I am.

I guess to wrap it up for this Sprint, I have to say I am
pleasantly pleased so far and look forward to what is to come and to see how my
blog grows and I grow in the process. I am looking forward to learning more
about the Ng2-Amrs project and collaborating with other developers via the MRS
wiki and forums and digging into the issue tracker on the JIRA server (another
thing I know zero about and am looking forward to learning) and just how
everything fits together. It is great actually seeing the process unfold and learning
new things. Until the next learning reflection blog…..

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 4 Reflections

Ok so I think that I have learned a bit this sprint as a lot
of things were new to me. I think the first thing is it feels like the Scrum
side of things is finally rolling to where it actually makes sense to me and I
can see the benefits of it now that I am putting it to use. I like how it all
works and it helps to keep me organized and on track. It feels good to be
putting the tools of the trade to use. Aside from the Scrum side of things I
have learned a lot about Angular and the project we will be working on. I am
still finding it challenging as I have never used Angular before and am really
not familiar with Javascript aside from the basics and I feel like that it is
making it harder for me to grasp not knowing it ahead of time. I am having to
not only look up Angular stuff, but also referring to J.S. docs as well. It isn’t
hindering me that much just a bit more work than I had originally thought.
I was excited to get the OpenMRS standalone running, thanks
to some of the other classmates help with code that needed changing, but it was
definitely a great feeling. I didn’t have much of an issue getting it up and
running. The NG2-amrs build was a little more frustrating to get up and
running. I spent a good deal getting help from classmates as well as the README
(who would of thought that would be helpful right?) but I did get it going and
did cartwheels. A bit was stupid mistakes and not taking a break when I should
have, but that is part of the learning process. Come to find out, that was the
easy part so far.
I am now actually into the code, well the login/auth code
side of things and digging into the meat and potatoes of what we will be
working on. The goal up until now was to re-write the auth/login module to get
a better understanding of how Angular works and how Ng2-amrs login is working.
We as a team ended up breaking the story down into smaller more manageable
tasks so it wasn’t so overwhelming. Initially we had committed to re-writing
the whole module on one card, but split into re-writing the HTML/CSS component
first then digging into the actual auth/routing side of things. That made life
a bit smoother for me. I basically copied the HTML/CSS taking note of things
that I didn’t grasp, such as the Angular additions (I have a good understanding
of HTML/CSS). The challenge is in the writing of the actual Angular. I had to
do a lot of peaking at the original code as well bouncing back to
DOCS/README/Tutorials and other help sites, but got it done. I am still far
from fluent and need a lot of help I think to further my understanding, but I
am persistent and have more help than I could ask for and am not afraid to ask.
That is why we are here in the first place. I am still not 100% up to par on
the RESTful architecture and routing but I am getting there. The more I am
exposed and the more I write and do the more comfortable I am.

I guess to wrap it up for this Sprint, I have to say I am
pleasantly pleased so far and look forward to what is to come and to see how my
blog grows and I grow in the process. I am looking forward to learning more
about the Ng2-Amrs project and collaborating with other developers via the MRS
wiki and forums and digging into the issue tracker on the JIRA server (another
thing I know zero about and am looking forward to learning) and just how
everything fits together. It is great actually seeing the process unfold and learning
new things. Until the next learning reflection blog…..

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 4 Reflections

Ok so I think that I have learned a bit this sprint as a lot
of things were new to me. I think the first thing is it feels like the Scrum
side of things is finally rolling to where it actually makes sense to me and I
can see the benefits of it now that I am putting it to use. I like how it all
works and it helps to keep me organized and on track. It feels good to be
putting the tools of the trade to use. Aside from the Scrum side of things I
have learned a lot about Angular and the project we will be working on. I am
still finding it challenging as I have never used Angular before and am really
not familiar with Javascript aside from the basics and I feel like that it is
making it harder for me to grasp not knowing it ahead of time. I am having to
not only look up Angular stuff, but also referring to J.S. docs as well. It isn’t
hindering me that much just a bit more work than I had originally thought.
I was excited to get the OpenMRS standalone running, thanks
to some of the other classmates help with code that needed changing, but it was
definitely a great feeling. I didn’t have much of an issue getting it up and
running. The NG2-amrs build was a little more frustrating to get up and
running. I spent a good deal getting help from classmates as well as the README
(who would of thought that would be helpful right?) but I did get it going and
did cartwheels. A bit was stupid mistakes and not taking a break when I should
have, but that is part of the learning process. Come to find out, that was the
easy part so far.
I am now actually into the code, well the login/auth code
side of things and digging into the meat and potatoes of what we will be
working on. The goal up until now was to re-write the auth/login module to get
a better understanding of how Angular works and how Ng2-amrs login is working.
We as a team ended up breaking the story down into smaller more manageable
tasks so it wasn’t so overwhelming. Initially we had committed to re-writing
the whole module on one card, but split into re-writing the HTML/CSS component
first then digging into the actual auth/routing side of things. That made life
a bit smoother for me. I basically copied the HTML/CSS taking note of things
that I didn’t grasp, such as the Angular additions (I have a good understanding
of HTML/CSS). The challenge is in the writing of the actual Angular. I had to
do a lot of peaking at the original code as well bouncing back to
DOCS/README/Tutorials and other help sites, but got it done. I am still far
from fluent and need a lot of help I think to further my understanding, but I
am persistent and have more help than I could ask for and am not afraid to ask.
That is why we are here in the first place. I am still not 100% up to par on
the RESTful architecture and routing but I am getting there. The more I am
exposed and the more I write and do the more comfortable I am.

I guess to wrap it up for this Sprint, I have to say I am
pleasantly pleased so far and look forward to what is to come and to see how my
blog grows and I grow in the process. I am looking forward to learning more
about the Ng2-Amrs project and collaborating with other developers via the MRS
wiki and forums and digging into the issue tracker on the JIRA server (another
thing I know zero about and am looking forward to learning) and just how
everything fits together. It is great actually seeing the process unfold and learning
new things. Until the next learning reflection blog…..

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 4 Reflections

Ok so I think that I have learned a bit this sprint as a lot
of things were new to me. I think the first thing is it feels like the Scrum
side of things is finally rolling to where it actually makes sense to me and I
can see the benefits of it now that I am putting it to use. I like how it all
works and it helps to keep me organized and on track. It feels good to be
putting the tools of the trade to use. Aside from the Scrum side of things I
have learned a lot about Angular and the project we will be working on. I am
still finding it challenging as I have never used Angular before and am really
not familiar with Javascript aside from the basics and I feel like that it is
making it harder for me to grasp not knowing it ahead of time. I am having to
not only look up Angular stuff, but also referring to J.S. docs as well. It isn’t
hindering me that much just a bit more work than I had originally thought.
I was excited to get the OpenMRS standalone running, thanks
to some of the other classmates help with code that needed changing, but it was
definitely a great feeling. I didn’t have much of an issue getting it up and
running. The NG2-amrs build was a little more frustrating to get up and
running. I spent a good deal getting help from classmates as well as the README
(who would of thought that would be helpful right?) but I did get it going and
did cartwheels. A bit was stupid mistakes and not taking a break when I should
have, but that is part of the learning process. Come to find out, that was the
easy part so far.
I am now actually into the code, well the login/auth code
side of things and digging into the meat and potatoes of what we will be
working on. The goal up until now was to re-write the auth/login module to get
a better understanding of how Angular works and how Ng2-amrs login is working.
We as a team ended up breaking the story down into smaller more manageable
tasks so it wasn’t so overwhelming. Initially we had committed to re-writing
the whole module on one card, but split into re-writing the HTML/CSS component
first then digging into the actual auth/routing side of things. That made life
a bit smoother for me. I basically copied the HTML/CSS taking note of things
that I didn’t grasp, such as the Angular additions (I have a good understanding
of HTML/CSS). The challenge is in the writing of the actual Angular. I had to
do a lot of peaking at the original code as well bouncing back to
DOCS/README/Tutorials and other help sites, but got it done. I am still far
from fluent and need a lot of help I think to further my understanding, but I
am persistent and have more help than I could ask for and am not afraid to ask.
That is why we are here in the first place. I am still not 100% up to par on
the RESTful architecture and routing but I am getting there. The more I am
exposed and the more I write and do the more comfortable I am.

I guess to wrap it up for this Sprint, I have to say I am
pleasantly pleased so far and look forward to what is to come and to see how my
blog grows and I grow in the process. I am looking forward to learning more
about the Ng2-Amrs project and collaborating with other developers via the MRS
wiki and forums and digging into the issue tracker on the JIRA server (another
thing I know zero about and am looking forward to learning) and just how
everything fits together. It is great actually seeing the process unfold and learning
new things. Until the next learning reflection blog…..

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 4 Reflections

Ok so I think that I have learned a bit this sprint as a lot
of things were new to me. I think the first thing is it feels like the Scrum
side of things is finally rolling to where it actually makes sense to me and I
can see the benefits of it now that I am putting it to use. I like how it all
works and it helps to keep me organized and on track. It feels good to be
putting the tools of the trade to use. Aside from the Scrum side of things I
have learned a lot about Angular and the project we will be working on. I am
still finding it challenging as I have never used Angular before and am really
not familiar with Javascript aside from the basics and I feel like that it is
making it harder for me to grasp not knowing it ahead of time. I am having to
not only look up Angular stuff, but also referring to J.S. docs as well. It isn’t
hindering me that much just a bit more work than I had originally thought.
I was excited to get the OpenMRS standalone running, thanks
to some of the other classmates help with code that needed changing, but it was
definitely a great feeling. I didn’t have much of an issue getting it up and
running. The NG2-amrs build was a little more frustrating to get up and
running. I spent a good deal getting help from classmates as well as the README
(who would of thought that would be helpful right?) but I did get it going and
did cartwheels. A bit was stupid mistakes and not taking a break when I should
have, but that is part of the learning process. Come to find out, that was the
easy part so far.
I am now actually into the code, well the login/auth code
side of things and digging into the meat and potatoes of what we will be
working on. The goal up until now was to re-write the auth/login module to get
a better understanding of how Angular works and how Ng2-amrs login is working.
We as a team ended up breaking the story down into smaller more manageable
tasks so it wasn’t so overwhelming. Initially we had committed to re-writing
the whole module on one card, but split into re-writing the HTML/CSS component
first then digging into the actual auth/routing side of things. That made life
a bit smoother for me. I basically copied the HTML/CSS taking note of things
that I didn’t grasp, such as the Angular additions (I have a good understanding
of HTML/CSS). The challenge is in the writing of the actual Angular. I had to
do a lot of peaking at the original code as well bouncing back to
DOCS/README/Tutorials and other help sites, but got it done. I am still far
from fluent and need a lot of help I think to further my understanding, but I
am persistent and have more help than I could ask for and am not afraid to ask.
That is why we are here in the first place. I am still not 100% up to par on
the RESTful architecture and routing but I am getting there. The more I am
exposed and the more I write and do the more comfortable I am.

I guess to wrap it up for this Sprint, I have to say I am
pleasantly pleased so far and look forward to what is to come and to see how my
blog grows and I grow in the process. I am looking forward to learning more
about the Ng2-Amrs project and collaborating with other developers via the MRS
wiki and forums and digging into the issue tracker on the JIRA server (another
thing I know zero about and am looking forward to learning) and just how
everything fits together. It is great actually seeing the process unfold and learning
new things. Until the next learning reflection blog…..

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Reflections on Learning and Work Products, Sprint 2

For our second Sprint in my Software Development Capstone we continued to set up our local computers so that we could work on OpenMRS and the AMPATH software. To do this, we first went to the OpenMRS Download Page and downloaded the OpenMRS Standalone version. Once that was downloaded onto my computer, I simply extracted the zip file and then ran the .jar file that was in the there to start the OpenMRS software (for this I also picked the demo data version that comes with 5,000 sample patients). Some people had issues that this point, but I was lucky that this worked right from the start for me so I didn’t have any modifications to make.

Once I had OpenMRS running, I then cloned the repository containing the Ampath Point of Care System Version 2 that one of my team members forked from AMPATH. To get this up and running I first had to download all the dependencies that they required. I first went and downloaded the newest version of Node.js from their website (for me that was the Windows 64-bit of LTS). Once that was working, I then downloaded the list of gloabals with npm install –global:

  • webpack (npm install –global webpack)
  • webpack-dev-server (npm install –global webpack-dev-server)
  • karma (npm install –global karma-cli)
  • protractor (npm install –global protractor)
  • typescript (npm install –global typescript)

Once all of that was installed, I finished up the rest of the installation by doing these last three steps:

  • npm install webpack-dev-server rimraf webpack -g to install required global dependencies
  • npm install to install all dependencies
  • npm run server to start the dev server in another tab

At first when I ran “npm install” it seemed to give me a list of issues, but when I ran the server everything seemed to work fine and I was able to get to the login screen.

With that completed, our team then set off to work on re-writing the Authentication Module in the AMPATH software and see if we could get it to work (basically just familiarizing ourselves with the software and Angular 2). Our team first put this up as one whole task that need to be completed, but after going through it, we decided to have a story time to break down this task into smaller ones. At this meeting we also decided on what our meaning of “Done” was. Since this was all done closer to the end of our Sprint (due to an excessive amount of snowstorms), our team was only able to do the very beginning of this project. We all start first on going over the login HTML and CSS. Since it’s been at least 4 years since the last time I wrote anything for HTML or CSS (not including what I did for the tour of heroes tutorial), I just put their code next to mine and copied it so I got a feel and could see what they were doing to create the login screen. The last thing that we got to do before the end of our Sprint this time was look over the authentication.module.ts and its dependencies to get a feel for how it works.

During our Sprint review/retrospective we decided to put the rest of the re-writing of the Authentication Module on our backlog and get to it next Sprint. Overall I think that this Sprint went really well, with the exception of how late we got to our story time, but that was all because of storms cancelling our time together and messing up our schedule. Another thing that I found really useful was one of my teammates saw that Scotch.io had a good chuck of their Routing Angular 2 Apps class free to watch. I ended up watching the first couple of videos and found it very helpful, and I will probably finish watching the rest of them over the weekend.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.