Maintenance Methods and Levels: A Practical Cheat Sheet
Part 1: Maintenance Method Cheat Sheet
When analyzing a scenario, ask yourself: Why are we performing maintenance on this machine?
1. Preventive Maintenance (Before Failure)
- Systematic (Periodic): Triggered by a strict interval (time, distance, operating hours, or cycles). The part is replaced regardless of its current condition.
- Keywords: “Every X km,” “weekly,” “monthly,” “at 100,000 km,” “start of winter.”
- Condition-based: Triggered by physical warning signs, sensors, or thresholds. Action is taken
AIOps and CI/CD: Mastering IT Operations and Automation
AIOps vs. DevOps: Key Differences
| Point | AIOps | DevOps |
|---|---|---|
| 1. Meaning | Uses AI and Machine Learning for IT operations | Combines development and operations |
| 2. Main Focus | Smart monitoring and automatic issue handling | Fast software development and deployment |
| 3. Technology Used | AI, ML, data analytics | CI/CD, automation tools |
| 4. Problem Handling | Predicts problems before they happen | Fixes problems after they occur |
| 5. Human Effort | Less manual work | More manual involvement |
| 6. Data Usage | Uses real-time and past data | Uses logs and scripts |
| 7. |
Modern Software Development and Database Fundamentals
Relational Database Design and Normalization
The relational model stores data in tables (relations), where rows represent tuples and columns represent attributes.
- Key components: Tables, attributes, tuples, and constraints (PK, FK, UNIQUE, NOT NULL).
- Mapping ER to Relational: Entity becomes a table, 1:many uses a foreign key (FK) on the many side, many:many requires a junction table, and multivalued attributes move to separate tables.
Functional Dependency (FD): X → Y means X uniquely determines Y.
Read MoreSoftware Requirements Engineering Principles and Practices
Software Requirements and Their Types
Software requirements are statements that describe what a system should do and how it should behave. They act as a foundation for designing, developing, and testing software.
Functional Requirements (FR)
Functional requirements define what the system must do by describing specific functions or tasks.
- Examples:
- “The system shall allow users to log in using a username and password.”
- “The system shall generate monthly sales reports.”
Non-Functional Requirements
Read MoreSoftware Engineer Responsibilities, Processes & Quality
Role of a Software Engineer
A software engineer is a professional who applies engineering principles, systematic methods, and tools to design, develop, test, deploy, and maintain software systems efficiently and reliably. The role covers the entire software development life cycle and focuses on producing high-quality software that satisfies user and business requirements. A software engineer is not only a programmer but also a planner, designer, tester, and maintainer of software systems.
Requirement
Read MoreSoftware Design Principles and Coding Best Practices
Software Design and Coding Best Practices for Developers
1. Basic Principles of Software Design
Basic principles of software design help create software that is simple, maintainable, and easy to understand. The major principles are:
- Abstraction – Show only important details and hide unnecessary information. It helps reduce complexity.
- Modularity – Break the system into small modules so each module handles one purpose.
- Information Hiding – Keep internal details of a module hidden to protect data