zhouzb2007 / best-practice-software-engineering Goto Github PK

Please add java doc to all interface, classes and methods in order make the
review of new code easier

Die Information ob ein Student ein Tutor ist wird als Boolean Attribut beim
Student hinterlegt

e.g. ref. to TU-Wien, to Book (Springer), Blog ...

Design Patterns are currently in Scratchpad; should be moved to main
directory; plus 

* update documentation page
* create download

Erik will code everything in English in his bpse-wicket-medium version. 
Kristof  will take Erik's DB script and mod his DAOs after that.

Developers ---> all in Master POM

Remove old JSF Documentation. The new example use Wicket instead of JSF

HTML/XML Export Test fails

In the documentation different file formats and styles are used (xdoc, apt,
etc.) We should agree to only one format and use this format.

Any suggestions?

Provide a simple example that illustrates the louse coupling in Java Systems.

Technologies:
- JMS and Active MQ
- Perhaps Mule as an Enterprise Service Bus

This could be implemented in an advanced example or as a seperate example.

Die gesamte Persistenzlogik, welche sich zur Zeit im Medium befinden in das
Core verlagern. (Mapper, Konfiguration)

Several forms... (that were originally part of the book-appendix) have to
be added to the documentation.

Medium Doku -> Example Requirements Spezifikation (PV & PA)
Review von DW, Mail von EG

Check Doc Page "Development Setup" (EG)

create a service layer

Add a new page, that explains distributed SCM briefly with Mercurial examples

connect Unit Tests and Integration Tests in bpse-wicket-sample

New Web-App Example using Wicket as discussed in Wiki

create an archetype

create a Wicket View for each DAO (CRUD)

Verwendung von JDBC Informationen (Driverclass, Datenbankname, 
Username, etc.) sollte man in eine Properties Datei auslagern (jdbc.properties) 
und über den PropertyPlaceHolder in den Spring Konfigurationen befüllen. So 
mischt man Infrastrukturinformationen mit spezifischen Informationen wie 
DB, etc.

Review des Pattern Abschitts der BPSE Website

Umlauts are not displayed properly on Windows (UTF-8 vs. ISO-8859-1)

http://best-practice-software-engineering.ifs.tuwien.ac.at/repository/

Build (Basic) creates Warnings

Don't know if it's possible. The actual structure is
examples
  - advanced
  - basic
  - core
  - designpatterns
  - documentation
  - medium

is it possible to extract the whole documentation from the examples? This
was done, because of Maven Site generation. I think it's better for
maintainance to seperate documentation and source code. Perhaps for the future

GUI Mockups for the new Medium Example with Wicket. Provide GUI screens for
the new medium example. These Mockups will be implemented with Wicket

Wicket Security mit Markus, Andi Pieber besprechen (EG)

create a Wicket Test for each Wicket Webpage

Update the AOP Documentation

Add additional information about Dependency Injection
JSR Standard:
http://jcp.org/en/jsr/detail?id=330

dbUnit DBTestvorgehensweise einbauen

Create/Upate Readme.txt in root

Add basic Wicket documentation

JTidy Plugin was included, cannot be found on repository servers.

What is this Plugin good for?

Update Basic example as discussed at Wiki-page

Write Testcases for all Model classes of bpse-sample-core (Student, Exam, 
etc...)

What steps will reproduce the problem?
1. In the left side menu, under 'Software Patterns' select 'Fundamental'
2. In the left side menu, under 'Software Patterns' select 'Architectural'

What is the expected output? What do you see instead?
When selecting the 'Fundamental' overview link, I expect to see the 
'Fundamental Design Patterns' page.
When selecting the 'Architectural' overview link, I expect to see the 
'Architectural Patterns' page.

What version of the product are you using? On what operating system?
Last Published: 2013-10-04, Version: 1.0
OSX

Please provide any additional information below.

BPSE QS Doku: Wie gut sind die Tests? -> eclEmma (Code-Coverage)