![[Solved] COSC2452 Week7-Independent Investigative Effort 7](https://assignmentchef.com/wp-content/uploads/2022/08/downloadzip.jpg)
| 5. This weeks programming task will cover concepts required by Assignment 2. You should aim to get the help of your tutors and make further revisions.Coding exercise steps (Hint: Need help? Ask your tutor via CanvasDiscussionsIIE07):Complete the 11/Jan/2021 solution first as this extends upon that work. Next follow CanvasModulesWeek 7 where the topics of creating non-static methods is explained. Your tutors will provide further explanations on these general topics and how they relate to this IIE during their weekly tutor chats. Please also follow the announcement How to debug large programs and get help on debugginga) In this weeks IIE, modify your own adaptation of the IIE06 student manager (which has to be different to the student manager) so that it has a console-based interface as well as a GTerm-based user interface within the same program (all within one class for now).The constructor must now take an int parameter named userInterfaceMode which when assigned an argument of:0: Allows the same functionality (adding and displaying of records) from IIE06 to be performed exclusively via the console (usingScanner for inputs and System.out for outputs)1: Allows the same functionality (adding and displaying of records) from IIE06 to be performed exclusively via the GTerm. You can reuse most of the GTerm code from your adaptation of IIE06.b) Refactor/re-organise your code so that:1. All GTerm-based method and object member variable names start with the prefix gui2. All console-based method and object member variable names start with the prefix console3. Whichever code that is somewhat common to both GTerm and console approaches must be put in to common methods and object member variables. These must not have gui or console in their names. You will likely need to some create methods that accept parameters and ones that return values (sometimes both).Tip: In IIE08, we will refactor the GUI/GTerm to one class, the console-code to another class and have the common code in yet another class to be used by the first two classes. As IIE07 is the last step before multi-class programs, it is expected it will be harder to maintain (which is what will be addressed by multi-classes in IIE08+).An important note about Assignment 2: In Assignment 2, there must be only one interface (GTerm). It is expected that students realise that there would be a better way to implement the ability to switch between different types of user interfaces and the concepts relevant to |
Access issues: For non-programming technical issues (relating to infrastructure, passwords, etc.) please call the RMIT IT Service and Support Centre for quick help on 03-9925 8888 and remember to ask for a reference number and pass it on to your instructor.
Extensions: For all new extensions, a pply for special consideration online . Contacting your tutors, instructors first will lead to delays.
Please follow/complete all steps below in the given sequence:
- Check your official @student.rmit.edu.au e mail account for announcements and other communication from the university. If getting in touch with your instructors, please only use this account (not Canvas inbox, messages, personal email, phone, Microsoft Teams, etc.)
- Watch any unwatched recordings of the Weekly Live Lecture and complete all missed tutorials before going further. For your convenience, the time stamps of recordings are sent via student email/CanvasAnnouncements.
- Is there something that you have not fully grasped from what has been covered so far? Please have your doubts clarified via one of the relevant forums under CanvasDiscussions. Leaving gaps has shown to be severely detrimental to learning.
- Did you want to make any additions to the previous IIE? Please do by replying to your original post. i.e. do not edit, change the images of existing posts as it affects submission timing.
| this will be covered when we cover multi-class programming in IIE08 (relevant to Assignment 3). |
Reviews
There are no reviews yet.