Write a simple server for yourself.
Object-oriented analysis and design the first step : Get requirements (based on use cases)
features : 1, support HTML static Web page, 2, support common HTTP request, and easy to extend support is not now requested 3, can publish the site
Add : For advanced features such as dynamic Web pages, just make sure that extensibility is available.
Target system Client role : 1, surfer 2, browser client 3, website publisher (temporarily think of the main roles)
As long as they meet their main needs, this server is also successful.
Customer initiated action (use case start): U1: Internet users------> Open website (www.xxx.com)
U2: Internet users------> Submit form a
U3: Internet users------> download File a
U4: Internet users------> click the x Link (and the first one looks the same)
Browser client is just the user's request agent performer, and the server directly interact, so the above initiating action, will certainly overwrite the browser
Action, so you don't have to list it.
U5: Website publisher------> Open Publishing Interface
Requirements Review : The execution path represented by U1 can override function 1, function 2
U2 override function 2
U3 override function 2
U4 coverage function 1, function 2
U5 override function 3
Conclusion: All functions are embodied in the use case, so long as the system realizes these use cases, the function points are completed.