Software Engineering Explained by G Krishna

  

Software Engineering Study Material

Sr. No.	Topic	Content
1	Introduction to Software, Software Applications	Software is a collection of programs that perform specific tasks. Software applications are used in business, education, healthcare, banking, and entertainment.
2	Importance and Evolution of Software	Software plays a vital role in automation and problem-solving. It has evolved from simple systems to complex web and cloud-based applications.
3	Software Components and Characteristics	Software includes programs, data, and documentation. Key characteristics are reliability, efficiency, usability, and maintainability.
4	Software Crisis and Myths	Software crisis refers to project failures due to poor planning. Common myths include easy development and effortless maintenance.
5	Software Engineering Paradigms	Paradigms define development approaches such as procedural, object-oriented, and component-based models.
6	Software Engineering Principles and Processes	Principles guide quality development while processes define systematic development activities.
7	Software Quality Attributes	Quality attributes include correctness, reliability, efficiency, integrity, usability, and maintainability.
8	Comparison: Software Engineering vs Computer Science vs Engineering	Software engineering focuses on process and quality, computer science on theory, and engineering on physical systems.
9	Software Terminologies: Product, Process, Deliverables, Milestones	Product is the final software, process is how it is developed, deliverables are outputs, and milestones track progress.
10	Measures, Metrics and Indicators	Metrics are quantitative measures used to evaluate software quality and productivity.
11	Programs and Software Products	Programs are individual instructions, while software products are complete systems.
12	Software Development Life Cycle (SDLC)	SDLC defines structured phases from requirement analysis to maintenance.
13	SDLC Models – Overview	SDLC models provide different approaches based on project needs and risks.
14	Structured Analysis and Object-Oriented Analysis	Structured analysis focuses on functions, while object-oriented analysis focuses on objects and classes.
15	Software Requirement Specification (SRS)	SRS is a formal document describing functional and non-functional requirements.
16	Waterfall and Prototype Models	Waterfall is linear; Prototype model uses early working versions to refine requirements.
17	RAD and Spiral Models	RAD emphasizes rapid development, while Spiral focuses on risk-driven iterations.
18	Evolutionary and Iterative Enhancement Models	These models support incremental development with continuous improvements.
19	Software Design Fundamentals	Design converts requirements into a blueprint for software construction.
20	Design Methodologies: Structured and Object-Oriented Design	Structured design uses functions, object-oriented design uses objects and classes.
21	Design Verification	Verification ensures the design meets specified requirements.
22	Monitoring, Control and Coding	Monitoring tracks progress, control manages deviations, coding implements design.
23	Software Testing Fundamentals	Testing ensures software correctness and reliability.
24	White Box and Black Box Testing	White box tests internal logic; black box tests functionality.
25	Software Testing Strategies	Strategies define systematic approaches for defect detection.
26	Unit and Integration Testing	Unit testing tests modules; integration testing tests module interactions.
27	Validation and System Testing	Validation ensures correct product; system testing evaluates the full system.
28	Debugging, Metrics and Specifications	Debugging removes errors; metrics measure quality; specifications define behavior.
29	Fault Avoidance, Fault Tolerance and Exception Handling	These techniques reduce failures and improve software reliability.
30	Defensive Programming	Defensive programming anticipates errors and prevents unexpected failures.
31	Software Maintenance	Maintenance modifies software after delivery to fix or enhance it.
32	Maintenance Characteristics and Maintainability	Maintainability indicates how easily software can be modified.
33	Maintenance Tasks and Side Effects	Maintenance tasks may introduce side effects if not properly managed.
34	CASE Tools – Introduction and Importance	CASE tools automate development activities and improve productivity.
35	CASE Architecture, Building Blocks and Repository	CASE architecture defines tool structure; repositories store project data.
36	Characteristics and Categories of CASE Tools	CASE tools are categorized as upper, lower, and integrated CASE.
37	Software Certification: Requirements, Types and Third-Party Certification	Certification ensures compliance with quality and industry standards.
38	Software Re-Engineering and Reverse Engineering	Re-engineering improves software; reverse engineering extracts design.
39	Software Configuration Management and Version Control	SCM controls changes; version control tracks revisions.
40	Change Control Process	Change control evaluates and approves software modifications.
41	Software Project Estimation: Cost, Effort and Schedule	Estimation predicts project resources, time, and cost.
42	COCOMO, Resource Allocation, Software Risk Analysis and Management	COCOMO estimates cost, resources are optimized, and risks are identified and managed.