"Demand analysis and system design" reading notes three

This one is mainly about interface design, which we also learned in the human interaction course. The design of the GUI is not mentioned in several other books. And this part is not the same as in the "Man-machine interaction". This chapter describes the UML configuration file (section)--ux storyline. The design of the graphical user interface should be based on the user's point of view.

The eighth chapter introduces the importance of the database. The database plays a vital role in software development. The database model consists of 3 levels: an external model, a logical model, and a physical model. This chapter focuses on the logical model. Object-to-database mapping is actually the mapping of the UML type model to the logical data model in the relational database. A transaction is a logical unit of work for a database that begins with a consistent state of the database and is guaranteed to be consistent at the end of it. Transactions can handle database concurrency and database recovery. The traditional database application system requires short transactions, while some new database application systems work on long transactions.

Quality and change management activities span the entire development life cycle. They require specialized documentation, such as test plans, test case documentation, and failure and improvement documentation. The test document identifies the test requirements and then connects the test requirements to the use case requirements in the use case documentation. There are two very orthogonal aspects of quality management. Used in the quality control mechanism is always passive, but when used to test drive development framework, it can be very proactive quality assurance activities. Quality control is related to system service and system constraint testing. System service tests can be static or dynamic. Static testing includes walk-through and review-a formal review meeting in the practice of quality assurance. Dynamic testing can be a test of the code for the specification. System constraint testing consists of a large number of related different tests. A change request that is usually made is either a processing failure or a process improvement. In the Change management tool, you can submit a change request and track what the developer has done with it. The main function of the Change management tool is to establish a recoverable path between the change request and other system artifacts, especially test requirements and use case requirements.

At the end of the book is a summary of the whole book. Use this example of online shopping to demonstrate all the important steps of demand analysis and system design. These steps are divided into 9 consecutive topics: 1. Use case modeling 2. Activity Modeling 3. Class Modeling 4. Interaction Modeling 5. State Machine Modeling 6. Implementation Model 7. Collaborative Design 8. Window navigation design 9. Database design.

This book reinforces our understanding of what we are learning from testing and practicing. There are examples of combinations that are easier to understand than just theoretical things. By doing exercises to consolidate and deepen the understanding of the content. This book focuses on the UML modeling, on the basis of the original learning more understanding.

"Demand analysis and system design" reading notes three