transputer.gif (9866 bytes)
Brock University
Department of Computer Science

COSC 4F00: Software Development

2017/18 Instructor: Vlad Wojcik mail.gif (1189 bytes)Support: John Futers Assignments:

darkDot.gif (501 bytes)COURSE OBJECTIVE:

Documentation: Teams:
Membership Form 1. No Code No Life
Teamwork Rules 2. Eat'n Greet
Generic Phase Plan

3. Poker Face

4. tree_ROOT

5. Solutions for Stuttering

6. Deshval Method

7. Goal Diggers

Peer Evaluation Form

To give students a feeling of the problems faced by the software industry when working on the medium to large scale software projects in general, and especially as real as possible an experience in team management and the teamwork on a software project. The course is organized in two parts, one theoretical (Fall Term) and one practical (Winter Term). In order to introduce practical illustrations to the theoretical material as early as possible, the two parts may partially overlap.


Scientific principles and managerial skills required for construction of reliable software. Attributes of large complex software systems and software process models for managing the phases of software development. Software requirements: analysis, tools and document preparation; software specification methods, software design concepts and alternate methodologies such as prototyping and OO paradigms. Software testing, verification and validation methods.

The students are required to learn on their own either C++ and/or Ada (their choice). Ada 2012 referece manuals are provided here.

darkDot.gif (501 bytes)PRACTICAL PART - THE PROJECT:

Projects in 2017/18 are to be defined a bit later. Click on a team name in the table above (top-right) to learn more.

darkDot.gif (501 bytes)TEXTBOOKS:

darkDot.gif (501 bytes)LECTURE SUMMARIES:

darkDot.gif (501 bytes)MARKING SCHEME:

The final mark of every student will consist of the individual component and the teamwork component.

1. Individual component: (50%) distributed as follows:

2. Teamwork component (50%) - winter term; individual mark distribution will emerge through peer evaluation process.

CAUTION: The Department reserves the right to scan submissions using electronic means, in order to ensure the originality of students' work.

darkDot.gif (501 bytes)NOTES:

In case a given mark is perceived unjust or unclear by a student or a team, s/he/they are encouraged to see the instructor to discuss the issue. Depending on the case s/he/they are able to make, a mark can be modified. The deadline to contact the instructor on these matters is one week after the mark has been issued. Marks not disputed within this period will be considered final.

darkDot.gif (501 bytes)PENALTIES:

Possible lateness in assignment submission is counted in days, each period of a day ending at 4 PM. The penalty for late submission of assignments is 25% up to three days (or a part of a day). After that period the penalty is 100%.

While honest cooperation between students is considered appropriate, the Department considers plagiarism a serious offense. For clarification on these issues you are directed to the statement of Departmental Policies and Procedures.

cameo.gif (1740 bytes)Instructor: Vlad Wojcikmail.gif (1189 bytes)
Revised: 27 October, 2017 10:22 AM
Copyright 2017 Vlad Wojcik