Learn and Evaluate
Alerts! Are you having the teaching of same standards like other sections in your or other universities
Object Oriented Software Engineering
Object Oriented Programming
Essentials of Cyber Security
E Marteking Tips
English 11 and 12
C Sharp Language
True/False Questions for Operation Contracts
Pre-conditions is the most critical part in operation contract.
Using attributes, Javadoc tags, or pre-compilers pre-conditions and post conditions can be provided in Java and C#.
In Inception phase of UP, Contracts are not motivated since they are too detailed.
If developers easily understand what to do without operation contracts, then operation contracts can be skipped
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.
In iterative and evolutionary methods, all analysis and design artifacts are considered partial and imperfect, and evolve in response to new discoveries.
UML operation specification can not show an algorithm or solution, but only the state changes or effects of the operation
Write operation contracts in a declarative, present tense form.
Write operation contracts in a declarative, passive past tense form.
One common mistake in operation contract is "Forgetting to include the forming of associations when new instances are created".
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.
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.
Post conditions are observations about the domain model objects that are true when the operation has finished after the smoke has cleared.
Post conditions are NOT actions to be performed during the operation of an operation contract
The post condition section of operation contract state changes include instances created, associations formed or broken, and attributes changed.
A single operation contract CANNOT have more than one operation contract.
A single system operation of SSD can have more than one operation contracts.
Operation contracts are defined against the system operations which were identified in system sequence diagrams.
Noteworthy assumptions about the state of the system or objects is recorded in pre-condition section of operation contract.
Noteworthy assumptions about the state of the system or objects is recorded in post condition section of operation contract.
In Operation Contract artifact the "Cross References" section describes the name and parameters of the system operation.
Who we are
Write to Us
Learn and Evaluate
Industry Liason Cell (ILC)
© 2020 - Subject Expert