SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
Here’s the process in a clean, real-world order:
1. Initial Request / Problem Identification
Someone identifies a need:
•“We need an online booking system”
•“Our current system is too slow”
This step is about defining the problem or opportunity, not jumping to solutions yet.
2. Feasibility Study
Before building anything, you check if it’s worth doing:
• Technical feasibility – Can we build it with current tech? • Financial feasibility – Is it worth the cost?
• Operational feasibility – Will people actually use it? If it fails here, the project stops early (which is a good thing).
3. Requirements Gathering & Analysis
This is one of the most important steps—and where many projects go wrong.
You collect:
• Functional requirements (what the system should do)
• Non-functional requirements (performance, security, usability) Methods include:
• Interviews
• Surveys
• Observing users
4. System Design
Now you plan how it will work:
• Architecture (frontend, backend, database)
• UI/UX design
• Data models
• Workflows
Think of this as the blueprint before construction.
5. Development (Coding)
The system is actually built:
• Frontend (what users see)
• Backend (logic, servers)
• Database setup
6. Testing
You don’t just hope it works—you prove it does.
Types include:
• Unit testing (individual parts)
• Integration testing (components working together)
• User Acceptance Testing (UAT)
Bugs are found and fixed here.
7. Deployment (Implementation)
The system goes live:
• Hosted on servers or cloud platforms
• TRAIN USERS OF THE SYSTEM
• Users start using it
This can be:
• Gradual rollout
• Full launch
8. Maintenance & Support
This never really ends:
• Fix bugs
• Improve features
• Update for security
Most systems spend years in this phase.
9. Evaluation / Feedback
After release:
• Did it solve the original problem?
• What needs improvement?
This often feeds into the next version—making the process cyclical.
Reality Check
In theory, this looks linear. In practice:
• Teams go back and forth between steps
• Requirements change mid-project
•Agile methods blur the lines between design, development, and testing
Send complaints to:
RSO Team: [email protected]
Mayor/District 1: Jacque Casillas
[email protected]
District 2: Tony Daddario
[email protected]
District 3: Tom Richins
[email protected]
District 4: Jim Steiner
[email protected]
Vice-Mayor/District 5: Wes Speake
[email protected]
“Don’t pee on my leg
And tell me it’s
raining.”
- Judge Judy Sheindlin