Timeshare SystemArchitecture&Design
From PeacockWiki
| Revision as of 14:22, 17 October 2005 (edit) 210.84.47.55 (Talk) (→SYSTEM ARCHITECTURE) ← Previous diff |
Revision as of 14:34, 17 October 2005 (edit) 210.84.47.55 (Talk) (→SUB-SYSTEM DESCRIPTIONS) Next diff → |
||
| Line 7: | Line 7: | ||
| ==SUB-SYSTEM DESCRIPTIONS== | ==SUB-SYSTEM DESCRIPTIONS== | ||
| + | Clinton 17/10/2005 I am not sure in this section. A quote from Edward: | ||
| + | |||
| + | "In the java world the site contains an excellent overview ?? many of the same patterns apply in PHP. Eg Front Controller. | ||
| + | |||
| + | http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html | ||
| + | |||
| + | To properly round out your sys arch document you need to take one use case and describe how the general patterns have been applied that usecase." | ||
| + | |||
| + | 2 things: | ||
| + | 1. Is the system architecture diagram in these guidelines?? I don't understand if it is or not. | ||
| + | 2. I do not know where to start when I take "one use case and describe how the general patterns have been applied [to] that usecase." What needs to be said here, and how much detail do we go into?? | ||
| + | |||
| ==SOFTWARE DESIGN OVERVIEW== | ==SOFTWARE DESIGN OVERVIEW== | ||
| ==SOFTWARE DESIGN DETAILS== | ==SOFTWARE DESIGN DETAILS== | ||
Revision as of 14:34, 17 October 2005
Contents |
DEVELOPMENT TOOLS & DEPLOYMENT ENVIRONMENT
Clinton 17/10/2005 I think this needs no more information. Says "When the system is complete, it will run on linux, but has not been tested in this environment yet". Not sure if we need to mention it is currently running in a Linux environment??
SYSTEM ARCHITECTURE
Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!
SUB-SYSTEM DESCRIPTIONS
Clinton 17/10/2005 I am not sure in this section. A quote from Edward:
"In the java world the site contains an excellent overview ?? many of the same patterns apply in PHP. Eg Front Controller.
http://java.sun.com/blueprints/corej2eepatterns/Patterns/index.html
To properly round out your sys arch document you need to take one use case and describe how the general patterns have been applied that usecase."
2 things: 1. Is the system architecture diagram in these guidelines?? I don't understand if it is or not. 2. I do not know where to start when I take "one use case and describe how the general patterns have been applied [to] that usecase." What needs to be said here, and how much detail do we go into??
