- 1 Project Overview A Few Paragraphs Describing The Purpose Of The Application The Development Environment Visual Stu 1 (267.5 KiB) Viewed 27 times
- 1 Project Overview A Few Paragraphs Describing The Purpose Of The Application The Development Environment Visual Stu 2 (243.91 KiB) Viewed 27 times
1. Project Overview. A few paragraphs describing the purpose of the application, the development environment (Visual studio code, JDK17, etc.) and the technologies used (JavaFX, SceneBuilder, file I/O, collections, graphics etc.) Your description must make clear how you will be incorporating the required elements: a) File I/O - What information will you save to files on disk, and/or what information will you load from files? Detailed file format information is not required. b) Dynamic array - What information will be stored in a dynamic data structure? How will it be managed? 2. User Interface. Provide one drawing for every window (stage/activity/dialog) you envision to be part of your project. You can draw it on paper, draw using Visio, or you can design it in Scene Builder and provide a screenshot. 3. Project Class Structure. Use UML class diagram(s) to present the rough class design you envision for the application. You should include all significant classes and their relationships (arrows). Fields and methods are not required to be listed. Diagrams can be done on paper, or with a UML drawing tool like StarUML or Visio (UML Model Diagram template). It must be clear which classes are GUI classes and which classes are non-GUI (data management) classes. For JavaFX all controller classes should have names ending with "Controller". ||
Although each project will be unique, all JavaFX projects will have - FXML files for the GUI layout (one file per window) - Controller classes for the GUI event handlers (one per window) - Data management classes (typically two or more) When designing a larger application like your course project avoid putting data management code in the controller (GUI) classes. 4. Division of responsibilities. To the extent possible, list the planned division of responsibilities, e.g. who will work on which classes, who will design/implement the GUI, etc. Work should be divided between group members as evenly as possible one group member should not do most of = the work! The proposal is not final. If it needs to be modified to be accepted, I will let you know. During development certain functionality may be changed, modified, added or removed. Your original design may change - this is a part of a normal development process. The proposal must be updated and resubmitted if there are any major changes. The professionalism of your submission, and clarity of written communication is important. If your proposal is incomplete or missing any major element by the project due date you will receive the penalty.