In_Tech.Corp

• Week 1
– Find group members and set up a blog site for project progress reporting

• Week 2
– A project proposal (1-2 pages) submit to lecturer (Uploaded to the blog)
i. Project Title
ii. Group member details (ID, name, email, major)
iii. Introduction to the background of your system
iv. Objectives and features of your system
v. Problem definition:
-What we want to do
-How are we going to do it
-What problem are we face
-How are we going to solve it
– Identify what technologies going to use: PHP, ASP.Net, JSP or others.

• Week 2 – 11
– Update project progress on the project blog site. (Instructions will be put on the MML online bulletin and/or during lecture/tutorial by Mr. Simon)
– Every student’s individual effort is to be stated in the blog regarding the diagrams / content etc. uploaded

• Week 3 – 5
– A project planning diagram (network diagram) and a Gantt Chart are to be drawn.
– Prepare a system requirement diagram (to be taught in lectures)
– Design of the system MUST be done using diagram learned such as Unified Modeling Language (UML) diagram (Use Case, Activity, State, Sequence etc.)

• Week 10-12
– We are tested on our developed application and document.

• Week 11-12
– Write a final technical report to describe the features of software system.
Show some screenshots of the system. (Strictly between 8-12 pages only not including source codes)

• Week 12
– A group presentation which takes 15 minutes per group (date/time will be announced later)

• Week 13
– Submission of project final technical report. (Format of the technical report is uploaded to the MMLS. Please follow.)

***** A weekly project progress documentation or report on development status is uploaded to the blog every week.

-by Tan Pang Chow-