Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
D. All the above
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
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
processing
programming
storing
organizing
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
Indian Statistical Organization
Inter State Organization
International Standards Organization
Indian Standards Organization
Minimization, Satisfaction
Minimization, Dissatisfaction
Maximization, Satisfaction
Maximization, Dissatisfaction
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
System Operator
Salesman
Database Manager
Accountant
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
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.
Unauthorized modification of computer material
Unauthorized access to computer material
Dissemination of viruses or other malware
All of the mentioned
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Accounting Personnel
Database Manager
Salesman
System Operator
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
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.
licensing
responsiveness
processing time
memory utilization
70 to 80
30 to 40
50 to 60
10 to 20
Entity- relation model
Data flow model
Structural model
Object model
abstraction
refinement
information hiding
all of above three
Fault avoidance
Fault tolerance
Fault detection
Fault repair
Intermediation
Disintermediation
Mediation
None of the above
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
bottom-up
random
top-down
center fingring
Failure detection
Damage assessment
Fault avoidance
Fault repair
Behavioural error
Logic errors
Performance error
Interface error
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b