• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Again Coupling & Cohesion confusion

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
A company has a business application that provides its users with many different reports. The company has just purchased some new state-of-the-art, wireless printers and a programmer has been assigned the task of enhancing all of the reports to use not only the company old printers but the new wireless printers as well. When the programmer discovers that because of the design of the application, it is necessary to make changes to each report to support the new printers. Which two design concepts most likely explain this situation?
A. Tighter encapsulation
B. Low cohesion
C. Tight cohesion
D. High cohesion
E. Loose cohesion
F. Object mutability
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic