Introduction to game software engineering

Software Engineering for game developers

Good books. It is unique in China. Game software engineering.
The original book provided a complete set of 3D games and code to describe a practical software engineering application.
The first few chapters in the book describe basic softwares. They are
1. Reduced number of players in the game field
2 Requirements
3uml Object-Oriented Programming
4. Software Design
5. Reusable Software Libraries
6 object-oriented fantasy and Practice
7. Design Mode

Practice at least one project (well... Not very successful ...), After chapter 1, some knowledge, including risk analysis, may become a treasure for not repeating the same mistakes. Who knows?

8

■ Defining risk as a category of software engineering as a category definition risk of Software Engineering
■ Establishing criteria to use for risk analysis establishes standards for risk analysis
■ Analyzing risks so that you can prevent them analyze risks to avoid them
■ Developing a risk management plan that is suitable for your setting to develop a risk management plan suitable for you
■ Tracking and controlling risk trace and control risks

9. Iterative Design

■ Learning the basics of iterating design basic knowledge
■ Selecting the right size components select a component of the proper size
■ Applying principles that are derived from object-oriented programming, refactoring,
Risk analysis, and patterns to your design effort is designed using object-oriented programming, refactoring, risk analysis, and principles in design patterns.
■ Using tively using the software design document effectively uses the software design document
■ Projecting plan considerations with iterative design efforts project plan considering Iterative Design
■ Testing on an iterative basis iteration-based test
■ Knowing when to break off an iterative effort knows when to break Iteration
■ Knowing when things have gone wrong knows when the direction is wrong

10 control disorder and configuration management

■ Establishing a culture for configuration Activities establishes a configuration activity Culture
■ Establishing policies for configuration practices establishes a configuration Practice Policy
■ Selecting tools for version control and Installation
■ Analyzing the design document to discover prospective directory structures and
File Names analysis design document to find the expected directory structure and file name
■ Setting up a build schedule
■ Creating baselines using the software design and the Project Plan use the software design and project scheduler home travel baseline
■ Arranging for disaster recovery
■ Creating ing with the creation of the installation package

11 art of testing

■ Identifying what counts as a defect defines Defects
■ Formalizing Testing
■ Creating documents to guide the test
■ The types of domain knowledge that testing involves Test types that contain the knowledge field
■ Using test reports and test templates test report and test template
■ Recognizing and guarding against coverage Risks identification and protection coverage risks
■ Efforts and effects of testing test results and effects

12 about the specification (numbers for nabobs)

■ Why metrics benefit software engineering efforts Why Software Engineering benefits from specifications
■ Preliminary concepts of elementary notions about software data
■ Preliminary concepts of elementary notions about software statistics software Statistics
■ Using Microsoft Excel as a tool for analysis use Excel as an analysis tool
■ Ways to display metrics display specifications
■ Approaches to refining metrics for your project: refine specifications for your project
■ Personalized metrics personalized specifications
■ Extended applications of metrics extended application specifications

13 Development Strategy

■ Defining a starting point for a project defines the start point of the project
■ Putting together a set of working principles
■ Documenting the product to be developed by developed
■ Documenting the Plan for Development Plan documented
■ Proceeding through reviews is reviewed
■ Introducing quality measures Quality Measurement
■ Making transitions from one project to another transition from one project to another

14 practices

... To be continued