SAD – Implementation & Maintenance
Quick Revision Notes · HSDDTTD · DPPP · CAPA · 50 Interactive MCQs
1. System Implementation
Implementation is the process of converting the designed system into a working information system.
Main Activities (HSDDTTD)
- H – Hardware Installation
- S – Software Installation
- D – Database Creation
- D – Data Conversion
- T – Testing
- T – Training
- D – Deployment
Objectives of Implementation
- ✔ Deliver a working system
- ✔ Reduce implementation risk
- ✔ Increase user satisfaction
- ✔ Ensure smooth transition
- ✔ Improve organizational efficiency
Components of Implementation
Hardware
- Server
- Computer
- Printer
- Scanner
- Router
- Switch
- UPS
Software
- Operating System
- DBMS
- Application Software
- Antivirus
- Drivers
Database
- Create Tables
- Relationships
- Constraints
- Import Data
Data Conversion
Transfer old system data into the new system.
📝 Example: Excel → MySQL
Types of Data Conversion
Manual
- Human enters data
- Slow
- More accurate checking
Automatic
- Software imports data
- Fast
- Less effort
- Less human error
System Testing
Purpose: Detect bugs · Verify correctness · Validate user requirements
| Testing Type | Description | Example |
|---|---|---|
| Unit Testing | Tests one module | Login Module |
| Integration Testing | Tests communication between modules | Login + Dashboard |
| System Testing | Tests complete software | Full Application |
| User Acceptance Testing (UAT) | Performed by client/users. Checks business requirements. | End-user validation |
Documentation
User Documentation
- User Manual
- Installation Guide
- FAQs
- Troubleshooting
Technical Documentation
- ER Diagram
- Source Code
- APIs
- Database Schema
- Flowcharts
User Training
Methods: Classroom · Online · Demo · Video · Manuals
Deployment
📌 Definition: Deployment means making the software live.
Implementation Strategies (DPPP)
1. Direct Changeover
Old System → New System
✔ Advantages: Cheapest, Fastest
✘ Disadvantages: Highest Risk, No Backup
2. Parallel Changeover
Old System + New System (Run Together)
✔ Advantages: Safest, Easy Comparison
✘ Disadvantages: Expensive, Double Work
3. Pilot Changeover
Implement in only one department
✔ Advantages: Low Risk, Real Testing
✘ Disadvantages: Slow
4. Phased Changeover
Module-wise Implementation (Login → Student → Fee → Reports)
✔ Advantages: Easy, Controlled
✘ Disadvantages: Time-consuming
🧠 Memory Trick: DPPP — Direct · Parallel · Pilot · Phased
| Strategy | Cost | Risk | Speed |
|---|---|---|---|
| Direct | Low | High | Fast |
| Parallel | High | Low | Slow |
| Pilot | Medium | Low | Medium |
| Phased | Medium | Medium | Medium |
System Maintenance
Definition: Maintenance means modifying software after deployment to improve performance or fix problems.
Objectives
- Remove bugs
- Improve speed
- Add features
- Adapt to new environment
- Increase security
Types of Maintenance (CAPA)
1. Corrective Maintenance
Fixes software errors.
Example: Login Bug, Calculation Error
2. Adaptive Maintenance
Adapts software to new environment.
Example: Windows Upgrade, GST Rule Change, Browser Update
3. Perfective Maintenance
Improves performance and functionality.
Example: Better UI, New Report, Search Feature
4. Preventive Maintenance
Prevents future problems.
Example: Backup, Security Patch, Code Refactoring, Optimization
🧠 Memory Trick: CAPA — Corrective · Adaptive · Perfective · Adaptive
Maintenance Process
- Problem
- Analysis
- Design
- Coding
- Testing
- Deployment
- Documentation
Maintenance Activities
- ✔ Bug Fixing
- ✔ Backup
- ✔ Database Optimization
- ✔ Security Updates
- ✔ User Support
- ✔ Performance Improvement
- ✔ Feature Enhancement
Challenges
- High Cost
- Legacy Systems
- Poor Documentation
- Security Threats
- Skilled Staff Requirement
Implementation vs Maintenance
| Implementation | Maintenance |
|---|---|
| Before Go-Live | After Go-Live |
| One-Time | Continuous |
| Install System | Improve System |
| Setup Software | Bug Fix & Upgrade |
Role of System Analyst
- Requirement Verification
- Planning
- Testing
- Documentation
- User Training
- Monitoring
- Maintenance Coordination
One-Line Revision (Exam Facts)
- 📌 Implementation comes before Maintenance.
- 📌 UAT is performed by End Users.
- 📌 Parallel strategy is Safest.
- 📌 Direct strategy is Fastest but Riskiest.
- 📌 Pilot strategy is used for one department.
- 📌 Phased strategy implements one module at a time.
- 📌 Corrective Maintenance = Fix Errors.
- 📌 Adaptive Maintenance = Environment Change.
- 📌 Perfective Maintenance = Performance Improvement.
- 📌 Preventive Maintenance = Avoid Future Problems.
- 📌 Documentation is of User and Technical types.
- 📌 Deployment means Making software live.
Ultra-Fast Last-Minute Revision
- ⚡ Implementation = Install + Test + Train + Deploy
- ⚡ Maintenance = Fix + Improve + Adapt + Prevent
- ⚡ DPPP = Direct, Parallel, Pilot, Phased
- ⚡ CAPA = Corrective, Adaptive, Perfective, Preventive
- ⚡ UAT = User Acceptance Testing (by End User)
- ⚡ Direct = Fastest, Highest Risk
- ⚡ Parallel = Safest, Costliest
- ⚡ Pilot = One Department First
- ⚡ Phased = Module by Module
- ⚡ Implementation → Maintenance (SDLC Order)
Conclusion
Implementation and Maintenance are two critical phases of the Software Development Life Cycle. Implementation converts design into a working system, while maintenance ensures the system remains operational and effective over time.
Master these concepts with the interactive MCQs below to ace your competitive exams!
परिणाम
बहुत अच्छा!
ऊपर 'पुनः प्रयास' बटन से दोबारा प्रयास करें