SA-21/06, C-11, Asapur, Varanasi, UP support@kamaldnp.com +91 8318013442
BTEUP Syllabus

Software Engineering — BTEUP Information Technology 3rd Semester Syllabus 2026-27

KAMALDNP Raj Kamal
November 19, 2026
11 Min Read
Software Engineering — BTEUP Information Technology 3rd Semester Syllabus 2026-27

Software Engineering — What This Subject Is About

Every unit in this subject carries the same 20% — there is no heavy unit and no light unit — and the subject itself is unusual: it is a practicum (3 lecture and 2 practical periods a week) that still has a 60-mark theory paper. Software Engineering is the subject that teaches you to build software the planned way: understand what is wanted, write it down, design it, and then test it — instead of starting to code and hoping.

The subject covers five units in 42 periods: an introduction to software engineering; software life cycle models; planning, requirement analysis and specification; design and implementation; and testing and maintenance. The theory paper is 60 marks external in 3 hours, with 40 internal marks, and each unit from Unit 2 onwards has a practical exercise: comparing models, writing an SRS, drawing DFDs, and using testing tools.

Subject 3.3 (Practicum) • Total 100 Marks • 4 Credits • L 3 – P 2 • 3rd Semester — Information Technology • Session 2026–27

Software Engineering syllabus — life cycle models, SRS, design and testing, BTEUP IT 3rd semester 2026-27
Software built the planned way — Software Engineering is where you learn to plan, design and test before a line of code is written.

What You Will Study

Unit 1 — Introduction to Software Engineering (8 Periods, 20%)

System concepts: types of systems (open, closed, static and dynamic systems). Basics of software engineering: need for software engineering — definition, programs vs software products, software characteristics.

What software engineering is and why it exists — the kinds of systems software works in, and how a software product differs from a single program.

Unit 2 — Software Life Cycle Models (8 Periods, 20%)

Requirement of life cycle model, classic waterfall model, prototyping model, evolutionary model, spiral model, introduction to agile methodology.

Practical exercise: Perform comparative analysis of various models.

The different ways a software project can be organised from start to finish — waterfall, prototyping, evolutionary, spiral — and an introduction to agile, with their strengths and weaknesses compared.

Unit 3 — Software Planning, Requirement Analysis and Specification (10 Periods, 20%)

Requirement gathering and analysis, Software Requirement Specifications (SRS), characteristics of good SRS. Metrics for project size estimation — LOC (Lines of Code), Function Point Metric. Project estimation techniques — using COCOMO model. Responsibilities of Software Project Manager.

Practical exercise: Develop an SRS on a given topic/project/problem.

How a project is planned before a line of code is written — gathering requirements, writing them down as an SRS, and estimating size and effort with LOC, function points and COCOMO.

Unit 4 — Software Design and Implementation (8 Periods, 20%)

Characteristics and features of good software design, cohesion and coupling. Software design approaches — function-oriented design (data flow diagrams, data dictionary, decision trees and tables), object-oriented design. Structured coding techniques, coding styles, and documentation.

Practical exercise: Develop DFD model (level 0 and level 1 DFD) of the problem.

How a design is drawn before it is coded — data flow diagrams, cohesion and coupling, function-oriented vs object-oriented design, and the coding styles that keep code readable.

Unit 5 — Software Testing and Maintenance (8 Periods, 20%)

Concept of testing, unit testing, black box testing, white box testing, alpha, beta testing, integration testing, system testing, testing type cycle (V-Model), verification vs validation, configuration management, overview of test cases.

Practical exercise: Use of testing tools such as JMeter, Canoo WebTest. Write test cases for any known application.

How software is checked before it is delivered — unit, integration and system testing, black box vs white box, the V-Model, and writing test cases; plus configuration management, which keeps track of every version.

Complete Syllabus

The full examination scheme, the unit-wise marks distribution and the reference books from the official syllabus. The unit-wise topics are in the “What You Will Study” section above.

Examination Scheme

