[Bibliography 20150303] The nature of software engineering: using the Semat kernel

Translator sequence
Robert Martin Preface
Bertrand Meyer Sequencing
Richard soley Sequencing
Objective
Thanks
The first part of the kernel thought explanation
The 1th chapter briefly describes how to use the kernel
1.1 Why developing excellent software is a big challenge
1.2 Understanding the nature of software engineering: the kernel
1.3 Applying the kernel to address specific challenges: an example
Key points of the 1.3.1 entry problem
1.3.2 Handling Challenges
1.4 Learn how to use the kernel to handle development challenges
The 2nd chapter on the kernel of some more details
2.1 How to use the kernel to handle specific challenges: an example
2.2 Alpha Introduction
2.3 Alpha Use Status Help team make progress
2.4 More about kernel content
3rd Chapter Overview of the complete kernel
3.1 Core Organizational structure
3.2 Things that are essential for progress and evolution: Alpha
3.3 What is the essence of doing things: activity space
3.4 Essential functions Required: capacity
3.5 More about kernel content
The 4th chapter uses cards to make the kernel alpha more specific
4.1 Using cards to help address specific challenges: an example
4.2 Activating the kernel.
5th. Learn more about kernel details through practice
5.1 Make practice Clear
5.2 Degree of certainty of practice
5.3 Building methods from practice
5.4 Learning methods and practices
6th Chapter What the kernel can do for you
6.1 Developing Software Excellence
6.2 Growth
6.3 Learn
6.4 Evolution
Extended Reading
The second part uses the kernel to run an iteration
7th. Running iterations using the kernel: Plan-execute-check-adjust
7.1 Terminology used
7.2 Plan-Perform-check-adjust
7.3 Setting the scene
7.4 Key points in the following chapters
The 8th chapter plans one Iteration
8.1 Using the Alpha status guidance program
8.1.1 Determine the current progress
8.1.2 determine the next work target
8.1.3 determine how to accomplish a goal
8.2 Determining the current status
8.3 Determining the next state
8.4 Determining how to reach the next set of States
How the 8.5 kernel can help you with iterative planning
9th. Execution and Inspection iterations
9.1 Using the kernel to perform and check iterations
9.2 Perform and examine the iterations in our story
9.3 How the kernel helps you perform and check iterations
The 10th chapter adjusts the working mode
10.1 Using the kernel to adjust how you work
10.2 Adjusting the way we work in our stories
10.3 How the kernel can help you adjust how you work
10.3.1 Clear working methods
10.3.2 Improving working methods
11th. Run an iteration with a clear requirement item state
11.1 Complete work with clear requirements
11.2 Planning the iterations in our story
11.3 Doing another iteration of our story
11.4 Adjusting the way we work in our stories
11.5 Discussions
Extended Reading
The third part uses the kernel to run a software development work
The 12th chapter runs a software development work: from idea to Operation
12.1 The characters in our story and the challenges they face along the journey
12.2 Understanding the Organizational environment
13th. Create a business case
13.1 Getting ready to start our story
13.2 Understanding opportunities and stakeholders
13.3 Understanding the Solution
13.4 Preparatory work
13.5 Develop an outline plan
13.6 Build time schedule
How the 13.7 kernel can help you get started
13.7.1 hug your stakeholders.
13.7.2 Guide Development
13.7.3 Pre-planned
14th Chapter development system
14.1 Build a skeleton system--Let it work
14.2 Stakeholder participation
14.3 Start Development
14.4 Establish a working approach that is recognized by all parties
14.5 making the skeleton system available--making the system work better
14.6 keeping stakeholders engaged
14.7 evolution of an available system
14.8 find a good way to work
14.9 evolve to a deployable solution-end work
14.10 Through acceptance
14.11 Ready to deliver
14.12 Complete! Complete development work
14.13 how the kernel can help you develop superior software
15th. Operating Software
15.1 Setting up a scene
15.2 on-line-successfully deploy the system
15.3 Deployment of the system
15.4 handover between two teams
15.5 support system until it retires
15.6 The end of our story
Extended Reading
Part IV using the kernel to scale development
16th, what does scale mean?
The 17th chapter refines the kernel to provide more details
17.1 "practice" becomes accurate for inexperienced members
17.2 Example: the practice of demand acquisition
17.3 Example: Practice of acceptance testing
17.4 Understand how the practice works together
17.5 value of "clear practice"
The 18th chapter expands the kernel to fit different types of software development
18.1 agreed practices that need to be used
18.2 Adapting to your development life cycle
18.3 incrementally build a method during development
18.4 methods in a large organization
18.5 Let the team control their approach
19th. Scaling up the kernel for large-scale complex software development
19.1 examples of large-scale software development
19.2 using alpha to organize work
19.3 visual development with Alpha method
19.4 using alpha to coordinate development teams
19.5 Let team members participate in the scale of the kernel
Extended Reading
Part V How the kernel changes the way you use your work
The 20th chapter considers and does not consider the method
20.1 Constant Thinking methods
20.2 better than that.
The 21st Chapter Agile Application Method
21.1 is the entire team, not a small number of people have methods
21.2 focus on method use trumps synthetic method description
21.3 evolving the team's approach rather than keeping the method constant
Where is the part six really new?
22nd Chapter Reconstruction Method
22.1 is not lack of methods, the lack of the foundation--Kernel
22.2 Core value of practicality
The 22.3 kernel is an actionable, extensible
The 23rd chapter applies the principle of separation of concerns in the method.
23.1 separating the kernel from practice
23.2 separating Alpha from work products
23.3 separating the essence from the details
Chapter 24th Key Distinctions
24.1 Innovations in methodology
24.2 Practical tools for software development teams and professionals
Part VII Conclusion
The 25th chapter is not the end.
The 26th chapter ... but now may be the end of the prologue
The 27th chapter of the realization of the vision
27.1 for Software professionals
27.2 for Industry
27.3 for Academia
27.4 exciting Future
Extended Reading
Appendix
Appendix A Concepts and Symbols
Appendix B The contents of this book are compared to the kernel differences
What the B.1 kernel and the book contain
The B.2 kernel does not contain content that is included in this book
B.3 kernel contains content that is not included in this book
Appendix C Reference Documents
C.1 Semat Work Literature
C.2 SEMAT: Other documents and references
C.3 Other references
Author Introduction
Industry insiders ' comments on this book
Index

[Bibliography 20150303] The nature of software engineering: using the Semat kernel