CSE681 Lecture #1 Lecture #1 - Introduction 20 May 2007 ../../webpages/FawcettHome.xml ../../webpages/Courses.xml ../../webpages/Code.xml ../../webpages/Books.xml www.ecs.syr.edu/faculty/fawcett/handouts ../../webpages/research.xml ../../webpages/swdev.xml ../../webpages/webdev.xml ../../webpages/news.xml ../../webpages/OtherLinks.xml ../../webpages/SiteDesign.xml ../../webpages/AllPages.xml ../../webpages/notices.xml ../../webpages/CSE681.xml ../../webpages/CSE686.xml ../../webpages/CSE687.xml ../../webpages/CSE775.xml ../../webpages/CSE776.xml ../../webpages/CSE778.xml ../../webpages/CSE784.xml ../Lectures/CSE681CodeL1.xml ../lectures/CSE681CodeL2.xml ../Lectures/CSE681CodeL3.xml ../Lectures/CSE681CodeL4.xml ../Lectures/CSE681CodeL5.xml ../Lectures/CSE681CodeL6.xml ../Lectures/CSE681CodeL7.xml
../Lectures/CSE681CodeL8.xml ../Lectures/CSE681CodeL9.xml ../Lectures/CSE681CodeL10.xml ../Lectures/CSE681CodeL11.xml ../Lectures/CSE681CodeL12.xml ../Lectures/CSE681CodeL13.xml ../Lectures/CSE681CodeL14.xml
../Lectures/CSE681CodeL15.xml ../Lectures/CSE681CodeL16.xml ../Lectures/CSE681CodeL17.xml ../Lectures/CSE681CodeL18.xml ../Lectures/CSE681CodeL19.xml ../Lectures/CSE681CodeL20.xml ../Lectures/CSE681CodeL21.xml Content Syllabus

www.togethersoft.com/services/practical_guides/umlonlinecourse/ www.w3schools.com www.codeproject.com/library/tutorials.asp www.msdn.microsoft.com www.develop.com/devresources/default.aspx xml.com sellsbrothers.com www.wdj.com windowsforms.net/ www.dotnetjunkies.com www.gotdotnet.com www.c-sharpcorner.com www.go-mono.com msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/queryperformancecounter.asp

../../webpages/officeHours.htm

This lecture is an introduction to the CSE681 course. Today we discuss topics to be covered in this course, its projects, examinations, and grading. We then introduce the notions of Software Architecture, the Operational Concept Document, modules and discuss a standard notation to be used throughout the course. What is a program? What is an architecture? What is design? Structure of ../.., ../../webpages/notices.xml, ../../webpages/officehours.xml The Syllabus describes topics to be covered, reading material for you to digest before coming to class, and due dates for the assigned projects. ../projects What projects are required? How will your submissions be evaluated? ../projects/Pr1su07.doc and #3 develop Operational Concept Documents for programs we will implement in ../projects/Pr2su07.doc and #4.
../projects/pr5su06.doc develops an Operational Concept Document for a large, complex, and interesting system. All code will be developed using C# and the .Net Framework Class Library. How will your submissions be evaluated? ../projects/ArchGradeSheet.doc, ../projects/CSE681GS.doc ../../webpages/notices.xml ../../cse681/presentations/SoftwareArchitecture.ppt ../../cse681/presentations/ArchitectureConceptSurvivalGuide.doc Example OCDs prepared by students in previous classes: ../projects/OCDsample1.doc Excellent discussion of critical issues. ../projects/OCDsample2.doc Fine discussion of the program architecture. ../projects/OCDsample3.doc Good discussion of Use Cases. ../presentations/ProjectCenterUseCases.ppt ../../cse681/presentations/notation.ppt The Universal Modeling Language is used to describe software with means other than code. ../presentations/modules.ppt

---