Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Expectation of future functionality enhancements

 
Ranch Hand
Posts: 170
Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The specifications mentions that:
"Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a framework that will support this with minimal disruption to the users when this occurs."
(notice it's a should and not a must)

now unless you do a complex runtime integration of functionality (that is, sending the logic to the client
which will make you fail the assignment since no security manager and code download is permitted in the
assignment) you'll have to change the executable at the client.

if so, then this is the only disruption the user can have (no matter if you do a minor change or write a completely
new application from scratch). I don't really get what they wanted to say in that sentence.
 
Bartender
Posts: 4568
9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I interpreted it more in terms of usability (note it specifically refers to the user-interface, not the rest of the client). So ideally you'd be able to add functionality without users losing familiarity with how the existing functionality works.
 
Ranch Hand
Posts: 159
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For the assignment you had to implement two search fields: one for searching by name and one for location.
In the near future the application may need more search fields.
So, is it easy to add some extra search fields, without having to rewrite parts of your GUI code?
 
Jonathan Elkharrat
Ranch Hand
Posts: 170
Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Dennis Grimbergen wrote:For the assignment you had to implement two search fields: one for searching by name and one for location.
In the near future the application may need more search fields.
So, is it easy to add some extra search fields, without having to rewrite parts of your GUI code?



that what i though but then it's not "with minimal disruption to the users" but rather "with minimal disruption to the programmers"
 
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Matthew Brown wrote:I interpreted it more in terms of usability (note it specifically refers to the user-interface, not the rest of the client). So ideally you'd be able to add functionality without users losing familiarity with how the existing functionality works.


That's how I interpreted it too
 
Ranch Hand
Posts: 101
Netbeans IDE Oracle Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
two search field? how? but i thought criteria[n] should match field n, according to the instruction. i think all fields should be checked.
 
Jonathan Elkharrat
Ranch Hand
Posts: 170
Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Oladeji Oluwasayo wrote:two search field? how? but i thought criteria[n] should match field n, according to the instruction. i think all fields should be checked.



FROM THE SPECIFICATIONS:

The User Interface
The user interface for this assignment must satisfy the following criteria:
• It must be composed exclusively with components from the Java Foundation Classes (Swing components).
• It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user.
• It must present search results in a JTable.
• It must allow the user to book a selected record, updating the database file accordingly.
 
Roel De Nijs
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Oladeji Oluwasayo wrote:two search field? how? but i thought criteria[n] should match field n, according to the instruction. i think all fields should be checked.


True, the find-method will check all fields, but in your gui you need only 2 fields (name and location).
 
I wasn't selected to go to mars. This tiny ad got in ahead of me:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic