User Management System Object-Oriented Implementation Development Plan
User Management System For Objective Destination: To better learning and practice object-oriented programming ideas, better to learn from each other with the majority of ASP.NET programming enthusiasts, I initiating open source joint development to implement a reusable user management system. Participants: Any interest-interested ASP.NET programming enthusiasts can participate, implement as the main body with VC # (because I can use C #, other languages can also participate, but the form is negotiable.) Participation: By mean Development procedure builds a framework, and participants are designed and implemented under the framework. Two kinds of framework are two: one is to write a test case, which specifies the framework of the class name, class interface, and its object relationship. Participants are only responsible for the specific code implementation or on this basis. The other is a fully open frame, only restricts the participant's development steps, and does not limit the implementation of ideas. Development steps: 1, user interface modeling, clear demand. Write a flow chart. In the login / interfacemodel directory 2, the reference routine will learn from the process of learning others. In the Login / Development Document / StudyExmple directory 3, the design class structure, determine the relationship between the interface and the object. Draw a UML map. Under the Login / Development Document Directory 4, quickly establish an object relationship model. In the login / quicklybuildmodel directory 5, write the test case code. Under the login / test directory 6, the code is implemented. 7. Discuss the excellent design ideas, extension. 8. Improve design, reconstruction implementation. 9, optimize the code. Overall requirements: Try to use object-oriented ideas, everything is an object. The code is elegant, it is best noted that it is easy to discuss. My development schedule: 1. Modeling, clear demand. Write a flow chart. ...... 1 day is expected to complete the 2, reference routine, learn from the realization process of others on June 28. ... 1 day is expected to complete the relationship between the 3, design class structure, determine the interface and objects on June 29. ... 1 day is expected to complete 4, quickly establish an object relationship model on June 30. ...... 2 days is expected to complete 5, write test use code code on July 1. ...... 2 days is expected to complete 6, code implementation on July 3. ... 2 days is expected to complete the ******************************************************************************* ********************** The above is a phase, released the source code to my forum http://www.ttly.net/study and netizen They communicate. *********************************************************** ************* 7, discuss the design idea, the extension. 8. Improve design, reconstruction implementation. 9, optimize the code.
