• Develop and produce software process artifacts, most importantly the code and user documentation.
• Demonstrate skills that help you work effectively as a member of a software development team.
• Analyze the fundamental principles of software engineering. Be able to identify and describe the software life cycle, roles, artifacts, and activities.
• Demonstrate the concepts of software "best practices" and when they apply.
• Synthesize the concepts of software "best practices".

1. Assignments                       25%
2. Presentations                     15%
3. Mid-Term Exam                 20%
4. Final Exam                          20%
5. Final Project                        20%

Final Project, Mid-term and Final exams are mandatory. 

Assignments:
The assignments include research paper critiques

Paper review assignments:

For each paper, students should write a review answering each of the following questions:
1. What problems (with prior work or the lack thereof) were addressed or surveyed by the authors?
2. What solutions were proposed or surveyed by the authors?
3. What are the technical strengths and main contributions of the paper's proposed solutions?
4. What are the technical weaknesses of the paper's proposed solutions?
5. What suggestions do you have to improve upon the paper's ideas?

Paper Presentation:

On the day of your paper review, you should bring your review presentation, i.e., power point file (flash drive), to the class. In total 15 ~20 minutes each, including:
- Brief description of (1) introduction/idea; (2) method (experimental design, participants, apparatus, experiment procedure, data collection); (3) results; (4) discussion and/or conclusion; and (5) etc.
- What knowledge did you learn from the paper/work, e.g., anything you’ve never known before; which part of the work interests you most…

Research papers will be assigned to students to read, analyze and present to the class. Presentations will be structured as follows:

• Presentation 
• Questions to presenter
• Open discussion 

Paper Presentation will be graded through following rubric
• Content                                   (35% Weighting)
• Preparedness                           (35% Weighting)
• Visual Aids/Handouts                        (15% Weighting)
• Discussion or Questions raised(15% Weighting)

Research paper: Each student is expected to do a research paper on a topic. Topics can be drawn from the following areas:

• Modeling adaptive software systems
• Using models at runtime to support automated and human-driven adaptation
• Rigorous model analysis (including testing and formal static analysis)
• Specifying and verifying model transformations
• Composing/weaving/fusing models
• Aspect-oriented software development
• Modeling and analyzing dependability features
• Multi-agent systems or agent based modeling

Research paper will be graded through following rubric

• Quality of Information                                   (25% Weighting)
• Organization                                                   (25% Weighting)
• Mechanics & grammatical or spelling (20% Weighting)
• Paper properly formatted in IEEE format      (15% Weighting)
• Research Paper Construction                          (15% Weighting)

Final Project:The purpose of the course project is to provide the students with the knowledge of software engineering methodology and the skills to apply it. The particular project is not the goal in itself; rather, it serves as a vehicle to apply your knowledge and to develop the skills. Projects also introduce students to team work, which is a must for large-scale software development. It also emerges as a key methodology for any- and every-scale software development, something called extreme programming. Team work is required since team work is an integral part of large-scale software development.

GRADING:  Academic dishonesty will result in grade F.  The following grade scale will be used:

90 % - 100% = A
80 % -  89%  = B
70 % -  79%  = C
60 % -  69%  = D
0   -    59%    = F

Final grades will be computed based upon credits earned for all the five components mentioned above.

References:

Bernd Bruegge and Allen H. Dutoit (2004) Object-Oriented Software Engineering: Using UML, Patterns and Java, Second Edition, Prentice Hall, Upper Saddle River, NJ.

Use ful links for iPad

1. iPad Programming Tutorial – Hello World++
2. IPad Sample Source codes
3. Creating an iPhone Application
4. OS development by reading these Getting Started documents
5. iPad eBook Source Code DEMO
6. Where can I find iPad Sample Code

 

---

USEFUL LINKS

1. Visual Studio 2008 Express Editions Tutorial

   Running Visual C++ 2008 Express Edition for the First Time

   Compiling a Sample Application "Hello World"

   C++ Namespaces

   Namespaces

Graphics

2. cccfiles.zip (Graphics Libraries)

Virtual Functions

Virtual Functions

Polymorphism

Introduction to Polymorphism in C++

Introduction to Eclipse Video

1. Core Java Video TutorialsVideo

2. Project: MetaAgent, a Steering Behavior Template Library

3. Projects: Fuzzy Logic - Obstacle Avoidance - WPF

4. Project: AI Life

5. Junit tutorial

6. JUNIT tutorial 2

7. Junit with NetBeans IDE 6.0 tutorial

8. Junit test case

9. Class Assert API

10. Introduction to testing Java programs with JUnit

11. JUnit assertTrue