Statistics AMS 5
Popular in Course
Popular in Applied Math And Statistics
This 30 page Class Notes was uploaded by Milton Sawayn DVM on Monday September 7, 2015. The Class Notes belongs to AMS 5 at University of California - Santa Cruz taught by Staff in Fall. Since its upload, it has received 55 views. For similar materials see /class/182149/ams-5-university-of-california-santa-cruz in Applied Math And Statistics at University of California - Santa Cruz.
Reviews for Statistics
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 09/07/15
CMPS 115 Winter 04 Class 2 20040108 ChangesReview Team Meeting lt10 minutesgt SW ReV Engineering SW DeV Processes CMM SW Processes framework RUP XP ltbreakgt SW methodology example IconiX Architecture Deliverable Expectations Lecture 1 Changes amp Takeaway Changes Drop exam 3 add Coding Standard requirement and 39 lecture to be AOP tutorial by AspectJ expert Wes Isberg Papers csllSreView Process methodology can mixnmatch Process is businessmanagement artifacts Methodology is technical req des decomp etc Fundamentals create tension in software development cost of error rises exponentially with time when fixed challenged by 39agile39 folks time value of money defers investmentwork 4 person ideal With overlap skills but strengths Facilitatormotivator organizer time allocator Communicator doc req elicit Tester also 0 n the tools amp setup p son l 2 i Ed Jackson had CMPSlO4A plus alg amp data struct Maria Ortiz maybe Chris 2nd yr AMS 5 yrs software engineer Reverse Engineering Support activity for maintenance information recovery Classic tools timesink but valuable mental activity Terms from reading Chikofsky Reverse engineering analyzing subject for Component identification and interrelationship Raising level of abstraction during maintenance design Redocumentation and designimplentation recovery Restructuring improve Without functional change essentially refactoring see Fowler for recipes Reengineering reverse engineering followed by re implementation often With added function RE Tools many internet links see e g httpscgwikiiamunibech8080SCG370 Intrinsically limited since multiple originals can lead to same outcome Static code gt diagram produce bad diagrams Impact analysis follow reference graphs click on a line or var get report of dependent linesvars Researcl product work recently in pattern detection also fragments as possible design errors component identification often using dynamic trace coupling discovery Via change analysis architecture recovery like component but different scale REMental Code reading is often needed Code reading is a practicable skill ref see Diomidis Spinellis Code Reading The Open Source Perspective Addison Wesley 2003 ISBN 0 201 79940 5 http WWW spinellis grcodereading practice on tutorial programs mark up read With intent recognize patterns learn the standard patterns depends on good naming clear programming comments help but are an art unto themselves Reading good code leads to writing good code Literate Programming code like a writer Knuth SW Dev Processes amp Methodologies process is an ordered collection of activities artifacts and dependencies that support management of the resources allocated to a software problem methodology illnamed but irreparable is a set of definitions activities and transformations that support the technical production of a software element throughout its life Example a waterfall process says requirements are developed before design and so forth but doesn t tell you how to structure the requirements or how to generate the design an object oriented development methodology doesn t tell you when to collect requirements or even that you need to actually but says you group together data and the methods that operate on that data Process Maturity SE1 Capability Maturity Models CMM software SWCMM systems engineering SECMM integrated product development IPDCMM merged in 2001 into CMM Integration nnnlm39 39 39 Becoming industry requirement a self amp audited assessment mama Baum particular level to bid like ISO900 preferred vendor WWW consulting business in doing audits l llill Process Maturity in Industry 3 160 project sample 26 to 1200 KSLOC Eu 5 4 3 2E 1D Prnjents Very Law Nominal High Wenr Extra law high high Quantifying the Effects of Process Improvement on Effort Clark IEEE Software NovDec 2000 Process Maturity Effect Quantifying the Effects of Process Improvement on Effort Clark IEEE Software NovDec 2000 1Ell Upper 95 conliden e l iLI39 1e on flffffr 1E ne level average change l Lower 95 confidence limi l econ Lxr39 quotquotquotquotF F39 r d r eon Hill n redncllon In ellorl per one level change In process Inalun 3r F Fe D D 1 1 H I N n 1amp0 zoo eon eon 500 Thousands of lines of code General Process Elements Goal setting business goals use cases requirements stories Work product definition chunks tasks budgets part management part technical decomposition Implementation Management schedule track feedback Code unit test integrate Test Deploy Different processes are different permutations of these Support Change Management Environment Process Elements Work Prod Def Divide into manageable pieces product decomposition requirement analysis design Work Breakdown Structure WBS pieces that can be each tracked budgeted 3 months same items used in budget and schedule functional product timephased hierarchies possible Product size estimation SLOC FP stories scenarios SLOC is most common SLOC is malleable number Boehm vs C Jones Often contractual basis for payment Process Elements Implement Implementation Control tasks milestones dependencies for labor tracking planning budgeting Simple Gantt timelines Probabilistic Program Evaluation and Review Technique Critical Path PERT using only nominal find longest path Team Velocity XP in storiestime leads to timeboxing You pay to measure Fundamental you optimize what you measure Code unit test integrate is the development methodology SW Dev Process Examples Rational Unified Process modern heavyweight thinking ceremonial tailorable UML centric 4phase inception elaborate construct transition iterative Extreme Programming XP agile family customerinvolved evolutionary requirements constant conversation built least code to meet latest conversation build test to define goal buildrefactor until pass always run all tests Inceptiun Elabura un Construction Trans m39an DISCIPLINES 5 39 BUSINEESMOPELWG REQUIREMENIS CONFIGURATION 8 CHANGE MANAGEMENT PROJECTMANAGEMENT A A AA ENVJB39MMENT MILESTONES J MILESTONESJ MILESTONES 41 x I I i Elam Hahn lCnnsH 39CunsszCunsmNman MITran 2 TEHAT ONs From IB MRavjonal summary poster RUP Bus Modelling From IBMRational summary poster Assess Bus Status magmas Modehngl Describe cunem Bu nsss mcepuonl 1 less Early Identify Busmess Processes Re ne Enams H Pinass he itiun Db Exmnm 5b Process Autuma nn Dasi Business Frncnss Rea zmirms l Re ne Roles and Rapunslhllm39w RUP New System New nput Analyze the Understand thlem Stakeholder EPgt Needs Manage Changing Requirements Addressing correct Pmmam Can t Do AH the Work Define the Manage the Scope System at the System EH5 Refine the System Deri From S MRauonal summary poster quot Eaiw lnceplimi Eiaburatmn Heramm A heratmn Ommnam De ne a candidate Design Demim Auhitenural Synthesis 5 Analyze Eehavini f Ammtectuve 13 043 Design Components OptionaH Design the Database From EMRational summary poster RUP E Implement Plan me Integration mplemenl cumnnnenls 4 sonmunems vmmemented and vahdatedl More Cumnunents 0 P WW Mo Integrate each fur ms nemmm MSW Subsystem lmegralmn 1m um Renaler v Sunsysmms Immemeuled aHd mama Imagrale me syszem Done Done are System awn forims mane From IBMRational summary poster v v nevanw w m m 1m R Test R RUP 9 Conf amp E Chg Mn g 23M Cu Chan 3 Comm 1 Manage create onJen change Requests CM Envlmnmems L1L E Mnnll078lt Regan change and Dellvar Manage Baselines cun gnmuon status conng munn Items and Releases From EMRamona ummary puxter From IBMRational summary poster sun 0 Frayed Only ml Subsequent HvraHDHs Manage nemuou I a e Cunnelva Plan lo new man mm Iteratinn Remandzmv Vnmal L Pm ecl nevauan in msqu 5mm Canceled ltgt We gt Hurannn Successful Evaluate From EFL Scnpe am Elsk i F Evaluate ijact I Scope and Risk Monim amp Control Pmiacl Pmch Emu Phase End memuuu End g Fm zm mans Closeout Clnsbom LF39VDJEC Appmea Pmlect Phase canceled Projecl mum Cnmulem 39 Cancelud Canceled Canceled Faned IF Wso Q Ptolec39t pmle Acceptance cummcm 0199 i Ophunah dapandlng on degree F or chunga From IBMRational summary poster 1 End mm XP This is one Hhc premises of XP It is 1391 technical prcmlac of X1quot I39 the amt ofdmngc msc slowly over lm you would act completely n lifi fercmlv From how you do under the umption that mm 156 chuncn Lirrlly You would make big decisions as late in the process Ah poss1blc to Cnsr 0F CHkNEE 4 l39lME FIGURE 3 The cost of change may not rise dramatically over time From extreme programming explained by Kent Beck XP DHFEWE CU Emma Practices PlPxHH39lrmkGMJLE 413 HDURWEEK METAplml SIMP Labeslm H Show Rabin3 ES Tam tangerine Maeganx19 Cow wuaua INTEeaniDN 0m th 3TANDARBS From extreme programming explained by Kent Beck Process Can Trap You Very large efforts have contractual interfaces with big implications longterm budgets and commitments statistical characteristics Techniques for these PERT CPM waterfall models have worked very well in their domain but these techniques don t scale down very well Your process should be organic it codifies what works for you and nudges you towards being a little more predictable and then you change the process to track your continuous software process improvement SW Dev Methods Three families are optimizationfocused based on the idea you are creating the elements and optimizing them to your purpose Classical Object Oriented Formal design classical inXfrmout modules in hierarchies C code OO encapsulated datastatemethods in communication nets Smalltalk Java C formal requirements stated as theorems proving desired characteristics logically automatic generation of implementing code and verification by mathematical argument the formal analysis methods can be applied to any body of code in theory Z language Recent approaches are selectionfocused COTS or crosscutting aspects features ProcessMethod Examples Modified Waterfall with simplified OOU ML concept CONOPS doc UML Activity requirements with GUI prototype REQ doc Use Case models validate amp refine with Robustness architecture UML structure for Domain then classes detail design UML classsequence codedebug SCM checkins metrics system test ATP SCEN plus nonfunctional REQ Simplified UML IconiX Process b f 39iETmlff quot W I II 39 i a 3 3 Sequence Hovrillel 1 39 4 Diagram quota Robustness I l 395595391 i 1 Static if Domain mass 39quot 3939I39lt iagram s Project Selection Expectations Team name and website URL Team membercontact list also on website Platform JZSE JZME if J2ME profile eX2J2SE with Swing in P2P using JXTA network ex J 2SE server with Tomcat Seeret engine J 2MECLDC monochrome phoneFDA Short game and system description
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'