BCA 108T Software Engineering Notes from Unnati Educations cover all 4 units of the GGSIPU BCA Semester 2 paper in 88 pages, with 40 diagrams, 9 solved numericals, 52 solved two-mark questions and 39 ten-mark questions mapped to their topics. They follow the syllabus for the batch admitted in 2024-25 onwards.
Scheme: BCA scheme w.e.f. 2024-25 (UGC CCFUP) | Applies to: batch admitted in 2024-25 onwards | Verified against: BCA scheme of examination, approved by the Academic Council on 20 Dec 2023
On this page
BCA 108T Software Engineering at a glance: GGSIPU BCA Sem 2 credits, units and exam pattern
| Item | Detail |
|---|---|
| Code and title | BCA 108T Software Engineering |
| Course and semester | BCA, Semester 2 |
| Category and credits | Core Course Theory (CCT), 4 credits, 4 lecture hours a week |
| Marks | 100: 40 internal + 60 end-term |
| Applies to | Batch admitted in 2024-25 onwards |
| End-term pattern | Q1 compulsory: 10 short questions of 2 marks, at least 2 per unit; then 1 of 2 questions from each unit at 10 marks (20 + 40 = 60 marks) |
| Units | 4 (official teaching hours 12, 10, 10, 12) |
| Paired lab | BCA 108P Software Engineering Lab: CCP, 1 credit, 40 internal + 60 external = 100 |
BCA 108T snapshot from the official BCA syllabus and scheme of examination
- Item
- Code and title
- Detail
- BCA 108T Software Engineering
- Item
- Course and semester
- Detail
- BCA, Semester 2
- Item
- Category and credits
- Detail
- Core Course Theory (CCT), 4 credits, 4 lecture hours a week
- Item
- Marks
- Detail
- 100: 40 internal + 60 end-term
- Item
- Applies to
- Detail
- Batch admitted in 2024-25 onwards
- Item
- End-term pattern
- Detail
- Q1 compulsory: 10 short questions of 2 marks, at least 2 per unit; then 1 of 2 questions from each unit at 10 marks (20 + 40 = 60 marks)
- Item
- Units
- Detail
- 4 (official teaching hours 12, 10, 10, 12)
- Item
- Paired lab
- Detail
- BCA 108P Software Engineering Lab: CCP, 1 credit, 40 internal + 60 external = 100
The paper sits with nine others in GGSIPU BCA Semester 2 papers.
BCA 108T Software Engineering Notes unit-wise: 40 diagrams and 9 solved numericals across 4 units
BCA 108T Unit 1: Introduction to Software Engineering and Requirement Analysis
Pages 5-29, 20 sections, 14 figures. Part A runs from the software crisis through the Waterfall, Prototype, Spiral, Iterative Enhancement and Agile models to one comparison table for "which model will you choose" questions.
Part B takes a single library management system through every diagram the syllabus names: Level-0 and Level-1 DFD, use-case with an "Issue Book" template, sequence, class and ER. It ends with the eight SRS characteristics and the IEEE 830 outline, then 14 two-mark answers.
Quick look: the three requirement types in QFD (from page 18)
| Type | Meaning | Library example |
|---|---|---|
| Normal | Stated by the customer | Search option |
| Expected | Unstated, but missing it upsets users | Data security |
| Exciting | Beyond expectation | SMS before the due date |
Quick look: three requirement types in QFD (from page 18)
- Type
- Normal
- Meaning
- Stated by the customer
- Library example
- Search option
- Type
- Expected
- Meaning
- Unstated, but missing it upsets users
- Library example
- Data security
- Type
- Exciting
- Meaning
- Beyond expectation
- Library example
- SMS before the due date
BCA 108T Unit 2: Software Project Planning and Risk Management
Pages 30-49, 15 sections, 6 figures. Metrics come first, then size: the LOC rule on a 7-line C program, function points with five function types, and Halstead's measures.
COCOMO follows in three modes, Basic and Intermediate, with the full 15-cost-driver table. Part B covers risk types, exposure and response strategies. The unit has 7 solved numericals, 3 practice numericals with answers, a formula sheet and 12 two-mark answers.
Quick look: Basic COCOMO constants (from page 40)
| Mode | a | b | c | d |
|---|---|---|---|---|
| Organic | 2.4 | 1.05 | 2.5 | 0.38 |
| Semi-detached | 3.0 | 1.12 | 2.5 | 0.35 |
| Embedded | 3.6 | 1.20 | 2.5 | 0.32 |
Quick look: Basic COCOMO constants, E = a(KLOC)b, D = c(E)d (from page 40)
- Mode
- Organic
- a
- 2.4
- b
- 1.05
- c
- 2.5
- d
- 0.38
- Mode
- Semi-detached
- a
- 3.0
- b
- 1.12
- c
- 2.5
- d
- 0.35
- Mode
- Embedded
- a
- 3.6
- b
- 1.20
- c
- 2.5
- d
- 0.32
BCA 108T Unit 3: Software Design, Quality Management and Implementation
Pages 50-69, 17 sections, 9 figures. Design covers seven types of cohesion and six of coupling, each with a C snippet.
Quality covers McCall's 11 factors, SQA, TQM and Fagan inspection. Implementation covers structured coding, re-engineering and five SCM activities, then 12 two-mark answers.
Quick look: cohesion against coupling (from page 56)
| Basis | Cohesion | Coupling |
|---|---|---|
| Measures | Inside one module | Between modules |
| Wanted | High | Low |
| Best type | Functional | Data |
| Worst type | Coincidental | Content |
Quick look: cohesion against coupling (from page 56)
- Basis
- Measures
- Cohesion
- Inside one module
- Coupling
- Between modules
- Basis
- Wanted
- Cohesion
- High
- Coupling
- Low
- Basis
- Best type
- Cohesion
- Functional
- Coupling
- Data
- Basis
- Worst type
- Cohesion
- Coincidental
- Coupling
- Content
BCA 108T Unit 4: Software Testing and Maintenance
Pages 70-88, 15 sections, 11 figures. Testing moves from the error, fault and failure chain to drivers and stubs, four integration approaches and nine kinds of system testing.
One table compares black, white and grey box testing, followed by the V-model, alpha and beta testing, and solved BVA and cyclomatic problems. Maintenance covers the four types, the IEEE 1219 process and five models, then 14 two-mark answers.
Quick look: three ways to get V(G) for the worked program (from page 81)
| Method | Working | V(G) |
|---|---|---|
| E − N + 2 | 8 − 7 + 2 | 3 |
| Predicates + 1 | 2 (if, while) + 1 | 3 |
| Regions | if-else, loop, outer | 3 |
Quick look: cyclomatic complexity of the worked program (from page 81)
- Method
- E − N + 2
- Working
- 8 − 7 + 2
- V(G)
- 3
- Method
- Predicates + 1
- Working
- 2 (if, while) + 1
- V(G)
- 3
- Method
- Regions
- Working
- if-else, loop, outer
- V(G)
- 3
Spiral model and risk analysis in software engineering: excerpt from page 12 of the BCA 108T notes
Excerpt from page 12
The Spiral Model was proposed by Barry Boehm in 1986. It joins the iterative nature of prototyping with the systematic steps of the waterfall model. Its defining feature is risk analysis in every cycle, which is why it is called a risk-driven model. Drawn on paper, it looks like a spiral with many loops, and each loop stands for one phase of the software process.
The four quadrants of each loop
- Determine objectives, alternatives and constraints: what this loop must achieve and which options exist.
- Evaluate alternatives; identify and resolve risks: risk analysis happens here, and a prototype may be built to reduce a risk.
- Develop and verify the next-level product: the actual design, coding and testing of this phase.
- Plan the next phase: the customer reviews the result and the next loop is planned.
Reading the diagram
The radius of the spiral shows the cumulative cost spent so far. The angular dimension shows the progress made inside the current loop. The number of loops is not fixed in advance; it depends on how risky the project turns out to be, which is why the end date is hard to predict.
Strengths and limits
| Advantages | Disadvantages |
|---|---|
| Risk is handled at every stage | Complex; needs risk-assessment experts |
| Suits large, high-risk projects | Costly for small projects |
| Customer feedback in every loop | Unknown number of loops makes the end date uncertain |
| Changes can be absorbed | A lot of documentation for intermediate stages |
Spiral model advantages and disadvantages (excerpt, page 12)
- Advantages
- Risk is handled at every stage
- Disadvantages
- Complex; needs risk-assessment experts
- Advantages
- Suits large, high-risk projects
- Disadvantages
- Costly for small projects
- Advantages
- Customer feedback in every loop
- Disadvantages
- Unknown number of loops makes the end date uncertain
- Advantages
- Changes can be absorbed
- Disadvantages
- A lot of documentation for intermediate stages
In an exam answer, quadrant 2 is the part to make visible. An answer that draws the spiral but never says where risk is identified and resolved misses the point of the model. Label each quadrant on the diagram itself, mark the radius as cost, and add one line saying that the number of loops depends on the risks found.
BCA 108T exam corner: 52 two-mark solved questions and 39 ten-mark questions by unit
| Unit | Two-mark answers (2 Marks) | Ten-mark questions (10 Marks) | Solved numericals |
|---|---|---|---|
| Unit 1 | 14 | 11 | 0 |
| Unit 2 | 12 | 8 | 7 (+3 practice) |
| Unit 3 | 12 | 10 | 0 |
| Unit 4 | 14 | 10 | 2 (+4 practice) |
| Total | 52 | 39 | 9 |
BCA 108T exam questions in the notes, by unit
- Unit
- Unit 1
- Two-mark answers (2 Marks)
- 14
- Ten-mark questions (10 Marks)
- 11
- Solved numericals
- 0
- Unit
- Unit 2
- Two-mark answers (2 Marks)
- 12
- Ten-mark questions (10 Marks)
- 8
- Solved numericals
- 7 (+3 practice)
- Unit
- Unit 3
- Two-mark answers (2 Marks)
- 12
- Ten-mark questions (10 Marks)
- 10
- Solved numericals
- 0
- Unit
- Unit 4
- Two-mark answers (2 Marks)
- 14
- Ten-mark questions (10 Marks)
- 10
- Solved numericals
- 2 (+4 practice)
- Unit
- Total
- Two-mark answers (2 Marks)
- 52
- Ten-mark questions (10 Marks)
- 39
- Solved numericals
- 9
Two-mark questions carry full answers; ten-mark ones point to their topics. One per unit:
- Unit 1 (page 27): Differentiate <<include>> and <<extend>>. Include is always used by the base use-case; extend is optional, as Pay Fine extends Return Book only for a late book.
- Unit 2 (page 48): What is CAF? Give its range. CAF = 0.65 + 0.01 × ΣFi over 14 characteristics rated 0 to 5, so 0.65 to 1.35.
- Unit 3 (page 68): Differentiate stamp and data coupling. Data coupling passes only needed values; stamp coupling passes a whole structure, as in
printName(studentRecord). - Unit 4 (page 87): How many BVA test cases for n variables? 4n + 1, and 6n + 1 for robustness testing.
The BCA 108T notes solve 52 two-mark questions across 4 units, map 39 ten-mark questions to their topics and work through 9 numericals step by step.
More practice for this paper sits in the BCA 108T important questions.
Who writes and checks the BCA 108T Software Engineering notes?
- Prateek Talwar, author and editor of these notes. Founder, Unnati Educations; Associate Company Secretary (ICSI, since May 2019); B.Com, University of Delhi (School of Open Learning), 2012. Author profile
- Ritik Rawat, subject reviewer for the BCA 108T notes. Senior Full Stack Developer, Unnati Educations; B.Tech. Reviewer profile
The 2026-27 edition maps to Table 7 (Second Semester) of the BCA scheme w.e.f. 2024-25: 88 pages, 67 numbered sections, 40 figures. Its solved numericals in Units 2 and 4 were recalculated for this edition and match their printed answers. Edited under our editorial policy.
The same team prepares GGSIPU important questions for every course, using this unit-by-unit mapping.
Do the BCA 108T notes cover the full GGSIPU syllabus?
Yes. Every topic in the four official BCA 108T units has a numbered section; the only wording difference is "Perceptive" maintenance, which the notes explain as Perfective.
| Official unit | Official topics | Where in the notes | Status |
|---|---|---|---|
| I | Software crisis; Waterfall, Prototype, Spiral, Agile, Iterative Enhancement models | 1.3-1.10, pp 8-15 | Covered |
| I | Requirement engineering; FAST, QFD; DFD, use-case, sequence, class (with case studies) and ER diagrams; SRS | 1.11-1.20, pp 16-25 | Covered |
| II | Metrics; LOC, function count; Halstead; cost estimation; COCOMO Basic and Intermediate | 2.1-2.10, pp 32-42 | Covered |
| II | Software risks, types, risk assessment, risk control | 2.11-2.15, pp 43-46 | Covered |
| III | Cohesion and coupling with classification | 3.1-3.5, pp 52-56 | Covered |
| III | Quality concept, SQA, TQM, review, inspection | 3.6-3.10, pp 57-61 | Covered |
| III | Structured coding, style, standards, documentation, reverse engineering, re-engineering, configuration management | 3.11-3.17, pp 62-67 | Covered |
| IV | Testing process, levels, manual and automation, black/white/grey box, V and V, alpha-beta, acceptance, functional and structural testing, debugging | 4.1-4.11, pp 72-82 | Covered |
| IV | Maintenance management, process; preventive, perceptive, adaptive, corrective | 4.12-4.15, pp 83-85 | Covered (as perfective, p 83) |
Official BCA 108T syllabus topics mapped to the notes
- Official unit
- I
- Official topics
- Software crisis; Waterfall, Prototype, Spiral, Agile, Iterative Enhancement models
- Where in the notes
- 1.3-1.10, pp 8-15
- Status
- Covered
- Official unit
- I
- Official topics
- Requirement engineering; FAST, QFD; DFD, use-case, sequence, class (with case studies) and ER diagrams; SRS
- Where in the notes
- 1.11-1.20, pp 16-25
- Status
- Covered
- Official unit
- II
- Official topics
- Metrics; LOC, function count; Halstead; cost estimation; COCOMO Basic and Intermediate
- Where in the notes
- 2.1-2.10, pp 32-42
- Status
- Covered
- Official unit
- II
- Official topics
- Software risks, types, risk assessment, risk control
- Where in the notes
- 2.11-2.15, pp 43-46
- Status
- Covered
- Official unit
- III
- Official topics
- Cohesion and coupling with classification
- Where in the notes
- 3.1-3.5, pp 52-56
- Status
- Covered
- Official unit
- III
- Official topics
- Quality concept, SQA, TQM, review, inspection
- Where in the notes
- 3.6-3.10, pp 57-61
- Status
- Covered
- Official unit
- III
- Official topics
- Structured coding, style, standards, documentation, reverse engineering, re-engineering, configuration management
- Where in the notes
- 3.11-3.17, pp 62-67
- Status
- Covered
- Official unit
- IV
- Official topics
- Testing process, levels, manual and automation, black/white/grey box, V and V, alpha-beta, acceptance, functional and structural testing, debugging
- Where in the notes
- 4.1-4.11, pp 72-82
- Status
- Covered
- Official unit
- IV
- Official topics
- Maintenance management, process; preventive, perceptive, adaptive, corrective
- Where in the notes
- 4.12-4.15, pp 83-85
- Status
- Covered (as perfective, p 83)
Source: BCA first-year syllabus, batch admitted 2024-25 onwards and BCA scheme of examination w.e.f. 2024-25.
Every course in GGSIPU notes is mapped to its official PDF the same way.
How to write BCA 108T answers: labelled DFD and UML diagrams, step-wise numericals and ten-mark theory answers
Page 28 of the notes fixes the ten-mark shape: definition, diagram, steps or parts, advantages and disadvantages, then an example.
For DFDs, page 20 asks for both Level-0 and Level-1, every arrow labelled and every bubble numbered. For an ATM or hospital system, list the actors first, then draw. For "which model will you choose", page 15 says name the deciding condition first (unclear requirements: Prototype; high risk: Spiral) and add two or three reasons.
In numericals, show the count × weight table before CAF, state assumptions, and write units with every result. The common-mistakes tables flag CAF without the 0.01, Intermediate COCOMO's organic a of 3.2 confused with Basic's 2.4, and 4n instead of 4n + 1 for BVA.
Worked example: a 20 KLOC organic project (Basic COCOMO, page 49)
Effort E = 2.4 × (20)^1.05 = 55.76 PM
Time D = 2.5 × (55.76)^0.38 = 11.52 months
Staff = 55.76 / 11.52 = 4.84 ≈ 5 persons
Productivity = 20000 / 55.76 = 358.7 LOC per PMEach line shows formula, substitution and unit. Practise this format on GGSIPU BCA important questions.
BCA 108T and the BCA 108P Software Engineering lab (10 practicals), plus other GGSIPU BCA Sem 2 papers
Paired lab: BCA 108P Software Engineering lab notes, 10 practicals, CCP, 1 credit, 100 marks.
The lab leans on Units 1 and 2. Its problem statement, SRS, DFD and UML practicals are the hands-on side of sections 1.15 to 1.20, where the notes already draw a full library system. The Halstead practical applies section 2.6 and its operator and operand rules. Units 3 and 4 stay theory only.
Semester 2 links: BCA 102T Database Management System (DBMS) reuses the ER notation of section 1.19, and BCA 104T Object Oriented Programming using Java turns section 1.18 class diagrams into code. BCA 106T Data Structures and Algorithms, BCA 142T Soft Skills and BCA 192T Environment Studies complete the theory papers. Unit 4 leads into BCA 204T Software Testing in Semester 4.
BCA 108T Software Engineering notes FAQs
How do I get the full BCA 108T notes?
Tap "Get Full Notes" at the top or the WhatsApp button at the end of this page. It opens a chat with our desk with the BCA 108T request already typed in. The notes come only as an 88-page printed book with all 4 units, 40 diagrams and each unit's exam zone; there is no PDF version. Open the sample in the header first to check the layout.
Which BCA 108T unit has the most numericals?
Unit 2. It solves 7 numericals and examples on function points, Halstead counting and measures, Basic and Intermediate COCOMO and risk exposure, then adds 3 practice numericals with answers and a formula sheet. Unit 4 has the other two, boundary value analysis and cyclomatic complexity, with 4 practice problems. Units 1 and 3 are diagram and theory based.
What is the passing mark for BCA 108T?
BCA 108T is marked out of 100: 40 internal and 60 in the end-term exam, as Table 7 of the BCA scheme of examination shows. The scheme does not print a separate pass percentage for this theory paper. End-term minimums, grading and re-appear rules come from Ordinance 11 of the university, which the scheme cites, so check it on ipu.ac.in or ask your college.
The BCA 108T syllabus says "Perceptive maintenance". Is that a different type?
No. Section 4.13 of the notes explains that the syllabus writes "Perceptive" while standard texts use Perfective maintenance: changes that add features or improve performance and usability at the user's request. The notes advise writing "Perfective" in the exam. The other three types, corrective, adaptive and preventive maintenance, match the syllabus wording exactly as printed.
Do the BCA 108T notes follow the syllabus for the 2024-25 batch?
Yes. They follow the BCA syllabus and scheme for the batch admitted in 2024-25 onwards, where BCA 108T is a 4-credit core theory paper in Semester 2. Every official topic, from FAST and QFD in Unit 1 to the maintenance process in Unit 4, has its own numbered section, as the syllabus map on this page shows.
How are BCA 108T and BCA 108P different?
BCA 108T is the 4-credit theory paper with a written end-term exam on four units. BCA 108P is the 1-credit lab, where you prepare a problem statement, an SRS, DFDs, UML diagrams and Halstead metrics for a system. The theory notes explain each of those on a library system, so they are the reading base; the lab notes cover the practical work itself.
Get the full BCA 108T Software Engineering Notes on WhatsApp
These notes are sold only as a printed book; they are not available as a PDF. Order the book on WhatsApp. It is the complete Software Engineering notes in English.
| Part | Pages | Highlights |
|---|---|---|
| Cover and index | 4 | Topic index |
| Unit 1 | 25 | 14 figures, library case study |
| Unit 2 | 20 | 7 solved numericals, formula sheet |
| Unit 3 | 20 | 9 figures, cohesion and coupling scales |
| Unit 4 | 19 | BVA and cyclomatic solved problems |
Pages in the printed BCA 108T notes book, by unit
- Part
- Cover and index
- Pages
- 4
- Highlights
- Topic index
- Part
- Unit 1
- Pages
- 25
- Highlights
- 14 figures, library case study
- Part
- Unit 2
- Pages
- 20
- Highlights
- 7 solved numericals, formula sheet
- Part
- Unit 3
- Pages
- 20
- Highlights
- 9 figures, cohesion and coupling scales
- Part
- Unit 4
- Pages
- 19
- Highlights
- BVA and cyclomatic solved problems
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Ready for the full notes?
Discuss coverage and delivery with our team.