i will do part 4 of the assignment
Resource CST-135 Activity 1 Guide Contents Part 1: Install Eclipse and Java2 Part 2: Person Class3 Part 3: Race Car Object6 Part 4: Key Learning8 Activity 1 Deliverables8 This activity has multiple parts. All parts must be completed prior to documentation submission. Your instructor will provide the materials necessary to demonstrate and explain the steps in each of these activities. Part 1: Install Eclipse and Java Goal In this activity you will install the latest version of Eclipse for Java and validate your local environment by developing a simple "Hello World" Java class in Eclipse. Execution Execute this assignment according to the following guidelines: 1. Install the latest version of Eclipse IDE for Java as directed in "Eclipse IDE for Java Developers" located in the Course Materials. 2. Make sure you have installed the latest version of Java SE. 3. Setup your Java Coding Style. From Eclipse Preferences, go to Java > Code Style > Formatter menu items. You can export this setup and share with your team so that everyone is coding using the same conventions. 4. Create a simple "Hello World" class using the Eclipse IDE: a. Start Eclipse. b. Create a new Eclipse Workspace and name it "workspaceCST-135," which will be used for all in-class activities. You should make sure you back up your workspace. c. Create a new Java Project using the File > New > Java Project menu items and name your project "assignment1." Also, validate that your project is configured to use the JavaSE-1.8 JRE. Click the Finish button. d. Right click on the project folder and select the New > Class menu options. Name your class "HelloWorld." Click the "public static void main" method creation option. Click Finish. e. Add a private method named "sayHello()" that returns void and takes a string as a parameter named "name." In the implementation, print a string "Hello my name is " and concatenate the "name" argument to the string. Print the string to the system console. f. In the main(), create an instance of the HelloWorld class and call it the sayHello() method. g. Run the HelloWorld class. h. Take a screen shot of the console when executing the HelloWorld class. Deliverables This activity has multiple parts. All parts must be completed prior to documentation submission. See instructions at the end of the is document. For this activity, you will need a Word document that contains screen shots of: 1. The Eclipse About Box 2. The console output when running the HelloWorld class Part 2: Person Class Goal In this activity you will write a Person class based on a UML model. Execution Execute this assignment according to the following guidelines: 1. Create a UML for a Person class. Create a variety of properties and methods that describe what you want the person to be able to be and do. Properties of a person could be a person’s name, age, weight, IQ, or any other statistic that can be quantified about a person. Methods of a person class could be actions that the person does in your application such as log on, start game, or make phone call. 2. Create a new Java Project using the File > New > Java Project menu items, and name your project "assignment2." Also, validate that your project is configured to use the JavaSE-1.8 JRE. Click the Finish button. 3. Right click on the project folder and select the New > Class menu options. Name your class "Person." Click the "public static void main" method creation option. Click Finish. a. Add the private state variables you created for your Person class. b. Create a nondefault constructor that initializes your Person state variables. c. Create a getter and setter method for at least one of the variables using Eclipse Refactoring (use the Source > Generate Getter and Setters menu options). d. Add the public behavior methods you selected. e. Add console print statements to each method that displays appropriate testing messages. f. In the main(), create an instance of the Person class and call each of the public methods. 4. Run the Person class. 5. Take a screen shot of the console when executing the Person class. 6. Create a JavaDocs snapshot of the classes in the application. 7. Generate the JavaDoc using Eclipse: a. Select the Project > Generate Javadoc menu options. b. If necessary, add the JavaDoc command in the first text entry field. Click configure and browse to the Javadoc executable. It should be located in the Contents/Home/bin folder of the Java SDK folder. The picture below is from a Mac. Here is the configuration for using JavaDoc in Windows. c. Select your project. d. Use the standard doclet. e. Set the location where you want the JavaDoc generated. The default location is the doc folder inside of the project. f. Click the Generate button. g. Validate the documentation by opening the index.html generated by JavaDoc. 8. Create a UML class diagram of your Person class. Deliverables This activity has multiple parts. All parts must be completed prior to documentation submission. See instructions at the end of the is document. For this activity you will need a Word document that contains: 1. UML class diagram of the Person class. 2. Screen capture of the console output when running the Person class. 3. A ZIP file containing the source code written in this activity. Part 3: Race Car Object Goal In this activity, you will be given a set of functional requirements for a race car game. You will then design/model and implement the game. Execution Execute this assignment according to the following guidelines: Problem Statement We need to design a racing car that can be used in a game, and the car must be able to be started, run, and stopped. Requirements 1. The car must have an engine and tires. 2. The car must have four tires. 3. The car must have one engine. 4. The engine must be able to be started and stopped. 5. Before the engine can be started all tires must have at least 32 psi. 6. The car must be able to start, run between 1 and 60 mph, stop, and restart. Modeling · You must do object-orientated analysis from the requirements. · What objects will you need (hint, pick the nouns out of the requirements)? · Make sure each object has the proper design: · States (nouns from requirements) · Behaviors (verbs from requirements) · Relationships: · If Object A has a relationship to (or contains) Object B, then it must be included as a member variable in Object A. · Create a UML class diagram of your complete model. Use a tool such as Draw.io or lucidchart.com if you wish. Implementation 1. Code the logic and rules to properly start, run, stop, and restart the car. 2. Code all the classes per your models. 3. You must be able to exercise your car from another "driver" script. 4. Take a screen shot demonstrating that you can start, drive, and stop your car. Deliverables This activity has multiple parts. All parts must be completed prior to documentation submission. See instructions at the end of the is document. For this activity you will need: 1. A Word document containing 0. A UML class diagram of your complete model. 0. Screen shots demonstrating that you can start, drive, and stop your car. 1. A ZIP file of your source code, including the Javadoc directory. Part 4: Key Learning Goal In this activity, you will summarize your key learning of this topic in 500–750 words. Execution Execute this assignment according to the following guidelines: Complete the assigned textbook readings. Create a Word document and write 500-750 words for these subjects: 1. Summarize what the textbook says about variable visibility (public, private, and protected) and how to decide which setting to give a variable. 2. Summarize what the textbook says about class relationships (is-a, has-a, inheritance, composition). Give an example of each type of relationship mentioned in the text. Deliverables: This activity has multiple parts. All parts must be completed prior to documentation submission. See instructions at the end of the is document. For this activity you will need a Word document that contains 1. Paragraph summarizing visibility of class properties. 2. Paragraph summarizing class relationships. Activity 1 Deliverables This activity has multiple parts. All parts must be completed prior to documentation submission. This first assignment has four sections. A good way to organize the assignment is to create four folders and ZIP the entire project. Inside each of these folders is usually another ZIP file that contains the project code and a Word document that contains screen shots of the application being demonstrated. © 2020. Grand Canyon University. All Rights Reserved. © 2020. Grand Canyon University. All Rights Reserved.