Home  >  Q&A  >  body text

java - 架构师是用什么软件画架构图的?软件架构有没有什么好的书?

架构师是用什么软件画架构图的?不会就是用PPT吧?思维导图应该也不够用啊.
还有软件架构有没有什么好的书?

阿神阿神2741 days ago1451

reply all(6)I'll reply

  • 阿神

    阿神2017-04-17 17:53:08

    About question 1: Drawing software

    No one has mentioned processon. Although it is a web application, its smoothness, beautiful pictures, and intelligent operation are far better than visio and ppt.
    Look at a few pictures drawn with it. knew.

    About question 2: Architecture book

    There are many kinds of architectures. I recommend books related to basic software pattern architecture:
    "Pattern-Oriented Software Architecture" (Volume 1 to Volume 4) from the shallower to the deeper.

    reply
    0
  • 高洛峰

    高洛峰2017-04-17 17:53:08

    • xmind

    • "Must-Read Software Architecture for Programmers"

    reply
    0
  • 大家讲道理

    大家讲道理2017-04-17 17:53:08

    xmindaxure 都可以,xmindThe style is more colorful, it depends on personal preference.

    reply
    0
  • 高洛峰

    高洛峰2017-04-17 17:53:08

    阿里用的是axure

    reply
    0
  • ringa_lee

    ringa_lee2017-04-17 17:53:08

    I just use mindjet and flowchart software, haha, I am not an architect

    reply
    0
  • 大家讲道理

    大家讲道理2017-04-17 17:53:08

    The fundamental purpose of drawing software architecture diagram is to describe it from different angles, and it has little to do with the tools. I generally use the following tools in this way, for reference only:

    1. xmind: Use mind maps to sort out requirements, or large functional blocks;
    PS: Mind maps are more flexible, and you can even change them while communicating with customers.
    2. axure: Used to draw low-guaranteed prototypes of APP, in fact, PPT can also be used;
    3. Use visual or EA's UML to draw software architecture:

    3.1 用例图:描述需求,业务场景
    3.2 基本框图:描述软件逻辑架构,就是分层、模块之类的;
    3.3 时序图:描述系统和外部,或者系统内部各模块的交互;
    3.4 状态机/泳道图:描述比较复杂的工作流;
    

    Personally, I think that software architecture still needs to be practiced first. It is best to start a project from scratch, starting from setting up the framework, and then continue to refactor as the requirements change (you may have to refactor). At this time, read some books. They will teach you how to reconstruct from a theoretical perspective and some excellent practices, and then you can apply it to practice and repeat it. . . .

    reply
    0
  • Cancelreply