1. Key points (know-how ), the use of skills4.1Design Guidelines
Design guidelines are the most important and critical work in the design phase. Often overlooked in practical work, most projects are sacrificed at this stage. Design guidelines focus on how to better design, design guidelines are usually to consider the content of: design content, methods, tools, templates, naming conventions, module partitioning rules (especially design granularity), quality and efficiency evaluation methods and so on. We must first determine the design content based on the needs of the system, customer capabilities, the characteristics of the project (cost, scale, schedule, quality) and its own experience. For software outsourcing engineering projects, especially some international outsourcing projects, design guidelines are generally established, and our design team only needs to learn, understand, produce and meet these requirements. In other cases, we need to define rules for one item and agree with our clients. In fact, in some ways, the design criteria represent the design capability.
1. Definition of design content
Identify and define the content of the summary design, detailed design, in defining the design content needs to consider the cost, quality, progress, team capabilities and other factors, but also to take into account the requirements of the testing phase.
Example: the design content of general website system
Overview design |
Summary Design Book |
1 copies |
System Architecture Design |
Physical architecture |
Software architecture & software hierarchy design |
subsystem (contains common part \package named) |
Overall design of the interface |
Overview Design -with XXX interface design book |
Some |
Sub-interface design with various products |
Overview Design -Website Structure design book |
1 copies |
Site structure Design (directory structure partition \ Include deployment design ) |
Overview Design -database design book |
1 copies |
Database physical /Logical Design |
Overview design -Data dictionary book |
1 copies |
Data dictionary |
Detailed design |
Picture List |
1 copies |
List of all display screens |
Joint design |
1 copies |
All program level co-design (total merge one): Log \log\ message \session\ permissions \ macro definition \ database procedures \ Screen components \ Special functions \ Business Common |
Hint Information design |
1 copies |
Log \log\ External messages all the external information is always concentrated together. |
Configuration design |
1 copies |
All kinds of configuration items overall lead cable |
Detailed design |
1 copies |
Universal rule design, most features unified design |
Detailed Design-xx function |
Some |
Complex functions, individually designed. About 30%~50% |
Example: Monitoring class system Design content
Number |
Outline design Content |
Describe |
1 |
Business aspects |
Business |
General outline design of the substation business layer |
1 copies |
|
2 |
|
Overview design of Substation Business Layer Station terminal |
1 copies |
|
|
|
..... |
|
|
5 |
|
"Screen Design List" |
1 copies |
|
6 |
|
Demo of the screen |
Several of the |
|
7 |
Service |
"Data Interchange standard for substation service layer" |
Total 1 copies |
|
8 |
|
Overview design of Substation service layer |
Total 1 (can also be divided by service) |
|
10 |
signal |
"Full signal list" |
1 this |
Signal Standard classification /number /device information standard -communication standard -Alert standard -processing Standard -performance requirements table |
11 |
|
"Information standard of substation intelligent equipment" |
Several of the |
Sub -devices, signal format specification |
|
|
.... |
|
|
16 |
|
"Version Import Signal list" |
1 copies |
Management with |
17 |
Data |
"Database Logic Design book" |
1 (according to the station /city /Province of the better) |
Logical design of database tables and fields |
|
|
.... |
|
|
21st |
|
"System Configuration Information Specification" |
Total 1 copies |
Content is a description of various configurations |
22 |
Interface |
"MIS interface design book" |
1 copies |
|
|
|
|
.... |
|
|
26 |
Technical aspects |
|
The design Manual of substation Auxiliary Monitoring architecture |
1 copies |
|
27 |
|
The key technology investigation case |
Some |
|
|
Detailed design Content |
|
1 |
Business aspects |
|
"Graphic Design" |
Several of the |
|
2 |
|
"Report Design" |
Several of the |
|
3 |
|
Detailed design of the service layer |
Several of the |
Design based on service (state management /control management /ADP) |
4 |
Technical aspects |
|
Detailed design of the screen layer |
1 copies |
Image engine /structure prototype design |
5 |
|
Detailed design of the service layer |
1 copies |
Service engine /structure prototype design |
6 |
|
"System common Design" |
1 copies |
|
7 |
|
"Business Common Design" |
1 copies |
|
8 |
|
Assisted development /testing Tools |
Several of the |
Management , auxiliary efficiency development use |
2. Design methods and tools
Design tools are considered based on the content of the design and the requirements. For example , using Erwin for DB design,Visio for process design, and so on. In addition, some design tools must be trained by the design team for effective use.
3. Create a design template
The design of the book into a corresponding template, the format, content, legend, text and other specific requirements to make the team more effective work. In some cases, we will design a 1-4-level catalogue will be detailed to ensure that the design is more effective.
Example Data template
Note: For templates such as Excel, you can make some macros or tools that are easier to retrieve, modify, and so on. In addition, the use of wikis and other systems to improve the management of design materials.
4. Naming conventions, module partitioning rules
Naming conventions can contain a lot of content, such as the naming of design documents, naming rules for various terms, numbering rules, and so on. It is a good habit to make a proper number for anything, and of course some people think it's an occupational disease. When the design material dozens of, hundred grams, when a designer needs and different levels of personnel, such as customers, users, business experts, managers, developers, testers and so on to communicate, and sometimes have to communicate in various languages, anyone would like to have a complete naming protocol.
2. Quality and efficiency assessment methods
Set the goal of quality and efficiency
4.2Design Review
Add
4.3Change Management
Add
4.4Team Organization
Add
Outline design, detailed design (c) key points (know-how), application skills