In the previous article, we conducted a requirement analysis as follows:
1. Dynamic News Listings (this is simple)
2. You can read the news list in pagination (this is not difficult)
3. Can read a news list without refreshing paging (this is a bit difficult)
4. Can preview the content of the news (this is also a little bit difficult)
5. Friendly interface (this is necessary)
According to the sequence of software engineering, we should develop software according to this order: feasibility analysis = = = "Requirements Analysis = = =" Design = = = "detailed design = = =" "Code = =" Test
Since we are only a small part of the project, it is a good habit to develop it in almost the same order. We put together the outline design and the detailed design.
Let's design the database by using an Access database and the fields are relatively simple. On a table tb_news, the database is named News.
Column
Name Type length
news_id Long Integral type 4
News_title Text 255
News_content Memory-
News_time Date/Time 8
News_readtimes Long Integral type 4
Of course, you can add fields or reduce fields according to your needs. Which news_content as long as possible, in line with the length of the news.
After the database design is finished, we can start coding. First build the ASP.net project (I prefer the Web application rather than the website) and name it mynewslist. As shown in the following illustration: