first part
Case-based analysis design capacity written test
Analysis and design capability of 1-7 scenes for specific design requirements
The knowledge and skills of the examinations are as follows:
Number Name Details 1 Java / J2EE can flexibly use J2EE, familiar with the Targets of J2EE Technical Architecture (such as JNDI, JMS, JTA, JMX, JaaS) applications, and association with design context. 2 UML masters the modeling of UML pairs of related design scenes. 3 OOA / OOD Master the core nature of OO three characteristics and OO. Understand some of the object-oriented design, such as OCP, DIP, etc.
4 Design Pattern / J2EE Pattern Familiar Model Application Three Elements: N Context - Environment / Context N System of Forces - Motivation / Purpose N Solution - Solution
The ability to apply various modes in flexible combination. 5 Architecture Pattern
Familiar with usage scenarios, such as N-Layer, Pipeline, and Reactor, etc. 6 Enterprise Application Architecture,
Enterprise
Integration Architecture, INTEGRATION ARCHITECTURE
According to specific enterprise applications, integration needs, master the ability of independent design enterprises, enterprise integration architectures. For example, data integration in heterogeneous environments, integration with legacy applications, based on event-driven software architecture (GUI applications, ESB applications, etc.).
The company has implemented a summary of the system design capacity evaluation case:
1. Seriously ignoring the system design factors involved in the case description, such as various constraints, system design features, the scope of work for system design is unclear, system design includes architecture design and detailed design, this time In addition to the case of the case, the problem needs to be designed in the architecture level. The remaining most questions are positioned in a specific background, which requires a more detailed system design, not just a few Class or mode. 3. Verification mechanism for system design or is based on their design, how to ensure that TDD (Test Driven Development) has not been thought of, at least traces at the system design level. 4. In the system design level, applicants pay more attention to the design of the static model, and ignore the nature of the software, elegant system design can be directly given in software code. A good system design should be a simple code, a clear logical structure. For example, in case four and case seven, on the one hand, the static model is not thought - well, just a grassy grass. Perhaps two applicants can write 2-5 lines of code to verify that your design is reasonable, whether it can be implemented.
