Software Design (Finals)

Question 1

a mechanism to transform user requirements into some suitable
form, which helps the programmer in software coding and implementation.

Answer 1

Software design

Question 2

It deals
with representing the client’s requirement, as described in SRS

Answer 2

Software design

Question 3

Objectives of Software Design

Answer 3

Correctness
Completeness
Efficiency
Flexibility
Consistency
Maintainability

Question 4

are concerned with providing means to handle the complexity of the design process effectively.

Answer 4

Software design principles

Question 4

the goal is to divide the problem into manageable pieces.

Answer 4

Problem Partitioning

Question 4

Two Types of Abstraction

Answer 4

Functional Abstraction
Data Abstraction

Question 4

The Software Design Principles

Answer 4

Problem Partitioning
Abstraction
Modularity
Top-down and Bottom-up Approach

Question 4

achieved by developing
functions that perform only one kind of task and do not excessively interact with other modules.

Answer 4

Functional Independence

Question 4

a tool that enables a designer to consider a component at an
abstract level without bothering about the internal details of the implementation.

Answer 4

Abstraction

Question 4

The details of the algorithm to accomplish the functions are not visible to the
user of the function.
* Functional abstraction forms the basis for Function oriented design approaches.

Answer 4

Functional Abstraction

Question 4

specifies to the division of software into separate modules which are
differently named and addressed and are integrated later on in to obtain the
completely functional software.

Answer 4

Modularity

Question 4

Details of the data elements are not visible to the users of data. It forms the basis for Object Oriented design approaches.

Answer 4

Data Abstraction

Question 4

only property that allows a program to be intellectually manageable.

Answer 4

Modularity

Question 4

It measures the relative function strength of a module.

Answer 4

Cohesion

Question 4

It measures the relative interdependence among modules.

Answer 4

Coupling

Question 4

suggests that modules
can be characterized by the design decisions that protect from the others, i.e., In other words, modules should be specified that data include within a module is inaccessible to other modules that do not need for such information.

Answer 4

Information hiding

Question 4

2 Strategy of Design

Answer 4

Top-down Approach
Bottom-up Approach

Question 4

explains a system’s core ideas and characteristics with respect to its relationships, environment, and other design principles.

Answer 4

Software architecture

Question 4

Additional Software Design Principles

Answer 4

• DRY (Don’t Repeat Yourself)
• Encapsulation Principle
• Principle of Least Astonishment (PoLA)
• You Aren’t Gonna Need It (YAGNI)
• Keep It Simple, Stupid (KISS)

Question 4

Different Architectural Patterns

Answer 4

Event Driven Architecture
Client-Server Architecture
Layered Pattern
Microservices
Monolithic
MV* Pattern

Question 4

• Defines the high-level structure and organization of a software system.
• focus on the system’s macro-level aspects
  and establish a framework for the design and implementation of the entire
  application.

Answer 4

Software Architecture Pattern

Question 5

An older approach where all components of an application are tightly integrated into a single codebase and are deployed together. While less common now, it’s still seen in some legacy systems.

Answer 5

Monolithic

Question 5

Structures applications as a collection of small, independently deployable services, enabling scalability and rapid development. Common in cloud-based systems.

Answer 5

Microservices

Question 5

It is an umbrella term that encompasses variants of this architecture pattern, and they differ in terms of the type and level of coupling between the components.

Answer 5

MV* Pattern

Question 5

They provide tested answers to common design issues, helping developers reduce code structure and improve maintainability.

Answer 5

Design patterns

Question 5

- general, recurring solution to a commonly encountered problem in software design that is utilized in software engineering. - It is not a comprehensive design that can be implemented in code straight immediately.

Answer 5

Design Pattern

Question 5

Types of Design Pattern

Answer 5

Creational Design Patterns Structural Patterns Behavioral Design Patterns

Question 6

* Attempt to generate things in a manner appropriate to the situation. * Are concerned with the generation of objects, ensuring that they are formed in a situationally appropriate manner

Answer 6

Creational Design Patterns

Question 7

*Concerned with object composition, specifying how to combine items to achieve additional functionality * It is a formula for combining many objects and classes to create a larger structure. * It's similar to building a house based on a blueprint.

Answer 7

Structural Patterns

Question 8

These patterns help resolve typical issues with how parts of codeshare work, disguise what they do, and stay organized.

Answer 8

Behavioral Design Patterns

Question 9

A stage where software developers define the technical details of the product.

Answer 9

Design Phase in SDLC

Question 10

All the details about the system design phase are mentioned in this document

Answer 10

software requirement specification document.

Question 11

It includes a brief description and the name of each module.

Answer 11

High-Level Design (HLD)

Question 12

It includes the functional logic of the modules. You have to collect the details of the interface, database tables, and type and size.

Answer 12

Low-Level Design (LLD)

Question 13

Provides business-related information, reviews materials prepared by the team, and approves project milestones.

Answer 13

Client

Question 14

Leads the project and makes decisions to ensure a successful outcome (project organization, task allocation, budget planning, progress monitoring, and others).

Answer 14

Project manager

Question 14

Ensures that the user’s interaction with the product is logical by creating user-centered product interface designs

Answer 14

UX designer

Question 15

Helps clients translate their requirements into product features, create an original code for the product

Answer 15

Software developer

Question 15

Creates product requirements for UX designers and reviews the designs they make

Answer 15

Business analyst

Question 16

basic blueprints that help teams align on requirements, keeping UX design conversations focused and constructive.

Answer 16

Wireframes

Question 16

Involved in analyzing requirements and testing product designs to ensure a lack of performance issues.

Answer 16

Quality assurance (QA) specialist

Question 17

prioritizes speed, so it’s limited in scope—but even a quick mockup can stress-test and improve a product design.

Answer 17

Rapid prototyping

Question 18

Create mock-ups of a design concept or flow, keeping your users’ needs and company’s goals in mind.

Answer 18

Build

Question 19

Test your prototype with target users and key stakeholders to learn whether it meets expectations.

Answer 19

Review

Question 20

Adjust the prototype based on the feedback you receive

Answer 20

Refine

Question 21

It is one of the most common types of architecture in software engineering. Organizes software into horizontal layers, each responsible for distinct functionalities like presentation, business logic, and data storage.

Answer 21

Layered Pattern

Question 22

Separates application into clients (user interfaces) and servers (data processing) to manage data sharing and user interactions. Ideal for distributed systems like web-based services.

Answer 22

Client-Server Architecture

Question 23

Emphasizes communication between components through asynchronous events, triggered by user actions or data changes. Used in real-time systems and graphical user interfaces.

Answer 23

Event Driven Architecture