Before the project
Download as PPTX, PDF0 likes72 views
The document discusses best practices for gathering requirements and specifications for a project. It recommends digging for requirements by working with users, using simple notation that communicates well, and avoiding overspecification. Formal methods are described as just one tool among many that can be used, and expensive tools do not necessarily produce better designs. Writing detailed specifications comes with responsibility, and some things are better learned through implementation and testing.
1 of 8
Download to read offline
Before the project
- 1. Before The Project The Pragmatic Programmer Juan Manuel Rúa Trujillo
- 2. The Requirements Pit ● Don’t Gather Requirements—Dig for Them. ● A requirement is a statement of something that needs to be accomplished. ● Work with a User to Think Like a User.
- 3. ● UML use cases, so simple a child could do it! ● Don’t be a slave to any notation; use whatever method best communicates the requirements with your audience. ● Don’t Overspecify ● Many projects failures are blamed on an increase in scope
- 4. ● Use a Project Glossary ● Publish the project documents to internal Web sites ● You want to write them down and publish a document that everyone can understand.
- 5. Solving Impossible Puzzles ● The secret to solving the puzzle is to identify the real (not imagined) constraints, and find a solution therein. ● Don’t Think Outside the Box—Find the Box ● There Must Be an Easier Way!
- 6. Not Until You’re Ready Listen to Nagging Doubts—Start When You’re Ready Good Judgment or Procrastination?
- 7. The Specification Trap Writing a specification is quite a responsibility. Some Things Are Better Done than Described (Shoe example). A healthy development process encourages feedback from implementation and testing into the specification process.
- 8. Circles and Arrows ● Don’t Be a Slave to Formal Methods. ● Formal development methods are just one more tool in the toolbox. ● Expensive Tools Do Not Produce Better Designs