CS504 Grand Quiz Mega File Set 2

FILE 1

Q1. Whole part structure is also called

1. Generalization
2. Aggregation
3. Specialization
4. Association
5. A prototype is not the real product. It is rather just a real looking of what would be eventually delivered and might not do anything useful.

1. Mock-up
2. Ad-hoc
3. Design
4. Structure

Q3. In "Railway ticket reservation system" the roles such as inquiry, reservation, ticketing and cancellation are to be performed by the user called:-

1. Passenger
2. System analyst
3. System developer
4. System designer

Q4. A useful technique for evaluating the overall complexity of a proposedarchitecture is to look at the component's

1. number and size of components
2. flow dependencies and sharing dependencies
3. size and cost
4. function points

5.

relationship is concerned with classes not with the class instantiates.

1. Association
2. Inheritance
3. Aggregation
4. Composition
5. Software development is a step-by-step process, and in phase of software development Business Objective of an organization gets cleared.

1. Maintenance
2. Development
3. Definition
4. Vision

Q7. The data on which the program operates is also considered as part of the

1. Important Data
2. Software
3. Logical Data
4. Utility Software

Q8. From the following which is/are not the example(s) of illegal data flow in Data Flow Diagram (DFD)

1. External Agents directly communicating with each other
2. External Agent updating information in a DataStore
3. External Agent accessing information from a Data Store
4. There must be an intermediate process which should transform data received from one external entity and then send the transformed data to the other external entity
5. In sequence diagram, the objects are organized in a line and the events in a time line.

1. Horizontal, straight
2. Vertical, straight
3. Horizontal, vertical
4. Vertical, horizontal
5. Consider the following piece of code: public class Square extends Shape { // some code

The above code is an example of: a. Part-Whole relationship b. Generalization/Specialization c. Data Sharing d. Data encapsulation

11. Requirement engineering mainly deals with the

of the system

1. Vision Phase
2. Definition Phase
3. Development Phase
4. Maintenance Phase
5. A relationship indicates that one entity is composed of one or more parts which are themselves instances of that or another entity.

1. Inheritance
2. Whole-part
3. Generalization
4. Specialization

Q13. In UML Object Model Notation

1. C++ language-specific programs are constructed
2. mathematical problems are visualised
3. relationships among classes and sub-classes are expressed
4. Graphs and tables are used to explain Software Engineering principles
5. In the case of , intra component linkages are stronger while inter component linkages are weak.

1. high cohesion
2. low coupling
3. low cohesion
4. high coupling
5. Transactions are the

that must be remembered through time.

1. Actions
2. Triggers
3. Methods
4. The modules interacting with each other through message passing have between them.

1. low cohesion
2. high cohesion
3. high coupling
4. In UML based Object Oriented model of a system, the inheritance relation between two classes is shown by a sign towards the super-class side on the association line between the two.

1. A filled diamond
2. An unfilled diamond
3. A half arrowhead

Q18. Which statement is not according to the software engineering principles? Software engineering is a(n)

1. Balancing act
2. Disciplined approach
3. Unsystematic approach
4. Quantifiable approach
5. A is not the real product but just a real looking mock-up of what would be eventually delivered.

1. Software
2. Program
3. Prototype(page 68)
4. Test Case

Q20. The best way to conduct a requirements validation review is to

1. examine the system model for errors
2. have the customer look over the requirements
3. send them to the design team and see if they have any concerns
4. use a checklist of questions to examine each requirement
5. More powerful hardware resulted into the development of powerful and software.

1. less, complex
2. more, complex
3. more, simple
4. less, simple
5. Events
6. low coupling
7. An arrowhead