• <abbr id="ck0wi"><source id="ck0wi"></source></abbr>
    <li id="ck0wi"></li>
  • <li id="ck0wi"><dl id="ck0wi"></dl></li><button id="ck0wi"><input id="ck0wi"></input></button>
  • <abbr id="ck0wi"></abbr>
  • <li id="ck0wi"><dl id="ck0wi"></dl></li>
  • Home >

    How To Establish Project Document Management Regulations

    2010/12/7 15:55:00 115

    Establishing Project Document Management Regulations

    How to establish

    Project documentation

    Management regulation


    Starting from the personality of every industry and individual project, we need

    Controller

    Combined with the actual situation, worked out suitable for oneself.

    Document management

    Regulations.

    (guidelines for software documentation management "and" guidelines for the compilation of computer software product development documents "(hereinafter referred to as the guide) provide us with relevant guidance.

    First of all, we should clarify the specific classification of software project documents.

    The documents in the guide can be divided into informal documents and official documents from the perspective of project importance. They can be divided into development documents, product documents and management documents from the perspective of project cycle. They can be further classified into L4 document documents, which include: feasibility study report, project development plan, software requirement specification, data requirement specification, outline design specification, detailed design specification, database design manual, user manual, operation manual, module development dossier, test plan, test analysis report, development progress monthly report, project development summary report.

    Such a classification refines the documents required for management at all stages of project progress.


    Secondly, we need to sort out the project documents.

    The following is a comparative analysis of the documentation of EDW project group and the guidelines for software documentation management.

    By contrast, we can see that there are 4 problems in EDW document without standardized management.


    Question 1: the project team conducted research on demand and information for business departments and technology departments in the early stages of development, which could cover some software requirements and data requirements specifications. However, there was a lack of documentation of project requirements descriptions and changes by business departments.

    This part of the document needs to be set up by the corresponding directory.


    Question 2: for design notes, in a more complex system, the design stage should be broken down into two steps: outline design and detailed design.

    At present, the EDW project team only provides the outline design specification for the ETL module. It does not store the directory separately, but confuses with other design documents.

    For more complex application development projects, these two design documents should be classified into directory management.


    Question 3: in project testing and acceptance, the project team did not require that the test plan document and test result report be regulated, but only the problem documents in the testing process were taken into account. Therefore, the progress and quality of the test could not be controlled.


    Problem 4:EDW project group's work is divided into 3 working groups: model design, ETL and market application. The corresponding document management needs to focus on these 3 themes.

    Among them, model design and ETL are the modules of data warehouse project implementation, and the market application includes the development of small projects based on data warehouse.

    Therefore, document management should also formulate management rules for these 3 parts.


    Through comparative analysis, aiming at the problems of EDW document management, EDW project team finally established a formal project document management rule based on general rules.

    The specific provisions are the following 5 points.


    (1) the document is divided into two parts: submission Management: project regular documents and project archive documents.

    The submission and use of regular documents are divided according to the different tasks of the team members in the project group. The project archive documents are classified and filed by the project management director (or project document manager) from the regular documents in the important documents of the project.


    (2) the conventional document management directory is divided into daily management documents and project process management documents.


    (3) daily management documents include project reports, meeting minutes, project management templates, major issues tracking, and data quality management.

    The project report can be divided into personal weekly report, group weekly report, project weekly report, project briefing, and project briefing.

    They are classified according to different catalogues.


    (4) submit a complete project development and application development process document.

    It usually includes: project plan, business requirement specification, data requirement specification, module, application development document, system test document, detailed design document, system test document, user manual, on-line document, training material, system operation and maintenance, etc.


    (5) all project team members have established corresponding users in the VSS software environment, each of them has the permission to read, write, add and delete all kinds of documents.

    The quality of submitted documents is guaranteed by each team leader, and the document manager or project manager is responsible for the overall submission of project documents at all stages.

    After the establishment of the project document management standard, the key lies in the "implementation according to regulations", so that the chaotic storage mode becomes well organized.

    • Related reading

    Overview Of Project Document Management

    Document management
    |
    2010/12/3 15:52:00
    52

    The Important Role Of Document Management In Project Process

    Document management
    |
    2010/12/1 15:45:00
    160

    Administrative Measures For Confidentiality Of Electronic Documents Filing

    Document management
    |
    2010/11/27 16:43:00
    648

    File Retrieval Rules

    Document management
    |
    2010/11/27 16:33:00
    76

    項目文檔管理的概述

    Document management
    |
    2010/11/25 16:06:00
    67
    Read the next article

    Du Yuzhou: Rising Industrial Cluster Economy

    In fact, since the reform and opening up, China's textile and garment industry has developed rapidly. Among them, the textile industrial cluster area mainly composed of city (county) and town regional economy has become an important part of China's textile and garment industry because of its vigorous economic vitality.

    主站蜘蛛池模板: 日本护士恋夜视频免费列表| 国产福利在线观看一区二区| 女人扒开双腿让男人桶| 天天干天天干天天干| 国产精品白丝在线观看有码| 日本精品3d动漫一区二区| 成年人在线网站| 天堂8在线天堂资源bt| 国产精品久久久久久久久齐齐| 国产做a爰片久久毛片| 国产男女免费完整视频| 国产三级在线观看免费| 国产三级在线观看完整版| 人妻少妇精品视频一区二区三区| 国产三级在线观看视小说| 免费视频淫片aa毛片| 亚洲伊人久久大香线蕉综合图片 | 午夜精品久久久久久毛片| 亚洲欧美精品伊人久久| 久久久精品波多野结衣| 99精品国产成人一区二区| a级毛片毛片免费观看永久| 亚洲国产成人精品激情| 精品特级一级毛片免费观看| 欧美日韩在线观看视频| 无码任你躁久久久久久老妇| 国内精品久久久久影院一蜜桃| 国产大片黄在线观看| 人妻精品久久久久中文字幕| 久久天天躁狠狠躁夜夜2020一| a级情欲片在线观看hd| 999精品视频在线观看热6| 香蕉精品一本大道在线观看| 男人天堂资源站| 日本videoshd高清黑人| 国产精品第44页| 冈本视频老版app下载安装进入口 再一深点灬舒服灬太大了视频 | 97碰视频人人做人人爱欧美| 香蕉免费在线视频| 特级毛片www| 日日日天天射天天干视频|