Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

OOAD Terms for IBM Test 486

 
Ashik Uzzaman
Ranch Hand
Posts: 2373
Eclipse IDE Firefox Browser Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear Pals,
I have been going through the OOAD@Whiz diagnostics test and found the following terms that needs a little more clarification to me. Please have your 1 or 2 lines comment on them.
  • throughput
  • contengency factor
  • legacy system
  • impedance mismatch
  • debit card
  • cohesion
  • qualified association
  • discriminator
  • mitigation strategy


  •  
    Ashik Uzzaman
    Ranch Hand
    Posts: 2373
    Eclipse IDE Firefox Browser Java
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    load factor - It is the difference between the ideal time and the real time needed to finish a project, and measured in percentage.
    BTW, how much is it different from contingency factor?
    [ March 26, 2003: Message edited by: Ashik uzzaman ]
     
    Bob Runstein
    Greenhorn
    Posts: 6
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
     throughput: A performance measurement. The amount of useful work that can be done by a system in a certain period of time. e.g., the number of transactions per second.
     contingency factor: The amount of time added to the estimate for construction time of a project due to the risks identified for the project. It is calculated as a percentage of the total construction time and is typically 10 to 20 percent, depending on the level of risk.
     legacy system: A system that already exists when a software project starts. Typically it uses languages, platforms, and techniques that are no longer current. Legacy systems often serve critical business needs and must be integrated into a new application rather than replaced.
     impedance mismatch: Impedance is a term borrowed from the electrical engineering discipline that refers to the opposition that a component presents to an electric current. Maximum power transfer efficiency occurs when the output impedance of a device matches the input impedance of the device it is feeding. Any mismatch in the impedance reduces the efficiency. For software it refers to differences in technology between two components or systems that reduces the efficiency of their interaction. An example is storing Objects in a Relational database. An adapter of some kind must be used to convert the Objects to columns and rows. Similarly, a Java application has an impedance mismatch with a legacy Cobol application. An adapter must be interposed to enable the systems to exchange information.
     debit card: A payment device linked to a bank account. Typically this is a plastic card with embossed numbers on the front and a magnetic stripe on the back. Payments are immediately deducted from the linked bank account, as opposed to credit cards where the payments are deducted from a line of credit that must be paid off at a future date.
     cohesion: Larman p.232 � �In terms of object design, cohesion ( or more specifically, functional cohesion) is a measure of how strongly related and focused the responsibilities of an element are.� If the responsibilities of a class are highly related and the class does not do a lot of work, it has high cohesion. If it does many unrelated things or too much work, it has low cohesion and will be brittle (easily broken by changes to other classes), hard to understand, reuse and maintain.
     qualified association: An association relationship between entities that specifies how the relationship is navigated. It reduces the cardinality of a relationship from one-to-many to one-to-one. For example, a file system may have many files. The file name may be applied as a qualifier to the relationship to specify that a file system may have only one file with a particular name.
     discriminator: A discriminator is a label applied to a generalization line on a UML diagram that specifies the basis of the subtyping. For example, a Person may be a Doctor, a Nurse or a Hospital Administrator. A Person may also be Male or Female. In the first case the discriminator would be �role�, in the second case it would be �sex�.
     mitigation strategy: A software project has many kinds of risks associated with it. Each risk needs to be rated according to its probability and impact in terms of cost, time or effort and a plan should be made to deal with the risk. A mitigation strategy is a plan that details steps that reduce either the probability of the risk materializing or reduce the impact of the risk, or both.
    Bob Runstein
    co-author, OOAD@Whiz
    Microsoft Certified Professional
    Sun Certified Developer for the Java 2 Platform
    Sun Certified Enterprise Architect for the Java 2 Platform
     
    Ashik Uzzaman
    Ranch Hand
    Posts: 2373
    Eclipse IDE Firefox Browser Java
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Thank you Bob. Your reply is full of valuable info. And your OOAD@Whiz is one of the best exam simulation product I have ever seen in terms of UI, content organization -- I did not get enough time to gothrough the questions so can't comment on them, but the few i saw were technically rich!
    Thanks again.
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic