System design specifications (architecture. Summary. More) directory structure

2010-06-18  来源:本站原创  分类:Java  人气:194 

From: http://hi.baidu.com/gaoxiaopan/blog/item/2adf220633584072030881ca.html

XXX architecture design specification

(Focus on the system architecture design and produce stratified layers within the module, to clarify the relationship between modules)

1. Overview

This reference describes the data and the likely content.

2. Objective

Describe the purpose of this writing.

3. Architecture Design

Clarify the general principles for architecture design, such as analysis of the problem domain.

3.1. Framework Analysis

On the scene and analyze the problem domain, constitute the system architecture level design, to clarify the system of stratification.

3.2. Design

Clarify design ideas for architecture, reference architecture model number, combined with the current system needs the actual circumstances.

3.3. Architecture system

According to structure analysis and design system architecture generated maps and chart to describe, explain the reasons for stratification, level of responsibility, and mapping system according to the physical structure of the deployment plan, describing the system's deployment system.

3.4. Module partition

According to the division of the module structure diagram and clarify the reasons for module division, the physical map drawing module and the module dependency graph.

3.4.1. Module Description

According to the module physical map described the duties of each module, and declare that the other modules interface requirements. .

3.4.2. Module Interface Design

Module interface design, and provide some pseudo-code.

XXX outline design specification

(Outline design focuses on the module is divided into objects and to clarify the relationship between objects)

1. Overview

This reference describes the data and the likely content.

2. Objective

This paper describes the preparation of purpose.

3. Module Design Summary

Reference architecture specification of the block diagram and described the general design for the module idea.

3.1. Design

Summary of design to clarify the idea, the outline design thinking usually involves the design model.

3.2. Module A

3.2.1. Summary of design

Responsibilities under the module outline of module design (decomposition module object, the object of duties and a statement describing the interface between the object), drawing module of the object graph, dependency graph between objects and the main function of the module sequence diagram, respectively, to description and corresponding description of the module exception handling.

3.2.2. Module Interface

Clarify the definition of the architecture in implementation of the interface module design.

Detailed design specification XXX

(Detailed design of the module focuses on the realization of the object module is divided into properties and methods, and explain how)

1. Overview

This set of reference, information and the likely content.

2. Objective

Explained the purpose of this article written.

3. Module detailed design

3.1. Design

Explain the detailed design of the module idea.

3.2. Module A

3.2.1. Detailed design

According to a detailed description of the module outline design for the module to achieve the object, including the object's responsibilities, properties, methods, objects, functions within the flow chart of the associated object class, object exception. (Requires a major draw for the class diagram)

Prompted the preparation of detailed design specification (reference case)

F.1 Introduction

F.1.1 preparation purposes

Help prepare the detailed design specification of the purpose, that readers expected.

F.1.2 Background

Description:

a. The name of the software system to be developed;

b. The task of the project proponent, developer, user and run the program system Computing Center.

F.1.3 Definition

Used in this document are listed in the definition of technical terms and foreign words the first letter of the original group of phrases.

F.1.4 References

Listed in the references, such as:

a. The project approved project plan or contract, approval of higher authorities;

b. Belong to this project and other published documents;

c. throughout this document refer to the documentation, including the use of software to development standards. These files are listed in the title, document number, publication date and publishing units, indicating the source of these documents can be obtained.

F.2 program structure of the system

Out the procedure using a series of charts for each program within the system (including each module and subroutine) name, identifiers and hierarchical relationships between them.

F.3 Procedure 1 (identifier) Design Notes

From the beginning of this chapter, one by one to give different levels of the design considerations of each program. The following outline is given for the general situation. For a specific module, especially the relatively low level modules or subroutines, the content of many of its entries and it is often attached to the upper layer of module content of the corresponding entries in the same, in this case, simply note that point can be.

F.3.1 Procedure Description

Give a brief description of the procedure, the main explanation of the purpose of arrangements for the design significance of this process, and, also shows the characteristics of this procedure (the case of permanent memory or non-resident? Are subroutines? Are available or can not emphasis on manpower emphasis on manpower of? whether coverage requirements? is the order processing or concurrent processing Pu ... .. etc).

F.3.2 Function

Note that the program should have the function, can be used IPO plan (ie, input-output map of a deal) form.

F.3.3 Performance

Note all the performance requirements of the program, including the accuracy, flexibility and time characteristics of the request.

F.3.4 entry

Given on the characteristics of each entry, including name, logo, data types and formats, data values of the effective range of input methods. Quantity and frequency, input media, input data sources and security conditions, etc..

F. 3. 5 export items

The output of each item is given the characteristics, including name, logo, data types and formats, data values of the valid range, the output of the form, amount and frequency, output media, graphics and symbols on the output of the note, security conditions and so on.

F. 3.6 Algorithm

Detailed description of the algorithm used in this procedure, the calculation formulas and calculation steps.

F. 3.7 Process Logic

Graphs (such as flow charts, decision tables, etc.) together with the necessary instructions to represent the logic of this process flow.

F. 3.8 Interface

Figure shows the form attached to this procedure the upper layer of module and attached to the next level of this program modules, routines, instructions, and call parameters of the assignment is to describe the phase directly associated with the program's data structures (databases, data, text volume).

F. 3.9 Storage Allocation

Necessary, explain the process of memory allocation.

F. 3.10 Design Notes

Help prepare the arrangements in the program notes, such as:

a. Add the module first comment;

b. Increase in the branching point of the comment; on the functions of each variable, scope, default conditions added by the Notes;

