Which units to study in SW Engineering

Software Engineering is by far the most dry subject in engineering, so many similar terms and only theory makes it very boring to study and more importantly score those 35 marks, just hoping that you would have the required 15 in internals :). (At least by our teacher's grace ;) ).

The key to score marks in Software Engineering is try NOT TO remember text the way it is in textbook, but to understand some part of it(yeah, some part, not all :) ) and try to write those keywords which conveys a lot to the evaluator.

So, lets get started.
                                                  PART-A

1: OVERVIEW

This unit is more like an introduction and has many questions directly given in the Q&A format itself. You will get an idea of how dry the rest of the subject is as you start from this chapter. 

So, considering that there wouldn't be much to mug up, I feel this chapter should be studied.

3: REQUIREMENTS:
This unit is a life-saver, it is really used everyday if you become a Software Engineer. In fact, a common scenario is that, you would be given a task to do at work, you may be asked to give in your estimate(approximate idea of when you can finish it). It always help to understand the requirement well before giving in an estimate. It is something that you can understand well and hence can be picked for exams.

4. System models, Project Management:
The best part about this unit is the Activity Networks and Bar Chart related problems in Project Mgmt, this are really easy to solve and if they come in exams, you can score 10 marks for sure(now, we all know the value of easily scorable 10 marks :P). The System Models have topics which are also explained in more detail in other subjects like (State machine models in FAFL, Inheritance in OOMD(this is in final year) ).

This is all for Part-A, watch out this page for PART-B :).