Application for booking rooms for Hotel -- 2
Budget: $10 – $30 USD
Semester project requirements
The semester project should meet the following criteria:
it should be an application with graphical UI (Win Forms, WPF, Xamarin...), console applications only in justified cases after approval by the trainer
the naming conventions in .NET should be followed
all classes, variables, etc. should have a clear and descriptive name
the code is clearly formatted
the code does not contain long methods
the project does not contain "dead code"
each method performs only one action
the code is well and meaningfully commented
the code does not contain outdated comments
the code does not contain unnecessary comments
the data and the operations that work with that data are part of the same class
all non-constant data attributes are defined as private (accessed by method or as a property)
in heredity, the relationship between ancestor and descendant is "is"
the code is meaningfully covered by unit tests (optional!)
all unit tests pass successfully
the application is divided into layers (the presentation part is separated from the application logic)
there are no anti-patterns/odors in the code, e.g.:
there are no "magic constants"in the code
there are no "divine objects"in the code
the "hiding errors"anti-pattern is not used
etc.
The semester project should meet the following criteria:
it should be an application with graphical UI (Win Forms, WPF, Xamarin...), console applications only in justified cases after approval by the trainer
the naming conventions in .NET should be followed
all classes, variables, etc. should have a clear and descriptive name
the code is clearly formatted
the code does not contain long methods
the project does not contain "dead code"
each method performs only one action
the code is well and meaningfully commented
the code does not contain outdated comments
the code does not contain unnecessary comments
the data and the operations that work with that data are part of the same class
all non-constant data attributes are defined as private (accessed by method or as a property)
in heredity, the relationship between ancestor and descendant is "is"
the code is meaningfully covered by unit tests (optional!)
all unit tests pass successfully
the application is divided into layers (the presentation part is separated from the application logic)
there are no anti-patterns/odors in the code, e.g.:
there are no "magic constants"in the code
there are no "divine objects"in the code
the "hiding errors"anti-pattern is not used
etc.