AJAX online music website (1) requirements and functional structure, ajax online music

AJAX online music website (1) requirements and functional structure, ajax online music

Some time ago, according to the course schedule, an ASP was implemented. NET online music websites are not busy recently. They plan to record and summarize small projects in the past. One is to review the entire process of the project, and the other is to deepen their understanding of the technologies and tools used, third, reflect on the problems and solutions in the project process.

1. Website requirements:

1. Song display: After a user logs on to the homepage of the website, the song ranking, album ranking, and singer ranking are displayed;

2. User logon and registration: When a visitor wishes to become a user of our website to gain more permissions, the website provides registration and login;

3. Website song search: You can search for the songs you want to listen to by name, album name, or artist. Fuzzy search is supported;

4. listen to and download ranklist songs: You can listen to and download songs you are interested in to your local computer;

5. My favorites function: saves the songs you are interested in, so that you can try again after the next login;

6. The administrator maintains and manages tracks. The administrator can log on to the background to add, delete, and modify songs, albums, and singers on the website;

7. Authorized users: Administrators can authorize normal users to become administrators to maintain and manage website tracks together.

The website front-end provides functions such as Song display, user logon and registration, searching for website songs, audition and downloading ranking songs, and my favorites. The website background includes functions such as adding music as administrator, modifying music, modifying albums, modifying artist information, authorizing users, and exiting.

 

2. website performance requirements

To ensure the long-term, stable and efficient operation of online music websites, online music websites must meet the following six performance requirements:

1. Generally, the response time for page Jump operations should be within 3-5 seconds.

2. Generally, each data addition or deletion update should be within 2-3 seconds.

3. There must be a rapid response to the data received by the user and the accuracy of the received information.

4. The website operation methods should be flexible and the website operation pages should be friendly;

5. When a variable in the website runtime environment changes, the website must automatically and quickly adapt;

6. Quick response to changes in plans or requirements, and certain scalability of websites.

 

3. website function structure

A. The website front-end features song display, user login and registration, website song search, audition and download of ranking songs, and my favorites. Its function structure is shown in Figure 3.1:

Figure 3.1 functional structure of the music front-end

 

B. website background functions include administrator background logon, music addition, music modification, album modification, artist information, authorized users, and exit. Its function structure is shown in Figure 3.2:

Figure 3.2 line Music Background Function Structure

 

4. Main website function Process

A. The administrator maintains the website track process.

The administrator can enter the correct account and password in the logon area of the homepage to log on to the background of the online music website. If an incorrect account or password is entered, the Administrator will log on again. After entering the background page, the administrator can modify and delete the song, album, and singer information, and then the website will save the change information to the corresponding database table. The administrator maintains the website track 4.1.

Figure 4.1 website track maintenance Flowchart

 

B. Review and download of the List songs

Log on to the online music website, and you can search for your favorite songs and download them to your local computer. The list of songs can be listened to and downloaded in 4.2.

Figure 4.2 Process Diagram

Analysis of music website design requirements

Www.hao123.com/music.htm
Chapter 1 development overview
1.1: topic introduction:
1.2 Development Environment and requirements
1.3 introduction to ASP and Related Technologies
1.4 comparison between ASP and CGI
Chapter 2 Requirement Analysis
2.1: System Survey:
2.1.1 requirement survey on this site:
2.1.2 functional requirement analysis:
2.2: logical solution of the new system:
2.2.1 data flowchart
2.2.2 Data Dictionary
2.3 Feasibility Study
Chapter 3 overall website Structure Design
3.1 Design of the functional module structure of the website
3.2 Database Design
3.2.1 Concept Design of databases
3.2.2 logical structure design of the database
3.3 Webpage Design
3.4 webpage link navigation design
Chapter 4 Implementation of music star network
4.1 create an Asp running environment
4.2 Implementation of the default. asp page on the home page
4.2.1 implementation and call of the file dbconn. inc
4.2.2 implementation and calling of the file news. asp
4.2.3 online research. asp implementation and calling
4.3 Implementation of kqst. asp on the music audition page:
4.3.1 implementation and call of home_sort.asp:
4.3.2 demo call file mfplayrm. asp
4.4 Implementation of background management
4.4.1 Implementation of log on to login. asp through background management
4.4.2 Implementation of mnews. asp on the homepage of background management
4.4.3 Implementation of addnews. asp
4.4.4 implement xgnews. asp on the background
Chapter V system testing and outlook

Assume that you want to develop an online transaction platform website and describe the website based on three types of requirements:

Functional requirements (this function is extracted from my blog post. For details, refer to my blog)
1. B2C system function module
1.1 multi-level and multi-type permission management system
1.1.1. System Overview
1.1.2. System Structure
1.1.3. system flowchart
1.1.4. System database modeling (Part 1)
1.1.5. Member permission management system application.
1.2 B2C front-end Display System
1.2.1 The page layout of each front-end node needs to be located based on the company's SEO solution.
1.2.2. the foreground effect should be designed based on the user experience.
1.2.3 front-end artists must plan and design based on product features.
1.2.4. layout of the system file system.
1.2.5. Analysis of the Function of the root directory folder of the E-Commerce Station.
1.2.6. File structure of the E-Commerce Station System
1.2.7. E-Commerce Station Screen migration diagram.
1.2.8. E-commerce site merchant registration application process.
1.2.9. E-commerce site shopping process.
1.2.9. E-commerce site order handling process.
1.2.10. E-commerce site refund process.
1.2.11. E-commerce site product release process.
1.3. Extensive portal CMS management system
1.3.1. document CMS management system
1.3.2. Data download and video presentation platforms.
1.3.3. Announcement and advertising system.
1.3.4. image management system.
1.4. Website marketing management platform.
14.1 System Overview.
1.4.2. system structure.

1.4.3 system flowchart
1.4.4. System database modeling (omitted)
1.5 website Report Management System
1.6 Data Interface Platform
1.7. Database Modeling (pay attention to the database table structure for details)

Business needs and constraints depend on what type of e-commerce platform (B2B, B2C, O2O, ABC...) You are, what profit model you are, and what type of products you are making.