ECE 450H1S: Software Engineering II
Spring 2005 Session

Apr 29.
Result of the course marks can be found 
here.

The phase C mark is obtained based on 
+ the number of features x correctess (at most 75%), 
+ the easiness of installation (at most 5%), 
+ the documentation (at most 20%),
+ the features for OpenOME (at most 10%).

Apr 26.
Partial result of the course can be found here.

Apr 21. 
In a few days, you will be contacted by the TA to start your web 
services when they are doing the testing.
For teams who just submitted the phase C documents or text-based test 
clients, you should submit the graph editor client binary by tomorrow 
(otherwise will be considered as delayed and will be punished by 
10% for the phase C).

Apr 12. 
Previous final exam. 
The format of this exam will be similar.

Apr 6.
If you are not able to submit the results by April 8th, you can also do it on April 11 without penalty. After that, a 5% per day penalty is
obliged.  The hard deadline is April 14, submission after that will
not be taken into accout for us. As you need to have one week
to prepare for the final exam.

The results must be sent through email, if it exceeds 10MB, send the
splited ones in several email.

You can submit the integrated system on different dates, not necessary
to be finished on the same day. 

We are fourth year students, so please do not try to cheat with the 
course project, such as copying the modules with "strategic" 
cooperating teams.  
First of all, only UNIQUE features will be considered.  The mark 
won't count duplicated features by copying code, renaming variables, 
changing comments. Secondly, I know the program quite well, 
believe me, that it is not difficult to catch such cases.
Once detected, such duplication will seriously damage the mark.

Mar 30th.

Answers to some frequently asked questions.

Mar 21st. 

The marking scheme for the deliverable at the end of Phase C:

80%   The integrated systems involving your team's modules, either
      your web service, or your client, or both. 
      The principle is, the more systems you deliver AND the better 
      quality of the integrated system, the better.
      The overall quality of one integrated system Qi is 
      determined by the formula:
      Qi = number of features  * system reliability * system correctness
      where the three factors are defined as follows: 
      * number of features here is the number of the distinct editing 
        features in one integrated system, at least 5 should be 
        provided as the baseline, but you may provide more; 
      * overall system reliability is the product of the integrate 
        system reliability;  
      * overall system correctness is the product of the integrated 
        system correctness.
      The overall quality of your work is determined by
	sum (Qi * Wi)
      The weights Wi on the providers for the integrated system are:
	60% for the web service provider
	40% for the client provider
	80% if your are both WS provider and client provider
20%   The documentation to help us gather the data of your integrated 
      systems.
   - A feature model describing your solutions as a whole (product
     line family). Then break it down to describe the features of 
     an individual integrated system (product). 
   - For each integrated system:
    * Accurate and testable requirement specifications for the 
      system 
    * Unit test cases for either the web service, or the client,
      or both, developed by your team
    * A software contract signed by both parties (except you
      are the team that sell and buy your own product)
    * A monitored evolution of the project using software metrics
   - A 360 degree evaluation of every person in the team. 
     This document can serve as the basis to reallocate the course
     project marks among your team (thus not every member are 
     guaranteed to have the same marks in the course project!).
+10% various bonus features, bug-fixes, quality-improvements on
     the OpenOME system (the drop put in the sourceforge).

Mar 18th. 

I created another directory "axis1.2" under the TOMCAT server, 
so that you may deploy the web service there.
After class, I will prolong the office hour from 2pm to 4pm, to 
address issues in deploying your web services.

Mar 10th. 

Please visit CCNET to give us your feedback of the course.
Afternoon: JBoss installation.

* To ease the information exchange required for the project swap,
  we have a public forum. I will observe your exchanges. The *official*
  announcement is still at this page.
  Use the RSS feed to read the recent posts there.

Mar 9th. Before class.

* Today you will present the progress of the work. 
  The presentation will have 10% impact on your phaseB raw marks. 
* The marks on your phase A assignment will be returned.
* There is NO hard deadline for the swap time. The principle is,
  do it *ASSP*. It is recommended to finish one module by this week and   focus on the integration and maintenance for your customers...
* Please provide the URL of your web service after the deployment
* Please develop your web service in Axis 1.1 if you will deploy it
  to the ECF server. Please report problems of deployment that you had.
* To ease the information exchange required for the project swap,
  we have a public forum. I will observe your exchanges. The *official*
  announcement is still at this page.

Mar 1st.

When you log into any workstation on the ECFPC Windows system, you can click
on Start -> Programs -> Terminal Services -> Map to W (Web Share)