d. Increase the use of the logic of the Notes and so on.

F. 3.11 constraints

Description of the program is running in the restrictions imposed conditions.

F. 3.12 Test Plan

Description of this procedure single test plan, including testing the technical requirements, input data, expected results, schedule, personnel functions, equipment condition and pile driver module requirements.

F. 3.13 unresolved issues

Shows the design of this program has not yet resolved and that the software designers to be resolved before completion.

F. 4 Procedure 2 (identifier) Design Notes

Similar to F. 3 is to describe the first two procedures as well as the first N-program design considerations.

Outdoor fine, invited jfhw360.taobao.com [size = medium] [/ size]

相关文章
  • System design specifications (architecture. Summary. More) directory structure 2010-06-18

    From: http://hi.baidu.com/gaoxiaopan/blog/item/2adf220633584072030881ca.html XXX architecture design specification (Focus on the system architecture design and produce stratified layers within the module, to clarify the relationship between modules)

  • Documentation of the development - the system architecture. Summary of the design. The detailed design specification 2011-05-23

    Note: The general architecture can be designed into the summary, unless the structure is particularly complex XXX architecture design specification (Focus on architecture design and produce levels of the system within the hierarchical modules, to cla

  • Perfect Understanding Linux file system directory structure in the 2010-03-11

    Articles Category: Operating system 1 What is the file system When you use Linux, when, if you ls-l / will be found in / under the bear with a lot of directories, such as etc, usr, var, bin ... ... and other directory, but in these directories, we go

  • File system directory structure 2010-12-07

    Linux file system structure for the tree. Linux file system entry is / all directory, file, device in / under / Linux file system is the organizer and the most superior leader. LINUX file system has four basic types: regular files, directories, files

  • Ubuntu system directory structure 2011-04-04

    Ubuntu Ubuntu system directory structure following the main directory the directory structure, you little know which files they contain can be, and no memory. / Root │ ├ boot / startup files. All systems start with the relevant files are kept in here

  • (Reproduced) linux file system directory structure 2011-06-09

    / Linux file system entry / Bin-based system required that the command is located in this directory is the minimum required for the system command, the files in the directory are executable, ordinary users can use the command / Boot Linux kernel and

  • News Publishing System Design and Implementation 2010-06-05

    Summary With the emergence of the network, web gradually integrated into people's lives. Quick and timely news browsing, colorful online information, the network and people's daily life. It breaks geographical restrictions, to truly make the informat

  • Logical architecture and physical architecture design in architecture 2011-05-23

    When observing and describing the overall situation of things, when the logical architecture and physical architecture is the most common point of view. For example, our office LAN as an example: From the physical point of view, all the computers "wi

  • User rights system design 2010-07-19

    Core Tip: This article describes a general-purpose business applications used in the user permissions system design framework, design documentation and the main source of iSecurityManager from SunWu Software Studio product. This guide applies to arch

  • System design principles 2010-09-12

    During system design, not only to consider the software's functional requirements, but also consider non-functional requirements such as software performance (Performance), scalability (Scalability), the system stability (Reliability), deployment (De

  • Reinsurance processing system design and implementation <switch> 2010-11-30

    At present, most insurance companies have completed the core business operations systems, customer service systems, information security system and other basic construction of information systems. But with the competitive environment and customer nee

  • Java logging system design and implementation framework 2010-12-17

    In the Java field, there are a lot of the logging component, open-open the log contains 21 components. Log system as an application service for tracking debugging, program state records, crash data recovery has an important role, we can put Java logg

  • Needs analysis on the system design problem 2008-06-19

    Needs analysis to what extent a summary of the design can begin? Outline design to what extent can the detailed design? Detailed design to what extent you can encode it? Needs analysis to: 1, a clear demand (the purpose of the system to be built, fun

  • JBoss directory structure that 2009-07-19

    jboss-as directory structure (Directory Structure) Directory Description bin Contains startup, shutdown and other system-specific scripts. Basically all the entry point JARs and start scripts included with the JBoss distribution are located in the bi

  • Content management system design and selection 2009-09-19

    Reprint Address: http://www.chedong.com/tech/cms.html Abstract: Content Management System Overview Content Management System Selection Advertising Management System Selection Forum / Community System Selection WYSIWYG Editor Selection Image upload an

  • Java logging framework of a system design and implementation (change) 2010-03-29

    1 Introduction Log tracking system is an indispensable debugging tool, especially in the background of any unattended procedures and debugging environment for those who do not follow the system has wide application. For a long time, the log system as

  • JBoss directory structure description 2010-05-03

    Directory Description bin Contains startup, shutdown and other system-specific scripts. Basically all the entry point JARs and start scripts included with the JBoss distribution are located in the bin directory. Contains the server startup, shutdown

  • (Transfer) JBoss directory structure description 2010-06-20

    jboss-as directory structure (Directory Structure) Directory Description bin Contains startup, shutdown and other system-specific scripts. Basically all the entry point JARs and start scripts included with the JBoss distribution are located in the bi

  • Ubuntu Linux directory structure 2010-07-12

    Ubuntu Linux directory structure Standard directory structure and important files / Root / Bin basic command of the binary file - contains the starting system and in the recovery mode to run the required documents the first time / Boot boot loader fo

  • Android 2.1 source directory structure of (turn) 2010-08-03

    Android 2.1 source directory structure of (turn) Author Rockie Cheng Android 2.1 | - Makefile | - Bionic (bionic C Library) | - Bootable (boot-related code) | - Build (compile rules and generic storage systems and other infrastructure development pac