Unauthorized modification of computer material
Unauthorized access to computer material
Dissemination of viruses or other malware
All of the mentioned
D. All of the mentioned
A Combination of prototyping and waterfall model
Includes project risks evaluation during each iteration
A high speed adaptation of the linear sequential model
Used to suggests a systematic sequential approach to software development
classical life cycle model
Fountain model
Spiral model
Concurrent model
Intermediation
Disintermediation
Mediation
None of the above
licensing
responsiveness
processing time
memory utilization
Grey- box testing
White box testing
Black box testing
Red Box Testing
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.
sometimes
many times
always
no times
Class Name
Entity
Attributes
Service
Polymorphism
Encapsulation
Inheritance
Information hiding
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Large system applications
Small system applications
Medium system applications
Very small system applications
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
bottom-up
random
top-down
center fingring
Software Analysis
Software Design
Software quality
Software testing
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
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.
Upper
Front-end
Intermediate
Lower
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
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-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
processing
programming
storing
organizing
Arrow Head
Rectangle
Rounded Rectangle
Circle
Data- flow design
Structural decomposition
Detailed design description
All the above
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.
Unit testing
Integration testing
Validation testing
System testing
Design
Project Management
Maintenance
Quality management
Minimization, Satisfaction
Minimization, Dissatisfaction
Maximization, Satisfaction
Maximization, Dissatisfaction
System Operator
Salesman
Database Manager
Accountant
An Old Fashioned model that cannot be used in a modern context
A good approach when a working program is required quickly
A useful approach when a customer cannot define requirements clearly.
A reasonable approach when requirement are well defined.