|
|
CSCC40 Analysis and
Design of Information Systems fall 2009 - assignments |
|
due |
assignment |
|
Oct. 5 |
|
|
Oct. 26 |
|
|
Nov. 2 |
|
|
Nov. 16, 23 |
|
|
Nov. 23 |
E. project walkthrough/presentation map for clients |
|
Dec. 3 |
F. final report include this letter |
|
Dec. 8 |
|
the 2009 teams Team:
AMCS Client:
System:
Exhibitor Support Chan Michael Kwok Pui-Hong Hong Eun Pyo Team:
FATES Client:
ViXS Systems Inc. System:
Fault Tracking Lazar Matei Shih Yu
Chung Siddiqui Abdul Baseer Team:
HT Technologies Client:
UofT Accessibility Services System:
Student Accomodation Chan Vincent Jayaram Prasanthan Wang Xiao Victor Team:
BCMY Client:
Gossner Management Ltd. System:
Property Management Butt
Tahir Matei Silviu Team:
VCMK Client:
RBC System:
Permission Control Chen Kevin Shuo Kwasik Andrew Mahendran Thivyan Vu
Thuy |
Team:
CDL Client:
System:
Assignment Control Chen Rui Deng Jiobao Lu
Team:
imDesign Client: Amphenol Canada CorpSystem: Shop Floor Control
Jia
Qiwei Liu
Chunhui Tung Herbert Team:
DSL Client:
UTSC Student Union System:
Meeting Room Booking Liu
Renxiang Qin
Liang Rochiramani Sunny Team:
SPEG Client:
UTSC Admissions System:
Student Recruitment Kuo
Li-Nung Yu
Chen Team:
ZHLX Client:
The Edge Bar and Lounge System:
Bar Control and Inventory Hung Andrew Leung Vincent Yuen-Dak Meng Qing Zhou Yin Galaxy |
|
assignments
overview All assignments, when combined, form one proposal for a new or replacement system for your client. Your team will produce a partial design and a draft implementation plan for a real system that your client wants. The proposal will contain the analysis documentation from assignment A, structured diagrams from assignment B, design documentation from assignment C, object-oriented diagrams from assignment D, and additional materials as outlined in assignment F. You will give a copy of the final proposal to your client and submit one for marking. Assignment E is a walkthrough/presentation of some portion of your proposal. You are required to attend at least three walkthroughs as audience/evaluators. You may invite your client to your team's walkthrough. Assignment G is your client’s evaluation of your proposed system and your methodology to complete the proposal. teams The work will be done in teams of 3 or 4. There is too much work for teams of 1 or 2, and teams of 5 or more will have difficulties coordinating their efforts and will be expected to produce a larger report. Some of the work will be for individual marks, and some for team marks. submitting
your work
All assignment documents must be identified and labeled as outlined in assignment F. All pages headers and diagram title blocks must contain the information outlined in the technical writing guidelines. And all research must be properly accredited. In assignments A to D inclusive,
hand-drawn diagrams will be accepted if they are legible. But the final diagrams in the proposal may
not be drawn by hand. Any drawing tool such as Rational Rose or Visio are
acceptable. problems you
may encounter with the case study
In your report, you may not say anything twice. This means you have to be careful to put information only into the correct section of the final report. You may not get some of the answers from the client (network requirements for example), so you will have to make an educated guess. There is no need to indicate in the report that it’s your guess, but do remember that your client will read this document and any wildly wrong guesses cause your report to lose credibility. If you are unable to get information and you don't know enough to make a credible guess, then indicate in your report that the information is still to be included. help with
your assignments
In tutorials, you will have examples, guidelines and reference materials as appropriate for the next assignment. In some tutorials, you will have exercises to help you with concepts. Plan on visiting the instructor to review your work at least once! |