Introduction to Software DevelopmentIntroduction to Software Development
Software development as a systematic SDLC process, methodologies (Waterfall, Agile, Scrum, Lean, DevOps), project planning and costing, UML representation, design patterns, debugging/testing and development tools.
1.6.1.3 Observer Pattern · Reviewed lesson · version 1 · published 16 Nov 2026
Observer Design Pattern logon ke aise group jaisa hai jo ek hi source (zariya) se updates lene mein dilchaspi rakhte hain. Jab bhi koi aham baat hoti hai, source khud ba khud tamam dilchaspi rakhne walon ko bata deta hai. Yeh sab ko ek jaisi maloomat par (in sync) rakhne ka tareeqa hai, baghair is ke ke har koi baar baar updates check kare.
Mukhtasar khulasa
Observer: kuch hone par source tamam dilchaspi rakhne walon ko khud batata hai; baar baar check nahi karna parta.
1.3.1.4 DevOps · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 87 KB
DevOps practices (kaam ke tareeqon) ka ek set hai jo software development (Dev) aur IT operations (Ops) ko jorta hai, ta ke software products aur services dene mein mil jul kar kaam (collaboration), efficiency aur agility (tezi aur lachak) barhe, jaisa Figure 1.6 mein dikhaya gaya hai. DevOps ka sab se bara maqsad development lifecycle ko chhota karna, software ki quality behtar karna aur high reliability (poore bharose) ke saath continuous delivery (lagatar naye versions users tak pohanchana) dena hai.
DevOps kyun apnana chahiye: DevOps is liye apnana chahiye ke yeh software banane aur users tak pohanchane ke process mein bohat se faide deta hai:
Behtar collaboration: DevOps development aur operations teams mein mil kar kaam karne ka mahol banata hai, un ke darmiyan ki deewarein (silos, alag alag khane) torta hai aur dono teams ko ek hi maqsad par lata hai.
Market tak jaldi (Faster Time-to-Market): processes ko automate (machine se khud ba khud karwana) kar ke aur continuous integration aur continuous delivery (CI/CD) se teams software updates aur naye features zyada tezi se de sakti hain.
Behtar quality: DevOps mein lagatar testing aur monitoring (nazar rakhna) development cycle ke shuru mein hi masle pakar kar theek karti hai, is liye software ki quality zyada hoti hai.
Zyada efficiency: baar baar hone wale kaam automate karne se haath ki mehnat aur insani ghalti ka khatra kam hota hai, aur kaam ka bahao (workflow) zyada efficient hota hai.
1.3.1.2 Agile Methodology (Roman Urdu)
1.3.1.2 Agile Methodology · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 79 KB
Agile Methodology software banane ka flexible (lachak wala) aur adaptive (halaat ke mutabiq badal jane wala) tareeqa hai. Waterfall Model steps ke sakht order par chalta hai, lekin Agile software ke chhote, kaam karte hisse jaldi dene aur project ke dauran aane wali tabdeeliyon ke mutabiq dhalne par zor deta hai. Asal khayal yeh hai ke kaam short cycles (chhote chakkar) mein ho jinhein iterations ya sprints kehte hain. In se teams software ke hisse jaldi deti hain aur shuru mein hi feedback (raaye) le leti hain, jaisa Figure 1.3 mein dikhaya gaya hai. Agile ke tareeqon mein yeh practices shamil hain:
Continuous Integration: code ki tabdeeliyan regular taur par ek central repository (woh main jagah jahan sab ka code rakha jata hai) mein milana, ta ke masle jaldi pakre aur theek kiye ja sakein.
Test-Driven Development: code likhne se pehle tests likhna, ta ke software waisa hi kaam kare jaisa chahiye.
Pair Programming: do developers ek hi workstation (computer) par mil kar kaam karte hain; ek code likhta hai aur doosra usi waqt (real-time) us ko check karta hai.
Figure 1.3: Agile Methodology (kitab ki Figure 1.3 ke mutabiq apni banayi hui drawing).
1.2.2 Stages involved in SDLC (Roman Urdu)
1.2.2 Stages involved in SDLC · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 66 KB
SDLC software banane ka ek organized (tarteeb wala) tareeqa hai jo yeh yaqeeni banata hai ke software quality standards poore kare aur theek kaam kare. Software developers aur engineers is ko software ke design, development aur testing mein guide (rehnumai) ke liye istemal karte hain. SDLC kai steps (qadmon) se mil kar bana hai jo Figure 1.1 mein dikhaye gaye hain. Har step ke apne alag kaam aur maqsad hain.
Figure 1.1: System development life cycle ki stages (kitab ki Figure 1.1 ke mutabiq apni banayi hui drawing).
1.6.2 Applications of Design Patterns in Software Design (Roman Urdu)
1.6.2 Applications of Design Patterns in Software Design · Reviewed lesson · version 1 · published 16 Nov 2026
Design patterns software development mein aam masle hal karne aur mazboot (robust) aur aasani se sambhalne wala (maintainable) code banane ke liye bohat istemal hote hain. Yeh in cheezon mein madad karte hain:
Saaf banawat (clear structure) de kar code ki complexity (pecheedgi, mushkil-pan) kam karna.
Aazmaye hue hal istemal kar ke code ka dobara istemal (reusability) barhana.
Developers ko ek jaise alfaaz (common vocabulary) de kar un ki aapas ki baat cheet behtar karna.
Design patterns aise systems banane mein madad karte hain jo flexible (lachak wale), aasani se sambhalne wale (maintainable) aur samajhne mein aasan hon.
1.5.2 Types of UML Diagrams · Reviewed lesson · version 1 · published 16 Nov 2026
Is hisse mein hum UML diagrams ki chaar qismein parhenge jo neeche di gayi hain.
Is chapter ke chaar UML diagrams
Diagram
Kya dikhata hai
Use case diagram
actors (users) aur woh kaam (use cases) jo woh system se karwate hain
Class diagram
classes, un ke attributes aur methods, aur aapas ke rishte
Sequence diagram
objects ke darmiyan messages, waqt ke order mein
Activity diagram
kisi process mein steps aur faislon (decisions) ka bahao
1.5.3 Using UML to Represent Software Systems (Roman Urdu)
1.5.3 Using UML to Represent Software Systems · Reviewed lesson · version 1 · published 16 Nov 2026
UML software development ki mukhtalif stages mein samajh aur baat cheet (communication) behtar karne ke liye istemal ho sakti hai. Is ke kuch practical (amli) istemal yeh hain:
Planning: code likhne se pehle UML diagrams se system ki requirements aur design ka naqsha banana.
Development: developers system ki banawat (structure) aur us ke hisson ke rishte samajhne ke liye UML diagrams dekhte hain.
Communication: UML diagrams team ke logon ko, un ko bhi jo technical nahi (non-technical stakeholders), samjhate hain ke system kaise kaam karta hai.
Mukhtasar khulasa
UML ke istemal: planning (code se pehle requirements aur design), development (banawat aur rishte), communication (non-technical log bhi samjhein).
1.5.2.2 What is a Class Diagram? · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.1 MB
Class diagram ek naqshe (map) jaisa hai jo dikhata hai ke system mein cheezein kaise organized (tarteeb se rakhi) hain, bilkul waise jaise aap apna kamra tarteeb se rakhte hain. Is se hum dekh sakte hain ke har dabbe (box) mein kya hai (jaise khilone, kitabein ya kapre) aur yeh dabbe aapas mein kaise jure hain.
Misal:
Apna kamra tarteeb se rakhne ki misal mein:
Room (kamra): poori jagah jis mein baqi sab cheezein hain; class diagram ki main banawat (structure) jaisa.
Box (dabba): kamre ke andar ek container; diagram mein class jaisa.
Attributes: har dabbe mein khaas cheezein hoti hain, jaise 'ToyBox' mein khilone ya 'BookBox' mein kitabein.
Methods: dabbe kuch kaam kar sakte hain, jaise 'open' (kholna) ya 'close' (band karna); class diagram ke methods bhi batate hain ke class kya kaam kar sakti hai.
Khaas dabbe (Specific Boxes): khilono ke liye 'ToyBox', kitabon ke liye 'BookBox' aur kapron ke liye 'ClothesBox'; yeh aam 'Box' class ki alag alag khaas qismein hain.
To class diagram bas ek tareeqa hai yeh dikhane ka ke system (jaise aap ka kamra) ke mukhtalif hisse kaise mil kar kaam karte hain, ta ke sab kuch ek nazar mein samajh aa jaye, jaisa Figure 1.10 mein dikhaya gaya hai.
1.2.2.3 Development (Roman Urdu)
1.2.2.3 Development · Reviewed lesson · version 1 · published 16 Nov 2026
Development phase mein software asal mein banna shuru hota hai. Yahan programmers code likhte hain. Code instructions (hidayaat) ka woh set hai jis par chal kar computer khaas kaam karta hai. Design specifications (detail mein likhi baatein) batati hain ke software ko kya karna hai aur kaisa dikhna hai; programmers in specifications ko kisi programming language mein likh dete hain.
Ise recipe par chalne jaisa samjhein: design specifications recipe hain, aur coding cake banane ke liye cheezein milana aur bake karna hai. Code ki har line recipe ke ek step jaisi hai, jo yaqeeni banati hai ke software theek (correctly) kaam kare aur design ki requirements poori kare. Is phase mein programmers apna code test bhi karte hain ta ke errors ya bugs (ghaltiyan) dhoond kar theek karein. Is testing se software waisa hi chalta hai jaisa umeed thi aur ghaltiyon se paak hota hai. Agar koi masla mile to programmers code badalte hain, masla theek karte hain aur dobara test karte hain, jab tak software agli stage ke liye tayyar na ho jaye.
Mukhtasar khulasa
Development: programmers design specifications ko programming language ke code mein likhte hain (recipe se cake).
Is ke saath apna code test karte, bugs theek karte aur dobara test karte hain.
1.3 Software Development Methodologies (Roman Urdu)
1.3 Software Development Methodologies · Reviewed lesson · version 1 · published 16 Nov 2026
Software development methodologies software banane ke structured (tay shuda, tarteeb wale) tareeqe hain jo software projects ki planning, banane (creation) aur management mein guide (rehnumai) karte hain. Yeh yaqeeni banate hain ke development ka process tarteeb wala (systematic) aur efficient ho, aur us se high-quality software bane.
Mukhtasar khulasa
Methodologies: software projects ki planning, creation aur management ke structured tareeqe.
Is chapter mein: Waterfall, Agile, Scrum, Lean, DevOps.
1.2.2.5 Deployment · Reviewed lesson · version 1 · published 16 Nov 2026
Jab software achi tarah test ho jaye aur masle theek ho jayein to woh deployment phase mein jata hai. Deployment ka matlab hai software ko users ke liye available (istemal ke liye tayyar) karna ta ke woh use istemal kar sakein. Is mein aksar kai steps hote hain:
Installation: software user ke system ya server par install kiya jata hai. Is mein aksar ek installation program chalaya jata hai jo files copy karta hai aur zaroori settings (configurations) set karta hai.
Configuration: software ko user ya organization ki khaas zarooraton ke mutabiq set kiya jata hai, jaise user ki pasand (preferences), network settings aur database connections.
Testing in the Real World: install hone ke baad software ko us ke real-world environment (asal jagah jahan woh chalega) mein test kiya jata hai ta ke woh doosre systems ke saath theek chale aur users ki zarooratein poori kare.
Mukhtasar khulasa
1.8.6 Integrated Development Environments (IDEs) (Roman Urdu)
1.8.6 Integrated Development Environments (IDEs) · Reviewed lesson · version 1 · published 16 Nov 2026
IDEs (Integrated Development Environments) mukammal software suites hain jo software development ke liye tamam zaroori tools ek hi jagah dete hain. IDE mukhtalif development tools, jaise editors, compilers, debuggers aur version control systems, ko jor deta hai ta ke development ka process aasan aur tez ho. IDE ek hi interface deta hai jahan developers apna code efficiently likh, test aur debug kar sakte hain.
Aam IDEs (Common IDEs)
Eclipse: Java development ke liye bohat istemal hota hai.
Visual Studio: .NET aur C++ development ke liye mashhoor.
PyCharm: Python development ke liye pasand kiya jata hai.
Mukhtasar khulasa
IDE: tamam development tools ek jagah (editor, compiler, debugger, version control); Eclipse, Visual Studio, PyCharm.
1.7.2.3 System Testing · Reviewed lesson · version 1 · published 16 Nov 2026
System Testing testing ka ooncha level hai jis mein poore software system ko ek saath (as a whole) test kiya jata hai. Is stage par software ko ek mukammal cheez samjha jata hai, aur testers us ki overall (poori) functionality, performance, security aur di gayi requirements ke mutabiq hona (compliance) jaanchte hain. System testing aise mahol mein ki jati hai jo production environment (asal istemal wala mahol) se bohat milta julta ho, ta ke yaqeen ho ke software asal halaat mein theek chalta hai. Is level par woh defects (khamiyan) pakri jati hain jo system ke mukhtalif hisson ke aapas mein milne se paida hoti hain, aur confirm hota hai ke software apna maqsad poora karta hai.
Mukhtasar khulasa
System testing: poora system ek saath; functionality, performance, security, compliance; production jaise mahol mein.
1.4.3 Estimating Costs · Reviewed lesson · version 1 · published 16 Nov 2026
Software project ke kharche (cost) ka andaza lagana project planning aur management ka bohat aham qadam hai. Is mein project ko kamyabi se mukammal karne ke kul kharchon ka prediction (pehle se andaza) kiya jata hai. Sahi andaze se budget banane, resources (wasail) baantne aur realistic expectations (haqeeqat ke qareeb umeedein) rakhne mein madad milti hai. Yahan hum kharche ke andaze ke aham factors dekhenge aur ek misal se process samjhenge.
Kharche ke andaze ke aham factors (Key Factors in Cost Estimation)
Development Team: kharcha developers ki tadaad, un ki expertise (maharat) aur hourly rate (ek ghante ki fees) par depend karta hai. Khaas skills wali teams zyada rate le sakti hain.
Technology Stack: chuni gayi technology, programming languages aur tools kharche par asar dalte hain. Kuch technologies ko zyada resources ya khaas ilm chahiye hota hai.
Project Duration (kitna waqt lagega): lambe projects aam taur par mehnge hote hain, kyun ke resources zyada der lage rehte hain aur scope (daira) badalne ka chance hota hai.
Risk Management: potential risks (ho sakne wale khatre) pehchanna aur un ko kam karne ke plans banana kul kharcha barha sakta hai. Achanak masloon ke liye aksar contingency fund (achanak kharchon ke liye alag rakhi raqam) rakha jata hai.
Quality Assurance: testing, bugs theek karne aur software ko quality standards par lane ke kharche bhi andaze mein shamil hote hain.
Misal: farz karein Pakistan ki ek company online shopping ke liye mobile application banana chahti hai.
1.7 Software Debugging and Testing (Roman Urdu)
1.7 Software Debugging and Testing · Reviewed lesson · version 1 · published 16 Nov 2026
Software debugging aur testing software development ke bohat aham stages (hisse) hain jo software product ki quality aur reliability (bharosa) yaqeeni banate hain. Achi debugging aur testing se developers confirm (pakka) kar sakte hain ke software zaroori specifications poori karta hai, waisa kaam karta hai jaisa chahiye aur us mein koi critical (bari, khatarnak) ghalti nahi.
1.7.1 Debugging · Reviewed lesson · version 1 · published 16 Nov 2026
Debugging software mein bugs ya errors (ghaltiyan) dhoondne aur theek karne ka process hai. Software debugging aur testing software development ke zaroori hisse hain. Yeh yaqeeni banate hain ke software theek kaam kare aur user ki requirements poori kare.
Bugs software ki woh ghaltiyan hain jin ki wajah se software unexpected (achanak, jaisa nahi chahiye) tareeqe se chalta hai. Bug pehchanne ke liye software ka behavior (woh kaise chal raha hai) dekha jata hai aur masle ki jarr (source) dhoondi jati hai. Pehchanne ke baad bug hal karne ke liye code mein tabdeeli kar ke ghalti theek ki jati hai.
Tools aur achhe tareeqe (Tools and Best Practices)
Debugging ke liye kai tools aur achhe tareeqe hain, jaise:
Debuggers: software tools jo programmers ko code step by step chalane, variables ki values dekhne aur program ke chalne par nazar rakhne de kar bugs dhoondne mein madad dete hain.
Print Statements: code mein print statements daalna ta ke program ki mukhtalif jagahon par variables ki values screen par nazar aayein.
Code Reviews: doosre developers se apna code check karwana ta ke mumkina ghaltiyan pakri jayein.
1.8.2 Language Editors (Roman Urdu)
1.8.2 Language Editors · Reviewed lesson · version 1 · published 16 Nov 2026
Language editors, jinhein code editors bhi kehte hain, woh tools hain jo developers ko mukhtalif programming languages mein code likhne aur edit karne mein madad dete hain. In ka maqsad code likhne ke liye aasan (user-friendly) interface dena hai. Misalein:
Notepad++: saada lekin taqatwar code editor.
Sublime Text: apni tezi aur aasan istemal ki wajah se mashhoor.
VS Code: mashhoor editor jis ki bohat si extensions (izafi features) hain.
Mukhtasar khulasa
Language (code) editors: code likhne ka aasan interface; Notepad++, Sublime Text, VS Code.
1.3.1 Introduction to Software Process Models (Roman Urdu)
1.3.1 Introduction to Software Process Models · Reviewed lesson · version 1 · published 16 Nov 2026
Software process models software development lifecycle ke processes ki ek abstract (khayali, saada) tasveer hain. Yeh software systems banane ki planning, structuring (cheezon ko tarteeb dena) aur control ke liye ek framework (dhancha) dete hain. Software process models is liye aham hain ke yeh yeh cheezein dete hain:
Predictability (pehle se andaza): tay shuda process par chal kar teams results (nateejon) ka pehle se andaza laga sakti hain aur risks (khatron) ko behtar sambhal sakti hain.
Efficiency: structured methodologies (tay shuda tareeqe) development ke process ko aasan aur seedha banate hain aur bekaar mehnat kam karte hain.
Quality: process model par chalne se quality assurance (quality ki jaanch) ke tareeqe poore development lifecycle mein shamil rehte hain.
Mukhtasar khulasa
Process models: development ke processes ki abstract tasveer; planning, structuring aur control ka framework.
1.7.2.1 Unit Testing · Reviewed lesson · version 1 · published 16 Nov 2026
Unit Testing testing ka pehla level hai, jis mein software ke alag alag components ya modules ko akela (in isolation) test kiya jata hai. Har "unit" software ka chhota sa hissa hai jise test kiya ja sake, jaise koi function ya method. Unit testing ka asal maqsad yeh confirm (pakka) karna hai ke har component apne design ke mutabiq theek kaam kare aur umeed ke mutabiq chale.
add() function ka unit test
python
defadd(a, b):
returna + bdef
1.8.3 Translators (Roman Urdu)
1.8.3 Translators · Reviewed lesson · version 1 · published 16 Nov 2026
Translators woh tools hain jo ek programming language mein likha code aisi language mein badalte hain jo computer samajh sake. Translators high-level programming languages (jaise Python) ko machine language (binary code, yani 0 aur 1) mein badalte hain jise computer chala (execute kar) sakta hai.
Interpreters: code ko line by line translate karte hain (misal: Python interpreter).
Compilers: poore code ko ek hi dafa translate karte hain (misal: C/C++ ke liye GCC).
Mukhtasar khulasa
Translators: high-level code ko machine language mein badalte hain; interpreter line by line (Python), compiler ek saath (GCC).
1.7.2.4 Acceptance Testing · Reviewed lesson · version 1 · published 16 Nov 2026
Acceptance Testing testing ka aakhri level hai jo yeh tay karne ke liye kiya jata hai ke software release ke liye tayyar hai ya nahi. Yeh aksar end-users (aakhri istemal karne wale) ya clients karte hain ta ke yaqeen ho ke software un ki expectations (umeedein) aur requirements poori karta hai. Acceptance testing formal (official, likhe hue tareeqe se) ya informal (bina khaas tareeqe ke) ho sakti hai, aur is mein aam taur par asal istemal jaise scenarios (halaat) hote hain jin se software ki usability (istemal mein aasani), reliability aur performance jaanchi jati hai.
Mukhtasar khulasa
Acceptance testing: aakhri level; users ya clients asal jaise scenarios mein jaanch kar tay karte hain ke software tayyar hai (UAT).
1.4.4 Risk Assessment and Management · Reviewed lesson · version 1 · published 16 Nov 2026
Risk assessment aur management har software project ke bohat aham hisse hain. In mein woh potential risks (ho sakne wale khatre) pehchane jate hain jo project ki kamyabi par asar dal sakte hain, yeh jaancha jata hai ke har risk hone ka kitna chance hai aur us ka asar kitna hoga, aur un se nipatne ki strategies (tareeqe) banaye jate hain. Acha risk management project ko on track, budget ke andar aur quality standards ke mutabiq rakhta hai.
Risk Assessment aur Management ke steps
Risks pehchanein (Identify Risks): har woh khatra likhein jo project par asar dal sakta hai: technical risks (jaise technology ki tabdeeli), operational risks (jaise resources ki kami) ya external risks (bahar ke risks) (jaise market ka utaar charhao).
Analyze Risks (risks ko jaanchna): dekhein ke har risk hone ka chance kitna hai aur project par us ka asar kitna hoga. Is se pata chalta hai ke kin risks par zyada dhyan chahiye.
Develop Mitigation Strategies (risk kam karne ke tareeqe banana): har bare risk ke liye plan banayein jo us ka chance ya asar kam kare, jaise schedule mein buffer (izafi waqt) rakhna, backup resources rakhna ya zyada testing karna.
Monitor and Review (nazar rakhna aur dobara dekhna): project par lagatar nazar rakhein ke naye risks to nahi aaye, aur purane risks ko dekh kar zaroorat ke mutabiq tareeqe badlein.
Misal: ek project nayi, untested (pehle kabhi test na hui) technology istemal kar raha hai. Khatra yeh hai ke technology umeed ke mutabiq kaam na kare, jis se der ho aur zyada kharcha ho.
1.4.5 Quality Assurance (Roman Urdu)
1.4.5 Quality Assurance · Reviewed lesson · version 1 · published 16 Nov 2026
Quality assurance yaqeeni banati hai ke project tay shuda standards (qaide aur paimane) poore kare aur theek kaam kare. Is mein yeh tareeqe shamil hain: testing, code ka review (jaanch), stakeholders se feedback lena aur project ki progress ko regular taur par check karna.
Misal: software project mein is ka matlab yeh yaqeeni banana hai ke code sahi likha gaya ho aur waisa hi kaam kare jaisa umeed hai.
Mukhtasar khulasa
Quality assurance: project standards poore kare aur theek chale; tareeqe: testing, code review, feedback, progress ki jaanch.
Execution (kaam karna): team kaam karti hai aur product banati hai.
Performance monitoring (progress par nazar rakhna): progress, kharche aur quality ko plan se mila kar dekha jata hai.
Project closure (project khatam karna): mukammal product hawale kar ke project band kiya jata hai.
1.2 Introduction to Software Development Life Cycle (SDLC) (Roman Urdu)
1.2 Introduction to Software Development Life Cycle (SDLC) · Reviewed lesson · version 1 · published 16 Nov 2026
Software Development Life Cycle (SDLC) ek framework (dhancha) hai jo batata hai ke organizations (companiyan aur idare) kisi application ko shuru ke khayal (initial conception) se le kar us ki deployment aur maintenance tak kin processes se banati hain. SDLC ka sab se bara maqsad aisa high-quality software dena hai jo customer ki expectations (umeedein) poori kare ya us se bhi behtar ho, diye gaye waqt aur kharche (time and cost estimates) ke andar mukammal ho, aur efficiently (achi tarah, kam resources mein) kaam kare.
Mukhtasar khulasa
SDLC: application ko khayal se deployment aur maintenance tak banane ke processes ka framework.
Maqsad: high-quality software, waqt aur kharche ke andar, efficiently kaam karta hua.
1.8.8 Source Code Repositories · Reviewed lesson · version 1 · published 16 Nov 2026
Source code repositories woh platforms hain jahan developers apna code rakh (store), sambhal (manage) aur us mein hone wali tabdeeliyan track kar sakte hain. Repositories version control mein madad deti hain, yani kai developers baghair conflicts (takrao) ke ek hi project par kaam kar sakte hain. Repositories code ki tabdeeliyon ka hisab rakhti hain aur tamam tabdeeliyon ki history (pichhla record) mehfooz rakhti hain.
GitHub: open-source projects ke liye mashhoor platform.
Bitbucket: private aur public dono tarah ki repositories ke liye istemal hota hai.
Mukhtasar khulasa
Repositories: code store, manage aur track karna; version control aur history; GitHub, Bitbucket.
1.2.2.4 Testing · Reviewed lesson · version 1 · published 16 Nov 2026
Jab software ban jata hai to woh ek bohat aham phase se guzarta hai jise testing kehte hain. Testing software ko check karne ka process hai ta ke koi bugs, errors ya masle pehchane ja sakein. Ise quality check samjhein jo yaqeeni banata hai ke sab kuch waisa hi kaam kare jaisa umeed hai. Testing mein software ko mukhtalif halaat (conditions) mein chala kar dekha jata hai ke woh theek kaam karta hai ya nahi. Is mein shamil hai:
Functionality Testing: check karna ke software ke tamam features specifications (detail mein likhi requirements) ke mutabiq kaam karte hain.
Performance Testing: check karna ke software mukhtalif halaat mein, jaise zyada traffic (bohat se users) ya bhaari data, achi tarah chalta hai.
Compatibility Testing: yaqeeni banana ke software mukhtalif devices aur operating systems par theek chalta hai.
Testing se woh chhupe hue masle samne aate hain jo development ke dauran nazar nahi aaye thay. In masloon ko theek kar ke developers yaqeeni banate hain ke software aasani se chale aur user ki zarooratein poori kare, aur user ko behtar aur zyada reliable (bharosay wala) tajurba mile.
Mukhtasar khulasa
1.3.1.1 Waterfall Model (Roman Urdu)
1.3.1.1 Waterfall Model · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.1 MB
Waterfall Model software banane ka ek seedha tareeqa hai jis mein project ki har phase agli phase shuru hone se pehle mukammal honi chahiye. Ise waterfall (aabshar / jharna) samjhein jis ka paani ek level se agle level par girta hai. Yeh model linear aur sequential (seedhi line mein, ek ke baad ek) hai: aap har phase se order mein guzarte hain aur mukammal ho chuki phase par wapas nahi jate, jaisa Figure 1.2 mein dikhaya gaya hai. Waterfall Model ki main phases yeh hain:
Saada aur samajhne mein aasan: is ki phases saaf aur alag alag hain, is liye is par chalna aasan hai.
1.2.1 Framework in Software Development (Roman Urdu)
1.2.1 Framework in Software Development · Reviewed lesson · version 1 · published 16 Nov 2026
Software engineering mein framework concepts, tareeqon (practices) aur tools ka ek standard aur reusable (baar baar istemal hone wala) set hai jo software applications banane ke liye ek structured foundation (tayyar bunyad / dhancha) deta hai. Framework pehle se bane hue components (hisse) aur architectures (banawat) deta hai jin se khaas software features banana aasan ho jata hai. Is tarah developers aam masloon ka hal dobara se banane (reinventing) ki bajaye sirf apni application ka khaas code likhne par dhyan dete hain. Frameworks kaam ko efficient, consistent (aik jaisa) aur code ko reusable banate hain, is liye software ki quality aur maintainability (aasani se theek aur update hona) behtar hoti hai.
Misal: Farz karein aap website banana chahte hain. Saara code shuru se likhne ki bajaye aap Django jaisa framework (websites ke liye) istemal kar sakte hain. Django mein user login, database management aur page templates jaise tayyar features hote hain. Yeh aisa hai jaise ghar banane ke liye sab kuch khud design karne ki bajaye pehle se bana hua naqsha (blueprint) istemal karna.
Mukhtasar khulasa
Framework: concepts, practices aur tools ka standard, reusable set jo software banane ki tayyar bunyad deta hai.
1.4 Project Planning and Management · Reviewed lesson · version 1 · published 16 Nov 2026
Software project ki planning safar (trip) ki planning jaisi hai. Aap ko maloom hona chahiye ke aap kahan ja rahe hain, kitna waqt lagega aur kitna kharcha hoga.
Mukhtasar khulasa
Project planning: shuru se pehle maqsad, waqt aur kharcha jaanna, safar ki planning ki tarah.
1.5.2.3 Sequence Diagrams · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.2 MB
Sequence Diagrams dikhate hain ke system ke objects ek khaas sequence (order) mein aapas mein kaise kaam (interact) karte hain. In se samajh aata hai ke waqt ke saath objects ke darmiyan messages kis tarah aate jate hain.
Interactions
open(): user har dabba kholta hai.
put toys/books/clothes inside: user khilone, kitabein aur kapre apne apne dabbe mein daalta hai.
close(): user har dabba band karta hai.
Figure 1.11: User ka cheezein label wale dabbon mein rakhne ka sequence diagram (kitab ki Figure 1.11 ke mutabiq apni banayi hui drawing).
1.6 Introduction to Design Patterns (Roman Urdu)
1.6 Introduction to Design Patterns · Reviewed lesson · version 1 · published 16 Nov 2026
Design patterns software development ka fundamental (bunyadi) concept hain. Yeh un aam masloon ke aazmaye hue (proven) hal hain jo software banate waqt baar baar samne aate hain. Yeh blueprints (naqshe) ya templates (saanche) ki tarah hain jinhein mukhtalif design ke masle hal karne ke liye apne mutabiq dhaala ja sakta hai, is liye development ka process zyada efficient aur ek jaisa (consistent) ho jata hai.
Mukhtasar khulasa
Design patterns: aam design masloon ke aazmaye hue hal; blueprints ya templates ki tarah.
1.4.2 Setting Project Timelines · Reviewed lesson · version 1 · published 16 Nov 2026
Project timelines set karne ka matlab hai yeh tay karna ke project ka har hissa kitna waqt lega. Is se project apne raaste par (on track) rehta hai aur waqt par mukammal hota hai.
Misal: agar aap website bana rahe hain to site design karne ki ek timeline, content likhne ki doosri aur sab kuch test karne ki teesri timeline rakh sakte hain.
Mukhtasar khulasa
Timelines: har hissa kitna waqt lega; project ko on track aur waqt par rakhti hain (website: design, content, testing).
1.7.2.2 Integration Testing · Reviewed lesson · version 1 · published 16 Nov 2026
Unit testing ke baad Integration Testing ki jati hai ta ke mukhtalif components ya modules ke darmiyan interaction (len den) jaancha jaye. Unit testing akele units par focus karti hai, jab ke integration testing yaqeeni banati hai ke yeh units milane ke baad saath theek kaam karein. Is testing mein interface ki ghaltiyan (do hisson ke jor ki ghaltiyan), modules ke darmiyan data ka bahao aur integration (jorne) wale doosre masle check kiye jate hain. Is se woh masle pakre jate hain jo unit testing mein samne nahi aate, jaise modules ki aapas ki communication ya data sambhalne mein mismatch (mel na khana).
Mukhtasar khulasa
Integration testing: unit testing ke baad; units ko mila kar test karna; interface errors aur data flow check karna.
1.5.1 Introduction to UML · Reviewed lesson · version 1 · published 16 Nov 2026
Unified Modeling Language (UML) software system ka design tasveer ki shakal mein dikhane ka ek standard tareeqa hai. Yeh developers ko samajhne mein madad deti hai ke system kaise kaam karta hai aur us ke hisse aapas mein kaise communicate (baat cheet) karte hain. UML is liye aham hai ke yeh complex systems ko samajhna aur sambhalna aasan banati hai.
Mukhtasar khulasa
UML: software design dikhane ka standard tasveeri tareeqa; complex systems samajhna aur sambhalna aasan.
1.6.1.2 Factory Pattern · Reviewed lesson · version 1 · published 16 Nov 2026
Factory Design Pattern ek khaas workshop jaisa hai jo mukhtalif products banana janti hai, lekin aap ko yeh fikr nahi karni ke woh products kaise bante hain. Aap bas factory ko batate hain ke aap ko kya chahiye, aur woh aap ko tayyar product de deti hai.
Mukhtasar khulasa
Factory: factory ko batao kya chahiye, woh tayyar object de deti hai; banane ki details chhupi rehti hai (workshop ki tarah).
1.3.1.3 Other Methodologies · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.3 MB
I. Scrum
Scrum ek agile framework hai jo complex (mushkil, kai hisson wale) software projects ko chalane aur mukammal karne ke liye bohat istemal hota hai. Yeh iterative (chhote chakkaron mein dohra kar) progress, mil jul kar kaam (collaboration) aur lachak (flexibility) ko barhata hai, is liye un badalte mahol ke liye bohat munasib hai jahan requirements aksar badalti hain. Yeh framework roles, events aur artifacts par bana hai jo project management ko structured (tarteeb wala) bhi rakhte hain aur adaptable (badalne ke qabil) bhi.
Scrum ke aham hisse (Key Components of Scrum)
Roles (kirdar): Scrum ke main roles Product Owner, Scrum Master aur Development Team hain. Product Owner product backlog (kaamon ki list) banata hai aur dekhta hai ke team sab se zyada priority (ahmiyat) wale kaam par kaam kare. Scrum Master process ko aasan banata hai, rukawatein hatata hai aur dekhta hai ke team Scrum ke tareeqon par chale. Development Team, jis mein mukhtalif maharat wale log hote hain (cross-functional), product ke naye hisse (increments) bana kar deti hai.
Events: Scrum mein regular progress aur review (jaanch) ke liye events hote hain: Sprints (fixed waqt ke iterations), Sprint Planning, Daily Standups (rozana chhoti meeting), Sprint Reviews aur Sprint Retrospectives (sprint ke baad apne kaam ke tareeqe par ghaur).
Artifacts: Scrum ke aham artifacts yeh hain: Product Backlog (features aur requirements ki priority wali list), Sprint Backlog (ek sprint mein poore hone wale kaamon ki list) aur Increment (is sprint ke nateeje mein bana hua chalta product).
1.8.1 Definitions and Usage (Roman Urdu)
1.8.1 Definitions and Usage · Reviewed lesson · version 1 · published 16 Nov 2026
Software development tools woh programs ya applications hain jo software banane ki mukhtalif stages mein madad karte hain. Yeh code likhne, edit karne, test karne, debug karne aur sambhalne ke liye istemal hote hain, ta ke software theek aur efficiently kaam kare.
Mukhtasar khulasa
Development tools: code likhne, edit, test, debug aur manage karne wale programs.
1.5 Graphical Representation of Software Systems (Roman Urdu)
1.5 Graphical Representation of Software Systems · Reviewed lesson · version 1 · published 16 Nov 2026
Software systems ki graphical representation (tasveeron ke zariye dikhana) ka matlab hai software system ke structure (banawat) aur behavior (system kaise chalta hai) ke mukhtalif pehlu diagrams ke zariye dikhana. Is se complex systems saada ho jate hain, aur developers aur stakeholders ke liye system ko samajhna, us par baat karna aur us ko sambhalna aasan ho jata hai. Unified Modeling Language (UML) jaise diagrams software ke mukhtalif components, un ke aapas ke rishte aur interactions (len den) dikhane ke liye bohat istemal hote hain.
Mukhtasar khulasa
Graphical representation: system ka structure aur behavior diagrams se dikhana; samajhna, baat karna aur sambhalna aasan; UML diagrams aam hain.
1.7.2 Testing · Reviewed lesson · version 1 · published 16 Nov 2026
Testing software ko jaanchne (evaluate karne) ka process hai ta ke yaqeeni ho ke woh requirements poori karta hai aur umeed ke mutabiq kaam karta hai. Testing ka process aam taur par ek hierarchy (chhote se bare tak darjon) par chalta hai: chhote hisson se shuru ho kar aahista aahista poore system tak, aur aakhir mein user acceptance (user ka software ko qubool karna) tak. Is hierarchy ki main qismein neeche di gayi hain.
Mukhtasar khulasa
Testing: requirements ke mutabiq software jaanchna; hierarchy: unit, integration, system, acceptance.
1.6.1.1 Singleton Pattern · Reviewed lesson · version 1 · published 16 Nov 2026
Singleton Design Pattern yeh yaqeeni banane ka tareeqa hai ke program mein koi khaas object ya resource sirf ek baar bane aur jab bhi zaroorat ho usi ko dobara istemal kiya jaye. Ise aise samjhein ke ek khaas kamre ki sirf ek chaabi hai; jo bhi kamre mein jana chahe, sab ko wahi ek chaabi istemal karni hai. Nayi chaabiyan nahi banti, sab ek hi chaabi share karte hain.
Mukhtasar khulasa
Singleton: object sirf ek baar banta hai aur sab usi ko share karte hain (ek kamre ki ek chaabi).
1.8.4 Compilers · Reviewed lesson · version 1 · published 16 Nov 2026
Compilers translator ki ek qism hain jo poore program ko chalne (execution) se pehle high-level language se machine code mein badalte hain. Compilers ka maqsad code ko behtar (optimize) kar ke efficient machine code mein badalna hai. Misalein:
GCC: C aur C++ ke liye GNU Compiler Collection. Javac: Java programs ka compiler.
Mukhtasar khulasa
Compilers: poora program chalne se pehle efficient machine code mein; GCC (C/C++), Javac (Java).
1.2.2.1 Requirement Gathering · Reviewed lesson · version 1 · published 16 Nov 2026
Is pehli phase (hissa / qadam) mein maqsad yeh samajhna aur jama karna hai ke software ko kya kaam karna hai. Is ke liye un logon se baat ki jati hai jo software istemal karenge, aur doosre stakeholders (jin ka project se talluq hai) se bhi, ta ke un ki zarooratein aur expectations (umeedein) maloom hon. Misal: agar aap school ke liye nayi app bana rahe hain to students, teachers aur administrators se poochenge ke woh app mein kaun se features dekhna chahte hain.
Is phase ke aham kaam (key activities):
Interviews and Surveys: potential users (jo aage software istemal karenge) se sawal poochna aur un ki raaye (feedback) jama karna ta ke un ki zarooratein aur pasand samajh aayein.
Observations (ghaur se dekhna): dekhna ke users abhi chalne wale (current) systems ko kaise istemal karte hain, ta ke masle aur behtari ke mauqe nazar aayein.
Document Review: pehle se bane hue documents, jaise reports aur user manuals, parhna ta ke requirements ke baare mein aur maloomat milein.
Functional and Non-Functional Requirements (Roman Urdu)
Functional and Non-Functional Requirements · Reviewed lesson · version 1 · published 16 Nov 2026
Requirements aam taur par do qismon mein baanti jati hain: functional aur non-functional requirements.
Functional Requirements
Functional requirements system ke khaas kaam (functions) aur behavior (system kaise chalta hai) batati hain. Yeh batati hain ke system ko kya karna chahiye: kaun se tasks, services aur features system ko lazmi karne hain. Yeh system aur us ke users, ya doosre systems, ke darmiyan len den (interactions) ko tay karti hain.
Misal:
Library Management System ki functional requirements.
User Registration: system users (students, faculty) ko register karne aur account banane de.
Book Borrowing: system users ko kitabein dhoondne aur udhaar (borrow) lene de.
Book Return: system users ko udhaar li hui kitabein wapas karne de.
Inventory Management: librarians inventory (kitabon ke stock) mein kitabein add, update aur remove kar sakein.
Notification: system users ko wapsi ki tareekh (due date) aur der se wapas hone wali (overdue) kitabon ki notification (khabar) bheje.
Non-Functional Requirements
1.5.2.1 Use Case Diagrams (Roman Urdu)
1.5.2.1 Use Case Diagrams · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.3 MB
Use Case Diagrams Unified Modeling Language (UML) ka fundamental (bunyadi, sab se aham) hissa hain. Yeh dikhate hain ke users, jinhein actors kaha jata hai, system ke saath kin kin tareeqon se kaam (interact) karte hain. Yeh diagrams user ki nazar se system ki functionality (system kya kya kar sakta hai) ki tasveer dete hain, aur requirements aur users aur system ke darmiyan len den pehchanne mein madad karte hain.
Definition (tareef) aur Purpose (maqsad)
Use case user (actor) aur system ke darmiyan un interactions (len den) ki description (bayan) hai jin se koi khaas maqsad (goal) poora hota hai. Use cases un functionalities ki bunyad par pehchane jate hain jo user ki zarooratein poori karne ke liye system mein honi chahiye. Har use case user ki nazar se ek mukammal workflow (kaam ka silsila) hai, jo kisi khaas kaam ko poora karne ke steps batata hai.
Use Case Diagrams kai kaamon ke liye istemal hote hain:
Functional requirements pakarna: system ki functional requirements pehchanne aur likhne mein madad dete hain.
User interactions samajhna: dikhate hain ke mukhtalif users system ke saath kaise kaam karenge.
Planning aur testing: development ke process ki planning mein aur system ke features check karne ke test cases banane mein madad dete hain.
Use cases kaise pehchanein (Identifying Use Cases)
1.2.2.2 Design (Roman Urdu)
1.2.2.2 Design · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.1 MB
Design phase mein hum plan karte hain ke software kaisa dikhega aur kaise kaam karega. Yeh ghar banane se pehle us ka naqsha (blueprint) banane jaisa hai. Is phase mein hum:
Diagrams banate hain: yeh dikhane ke liye ke software ke mukhtalif hisse kaise jurenge aur mil kar kaam karenge. Misal: hum flowchart banate hain jo dikhata hai ke program kaam poora karne ke liye kaun se steps lega.
Models banate hain: software ki banawat (structure) dikhane ke liye. Is mein user interface ke mockups (namoone) bhi ho sakte hain jo dikhate hain ke program kaisa nazar aayega aur users us ke saath kaise kaam karenge.
Architecture plan karte hain: software ki poori banawat tay karna, aur yeh ke mukhtalif components (hisse) aapas mein kaise kaam karenge. Is se program organized (tarteeb se) rehta hai aur aasani se chalta hai.
Requirements saaf karte hain (Specify Requirements): saaf likhna ke software ke har hisse ko kya karna hai, ta ke har feature plan ho aur koi cheez reh na jaye.
Yeh steps yaqeeni banate hain ke aakhri software organized ho, user-friendly (istemal mein aasan) ho aur users ki zarooratein poori kare.
1.2.2.6 Maintenance (Roman Urdu)
1.2.2.6 Maintenance · Reviewed lesson · version 1 · published 16 Nov 2026
Aakhri phase mein lagatar (ongoing) maintenance aur updates hote hain. Is se software theek chalta rehta hai aur users ki zarooraton ya technology mein tabdeeli ke mutabiq dhalta (adapt hota) rehta hai.
Mukhtasar khulasa
Maintenance: aakhri phase; lagatar updates aur fixes ta ke software theek chale aur tabdeeli ke mutabiq dhale (paude ki dekh bhaal ki tarah).
1.8.5 Debuggers · Reviewed lesson · version 1 · published 16 Nov 2026
Debuggers woh tools hain jo developers ko apne code mein errors (bugs) dhoondne aur theek karne mein madad dete hain. Debuggers ka maqsad developers ko apna code test karne aur yeh pehchanne dena hai ke errors kahan aate hain. Misalein:
GDB: C/C++ ke liye GNU Debugger.
Visual Studio Debugger: Visual Studio IDE ke andar shamil.
Mukhtasar khulasa
Debuggers: code test kar ke errors ki jagah dhoondne aur theek karne ke tools; GDB, Visual Studio Debugger.
1.6.1 Commonly Used Design Patterns · Reviewed lesson · version 1 · published 16 Nov 2026
Design patterns bohat se hain, lekin kuch zyada istemal hote hain kyun ke woh har tarah ke kaam aate hain (versatile) aur bohat se masle achi tarah hal karte hain. Neeche sab se zyada mashhoor design patterns diye gaye hain:
Chaar aam design patterns
Pattern
Khayal
Rozmarra ki misal
Singleton
ek object sirf ek baar banta hai aur sab usi ko istemal karte hain
khaas kamre ki ek hi chaabi jo sab istemal karte hain
Factory
aap object maangte hain; factory khud tay karti hai ke kaise banana hai
workshop jo tayyar product de deti hai
Introduction (Roman Urdu)
Introduction · Reviewed lesson · version 1 · published 16 Nov 2026
Student Learning Outcomes (is unit mein kya seekhenge)
Is unit ke aakhir tak aap yeh kar sakenge:
Software development kya hai yeh bata sakenge aur yeh kyun zaroori (important) hai, samjha sakenge.
Software development ke ahem terms samajh aur bata sakenge, jaise Software Development Life Cycle (SDLC), debugging (ghaltiyan dhoond kar theek karna), testing aur design patterns.
SDLC ki stages (hisse) aur har stage ka objective (maqsad) aur us mein hone wale kaam bata sakenge.
Software development ki alag alag methodologies (kaam ke tareeqe) mein farq bata sakenge, jaise Waterfall model aur Agile methodology.
Software project ki planning kar sakenge: timelines (waqt ka khaka) banana, cost (kharcha) ka andaza lagana aur risks (khatre) sambhalna.
Quality assurance (quality ki jaanch) ke tareeqe pehchan aur istemal kar sakenge taake software achhi quality ka ho.
Software systems dikhane ke liye Unified Modeling Language (UML) diagrams istemal kar sakenge.
Aam software design patterns pehchan kar software design mein istemal kar sakenge.
Debugging ke tareeqe aur testing strategies istemal kar ke software ko reliable (bharosemand) bana sakenge.
Software development ke tools samajh aur istemal kar sakenge, jaise Integrated Development Environment (IDE), compilers aur source code repositories (code rakhne ki jagah).
Software development ek systematic (tarteeb aur qaide wala) process hai jo users ki zarooraton (needs) ko software products mein badalta hai. Is mein kai stages (hisse) hoti hain: shuru ke analysis (jaanch) se le kar design, coding, testing aur deployment tak. Har stage ki apni ahmiyat hai aur har stage ke liye khaas skills aur tools chahiye hote hain. Software development ka process samajhna zaroori hai ta ke hum reliable (bharosay ke qabil), maintainable (aasani se theek aur update hone wala) aur scalable (barhne ke qabil) software bana sakein. Yeh chapter software development ke basic (bunyadi) concepts sikhata hai: aham terms, Software Development Life Cycle (SDLC), software development methodologies (kaam karne ke tareeqe), project planning aur management, quality assurance aur software design patterns.
1.4.1 Comprehensive Project Planning (Roman Urdu)
1.4.1 Comprehensive Project Planning · Reviewed lesson · version 1 · published 16 Nov 2026
Comprehensive (mukammal) project planning ka matlab hai project shuru karne se pehle us ki tamam details par sochna. Is mein yeh samajhna shamil hai ke kya karna hai, kaun karega aur kaise kiya jayega.
Mukhtasar khulasa
Comprehensive planning: shuru se pehle tay karna ke kya karna hai, kaun karega aur kaise.
1.6.1.4 Strategy Pattern · Reviewed lesson · version 1 · published 16 Nov 2026
Strategy Design Pattern mukhtalif tools (auzaron) se bhare dabbe (toolbox) jaisa hai, jis mein har tool ek khaas kaam ke liye bana hai. Jab koi masla aaye to aap kaam ke mutabiq dabbe se theek tool chun lete hain. Yani masla hal karne ke “kai tareeqe” hote hain aur aap baqi cheezein zyada badle baghair un mein aasani se badal sakte hain.
Mukhtasar khulasa
Strategy: ek kaam ke kai tareeqe; zaroorat ke mutabiq chuno aur aasani se badlo (toolbox).
1.1 Software Development · Reviewed lesson · version 1 · published 16 Nov 2026
Software development computer programs banane ka process hai, aise programs jo khaas kaam (specific tasks) karne ke liye banaye jate hain. Is mein code likhna, us ko test karna aur jo masle (issues) samne aayein un ko hal karna shamil hai. Software development is liye aham hai ke yeh masle hal karta hai aur hamari zindagi aasan banata hai. Misal ke taur par software ki madad se hum social media par doston se baat karte hain, banking apps se apne paise sambhalte hain, aur educational games se seekhna mazedar ban jata hai.
Mukhtasar khulasa
Software development: khaas kaam karne wale programs banana: code likhna, test karna, masle hal karna.
Aham kyun: masle hal karta hai aur zindagi aasan banata hai (social media, banking apps, educational games).
Summary · Reviewed lesson · version 1 · published 16 Nov 2026
Is chapter mein aap ne software development ke zaroori pehlu parhe: basic (bunyadi) concepts aur aham terms se le kar Software Development Life Cycle (SDLC) ki detailed stages tak. Aap ne software development ki mukhtalif methodologies dekhin, jin mein Waterfall model aur Agile methodology shamil hain, aur seekha ke software project ki planning aur management achi tarah kaise ki jati hai. Chapter mein quality assurance ke tareeqe, graphical representation ke liye UML ka istemal aur software design mein design patterns ki ahmiyat bhi aayi. Aakhir mein aap ne debugging ke tareeqe, testing ki strategies aur woh mukhtalif software development tools parhe jo high-quality software products efficiently banane mein madad dete hain.
1.5.2.4 Activity Diagrams · Reviewed lesson · version 1 · published 16 Nov 2026
Images and handouts: 0.1 MB
Activity Diagrams kisi process mein activities ya steps ka bahao (flow) dikhate hain. Yeh complex kaamon ki logic (mantiq) ka model banane ke liye faidamand hain.
Misal: restaurant management system mein activity diagram 'Order Placement' (order dena) se 'Food Preparation' (khana tayyar karna) aur aakhir mein 'Order Delivery' (order pohanchana) tak ka process dikha sakta hai.
Figure 1.12: Decision aur connector nishan wala activity diagram (kitab ki Figure 1.12 ke mutabiq apni banayi hui drawing).
Upar wala activity diagram dikhata hai ke process shuru se aakhir tak kaise chalta hai. Restaurant ki misal mein process 'Start' se shuru hota hai, 'Order Placement' par jata hai, phir 'Food Preparation' par, aur aakhir mein 'Order Delivery' par. 'End' node process khatam karta hai. Teer (arrows) steps ka order dikhate hain, is liye samajhna aasan hai ke order kaise aage barhta hai.
Figure 1.6: DevOps Methodology (kitab ki Figure 1.6 ke mutabiq apni banayi hui drawing).
DevOps kin ke liye suitable (munasib) hai: DevOps web aur mobile apps aur cloud services ke liye behtareen hai jahan tez development aur scaling (barhna) bohat zaroori hai. Misal: Amazon ka e-commerce platform DevOps se lagatar naye features aur updates release karta hai.
DevOps kin ke liye munasib nahi: highly regulated (sakht qaide qanoon ke paband) ya hardware par depend karne wale projects ke liye DevOps kam munasib ho sakta hai. Misal: medical devices (hospital ki machines) ke software ko sakht testing aur compliance (qaide qanoon ki paabandi) chahiye, jo DevOps ki tez raftar se shayad mel na khaye.
"Waterfall" ki term sab se pehle Dr. Winston W. Royce ne 1970 mein pesh ki thi, lekin unhon ne is ko iteration (dohrane) ke baghair istemal karne ki support (himayat) nahi ki thi.
Mukhtasar khulasa
DevOps: development (Dev) aur IT operations (Ops) ka mel; chhota lifecycle, behtar quality, continuous delivery (Fig. 1.6).
Faide: collaboration, market tak jaldi (CI/CD), quality, efficiency. Web, mobile aur cloud (Amazon) ke liye munasib; medical devices jaise regulated projects ke liye kam.
Waterfall ki term Dr. Winston W. Royce ne 1970 mein pesh ki.
Requirements (1) se kaam shuru hota hai aur phir Design, Development, Testing, Deployment aur Review (2 se 6) ka chhota chakkar (iteration ya sprint) chalta hai. Review ke baad agla chakkar phir isi tarah chalta hai, is liye software chhote chhote hisson mein jaldi milta hai aur har chakkar ke baad raaye (feedback) li ja sakti hai. Waterfall ki seedhi lakeer ke muqable mein yahan gol chakkar hai.
Benefits aur Limitations (faide aur kamiyan)
Benefits (faide):
High Flexibility (zyada lachak): development shuru hone ke baad bhi requirements badli ja sakti hain, is liye nayi zarooraton ya feedback ke mutabiq dhalna aasan hai.
Improved Customer Satisfaction (customer ki zyada tasalli): regular updates aur kaam karta software baar baar milne se customer progress dekh sakte hain aur zyada baar feedback de sakte hain.
Limitations (kamiyan):
Scaling Challenges (bare projects mein mushkil): kai teams wale bare projects sambhalna mushkil hai, kyun ke bohat dhyan se coordination (sab teams ka kaam aapas mein jorna) aur baat cheet chahiye.
Stakeholder Involvement (stakeholders ka shamil hona): Agile mein tamam stakeholders ka poora hissa lena zaroori hai; agar kuch log available (mojood) na hon ya poori tarah shamil na hon to mushkil hoti hai.
Less Predictable (pehle se andaza mushkil): Agile projects feedback aur tabdeeliyon se aage barhte hain, is liye aakhri product ka theek waqt (timeline) aur scope (daira) pehle se batana mushkil hai.
Mukhtasar khulasa
Agile: flexible aur adaptive; chhote iterations ya sprints mein kaam karte hisse aur jaldi feedback (Fig. 1.3).
Practices: continuous integration, test-driven development, pair programming. Benefits: lachak, customer ki tasalli; limitations: bare projects, stakeholders ka shamil hona, kam andaza.
Figure 1.10: Kamra organize karne ka class diagram (kitab ki Figure 1.10 ke mutabiq apni banayi hui drawing, UML ke inheritance (virasat) wale arrowhead ke saath).
Mukhtasar khulasa
Class diagram: classes (attributes aur methods ke saath) aur un ke rishte; kamre ke dabbon ki misal (Fig. 1.10).
ToyBox, BookBox aur ClothesBox aam Box class ki khaas qismein hain.
Operational Costs: cloud hosting, development tools aur software licenses ke kharche.
Risk Management: scope ki tabdeeli aur technology jorne (integration) ke masle mumkina risks hain; kul kharche ka 10% contingency fund rakha jayega.
Quality Assurance: functionality aur performance yaqeeni banane ke liye mukammal testing phases.
Cost Breakdown (kharche ki detail)
Kharche ka sahi hisab (PKR)
Item
Hisab
Kharcha (PKR)
Project Manager
5,000/ghanta x 20 ghante/hafta x 24 hafte
2,400,000
Frontend Developers
2 x 3,500/ghanta x 30 ghante/hafta x 24 hafte
5,040,000
Backend Developers
2 x 4,000/ghanta x 30 ghante/hafta x 24 hafte
5,760,000
UI/UX Designer
3,000/ghanta x 20 ghante/hafta x 24 hafte
1,440,000
QA Testers
2 x 2,500/ghanta x 20 ghante/hafta x 24 hafte
2,400,000
Operational Costs
cloud services aur tools
1,000,000
Jama (subtotal)
upar ke chhe items
18,040,000
Contingency Fund
18,040,000 ka 10%
1,804,000
Total Estimated Cost
18,040,000 + 1,804,000
19,844,000
swipe
Explanation (wazahat): kul andazan kharcha PKR 19,844,000 development ke tamam hisson ko shamil karta hai: planning aur design se le kar implementation aur testing tak. Yeh misal dikhati hai ke mukhtalif factors kul kharche mein kaise hissa dalte hain aur kharche ke andaze mein detailed planning kitni zaroori hai.
Khud chala kar dekhein
Yeh program upar wala kharche ka hisab khud karta hai. weeks, kisi ka rate ya contingency_percent badal kar Run karein aur dekhein ke subtotal (jama), contingency fund aur Total Estimated Cost kaise badalte hain.
Print statement ki misal (Python): agar kisi variable ki value ghalat aa rahi ho to program ke beech mein print() laga kar dekha jata hai ke us waqt value kya hai.
Print statements se har step par values dekhna
python
total = 0fornin [4, 5, 6]:
total = total + nprint("n =", n, "total =", total)
print("Final total:", total)
Output
n = 4 total = 4
n = 5 total = 9
n = 6 total = 15
Final total: 15
Khud chala kar dekhein
Yeh program ek bug aur us ka fix dikhata hai: bug wala hissa marks ka jama hamesha 2 se taqseem (divide) karta hai, jab ke fix marks ki asal ginti se. marks ki list mein number badlein ya ek aur number jorein, Run karein aur dekhein ke bug wala average kaise ghalat aata hai aur print() wali line bug pakarne mein kaise madad karti hai.
python
marks = [72, 85, 64] # teen subjects ke marks# Bug wala version: hamesha 2 se taqseem (divide) karta haiwrong_average = sum(marks) / 2# Debugging: print se values dekheinprint("sum =", sum(marks), "| marks ki ginti =", len(marks))
# Fix: jitne marks hain utni ginti se taqseem kareinright_average = sum(marks) / len(marks)
print("Bug wala average:", wrong_average)
print("Theek kiya hua average:", round(right_average, 2))
Mukhtasar khulasa
Debugging: bugs dhoondna aur theek karna; behavior dekh kar pehchanna, code badal kar hal karna.
Tools: debuggers, print statements, code reviews; 1947 ke patange (moth) ke waqiye se debugging ka naam para.
Mitigation Strategy (khatra kam karne ka tareeqa): technology ko main project mein poori tarah jorne se pehle ek chhota pilot project (test ke liye chhota project) chala kar test karein. Is se masle jaldi samne aa jate hain aur bare project ko nuqsan pohanchaye baghair un ko hal karne ka mauqa milta hai.
Discussion: kitab kehti hai ke ek figure risk management ka process dikhati hai: risks pehchanne se le kar monitor aur review tak. In steps par chal kar project managers risks ko step by step sambhal sakte hain aur project aasani se chalta hai.
Mukhtasar khulasa
Risk management ke steps: identify, analyze, mitigation strategies, monitor and review.
Misal: nayi technology ko pehle chhote pilot project mein test karna.
Sequential process: har phase ek waqt mein ek mukammal hoti hai, is liye kaam sambhalna aur progress dekhna aasan hai.
Chhote projects ke liye suitable (munasib): un projects ke liye acha hai jin ki requirements saaf aur pakki hon aur tabdeeli ka chance kam ho.
Limitations (kamiyan):
Inflexibility (lachak na hona): phase mukammal hone ke baad wapas ja kar tabdeeli karna mushkil aur mehnga hai.
Complex projects ke liye theek nahi: jin projects ki requirements badalti rehti hon ya design complex (mushkil) ho, un mein yeh model achi tarah chalana mushkil hai.
Risk and Uncertainty (khatra aur pakka pata na hona): yeh model farz karta hai ke saari requirements shuru se maloom hain; agar baad mein nayi zaroorat ya masla aaye to nuqsan ho sakta hai.
Figure 1.2: Waterfall Model (kitab ki Figure 1.2 ke mutabiq apni banayi hui drawing).Describe this diagram
Phases ke neeche chhape kaam: Requirements: project ka scope (daira) tay karna, stakeholders se interview, user research, requirements jama karna, kick-off meeting. Design: high-level design, design review, design mein tabdeeliyan, stakeholder ki manzoori. Implementation: dev phase 1, review, dev phase 2, review. Testing: testing, tabdeeliyan. Delivery: deployment.
Mukhtasar khulasa
Waterfall: linear aur sequential phases (requirements, design, implementation, testing, deployment, maintenance); wapas nahi jate (Fig. 1.2).
Benefits: saada, progress dekhna aasan, chhote pakke projects ke liye acha; limitations: lachak nahi, complex projects ke liye mushkil, risk.
Scrum kin ke liye suitable (munasib) hai: Scrum khaas taur par un software projects ke liye munasib hai jin mein baar baar updates chahiye hon aur requirements badalti rehti hon, jaise:
Mobile Applications: mobile app banane mein aksar lagatar feedback aur tez iterations chahiye hote hain ta ke users ki zarooratein poori hon aur app muqable mein rahe. Scrum ka iterative tareeqa user feedback aur market ki tabdeeli par jaldi tabdeeli karne deta hai.
Web Development: un web applications ke liye jinhein regular taur par naye features aur behtari chahiye. Scrum aisa development process deta hai jo nayi requirements aur user feedback ke mutabiq jaldi dhal jata hai.
Scrum kin ke liye suitable nahi: jin projects ki requirements pehle se saaf hon aur tabdeeli ka chance kam ho, un ke liye Scrum shayad behtareen na ho, jaise:
Embedded Systems: embedded systems (machines ke andar lage software) mein aksar hardware ke saath jorna aur strict regulations (sakht qaide qanoon) hote hain; un ke liye Scrum ke iterative tareeqe ki bajaye traditional (purana), linear (seedha) tareeqa behtar ho sakta hai.
Safety-Critical Software: medical software ya aerospace (jahaz aur khala) systems jaise projects, jahan mukammal documentation aur bohat zyada jaanch (validation) zaroori hai, Scrum ke lachakdar aur iterative tareeqe se achi tarah mel nahi khate.
Figure 1.4 Scrum ke process ka bahao (flow) dikhati hai: is ke aham hisse aur Scrum framework mein un ka aapas mein talluq.
Figure 1.4: Scrum Lifecycle (kitab ki Figure 1.4 ke mutabiq apni banayi hui drawing).
ii. Lean
Lean Software Development software banane ka iterative tareeqa hai jo efficiency, waste (bekaar kaam) khatam karne aur high-quality products jaldi dene par zor deta hai. Yeh Lean manufacturing (karkhanon mein bachat wale tareeqe) ke principles (usoolon) se nikla hai. Lean Software Development kaam ke bahao (flow of work) ko behtar kar ke aur ghair zaroori kaam kam kar ke customer ko value (faida) dene par focus karta hai.
Lean Software Development ke Key Principles (aham usool)
Eliminate Waste: woh kaam pehchan kar hata dein jo customer ke liye koi value nahi barhate.
Decide as Late as Possible: faisle jitni der se ho sake, sab se nayi maloomat ki bunyad par karein, ta ke uncertainty (pakka pata na hona) kam ho.
Deliver as Fast as Possible: chhote chhote, incremental (thore thore kar ke barhne wale) features jaldi dene ko pehle rakhein.
Empower the Team: teams ko faisle karne aur masle hal karne ki authority (ikhtiyar / haq) aur zimmedari dein.
Build Integrity In: development ke poore process mein quality qaim rakhein.
See the Whole: kaam ke poore bahao ko behtar karne ke liye poore system aur us ke mahol ko dekhein.
Figure 1.5: Lean Software Development Model (kitab ki Figure 1.5 ke mutabiq apni banayi hui drawing).
Lean kin ke liye suitable (munasib) hai: Lean Software Development khaas taur par un projects ke liye munasib hai jinhein tez delivery aur baar baar iterations chahiye, jaise startup software, mobile applications aur web-based services. Misal: nayi mobile app banane wala startup user feedback par jaldi jaldi tabdeeliyan kar ke aur faida dene wale updates de kar Lean ke usoolon se faida uthata hai.
Lean kin ke liye suitable nahi: jin projects mein shuru mein bohat zyada planning chahiye aur jo bohat complex hon ya highly regulated (sakht qaide qanoon ke paband) hon, jaise bare enterprise systems, embedded systems ya safety-critical applications, un ke liye Lean shayad behtareen na ho. Misal: aviation control system (hawai jahazon ko control karne wala system) ka software banane mein sakht documentation, bohat zyada testing aur regulatory compliance (qaide qanoon ki paabandi) chahiye, jo Lean ke iterative tareeqe se achi tarah mel nahi khati.
Scrum mobile aur web apps ke liye munasib; embedded aur safety-critical software ke liye nahi.
Lean: waste khatam karna, saat principles (Eliminate Waste se See the Whole tak); startups aur mobile apps ke liye munasib, sakht regulations wale bare systems ke liye nahi.
Non-functional requirements system ki quality attributes (quality ki khoobiyan), performance criteria (napne ke paimane) aur constraints (pabandiyan / hadein) tay karti hain. Yeh batati hain ke system koi kaam kaise (kitni achi tarah) karta hai, yeh nahi ke kya karta hai. In mein usability (istemal mein aasani), reliability (bharosa), performance aur security jaisi cheezein aati hain.
Misal:
Library Management System ki non-functional requirements.
Performance: system ek hi waqt mein 1000 tak users ko sust (slow) hue baghair sambhale.
Usability: user interface aasani se samajh aaye aur chalane mein aasan ho, ta ke users kam mehnat se kaam kar sakein.
Reliability: system 99.9% waqt chalta (available) rahe, yani bohat kam waqt band (downtime) ho.
Security: user ka data encrypted (khufiya code mein) ho, aur access mehfooz authentication (pehchan ki jaanch) se control ho.
Scalability: system barhte hue users aur inventory ki barhti kitabon ko sambhalne ke liye barh sake.
Use cases pehchanne ke process mein yeh steps hain:
Actors pehchanein: dekhein ke kis kis qism ke users system ke saath kaam karenge. Actors insaan bhi ho sakte hain aur doosre systems bhi.
Goals tay karein: har actor ke liye maloom karein ke us ka maqsad kya hai, yani woh system se kya kaam karwana chahta hai.
Interactions likhein: un goals tak pohanchne ke liye actors aur system ke darmiyan len den bayan karein. Har woh interaction jis ka koi aham nateeja nikle, ek possible (mumkina) use case hai.
Validate Use Cases (check kar ke pakka karna): pehchane gaye use cases stakeholders ke saath dekhein ta ke yaqeen ho ke zaroori features aur interactions sahi tarah shamil hain.
Figure 1.9: Library system ka use case diagram (kitab ki Figure 1.9 ke mutabiq apni banayi hui drawing).
Mukhtasar khulasa
Use case diagram: actors aur woh use cases jo woh system se karwate hain; functional requirements, interactions, planning aur testing.