CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!Software Engineering: Analysis and Design - CSE3308Da"id S#uireDa"id!S#uire$csse!%onas&!edu!au'oo% 3(, )uilding *5, Clayton++05 830*'oo% 5!23A ) )loc,, Caulfield ++03 033 -t&an,s to .artin Dic, for initial de"elo/%ent of unit resources0CSE33081D.S1200512CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!2Lecture Outline2nit 3utline4&at is Software Engineering54&y )ot&er wit& Software Engineering56roduct and 6rocessCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!3Unit outline378ecti"esAssess%ent6assing t&e unitLectures, /ractice classes, t&e lecturer and consultation'eco%%ended readingAssign%ent wor,4e7 /agesCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!(Obecti!es "#$9nowledge of t&e difficulties of s/ecifying and /roducing large software /roducts, leading toan a//reciation of t&e need for software engineering %et&odologiesunderstanding of t&e distinction 7etween software engineering and /rogra%%ing, and t&us t&e distinction 7etween a software configuration and a /rogra%An understanding of, and a7ility to a//ly, t&e %et&ods of analysis and design, including:structured analysis and design using :ourdon notation Conte;t Diagra%, E"ent Lists, Data-! =&e 2nified .odeling Language 2ser Iuide -++80 :ourdon, E!: .odern Structured Analysis -+8+0 6ress%an, '!, Software Engineering: A 6ractitionerKs A//roac&, -20000=&e lecture slides are long and detailedLt&e intention is to gi"e you t&e %aterial you will needA list of furt&er useful 7oo,s is /ro"ided in t&e 2nit 3utline! Co/ies of t&ese 7oo,s are on reser"e in t&e li7rary!CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!Assign&ent wor)All wor, su7%itted 7y a grou/ %ust 7e solely t&e wor, of t&at grou/All wor, su7%itted 7y an indi"idual %ust solely 7e t&e wor, of t&at indi"idual=&is is not to %ean t&at you %ay not consult wit& ot&ers, 7ut:>f you recei"e any &el/, you %ust s/ecifically ac,nowledge t&at /erson in your su7%itted wor,>f any student or grou/ of students su7%its wor, w&ic& is not t&eir own, t&ey will 7e disci/lined according to t&e 2ni"ersity and f you 7elie"e t&at your assign%ent will 7e delayed 7ecause of circu%stances 7eyond your control, you %ust a//ly for an e;tension before t&e due date .edical certificates or certification su//orting your a//lication %ay 7e re#uiredContri7utions to grou/ wor, Irou/ %e%7ers will rate t&e contri7utions of all ot&er %e%7ers t&ese ratings will %odify t&e %ar, t&at eac& indi"idual recei"es, 7ut not 7y %ore t&an 20B! >f a grou/ is &a"ing trou7le wit& an indi"idual %e%7er and is una7le to resol"e t&e /ro7le% t&e%sel"es: t&e grou/ must a//roac& t&e lecturer to assist in resol"ing t&e /ro7le% as soon as it arises A clai% t&at a student did not contri7ute &is or &er fair s&are will not be considered if it is %ade 8ust /rior to t&e su7%ission of t&e assign%ent, or after su7%issionCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!3*eb site=&e unit we7 site can 7e found at:&tt/:11www!csse!%onas&!edu!au1courseware1cse33081>nfor%ation at t&e we7 site will include:Lectures slidesAssign%ent s/ecifications'esources and lin,s rele"ant to t&e unitAnony%ous feed7ac, foru%:ou s&ould c&ec, t&e unit we7 site eac& wee,CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!(*+at is Software Engineering,Irou/ E;ercise)rea, into grou/s of ( or 5 -i!e! your neig&7ours, donNt %o"e around t&e t&eatre0=a,e 5 %inutes to write down a definition of software engineering - t&is can 7e in /oint for%After 5 %inutes, we will collect definitions fro% t&e classCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!5*+at is Software Engineering,.any DefinitionsCO t&e esta7lis&%ent and use of sound engineering /rinci/les in order to o7tain econo%ically software t&at is relia7le and wor,s efficiently on real %ac&ines!D -)auer +A+0 C=&e a//lication of science and %at&e%atics 7y w&ic& t&e ca/a7ilities of co%/uter e#ui/%ent are %ade useful to %an "ia co%/uter /rogra%s, /rocedures, and associated docu%entation!D -)oe&% +80C=&ea//lication of a syste%atic, disci/lined, #uantifia7le a//roac& to t&e de"elo/%ent, o/eration and %aintenance of softwareP t&at is t&e a//lication of engineering to software!D ->EEE ++30 Designing, 7uilding and %aintaining large software syste%s in a cost-effecti"e way!CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!A*+y bot+er wit+ Software Engineering,.any "ery successful /ro8ects donNt use software engineering, e!g! early .icrosoft >D SoftwareNs Doo% SausageNs Fotdog)2= t&ey are often not re/eata7le.any %ore /ro8ects fail 7ecause t&ey donNt use software engineering! s not t&e sa%e as a &ardware /roductSoftware is de"elo/ed or engineered, it isnNt %anufactured li,e a /ersonal co%/uterSoftware doesnNt wear out.ost software is custo%-7uilt, rat&er t&an 7eing asse%7led fro% e;isting co%/onentsA software /roduct s&ould /erfor% t&e re#uired function7e relia7le7e %aintaina7le7e efficient &a"e an a//ro/riate user interface&a"e an a//ro/riate lifeti%eCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!22A good software 0roduct,CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!23.+e Software 'roduct>s co%/osed of6rogra%sDataDocu%entation re#uire%ents, analysis R design docu%ents, wal,-t&roug& %inutes, test /lan, user %anuals, etc!often referred to as t&e Csoftware configurationD=wo %ain ty/es of /roductIeneric - eg! 4indows, .acintos& a//lication software)es/o,e - Syste%s created for s/ecific a//lication areas.ost software e;/enditure is generic.ost software de"elo/%ent effort is 7es/o,eCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!2(.+e Software 'rocess=&e set of acti"ities and associated results w&ic& /roduce a software /roduct=&e se#uence of ste/s re#uired to de"elo/ and %aintain softwareSets out t&e tec&nical and %anage%ent fra%ewor, for a//lying %et&ods, tools and /eo/le to t&e software tas,Definition:=&e Software 6rocess is a descri/tion of t&e /rocess w&ic& guides software engineers as t&ey wor, 7y identifying t&eir roles and tas,s!CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!25C+aracteristics of a good 0rocess2nderstanda7ility?isi7ilitySu//orta7ilityAcce/ta7ility'elia7ility'o7ustness.aintaina7ility'a/idityCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!2A.wo 1uestions>s t&ere a rig&t /rocess for software engineers to ado/t54ill &a"ing a good /rocess guarantee a good /roduct5CSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!2**+en do we need 0rocess,4e always &a"e so%e /rocessS=&e larger t&e /ro8ect, t&e greater t&e need for a for%al /rocessCo%/le;ity of 7uilding a syste% w&en related to siMe is not linear!SiMe Effort'e#uiredErrorsafterreleaseIigatron 5,00025Iigatron 2Delu;e50,000 20 3*5 -5ti%esCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!28Deter&ining 'rocessSe"eral Sc&e%es2S De/art%ent of Defense use t&e 6ro8ect %/le%entation of t&e syste% into t&e wor,ing en"iron%ent and re/lace%ent of t&e e;isting syste%.aintenanceCorrecti"eAda/ti"e6erfecti"eCSE3308 - Software Engineering: Analysis and Design, 2005 Lecture A!33(eferencesT6re2000U 6ress%an, '!, Software Engineering: A Practitioner's Approach, .cIraw-Fill, 2000, -C&a/tersand 20!T.cC++*U .cConnell, S!, Less is More: ump!Start Productivity with Small "eams, Software De"elo/%ent, 3cto7er ++*, //! 28-3(!&tt/:11www!ste"e%cconnell!co%1articles1art0A!&t%