Wingfury
commented
6 years ago Backend constraints • You should setup some sort of continuous integration, it is recommended that you use Travis CI as it doesn’t require setting up infrastructure, but other alternatives are acceptable. • You should have at least one example test case running, using an established testing framework, in the language you will use for all subsequent test cases. • You should mock up your page design and interaction. • You should use UML to describe user interactions • All design documentation should be available on your project’s GitHub
Just like when designing a network it is important to have documentation about how a web application will act. Different teams will go about this in different ways. Unified Modeling Language is designed in order to aid with generalizing how designs and flows should work. The end goal of this activity is to have a set of design documentation that would allow someone to create your vision, even if you were not present. You should use UML along with other mockups to allow your team to more easily complete the subsequent sections. The output of this step should include at minimum Use Cases (and diagrams), Network Topology, Flow Graph(s), Database Schema(s), and State-diagram(s) for each part of the application (This may be done using tools like Visio or online tools like Draw.io). This will require you to understand, review, and consider the requirements for the subsequent activities. You are also required to prepare a site mockup. This may be done in a graphics tool like Photoshop or an online design tool like Invisionapp (https://www.invisionapp.com/) In addition to this you should setup a testing service to ensure that these requirements are fulfilled. You are free to setup whichever testing environment you see fit as long as it is capable of running all the various types of tests you’ll need to verify that your application functions (see further activities for examples).