Matt's CSUMB Journey

 1. The proper way to use git and git hub, I was fumbling my way through these two services up until this class and now I can see how powerful a tool both can be.  2. The difference between project lifecycles like agile and plan and develop, at the begining of this class I thought that agile was the best way to run a project but now I can see that although plan and develop is more rigid it can be useful for ensuring projects meet deadlines.  3. I learned a lot about the importance of multilevel testing, unit tests to ensure that methods preform properly and system tests to ensure they work together correctly.  4. I learned about mocks for testing which are useful for testing if your programs are preforming as expected without risking connecting two separate servers.  5. How an SRS document can serve as the blue print for a major project and allows for everyone to be on the same page even if they join the project at a later date. I may use documents like this in ...

Some of the main differences between agile and a process like Waterfall comes from the more rigid structure of Waterfall and the more fluid structure of agile. Agile relies on BDD which uses user stories and constant interaction with the customers where as waterfall relies on interviews and documentation driven design to complete processes. Agile uses iteration that are flexible on time but require more meetings and interaction than waterfall. 

 This week we again worked with system tests, one of the things I learned is that on pages with multiple dialog boxes and or modals it is important to make sure that all elements have unique Id's otherwise the system may not find the right element to interact with. I also learned about cloud computing and virtual machines which can be useful for companies who cannot afford to have servers and server rooms on site. 

 This week I learned more about using reacts front end and the importance of ensuring your backend is completed and performs as expected to ensure that your frontend reacts as it should. This also shows the importance of testing as testing will show where the issues are at so they can be fixed instead of discovered later. Large tests often are less efficient than smaller tests and tests should be small to ensure that individual componets are working but also make it easier to find where the faults are at.