I am now on vacation and I will be back on Monday, 23rd of June.

I will post your project grades in the next week.

The members of some teams that have unbalanced works or have team members who did not do his/her responsibilities will get different grades in grading of Process & Communication and Coding and Product parts.

For final grading of these two parts I would like to talk to the project managers of your project teams on Monday, 23rd of June. They should come and talk to me on Monday. Other members may also come.

I will do an announcement for the final exam in the middle of the next week.
 

Coming late to your final project meeting will be considered as a negative point for your demo. You will normally not get an extra time for your presentation.
 

I will not grade your SPMP, TD, and UM. They will be counted for the completeness of your project. See the new grading table given below.

See my software design, documentation and coding page. Your source files must satisfy the minimum requirements given in this page.
 

See this sample contribution summary report that you will submit before your demo. In this report the subjective data part is missing. At least they could write technologies learned and used during the project, difficulty of problems solved.
 

Submit SAD, SPMP,  and the updated RAD documents (Deadline: Friday, 5 pm).

Submit UM and TD (Deadline: Monday, 5 pm).

You will also submit a one-page contribution summary report for your project on Monday. It can be a table. In this report, you must give the following minimum information:
1) The number of files and lines of code (LOC) originally written
2) List the file names and/or methods you have developed with the names of their developers
3) Write LOC that each developer has written
4) If you use some existing code, you should give some information about it, like the number of files, LOC used, ...
5) All design documents, chapters (if one document is written by several project members) and their authors
6) Some subjective data: Special algorithms, data structures, design patterns used or/and developed, technologies learned and used during the project, difficulty of problems solved, investments made,  ...
7) Other project efforts, work products and their doers. 

Before you calculate LOC you have written, you should delete unnecessary space lines and optimize your code. Use refactoring techniques for code optimization and getting efficient and understandable code.

In addition to this last important task indicated above for calculating LOC, you should format your code using the features of your development environment. The formatting and code indentation are very important for code readability. To format your source file, click your program code in the Editor and use CTRL-T in Together and Format All in JBuilder 8.

Upload all design documents (in word format, also optionally in other formats) to your web site.

Work on your software, coding documentation, and API.

Upload all your UML design documents (normally Together project) in a zip file to your web site.

Upload your JBuilder or Together project directory in a zip file and/or other implementation source files to your web site.

Upload your project web site in a zip file to your project web site. When this zip file is opened, your web site must be constructed and all work products must be available through its index file.

Arrange a meeting  date (Monday, Wednesday, Thursday and Friday) and an hour (at least 1 hour) with me for the next week (Deadline: Monday, 5 pm). The first comers will get some extra bonus.

I will download your project web site zip file and open it on my machine before our meeting starts.

Anyone may normally download your work products from your web site and examine and run them on his/her computer. You should write all the instructions for downloading, installing and running your program.

For some projects which need some special hardware and software configurations, after examining your source files on my machine, and maybe partly running same parts, we may go to the lab to evaluate the remaining part.
 

You can use the following html and word templates for your SDD (System Design Document) and the word template for ODD (Object Design Document) which are the two parts of SAD (System Architecture Document).

Don't use these word templates as given, make some small changes to the format of the document. For example, the space between a header and the body text is too much. The headers may be Arial and bold. This word document templates need such modifications.

Dont put Glossary and Index parts as you will see in the word templates into your SAD.

Especially use these two word templates to get an idea about what you can put into SAD. Don't forget that these word documents are not perfect example templates.

Use the template given on page 365 for your TD. The sections of this document are explained on 365, 366 and other parts of the Chapter 9.
 

The summary of CENG 302 Project Work Products, Processes and their Grading:
 

Your proposals and RADs were graded and your grades were posted. You are advised to look at the project proposal and RAD gradings given above carefully and try to improve the quality of your next documents.

You can get your RAD documents from me and look at the comments I have written.

You will resubmit the final RAD document to me after making corrections and adding missing parts.

Your RAD grade will not change.
 

Drawing Use Case Diagrams but forgetting companion explanations for use cases. For each use case oval, you should normally write a use case document.

You should use the use case template given on page 40. Look at also the example use case on page 41.

Ignoring scenarios. Use the template on page 42 for your scenarios.

Ignoring 3.5.5 (first GUI prototypes) - navigational paths and screen mockups.

Forgetting the practices of your software development process and team work.

Grammar and spelling mistakes.
 

Today and tomorrow (Friday) you are required to talk to me about your RAD and your project progress.

Before coming to talk to me you should have put your RAD (in word format) and your Together design documents (make a zip file of your Together working directory) to your web site.

If you are not able to come to talk to me for any reason, you should have put these two Requirement Analysis works to your web site until tomorrow 5 pm.

We will download your documents from your web site tomorrow for grading.

For full grading, meeting and oral status reporting are required.
 

In your design documentations (RAD, architecture (system/object) and implementation documents) try to use the online document generation features of Together.

Look at the following presentation Documentation Designer, Tips and Trips.

In the Together tutorial, A Practical Guide to Getting Started with Together ControlCenter 6.0, there are two lessons related to documentation and coding: 9. Documentation Generation and 10. Audits and Metrics. Go over these lessons and learn some important skills for online documentation and implementation in Together.

You can use the following html and word templates for your RAD (Requirement Analysis Document) which you will submit this week.
 

Today (Time: 09-12:00) and tomorrow (Time: 09:30-12:30 and 14:00-16:30) you (with all your team members) are invited to come to my office to talk to me about your project and second homework assignment.

Before you come, please take a print-out of your second homework assignment. If for any reasons you cannot take the print-out, send it to me by an e-mail.

I will evaluate the second homework assignment during our meeting. All team members must be ready for comparison of 5 software development processes. I will ask questions.

The simple format of the homework: Body text: 11 Times New Roman, on all pages margins should be 2.5 cm. It should be in fully-justified text

The first comers will take the first meeting times. Don't forget, always the more you are in the first comers, the better it is for you!

You should post the following minimum documents to your project web site this week as announced in the last lecture:
- Project (team’s) name and vision statement.
- Your initial Project Proposal (You can use the simplified version of the template given on page 53 of Developing Applications with Java and UML or look at here for a more simplified one.
- Project roles and responsibilities
- Your initial Software Project Management Plan (SPMP). This document will be updated by your Project Manager.
- Your team’s weekly activities (this week and next week)

The midterm date is 15 May 2003, Thursday, Time: 09:00-12:00.

The last grading update: Project: 40 %, Homeworks and Quizzes: 20 %, Midterm: 20 %, Final Exam: 20 %.
 

The comparison criterion for the second homework: Major process activities, artifacts in all software development phases, utilization of UML, documentation, team model and communication, project management, risk management, configuration management, design reviews and formal code inspections, measurement and control, testing, training, technology and process change management and readiness, process tools, worldwide usage, typical organizations, teams and projects for each process.