Assignment As noted above, this lab has 2 major components: the design of the program and the implementation of the program. The important thing to realize here is that this process is not a one-way street. As you design, you should implement small pieces of your program and allow them to inform your decisions and how you work moving forward. Save and compile often, and be flexiblel The first step to of any creating any complicated program is to hatch a plan! In both the higher levels of academia and the professional workplace, there is immeasurable value in thinking and planning before you ever touch a keyboard. This is for many reasons . Planning gives us a roadmap for what we need to code It's easier to communicate with a team if we have a design laid out . . We can identify tricky parts of our program before we begin to work on thenm There are entire classes you will take here at Clemson which deal with useful design principles, what kind of documentation you should keep, and how a team deals with the design phase of creating software. For our purposes, we just need a graphical representation of our program that allows us to organize our thinking. Open draw.io and create a new diagram. Familiarize yourself with some of the tools, and consider the following diagram: ar string: make string: model Engine: engine TireD: tiresj41 top_speedo double Vehicle +to_stringo: string Engine Tire double: horsepower double: wear Between 0.0 and 1.0 double: weight total wearO: double +total_power0: double This is a simple diagram created using the UML tools in draw.io. UML stands for Unified Modelling Language and it is a powerful tool for describing software designs. This is not a complete UML diagram, and UML has many, many other features to help in designing software All we want to do here is talk about the organization of our classes. In this example, I want to design a piece of software that simulates various kinds of vehicles. The program should . Support many kinds of vehicles .Support vehicles with different functionality (boat, car) but similar components (engines) . Allow me to calculate statistics about the vehicles with a single method call (i.e. top speed) As you can see, I've modeled 3 classes in a top-level package called Vehicle: Car, Engine, and Tire. Assignment As noted above, this lab has 2 major components: the design of the program and the implementation of the program. The important thing to realize here is that this process is not a one-way street. As you design, you should implement small pieces of your program and allow them to inform your decisions and how you work moving forward. Save and compile often, and be flexiblel The first step to of any creating any complicated program is to hatch a plan! In both the higher levels of academia and the professional workplace, there is immeasurable value in thinking and planning before you ever touch a keyboard. This is for many reasons . Planning gives us a roadmap for what we need to code It's easier to communicate with a team if we have a design laid out . . We can identify tricky parts of our program before we begin to work on thenm There are entire classes you will take here at Clemson which deal with useful design principles, what kind of documentation you should keep, and how a team deals with the design phase of creating software. For our purposes, we just need a graphical representation of our program that allows us to organize our thinking. Open draw.io and create a new diagram. Familiarize yourself with some of the tools, and consider the following diagram: ar string: make string: model Engine: engine TireD: tiresj41 top_speedo double Vehicle +to_stringo: string Engine Tire double: horsepower double: wear Between 0.0 and 1.0 double: weight total wearO: double +total_power0: double This is a simple diagram created using the UML tools in draw.io. UML stands for Unified Modelling Language and it is a powerful tool for describing software designs. This is not a complete UML diagram, and UML has many, many other features to help in designing software All we want to do here is talk about the organization of our classes. In this example, I want to design a piece of software that simulates various kinds of vehicles. The program should . Support many kinds of vehicles .Support vehicles with different functionality (boat, car) but similar components (engines) . Allow me to calculate statistics about the vehicles with a single method call (i.e. top speed) As you can see, I've modeled 3 classes in a top-level package called Vehicle: Car, Engine, and Tire