4 marks

1. Write short note : System characteristics.

A system is a set of interrelated components working
together to achieve a common goal. Key characteristics
include:
Boundaries (defines scope),
Environment (external factors affecting the system),
Inputs and Outputs (data flow),
Feedback Mechanism (self-regulation),
Subsystems (smaller interconnected parts).
2. Explain the types of formal information
system.
Formal information systems are structured
and organized to support business
operations. Types include:
Transaction Processing Systems (TPS) –
Handles daily transactions.
Management Information Systems (MIS) –
Provides reports for decision-making.
Decision Support Systems (DSS) – Assists in
complex decisions.
Enterprise Systems (ERP, CRM, SCM) –
Integrates various business processes.
3. Expert system
An expert system is an AI-based system that
simulates human decision-making. It consists
of:
Knowledge Base (facts and rules),
Inference Engine (logical reasoning),
User Interface (interaction with users).
Example: Medical Diagnosis System.
4. Write short note: Element of system.
Input (resources like data, energy),
Process (transformation of input),
Output (final result),
Feedback (monitoring and control),
Environment (external factors),
Boundary (defines system limits).
5. Discuss software Qualities Factors
(McCall's quality factors).
McCall categorized software quality into:
Product Operation (correctness, reliability,
efficiency),
Product Revision (maintainability, flexibility),
Product Transition (portability, reusability).
6. Explain various characteristics of
software engineering.
Scalability (handles growth),
Maintainability (easy to update),
Efficiency (optimal resource use),
Reliability (consistent performance),
Security (protection from threats).
7. Short note: McCall's quality factors.
These factors measure software quality in
terms of reliability, efficiency,
maintainability, usability, and security.
8. Write short note: prototype model.
A software development approach where a
rough working model is built, refined through
user feedback, and finalized.
9. State limitations of SDLC.
Time-consuming
Expensive
Rigid (not flexible to changes)
Not suitable for evolving requirements
10. Explain waterfall model in detail.
A linear, sequential software development
approach with phases:
1. Requirement Gathering
2. System Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance
Limitations: Rigid, costly to make changes.
11. Explain feedback control mechanism in
detail.
A system that adjusts its operation based on
output feedback to maintain stability.
Examples: Thermostat, Cruise Control.
12. Explain prototype model in detail.
A model where an initial prototype is
developed, user feedback is incorporated,
and refinements are made before finalizing.
13. Short note: Maintenance of system.
Involves:
Corrective Maintenance (bug fixes),
Adaptive Maintenance (environmental
changes),
Preventive Maintenance (future-proofing).
14. Explain fact finding technique in detail.
Interviews
Surveys
Observation
Document Analysis
15. Write short note: Requirement
anticipation.
Predicting future software needs to ensure
scalability and flexibility.
16. Discuss different fact finding techniques.
Same as point 14 but includes:
Prototyping (building rough models)
Joint Application Development (JAD) (team
workshops)
17. Write short note: Structured chart.
A graphical representation of a system’s
modules, showing hierarchy and
relationships.

18. Define stamp cooling

Occurs when modules share complex data
structures instead of simple parameters,
making modifications harder.
19. Define module. Explain types of modules.
A module is an independent unit of a
system. Types include:
Procedural (performs tasks),
Functional (specific functions),
Data Modules (handles data).
20. What is coupling? Explain different types
of coupling.
Coupling refers to the dependency
between modules. Types:
Tight Coupling (high dependency),
Loose Coupling (low dependency, preferred).
21.short note: structured chart
Same as point 17—used in system design.
22. Write short note : white box testing.
A testing method where internal code and
logic are tested using techniques like path
testing and branch testing.

23. Explain testing principles and objectives.

Principles: Testing must be systematic,
exhaustive, and defect-focused.
Objectives: Find defects, ensure
functionality, validate performance.
24. Write short note: black box testing.
A testing method focusing on input-output
functionality without checking internal code.
25. Differentiate between white box and
black box testing.

Paramete Black Box Testing White Box Testing

rs

White Box Testing is a way

Black Box Testing is a way
of testing the software in
of software testing in which
which the tester has
the internal structure or the
knowledge about the
program or the code is
internal structure or the
hidden and nothing is
code or the program of the
known about it.
software.
Definition

Black box testing is mainly

White box testing is
focused on testing the
mainly focused on
functionality of the
Testing ensuring that the internal
software, ensuring that it
objective code of the software is
meets the requirements
correct and efficient.
s and specifications.

Black box testing uses

White box testing uses
methods like equivalence
methods like control flow
partitioning, boundary
testing, data flow
value analysis, and error
Testing testing and statement
guessing to create test
coverage testing.
methods cases.

Knowledg Black box testing does not White box testing requires
e level require any knowledge of knowledge of
Paramete Black Box Testing White Box Testing
rs

the internal workings of the

software, and can be programming languages,
performed by testers who software architecture and
are not familiar with design patterns.
programming languages.