Timeshare SystemArchitecture&Design - Revision history

Trevorp at 06:55, 25 October 2005

2005-10-25T06:55:39Z

←Older revision		Revision as of 06:55, 25 October 2005
Line 1:		Line 1:
	==Development Tools & Deployment Environment==		==Development Tools & Deployment Environment==
-	Clinton 17/10/2005	+	<div id="comment">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??	+	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??</div>

	==System Architecture==		==System Architecture==
-	Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!	+	<div id="comment">Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!</div>

-	Clinton 18/10/2005 After meeting with Edward, need to mention smarty is being used. Also need to add smarty needs to be installed?? I am not sure of this?? After talking to Trevor after meeting, smarty is part of the system?? It is being installed when we install the system??	+	<div id="comment">Clinton 18/10/2005 After meeting with Edward, need to mention smarty is being used. Also need to add smarty needs to be installed?? I am not sure of this?? After talking to Trevor after meeting, smarty is part of the system?? It is being installed when we install the system??</div>

	==Sub-System Descriptions==		==Sub-System Descriptions==
-	Clinton 17/10/2005 I am not sure in this section. A quote from Edward:	+	<div id="comment">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.		"In the java world the site contains an excellent overview �?? many of the same patterns apply in PHP. Eg Front Controller.
Line 19:		Line 19:
	2 things:		2 things:
	1. Is the system architecture diagram in these guidelines?? I don't understand if it is or not.		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??	+	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??</div>

	==Software Design Overview==		==Software Design Overview==
-	Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??	+	<div id="comment">Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??

-	Everything else is fine. Thanks again Trevor for updated ERD!!	+	Everything else is fine. Thanks again Trevor for updated ERD!!</div>

-	Clinton 18/10/2005 After meeting with Edward, we need to consider how the ERD may look. Do we keep iot the way it is, with the layout being landscape, or do we keep to the "rule of 7"?? I think if we can break up the diagram into 2, maybe 3 chunks (timesheets, statusreports, other??), then this would be easier to read, and in the end, more marks.	+	<div id="comment">Clinton 18/10/2005 After meeting with Edward, we need to consider how the ERD may look. Do we keep iot the way it is, with the layout being landscape, or do we keep to the "rule of 7"?? I think if we can break up the diagram into 2, maybe 3 chunks (timesheets, statusreports, other??), then this would be easier to read, and in the end, more marks.</div>

	==Software Design Details==		==Software Design Details==
-	Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.	+	<div id="comment">Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.</div>

-	Clinton 18/10/2005 Trevor and I will meet Saturday 22 October 2005 to complete use case 6.	+	<div id="comment">Clinton 18/10/2005 Trevor and I will meet Saturday 22 October 2005 to complete use case 6.</div>

Trevorp: remove caps

2005-10-25T06:36:17Z

remove caps

←Older revision		Revision as of 06:36, 25 October 2005
Line 1:		Line 1:
-	==DEVELOPMENT TOOLS & DEPLOYMENT ENVIRONMENT==	+	==Development Tools & Deployment Environment==
	Clinton 17/10/2005		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??		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==	+	==System Architecture==
	Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!		Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!

	Clinton 18/10/2005 After meeting with Edward, need to mention smarty is being used. Also need to add smarty needs to be installed?? I am not sure of this?? After talking to Trevor after meeting, smarty is part of the system?? It is being installed when we install the system??		Clinton 18/10/2005 After meeting with Edward, need to mention smarty is being used. Also need to add smarty needs to be installed?? I am not sure of this?? After talking to Trevor after meeting, smarty is part of the system?? It is being installed when we install the system??

-	==SUB-SYSTEM DESCRIPTIONS==	+	==Sub-System Descriptions==
	Clinton 17/10/2005 I am not sure in this section. A quote from Edward:		Clinton 17/10/2005 I am not sure in this section. A quote from Edward:

Line 21:		Line 21:
	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??		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==
	Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??		Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??

Line 28:		Line 28:
	Clinton 18/10/2005 After meeting with Edward, we need to consider how the ERD may look. Do we keep iot the way it is, with the layout being landscape, or do we keep to the "rule of 7"?? I think if we can break up the diagram into 2, maybe 3 chunks (timesheets, statusreports, other??), then this would be easier to read, and in the end, more marks.		Clinton 18/10/2005 After meeting with Edward, we need to consider how the ERD may look. Do we keep iot the way it is, with the layout being landscape, or do we keep to the "rule of 7"?? I think if we can break up the diagram into 2, maybe 3 chunks (timesheets, statusreports, other??), then this would be easier to read, and in the end, more marks.

-	==SOFTWARE DESIGN DETAILS==	+	==Software Design Details==
	Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.		Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.

	Clinton 18/10/2005 Trevor and I will meet Saturday 22 October 2005 to complete use case 6.		Clinton 18/10/2005 Trevor and I will meet Saturday 22 October 2005 to complete use case 6.

137.166.4.130: /* SOFTWARE DESIGN DETAILS */

