Code Complete ----------- (Note 1—— Laying the foundation)

最新推荐文章于 2025-03-18 16:00:00 发布

CrystalHareHus

最新推荐文章于 2025-03-18 16:00:00 发布

阅读量1.3k

点赞数

CC 4.0 BY-SA版权

分类专栏：读书笔记文章标签： construction system scalability testing components debugging

本文链接：https://blog.csdn.net/CrystalHareHus/article/details/1460464

读书笔记专栏收录该内容

13 篇文章

订阅专栏

本文详细介绍软件开发过程，包括问题定义、需求开发、软件架构等前期活动；深入探讨详细设计、编码调试、单元测试等建设阶段活动；并涉及系统测试及维护等后期活动。文章还阐述了迭代与顺序方法在软件开发中的应用。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

No comparable book is available.

    Activities Before Construction:
   Problem Definition --> Requirements Developments --> Softare Architecture

   Construction activities focuses on:
   Detailed Design --> ****Coding and Debugging**** --> Unit Testing --> Integration --> Integration Testing.

   Activities After Construction:
   System Testing --> corrective maintenance(保障维护)

Construction is also sometimes knowns as "coding" and "programming".

A Richer understanding way of software development ---- Metaphors(隐喻)

Measure Twice, Cut Once --- Look before you leap (三思而后行)

Prerequisites --- Iterative and Sequential Approaches

1. A problem definition (Product Definition) defines what the problem is without any reference to possible solutions. The problem definition should be in user language, and the problem should be described from a user's point of view.

2. Requirements describe in detail what a software system is supposed to do. ---- Specification(Spec).
     Handling requirements changes during construction.

3. Architecture, is also known as "System Architecture", "high-level design", "top-level design", is the frame         that holds the more detailed parts of the design.
    Typical Architectural Components:
    Program Organization.   ----- The less responsiblity Sub-System has, the better the system divide into;
    Major Classes;
    Data Design ---- Data base design;
    Business Rules;
    User Interface Design;
    Resource Managerment -----   Thread, Memory, handle, etc...
    Security;
    Performance;
    Scalability --- is the ability of a system to meet future demands;
    Interoperability --- share data or resources with other software or hardware;
    Internationalization/Localization;
    Input/Output ---- look-ahead, look-behind, just-in-time;
    Error Processing --- Exception, detective or corrective....;
    Fault Tolerance;
    Feasibility;
    Overengineering --- robustness
    Buy vs Build Decisions;
    Reuse Decisions;
    Change Strategy --- if , else, table-driven;
    General Architectual Quality;

Generally, a well-run project devotes about 10 to 20 percent of its effort and about 20 to 30 percent of its schedule to requirements, architecture, and up-front planning. These figures don't include time for detailed design --- that's part of construction.