Scribd
Upload
3 views3 pages

Software Engineering Answers

The document contains exam answers for a Software Engineering course (CS-232) covering various topics such as software development models, design principles, and UML diagrams. Key concepts include the Spiral Model, Agile methodologies, and the importance of use case and activity diagrams. It also discusses negotiation, cohesion and coupling, and the differences between structured and unstructured interviews.

Uploaded by

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

Software Engineering Answers

The document contains exam answers for a Software Engineering course (CS-232) covering various topics such as software development models, design principles, and UML diagrams. Key concepts include the Spiral Model, Agile methodologies, and the importance of use case and activity diagrams. It also discusses negotiation, cohesion and coupling, and the differences between structured and unstructured interviews.

Uploaded by

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

**Software Engineering Exam Answers (CS-232)**

Q1) Attempt any Eight:

a) Activities of Spiral Model:

- Objective setting

- Risk assessment & reduction

- Development & validation

- Planning for next iteration

b) Class & Object:

- Class: Blueprint of objects.

- Object: Instance of class.

c) ASD stands for:

- Adaptive Software Development.

d) Define Agile:

- Agile is an iterative and incremental software development approach emphasizing flexibility and
customer collaboration.

e) Symbol of Component:

- A rectangle with two small rectangles on the left side.

f) Two key XP activities:

- Pair programming

- Continuous integration

g) Design notation justification:

- Design notations represent system components symbolically for clarity, communication, and
documentation.

h) Structural analysis:

- A method focusing on system functions, data flow, and process decomposition.

i) Pattern:

- A reusable solution to a commonly occurring software design problem.

j) Deployment diagram notations:


- Nodes, artifacts, dependencies.

----------------------------------------------------------

Q2) Attempt any Four:

a) Negotiation:

- Discussion between stakeholders to agree on requirements.

b) Cohesion & Coupling:

- Cohesion: Degree to which module elements belong together.

- Coupling: Degree of dependency between modules.

c) Purpose of Use Case Diagram:

- Represents system interactions with external actors.

d) Concurrent Deployment Model:

- Manages parallel execution of multiple processes in software development.

e) Activity Diagram Elements:

- Initial node, activities, decision node, merge, fork, join, final node.

----------------------------------------------------------

Q3) Attempt any Two:

a) Structure vs Unstructured Interviews:

- Structured: Predefined questions.

- Unstructured: Open-ended, conversational.

b) Sequence Diagram for Student Registration:

- Student → Registration System → Database interactions sequence.

c) Umbrella Activities:

- Project tracking, configuration management, QA, risk management.

----------------------------------------------------------

Q4) Attempt any Two:


a) RAD Model:

- Rapid Application Development uses prototyping + iterative delivery.

b) Agile Process Model:

- Lightweight model based on iterative development and customer collaboration.

c) SRS Definition:

- A document describing functional & non-functional requirements of software.

----------------------------------------------------------

Q5) Attempt any One:

a) UML Class Diagram for Railway Reservation:

- Classes: Train, Passenger, Ticket, Payment, Reservation.

b) Types of Design Classes:

- Entity classes

- Boundary classes

- Controller classes

You might also like