Chapter 1 - Class 11 Computer
Chapter 1 SDLC notes ko PDF-style layout me rakha gaya hai taake user ko quick access, printable format aur low-friction revision mile. Neeche full notes, solved exercises aur important questions aik hi page par available hain.
Printable Notes
Yeh page Software Development Life Cycle chapter ko document format me organize karta hai. Is me notes, solved exercises aur important questions aik printable flow me diye gaye hain taake student bina extra clicks ke revise kar sake.
Chapter 1 ka focus Software Development Life Cycle par hai. Is chapter me software banane ke main stages, requirement types, planning mindset aur common development models ko samjhaya jata hai.
Neeche diye gaye notes exam preparation ke liye concise hain, lekin itne complete hain ke student chapter ka overall structure samajh sake aur short ya long answer me points build kar sake.
Software Development Life Cycle aik structured process hai jo software project ko planning se deployment tak step-by-step chalata hai. Is se team ko clear direction milti hai aur project random coding ke bajaye organized tareeqe se complete hota hai.
Is ka sab se bara faida control hai. Jab requirements clear hoti hain, design pehle socha jata hai aur testing later ignore nahi hoti, to bugs, delays aur unnecessary cost dono kam ho jate hain.
Functional requirements yeh batati hain ke system kya kaam karega, jaise login ya search. Non-functional requirements system ki quality define karti hain, jaise speed, reliability, security aur performance.
Linear model hai jahan har stage fixed order me chalti hai. Stable requirements wale projects me easy hota hai lekin late changes handle karna mushkil hota hai.
Project ko small cycles ya sprints me divide karta hai. Feedback jaldi milta hai aur improvement continuously hoti rehti hai, is liye changing requirements ke liye useful hota hai.
Solved exercises ka purpose direct exam wording ko manageable answers me convert karna hai. In examples ko yaad karne ke bajaye inka answer structure samajhna zyada important hai.
SDLC ka main purpose kya hai?
Correct answer: Software banane ko step-by-step plan karna
Correct answer 'Software banane ko step-by-step plan karna' hai kyun ke SDLC ka kaam project ko ordered stages me divide karna hota hai. 'Random coding' galat hai kyun ke SDLC planning ke baghair kaam nahi karta.
Functional requirement kya batati hai?
Correct answer: System kya kaam karega
Correct answer 'System kya kaam karega' hai kyun ke functional requirement feature ya action batati hai, jaise login ya search. Color theme aur speed functional nahi, balke doosri categories me aati hain.
Non-functional requirement kis cheez se related hoti hai?
Correct answer: System kitna fast aur reliable hai
Correct answer 'System kitna fast aur reliable hai' hai kyun ke non-functional requirement quality, speed, security aur performance ko cover karti hai. Ye feature ka naam nahi, balke system ki quality batati hai.
Waterfall model kaisa hota hai?
Correct answer: Step-by-step linear process hota hai
Correct answer 'Step-by-step linear process hota hai' hai kyun ke Waterfall me phases aik fixed order me chalti hain. 'Small cycles' Agile ki taraf jata hai, is liye woh option galat hai.
SDLC ke core stages aik sequence me software ko stable banati hain. Planning project ka direction set karti hai, design structure banati hai, development code likhti hai, testing bugs pakarti hai aur deployment final software ko users tak pohanchati hai.
Use Case Diagram ka purpose yeh dikhana hota hai ke kaun sa user system ke sath kya action karta hai. Is se project ke functions ko simple visual form me samajhna easy hota hai aur requirements clear hoti hain.
Yeh section board-style short questions ke liye useful hai. In ko revise karke student concept wording ko fast recall me convert kar sakta hai.
SDLC important hai kyun ke yeh software development ko organized banata hai. Jab planning, design, development aur testing alag clear stages me hoti hain to bugs kam hotay hain, time waste nahi hota aur cost control me rehti hai.
Functional requirements batati hain system kya karega, jaise user login kar sake. Non-functional requirements batati hain system kaise perform karega, jaise fast ho, secure ho aur reliable ho. Is liye aik feature batati hai aur doosri quality batati hai.
Waterfall linear order follow karta hai, yani aik stage ke baad doosri stage aati hai. Agile me project small cycles ya sprints me chalta hai jahan feedback ke baad improvement hoti rehti hai.