sometimes
many times
always
no times
C. always
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Madhavji
Sutton
Khalifa
Humphrey
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.
classical life cycle model
Fountain model
Spiral model
Concurrent model
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
that are not relevant to him
that re relevant to him
that may be maliciously handled by him
that are confidential
Entity- relation model
Data flow model
Structural model
Object model
Waterfall model
Incremental model
Spiral model
Iterative model
Failure detection
Damage assessment
Fault avoidance
Fault repair
Upper
Front-end
Intermediate
Lower
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Unit testing
Integration testing
Validation testing
System testing
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
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
bottom-up
random
top-down
center fingring
Ability to deliver software on time with good quality
A situation in which experienced developers leave the company
Inability of new software to inter-operate with existing software
Instability in the development team
distinctly specific
unambiguous
all of these
functional
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Asset
Resource
Problem Solver
Knowledge Provider
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
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.
70 to 80
30 to 40
50 to 60
10 to 20
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Grey- box testing
White box testing
Black box testing
Red Box Testing
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
Internet Explorer
Mozilla
MS-Office
Oracle
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
Behavioural error
Logic errors
Performance error
Interface error