CSE681 Lecture #1 CSE681 - Software Modeling and Analysis Lecture #1 - Introduction 27 May 2010 ../../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
../Lectures/CSE681CodeL22.xml ../Lectures/CSE681CodeL23.xml ../Lectures/CSE681CodeL24.xml ../Lectures/CSE681CodeL25.xml ../Lectures/CSE681CodeL26.xml ../Lectures/CSE681CodeL27.xml ../Lectures/CSE681CodeL28.xml Syllabus StudyGuideSMA.xml StudyGuideOCD.xml StudyGuideNotes.xml
edn.embarcadero.com/article/31863 www.w3schools.com www.codeproject.com/ www.msdn.microsoft.com www.develop.com/devresources/default.aspx xml.com sellsbrothers.com www.ddj.com/windows/?cid=vnav windowsclient.net// www.dotnetjunkies.com asp.dotnetheaven.com/ www.c-sharpcorner.com www.go-mono.com msdn.microsoft.com/en-us/library/w8f5kw2e(VS.71).aspx
../../webpages/officeHours.xml
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? cse681Note1.xml, cse681Note2.xml ../presentations/modules.ppt, ../Code/Parser
Packages are the building blocks for a complex architecture. CSE681Note6b.xml
A rational way of building large, complex software systems. The Syllabus describes topics to be covered, reading material for you to digest before coming to class, and due dates for the assigned projects. StudyGuideSMA.xml, StudyGuideOCD.xml, StudyGuideNotes.xml Structure of ../.., ../../webpages/notices.xml, ../../webpages/officehours.xml ../Midterm/MTSp10/MT1Sp10InstrSol.doc ../projects What projects are required? How will your submissions be evaluated? ../projects/Pr1F10.doc Operational Concept Document for File Dependency Analysis

../projects/Pr2F10.doc File Dependency analysis across file set

../projects/pr3F10.doc Operational Concept Document for Test Harness

../projects/pr4F10.doc Client/Server test harness system

../projects/pr5s10.doc Develops an Operational Concept Document and code prototypes for Quality Assurance Tool Set, a large, complex, and interesting system. All code will be developed using C# and the .Net Framework Class Library with Visual Studio 2010. How will your submissions be evaluated? ../projects/ArchGradeSheet.doc, ../projects/CSE681GS.doc ../../webpages/notices.xml ../../cse681/presentations/SoftwareArchitecture.ppt ../../cse681/presentations/ArchitectureConceptSurvivalGuide.doc ../presentations/ProjectCenterUseCases.ppt This presentation was developed for a Software Studio project. It gives you a good idea of the kind of analyses you need for an OCD. ../../cse681/presentations/notation.ppt The Universal Modeling Language is used to describe software with means other than code. You will use these diagramming techniques in your OCD.