At this point, you should enter the credentials which we provided you 
for your team accounts, which is one of:
-------------
canadiantired   
lumiere        
mindz         
mugqq        
overnight   
photons    
bluewave // previously called team2
team7    
team9   
websilon  
xteam    
--------- Please ask me what's your password if you don't know it.

This mapping will provide you with a letter W:\, which will point to:

c:/program files/apache software foundation/tomcat 5.5/webapps/axis/WEB-
INF/classes


** Also, on any ECFPC Windows workstation, if you point your browser 
to :

http://128.100.36.17:8080/axis,

You should see the deployed Web Services.

Feb-27. 
To ease the swapping of the phase B, you will have a chance of giving
presentations. (Time to be decided, preferrably on March 9th).
Each team will be given at most 5 minutes (don't over use your time).  After
all the presentations are done, we will use the remaining time for you to
market your product (question/answers). You can sign a contract with other
teams after the class.

Your presentation will be monitored.

Feb-25. 

Concerning the project deployment for phase B, you may look at the last slide
in tutorial6. You team must have a code name as the username and the password
for that username is secret, only known to your team members.  I issued some
accounts during the tutorial, if you haven't got it, send me an email.

Secondly, on next Thursday there is a unmonitored lab time at the 
following rooms where the seats will be free:
==============
BA2128 9am-2pm
BA2124 9am-2pm
BA1120 11am-2pm
==============
Other times, you may also go to any Windows ECFlab to deploy your web 
service.

By Mar 11, hopefully your web service is accessible by other teams.

Lastly, your web services should be put under a directory
c:\program files\apache software foundation\tomcat 5.5\webapps\axis\WEB-INF\classes
And your document should be put under a directory
c:\program files\apache software foundation\tomcat 5.5\webapps\axis

Feb-22.
-- The deadline for Phase B document is postponed to midnight on Feb 28.
-- The marking scheme for PhaseA has been given to the TA's. You 
   probably will not get the phase A mark by finishing phase B.  Thus 
   the phase B document do not need contain the update for the whole 
   phase A document, rather, you need only to update the requirement 
   specifications as it is still required for phase C.

-- By March 11, your phase B implementation should be ready.
-- ECF will set up a Windows lab to host the web service through a 
   dedicated TOMCAT server, hopefully by the end of the week.
   Currently, if you want to test the deployment of your work, 
   I can host them at the CDF directory. 

Feb-21.
The required deliverables for phase B include the followings:
40% - A WSDL specification of your OmniGraphEditor web service
20% - A document associated with the WSDL to explain 
      why you reach this Web service design
30% - A document associated with the WSDL to explain
      how you can use the Web service, such as use scenarios
//change explained in the Mar 9 annoucement
10% - Your presentation of the web service
//10% - A document updating your requirements changes
//change explained in the Feb 22 annoucement
//10% - A document updating your phase A document, such as 
//      requirements changes, design issues and non-technical
//      issues (project management)

Jan-28.
The required deliverables for phase A include the followings:
20% - Understanding of legacy software: their components related 
      to your course project that may be reused; 
30% - Requirements (Functional and Non-functional) and their 
      specifications
20% - Team organization and Project plan
20% - Test plan 
10% - Risk analysis and mitigatations

Please post the following annoucement on your course websites and let 
your students know about this upcoming event:

Are you interested in a future research opportunity?  Would you like to
find out what your friends and classmates are up to?

Come to the Computer Science Undergrad Research Showcase on February 2nd
at 4pm in BA1190.

Undergraduate students will be giving short presentations on the research
they have done in CSC494, CSC491 and summer NSERC projects.

There will be a prize for the Best Presentation and refreshments will be
provided.

The instructor would ask each of you to vote for the following decisions:
* Shall we have a marking scheme 60% on course project, 40% on final
  exam; or to have 50%/50% distribution?
* Shall we have a close book/notes final exam, or to have an open 
  book/notes final exam?

It is up to you to decide the size of your group. You can have a group of N =
3, 4, 5, 6, 7 students as long as you can manage to fulfill all the
requirements.  If every group has 5 memebers, then we don't need to add/remove
any marks.  The thing is, such self-organized groups will indeed become a set
of groups with different sizes. 

The size factor has a multiplying impact on the course project marks only, It
is following exp(log(5/N)/3) since we aim at 5 person groups on average. 
Team of other size is not allowed.

N	factor
3       1.076752518
4       1.032830754
5       1
6       0.973951522
7       0.952457926

Note. The team factor is only applied after all the bonus points are included.
For example, if your 6 people team got 92% marks for the required features, and
15% marks for the bonus features that are all passed the test, then you will
get 107% raw marks. After the adjustment, you will still be above 104%!