Experience sharing of system architecture designers in preparing for the exam: the direction of paper writing

One 、 Amount of exercises

Comprehensive knowledge multiple choice questions ：

350 Tao architecture every day 10 Practice （35 God ）、250 The way is divided into questions （25 God ）.

Take time to do 3 A set of real questions .

Case analysis questions ：

take 8 The real problem of the year is the penultimate 2 It's done in six months （ In the last month, choose the question type according to everyone's situation ）

2017 The real topic of the year is reserved for “ The Saturday before the exam ”.

The paper ：

9 A theme 11 Papers

after 3 At the end 1 Practice within months .

“ The Saturday before the exam ” Play a topic that you don't often take an exam on the spot according to the exam time

Two 、 Experience sharing of architectural designer examination papers

1.1 Structure the paper 7 Most common directions

1.1.1 Structure the paper 7 Most common directions

Software development model ：

agile （ The Department score has been tested 3 Time , The architecture has not yet appeared ）

Rapid application development 、 Component assembly model （ You can use the same material ）

Spiral model （ Unified process 、 Architecture based development ）

Domain specific architecture

system modeling ：

UML modeling

Data flow graph modeling

1.1.2 Structure the paper 7 Most common directions

Software — Software architecture ：

System integration

SOA（ Microservices ）

No service （2017 The annual structure has been examined ）

Software internal architecture ：

Architectural style （ Almost test ！！！ But it may be like 13 The architecture style was specified in ）

Design patterns

1.1.3 Structure the paper 7 Most common directions

Quality attributes ：

Security

reliability

performance （ Distributed cache \ Storage forms appear ）

Data persistence layer design ：

ER chart （ Have not published papers ）

NoSQL

Demand engineering ：

Requirements development

demand management

1.2 Structure the thesis's secondary argument 4 Create question dimensions

What are the classifications

What are the common technical means

encounter / What problems to solve （ The security is ： What are the threats ）

What are the steps / Process area （ Special for Software Engineering ）

1.3 The paper “ The words are ugly ” What do I do ？

1.3.1 First impression is better

Leave no blank lines in the summary

Leave no blank pages in the body

First impression is not font , It's the number of words ！

1.3.2 front 500 The word “ Project introduction ” curing

“ Project introduction ” After curing , Write more and practice more .

At the same speed , Try to do this 500 The words are clear and recognizable .

1.3.3 These positions slow down and write well

Abstract

Start with an argument

The last paragraph