munotes®

B.Sc. (Information Technology) Problem Solving Using Computer Syllabus - Mumbai University 2026

MU B.Sc. (Information Technology) student group Free to join

This is the FY BSc IT syllabus under NEP 2020, in force from the academic year 2024-25. The University still sets the earlier Choice Based papers alongside it for ATKT candidates, so check which scheme your exam form names before you revise.

Problem Solving Using Computer Syllabus.pdf
Minor · Semester 2 · FY BSc IT · 2 credits · 50 marks

Loading syllabus...

Syllabus for Problem Solving Using Computer

Minor · Semester 2 · FY BSc IT · 2 credits · 50 marks

This is a paper of the Information Technology Minor, for students whose college runs that Minor. In Semester 2 you sit one of these: Problem Solving Using Computer, or Fundamentals of Python Programming. From 2026-27 your college sets and marks Minor papers itself.

Module I

  • 1 Computational Thinking: Objectives, What is it? How is it used? Disclaimers
  • 2 Logical and Algorithmic thinking: Objectives, Approach, Logical thinking, Algorithmic thinking, ‘Gotchas’
  • 3 Problem Solving and Decomposition: Objectives, Where to start? Defining a problem, devising solution, decomposition, other effective strategies, patterns and generalization
  • 4 Abstraction and Modelling: Objectives, Abstraction, Modelling
  • 5 Anticipating and dealing with errors: Objectives, coming to terms with bugs, Designing out the bugs, Mitigating errors, Testing, Debugging, deciding which errors to fix
  • 6 Evaluation a solution: Objectives, Solution evaluation, Is it correct? Is it efficient? Is it elegant? Is it usable? Trade-offs

Module II

  • 7. Introducing Python: Objectives, Introduction, First steps, Basic types, Basic operations, Function, Comments 8. Effective Building Blocks: Logic, Basic arithmetic constructs, Program state, Advanced constructs 9. Organising Code: Objectives, tkinter, Separating concerns, defining information scope, using modules, packages 10. Using abstractions and patterns: Objectives, finding patterns in programs, abstractions in programming, built-in types, creating own types, ready-made patterns 11. Effective modelling: Objectives, entities, relationships, processes, usage, modelling tips 12. Testing and evaluation programs: Objectives, introduction, anticipating bugs, verification and validation, testing in parts, testing the whole, debugging 13. Example

Text and References

  • 1 COMPUTATIONAL THINKING: A beginner’s guide to problem-solving and programming, Karl Beecher, BCS Learning & Development Ltd, 2017
  • 2 Problem Solving with Computers, Greg W. Scragg, Jones and Barlett Publishers, 1997

Reproduced from the University of Mumbai syllabus for B.Sc. (Information Technology) under NEP 2020, in force from the academic year 2024-25. Wording is as printed in that syllabus. Module numbering is as printed there too.

The complete syllabus

This subject is cut from the University circular for its year. Open a document here if you want the whole thing rather than a single subject.

PDF BSc IT SEM I & II (2024 25) NEP NEP 2020 syllabus, in force from 2024-25 Read full PDF Read
PDF BSc IT Minor SEM - II Problem Solving Using Computer (2024-25) NEP NEP 2020 syllabus, in force from 2024-25 Read full PDF Read
PDF BSc IT Minor SEM - II Fundamentals of Python Programming (2024-25) NEP NEP 2020 syllabus, in force from 2024-25 Read full PDF Read
PDF BSc IT Minor SEM - V & VI (2026-27) NEP NEP 2020 syllabus, in force from 2026-27 Read full PDF Read
PDF BSc IT V & VI 2024 25 Earlier Choice Based syllabus, still set for ATKT candidates Read full PDF Read
PDF SY BSc IT 23 24 Earlier Choice Based syllabus, still set for ATKT candidates Read full PDF Read
BSc IT Syllabus Study Path
Start with the year folder.
Use FYBSc IT, SYBSc IT, or TYBSc IT first so your syllabus check matches the semester you are preparing for.
Check units before opening notes.
Use the syllabus to confirm topics, then open BSc IT notes for the same semester.
Practice after the syllabus check.
Move to BSc IT question papers after reviewing the module scope.
Issue
Done!