Scribd
Upload
65 views2 pages

Oose Questions Set

The document outlines the practical examination for the B.E/B.Tech sixth semester course on Object Oriented Software Engineering, scheduled for April-May 2024. It includes a series of tasks such as identifying a software system, documenting its requirements, developing use case models, and implementing and testing the system. The exam is structured to assess students' understanding of software engineering principles and their application in real-world scenarios.

Uploaded by

examcell9615
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
65 views2 pages

Oose Questions Set

The document outlines the practical examination for the B.E/B.Tech sixth semester course on Object Oriented Software Engineering, scheduled for April-May 2024. It includes a series of tasks such as identifying a software system, documenting its requirements, developing use case models, and implementing and testing the system. The exam is structured to assess students' understanding of software engineering principles and their application in real-world scenarios.

Uploaded by

examcell9615
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

B.E / B.Tech.

PRACTICAL END SEMESTER EXAMINATIONS,


APRIL MAY 2024
Sixth semester

CCS356 OBJECT ORIENTED SOFTWARE ENGINEERING

(Regulations 2021)

Time : 3 Hours Answer any one Question Max. Marks 100

Aim/ Program/ Results Viva-Voce Record Total


Procedure Drawing
20 30 30 10 10 100

1. Identify a software system that needs to be developed.

2. Document the Software Requirements Specification (SRS) for the identified


system.

3. Identify use cases and develop the Use Case model.

4. Identify the conceptual classes and develop a Domain Model and


also derive a Class Diagram from that.

5. Using the identified scenarios, find the interaction between objects and
represent them using UML Sequence and Collaboration Diagrams

6. Draw relevant State Chart and Activity Diagrams for the same system.

7. Implement the system as per the detailed design

8. Test the software system for all the scenarios identified as per the use case
diagram
9. Improve the reusability and maintainability of the software system by
applying appropriate design patterns

10.Implement the modified system and test it for various scenarios.

INTERNAL EXAMINER EXTERNAL


EXAMINER

You might also like