Loading, please wait ...
Categories of Principles By Mukhtiar Zamin


Teachers with
Mukhtiar Zamin
For Learning
Security Status
By Teachers
  1. Students are auto-evaluated against related topics to ensure they learned it.

Software engineering principles can be categorized into various levels of complexity based on their scope and impact. Here are five categories, ranging from simple to complex: 

  1. Basic Principles: DRY (Don't Repeat Yourself): Avoid duplication of code or functionality. KISS (Keep It Simple, Stupid): Strive for simplicity and avoid unnecessary complexity. YAGNI (You Ain't Gonna Need It): Only implement what is currently necessary and avoid speculative additions. 
  2. SOLID Principles: Single Responsibility Principle (SRP): A class should have only one reason to change. Open/Closed Principle (OCP): Software entities (classes, modules, functions) should be open for extension but closed for modification. Liskov Substitution Principle (LSP): Subtypes must be substitutable for their base types without affecting the correctness of the program. Interface Segregation Principle (ISP): Clients should not be forced to depend on interfaces they do not use. Dependency Inversion Principle (DIP): High-level modules should not depend on low-level modules; both should depend on abstractions. 
  3. Design Patterns: Creational Patterns: Provide object creation mechanisms that encapsulate the process. Structural Patterns: Deal with object composition, relationships, and class hierarchies. Behavioral Patterns: Address communication between objects and the assignment of responsibilities. 
  4. Architectural Patterns: Layered Architecture: Separates a system into logical layers with defined responsibilities. Model-View-Controller (MVC): Separates the application into three interconnected components to handle user interface, data, and control flow. Microservices Architecture: Decomposes an application into loosely coupled, independently deployable services. Domain-Driven Design (DDD): Focuses on modeling complex business domains and aligning software design with the domain. 
  5. Agile Methodologies: Scrum: An iterative and incremental framework for managing and delivering complex products. Extreme Programming (XP): Emphasizes close collaboration, continuous testing, and rapid feedback loops. Kanban: Visualizes work on a Kanban board and optimizes flow, limiting work in progress. Lean Software Development: Aims to reduce waste and improve efficiency by eliminating non-value-adding activities. These categories represent a progression from fundamental programming principles to higher-level concepts for software design, architecture, and project management. It's important to note that these categories are not strictly linear, and principles from different categories can be applied simultaneously or in a non-sequential manner depending on the project requirements and context.

More Categories for All, By Mukhtiar Zamin

Software engineering principles can vary in complexity depending on the specific context and application. However, I can provide you with a general progression of software engineering principles from simpler concepts to more complex ones. Keep in mind that these categories are not strictly hierarchical, and some principles may overlap or interact with others. Here's a broad outline:

  1. Modularity: Breaking down a software system into smaller, manageable components or modules, which can be developed, tested, and maintained independently. 
  2. Abstraction: Hiding unnecessary implementation details and focusing on essential features, providing a simplified view of complex systems. 
  3. Encapsulation: Bundling data and related operations (methods or functions) into a single unit, called an object or class, to enforce data integrity and maintainability. 
  4. Separation of Concerns: Dividing a system into distinct sections, each addressing a specific aspect or concern, such as user interface, business logic, and data storage, to enhance maintainability and readability. 
  5. Information Hiding: Restricting access to internal details of an object or module, exposing only necessary interfaces or public APIs, which helps to minimize dependencies and improve system stability. 
  6. Single Responsibility Principle (SRP): Assigning a single, well-defined responsibility or purpose to each module or class, reducing complexity and promoting maintainability. 
  7. Open-Closed Principle (OCP): Designing software entities (classes, modules, etc.) that are open for extension but closed for modification, allowing new functionality to be added without changing existing code. 
  8. Liskov Substitution Principle (LSP): Ensuring that objects of a superclass can be replaced by objects of their subclasses without affecting the correctness of the program, maintaining the behavior and contract of the superclass. 
  9. Interface Segregation Principle (ISP): Clients should not be forced to depend on interfaces they do not use. Breaking large interfaces into smaller, more specific ones, to minimize coupling and improve code maintainability. 
  10. Dependency Inversion Principle (DIP): High-level modules or classes should not depend on low-level modules or classes directly. Both should depend on abstractions, promoting loose coupling and flexibility. 
  11. Design Patterns: Reusable solutions to common software design problems, providing proven approaches to design complex systems effectively and efficiently. 
  12. Domain-Driven Design (DDD): Focusing on the core domain and modeling it explicitly in software, aligning the implementation with business requirements and concepts. 
  13. Test-Driven Development (TDD): Writing tests before writing the actual code, driving the design and development process and ensuring better code quality and maintainability. 
  14. Continuous Integration and Deployment (CI/CD): Automating the process of integrating, testing, and deploying software changes, enabling faster and more frequent delivery with higher reliability. 
  15. Agile Software Development: Emphasizing iterative development, collaboration, and adaptability, enabling teams to respond to changes quickly and deliver value in shorter cycles. 
  16.  These are just some of the key principles in software engineering, and there are many more specific practices and methodologies that can be explored within each category.


Categories of Principles Evaluation

To earn PASS status, system is about to evaluate you using multiple choice questions (MCQs) and True/False type questions.

  • Make sure you have learned this lecture along with its topics and tutorials.
  • On first evaluation you get 100% marks on correct answer, then on 2nd you get 95% marks and so on.
  • Answer the questions with a gap NOT MORE THAN A MINUTE, Otherwise it will re-start.

I have read above instrucitons and ready for evaluation.
Not Registered
Mukhtiar Zamin
Please ask your teacher to link related questions for this lecture.
Your performance monitoring will start when you register in a class of this course.

Questions on

No Linked topics!
Contact Us

Write to Us View Help
Subject Expert Logo

Subject Expert

Learn, Evaluate and Optimize

Follow Us
Facebook Switch Display Mode Enable Translation
© 2024 - Subject Expert