True/False Questions for Operation Contracts

  • 1 Pre-conditions is the most critical part in operation contract. False View Answer

  • 2 Using attributes, Javadoc tags, or pre-compilers pre-conditions and post conditions can be provided in Java and C#. True View Answer

  • 3 In Inception phase of UP, Contracts are not motivated since they are too detailed. True View Answer

  • 4 If developers easily understand what to do without operation contracts, then operation contracts can be skipped True View Answer

  • 5 Operation contracts are useful in situations where the details and complexity of required state changes are awkward or too detailed to capture in use cases. True View Answer

  • 6 In iterative and evolutionary methods, all analysis and design artifacts are considered partial and imperfect, and evolve in response to new discoveries. True View Answer

  • 7 UML operation specification can not show an algorithm or solution, but only the state changes or effects of the operation True View Answer

  • 8 Write operation contracts in a declarative, present tense form. False View Answer

  • 9 Write operation contracts in a declarative, passive past tense form. True View Answer

  • 10 One common mistake in operation contract is "Forgetting to include the forming of associations when new instances are created". True View Answer

  • 11 If object X establish a relationship with another object Y in a post condition of the operation contract then it will belong to "Association formed or broken" category. True View Answer

  • 12 If object X establish a relationship with another object Y in a post condition of the operation contract then it will belong to "Attribute change State" category. False View Answer

  • 13 Post conditions are observations about the domain model objects that are true when the operation has finished after the smoke has cleared. True View Answer

  • 14 Post conditions are NOT actions to be performed during the operation of an operation contract True View Answer

  • 15 The post condition section of operation contract state changes include instances created, associations formed or broken, and attributes changed. True View Answer

  • 16 A single operation contract CANNOT have more than one operation contract. True View Answer

  • 17 A single system operation of SSD can have more than one operation contracts. False View Answer

  • 18 Operation contracts are defined against the system operations which were identified in system sequence diagrams. True View Answer

  • 19 Noteworthy assumptions about the state of the system or objects is recorded in pre-condition section of operation contract. True View Answer

  • 20 Noteworthy assumptions about the state of the system or objects is recorded in post condition section of operation contract. False View Answer

  • 21 In Operation Contract artifact the "Cross References" section describes the name and parameters of the system operation. False View Answer

Contact Us

support@subexpert.com
Write to Us View Help
Subject Expert Logo

Subject Expert

Learn and Evaluate

Follow Us
© 2020 - Subject Expert