8

Question 1

is 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 (Software
Requirement Specification) document, into a form, i.e., easily implementable using
programming language.

Answer 2

Software Design

Question 3

6 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. Effectively managing the complexity will
not only reduce the effort needed for design but can also reduce the scope of
introducing errors during design.

Answer 4

Software Design Principles

Question 4

These are recommendations that help you write code that is clear, manageable, and
scalable. These principles give a foundation for developing software systems that are
both robust and responsive to change.

Answer 4

Software Design Principles

Question 5

4 Software Design Principles

Answer 5

Problem Partitioning
Abstraction
Modularity
Top Down & Bottom up Strategy

Question 6

For small problem, we can handle the entire problem at once but for the significant
problem, divide the problems and conquer the problem it means to divide the
problem into smaller pieces so that each piece can be captured separately.

Answer 6

Problem Partitioning

Question 7

• For software design, the goal is to divide the problem into manageable pieces.

Answer 7

Problem Partitioning

Question 8

6 Benefits of Problem Partitioning

Answer 8

• Software is easy to understand
• Software becomes simple
• Software is easy to test
• Software is easy to modify
• Software is easy to maintain
• Software is easy to expand

Question 8

A module is specified by the method it performs.

Answer 8

Functional Abstraction

Question 9

is a tool that enables a designer to consider a component at an
abstract level without bothering about the internal details of the implementation.
Abstraction can be used for existing element as well as the component being
designed.

Answer 9

Abstraction

Question 9

two common abstraction mechanisms:

Answer 9

Functional Abstraction
Data Abstraction

Question 10

The details of the algorithm to accomplish the functions are not visible to the
user of the function.

Answer 10

Functional Abstraction

Question 11

forms the basis for Function oriented design approaches.

Answer 11

Functional Abstraction

Question 12

Details of the data elements are not visible to the users of data.

Answer 12

Data Abstraction

Question 13

forms the basis for Object Oriented design approaches.

Answer 13

Data Abstraction

Question 13

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 13

Modularity

Question 14

It is the only property that allows a program to be intellectually manageable. Single
large programs are difficult to understand and read due to a large number of
reference variables, control paths, global variables, etc.

Answer 14

Modularity

Question 15

Advantages of Modularity

Answer 15

• It allows large programs to be written by several or different people
• It encourages the creation of commonly used routines to be placed in the library and
  used by other programs.
• It simplifies the overlay procedure of loading a large program into main storage.
• It provides more checkpoints to measure progress.
• It provides a framework for complete testing, more accessible to test
• It produced the well designed and more readable program.

Question 16

Disadvantages of Modularity

Answer 16

• Execution time maybe, but not certainly, longer
• Storage size perhaps, but is not certainly, increased
• Compilation and loading time may be longer
• Inter-module communication problems may be increased
• More linkage required, run-time may be longer, more source lines must be written,
  and more documentation has to be done

Question 17

is achieved by developing
functions that perform only one kind of task and do not excessively interact with other
modules. Independence is important because it makes implementation more accessible
and faster. The independent modules are easier to maintain, test, and reduce error
propagation and can be reused in other programs as well. Thus, functional
independence is a good design feature which ensures software quality.

Answer 17

Functional Independence:

Question 18

It measures the relative function strength of a module.

Answer 18

Cohesion

Question 18

It is measured using two criteria:

Answer 18

Cohesion:
Coupling:

Question 19

It measures the relative interdependence among modules.

Answer 19

Coupling:

Question 20

The fundamental of Information hiding 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 20

Information hiding

Question 21

To design a system, there are two possible approaches:

Answer 21

Top-down Approach Bottom-up Approach

Question 22

A good system design strategy is to organize the program modules in such a method that are easy to develop and latter too, change. Structured design methods help developers to deal with the size and complexity of programs. Analysts generate instructions for the developers about how code should be composed and how pieces of code should fit together to form a program.

Answer 22

Strategy of Design

Question 23

SOLID Principles

Answer 23

(Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion)

Question 24

Additional Software Design Principles

Answer 24

* SOLID Principles (Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) * 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 25

DRY

Answer 25

(Don’t Repeat Yourself)

Question 26

(PoLA)

Answer 26

