Answer:
import java.util.Scanner;
public class TestClock {
public static void main(String[] args) {
Scanner in = new Scanner (System.in);
System.out.print("Enter favorite color:");
String word1 = in.next();
System.out.print("Enter pet's name:");
String word2 = in.next();
System.out.print("Enter a number:");
int num = in.nextInt();
System.out.println("you entered: "+word1+" "+word2+" "+num);
}
}
Explanation:
Using Java Programming language
- Import the Scanner class
- create an object of the scanner class
- Prompt user to enter the values for the variables (word1, word2, num)
- Use String concatenation in System.out.println to display the output as required by the question.
They have the same vertical resolution. I can suggest you to watch the video in youtube .<span>https://www.youtube.com/watch?v=uluEEGBHyUE</span>
Answer:
D. method, class, generalization/specialization
Explanation:
The Cohesion is said to be the level to what an element of a module is related to others. Generally, the cohesion can be understood as an internal adhesive that holds together the modules. If the software is good then it is going to have high cohesion. Method and class are type of cohesion, as they hold the modules together. And generalization/specialization also is a general type of cohesion as generalization tracks the common features among the class, and binds them into one superclass. However, the specialization means creating subclasses out of the classes, and which is the meaning of the specialization. In an ideal situation, there should be high cohesion or single responsibility. However, in the case of inheritance, there can be multiple responsibilities. And hence composition like a generalization, specialization, association, aggregation are used to make use of the composition for reuse rather than inheritance. Have you seen language supporting multiple inheritances. You will never see it though there is some way. And its never allowed to ensure high cohesion. And hence three general types of cohesion are method, class and generalization/specialization. And this is option D.
The answer is the team. Teams are self-establishing which no one not even the scrum master tells the team how to turn product backlog into augmentations of stoppable functionality. Each team member put on his or her knowledge to all of the complications. The interaction that outcomes progresses the entire scrum team’s general competence and usefulness. The optimal size for a scrum team is seven people, plus or minus two. When there are fewer than five team members, there is less interface and as a result less productivity improvement. The product owner and scrum master roles are not comprised in this count. Team arrangement may variation at the end of a sprint. Every time Team membership is altered, the productivity increased from self-organization is reduced.
Pressing enter two times I’m pretty sure that’s right cuz like it does nothing when I do it. It’s either that or idk up to u to take an answer from someone who has bad grammar
