This week, we were given our assignment and reached out to our customers. Our team met with them, and were able to define many of the requirements for our project. After collecting this information we were able to start mapping out general goals to show our customers the next time we met.

During this week, our team gathered to work on our "Use Case Scenarios" assignment. Using information our customers provided us during our last meeting, we could create the user cases needed to flesh out different tools we could use. After finishing this assignment, we were able to research different libraries and open source projects that could be integrated with our cloud editor. 

Finishing the requirements specification project was the main priority for this week. This assignment helped us look at the big picture. I was in charge of writing about the non-functional requirements, the user stories, and the project overview. Our team had a meeting with our customers so we could share the different tools we had been researching and receive feedback. 

This week we started tackling the architecture assignment. During our weekly meeting, we talked to Michael Lehenbauer. He is the one who built Firepad, which is a key piece to our project. This gave us insight on how it was developed, and the features it has that can help us. We split up the worked and drew webs to make sure we are all on the same page when it comes to scope, functionality, and how we plan to do it. This made it easier to work out the architecture and class diagrams as well.

Since the previous week was mostly spent with figuring out the architecture, building the diagram was not too difficult. I received feedback from both Matt and Tommy on any inconsistencies that were in the diagram, as well as how to make it more visually appealing. We also had our check-up meeting, and started creating the foundation for our demo. We plan on showing the demo to our customers next Friday.

This week we continued to work on a basic demo for our supervisors. Now that the architecture assignment was finished and we had a strong idea of where to start and grow what we worked on first. The basic demo has a rough user interface but has a few key features. Now that the demo was looking better it is easier to receive feedback from our customers.

This week we focused on getting the demo to not only run on node.js. This was done by using Angular to host the front end of the website. This allowed us to start polishing the user interface and make the project in general much more presentable. We will receive feedback next week for the new user interface and can work from there. 

After talking more with our clients, we decided that the app would be incredibly helpful to those who wanted to render a website written in the editor to test and see an example for their code. This was the main feature we focused on this week. HTML code can be rendered to make an example website and this feature would be very convenient for a collaborative code editor. 

This week we worked to add more features to the application. Matt focused on working auto-save into the application so any changes made in real-time can be accessed later by users. This was when I started to get Karma installed for unit testing. I also did a large amount of research to understand how to write tests to be implemented in the future.

This week we had a big discussion with out clients for the future of the project. Based on the work we got done in the time frame and with a month or so remaining we decided that this project will be a proof of concept more than a working prototype. The demo will lack user login and git functionality but will still be a collaborative code editor. Karma is missing lots of different libraries that is preventing it to work, but Tommy said he will help me try to get it off the ground.

Tommy and I were able to get Karma working properly so testing can be done to test different functions. Aside from that, we mostly focused on organizing our coding assignment and delegating work. I focused on testing and the source code review but we all discussed potential issues and questions with each other as we did our parts for the coding assignment. 

This week we focused on adapting our application to be appealing for a live demo. The demo for our coding presentation required the application to work efficiently and have the features work consistently. We practiced our presentation in front of friends to receive feedback and we able to give a nice, professional presentation.

We only had two school days this week so we did not make much progress with coding. However we were given our twist. We were asked to include a feature that allows for image editing. There were not many features required to edit the image, but we had only focused on working with text files until this point. We will look at it after the break.

After the break we met up to understand the twist and implement it. What we decided to do was use a library to edit files and import it to our project when different images were uploaded. Not only could it work with .jpg and .png, but also .gif files! It sometimes struggles with performance issues, but we are able to manipulate and crop different images on our text editor.