2005-10-18T02:49:38Z

SOFTWARE DESIGN DETAILS

←Older revision		Revision as of 02:49, 18 October 2005
Line 30:		Line 30:
	==SOFTWARE DESIGN DETAILS==		==SOFTWARE DESIGN DETAILS==
	Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.		Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.
		+
		+	Clinton 18/10/2005 Trevor and I will meet Saturday 22 October 2005 to complete use case 6.

137.166.4.130: /* SYSTEM ARCHITECTURE */

2005-10-18T02:48:49Z

SYSTEM ARCHITECTURE

←Older revision		Revision as of 02:48, 18 October 2005
Line 5:		Line 5:
	==SYSTEM ARCHITECTURE==		==SYSTEM ARCHITECTURE==
	Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!		Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!
		+
		+	Clinton 18/10/2005 After meeting with Edward, need to mention smarty is being used. Also need to add smarty needs to be installed?? I am not sure of this?? After talking to Trevor after meeting, smarty is part of the system?? It is being installed when we install the system??

	==SUB-SYSTEM DESCRIPTIONS==		==SUB-SYSTEM DESCRIPTIONS==

137.166.4.130: /* SOFTWARE DESIGN OVERVIEW */

2005-10-18T02:46:35Z

SOFTWARE DESIGN OVERVIEW

←Older revision		Revision as of 02:46, 18 October 2005
Line 22:		Line 22:
	Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??		Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??

-	Everything else is fin. Thanks again Trevor for updated ERD!!	+	Everything else is fine. Thanks again Trevor for updated ERD!!
		+
		+	Clinton 18/10/2005 After meeting with Edward, we need to consider how the ERD may look. Do we keep iot the way it is, with the layout being landscape, or do we keep to the "rule of 7"?? I think if we can break up the diagram into 2, maybe 3 chunks (timesheets, statusreports, other??), then this would be easier to read, and in the end, more marks.

	==SOFTWARE DESIGN DETAILS==		==SOFTWARE DESIGN DETAILS==
	Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.		Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.

210.84.47.55: /* SOFTWARE DESIGN DETAILS */

2005-10-17T14:38:43Z

SOFTWARE DESIGN DETAILS

←Older revision		Revision as of 14:38, 17 October 2005
Line 25:		Line 25:

	==SOFTWARE DESIGN DETAILS==		==SOFTWARE DESIGN DETAILS==
		+	Clinton 17/10/2005 I think this is OK. I have not done Use Case 6 (Setup project ts and sr schedule) yet.

210.84.47.55: /* SOFTWARE DESIGN OVERVIEW */

2005-10-17T14:37:28Z

SOFTWARE DESIGN OVERVIEW

←Older revision		Revision as of 14:37, 17 October 2005
Line 20:		Line 20:

	==SOFTWARE DESIGN OVERVIEW==		==SOFTWARE DESIGN OVERVIEW==
		+	Clinton 17/10/2005 Code extracts?? Which bits of code should go here?? Not sure, of all of our files, needs the most attention??
		+
		+	Everything else is fin. Thanks again Trevor for updated ERD!!
		+
	==SOFTWARE DESIGN DETAILS==		==SOFTWARE DESIGN DETAILS==

210.84.47.55: /* SUB-SYSTEM DESCRIPTIONS */

2005-10-17T14:34:55Z

SUB-SYSTEM DESCRIPTIONS

←Older revision		Revision as of 14:34, 17 October 2005
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==

210.84.47.55: /* SYSTEM ARCHITECTURE */

2005-10-17T14:22:37Z

SYSTEM ARCHITECTURE

←Older revision		Revision as of 14:22, 17 October 2005
Line 4:		Line 4:

	==SYSTEM ARCHITECTURE==		==SYSTEM ARCHITECTURE==
		+	Clinton 17/10/2005 I think this is finished too. Thanks Trevor for updating the diagram for me!!
		+
	==SUB-SYSTEM DESCRIPTIONS==		==SUB-SYSTEM DESCRIPTIONS==
	==SOFTWARE DESIGN OVERVIEW==		==SOFTWARE DESIGN OVERVIEW==
	==SOFTWARE DESIGN DETAILS==		==SOFTWARE DESIGN DETAILS==

210.84.47.55: /* DEVELOPMENT TOOLS & DEPLOYMENT ENVIRONMENT */

2005-10-17T14:21:35Z

DEVELOPMENT TOOLS & DEPLOYMENT ENVIRONMENT

←Older revision		Revision as of 14:21, 17 October 2005
Line 1:		Line 1:
	==DEVELOPMENT TOOLS & DEPLOYMENT ENVIRONMENT==		==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==		==SYSTEM ARCHITECTURE==
	==SUB-SYSTEM DESCRIPTIONS==		==SUB-SYSTEM DESCRIPTIONS==
	==SOFTWARE DESIGN OVERVIEW==		==SOFTWARE DESIGN OVERVIEW==
	==SOFTWARE DESIGN DETAILS==		==SOFTWARE DESIGN DETAILS==