Worksheetscnpm
Total questions: 126
Worksheet time: 1hrs 3mins
What is the first stage in the software development lifecycle?
A. Design
B. Specification
C. Implementation
D. Evolution
Which stage in the software development process focuses on testing and ensuring the quality of the software?
A. Design
B. Validation
C. Evolution
D. Specification
Which stage occurs after the software has been released and requires improvements or modifications?
A. Specification
B. Validation
C. Evolution
D. Implementation
In a plan-driven process, how is progress typically measured?
A. Through customer feedback
B. Against a predefined plan
C. Based on incremental changes
D. By the number of software iterations completed
Which statement is true about real-world software development processes?
A. They are exclusively plan-driven
B. They are exclusively agile
C. They often combine elements of both plan-driven and agile approaches
D. There is only one right way to develop software
What is the overall goal of real software processes?
A. To create inter-leaved sequences of activities.
B. To specify, design, implement, and test a software system.
C. To focus on technical activities only
D. To organize activities differently in different processes.
Which of the following is NOT one of the four basic process activities?
A. Specification
B. Development
C. Validation
D. Management
How are the four basic process activities organized in different development processes?
A. They are always organized in the same sequence.
B. They are organized randomly
C. They are organized differently depending on the specific process.
D. They are not important for different development processes.
Which of the following software processes primarily relies on a predefined plan and measures progress against that plan?
A. Agile Process
B. Plan-driven Process
C. Hybrid Process
D. Incremental Process
What is agile processes?
A. Processes where all the process activities are planned, and progress is measured against this plan.
B. Planning is incremental, and it is easier to change the process to reflect changing customer requirements.
C. Process focuses on breaking down work into smaller, manageable chunks.
D. It's a flexible and adaptive cycle that continuously refines and improves the product.
Which statement accurately reflects the nature of real-world software processes?
A. All software processes are either purely Plan-driven or Agile and cannot be combined.
B. Real-world software processes never include elements of both Plan-driven and Agile approaches.
C. Real-world software processes often incorporate elements of both Plan-driven and Agile approaches.
D. No software process is considered suitable for every project.
What are real software processes composed of?
A. Only technical activities
B. Only managerial activities
C. Inter-leaved sequences of technical, collaborative, and managerial activities
D. Only collaborative activities
What is the overall goal of the activities in a software process?
A. Marketing a software product
B. Specifying, designing, implementing, and testing a software system
C. Writing documentation
D. Providing user support
What are the three core activities involved in the requirements engineering process?
A. Requirements elicitation, specification, validation, and verification
B. Requirements elicitation and analysis, specification, and validation
C. Requirements analysis, specification, validation, and implementation
D. Requirements elicitation, specification, testing, and deployment
What is the goal of the requirements specification process?
A. To verify that the system meets user needs
B. To define the requirements in detail for stakeholders and developers
C. To implement the system’s architecture
D. To test the system’s performance
What is the primary goal of requirements validation?
A. Defining the system’s architecture
B. Checking the validity of the requirements
C. Developing the system’s functionality
D. Gathering requirements from stakeholders
What is four basic process activities ?
A. Specification, development, validation and evolution
B. Specification, validation, design and evolution
C. Design, documentation, evolution and development
D. Specification, validation, design and documentation
Which of the following is not one of the four basic process activities?
A. Specification
B. Development
C. Documentation
D. Validation
How are real software processes structured?
A. As a fixed sequence of tasks
B. As inter-leaved sequences of technical, collaborative, and managerial activities
C. As a collaborative-only activity
D. As a technical-only process
Which process in the requirements engineering focuses on identifying what stakeholders expect from the system?
A. Requirements validation
B. Requirements specification
C. Requirements elicitation and analysis
D. System development
What is the main goal of the requirements specification process?
A. To check the validity of the requirements
B. To define the requirements in detail
C. To estimate the project budget
D. To implement the system
What is the purpose of the requirements validation process?
A. To check and ensure the validity of the requirements
B. To gather requirements from stakeholders
C. To define system constraints
D. To develop software modules
What is a requirement?
A. A list of specifications for a project.
B. A statement that can range from an abstract service to a detailed functional specification
C. A rule that must always be followed.
D. A requirement is always a simple and easy-to-interpret guideline.
Why must requirements sometimes be open to interpretation?
A. Because they are always unclear.
B. Because they are the basis for bids for contracts.
C. Because they are part of the contract itself.
D. Because no one knows what the requirement is.
What dual functions can requirements serve?
A. Defining project goals and testing methods.
B. Writing documentation and serving clients.
C. Being the basis for a contract bid and the contract itself.
D. Developing new systems and maintaining old ones.
What is Software specification?
A. The set of establishing what services are required and the constraints on the system’s operation and development.
B. The part of establishing what services are required and the constraints on the system’s operation and development.
C. The way of establishing what services are required and the constraints on the system’s operation and development.
D. The process of establishing what services are required and the constraints on the system’s operation and development.
Fill in the blank: “Software specification is the ______ of establishing what services are required and the constraints on the system’s operation and development.”
A. Set.
B. Part.
C. Process.
D. Way.
Requirements engineering process include which of the following?
A. Specification.
B. Design.
C. Implementation.
D. Evolution.
What is the primary purpose of the document described?
A. To outline the system's development timeline.
B. To define the system’s functions, services, and constraints.
C. To list all system errors and troubleshooting steps.
D. To describe the aesthetic design of the system.
Who is the target audience for the natural language statements and diagrams of the system's services?
A. System developers.
B. Project managers.
C. Customers.
D. Marketing teams.
In what context might this document be used as part of a contract?
A. To determine system pricing.
B. To clarify what should be implemented between client and contractor.
C. To resolve system performance issues.
D. To provide system maintenance guidelines.
What is a requirement?
A. It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.
B. It may range from a low-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.
C. It may range from a high-level abstract statement of a service to a detailed mathematical functional specification.
D. It may range from a low-level abstract statement of a service or of a system constraint to a detailed functional specification.
Why are requirements range from high-level abstract statements to a detailed mathematical functional specification?
A. As requirements always are changed by customer.
B. As requirements may serve a dual function.
C. As requirements always serve a dual function.
D. As requirements may changed by customer.
Why might the same requirement need to be both open to interpretation and defined in detail?
A. To allow room for mathematical analysis.
B. To serve as the basis for both a contract bid and the contract itself.
C. To provide clarity for abstract services.
D. To ensure requirements are always flexible.
What are functional requirements of a system?
A. Statements of services the system should provide, how the system reacts to specific inputs.
B. Timing constraints and development process restrictions.
C. Standards the system must follow.
D. Constraints from the system's domain of operation.
Non-functional requirements typically apply to?
A. Only specific features of the system.
A. Only specific features of the system.
C. The system as a whole.
D. Only related software components.
Which of the following is an example of a domain requirement?
A. The system must follow security standards.
B. The system must not process data after 10 PM.
C. The system must be compatible with the organization’s operating environment.
D. The system must respond to data input within 1 second.
Who is considered a stakeholder in a system?
A. Only the end users who interact with the system.
B. Any person or organization affected by the system and who has a legitimate interest.
C. Only the developers who create the system.
D. Only the external regulators of the system.
Which of the following is NOT a type of stakeholder?
A. End users.
B. System managers.
C. External stakeholders.
D. System developers.
Which stakeholder type is primarily responsible for the day-to-day operation of the system?
A. End users.
B. System managers.
C. System owners.
D. External stakeholders.
What are user requirements?
A. A structured document detailing the system’s functions and services.
B. Statements in natural language with diagrams describing the system's services and constraints.
C. A contract between the client and the contractor.
D. A technical document describing system architecture.
What is the purpose of system requirements?
What is the purpose of system requirements?
B. To define detailed descriptions of system functions and constraints, and may form part of a contract.
C. To include natural language descriptions of the system for non-technical stakeholders.
D. To provide a high-level view of user needs.
How do system requirements differ from user requirements?
A. System requirements are written for customers, while user requirements are technical specifications.
B. User requirements focus on how the system should be implemented, while system requirements describe only the user interface.
C. System requirements provide structured and detailed descriptions, while user requirements are more general and written in natural language.
D. User requirements are more detailed and contractual, while system requirements are brief and high-level.
What are functional requirement?
A. Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations.
B. Constraints on the system from the domain of operation.
C. Statements of services the system shouldn’t provide, how the system should react to particular inputs and how the system should behave in particular situations.
D. Often apply to the system as a whole rather than individual features or services.
”Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.”What kind of a requirement the system is providing ?
A. Functional requirements.
B. Non-functional requirements.
C. Domain requirements.
D. Functional
What are domain requirements?
A. Constraints on the system from the domain of operation.
A. Constraints on the system from the domain of operation.
C. May state what the system should not do.
D. Constraints on the system not from the domain of operation.
What is requirements engineering?
A. The process of designing a system.
B. The process of testing a system.
C. The process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed.
D. The process of implementing a system.
What are system requirements?
A. The descriptions of the system's hardware.
B. The descriptions of the system's software.
C. The descriptions of the system services and constraints that are generated during the requirements engineering process.
D. The descriptions of the system's users.
What is the primary goal of requirements engineering?
A. To design the system architecture.
B. To develop the system's code.
C. To understand and document the customer's needs.
D. To test the system's functionality
Which step in the requirements engineering process is responsible for gathering and analyzing user requirements?
A. Requirements specification.
B. Requirements validation.
C. Requirements elicitation and analysis.
D. System descriptions.
What is the final document produced after completing the requirements engineering process?
A. System descriptions.
B. User and system requirements.
C. Requirements specification.
D. Requirements document.
Which step ensures that the requirements are accurate and meet the intended needs?
A. Requirements elicitation and analysis.
B. Requirements specification
C. Requirements validation.
D. User and system requirements.
What is the main goal of requirements elicitation?
A. To develop a prototype
B. To find out about the system's domain and required services
C. To write test cases
D. To validate the system's design
Which of the following is NOT typically a concern during requirements elicitation?
A. Hardware constraints
B. Application domain knowledge
C. User interface design
D. System performance
How do software engineers prioritize and negotiate system requirements?
A. Discovering requirements from users
A. Discovering requirements from users
C. Working with stakeholders to identify the most important requirements
D. Automatically categorizing requirements by performance
What is the purpose of requirements validation?
A. To verify that the system meets the users' needs
B. To discover requirements
C. To classify and organize requirements
D. To develop system descriptions
What document is typically produced after requirements elicitation and analysis?
A. Test plan
B. Design specification
C. Requirements document
D. User manual
Which of the following is the first stage in the requirements elicitation process?
A. Requirements prioritization
B. Requirements specification
C. Requirements discovery
D. Requirements validation
Requirements classification and organization" is which step in the requirements elicitation and analysis process?
A. Step 1
B. Step 2
C. Step 3
D. Step 4
Arrange the steps of the requirements gathering and analysis process ?
A. Requirements discovery -> Requirements prioritization and negotiation -> Requirements classification and organization -> Requirements specification
B. Requirements discovery -> Requirements prioritization and negotiation -> Requirements specification ->Requirements classification and organization
C. Requirements discovery ->Requirements classification and organization -> Requirements prioritization and negotiation -> Requirements specification
D. Requirements discovery ->Requirements classification and organization ->
Requirements specification ->Requirements prioritization and negotiation
Which of the following steps are steps in the requirements eliciation and analysis process?
A. Sprint Retrospective
B. Organize the Backlog
C. Requirements discovery.
D. There is no correct answer.
Which of the following steps is not part of the requirements eliciation and analysis process?
A. Requirements discovery
B. Requirements specification
C. Requirements prioritization and negotiation
D. Organize the Backlog
Why must user requirements be understandable?
A. So that users can develop the software themselves .
B. To ensure that all users have a technical background .
C. So that users and customers without a technical background can understand clearly.
D. To reduce software development time.
Which statement talks about requirements specification ?
A. The process of writing down the user and system requirements in a requirements document.
B. System requirements are more detailed requirements and may include more technical information.
C. The requirements may be part of a contract for the system development.
D. User requirements must be understandable to end users and customers with a technical background.
What do system requirements typically include?
A. Only high-level descriptions of the system.
B. More detailed requirements and potentially more technical information.
C. User preferences and opinions
D. Marketing strategies for the software
Why does the business and technical environment of a system often change after installation?
A. New hardware may be introduced or the system may need to interface with others.
B. Systems are always stable and rarely require any changes.
C. System performance degrades, forcing updates.
D. The original environment never changes, only the system does.
What issues may arise because the people who fund the system and those who use it are different?
A. Users always get what they need from the system.
B. Customer requirements may conflict with the needs of end-user.
C. Users have complete control over system requirements.
D. Customers rarely impose budgetary or organizational constraints.
Why might new features need to be added to a system after delivery?
A. Systems are delivered with all possible features in place.
B. Changes in business priorities or regulations may require additional features.
C. Users never request new features once the system is operational.
D. Systems cannot be modified after delivery.
What can happen to a system after it is installed?
A. It will remain unchanged.
B. It may require updates to interface with other systems.
C. No new regulations will affect the system.
D. System hardware will always stay the same.
Why might there be a conflict between system customers and end-users?
A. They both have the same priorities.
B. Customers and users always agree on requirements.
C. Customers may impose requirements based on budget constraints that differ from user needs.
D. End-users are responsible for the organizational budget.
Which of the following is a reason why new features may be added to a system after delivery?
A. To meet new user support needs.
B. To decrease system functionality.
C. To eliminate the need for hardware updates.
D. To reduce the number of users.
What challenge do large systems often face due to their diverse user community?
A. All users have the same requirements.
B. Users have conflicting or contradictory requirements.
C. The system never needs updates.
D. Users rarely provide feedback.
How are the final system requirements usually determined?
A. They are based solely on the most vocal user.
B. They are always decided by the developers.
C. They are a compromise between different user requirements.
D. They never change after initial implementation.
What is the primary concern when demonstrating that the requirements define the system?
A. Meeting the development team's preferences.
B. Ensuring the system aligns with what the customer really wants.
C. Reducing the cost of implementation.
D. Increasing the complexity of the system.
Why is requirements validation considered very important?
A. It reduces the overall project timeline.
B. It helps improve the user interface.
C. Requirements error costs are high.
D. It ensures that the project follows the latest technology trends.
How much more expensive can fixing a requirements error after delivery be compared to fixing an implementation error?
A. 10 times
B. 20 times.
C. 50 times.
D. 100 times.
What is a plan-driven process?
A. processes where all the process activities are planned
B. processes in where some process activities are planned
C. progress is measured against this plan.
D. processes where all the process activities are planned and progress is measured against this plan.
In the Agile process, planning is characterized by?
A. Detailed and comprehensive from the beginning
B. Incremental and easier to change
C. Rigid and unchanging
D. Based entirely on customer requirements
In reality, software projects often encounter?
A. Only use Agile methods
B. Use only the plan transmission method
C. Include elements of both plan-driven and agile approaches.
D. Do not use any method.
What are the four fundamental activities in software processes?
A. Specification, development, validation and evolution
B. Requirements, Design, Coding, and Testing
C. Analysis, Implementation, Debugging, and Deployment
D. Planning, Scheduling, Documentation, and Maintenance
What are software processes really?
A. Inter-leaved sequences of technical, collaborative
B. Managerial activities, collaborative
C. Inter-leaved sequences of technical, managerial activities
D. Inter-leaved sequences of technical, collaborative and managerial activities
What is the overall goal of inter-leaved sequences of technical, collaborative and managerial activities?
A. Specifying
B. Designing
C. Specifying, designing, implementing and testing a software system
D. Implementing and testing a software system
The process of establishing what services are required and the constraints on the system’s operation and development is called?
A. Requirements engineering process
B. Software Development Process
C. System Maintenance Process
D. Software Testing Process
Which stage in the requirements engineering process does analyze what the system stakeholders require or expect from the system?
A. Requirements specification
B. Requirements elicitation and analysis
C. Requirements validation
D. A & B
Which stage in the requirements engineering process defines the system's requirements in detail?
A. Requirements specification
B. Requirements elicitation and analysis
C. Requirements validation
D. A & C
What is the primary purpose of requirements validation?
A. To verify the performance of the system
B. To demonstrate that the system meets customer requirements
C. To evaluate the security of the system
D. To check if the system is correctly implemented
Why is requirements validation particularly important?
A. Because requirements are often unclear
B. Because fixing a requirements error after delivery is easy
C. Because requirements errors are costly to fix after delivery
D. Because implementation errors are more costly than requirements errors
How much more costly can fixing a requirements error after delivery be compared to fixing an implementation error?
A. 10 times
B. 50 times
C. 100 times
D. 200 times
What does the "Validity" check in requirements validation aim to verify?
A. Whether the system meets its performance goals
B. Whether the system supports the customer's needs with the correct functions
C. Whether the system’s design is realistic
D. Whether the system can be verified through testing
What does the "Consistency" check focus on during requirements validation?
A. Ensuring all customer-required functions are included
B. Verifying that there are no conflicts between requirements
C. Checking if the system is within budget constraints
D. Making sure the system can be checked through testing
What is the primary goal of the "Realism" check in requirements validation?
A. To ensure the system can be implemented with the given budget and technology
B. To confirm that the system's functions meet customer needs
C. To verify that all necessary requirements are included
D. To determine if the system can be verified through testing
During a requirements review, which of the following is crucial for ensuring completeness and consistency?
A. Involving only the development team.
B. Conducting reviews without any set criteria.
C. Involving stakeholders and using predefined criteria.
D. Focusing solely on technical specifications.
What is the primary purpose of using prototyping in requirements validation?
A. To finalize the design of the system.
B. To create a complete and final version of the system.
C. To validate the system's requirements with end-users and stakeholders.
D. To write the codebase of the system.
What is the main objective of generating test cases for requirements?
A. To ensure that the system is fully developed.
B. To verify the testability and completeness of the requirements.
C. To document the final system requirements.
D. To train users on the system.
Why should regular reviews be held while the requirements definition is being formulated?
A. To accelerate the development process
B. To resolve problems at an early stage through good communication.
C. To finalize the design before requirements are complete.
D. To avoid involving clients and stakeholders.
What is one benefit of involving both developers and customers in the requirements review process?
A. It ensures that all requirements are strictly technical.
B. It helps in early identification and resolution of potential problems.
C. It limits the scope of the requirements.
D. It reduces the overall time spent on documentation.
What is a key factor that enhances the effectiveness of requirements reviews?
A. Strictly following formal procedures without client input.
B. Limiting communication to only the development team
C. Ensuring good communication between developers, customers, and users.
D. Conducting reviews after the development is complete.
What does “Verifiability” refer to in requirement review checks?
A. Whether the requirement can be traced back to its origin.
B. Whether the requirement can be realistically tested.
C. Whether the requirement is adaptable to changes.
D. Whether the requirement is properly understood.
Which review check ensures that the requirement is properly understood?
A. Verifiability
B. Adaptability
C. Comprehensibility
D. Traceability
What is checked by “Traceability” in requirement reviews?
A. Whether the requirement can be tested.
B. Whether the requirement is clearly stated and its origin identified.
C. Whether the requirement can be changed easily.
D. Whether the requirement is understood correctly
What activities are combined in a real software development process?
A. Technical, collaborative, and managerial activities
B. Only technical activities
C. Design and implementation activities
D. Marketing and sales activities
What are the four basic process activities in software development?
A. Specification, development, testing, and deployment
B. Planning, coding, testing, and maintenance
C. Specification, development, validation, and evolution
D. Design, coding, debugging, and documentation
What is the overall goal of the activities in a software development process?
A. To increase profits for the company
B. To specify, design, implement, and test a software system
C. To train developers on new technologies
D. To focus only on coding the software
What is the first step in the requirements engineering process?
A. Requirements specification
B. Requirements validation
C. Requirements elicitation and analysis
D. Requirements implementation
Which step defines the requirements in detail?
A. Requirements elicitation and analysis
B. Requirements specification
C. Requirements validation
D. Requirements review
Which process ensures that the system requirements are valid?
A. Requirements validation
B. Requirements elicitation
C. Requirements specification
C. Requirements specification
What is a requirement?
A. A requirement may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.
B. A requirement is always a detailed technical specification with no room for abstraction.
C. A requirement is strictly a system constraint and does not describe the service that the system should provide.
D. A requirement must always include mathematical specifications to be considered valid.
Why must requirements sometimes be open to interpretation?
A. Because they may be the basis for a bid for a contract - therefore must be open to interpretation.
B. Because they are always technical and never involve abstract thinking.
C. Because requirements are only used in internal system designs.
D. Because requirements never need to be clearly defined.
In what scenario must requirements be defined in detail?
A. When they are the basis for the contract itself.
B. When they are the basis for project budgeting only.
C. When they are about high-level abstract ideas that require flexibility.
D. When they do not involve any technical or functional specifications.
How many main activities are involved in the requirements engineering process?
A. Five
B. Four
C. Three
D. Six
What is the purpose of requirements validation?
A. To define the requirements in detail
B. To check the validity of the requirements
C. To establish what services are required
D. To manage the requirements throughout the project
what can a requirement be in the software development process?
A. A marketing plan
B. A business strategy statement
C. A detailed mathematical function specification
D. A user manual
What role can a requirement play in a contract ?
A. Only as the basic for software development
B. The basic for a bid for a contract
C. A legal regulation
D. A training plan
Why do requirement need to be defined in detail?
A. Because requirements can change at any time
B. Because requirements are only for referent
C. Because requirements may be the basic for the contract itself
D. Because requirements may not be necessary
How many types of requirement?
A. 1
B. 2
C. 4
D. 3
What type of user requirements are written for?
A. Developer
B. Tester
C. Customer
D. Engineer
What is included in a system requirements document?
A. The system’s functions
B. The system’s services
C. The operational constraints of system
D. All of the above
Who are the stakeholders of the system?
A. End users
B. System managers
C. System owners
D. All of the above
Which type of stakeholder is primarily responsible for the day-to-day operation of the system?
A. End users
B. System managers
C. System owners
D. External stakeholders
Why is identifying stakeholders important?
A. To ensure the system meets their needs
B. To reduce development costs
C. To speed up development
D. To reduce the number of system errors
What are functional requirements?
A. Time constraints
B. Services the system should provide
C. Development standards
D. Domain constraints
Non-functional requirements typically apply to:
A. Individual features of the system
B. The entire system
C. Specific services
D. Specific inputs
What are domain requirements?
A. Services the system should provide
B. Time constraints
C. Domain constraints
D. Development standard
What is the main difference between functional requirements and non-functional requirements?
A. Functional: tasks; Non-functional: system services.
B. Functional: what system does; Non-functional: performance and constraints.
C. Functional: timing/standards; Non-functional: system services.
D. Functional: reliability/usability; Non-functional: behavior in situations.
What are the descriptions of the system services and constraints generated during the requirements engineering process?
A. System requirements
B. Functional requirements
C. Non-functional requirements
D. Domain requirements
Which of the following best describes the process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed?
A. System Design
B. Requirements Engineering
B. Requirements Engineering
D. Software Testing
