Design model in software engineering — Csmates.com

Software Design problemsand solutions are generally complex, and many aspects of software systems must be modelled. Consequently, there are so many kinds of modelling notations used in software design.

Software design models may be classified into 2 broad classes.

• These models represents aspects of software systems that do not change during execution.
• Generally these models represents software components, their characteristics, and unvarying relationships between software components.
• Examples of static models are object and class diagrams, use case diagrams, data structures pictures, operation specification and implementation diagrams.
• These models show what happens during software execution.
• Examples of dynamic models are interaction diagrams, state-charts, data-flow diagram, decision trees, and tables and mini-specs.

In software design, models from those of these categories are used for problem analysis, design creation and investigation, and design documentation.

Software Design Strategy

Software design is a problem solving activity and a general problem solving strategy is comprised as

1. Understand the problem.
2. Generate potential solutions to the problem.
3. Evaluate the potential solutions to pick the best.
4. If the best solution are inadequate, return to step 2 to refine solutions or generate new solutions.
5. Ensure that the solution is adequate, and that the work is complete and well documented.

The problem solving strategy outlined is simple and complete, and the same will be used as the basis for the general design process.

General Design Process

1. This step should produce a clear design problem statement to guide the remainder of the process.

• Generate/Refine the Design

1. The next step is to generate design ideas, including design alternatives, or to refine ideas generated and evaluated before.

2. These ideas are recorded in various design documents.

1. The newly generated or refined design ideas are evaluated, especially against the problem statement.

2. Evaluation conclusions are recorded, along with design decisions resulting from evaluation.

1. The final step in the process is a review by people.

2. Ideally reviewers are drawn from outside the design group, and may include clients, upper management, representatives of the other part of the organization, or design consultant.

3. The goal is to ensure that the design succeeds in solving the design problems.

Originally published at https://www.csmates.com.