cp2044-in-depth Java Web Project combat explaining (2 sets of practical projects)

Essay background: In a lot of times, many of the early friends will ask me: I am from other languages transferred to the development of the program, there are some basic information to learn from us, your frame feel too big, I hope to have a gradual tutorial or video to learn just fine. For learning difficulties do not know how to improve themselves can be added: 1225462853 to communicate to get help, access to learning materials.

cp2044-in-depth Java Web Project combat explaining (2 sets of practical projects)

: Http://pan.baidu.com/s/1eQcrfMA

Course Objective: 1, grasp the work principle of Shiro 2, GRASP Shiro system organization and running process 3, grasp the core components of Shiro and use 4, realize Shiro and Jsp/servlet application integration 5, realize Shiro with spring integration 6, Implement Shiro integration with SSH

Detailed knowledge of permissions and organization in enterprise-level development is explained in detail.

A, "Enterprise Official Document Management project" is * * * Company according to business needs development needs, the establishment of enterprise internal use of integrated Document information Management Service platform. The enterprise data collects the input system in the Web form, after collecting and summarizing, provides the daily service information management, the business process execution and so on to the end user at all levels to provide the everyday Office services auxiliary Platform, assists this function department to issue the plan decision, enhances the overall enterprise internal business efficiency.

B, CMS project combined with the previous knowledge, comprehensive SSM three framework, combined with javascript,jquery,springmvc,svn,junit,maven,freemarker and other large number of knowledge points to explain a complete site implementation

Suitable crowd: Java program javaweb engineer SSH application developer SSM application developer other Java application developer

Complimentary OOA and Ood video commentary

Specific steps of the Ooa method

When using OOA to analyze a thing concretely. Generally follow the following 5 basic steps;

1. Determine the object and class. The object here is an abstraction of the data and how it is handled, reflecting the ability of the system to preserve and process the information that is always in the real world. A class is a description of a common set of properties and methods for multiple objects, including a description of how to create a new object in a class.

2, determine the structure (structure). Structure refers to the complexity of the problem domain and the connection relationship. The class member structure reflects the pan-China-special relationship, and the whole-part structure reflects the relationship between the whole and the local.

3, determine the theme (subject). A theme is a general overview of things and an overall analysis model

4, determine the attribute (attribute). A property is a data element that can be used to describe an instance of an object or classification structure, given in the diagram, and specified in the object's storage.

5, determine method. Methods are some of the processing methods that must be made after a message is received: The method is defined in the diagram and specified in the object's storage. For each object and structure, the ones used to add, modify, delete, and select a method are inherently implicit (although they are defined in the object's storage, but not on the diagram), while others are displayed.

Ood

The object-oriented design (object-oriented Design,ood) method is an intermediate transition in the Oo method. Its main function is to further standardize the structure of OOA analysis so that it can be accepted directly by OOP.

Object-oriented design (OOD) is a software design method and an engineering specification. There is no doubt about it. According to Bjarne Stroustrup, the object-oriented programming paradigm (Paradigm) is [stroustrup,97]:

Decide on the class you want:

Provides a complete set of operations for each class.

Explicitly use inheritance to show common ground:

By this definition, we can see that Ood is "deciding on the requirements of the class, the operation of the class, and the process associated with the class."

The goal of Ood is to manage the interdependence of parts within the program. To achieve this goal, Ood requires that the program be partitioned into chunks, each chunk should be small to manageable, and then hidden behind the pretext (interface), allowing them to communicate with each other only through interfaces. For example, if you use the Ood method class to design a server-client (client-server) application, then the server and the client should not be directly dependent, but should make the interface of the server and the interface of the client depend on each other.

The transformation of this dependency makes the parts of the system reusable. In the example above, the client does not have to rely on a particular server, so it can be reused in other environments. If you want to reuse a block, just implement the necessary interface.

Ood is a design paradigm for solving software problems (paradigm), an abstract paradigm. Using the design paradigm of ood, we can use objects (object) to represent the entities of the problem domain (problem domain), each with corresponding states and behaviors. We have just said that Ood is an abstract paradigm. Abstractions can be divided into layers, from very generalized to very special, and objects may be at any level of abstraction. In addition, different but interrelated objects can form an abstraction: As long as there is similarity between these objects, they can be treated as object classes of the same class.

cp2044-in-depth Java Web Project combat explaining (2 sets of practical projects)