Trial 002

Question 1

Define Problem Statement

Answer 1

A clear, concise description of an issue to be addressed by a software product.

Question 2

Importance of a problem statement

Answer 2

Guides development, ensures focus, and aligns stakeholders.

Question 3

Procedure for Writing a Problem Statement

Answer 3

1. Identify the problem.
2. Explain its impact.
3. Propose a solution.
4. Define success criteria.

Question 4

Define Software

Answer 4

Programs, data, and instructions that enable computers to perform tasks.

Question 5

Importance of Software Engineering

Answer 5

Ensures systematic, efficient, and reliable software development.

Question 6

Attributes of Good Software

Answer 6

Correctness, reliability, usability, efficiency, maintainability, and scalability.

Question 7

Challenges in Software Engineering

Answer 7

• Managing complexity.
  
  • Ensuring quality and reliability.
  • Adapting to changing requirements.
  • Meeting deadlines and budgets.
  • Security and privacy concerns.

Question 8

Software Engineering vs. Computer Science

Answer 8

Software Engineering: Focuses on building software systems using engineering principles.

Question 9

Software Engineering vs. Computer Science

Answer 9

Computer Science: Focuses on theory, algorithms, and computational systems.

Question 10

Professional Ethics in Software Engineering

Answer 10

• Confidentiality.
  
  • Integrity.
  • Accountability.
  • Respect for intellectual property.
  • Avoidance of harm.

Question 11

Roles in Software Engineering

Answer 11

• Software Developer.
  
  • Project Manager.
  • Systems Analyst.
  • Quality Assurance Engineer.
  • UX/UI Designer.

Question 12

Problem Solving Process

Answer 12

Step:
1. Define the problem.
2. Analyze the problem.
3. Generate alternative solutions.
4. Evaluate and select the best solution.
5. Implement and test the solution.

Question 13

Bottom-Up vs. Top-Down:

Answer 13

Bottom-Up: Start with small components and build up.
Top-Down: Start with the big picture and break it down.

Question 14

Define System Requirements

Answer 14

Specifications of what the system should do.

Question 15

Types of Requirements

Answer 15

Functional: What the system should do.
Non-Functional: How the system should perform (e.g., speed, security).

Question 16

Types of Requirements(User Requirements & System Requirements)

Answer 16

User vs. System Requirements:
•User Requirements: High-level needs of users.
• System Requirements: Detailed technical specifications.
•User Involvement: Ensures the software meets user needs and expectations.

Question 17

Fact-Finding Techniques and Tools

Answer 17

Interviews, surveys, observation, document analysis.

Question 18

Fact Recording Tools

Answer 18

Use case diagrams, flowcharts, decision tables.

Question 19

What is Technical Feasibility

Answer 19

Technical Feasibility:
- Can the technology and resources required to build the system be acquired or developed?
- Evaluates hardware, software, and technical expertise.

Question 20

Types of Feasibility

Answer 20

Economic Feasibility:
- Is the project financially viable?
- Assesses costs (development, maintenance) vs. benefits (revenue, savings).

Question 21

What is Legal Feasibility

Answer 21

Legal Feasibility:
- Does the project comply with laws, regulations, and standards?
- Ensures no legal risks or violations.

Question 22

What is Operational Feasibility

Answer 22

Operational Feasibility:
- Can the system be integrated into existing workflows?
- Evaluates user acceptance and organizational impact.

Question 23

Define the term Schedule Feasibility

Answer 23

Schedule Feasibility**:
- Can the project be completed within the given timeframe?
- Assesses deadlines, resource availability, and project scope.

Question 24

Importance of Requirements Validation

Answer 24

Accurate: Correctly reflect stakeholder needs.

Complete: Cover all necessary functionalities.

Achievable: Realistic within technical and resource constraints.

Question 25

Requirements Engineering Process

Answer 25

Elicitation: Gathering requirements from stakeholders. Analysis: Refining and prioritizing requirements. Specification: Documenting requirements clearly. Validation: Verifying requirements for accuracy and completeness.

Question 26

Requirements Elicitation and Analysis

Answer 26

Techniques: Interviews, workshops, brainstorming, prototyping. Goal: Understand stakeholder needs and translate them into actionable requirements. Challenges: Miscommunication, conflicting requirements, changing needs.