Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
CECS 343 Quiz5- CH.6
| Question | Answer |
|---|---|
| Before performing requirements engineering activities, organizations must plan: A. Programming languages B. Resources, methodology, and time C. Database structures D. Compiler design | B. Resources, methodology, and time |
| Some organizations perform requirements engineering as: A. A testing phase B. A separate stand-alone activity C. A debugging stage D. A coding phase | B. A separate stand-alone activity |
| Which of the following is a major requirements engineering activity? A. Deployment B. Prototyping C. Debugging D. Refactoring | B. Prototyping |
| Requirements documentation is important because it: A. Replaces the need for testing B. Helps control scope creep C. Eliminates the need for coding D. Removes the need for users | B. Helps control scope creep |
| Requirements elicitation refers to: A. Coding requirements B. Collecting requirements from stakeholders C. Deleting requirements D. Testing requirements | B. Collecting requirements from stakeholders |
| Requirements may be provided to software engineers as part of: A. Hardware installation instructions B. A request for price quotation C. Compiler specifications D. A coding manual | B. A request for price quotation |
| Software engineers who work closely with business management to gather requirements are often called: A. Database administrators B. Business analysts C. Software testers D. Network engineers | B. Business analysts |
| Which of the following is part of high-level requirements elicitation? A. Project scope B. CPU architecture C. Programming syntax D. Assembly language | A. Project scope |
| Requirements analysis involves: A. Writing code B. Categorizing and prioritizing requirements C. Designing algorithms D. Testing programs | B. Categorizing and prioritizing requirements |
| Functional requirements describe: A. System performance B. What the system should do C. Hardware specifications D. Network topology | B. What the system should do |
| Non-functional requirements include: A. Algorithms B. Input formats C. Performance and reliability D. Data structures | C. Performance and reliability |
| Which of the following is one of the six dimensions of requirements? A. Business flow B. Compiler optimization C. Machine code D. Memory allocation | A. Business flow |
| User interfaces fall under which requirement dimension? A. Functional requirements B. Interface requirements C. Constraint requirements D. Data requirements | B. Interface requirements (user interfaces) |
| Which of the following is considered a constraint requirement? A. Security B. Data structures C. Programming syntax D. File naming conventions | A. Security |
| View Oriented Requirements Definition (VORD) focuses on: A. Hardware design B. Different stakeholder viewpoints C. Database queries D. Code efficiency | B. Different stakeholder viewpoints |
| Requirements prioritization is necessary because projects often have: A. Unlimited budgets B. Limited time and resources C. Unlimited developers D. Unlimited computing power | B. Limited time and resources |
| Which factor may influence requirement prioritization? A. Market competition B. Programming language syntax C. Compiler version D. CPU speed | A. Market competition |
| Which prioritization method involves comparing requirements pair-by-pair? A. Linear regression B. Analytical Hierarchy Process C. Binary search D. Divide and conquer | B. Analytical Hierarchy Process |
| The Analytical Hierarchy Process (AHP) is used to: A. Compile programs B. Prioritize requirements C. Design networks D. Build prototypes | B. Prioritize requirements |
| Requirements definitions may be written using: A. Data Flow Diagrams B. Assembly instructions C. CPU registers D. Encryption algorithms | A. Data Flow Diagrams |
| Data Flow Diagrams (DFD) primarily capture: A. Data movement and processes B. CPU architecture C. Programming language grammar D. Network routing | A. Data movement and processes |
| Entity Relationship Diagrams (ERD) describe: A. Data relationships B. User interfaces C. Program loops D. Encryption methods | A. Data relationships |
| Unified Modeling Language (UML) use case diagrams identify: A. Actors and system functionalities B. CPU instructions C. Hardware components D. Machine code | A. Actors and system functionalities |
| Use cases describe: A. Database indexing B. System interactions with users C. Compiler behavior D. Hardware installation | B. System interactions with users |
| Requirements traceability ensures that requirements can be tracked: A. Only during testing B. Through design, implementation, and testing C. Only during coding D. Only after release | B. Through design, implementation, and testing |
| Requirements traceability helps ensure that: A. Code compiles faster B. All requirements are implemented C. Hardware is upgraded D. Networks run faster | B. All requirements are implemented |
| Requirements prototyping mainly focuses on: A. Hardware components B. User interface behavior and layout C. CPU performance D. Programming syntax | B. User interface behavior and layout |
| Low-fidelity prototypes typically use: A. Paper sketches or cardboard mockups B. Full production code C. Complex databases D. Network simulations | A. Paper sketches or cardboard mockups |
| High-fidelity prototypes usually involve: A. Fully automated UI tools or simple software implementations B. Paper drawings only C. Manual calculations D. Hardware testing | A. Fully automated UI tools or simple software implements |
| A requirements specification document typically includes: A. Introduction B. High-level description C. Detailed requirements D. All of the above | D. All of the above |
| Performance requirements typically specify: A. Response time and throughput B. Programming syntax C. Memory addresses D. Compiler behavior | A. Response time and throughput |
| Design constraints may include: A. Security and reliability standards B. Programming loops C. CPU registers D. File compression methods | A. Security and reliability standards |
| Requirements sign-off serves as: A. The end of coding B. A milestone marking completion of the requirements phase C. A debugging checkpoint D. A testing milestone | B. A milestone marking completion of the requirements phase |
| Requirements sign-off also creates: A. A baseline for future changes B. A new programming language C. A hardware specification D. A network architecture | A. A baseline for future changes |
| One criticism of strict sign-off processes comes from: A. Waterfall development B. Agile development C. Hardware engineering D. Network design | B. Agile development |
| Some organizations perform requirements engineering as a separate stand-alone activity in order to? | Price the activity separately from the software project |
Created by:
MinYoongi67