This repository was archived by the owner on Nov 3, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Bad Practices & Good Practices in Software Development
gozdeberk edited this page Feb 23, 2016
·
2 revisions
Most software projects fail but there are also successes. To be successful rather than fail, software developers should place importance on practices. Bad practices stem from the incomplete good practices. In other words, best practices address the root causes of poor software development.
Here is an outline of bad practices & good practices.
- Ambiguous communication
- Overwhelming complexity
- Insufficient testing
- Insufficient requirements management
- Undetected inconsistencies among requirements, designs and implementations
- Brittle architecture
- Develop iteratively
- Manage requirements
- Use component architecture
- Model software visually
- Verify quality
- Control change
Resources:
[Resource - The University of Texas at Austin] (https://www.cs.utexas.edu/~mitra/csSummer2014/cs312/lectures/bestPractices.html)
Resource - IBM
Resource - University of North Florida
- Project Description
- Project Video
- Themes/Features
- User Stories & Acceptance Criteria
- Personas
- Domain Analysis
- Requirements
- Initial Plan
- Diagrams
- Use Cases
- Peer Reviews
- Mockups
- Test Plan
- User Tests
- Test Web Project
- Meeting 1 - 16.02.2016
- Meeting 2 - 18.02.2016
- Meeting 3 - 3.3.2016
- Meeting 4 - 7.3.2016
- Meeting 5 - 11.3.2016
- Customer Meeting 1 - 28.03.2016
- Meeting 6 - 8.4.2016
- Customer Meeting 1 - 29.9.2016
- Customer Meeting 2 - 06.10.2016
- Meeting 7 - 06.10.2016
- Meeting 8 - 13.10.2016
- Customer Meeting 3 - 27.10.2016
- Meeting 9 - 27.10.2016
- Customer Meeting 4 - 03.11.2016
- Meeting 10 - 03.11.2016
- Meeting 11 - 10.11.2016
- Meeting 12 - 01.12.2016
- Meeting 13 - 08.12.2016
- Customer Meeting 5 - 08.12.2016
- Meeting 14 - 08.12.2016