Minimization, Satisfaction
Minimization, Dissatisfaction
Maximization, Satisfaction
Maximization, Dissatisfaction
A. Minimization, Satisfaction
Waterfall
Spiral
Iterative
Cleanroom
Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
licensing
responsiveness
processing time
memory utilization
Internet Explorer
Mozilla
MS-Office
Oracle
Behavioural error
Logic errors
Performance error
Interface error
distinctly specific
unambiguous
all of these
functional
Asset
Resource
Problem Solver
Knowledge Provider
Madhavji
Sutton
Khalifa
Humphrey
major decision points are tested early
no drivers need to be written
no stubs need to be written
regression testing is not required
Accounting Personnel
Database Manager
Salesman
System Operator
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.
User satisfaction
Job satisfaction
Business success
Profit making
interface design
data design
procedural design
architectural design
System Operator
Salesman
Database Manager
Accountant
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-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Unauthorized modification of computer material
Unauthorized access to computer material
Dissemination of viruses or other malware
All of the mentioned
Boehm and Belz
Khalifa and Verner
Madhavji et al.
Blackburn et al.
that are not relevant to him
that re relevant to him
that may be maliciously handled by him
that are confidential
processing
programming
storing
organizing
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
Unit testing
Integration testing
Validation testing
System testing
sometimes
many times
always
no times
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
70 to 80
30 to 40
50 to 60
10 to 20
Entity- relation model
Data flow model
Structural model
Object model
Random Application Development
Raw Application Development
Robust Application Development
Rapid Application Development
Fault avoidance
Fault tolerance
Fault detection
Fault repair
Class Name
Entity
Attributes
Service
bottom-up
random
top-down
center fingring