CodePaperTypeL – PCreditsInternalExternalTotal
3.3Software EngineeringPracticum3 – 24Theory 40Theory 60 (3 hrs)100
Software Engineering Total44060100

Units at a Glance

UnitTopicPeriodsMarks (%)
1Introduction to Software Engineering820
2Software Life Cycle Models820
3Software Planning, Requirement Analysis and Specification1020
4Software Design and Implementation820
5Software Testing and Maintenance820
Total42100

Total: 42 periods, 100%. The percentages are the suggested distribution of marks in the official syllabus, out of the 60-mark external theory paper. All five units carry the same 20%, so no unit can be skipped.

Course Outcomes

  • CO1: Understand the basic concepts of software development.
  • CO2: Classify life cycle models and their comparison.
  • CO3: Will be able to write the SRS for the given problem and project planning estimation techniques.
  • CO4: Explain various software design strategies.
  • CO5: Explain about different testing methods, need for testing.

Reference Books

As listed in the syllabus:

  • Software Engineering — Rajib Mall, PHI Publishers, New Delhi.
  • An Integrated Approach to Software Engineering — Pankaj Jalote, Narosa Publishing House Pvt. Ltd., Darya Ganj, New Delhi 110002.
  • Software Engineering — Sangeeta Sabharwal, New Age International, Delhi.
  • Software Engineering — Priyam Tayal, Pawan Kumar Gupta and Pradyumna Kumar, Asian Publishers, Muzaffarnagar. ISBN: 978-93-91541-85-9.
  • Software Engineering — K. K. Aggarwal and Yogesh Singh.
  • Software Engineering: A Practitioner’s Approach — R. S. Pressman, Tata McGraw Hill Publishers, New Delhi.

How to Prepare for Software Engineering

Compare the life cycle models in one table. Waterfall, prototyping, evolutionary, spiral, agile — make one table with a column for each model and rows for how it works, when it suits, and what goes wrong with it. The practical exercise for Unit 2 is exactly this comparison, and the theory paper asks for it too. A table you have made yourself is easier to reproduce in the exam than five separate paragraphs.

Write a real SRS, not a summary of one. Unit 3 gives you the practical exercise of developing an SRS on a given topic — do it properly, for a real small system like a library or a canteen. A good SRS has functional requirements, non-functional requirements, and acceptance criteria; writing one teaches you what each of those means far better than reading definitions.

Do the estimation numericals by hand. LOC, function points and COCOMO are the only numericals in this paper, and they are the most scoring questions in it: the method is fixed, the arithmetic is simple, and every correct step earns marks. Practise one function-point count and one COCOMO estimate until the formulas feel automatic.

Draw DFDs level by level. Level 0 first — one process, the external entities, the data flows — then explode it into level 1. The commonest DFD mistake is mixing the levels: a level 0 diagram with level 1 detail in it. Keep the levels separate and the data dictionary will write itself.

Finish with timed practice. Work through model papers in one sitting of 3 hours, without notes — exactly like the real examination. Then compare your answers with the model answer outline and note the points you missed. Questions that repeat across sets are the subject's most important questions.

Exam Tips

  • Attempt all five questions. The paper pattern gives three parts (a), (b) and (c) in each question, of which any two are to be answered — pick the two parts you know best in every question, and do not leave any question blank.
  • Show your working in estimation numericals. Write the formula, substitute the numbers, and show each step of a function-point count or a COCOMO estimate. Examiners give marks for the correct method even if the last number slips.
  • Draw DFDs with the levels labelled. Write “Level 0” or “Level 1” on the diagram and keep the level 0 diagram to one process. An unlabelled DFD that mixes levels earns little.
  • Learn the differences as pairs. Verification vs validation, black box vs white box testing, cohesion vs coupling, alpha vs beta testing — this paper loves “differentiate” questions, and a two-column comparison is the fastest way to answer them.
  • Manage the 3 hours. About 35 minutes per question leaves a few minutes at the end to re-read your answers. Do not spend an hour on one favourite question.
  • Write in your own words, in the same order as the questions. Short, clear points with the key terms score better than long copied paragraphs.

