Reflection: Sprint 2

This sprint first thing we did is basically created our team organization called “Teamloading” on Github and then cloned the copy of ng2-amrs project from our organization. This way we all team members have own copy to work on, and any changes we did we be handled and review by our organization as a whole before pushing the changes to the actual AMPATH project. The same Github workflow designed by our Prof. Wurst is given below:

p_20170216_103350

Next thing we did is build and run the ng2-amrs. While running the project we also needed the openMRS platform which is basically  a back-end system, with a database and APIs. But I was Unable to start OpenMRS , so I posted the issue on the openMRS talk forum. The screenshot of the issue is given below:

capture

As of now I am still getting the error.Error thrown was: org.openmrs.api.APIException: Service not found: interface org.openmrs.scheduler.SchedulerService. The link to the page is listed below:

Issue: Unable to start OpenMRS

Hopefully experts over there will be able to troubleshoot soon.

This sprint I also looked over the code in the authentication module of the login page. Furthermore, I also looked over Angular 2 tutorials online.

From the blog CS@Worcester – Software Dev Capstone by osworup007 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.

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.

Sprint 2 Reflection

For Sprint 2 we started to actually get involved with the AMPATH project. The first main task was to actually get the project running. First we forked the project to our GitHub accounts, then we cloned the remote repository to our local repository. If we didn’t already have Node JS installed we needed to download that and install any required packages into the ng2-amrs folder. After that we could run the server with the npm command and have a live AMPATH site running in our browser. Once we had AMPATH running we then needed to download the openMRS standalone and connect AMPATH to it. In order to connect them we needed to update the server settings on AMPATH to the standalone server and add some code to a web XML file. Connecting AMPATH to the standalone allowed us to successfully login to AMPATH with access to a mock database. As simple as these tasks sound it was far from an easy setup. At least in our group it took us all several attempts and some troubleshooting to successfully get AMPATH online. We had server errors, issues getting the standalone to run, and version compatibility problems. Each team member basically had to work through their own list of issues to get connected. Aside from the effort of getting the project up and running I completed a good Angular 2 beginner’s tutorial on thinkster.io. I thought it was a better introduction to Angular 2 and I definitely feel more confident with the framework’s fundamentals. To finish off the sprint I started browsing the AMPATH source code. It is a bit overwhelming but I think the more I review the better I will understand. The biggest learning curve is learning the complexities of Angular 2 syntax and the module style development. At the end of the sprint I thought our team retrospective went pretty well. This was another sprint where all the tasks had to completed by each individual so it’s hard to really judge the team’s effectiveness. Overall we are all completing our individual tasks and helping each other as we move through the sprints. Looking into the next sprint it looks like we will be re-writing a module and working on some known AMPATH issues. This should allow us to make our first true contributions to the project and tracking issues will improve our knowledge of the code base.

From the blog CS@Worcester – Software Development Blog by dcafferky and used with permission of the author. All other rights reserved by the author.

Reflections (2/22/17) Week 4

After deciding to have the reflections due at the end of each sprint instead of the end of the week, this reflection is going to summarize what happened during the last two sprints. The team began by forking the AMPath code on github and cloning the code to their computers. After getting the code settled and making sure everyone can open up the code in Webstorm, we tried to make sure that everyone was able to connect to the AMPath database through local host 3000. A majority of us had a problem where we got the login page to AMPath to appear, however the bottom right kept saying that the server was offline instead of online so we could not connect to it. That obstacle was later solved thanks to Ryan and other people in the class for searching for workarounds to the problem. The most common fix was a google chrome extension that you could download and it will allow you to connect to the server, however when that extension ran on my laptop it disconnected me from using the web. Later on, we found another fix that Ryan suggested which includes adding code to an xml file in the OpenMRS standalone folder and the connection worked out well with no side effects. We also added the proper OpenMRS directory to the server settings which connected us properly.

Other than connecting to AMPath, some users in our team had trouble starting OpenMRS itself since it took around 30 minutes to open for people, later on that issue was resolved but i do not recall what fixed it for them .We troubleshooted by giving them faster internet through a wireless adapter but that did not work out, they probably reinstalled it. We were also instructed to modify the login page of the AMPath and also get a proper understanding of the code which some of us did, but not all. We are now awaiting access to the tracker so we can help fix bugs and as well look forward to the EPIC goal that we are going to do as a class.

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.