Download what the course is about

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Software Design
EECS 3311
Gunnar Gotshalks
LAS 2032
www.eecs.yorku.ca/~gunnar
[email protected]
© Gunnar Gotshalks
01-1
Course Information
• www.eecs.yorku.ca/course/3311
–  Contains all information about the course
© Gunnar Gotshalks
01-2
Course Forum
https://forum.eecs.yorku.ca
• Used by the instructor
–  For announcements about the course
• Report specifications
• Notification that course work has been graded
• Used by students
–  To discuss the course material and general problems
your with reports
–  NOT for posting solutions or partial solutions for
reports
• Login using your EECS account
© Gunnar Gotshalks
01-3
What this Course is About
• Building software systems and components
–  small to medium systems
• Object oriented design and implementation
–  Design patterns
–  Multiple Inheritance
• Design by contract for quality software
• Documenting and describing software
• Evaluating design decisions according to quality factors
• Practice ... practice .... practice ...
© Gunnar Gotshalks
01-4
On Software Engineering
• Software engineering is a pure intellectual activity
–  Output is documentation
–  Program text is a form of documentation
• Difference with other engineering disciplines
–  Software has no physical characteristic
• no mass, no heat produced
–  Software implements highly complex functions in a flexible
way, making it an essential part of other systems
© Gunnar Gotshalks
01-5
What this Course in Not Directly About
• Requirements analysis: figuring out what a customer wants
• Teaching algorithms, data structures, syntax
• Teaching programming
–  expect that you know how to program
• Teaching a programming language
–  use a language to explain and apply the concepts
• Just getting programs to work
–  a program that executes is one small piece of the solution.
• WARNING: design is challenging
–  there is no right or wrong way to do it
© Gunnar Gotshalks
01-6
Why Eiffel? – 1
• Why not C++? Java? Smalltalk? Objective-C?
• This isn't a language course! You're here to learn about
design
• Want a language that supports software engineering and
production of quality software
• Want a language that has an integrated development
method
© Gunnar Gotshalks
01-7
Why Eiffel? – 2
• Want an industrial-strength language (Java? Getting better)
• Eiffel is used successfully on large projects
• People who have learned Eiffel and OO have no trouble
picking up
–  C++, Java, other design methods (Booch, OMT, UML,
Objectory, Fusion)
• Designers experienced with Eiffel and its methods are
generally more experienced, more competent, and more
versatile than others
© Gunnar Gotshalks
01-8
Study Strategy
• Don’t fall behind
–  Learning is work and self-testing
• Attend classes
–  Not all material is in textbook or slides
• For each class
–  Read relevant material before class
–  Do suggested exercises before class
–  Within 24hr after class re-read, think, and expand notes
If you do not reflect on and use the material within 24
hours you forget 50%, and within 48 hours you forget
80%.
© Gunnar Gotshalks
01-9
How to succeed
success_in_3311
require
some_courage -- mental and moral strength to venture
do
prepare_for_classes
attend_classes
critically_review_notes
plan_build_debug_software
ensure
enjoyment_and_mastery_of_the_material
end
© Gunnar Gotshalks – Curtesy Ali Mamoodi
01-10