Many companies approach product development as if it were manufacturing, trying to control costs and improve quality by applying zero-defect, efficiency-focused techniques. While this tactic can boost the performance of factories, it generally backfires with product development. The process of designing products is profoundly different from the process of making them, and the failure of executives to appreciate the differences leads to several fallacies that actually hurt product-development efforts. In this article, the authors, an HBS professor and a consultant, expose these misperceptions and others. They look at six dangerous myths:

High utilization of resources will make the department more efficient
Processing work in large batches will be more economical
Teams need to faithfully follow their development plan, minimizing any deviations from it
The sooner a project is started, the sooner it will be finished
The more features a product has, the better customers will like it; and
Projects will be more successful if teams "get them right the first time."
The authors explain the negative effects these "principles" have when applied to product development, offer practical guidelines on overcoming them, and walk readers through a visual tool that will help them keep projects on track.

Based on the reading and analysis of the paper, Six Myths of Product Development, and your understanding of the topics covered in this course, discuss how inadequate testing leads to problems and the impact of the cost of defects on the project.

[java] create an application called registrar that has the following classes: a. a student class that minimally stores the following data fields for a student: - name - student id number - number of credits - total grade points earned and this class should also be provides the following methods: - a constructor that initializes the name and id fields - a method that returns the student name field - a method that returns the student id field - methods to set and retrieve the total number of credits - methods to set and retrieve the total number of grade points earned. - a method that returns the gpa (grade points divided by credits) b. an instructor class that minimally stores the following data fields for an instructor: - name - faculty id number - department the following methods should be provided: - a constructor that initializes the name and id fields - methods to set and retrieve the instructor’s department. c. a course class that minimally stores the following data for a course: - name of the course- course registration code- maximum number of 35 students- instructor- number of students- students registered in the course (an array)the following methods should also be provided: - a constructor that initializes the name, registration code, and maximum number of students- methods to set and retrieve the instructor- a method to search for a student in the course; the search should be based on an id number.- a method to add a student to the course. if the course is hill, then an exception with an appropriate message should be raised (try creating your own exception class for this). also, be sure that the student is not already registered in the course. the list of students should be in the order that they registered.- a method to remove a student from the course. if the student is not found, then an exception with an appropriate message should be raised (use the same exception class mentioned a method that will allow course objects to be output to a file using object serialization- a method that will allow course objects to be read in from a file created with object serializationyou will note that the student and instructor classes described above have some commonality. create aperson class that captures this commonality and uses it as a base class for student and instructor. this class should be responsible for the name and id fields and also provide atostring method that returns a string of the form name, id. this will be the inheritedtostring method for the student and instructor classes.1. draw a uml diagram for diss application.2. implement the previous classes in java. write a main program that can serve as a test class that tests all of the methods created and demonstrates that they are working