objects inherit the properties of the class
classes are defined based on the attributes of the object
objects can belong to two classes
classes are always different
C. objects can belong to two classes
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
data,architectural and procedural designs only
architectural,procedural and interface design only
data,architectural and interface design only
data,architectural interface and procedural design
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Fault avoidance
Fault tolerance
Fault detection
Fault repair
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
The time between system failure
The frequency of occurrence with which unexpected behaviour is likely to occur
The elapsed repair or restart time when a system failure occurs. Given that the system must be continuously available.
The number of system failures given a number of systems inputs.
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
not use your technical skills to misuse other peoples computers.
not knowingly accept work that is outside your competence.
be dependent on their colleagues.
maintain integrity and independence in their professional judgment.
Number of request for corrective maintenance
Average time required for impact analysis
All the above
Number of oustanding change request
ensure that their products only meet the SRS.
act consistently with the public interest.
act in a manner that is in the best interests of his expertise and favour.
none
Understanding
Restrictions
Transparency
Controversy
abstraction
refinement
information hiding
all of above three
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Large system applications
Small system applications
Medium system applications
Very small system applications
Madhavji
Sutton
Khalifa
Humphrey
A useful approach when a customer cannot define requirements clearly.
Is more chaotic than the incremental model
Includes project risks evaluation during each iteration
Often used for the development of client/server applications
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
Failure detection
Damage assessment
Fault avoidance
Fault repair
Polymorphism
Encapsulation
Inheritance
Information hiding
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
The product should be easy to use.
It means that the product designed /created should be easily available.
Software engineers shall ensure that their products and related modifications satisfy the client.
Procedure-oriented, Structured
Structured, Procedure-oriented
Structured, Object-oriented
Object-oriented, Structured
classical life cycle model
Fountain model
Spiral model
Concurrent model
Internet Explorer
Mozilla
MS-Office
Oracle
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
Grey- box testing
White box testing
Black box testing
Red Box Testing
Upper
Front-end
Intermediate
Lower