Asp. NET application planning and design (1)

Asp.net| Program | planning | Design Summary: Learn how to plan and design asp.net applications. This paper takes a knowledge base WEB application as an example to discuss some of the most common factors in the practice of practical application creation.

Brief introduction

This is a series of articles that we will step through in detail on how to design, implement, and deploy a typical WEB application using Microsoft ASP.net and Microsoft Visual Studio.NET. To explore some of the most common factors in the practice of practical application creation. We're not just setting up some Web forms, it's not limited to just some data binding on the back-end database. Data binding and Web forms layout are important, but there are a number of other issues that are important.

For example, regardless of the target platform or language, all well coded projects include basic planning steps, such as goal statements, user scenario documents, and even architectural documents that identify the physical and logical boundaries of the solution. In addition, it is a good practice to include security planning early in the solution lifecycle. Together with a good database model, well-designed middleware components, and a concise user interface design, this content ensures that the applications you end up deploying in production are secure, reliable, and user-friendly.

At this point, some readers may think that this article belongs to some of the most keynote articles, targeting at some very large enterprise-class solutions that do not apply to ordinary small factories, enthusiasts or individual development groups. Not really! Even if you're just creating a small, web-based solution for your own personal use, a well-developed plan from the start will help ensure that the process is ultimately easy to implement and deploy. Also, it is not advanced programmers or WEB developers who can use these technologies. Regardless of your skill level or your target audience, I'm sure you'll find this series of articles helpful, it gives you a wealth of information, and (let me say this) is very interesting.

We will build a sample repository Web application called DotNetKB, which will run through the entire series of articles. In this article of the first article, we will cover the design phase of a typical project, including basic planning, application architecture, and implementation design. By the end of this article, you'll have all the documentation ready and you'll be eager to start creating the solution.

The preparation is very simple, we skip this part and go directly to the first step of "Application planning."

Planning basic asp.net applications

The first step in creating a web-based asp.net application using Visual Studio. NET is to develop a basic application plan (AP). Planning is essential not only for large solutions built by multiple developers, but even for the smallest applications, a sophisticated AP is important. Creating an AP helps you to think about some common problems before you start coding "before". This allows you to fully understand the challenges and solutions in the early stages of the application lifecycle, rather than finding problems after a total embarrassment. In the book Software Project Survival Guide, the author, Steve McConnell, points out that the cost of correcting errors later in a software project is 50-200 times more than the cost of discovering and correcting them at an early stage.

What is included in a comprehensive project plan? Can contain a lot of content, but the most basic is to include the target statement and a series of user scenarios. There are a number of other useful materials, including requirements documentation, coding standards, delivery schedules, testing processes, and more. For the simple example solution we are going to build, we will focus on simple application declarations and some user scenarios. Some other issues will also be addressed.

Application Declaration

The project to be built in this series, called DotNetKB, is a simple knowledge base Web site where users can ask questions and receive an authoritative "expert" answer. As a result, visitors can search and filter the resulting data as they look for solutions to common asp.net problems.

This is a basic goal statement for our DotNetKB project. DotNetKB is a web-based application that lists a list of questions that visitors have raised and shows the authorized expert's response to these questions. Visitors can add new problems to the system and can search for and filter these issues according to the subject matter, questions, and/or keywords in the answer. Visitors can also sort the list of issues by topic or by date added to the system.

Authorized experts can log in to the security-enabled section of the application, review the issue, add, edit, and delete one or more answers to one question. Application administrators can also establish expert logon rights and logon profiles, as well as add, edit, and delete issue topics.

In addition, some basic statistics are provided, including the number of questions and answers in the system, as well as the number of responses per expert and the number of pages that have been visited so far.

As you can see from the above statement, the solution is simple. As you read the goal statement, you may begin to consider many other features that you can add to this application to make your application more powerful. This illustrates one of the main grounds for a project's goal statement, which is to avoid "functional sprawl". We all know that if we change the concept that the end result is based on, simple ideas will lead to very large and distorted results. There is an old adage: "If you don't know where you're going, you might stop somewhere," which originally revealed a summer road trip, which is also useful for software projects.

Some projects may need to include more information in their target declarations. For our use, the above goal statement meets the requirements. Now that we have a clear understanding of the application to be completed, we need some detailed information to describe how users interact with the system and what tasks users need to perform to accomplish their goals. We need a range of user scenarios.