Software Engineering - Part A (1 Mark Questions)
1. Explain any one common software myth.
One common myth is "Customers dont know what they want."
Actually, customers do know their needs, but they may not express them properly at the start.
Software engineers must help them clearly define their needs.
2. What does CMMI stand for?
CMMI stands for Capability Maturity Model Integration.
It is a model that helps organizations improve their software processes.
It defines five maturity levels of process development.
3. What are functional requirements? Give example.
Functional requirements define what a system should do.
They include tasks, functions, or features the software must perform.
Example: "The system shall allow users to log in with a password."
4. Define requirements elicitation?
It is the process of gathering software requirements from stakeholders.
It includes interviews, surveys, and meetings.
This helps in understanding what the user wants from the system.
5. Explain the purpose of sequence diagram.
A sequence diagram shows how objects interact in a system over time.
It displays the order of messages or events between objects.
It is helpful in understanding the flow of operations.
6. Describe the Design Process.
Design process is about planning the structure of software.
It decides how components will work and interact.
It includes architectural, high-level, and detailed design steps.
Software Engineering - Part A (1 Mark Questions)
7. What is validation testing?
Validation testing checks whether the final product meets user needs.
It ensures that "we built the right product".
It is done after development to check correctness and completeness.
8. Define black-box testing.
Black-box testing is testing without looking at the internal code.
Only inputs and outputs are checked.
Testers dont need to know how the system works inside.
9. Difference between Reactive and Proactive Risk Strategies.
Reactive strategy handles risks after they happen.
Proactive strategy prevents risks before they happen.
Proactive is better as it avoids problems early.
10. What is software reliability?
Software reliability is the ability of software to perform correctly over time.
It means fewer errors and more stability.
Reliable software works smoothly without frequent failures.
11. List the four layers of software engineering technology.
The four layers are:
1. Quality Focus central concern
2. Process step-by-step method
3. Methods technical approaches
4. Tools software support systems
12. What is software, and what are its main features?
Software is a set of programs and instructions used to operate computers.
Software Engineering - Part A (1 Mark Questions)
Its features include being intangible, reusable, and easy to modify.
It also includes documentation and data.
13. What are non-functional requirements? Give one example.
Non-functional requirements describe how the system works.
They relate to performance, security, or usability.
Example: "The response time shall be less than 2 seconds."
14. How is requirements validation defined?
Requirements validation ensures that all gathered requirements are correct.
It checks if they match user needs and are complete.
Errors found early save time and cost.
15. Explain the purpose of a use case diagram.
A use case diagram shows the interaction between users and the system.
It helps to identify system functionality clearly.
Actors and use cases are the main parts of it.
16. Define software architecture.
Software architecture is the high-level structure of a system.
It defines how components interact and are organized.
It is like the blueprint of software.
17. Why we need system testing?
System testing checks the entire system as a whole.
It ensures all parts work together correctly.
It is done before final delivery to users.
18. What is white-box testing?
Software Engineering - Part A (1 Mark Questions)
White-box testing is done by looking into the internal code and logic.
It tests loops, conditions, and data flow.
It requires programming knowledge.
19. Define Software Risk.
Software risk is a chance of something going wrong during development.
It may affect cost, schedule, or quality.
Risks should be identified and managed early.
20. Write any two software review guidelines.
1. Reviewers should prepare before the meeting.
2. Focus on major errors, not small grammar mistakes.
Reviews help in improving software quality.
