Java project, product types, user input, error handling, graphical interface, command terminal, IProduit interface, ProduitA, ProduitB, Client, ClientDao
This document summarizes the problems encountered during a Java project implementation and the solutions found to address them, focusing on handling different product types and user input.
[...] 1.1 The problems encountered During the development of this project, we encountered various problems and difficulties. First problem: The first major difficulty encountered is that of taking into account the type of product entered by the user without the code being redundant, and without realizing the entire project with graphical interfaces. (We think here that this is not what is requested). It is not either requested to realize a menu. How to treat then the two different types of product? [...]
[...] How to handle these errors? 1.2 The solutions found We respond to the problems encountered in this section, as stated in the previous part. First problem: To solve this problem, we think of creating a product type request to the user. We would then need to ask for the product type in the graphical interface, which would add a non-negligible amount of code to produce. We do not think that this is what is being asked. [...]
[...] We will first study the data in order to realize a class diagram and have a general view on the structure of the data of our project. We will then implement the IProduit interface, followed by the ProduitA and ProduitB inheriting classes in order to be able to create and add a product. To do this, we create a small graphical interface. Next, we will implement the Client and ClientDao classes in order to be able to create lists of clients and perform operations on them. Finally, we will create a main class to test the entire code that we have put in place. [...]
[...] We are trying to ask for the desired product type by terminal input, but this does not work. We then decide to include the product type in the code, and offer the programmer to change it manually in order to test both product types. Second problem: We cannot find a solution to this problem. We think that it would be necessary to choose one of the two input modes for the entire program, so that it is ergonomic. We leave the graphical interface to open in parallel to the input requests on the terminal. [...]
[...] Java Diagrams and Project Project JAVA Report Version1.0 2/15/26 NAME : FIRST NAME : SUMMARY 1. INTRODUCTION 1.1. The problems encountered 1.2. The solutions found 2. THE JAVA CODE 2.1. [...]
APA Style reference
For your bibliographyOnline reading
with our online readerContent validated
by our reading committee