Key takeaways
- SDLC models, cohesion and coupling, COCOMO, function points and cyclomatic complexity carry most marks.
- Draw DFDs and UML diagrams neatly; they earn marks on their own.
- Each section has exam tips and formula boxes, and the last page lists the most asked practice questions.
- These are original Uncodemy revision notes, not official university notes; check your own syllabus.
About these Software Engineering handwritten notes
This page offers Uncodemy's Software Engineering notes as a free handwritten-style PDF. Software Engineering is the disciplined way to plan, build, test and maintain software so it is delivered on time and works as required. The notes are written in short points with neat tables, labelled diagrams, boxed formulas and exam tips, so you can revise a full unit in one sitting instead of reading a long textbook chapter.
Please note: these are original Uncodemy revision notes. They follow the common syllabus that most Indian universities share for this subject, but they are not official university notes. Check your own university syllabus and add anything it lists that is missing here.
What's inside the Software Engineering notes
The PDF is arranged in 8 sections plus a final page of most asked practice questions. The sections follow the usual unit order of a Software Engineering syllabus, so you can map them to your own units quickly. Here is what each section covers.
Introduction
Characteristics of software, the software crisis and the layers of software engineering.
Software process models
Waterfall, iterative, prototyping, spiral and V-model compared, and Agile basics such as Scrum.
Requirement engineering
Requirement elicitation and analysis, functional vs non-functional requirements, the SRS and its qualities, and analysis models such as DFDs and ER diagrams.
Software design
Design principles, types of cohesion and coupling, function-oriented and object-oriented design, and UML diagrams.
Software metrics and estimation
LOC and function point size metrics, McCabe's cyclomatic complexity and basic COCOMO.
Software testing
Black-box and white-box testing, and unit, integration, system and acceptance testing levels.
Maintenance and quality
Corrective, adaptive, perfective and preventive maintenance, software quality and reliability, and CMM levels.
Project management and risk
Project planning and scheduling, risk identification and management.
Most asked questions (practice)
Ten exam-style questions, from comparing SDLC models to CMM levels.
How to use handwritten notes to revise Software Engineering
Software Engineering answers need structure: definitions, a diagram and a comparison. Use the tables and diagrams in the notes as the frame for each answer.
- Make one comparison table of Waterfall, Spiral, Prototyping and Agile on when to use, risk and customer involvement.
- Draw level 0 and level 1 DFDs for a library system from memory.
- Solve one basic COCOMO problem for each mode: organic, semi-detached and embedded.
- Compute function points and cyclomatic complexity for one example each.
A simple three-pass method works well with handwritten notes. In the first pass, read one section and underline only what you do not already know. In the second pass, close the notes and write the definitions, diagrams and steps for that section on a blank sheet, then compare and correct in a different colour. In the third pass, a day or two later, answer two or three exam-style Software Engineering questions in timed conditions using only memory. Add your own examples and doubts in the margins so the PDF becomes your personal revision copy.
Formulas, diagrams and definitions to memorise
- Basic COCOMO: Effort = a (KLOC)^b person-months and Time = c (Effort)^d months, with constants for organic, semi-detached and embedded modes.
- Function points: FP = UFP x (0.65 + 0.01 x sum of the 14 adjustment factors).
- Cyclomatic complexity: V(G) = E - N + 2 = number of decisions + 1 = number of regions.
- Cohesion from best to worst (functional to coincidental) and coupling from best to worst (data to content).
- The four maintenance types and the five CMM levels.
Common mistakes that cost marks
- Saying high coupling is good; the goal is high cohesion and low coupling.
- Using the wrong COCOMO constants for the project mode given in the question.
- Drawing a DFD with control flow or loops, which belong in a flowchart.
- Listing SDLC models without saying when each one should be used.
Exam focus: Software Engineering topics that carry the most marks
These Software Engineering topics carry the most marks in most university papers.
- SDLC models and Agile.
- Requirements, SRS and DFDs.
- Cohesion and coupling, and UML diagrams.
- COCOMO, function points, cyclomatic complexity, testing levels and maintenance.
Typical long questions
- Compare Waterfall, Spiral, Prototyping and Agile models.
- Differentiate functional and non-functional requirements and list the qualities of a good SRS.
- Draw level 0 and level 1 DFDs for a library system.
- Explain the types of cohesion and coupling with examples.
- Calculate effort and development time using basic COCOMO.
- Compute function points for given counts and adjustment factors.
- Explain the types of software maintenance and the CMM levels.
Marks per question change between universities and years, so confirm the pattern on a recent official paper. In long answers, start with a definition, add a labelled diagram or table, explain the steps and finish with an example or comparison. Underline the key term in each answer and leave a line between steps, because examiners mark faster when the structure is easy to see.
A 7-day revision plan for Software Engineering
- Day 1: Introduction, Software process models.
- Day 2: Requirement engineering, Software design.
- Day 3: Software metrics and estimation, Software testing.
- Day 4: Maintenance and quality.
- Day 5: Project management and risk.
- Day 6: redo the numericals and diagrams: COCOMO, function points, cyclomatic complexity, one DFD and one UML class diagram.
- Day 7: answer the most asked practice questions at the end of the notes from memory, then solve one official previous year paper in three hours and mark the units that cost you time.
Keep a single sheet of formulas, definitions and diagrams from the notes for the last hour before the exam, and do not start new topics on the final day.
Who these notes are for
- B.Tech CSE and IT students preparing for the semester Software Engineering exam.
- BCA and MCA students with a software engineering paper.
- Students writing a project report who need SDLC, SRS and UML basics.
- Freshers revising SDLC and Agile before developer or testing interviews.
The notes are a revision aid, not a first textbook. If a Software Engineering topic is new to you, learn it from your prescribed book or class lectures first, then come back to the notes to compress and revise it. For practice, pair them with the Software Engineering Important Questions PDF page and your university's official previous year papers. If your syllabus has a topic that is not covered here, you can ask for it through the handwritten notes request page linked below.
Download Software Engineering Handwritten Notes PDF
Software Engineering Handwritten Notes PDF (Free)
The PDF carries the same content as this page in a clean, print-ready layout, so you can read it offline and keep it for revision.
7 pages · 260 KB · PDF · Updated 5 Nov 2026