Scribd
Upload
36 views3 pages

Question: Explain Software Design?

Software design is the process of identifying software components and their relationships based on customer requirements. It involves abstraction, refinement, and modularity. Key concepts include software architecture, control hierarchy, structural partitioning, data structures, procedures, and information hiding. Design considerations are compatibility, extensibility, fault tolerance, maintainability, reliability, reusability, robustness, security, usability, performance, portability, and scalability.

Uploaded by

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

Question: Explain Software Design?

Software design is the process of identifying software components and their relationships based on customer requirements. It involves abstraction, refinement, and modularity. Key concepts include software architecture, control hierarchy, structural partitioning, data structures, procedures, and information hiding. Design considerations are compatibility, extensibility, fault tolerance, maintainability, reliability, reusability, robustness, security, usability, performance, portability, and scalability.

Uploaded by

kamran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Question: Explain software design?

What is software Design?


Software design is an activity in which you identify software components and their relationships, based
on a customer’s requirements.

Software Design Concepts:


1. Abstraction 2. Refinement 3. Modularity
4. Software Architecture 5. Control Hierarchy 6. Structural Portioning
7. Data Structure 8. Software Procedure 9. Information Hiding

1. Abstraction:
 Abstraction is the process of generalization by reducing the information content of a
concept.
 It is an act of representing essential features without including the background details or
explanation.

2. Refinement:
 It is the process of elaboration
 One or several instructions of a given program are decomposed into more detailed instructions.
 Abstraction and Refinement are complementary concepts.

3. Modularity:
 Software Architecture is divided into components called modules.

4. Software Architecture:
 The overall structure of the software and the ways in which that structure provides conceptual
integrity for a system.

5. Control Hierarchy:
 A program structure that represents the organization of a program components and implies a
hierarchy of control.

6. Structural Portioning:
 The program structure can be divided both Horizontally and vertically.
 Horizontal partition defines separate branches of modular hierarchy for each major program
function.
 Vertical partition suggests that control and work should be distributed top down in the program
structure.

7. Data Structure:
 It is a representation of the logical relationship among individual elements of data.
8. Software Procedure:
 It focusing on the processing of each module individually.

9. Information Hiding:
 Modules should be specified and designed so that information contained within a module is
inaccessible to other modules that have no need for such information.

Software Design Consideration:


1. Compatibility 2. Extensibility 3. Modularity
4. Fault Tolerance 5. Maintainability 6. Reliability
7. Reusability 8. Robustness 9. Security
10. Usability 11. Performance 12. Portability
13. Scalability

1. Compatibility:
 The software is able to operate with other products that are designed for interoperability with
another product.
 For Example, a piece of software may be backward-compatible with and older version of itself.

2. Extensibility:
 New Capabilities can be added to the software without major changes to the
underlying architecture.

3. Modularity:
 The resulting software comprises well defined, independent components which
leads to better maintainability.
 The components could be then implemented and tested in isolation before being
integrated to form a desired software system.

4. Fault Tolerance:
 The software is resistant to and able to recover from component failure.

5. Maintainability:
 A measure of how easily bug fixes or functional modification can be accomplished.

6. Reliability:
 The software is able to perform a required function under stated conditions for a
specified period of time.

7. Reusability:
 The ability to use some or all of the aspects of the preexisting software in other
projects with little to no modification.

8. Robustness:
 The software is able to operate under stress or tolerate unpredictable or invalid
input.

9. Security:
 The software is able to withstand and resist hostile acts and influences.

10. Usability:
 The software user interface must be usable for its target user/audience.

11. Performance:
 The software performs its tasks within a time frame that is acceptable for the user,
and does not require too much memory.

12. Portability:
 The software should be usable across a number of different condition and
environments.

13. Scalability:
 The software adapts well to increasing data or number of user.

You might also like