Anna University Model Question Paper BE IV sem IT SOFTWARE ENGINEERING
B.Tech. DEGREE EXAMINATION.
IF 255 — SOFTWARE ENGINEERING
Time : Three hours Maximum : 100 marks
Answer ALL questions.
PART A — (10 ´ 2 = 20 marks)
- Justify the term ‘‘Software is Engineered’’.
- Distinguish between process, methods, tools.
- Define software scope.
- Define process maturity. Indicate different process maturity levels of CMM/SEI.
- Give an example of a design fault that leads to failure.
- Distinguish between alpha testing and beta testing.
- What is Software Architecture?
- Define Software re–engineering.
- What is meant by software change?
- Write short notes on estimation models.
PART B — (5 ´ 16 = 80 marks)
- (i) Discuss in detail the FAST method of requirement gathering with an illustration.
(ii) Discuss in detail the Quality Function deployment.
- (a) List several software process paradigms. Explain how both waterfall model and prototyping model can be accommodated in the spiral process model.
(b) (i) Discuss in detail the data modeling activity.
(ii) Write briefly about the utility of state transition diagram in analysis modeling activity.
- (a) (i) Describe the design process in software development.
(ii) What are the characteristics and criteria for design?
(b) (i) What are different activities in user interface design process? Elaborate each of these activities.
(ii) Describe your approach to ‘‘user help’’ facilities which integrate with error messages.
- (a) (i) Discuss the differences between black box and white box testing models. Discuss how these testing models may be used together to test a program module.
(ii) Discuss the importance of cyclomatic complexity with an illustration.
(b) (i) Justify the statement ‘‘Software maintenance is costlier’’.
(ii) Discuss the concept of maintenance process with neat block diagram.
- (a) Explain clearly the concepts of coupling and cohesion. Are there some systems that cannot be made functionally cohesive? Why or why not?
(b) Write short notes on the following :
(i) System Software.
(ii) Functional decomposition.
(iii) Structured constructs.
(iv) CASE Tool.