Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
27 views2 pages

Lecture 4 Questions

The document contains a series of multiple choice questions about requirements analysis and modeling techniques used in systems analysis and design. It covers topics like the purpose of domain models, use case diagrams, distinguishing between functional and non-functional requirements, examples of non-functional requirements, how requirements are represented after discovery, consequences of a poor analysis phase, the role of a systems analyst, examining source documents, what domain models show, characteristics of good requirements, and types of requirements.

Uploaded by

ahmed.eg3842
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
27 views2 pages

Lecture 4 Questions

The document contains a series of multiple choice questions about requirements analysis and modeling techniques used in systems analysis and design. It covers topics like the purpose of domain models, use case diagrams, distinguishing between functional and non-functional requirements, examples of non-functional requirements, how requirements are represented after discovery, consequences of a poor analysis phase, the role of a systems analyst, examining source documents, what domain models show, characteristics of good requirements, and types of requirements.

Uploaded by

ahmed.eg3842
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

1. What is the purpose of a domain model (ERD)?

A) To identify things of interest which eventually form aspects of the database


B) To demonstrate how a source document can yield useful information for designing the
database
C) To show how form analysis can lead to a design
D) To illustrate the kind of information we can obtain and how we can use this information
Answer: B

2. What is the purpose of modelling business activities using Use Case diagrams?
A) To model the behaviour of the system
B) To identify the types of people or systems that interact with the system
C) To represent a real-world scenario
D) To capture work processes and provide a high-level view of what the system does
Answer: D

3. What is the distinction between functional and non-functional requirements?


A) Functional requirements describe the system behaviour, while non-functional
requirements describe the system availability
B) Functional requirements describe what the system does, while non-functional
requirements describe other aspects of the system
C) Functional requirements describe the user interface, while non-functional requirements
describe the data requirements
D) Functional requirements describe the implementation of the system, while non-
functional requirements describe the performance of the system
Answer: B

4. What are examples of non-functional requirements?


A) General requirements, usability requirements, operational requirements
B) General requirements, data requirements, usability requirements
C) Implementation requirements, performance requirements, operational requirements
D) Data requirements, usability requirements, performance requirements
Answer: C

5. How are requirements represented after discovery?


A) Requirements are represented using programming code
B) Requirements are represented using diagrams and charts
C) Requirements are documented using models and natural language descriptions
D) Requirements are documented using formal specification languages like Z Notation
Answer: C

6. What are the consequences of a poor analysis phase?


A) Facilitates communication between stakeholders
B) Improves the understanding of the problem domain
C) Leads to clear requirements discovery
D) Affects later stages of SDLC through exponentially increasing costs
Answer: D
7. What is the role of a systems analyst?
A) Manage future revisions of requirements
B) Discover as much as possible about the problem domain
C) Document requirements accurately and consistently
D) Elicit requirements from as many sources as possible
Answer: B

8. What is the purpose of examining a source document?


A) To survey stakeholders
B) To discover issues and confirm requirements
C) To document observations and get approval
D) To observe business processes
Answer: C

9. What does a domain model (ERD) show?


A) Main activities and initiators of activities
B) Flow of data
C) Functionality of the proposed system
D) Order of processing and trigger events
Answer: A

10. What are the characteristics of good requirements?


A) Complete, Untraceable, Precise, Consistent, Concise, Incorrect, Feasible, Atomic,
Testable, Ambiguous
B) Complete, Traceable, Precise, Consistent, Concise, Correct, Feasible, Atomic, Testable,
Unambiguous
C) Complete, Untraceable, Precise, Inconsistent, Concise, Correct, Infeasible, Atomic,
Testable, Unambiguous
D) Incomplete, Untraceable, Vague, Inconsistent, Lengthy, Incorrect, Infeasible, Complex,
Ambiguous
Answer: B

11. What are the types of requirements?


A) Functional, Non-functional, General, Data, Usability, Implementation, Performance,
Reliability
B) Functional, Non-functional, General, Data, Usability, Implementation, Performance,
Operational
C) Functional, Non-functional, General, Data, Usability, Implementation, Efficiency,
Operational
D) Functional, Non-functional, Specific, Data, Usability, Implementation, Performance,
Operational
Answer: B

12. Data requirements: The ISBN is a ……. -part item:


A) 4
B) 5
C) 3
D) 6
Answer: B

You might also like