Detailed description of the overall scheme of software development

Detailed description of the overall scheme of software development

Software development is the process of building a software system or the software part of the system according to the needs of users. Software development is a systematic project, including requirements capture, requirements analysis, design, implementation and testing. The following is a detailed description of the overall scheme of software development I have compiled, and you are welcome to refer to it!

Chapter 1 Introduction

The use of 1. 1

Explain the main purpose of writing detailed design scheme.

The purpose of manual compilation is to explain the design considerations of each program (each module or subroutine) and database system at all levels of a software system, and to provide coding basis for programmers.

If a software system is relatively simple and has few layers, then this document can be written without being written separately, and combined with the non-repetitive parts in the outline design specification.

This scheme focuses on the realization process of the module and the detailed design of the database system.

1.2 background

It should include the following aspects:

A. the name of the software system to be developed;

B. Basic concepts of the system, such as the type and subordinate status of the system;

C. name of the development project team.

1.3 reference

List the documents or materials cited in the detailed design report, the author, title, publishing unit and date of publication of the materials, and explain how to obtain these materials if necessary.

1.4 Definition and interpretation of terms

List the original technical terms, definitions and abbreviations used in this document that may cause confusion.

Chapter II Design Overview

2. 1 tasks and objectives

Explain the tasks and objectives of detailed design.

2.2 Overview of requirements

A brief description of the developed software, including main business requirements, input, output, main functions, performance, etc. , especially the system performance requirements.

2.3 Overview of Operating Environment

Description of the hardware on which the system depends, including operating system, database system, middleware, interface software, possible performance monitoring and analysis, and configuration requirements.

2.4 Conditions and Restrictions

Detailed description of internal and external constraints and limitations of the system. Including commercial and technical conditions and constraints, as well as schedule, management and other constraints.

2.5 Detailed design methods and tools

Briefly explain the methods and tools used in detailed design. For example, HIPO diagram method, IDEF(I2DEF) method, E-R diagram, data flow diagram, business flow diagram, selected case tools and so on. , try to use standard specifications and auxiliary tools.

Chapter 3: Detailed system requirements analysis.

This paper mainly analyzes the system-level requirements. First of all, it is necessary to further confirm the enterprise demand put forward by the demand analysis, and make a more detailed analysis of the demand changes brought about by the changes in the situation.

3. 1 Detailed requirements analysis

Including: detailed functional requirements analysis, detailed performance requirements analysis, detailed resource requirements analysis, detailed system operating environment and constraints analysis.

3.2 Detailed system operating environment and constraint analysis interface requirements analysis

Include system interface requirement analysis, existing software and hardware resource interface requirement analysis and import software and hardware resource interface requirement analysis.

Chapter IV Determination of Overall Plan

Focus on the determination of the overall structure of the system and the division of interfaces.

4. 1 Confirmation of the overall structure of the system

Confirm the composition, logical structure and hierarchy of the system, confirm the application system, supporting system and their respective functions, refine the integrated design and system workflow, and pay special attention to the structural changes of the system itself and other systems of the company caused by the introduction of software. Including system composition, logical structure and hierarchical structure confirmation, application system structure confirmation, supporting system structure confirmation, system integration confirmation and system workflow confirmation.

4.2 Detailed interface division of the system

4.2. 1 Detailed interface division between application system and supporting system

The interface between application system and supporting system includes the service scope and access mode of main server and other servers, the support mode of network and database to application system, the management and access mode of global data, etc.

4.2.2 Detailed interface division within the system

Interfaces between system functions include coverage, methods involved in system modules and function calls between modules, global data formats, system performance requirements, etc.

Chapter V Detailed System Design

5. 1 System structure design and subsystem division

Confirm the composition and logical structure of the system before design.

Divide system functional modules or subsystems (if necessary or necessary, especially large-scale software systems).

5.2 Detailed design of system function modules

According to the structural design method, the functional modules or subsystems of the system are designed on the basis of the decomposition of system functions layer by layer. This is one of the main parts of detailed design.

Hierarchical diagram is used to describe the overall structure, functional decomposition, mutual call relationship and information interaction between modules, and IPO diagram or other methods are used to describe the functions completed by each module. For higher requirements, it is suggested to use HIPO diagram for functional decomposition and module description, and use IDEF0 method for functional model design.

Detailed design of the functions and their relationships completed by each module of the application system, describing the component structure, algorithm, interface relationship between modules, requirements, functions and comparison relationship between modules with IPO or structural diagram.

The description of each module can refer to the following format:

Module number:

Module name:

Input:

Handling:

Algorithm description:

Output:

Among them, the processing and algorithm description are mainly completed by pseudo-code or specific programming language.

For higher detailed design requirements, it is suggested to design each functional module with IDEF0 diagram.

If the software needs secondary development (including function expansion, function transformation, user interface transformation, etc.). ), the corresponding design work should be completed by setting sub-topics.

5.3 Detailed design of system interface

System interface describes various interfaces of application system software. Other interfaces of the whole system (such as system hardware interface and communication interface, etc.). ) is explained in the corresponding section.

5.3. 1 external interface design

According to the division of system interfaces, the external interfaces of the system are designed, and all external interfaces (including function and data interfaces) of the system are designed.

Internal interface design

Design the call relationship and data interface between functional modules in the system.

User interface design

Specify the content, interface style and calling mode of man-machine interface, including so-called form design, report design and printout required by users. This part may be more informative.

Chapter VI Database System Design

This database design can be written independently, especially for large-scale database application systems, that is, there is a separate database design manual.

6. 1 design requirements

Information model design

Determine the type (entity or view) of system information, determine the attributes and keywords of system information entities and the relationship between entities, and describe the database and structure design, data elements and attribute definitions, data relationship patterns, data constraints and restrictions in detail.

6.3 database design

6.3. 1 design basis

Explain the database design basis such as frequency and flow of data access, maximum data storage capacity, data growth and storage time.

6.3.2 Types and characteristics of database

Explain the types, characteristics and quantity of databases used in the system, how to realize interconnection and how to transmit data.

Logical structure of database

Explain the methodology and tools used in the transformation from database conceptual mode to logical mode, and complete the transformation from database conceptual mode to logical mode. List in detail the identification, definition, length and relationship of each data item, record and file in the data structure used. This part is the main part of database design.

6.3.4 Physical Structure Design

List the storage requirements, access methods, access units and access physical relationships of each data item in the data structure used. Establish the system programmer view, including: the arrangement of data in memory, including the design of index area and buffer area; Organization of external storage devices and external storage spaces, including organization and division of index areas and data blocks; Ways and methods of accessing data.

Database security

Explain how to enjoy the data and how to ensure the security and confidentiality of the data.

data dictionary

Write a detailed data dictionary. For various items involved in database design, such as data items, records, departments, file patterns and sub-patterns, a data dictionary is generally established to explain their identifiers, synonyms and related information.

Chapter VII Non-functional Design

Chapter VIII Environmental Configuration

Development. Test and operating environment

;