

Fall
2011 Instructor: Vlad Wojcik
Support: John Futers, Lecture times: Mondays, Fridays 12:30 PM - 2 PM, room TH257 Assignments:
COURSE OBJECTIVE:
Documentation: Teams: Membership Form 1. Perpetual Motion Squad Teamwork Rules 2. ProMonkeys Generic Phase Plan 3. White Elephant Peer Evaluation Form 4. Quantum Programmers 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.
THEORETICAL PART - TOPICS COVERED:
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 2005 (their choice). Access to labs and consultative support is provided.
PRACTICAL PART - THE PROJECT:
This year project deals with computer vision. Specifically: 3D scene reconstruction from groups (pairs, triples, quintuples) of 2D images. Students are invited and encouraged to borrow the custom camera support equipment (demonstrated in class) to make their own sample images.
Immersive photographs of some objects are provided as an illustration of our goals, together with the definition of the photographic TIFFormat.
RECOMMENDED READING FOR THE PROJECT:
TEXTBOOKS:
- R.S. Pressman: Software Engineering, 7th ed., McGraw-Hill.
- J. Barnes: Programming in Ada 2005, Addison-Wesley 2006, ISBN 0-321-34078-7.
- S. Prata: C++ Primer Plus, 5th ed., SAMS 2005, ISBN 0-672-32697-3.
USEFUL NOTES:
- Refresher on Semaphores
- Overview of ADA 2005 (Courtesy of IBM)
- Tasking in Ada
- Use of Attributes in Ada
LECTURE TOPICS:
Chapter 1: Software and Software Engineering
Chapter 2: Process: A Generic View
Chapter 3: Prescriptive Process Models
Chapter 4: Agile Development
Chapter 5: Practice: A Generic View
Chapter 6: Systems Engineering
Chapter 7: Requirements Engineering
Chapter 8: Analysis Modeling
Chapter 9: Design Engineering
Chapter 10: Architectural Design
Chapter 11: Component-Level Design
Chapter 13: Software Testing Strategies
Chapter 14: Software Testing Techniques
Chapter 21: Project Management Concepts
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:
- Two assignments in programming language (10% each) - fall term
- One proficiency test in programming language (15%) - late in the fall term
- One proficiency test in theoretical aspects of project management (15%) - early in the winter term
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.
NOTES:
In case a given mark is perceived unjust or unclear by a student, s/he is encouraged to see the instructor to discuss the issue. Depending on the case s/he is 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.
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.
Instructor: Vlad Wojcik
Revised: 12 January, 2012 12:32 PM
Copyright © 2012 Vlad Wojcik