Software Development Outline (specific adjustments to the actual situation)

Software Development Outline, specific adjustments to the actual situation
==========================================
Encoding specification:
Strings are stored in the database.
Database Table: lowercase and underlined words
Uppercase SQL statement keywords
Try to use the stored procedure without hard coding the SQL script into the program (except for using the LINQ technology)
Hierarchical Structure of project source code
If the system needs to directly access a third-party database, try to create the SQL synonym and view views, which are less coupled with them.
There are obvious business modules in the project, and each module is relatively independent. Try to distinguish between the source code structure and database table name prefix.
The source code is divided by "module \ component" (for example, analysis service \, website \; finance and customer of business components under website)

Development Environment:
Development Environment configuration: testing machine, development machine, server (quantity, configuration parameters)
Program source code directory structure (Database Script directory [Create Table, initialize data], public code directory, documentation, source code, class library, tools, etc)
Main project interface style
SVN
List of software to be developed (Vs, SQL Server, and third-party components (may need approval ))
Bugzilla

Communication Method:
Contact information (mobile phone, name, email)
Email
Phone number
If the document version is updated or key components (shared component updates) are notified by email
Communication information is stored in the project folder

Staffing:
Artist
Development
Test
Database Management

Document Writing:(Define the document format: font, home page, directory, and version description)
System User Manual
Deployment document
Overview design (host configuration: development environment and product environment)
Detailed Design
Requirement document
Storyboard
Main module design (interface, interface, function description)

Start development:
Code Review
Test Case writing
Module function discussion meeting

Design phase:
You can use Windows Service (self-developed), SQL Server Agent (SQL operation), Windows Task Plan + self-developed programs to schedule tasks.

Preparations:
Prepare reference materials required for project development and put them in the study folder for reference by the team members.
Define the format of the requirement document (the development team carefully confirms the requirement, communicates with the customer repeatedly), and generates a complete requirement document, develop requirement change control (the customer submits the change request email-> the development team analyzes the impact scope of the change and determines the workload (select change items) -> the development team reports the superior and the customer's change cost-> the customer and the superior determine the change-> the customer updates the requirement document and sends it to the development team-> the development team implements the change-> both parties confirm the change)
Prepare and conquer the technologies needed (filter or postpone the functions that cannot be implemented by the current technology or Schedule)
Human resource arrangement and role allocation
The artist designs the product's main interface and display style as needed (repeatedly confirms the interface and interface design with the customer)
Develop appropriate development cycles (requirements, development, testing, UAT phase; version delivery milestones; Acceptance Criteria) delivery Plan, after-sales service period and scope (modify existing products reasonably without adding new functions)
Leader prepares reusable parts of existing development projects or technologies, and prepares the project development structure and reusable components) to improve development efficiency as much as possible.
Establishes an automatic deployment mechanism to synchronize development and test code and reduce deployment time.
Definition of database table structure, generating script files and documents
Submit the research results report (What are the features of the study object, the role of the study object on the project, how to use it, the current issue, refer to the Documentation)
Create a Project software library. All development tools, third-party components, and their associated documents are stored in the project group software folder.
Prepare the development environment and communication methods in advance

New Employee Training Questions:
Formulate the primary guidance staff for newcomers, preferably 1-to-1
View work results on a regular basis, even if the problem is corrected

Under development:
Update the tool functions and module functions of the project members at any time (synchronize the project status and the latest technology to the entire team)
Pay attention to the code quality and conduct code review in the early stage to standardize the description of the source code check-in.
Pay attention to the following aspects for testing: Product interface, business logic, data correctness, and product performance; learn to use SQL profiler to verify the SQL access performance of each operation if necessary
Regular communication (such as in the form of dailymeeting): report the development progress, current problems, determine the next plan, test report the test status, completed test tasks
Set the deployment time, submit the test and verification, and synchronize the current development progress and quality.

Common functions:
Verification and Security
Logs
Permission System