classical life cycle model
Fountain model
Spiral model
Concurrent model
A. classical life cycle model
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
distinctly specific
unambiguous
all of these
functional
Class Name
Entity
Attributes
Service
1-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
Spiral model
Incremental model
Iterative model
Waterfall model
Intermediation
Disintermediation
Mediation
None of the above
processing
programming
storing
organizing
that are not relevant to him
that re relevant to him
that may be maliciously handled by him
that are confidential
Identify system- processing transformation
Identify input transformation
Identify output transformation
All the above
Entity- relation model
Data flow model
Structural model
Object model
Study and understand the problem
Identify gross features of at least one possible solution.
Describe each abstraction used in the solution
Maintenance
Internet Explorer
Mozilla
MS-Office
Oracle
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
Madhavji
Sutton
Khalifa
Humphrey
System Operator
Salesman
Database Manager
Accountant
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
interface design
data design
procedural design
architectural design
Confidentiality
Intellectual property rights
Managing Client Relationships
Both a & b
User Action Notation
User Action Norms
User Analogy Notation
User Analogy Norms
abstraction
refinement
information hiding
all of above three
1-True, 2-True
1-True, 2-False
1-False, 2-True
1-False, 2-False
Profit maximization
Cost reduction
Customer satisfaction
All of the above
Unit testing
Integration testing
Validation testing
System testing
data,architectural and procedural designs only
architectural,procedural and interface design only
data,architectural and interface design only
data,architectural interface and procedural design
bottom-up
random
top-down
center fingring
70 to 80
30 to 40
50 to 60
10 to 20
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
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-False, 2-False
1-True, 2-False
1-False, 2-True
1-True, 2-True
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.