JNTU MCA 2021 OBJECT ORIENTED ANALYSIS AND DESIGN USING UML Previous Question Paper (July/August - 2021 - R17)

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

The standard phases of the SDLC are as follows:

1. Requirement Analysis: The most important phase where senior team members gather requirements from the customer to define the scope and feasibility of the project.
2. Feasibility Study: Assessing whether the project is technically, operationally, and economically viable.
3. Design: Architects create the Software Design Document (SDD), specifying system architecture, data flow, and interface design based on the requirements.
4. Coding (Implementation): Developers write the actual code based on the design documents using a chosen programming language.
5. Testing: Quality assurance teams test the software to identify defects, bugs, and ensure the product meets the initial requirements.
6. Deployment: The software is released to the production environment for user access.
7. Maintenance: Ongoing support, updates, and bug fixes are provided to ensure the software continues to function correctly in a changing environment.

The SDLC process follows a cyclical flow represented as: Requirement Analysis → Feasibility Study → Design → Coding → Testing → Deployment → Maintenance, with feedback loops returning to earlier phases if issues are identified.

UML diagrams are categorized into structural and behavioural types. Structural diagrams represent the static architecture of a system, while behavioural diagrams illustrate the dynamic aspects and interactions.

Structural Diagrams:

1. Class Diagram: This is the most common structural diagram. It depicts the system's static structure by showing classes, their attributes, methods, and the relationships between them (such as inheritance, association, and aggregation). It provides a blueprint for the system implementation.
2. Component Diagram: This diagram describes the organization and wiring of the physical components in a system. It shows how software components (such as source code files, libraries, or executables) are structured and their dependencies, helping to manage system complexity and modularity.

Behavioural Diagrams:

1. Use Case Diagram: This diagram captures the functional requirements of a system. It illustrates the interactions between actors (users or external systems) and the system's use cases (specific goals or tasks). It is essential for defining the system scope and user expectations.
2. Sequence Diagram: This is an interaction diagram that shows how objects communicate with each other over time. It emphasizes the time-ordering of messages exchanged between objects to perform a specific function, providing a clear view of the flow of control within a use case.