[Software engineering knowledge]

1. Each aspx webpage is directly or indirectly inherited from the system. Web. UI. Page class in the class library.
2. C #2.0 provides distributed class writing, which allows the definition of classes to be dispersed into various code snippets.

Requirements: 1) as long as the same namespace and class name are used in each file, and the partial modifier is added before the definition of each class, the compiler automatically compiles these files together to form a complete class.

1. The common links in class are:
   1) Generalization)
   In a word, it is an inherited representation of the is-a relationship. Use a solid line with arrows to point to the parent class.
   2) Dependency)
   In a UML class diagram, dependency is a usage relationship. It indicates that the change of one thing specification may affect another thing that uses it. Otherwise, it is not.
   The dependency is directed to the interface with a dotted line with arrows. It is a use-a relationship.
   3) Association)
   Describes the connection between a class and a class. It is a link between has-.
   4) Aggregation)
   Aggregation is a special case of association. If the relationship between a class and a class has the characteristics of "whole and local", the relationship is set. It often means "containing..." "containing.
2. Some knowledge about. net
   . NET Framework SQL Server ADO. Net winform HTML CSS Javascript
   Xml dtd Schema
   ASP. NET jquery Ajax
   MVC2 mvc3
   ADO. NET Entity (EDM)
   LINQ Lambda expression
   Ria: Silverlight
   UML: Unified Modeling Language
   Design Pattern
   Project management. SDP
   Testing deployment
   Professional Quality
   Project development with full process

Software development process and tasks at various stages
Phase	Key Issues	Termination criteria
1. Problem definition	What is the problem?	Reports on scale and objectives
2. Feasibility Study	Is there a feasible solution?	High-level system logic model Data Flow Diagram Cost/benefit analysis
3. Requirement Analysis	What must the system do?	System logic model Data Flow Diagram Data Dictionary Algorithm Description
4. Overall Design	In summary, how should we solve this problem?	Possible solutions System flowchart Cost/benefit analysis Recommended System Structure Level chart or structure chart
5. Detailed Design	How to implement this system	Encoding specifications Hipo diagram and PDL Diagram
6 coding and unit testing	Correct program module	Original program list Unit Test Plan and Result
7. Comprehensive Test	Compliant software	Results of the Overall Test Plan Complete and consistent software configuration
8. Maintenance	The system can run smoothly for a long time.	Software Issue Report Software Modification report