Large system applications
Small system applications
Medium system applications
Very small system applications
A. Large system applications
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
Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
Procedure-oriented, Structured
Structured, Procedure-oriented
Structured, Object-oriented
Object-oriented, Structured
Which is used by one person only
Which is assigned one and only one task
Which uses one kind of software
Which is meant for application software
Profit maximization
Cost reduction
Customer satisfaction
All of the above
Failure detection
Damage assessment
Fault avoidance
Fault repair
processing
programming
storing
organizing
Lower
Back-end
Intermediate
Upper
data,architectural and procedural designs only
architectural,procedural and interface design only
data,architectural and interface design only
data,architectural interface and procedural design
Spiral model
Incremental model
Iterative model
Waterfall model
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Indian Statistical Organization
Inter State Organization
International Standards Organization
Indian Standards Organization
System Operator
Salesman
Database Manager
Accountant
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
Waterfall
Spiral
Iterative
Cleanroom
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Intermediation
Disintermediation
Mediation
None of the above
Software Analysis
Software Design
Software quality
Software testing
Understanding
Restrictions
Transparency
Controversy
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
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.
distinctly specific
unambiguous
all of these
functional
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Function reuse
Application system reuse
Sub- system reuse
Generator based reuse
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