ICS103 – Lab Lecture 1

Introductory Remarks

Who am I?

• Point to biography Ejaz Ahmed

Who are you?

• Discuss background preparation, e.g., courses taken, languages and systems used, home computer? Modem?   Specifically what kind of background is best for C103

What is this course about?

This is a course on how to design and construct good programs. It is about programming in the small as opposed to system design.

How is this course going to be run?

Rather than teach the syntax of the C/C++ language in class, I will try to examine some case studies: sample problems where we duplicate the problem solving process, complete with false starts and bad decisions.

Why? Because you learn by doing, and that means maJeri mistakes. Engineering Maxim: You learn more from your failures than from your successes.  Therefore it is important that you do the assigned work yourself, and not "borrow" heavily from the work of those who have gone before you through ICS103.

What do I expect you to do?

• Read the texts. Jeri: Chapters 1 to 4, this week.
• Start the assignments early. Assignment #1 can be started whenever you are ready. Keep on working at it, a little each week until all the exercises are done. Support for these exercises is to be found in Jeri's book, or your preferred C-language text.
• Come to the labs prepared, that is, read the lab before hand, perhaps even setup the directories in your account.

Most importantly, I expect you to ask questions. If you are confused during the lecture, stop me and ask. Chances are that others are equally confused.

The Bureaucracy

The lab course description contains important information. It is available through netscape/explorer. Take some time to read it now.

• Note important dates
• Lab work
• Evaluated work.

Important things to note:

• Plagiarism and Cheating.  Potential problem.
• Basically you must give proper credit for assistance you have received.  Submitting the work or ideas of others as your own is a violation of the Code of Student Behaviour
• There is no midterm, instead we have a series of quizzes. If you miss a quiz you MUST come and talk to me and provide some explanation. I will then advise you about your options.
• Labs start immediately. Get your Computing Science Windows login ID immediately (about all of the class need IDs). Lab 1 is a refresher. You can do it on your own time. It carries no mark and no penalty.

Software Engineering is a Serious Business

Software is not benign, it has risks.  Software in embedded systems, like airplane flight controllers, fuel injection systems, traffic light control, real-time systems (such video arcade games!) can lead to serious problems if they malfunction

What characterizes good software?

• correct
• reliable
• robust
• efficient wrt important resources
• usable
• maintainable
• portable to different platforms

Many of these are exactly the same as used for the engineering of physical devices.

How software is (both good and bad) developed?

The waterfall model:

requirements 
- the goals of the client
 specification - 
a description of the tools to be built
 design 
- overall plan for the software 
 implementation - the 
coding of the software 
 testing 
- weak verification that the implementation 
is correct 
 maintenance - fixing errors and evolving the system

For many systems, in which the requirements are well defined, the waterfall model is satisfactory. However

• in many cases, clients do not know what they want.

No point in simply automating some existing manual process. It is better to re-asses the entire way of doing things and exploits the additional power of the hardware/software of the new computing system.

Rapid Prototyping:

repeat:
 specify
 design and implementation 
 use 
 reevaluate