Frequently Asked Questions

How many marks is Software Engineering worth in the 3rd semester?
100 marks in total and 4 credits. Although it is a practicum (3 lecture + 2 practical periods a week), it has a theory external: internal assessment 40 marks (theory) and external theory paper 60 marks in 3 hours.

Which units carry the most marks in Software Engineering?
All five units carry the same 20% each — there is no heavy unit and no light unit. Unit 3 gets slightly more teaching time (10 periods) than the others (8 periods each). The complete unit-wise table is in the Complete Syllabus section above.

What are the practical exercises in Software Engineering?
Unit 2: comparative analysis of the life cycle models. Unit 3: develop an SRS on a given topic. Unit 4: develop a DFD model (level 0 and level 1) of the problem. Unit 5: use testing tools such as JMeter and Canoo WebTest, and write test cases for any known application.

What are the most scoring topics in Software Engineering?
The estimation numericals — LOC, function points and COCOMO — are the most scoring, because the method is fixed and every correct step earns marks. Well-drawn DFDs (level 0 and level 1) and a well-structured SRS are the next best scorers.

Which books should I refer to for Software Engineering?
The syllabus lists 6 books, including Software Engineering by Rajib Mall and Software Engineering: A Practitioner's Approach by R. S. Pressman. The full list is in the Complete Syllabus section above.

What is the paper pattern for Software Engineering?
The board's last published pattern is 5 questions with three parts (a), (b) and (c) each, of which any two parts are to be answered per question. The 2026-27 format has not been published separately, so prepare on this pattern and confirm with your polytechnic.

How can I download the Software Engineering syllabus PDF?
The PDF is free to download — use the download link in the Download section below. It is prepared by KAMALDNP from the official BTEUP syllabus.

Related Syllabus Posts

Notes, Question Bank & Practice Sets — Software Engineering

The syllabus PDF on this page stays 100% FREE — no login, no payment, always. The study material below is a paid KAMALDNP product: buy once for just ₹10 and you get both the Hindi and English PDFs. Every PDF is generated with your name and enrolment number and is password-locked, so it remains personal to you. After purchase, the PDF is also sent to your email, and it is always available for download on the My Downloads page.

Short Notes (English + Hindi) — ₹10

Unit-wise short revision notes prepared from the official BTEUP 2026-27 syllabus of this subject.

Buy / Download — My Downloads
Question Bank (English + Hindi) — ₹10

One original practice (model) paper with a model-answer outline. This is a KAMALDNP practice paper — NOT a BTEUP board paper, and no question in it is promised to appear in your exam.

Buy / Download — My Downloads
Practice Sets (English + Hindi) — ₹10

10 Practice Sets — practice/guess sets only (no verified previous-year board papers available for this subject yet)

Buy / Download — My Downloads

Already purchased? You will find the Download button on the same My Downloads page — you will not be charged again.

Download the Software Engineering Syllabus PDF

Download the complete Software Engineering syllabus PDF below — prepared by KAMALDNP, with the full topic list, examination scheme and reference books.

Download the Software Engineering Syllabus PDF

Source: BTEUP IRDT Kanpur NEP-2020 curriculum for Diploma in Information Technology, effective session 2026-27 (urise.up.gov.in). Topic lists follow the official syllabus; short explanations are the author's own plain-English summaries, not syllabus text. Please confirm with your own polytechnic for any local changes.

Comments (0)

Share your question or experience about this syllabus. Your comment will appear after review.

No comments yet — be the first to share your thoughts!

🤖 KAMALDNP AI Assistant

Ask about courses, website & more

Hi! I'm KAMALDNP AI Assistant. Ask me about our courses, website features, or anything else! 😊
Please wait 5s...
🤖 KAMALDNP Assistant ✕

Request human callback:

🔐 Login Required
✕

Please log in to download. You will stay on this page after logging in!

New here? Register now →