Web server Analysis and Design (II.)

Object-oriented analysis and design the second step: finding the object and establishing the problem domain model

1, use case scenario Description

Connect to the use case in the previous article, write a use case scenario

U1:

Internet Users: Open website (www.xxx.com)

Browser: Connect Web site

Target system: Accept Connection

Check the legitimacy of the connection (mainly because the server is vulnerable, so you need to join the security check)

Legal, access connection, wait for HTTP request (illegal see alternative process)

Browser: send a GET request

Waiting for a reply

Target system: Get request Received

Handling GET Requests

Send back a request reply to the browser

Reply Complete, disconnect

Alternate process: The connection is illegal and disconnected.

U2

Internet users: Click the Submit button

Browser: Connect Web site

Target system: Accept Connection

Check the legitimacy of the connection (mainly because the server is vulnerable, so you need to join the security check)

Legal, access connection, wait for HTTP request (illegal see alternative process)

Browser: Send POST request

Waiting for a reply

Target system: Receive a POST request

Processing Post Requests

Send back post request reply to Browser

Reply Complete, disconnect

Alternate process: The connection is illegal and disconnected.

U3,u4 and U1,u2 basically like, no longer repeat.

U5 (because I'm not sure how the site was found, I referred to the new IIS site)

Site Publisher: Open the Publishing interface

Target system: Display Publishing interface

Website Publisher: Fill in the Site configuration (main target, port, etc.)

Confirm that the site is enabled

Target system: Start Web site

Start waiting for browser connection

(It suddenly occurred to the system to provide the functions of the management site, such as routine maintenance, etc., but it does not matter,

A "need review" has been conducted in the previous pass to ensure that our target system can fulfill important requirements. ）

2, use case scenario analysis: extracting objects

Using the method of the predecessor invention: the verb noun method. A noun in a process is likely to be an important entity object in the system.

U1 noun: Web Connection HTTP request Get request reply

U2 noun: Button connection HTTP request Post request POST request reply

U5 noun: Publishing Interface Site Configuration site

The possible objects are found, and what are the objects in the system?

The button is definitely not.

HTTP requests, get requests, and so on, are obviously objects in the system.

A connection is an entity that the client communicates with the system and is also an object of the system.

The publishing interface is the user interface that provides the publisher, as well as the object in the system.

What is the website? The essence is to receive the connection of the browser, is also the object in the system.

The site configuration may be an important property of the site.

3, object analysis, establishing type relationship

Analyze the commonality and modification of objects, and use classes to summarize them. The following is a class diagram drawn with ArgoUML.