Pagwin/BinghamtonBetterBus-v2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update GUIDELINES.md

Browse source
This commit is contained in:
Steven A Moore 2025-02-03 08:25:26 -05:00 committed by GitHub
parent 782c2f51e4
commit 7edca6abff
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
etc/GUIDELINES.md
View file

@ -1,9 +1,7 @@
# CS445: Software Engineering Guidelines
*A portion of your team's final project will be graded against these guidelines and specifications*
# CS445: Software Engineering Principles
1. Software breaks at the interfaces
* If you don't do a system architectural design with well-defined interfaces, integration will be a big mess.You must have some external system architecural design that is kept up to date with your current architecture.
* If you don't do a system architectural design with well-defined interfaces, integration will be a big mess. You must have some external system architecural design that is kept up to date with your current architecture.
2. Good software is in your head, not the computer
* Design, Design, Design, then design some more. You should spend at least as much time designing your code, before you write a single line, as you will spend coding.