JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY HYDERABAD MCA 2020 OBJECT ORIENTED ANALYSIS AND DESIGN USING UML Previous Question Paper (October/ November - 2020 - R17)

Things are the basic building blocks in the Unified Modeling Language (UML). They represent the vocabulary of the language and are categorized into four distinct types, each serving a specific purpose in modeling a system.

1. Structural Things: These are the nouns of UML models, representing the static parts of a system, whether conceptual or physical.

• Class: Represented by a rectangle divided into three compartments (name, attributes, operations).
• Interface: Represented by a circle or a rectangle with the stereotype «interface».
• Collaboration: Represented by an ellipse with dashed lines.
• Use Case: Represented by an ellipse.
• Component: Represented by a rectangle with two small rectangles protruding from the side.
• Node: Represented by a 3D cube.

2. Behavioral Things: These are the dynamic parts of UML models, representing the behavior of the system over time and space.

• Interaction: Represented by a directed line connecting two objects, often with a message name.
• State Machine: Represented by a rounded rectangle containing states and transitions.

3. Grouping Things: These are the organizational parts of UML models, used to divide the model into smaller, manageable units.

• Package: Represented by a tabbed folder icon.

4. Annotational Things: These are the explanatory parts of UML models, used to add comments, descriptions, or constraints to the model.

• Note: Represented by a rectangle with a folded top-right corner, connected to the element it describes by a dashed line.

The Software Development Life Cycle (SDLC) is a structured process used by software organizations to develop, design, test, and deploy high-quality software. It aims to produce software that meets or exceeds customer expectations within specified time and cost estimates.

The standard phases of the SDLC are as follows:

1. Requirement Analysis: This is the most critical phase where business analysts and project managers gather requirements from stakeholders to define the scope, objectives, and constraints of the project. The output is typically a Software Requirement Specification (SRS) document.
2. System Design: Based on the SRS, architects define the system architecture, data flow, database design, and user interfaces. This phase results in a Design Document Specification (DDS) that guides developers.
3. Implementation (Coding): Developers write the actual code based on the design specifications. This is the longest phase where the software is built according to coding standards and programming languages.
4. Testing: The developed software is rigorously tested to identify bugs, defects, or gaps in requirements. Various testing methods like unit testing, integration testing, and system testing are performed to ensure quality.
5. Deployment: Once the software is tested and certified, it is released to the production environment or delivered to the client.
6. Maintenance: After deployment, the software enters the maintenance phase where developers address user feedback, fix newly discovered bugs, and perform necessary updates or enhancements to keep the system functional and relevant.

Common SDLC models include the Waterfall Model (linear and sequential), the Agile Model (iterative and incremental), and the Spiral Model (risk-driven), each chosen based on project size, complexity, and client requirements.