Scribd
Upload
3 views3 pages

Assign Requirement

The assignment for ISOM 2007 requires students to submit a programming project by the specified due date, with penalties for late submissions. Students must include a cover page, program description, procedural comments, and a sample input/output to demonstrate functionality. The evaluation criteria include program functionality, readability, personal suggestions, and potential bonus points for additional features.

Uploaded by

luxinke28
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views3 pages

Assign Requirement

The assignment for ISOM 2007 requires students to submit a programming project by the specified due date, with penalties for late submissions. Students must include a cover page, program description, procedural comments, and a sample input/output to demonstrate functionality. The evaluation criteria include program functionality, readability, personal suggestions, and potential bonus points for additional features.

Uploaded by

luxinke28
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

ISOM 2007 – Programming for Business Analytics

GENENAL ASSIGNMENT REQUIREMENT

Due time of your assignment:


 All assignments are due at the class time on the due date specified on the Assignment.

 20% mark deduction per day will be applied to late assignments and work submitted 3 days after
the due date will not be accepted.
 If you really have a situation that you can’t submit your assignment in person or by your classmate,
please inform the instructor BEFORE the due time. Make sure that he/she knows it by replying you.

Your program listing should contain the followings:


 Cover page with your personal information (Student Name, Student ID, Session No., etc) and the
Evaluation Table (please copy the table below).
 Program description (On top of your program listing)
 What problem is being solved?
 What are the limitations of your programs (if any)?
 Procedural comments (In each function except when it is too small)
 General description (e.g., this function takes two numbers and output their sum)
 Input ranges, error handlings, limitations and meanings of all your (input/output) parameters or
return values.
 List other functions that are related to this function (e.g. Who will call this function? Whom will
this function call?)
 Comments and suggestions about this assignment
 What have you learnt? (Be creative!!! Don't just say I learnt how to calculate the GCD!!!)
 What problems have you faced and how were they solved?
 What may be the application of this program?
 Examples of the comments and suggetstions:
 I prefer to see this question in my exam.
 This assignment is too tough for us.
 All students are copying from each other.
 No one knows how to do this assignment.
 Program sample input and output:
 Please provide enough evidences to show that your program is working!

Evaluation Table (To be copied onto the cover page of your assignment!)

Criteria Percentage Q.1 Q.2 Q.3 Bonus


Workable Program
30%
- sample input & output
30%
- uploaded program code
20%
- no errors of any type
Program Readability (easy to
15%
understand, internal comments, etc.)
Your own suggestions 5%
Bonus: Additional features (e.g. error
5%
handling, more efficient way, etc.)
Total: 105%
 You have to submit both the hardcopy and softcopy of all your programs. You may submit the
hardcopy to the instructor on/before the due date. In addition, you should upload your programs to
the UMMoodle course on/before the due date as well. NO E-mails containing your assignment will
be accepted!

Note:
 Tips for making your program readable
 Do not use global variables unless necessary.
 Use short but meaningful names for variables and functions.
E.g., PrintNum(StudName). People can guess what you are doing without looking at the procedure
and the variable details.
 Give a short description whenever there is a section of big/main/complex calculation (state the
purpose and the expectation before and after each section). Usually it is called inline
comments/description. Write this kind of description when you are writing your program. Do not
wait until you finish the program.
 Comments that are added after program completion are those general description and parameters'
description, not inline comments.

 Special Offer
Keep in mind that in order to PASS your assignment, your program has to be at least working fine in
most situations (You have to test it by yourself). However, if you have really tried your best but still
couldn't get your program running smoothly, please do write a brief description to explain what you
have done. Then, hand in your partial work and your description. Appropriate marks will be given,
don’t worry!

 Cheating
Please DO NOT CHEAT! If your program is not working, just let it be and submit whatever you could
do! If you hand in your program that couldn’t work out, but make up some fake sample input or output,
you will get a grade ZERO!

MOST IMPORTANT:
PLEASE DO NOT COPY ANY OF YOUR CLASSMATE's WORK!
Heavy penalty will be enforced without any mercy!

Reminders:
When you are writing your programs, you should try to ask yourself the following questions before you
submit:
 Is your current work the most efficient way to do it? Are there any other ways to implement your
program?
 If your program were to submit to your classmate to read, will your classmate understand your code
WITHOUT your presence?
 If you are asked to add additional features later on, what percentage of your code needs to be
modified?
 Is it possible for your code to be applied in other similar problems with minor changes?
 Are you using too many functions? Are you using only one main program?
 Do you have enough comments to explain loops and inner functions?
 What input and/or output errors are handled? Have you included all cases?
 Are you using meaningful names for all of your identifiers?
Last reminder: Be very patient in writing programs!

You might also like