How to write software outline design?

Overview Design

Profile design is an important phase of translating user goals and requirements into a specific interface design, where we need to get the design and data structure of the software (including mobile applications and websites) from the needs analysis of the previous phase.

It is usually the complexity of the system according to different functions of modularization, clear the hierarchical relationship between the modules and call relationships, determine the interface between the modules and the user interface. The data structure part is based on the characteristics of the data to determine the structures and design the corresponding database.

the process of software design

The software design generally has the following process:

1，需求分析    在这一阶段,我们需要理清楚到底要解决哪些问题    并完成“软件需求说明书”2，概要设计    在这一阶段，根据上一阶段的需求来确定总体的实现方案    确定整个软件的大体布局    各模块的功能以及模块之间的衔接    模块与外部系统的关系，    并完成“软件概要设计说明书”3，详细设计    在这一阶段，我们应该开始探讨每个模块该如何具体实现    每个实现中需要哪些算法、属性、参数、数据结构、接口    并完成“软件详细设计说明书”

How to write an outline design manualOverall design

需求目标运行环境局限结构未解决的问题

The reader has a holistic view of the module design behind the preparation.

Interface design

外部接口内部接口用户接口

These interfaces are not interface in programming, but are resources available for the software. Enables the reader to understand what resources are available for use.

Run the design

模块组合运行时间与控制

Module design

This is the core of the overall outline design and it needs to indicate:

每个模块做什么，实现了哪些功能每个模块怎么做，包括输入、输出、逻辑、与其他模块的衔接、接口每个模块所处的逻辑位置每个模块所处的物理位置每个模块的层次结构，可以用软件框图来展示每个模块的关系，诸如依赖、通信等关系每个模块的接口，模块之间如何传递信息以及信息本身的结构每个模块的处理方式，其需要满足于哪些功能或性能上的要求

Data

逻辑结构物理结构

Disaster tolerance Design

出错信息补救措施系统维护设计

Monitoring design

各个模块的组合、控制以及模块运行的时间

Interface design

Theme interface design of software

There are also things like "safe design" that can be considered.

Team consultation is required for design guidelines, code specifications, interface conventions, named Rules, and so on.

use of the outline design

The summary design is an important support to evaluate the overall design feasibility of the software, as each module has already been identified, it is good to check whether the existing modules are sufficiently complete, can also be used to assess the workload and to know the next step of the plan, but the summary design should not focus too much on the specific business processes and details of implementation, It's just a modular program.

How to write software outline design?