Principle of Least Astonishment (

Question 27

(YAGNI)

Answer 27

You Aren’t Gonna Need It

Question 28

Different Designs in Software

Answer 28

Architectural Pattern Design Pattern

Question 28

KISS

Answer 28

Keep It Simple, Stupid

Question 29

explains a system’s core ideas and characteristics with respect to its relationships, environment, and other design principles. It includes a software system’s organizational structure, behavioral components, and composition of those components into more complex subsystems.

Answer 29

Software architecture

Question 30

defines the high-level structure and organization of a software system. It outlines the fundamental components, their interactions, and the overall layout of the system. It guide decisions about the system’s scalability, performance, and maintainability. They focus on the system’s macro-level aspects and establish a framework for the design and implementation of the entire application.

Answer 30

software architecture pattern

Question 31

6 Different Architectural Patterns

Answer 31

* Layered Pattern Client-server architecture event-driven architecture Microservices Monolithic MV Pattern

Question 32

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 32

Client-server architecture

Question 32

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. Enables modular development and maintenance, commonly used in web applications.

Answer 32

Layered Pattern

Question 33

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

Answer 33

event-driven architecture

Question 34

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

Answer 34

Microservices

Question 35

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 35

Monolithic

Question 35

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 35

MV* Pattern

Question 36

are an important concept in software development. They provide tested answers to common design issues, helping developers reduce code structure and improve maintainability. Design patterns allow you to construct resilient and scalable systems while also supporting excellent software architectural practices.

Answer 36

Design Pattern

Question 37

is a general, recurring solution to a commonly encountered problem in software design that is utilized in software engineering.

Answer 37

Design Pattern

Question 38

It is not a comprehensive design that can be implemented in code straight immediately.

Answer 38

Design Pattern

Question 39

It is a description or model for issue solving that may be used in a variety of settings.

Answer 39

Design Pattern

Question 40

are similar to cooking recipes in that they provide a tried-and-true approach to producing consistent results without having to start from scratch each time.

Answer 40

Design Pattern

Question 41

Attempt to generate things in a manner appropriate to the situation.

Answer 41

Creational Design Patterns

Question 42

Types of Design Pattern

Answer 42

1. Creational Design Patterns 2. Structural Patterns 3. Behavioral Design Patterns

Question 43

Are concerned with the generation of objects, ensuring that they are formed in a situationally appropriate manner and providing flexibility in how objects are instantiated.

Answer 43

Creational Design Patterns

Question 44

Concerned with object composition, specifying how to combine items to achieve additional functionality

Answer 44

Structural Patterns

Question 44

It is a formula for combining many objects and classes to create a larger structure.

Answer 44

Structural Patterns

Question 45

It's similar to building a house based on a blueprint.

Answer 45

Structural Patterns

Question 46

These patterns tell us how to incorporate the distinct components of a system in a way that is simple to update or grow without affecting the overall system.

Answer 46

Structural Patterns

Question 46

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

Answer 46

Behavioral Design Patterns

Question 47

When developers adopt these patterns, it's like putting together a jigsaw, with the pieces fitting together effortlessly.

Answer 47

Behavioral Design Patterns

Question 48

This makes the software more organized, easy to alter, and less likely to break when we add or change things.

Answer 48

Behavioral Design Patterns

Question 49

is an essential phase of the Software Development Life Cycle. The list of requirements that you develop in the definition phase is used to make design choices. In the design phase, one or more designs are created to achieve the project result. Depending on the project subject, the design phase products include dioramas, flow charts, sketches, site trees, HTML screen designs, photo impressions, prototypes, and UML schemas.

Answer 49

Design Phase in SDLC

Question 50

All the details about the system design phase are mentioned in the software requirement specification document. It helps development teams in the implementation phase for error-free system development.

Answer 50

true

Question 51

A thorough analysis and requirement helps to prepare better designs at once. Many companies follow agile methodology for software development.

Answer 51

Design Phase in SDLC

Question 52

Many types of designs are created in this phase of the software development process. Depending on the business requirements and the client’s needs, the design is improved many times. Moreover, developers build a minimum viable product and get feedback from real customers.

Answer 52

Design Phase in SDLC

Question 53

A software developer checks all required documents for a better production environment. Since designing defines the entire system architecture, no development team moves forward without it.

Answer 53

true

Question 54

The design of a software system falls into two categories.

Answer 54

1) High-Level Design (HLD): 2) Low-Level Design (LLD):

Question 55

It includes the functional logic of the modules. You have to collect the details of the interface, database tables, and type and size. Furthermore, a listing of error messages, and addresses dependency issues.

Answer 55

2) Low-Level Design (LLD):

Question 56

It includes a brief description and the name of each module. So, you have to analyze the functionality of each module. Moreover, key elements are used to identify the database tables.

Answer 56

1) High-Level Design (HLD):

Question 57

At this stage, developers define the technical details of the product. They are as follows.

Answer 57

* Screen design * Sketches * System interfaces * UI/UX designs * Databases * Prototypes

Question 58

Roles in design phaseq

Answer 58

Client. * UX designer. * Project manager. * Business analyst. * Software developer. * Quality assurance (QA) specialist.

Question 59

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

Answer 59

Client

Question 60

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

Answer 60

UX designer.

Question 61

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

Answer 61

Project manager.

Question 62

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

Answer 62

* Software developer.

Question 63

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

Answer 63

Business Analyst

Question 64

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

Answer 64

* Quality assurance (QA) specialist.

Question 65

Requirements Visualization in Design Phase

Answer 65

Rapid Prototyping Wireframes

Question 65

Starting with a clean, spare wireframe design also gives UI/UX designers room to iterate. They can collect early feedback from user testing on core UX/UI elements, without distracting users with visual design details. Design teams try out different concepts, user flows, and templates as they work toward the ultimate user experience.

Answer 65

true

Question 66

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

Answer 66

wireframe

Question 67

Your wireframe shows the design team and stakeholders the bare- bones outlines of essential webpages, components, and features, including: * Screen layouts * Navigation bars * Components of UX and UI design * Interactive elements

Answer 67

true

Question 68

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

Answer 68

rapid prototyping

Question 69

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

Answer 69

* Review.

Question 69

The three-step rapid prototyping process is basically a loop that repeats until you’ve got a prototype that resonates with your users. The main steps are:

Answer 69

Build. * Review. * Refine.

Question 70

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

Answer 70

Build

Question 71

Adjust the prototype based on the feedback you receive.

Answer 71

* Refine.