TA for 14:332:452 :
Introduction
to Software Engineering
Name: Beizhong Chen
Office hours: Tuesday 5 (3:20 - 4:40 p.m.)
Office: CoRE 723
Email: bzchen@caip.rutgers.edu
If you need extra office hours, please send me e-mail.
*********************************************************************************************
Please come back to check for update.
Latest update(5/8)
For Presentation/Demo/Overall grade, please contact Professors.
Final exam:
The minimum is around 20, the maximum is around 87, all out of 100. Average 48.12
Report 3:
The minimum is around 60, the maximum is 100, Average 74.4
(The score is scaled to 100)
Question: how could you tell a report is excellent or not?
One possible answer: After reading your report, another person who is not in your project, can obtain a clearly picture about your design, and can easily convert your design into codes, basically, based on your Interaction diagram and class diagram.
About Demo.(3/20,3/27)
The detailed requirement could be found Here.
The note about presentation is also applied to Demo.
In the Demo, you must show all elaborated use cases, avoiding too much time on simple use cases .
You must list your elaborated use cases in your hand-out for evaluation purpose.
The demo date could be May 4 & 5. To be decided after 3 weeks.(3/27)
About Report 3.(3/20,3/27)
The detailed requirement could be found Here.
All groups are required to return proposal, report 1 & 2 when you submit your report3. Fail to do this would result in no grading for report3.
Your are required to correct all errors pointed out by Professors and TA and any possible mistakes overlooked. Fail to do this will lose 10~40 % (to be decided) points.
After you submit your report, don't ask Professors/TA to collate your report (e.g. tape diagrams together, make a new print-out). Otherwise, at least some Professor/TA labor fee ( minus points) will be charged.
Keep the question above in mind (how could you tell a report is excellent or not?) when you prepare your report.
About Presentation.(3/20, 3/27)
The detailed requirement could be found Here.
Additional requirement.
Every group is required to submit a slide print-out. Any group that fails to do this will lose 10~30 % (to be decided) points.
Make sure you mention ALL elaborated use cases. Because of the time constraint, it is better to avoid spending too much time on those simple use cases, e.g. log-in, log-out.
To check out whether your project is trivial or not, one good way is to check your use cases implemented. If you only show 2 or 3 simple use cases, your project is trivial.
You must pick up your report 1 & 2 and avoid mistakes pointed out by Professors & TA and any possible errors overlooked. Any group that fails to do this will lose extra credits.(3/27)
About Report 2(3/20)
Every group is required to provide Interaction Diagrams for all elaborated use cases in the report1 but some groups failed to do that. It is impossible to evaluate those Interaction Diagrams without use cases description. This is considered as incomplete.
It is a plus to submit Interaction Diagrams for brief and casual use cases.
Some groups confused SSD with Interaction Diagram. Please make sure you understand those two concepts.
There should not be any actors in your interaction diagram. You may argue that the figure 34.10 shows an actor, but it is different. Please read figure 18.1(page 323), chap 17/18 and other chapters to see how the textbook authors handle this issue.
Page 221, first sentence about interaction diagrams, "The UML includes interaction diagrams to illustrate how objects interact via messages. They are used for dynamic object modeling". Actors are NOT objects in your software, e.g. Actors can never be part of your loop in your Interaction Diagrams. (maybe it could be true in distant future when human being can be transferred by FAX machine ?? :)) )
The minimum is around 40, the maximum is around 90, all out of 110. Average 61.8
About quiz 2
The minimum is 0, the maximum is 9, all out of 10. Average 3.01
About Exam 1
The minimum is 20 something, the maximum is 80 something, all out of 100. Average 48.1
Presentation Slot Reservation(2/23)
About Report 1
All reports have been carefully reviewed by TA & Professors and a lot of comments are given on every reports. Most of your reports show a lot of problems, some of which are serious. It is impossible to point out all problems on each page, especially for those similar problems. It does not necessarily mean that your report is correct even if TA/Professors didn't write comments on some of your pages. All groups are required to read lecture notes and text book again to make sure you understand the concepts and ideas. You also need to follow the conventions when you prepare your report.
The minimum is around 40, the maximum is around 90, all out of 110. Average 62.8
You are required to return the graded report when you submit your next report. Any groups that fail to follow this may suffer penalty.
The reports will be returned in class, 2/24. If not, please contact Professor Marsic.
About Quiz 1
The quiz will be returned in class, 2/24. If not, please contact Professor Marsic.
Commons on Proposals(02/06/2006)
(1) Some proposals don't meet professors' requirement. Please following the instruction on your proposal.
(2) Please contact Professors or TA if you have any questions about your proposal.
(3) Please return your proposal to TA. You could return it with your next report or eariler. DON'T lose it.
(4) Your project's web link is shown on the "project group information" page. If it is not correct, please inform TA.
Please check your group information. The proposal deadline is approaching(1/27/2006).
Commons on Proposals (01/30/2006)
All the proposals have been reviewed by Professors and TA.
(1) Some groups didn't clearly state whether they will implement any algorithm
programming. Some groups only mention that their projects will provide some web
services like login/logout, searching, etc, without stating whether they will
only use existing components/libraries/API or to program their own algorithms.
Also, saying that your system will do search may mean that you'll simply use SQL
database search, so you don't need to do any programming.
Professors expect you to program your own algorithms, not only to combine some
existing components. A proposal that only provides web services based on
existing tools is considered as "not good proposal".
(2) This course, Introduction to Software Engineering, is very different from
other courses, e.g. a math course. In a math course, even if you wrote in a
messy hand-writing, you may get a full credit if you have the correct answer.
The story is different for this course. Imagine that you own a software company
and you want to sell your product to your customers. The first impression your
customers have will be from your documents. This makes your documents very
important. A poor-looking document will not attract many customers. In this
class, a professionally-looking document may bring you some extra points, and
hastily prepared document may give you some negative points. So,
please make sure your document looks neat, well-organized,
and professional in addition to having correct solutions.