M.E DEGREE EXAMINATION, JANUARY 2010

First Semester

Software Engineering

SE9213 – OBJECT ORIENTED SOFTWARE ENGINEERING

(Common to M.E. Computer Science and Engineering)

(Regulation 2009)

Time: Three hours Maximum: 100 Marks

Answer all the questions

Part A – (10*2=20 Marks)

1. What are the functional and no functional requirements?

2. What is the difference between a scenario and use case? When do we use each construct?

3. How do you identify the Actor’s in particular system? Give example.

4. What are the requirements in elicitation activities?

5. Define Peer-to-Peer architectural style with diagram.

6. When should we choose an object-oriented database?

7. Who is the person involved in reuse? What are the responsibilities?

8. Give a simple example for contract inheritance.

9. What is NFR framework? Mention its decompositions.

10. What is WBS? Give one example.

Part B – (5*16=80 Marks)

11. (a)(i) How do you manage the software development? Explain its activities (8)

(ii) Draw a class diagram representing the relationship between parents and children.

Take into account that a person can have both a parent and a child. Annotate associations

with roles and multiplicities. (8)

(Or)

(b)(i) What are the types of roles found in a software engineering project? Explain. (8)

(ii) Discuss about unplanned communication and its events in detail. (8)

12. (a)(i) How do you identify Actors and scenarios in a project? Explain. (8)

(ii) Consider a scenario of selecting a file on a floppy, dragging it to folder and

releasing the mouse. Identify and define at least one control object associated with this

scenario. (8)

(Or)

(b)(i) Draw a UML diagram for a Analysis activities. Also brief its various stages. (8)

(ii) Describe the strength and weakness of users and developers during the

requirements elicitation activities. (8)

13. (a)(i) What is coupling and cohesion in system design? Also explain how to reduce the

coupling of subsystems. (8)

(ii) Assume you are developing a system that stores its data on a Unix file system. You

anticipate that you will port future versions of the system to other operating systems that

provide different file system. Propose a subsystem decomposition that anticipates this

change. (8)

(Or)

(b)(i) Discuss mapping of subsystems to processors and components. (8)

(ii) How is communication difficult in system design? Explain. (8)

14. (a)(i) How do you plan for testing? Explain with PERT chart. (8)

(ii) Draw a class diagram representing the application domain facts below, and map it

to a relational schema. (8)

(1) A project involves a number of participants.

(2) Participants can take part in a project either as project manager, team leader or

developer.

(Or)

(b)(i) How do you identify the missing attributes and operations in interface

specification? Explain. (8)

(ii) What is Unit testing? Why it is important in software project? Explain. (8)

15. (a)(i) How do you manage the Rationale? Explain briefly. (8)

(ii) Write a brief note on version identification schemes. (8)

(Or)

(b)(i) Discuss the Task model in the project management. (8)

(ii)Explain simple life cycle with suitable UML activity diagram. (8)