Popular in Course
Popular in ComputerScienence
This 29 page Class Notes was uploaded by Vito Kilback on Wednesday September 23, 2015. The Class Notes belongs to CS451 at Drexel University taught by YuanfangCai in Fall. Since its upload, it has received 52 views. For similar materials see /class/212445/cs451-drexel-university in ComputerScienence at Drexel University.
Reviews for SoftwareEngineering
Report this Material
What is Karma?
Karma is the currency of StudySoup.
Date Created: 09/23/15
CS 451 Software Engineering Winter 2009 Yuanfang Cai Room 104 University Crossings 2158950298 yfcaicsdrexeledu Drexel University The Inspection Process Drexel University Background El Main goal of inspection process is to detect defects in work products El First proposed by Fagan in 708 El Earlier used for code now used for all types of work products El ls recognized as an industry best practice El Data suggests that it improves both QampP a Drexel University Background II Defects injected in sw at any stage El Hence must remove them at every stage El Inspections can be done on any document including design docs and plans El Is a good method for early phases like requirements and design El Also useful for plans PM plans CM plans testing plans Drexel University Some Characteristics El Conducted by group of technical people for technical people ie review done by peers El Is a structured process with defined roles for the participants El The focus is on identifying problems not resolving them El Review data is recorded and used for monitoring the effectiveness 5 Drexel University A Review Process cm me Meeting Defects Log Recommendation Rewafkamp Fallnw Liv Reviewed Work mater Summary Report 6 Drexel University Planning El Select the group review team three to five people group is best El Identify the moderator has the main responsibilityfor the inspection El Prepare package for distribution work product for review plus supporting docs El Package should be complete for review 7 Drexel University Overview and SelfReview El A brief meeting deliver package explain purpose of ther view39 El All team members then individually review the work roduct I Lislslhe issuesproblems Iheylind in Ihesellrpreparalion log I Checklistsguidelines are us El Ideally should be done in one sitting and issues recorded in a log E Drexel University SelfReview Log Project name Work product name and ID Reviewer Name Effort spent hours Defect list No Location Description Criticality 9 Drexel University Group Review Meeting El Purpose define the final defect list I Entry criteria each member has done a proper selfreview logs are reviewed El Group review meeting I A reviewer goes over the product line by line I At any line all issues are raise I Discussion follows to identify if a defect I Decision recorded by the scribe m Drexel University Group Review Meeting El Atthe end of the meeting I Scribe presents the list of defectsissues I If few defects the work product is accepted else it might be asked for another review I Group does not propose solutions though some suggestions may be recorded I A summar of the inspections is prepared useful for evaluating effectiveness n Drexel University Group Review Meeting II Moderator is incharge of the meeting and plays a central role I Ensures that focus is on defect detection and solutions are not discussedproposed I Work product is reviewed not the author of the work product I Amicableorderly execution of the meeting I Uses summary report to analyze the overall effectiveness of the review 12 Drexel University Summary Report Example Project XXXX Work Product Type Project plan Size of work product 14 pages Review team P1 P2 P3 Effort person hours Preparation 10 total Group meeting 10 Total 20 n Drexel University Summary Contd Defects No of critical defects No of major defects No of minor defects Total Review status Reco for next phase Comments 0 3 16 19 Accepted Nil Nice plan Drexel University Rework and Follow Up El Defects in the defects list are fixed later by the author El Oncefixed author gets it OKed by the moderator or goes for another review El Once all defectsissues are satisfactorily addressed review is completed and collected data is submitted 15 Drexel University Roles and Responsibilities El Main roles Moderator reader scribe author reviewer El Moderator overall responsibility El Reviewer to identify defects El Reader not there in some processes reads line by line to keep focus El Scribe records the issues raised is Drexel University Guidelines for Work Products Design is implementable Designer Designer Developer Guidelines for Work Products Detects in code Drexel University Drexel University SR8 Review Criteria a Meet Customer Needs a Implementable 39ssions El Forexample the chess gameSRS shouldat leasthave the following iOi iS luhct El Ehterthe Game in Playthe Game Egtltit the Game El Savereload the Game n Inconsistencies 9 functions shown in use cases are not specified a Ambiguities n E g 1he size of the input file shouldn t be too largequot Drexel University Summary El Purpose of reviews to detect defects II Structured reviews are very effective can detect most of the injected defects El For effective review process has to be properly d defined and followe El Data must be collected and analyzed Drexel University CS 451 Software Engineering Winter 2009 Yuanfang Cai Room 104 University Crossings 2158950298 yfcaicsdrexeledu Drexei University Information Hiding Drexei University A Canonical Example The K WIC index system accepts an ordered set of iines each iine is an ordered set of words and each word is an ordered set of characters Any iine may be circuary shiftedquot by repeatedy removing the first word and appending it at the end of the iine The K WIC index system outputs a iisting of ai circuar shifts of ai iines in aphabetica order Drexei University A Canonical Example Key Word in Context P31113572 in u So warcArchitccture 1 2 Circuiarshiii Senseaiiitcc isiciivw 3 A Dhabe izmg Crouching Tiger Hidden Diagon 4 uipui Architecture So war ari Sensihihui sei and tiger Hidden Dragon Crouching Hidden Dragon Crouching Tiger Dragon Crouching Tiger Hidden Drexei University Design for Change I What if I Memory Size change I Input Size change I Input Format change I Alphabetizing Policy change A Main ProgramSubroutine Architecture IE Modules Functions Direct Memory Access I Data Rep m Mammy 4 Subprogram Call El no Medium system V0 5 Drexel University 5 Drexel University Review Main ProgramSubroutine Architecture Changeability Analysis Changes Affected Modules 1 Input Format Input 2 Not to store all lines in core All 3 Not to pack characters All 4 Store full shifted lines All except input 5 Different Alphabetizing Alphabetizer Output Drexel University The Data Abstraction and Object Oriented Architecture Itimmmm Irvin3 El Modules Dialects Methodlnvacallori I Public interrace m IO El Io Medium Drexel University Review The Data Abstraction and Object Oriented Architecture Changeability Analysis t0 store to Drexel University Design Principle Information Hiding Identify the aspects of your application that vary and separate them from whatstays the same a e what varies and The result Fewer extract it so it won39t unintended consequences affect the rest of your from COde Changes arid code more flexibility in your ystem Drexel University Design Principles Dependency Inversion Program to an interface not an inwlementation Favor coirposition over Inheritance Separation of Concern Open close principle Lesson knowing major 00 concepts like encapsulation inheritance polymorphism does not automatically make a good designer A design guru thinks about how to create flexible designs that are maintainable and that can cope w th Drmi University Goodbye and Good Luck A Drmi University CS 451 Software Engineering Winter 2009 I Design within the Context of Yuaniang Cal Room 104 University Crossings SOftware Engmeerlng 2158950298 yicaicsdrexeledu 2 Drexel University D rexel U n iversity Translating the Analysis Model Software Design into the Design Model El Between Requirement and Coding Scenariobased FlowOriented Tl thenfs r f elements 1 fr n Usecisees text Data ow diagrams 39 USecase diagrams Controlllow diagrams I Data DeSIgn Activity diagrams Processing narratives gt n r V I I Swim lane diagrams 39 iIn tezrf a cz39e ie sig n I Architectural Desngn 39 I Interface Design AnalyssModel I component DeSign il l39Clqss based A BBhGViOWl39EL D g 3739 ff39 l 39inerfts 7 elements 339 I Need to be modeled analyzed and revnewed in Class diagrams giate diagrcjzms I 39 Analysis packages 4 H equence iagrams Industri al strength software CRC modek Collaboration diagrams l D rexel U n iversity D rexel U n iversity Design Process and Desgin Quality Drexel University Design Engineering El Software design is an iterative process through which requirements are translated into a blueprint for constructing software I Abstraction l Refinement Drexel University Design Engineering contained int e analysis mo e a accommodate all of the implicit requirements desired by the customer El A design must be a readable understandable guide for those who generate code and those who test and subsequently support the software The design should provide a complete picture of the software addressing the data functional and behavioral domains from an implementation perspective El A design must implement all of the explicit requirements h d n it must El Drexel University Design Quality El FURPS Functionality Usability Reliability Performance and Supportability El Functionality assessed by evaluating o the feature set 0 capabilities of the program El Usability assessed by considering 0 human factors 0 overall aesthetics o consistency o enduserdocumentation E Drexel University Design Quality Functionality Usability Reliability Performance and Supportability El Reliability is evaluated by measuring 0 the frequency and severity of failure 0 the accuracy of output results 0 the meanrtimertorlailure o the ability to recover from failure 0 the predictability of the program El Performance is measured by 0 processing speed sponse time resource consumption throug put e iciency Drexel University Design Quality Functionality Usability Reliability Performance and Supportability El Supportability combines o the ability to extend the program extensibility o adaptability o serviceability o testability o compatibility o configurability Drexel University Design Concepts ormi University Design Concepts El Abstraction II Architecture El Patterns El Modularity El Information Hiding El Functional Independence El Refinement El Refactoring I Design classes ormi University Design ConceptsAbstraction El Abstraction is one of the fundamental ways that we as humans cope with complexityquot Grady Booch El What kinds of things do we abstract 0 data 0 objects 0 procedures 0 modules 0 just about anything Drexel University Design ConceptsArchitecture El Software architecture alludes to the overall structure of the software and the ways in which that structure provides conceptual integrity for a system El Architecture is o the structure or organization of program components modules 0 the manner in which these components interact o the structure of data that are used by the components Drexel University Design ConceptsPatterns El A pattern is a named nugget of insight which conveys the ssence of a proven solution to a recurring problem within a certain context amidst competing concernsquot El Each pattern describes a problem which occurs over and over again in our environment and then describes the core of the solution to that problem in such a way that you can use this solution a million times over without ever doing it the same way twicequot Christopher Alexander Drmi University Design Concepts Modularity El MODULARITY l Modularity is the single attribute of software that allows a program to be intellectually manageablequot l Software is divided into separately named and addressable components sometimes called modules that are integrated to satisfy problem requirements El See FIGURE 92 Drmi University Design Concepts nformation Hiding El Modules should be specified and designed so that information algorithms and data contained within a module is inaccessible to other modules that have no need for such information El This means that inadvertent errors introduced during modification are less likely to propagate to other locations within the software El Changes to the internal representation of one module should have not have an effect on other modules n Drexel University Design ConceptsFunctional Independence El Functional independence is achieved by developing modules with singlemindedquot function and an aversion to excessive interaction with other modules El We want to design software so that each module addresses a specific subfunction of requirements and has a simple interface when viewed from other parts of the program structure Drexel University Design ConceptsFunctional Independence El Independence is assessed by using two qualitative criteria I Cohesion How related a module is to itself It should perform a single task and require little interaction with the rest of the program I Coupling is an indication of the interconnectoin a ure mong modules In a software struct Drexel University Design ConceptsRefinement El Stepwise refinement is when a program is developed by successively refining levels of procedural detail El Refinement is actually the process of elaboration Drexel University Design ConceptsRefactoring El Refactoring is a reorganizational technique that simplifiesthe design of code of a component without changing its function or behavior Drexel University Design ConceptsDesign Classes El Refine analysis classes by providing design details El Create a new set of design classes that implement a software infrastructure to support the business solution El Five types I Userinlerlaceclasses I Business domain classes I Process classes I Persistenlclasses I Systemclasses Drexel University CS 451 Software Engineering Winter 2009 Yuanfang Cai Room 104 University Crossings 2158950298 yfcaicsdrexeledu Drexel University From Requirement to 00 Design Identify use cases from SRS EIEIEIEI I UML state diagrams I UML sequence diagrams Find analysis classes from use cases Create CRC cards from use cases Refine CRC cards into UML class diagrams Analyze and model the behaviors using I UML collaboration diagrams El Design the architecture using UML component diagrams II Create UML deployment diagrams El Detailed Design Drexel University From Requirement to 00 Design 8 II Identify use cases from S EIEIEIEI I UML state diagrams I UllIL sequence diagrams I UML collaboration diagrams Design the architecture using lr39 Create UML deployment diagrams Detailed Design EIEI Drexel University Refine Analysis Model Requirement into Design Model Design I Identify use cases from SRS I Find analysis classes from use cases I Create CFlC cards from use cases I Refine CRC cards into UML class diagrams I Analyze and model the behaviors usrng I UML state diagrams I UML sequence diagrams I UML collaboration diagrams I Design the architecture using UML component diagrams I Create UML deployment diagrams I Detailed Design Floworiented e lem ent39si u i I Data ow diagrams ControlHow diagrams Processing narratives arissbqseci rh nts 5 UseCases text Use case diagrams Activity diagrams Swim lane diagrams jse n Analysis Model thehqviora39ql V39element39s quot State diagrams Sequence diagrams Class diagrams Analysis packages CRC models Collaboration diagrams Drexel University Fr El until an El om Requirement to 00 Design Identify use cases from SRS See ATM Example Find analysis classes from use cases Create CFlC cards from use cases Refine CRC cards into UML class diagrams Analyze and model the behaviors using I UML sate diagrams I UML sequence diagrams I UML collabora a39on diagrams Design the architecture using UML componentdiagrams Create UML deploymentdiagrams Detailed Design Drexel University From Requirement to 00 Design El until an El Identify quots 5 from SRS Find analysis classes from use cases See ATM Example Create CFlC cards from use cases Refine CRC cards into UML class diagrams Analyze and model the behaviors using I UML sate diagrams I UML sequence diagrams I UML collabora a39on diagrams Design the architecture using UML componentdiagrams Create UML deploymentdiagrams Detailed Design Drexel University From Requirement to 00 Design El until an El Identify from SRS Find analysis classes from use cases Create CRC cards from use cases See ATM Example Refine CRC cards into UML class diagrams Analyze and model the behaviors using Design the architecture using UML componentdiagrams Create UML deploymentdiagrams Detailed Design Drexel University CRC Cards Drexel University Introduction to CRC Cards El CRC Card Class Responsibility Collaborator Card El Purpose interactively brainstorm an initial design of a program or program segment El Invented in 1989 by Kent Becfa Cunningham l7 39 Drexel U niversity CRC Cards II Class the name of an 00 class a good descriptive noun II Responsibility the things the 00 class does behavior responsibility I Collaborator the relationship the class has with other classes Class Name 4 X 6 Main Responsibility Stir 3 X Responsibilities Index Collaborators card Some also suggest writing down the classes properties what the class must know about itself knowledge responsibility on the back of the card Drexel U niversity An Example CRC Card Front Front Class Nollie Patient Mai A patient makes appointments review or configure Responsibilit y insurance information and provides medical history Hospmsihililim Collaborators Malta appointment Appointment Calculate last visit Change status 7 Prm ide medical historr l r39ledlcal historyr Drexel U niversity An Example CRC Card Back r tllrihules Amount double lnsurante carrier teth litla ionships Goneralinlion laItindoil Person i iggrogalion hasparts Medical I Iistorjr Other Associations Appointment Slide 12 Drexel U niversity Step 1 Identity and assign candidate classes El Read requirements specification El Highli ht nouns and noun phrases to give candi ate classes excluding abstract nouns El Write each candidate class down on an index card Assign each index card to one person who is participating in the CRC card modelling session Drexel Urllverslty Step 1 Identity and assign candidate classes l Consists of classes of domain objects I Example any ATM model will involve Card BankAccount classes I Names are important l Class identification is a key process for a good class model I noun identification I responsibility driven approach Drexel Urllverslty Noun identification a Two stages requlremerlts specltlcatlorl document I dlscardlrlapproprlatecal ldldates A candidate is an inappropriate class when it is redundant ex book booklrl manyvolumes member oi the llbraryllbrarymem er vague tltem it may be eltherbook orlourrlal etc an event or an operatlol39l a loane an event lendlng a book El t and the system at a very high level system rule inlormation or reporting requirements a outsidethe scope oi the system time u an attribute name Drexel Urllverslty ATM Non Identification El Nouns are outlined insert card inserts card valldates the m entered by the user against lne central ampvzlidate PIN record held an the bank svste eml e can sentlnue lrtne PlN is not correct en e sesstonwtit temnnate and tne Card snuuld be returned to the user it allows changingd le luur dtgtl PIN wtm a new value it displayspunts out the mnem balance alme bank account T ie I is 5 n 1quot EE 6 g the cards released and the cash ts dispensed to candntons ts lalsetnen tine uustumerwlll be pmmpted o conslder another 09mm Drexel Urllverslty ATM A Nouns old card 7 class m PlN four digit PIN 7 all are attributes or card 7 outside the scope of the system 7 vague bank 7 Que will 7 mela7language session session 7 vague ll mlgm became of interest changlng 7 metaltlarlguage value 7 me 7language current balallne current balance 7 attnbule oi bank account bank anon nk account assoclaied bank account 7 one ofthese E a class ll ATMProvisional Classes ll Class candidates a d I c r I bank account ATM dispenser amp session 7 vague it might become ol interest ta associate PIN 7 attribute ol card El Ell custom customer 7 out s 9 Scope of lhs system amount mum lree cholce amoun eunested amount Euested amount 7 altnbmes L 7meta7language I current balance 7 attrlbute ol bank account ovemrah llmtl 7 attrlbute of bank a Lav rw de he mp6 owe myquot I amount 7 attrlbute ln varlous classes 4Mquot d 5 W E i s I overdralt limit 7 attribute ol bank account summons candltlorls 7 melsaanguage card llmligerday 7mmbute cicard I card llmlt per day 7 attrlbute ol car dlsgnser amount 7 attrlbute of ATM dgpenser 9h me mngmge I dlspenser amount 7 attrlbute ol ATM dlspenser ggnon 7 meuJanguage 1E Drexel University Drexel University Step 2 Step 3 Walkthrough the scenarlo namlng Determine a set of specific scenarios ll Develop a comprehensive and specific set of endtoend scenarios based upon the requirements I A scenario is a sequence of actions that iustrates behavior ll Example I Requirement The alarm clock shall allow a user to set the time I Scenario The user sets the time for 115PM Drexel University cards and responsibilities ll Walkthrough the handling of ascenario case pointing to or picking up the cards naming their responsibilities and how they handle and delegate each request I Add new cards as classes are needed I Note It s always good to do ver basicmainstream use cases first then explore alternativecomplicated use cases Drexel University CRC Cards 9 What next Write main responsibility for each class Split c asses when needed Tum these car s inm yourclass diagram Card gt class Responsibilities gt Methods Collaborators gt Associations need to have instances of collaborating classes ta members on the card back gt Attributes Class Name or 394 y Main Responsibility Responsibilities Collaboramrs Drexel University Clear Intersection Example ll Car wants to drivethrough an intersection ll The car can only drive through the intersection if the traffic light is green and there are no cars in the intersection ll Otherwise the car needs to join a queue Drexel University Step 1 Identify and assign candidate classes ll Car wants to drive through an intersection ll The car can only drive through the intersection if the traffic light is green and there are no cars in the intersection ll Otherwise the car needs to join a queue ar Traffic light Queue Intersection Drexel University Step 2 Determine a set of specific scenariosBuild Use Cases ll Car approaches the intersection and the light is green and there are no cars in the way ll Car approaches the intersection and the light is red ll Car is in the queue and the light turns green Drexel University Step 3 Walk through the scenario naming cards and responsibilities Index Card Car El 1quot I 39 4 cl lighlis green and there are no cars in the I Drive way I Join Cara roacheslheinlerseclionandlhe El Collaborator wilted I Traffic light Car is m the queue and the light turns I Queue green I Intersection I Drexel University From Requirement to 00 Design El Identify quots from SRS Find analysis classes from use cases ElEIEI Create r a from use cases Refine CRC cards into UML class diagramsSee ATM ample Analyze and model the behaviors using I UML smte diagrams I UML sequence diagrams I UML colabora a39on diagrams Design the architecture using UML componentdiagrams Create UML deploymentdiagrams a Detailed Design El Ell Drexel University UML and Class Diagrams Drexel University What is UML El UML Unified Modeling Language 20 I A standard for modeling objectoriented software I Resulted from the convergence of notations from three leading objectoriented methods OMT James Rumbaugh n OOSE Ivar Jacobson n Booch Grady Booch El For more information on the Object Management Group OMG see httpwwwomgorg Drexel University Class Diagram Class 9 Under a dateReoeived Date 0 isPI39epaicl Boolean o nLrnber Stling 0 price Money 9 dispatch 1U 9 close n A class encapsulates state 5 3 and behavior w I Each attribute has a zquot I Each operation has a El The class name is the only mandatory information Drexel University Drexel University Attributes Operations G Order 0 dateReoeived Dale G 7 Order 0 isnepaid Boolean o dateReoeivecl l Date 0 z o nunber string IsR epald Boolean o nunber String 0 price 1 Money 0 plice Money 9 dispatch e dispatch 9 close 9 close alanceOn dte Date 3 Drexel University Drexel University Generalization J classes 39 El Thechildrencla the parent class El Indicated by a hollow arrow Multiplicity a lsh epald 1 Bodean 0mm r n Multbtlclty o isR39epaid l Eudean o nun ber sum 9 dispakzho vdd 3 Remove From Diagram Delete From Model sses inheritthe attributes and operations of G Drexel U n iversity Association Indicated by a solid arrow line from the source class to the taraet class Can be bi directional represented by lines witho rrow heads Mm y has a mm m Don t usually put the association down as an attribute in the class n o imam Badun Drexel University Candidate classes Noun extraction Company XYZ has two types of customers corporate customers and personal customers All customers can place orders Every order is placed by a customer Evaluating a ClassClass Diagram 1 Intentionrevealing naming Does the name of the object convey its abstractions Does the abstraction have a natural meaning and use in the domain 2 Single Responsibility Do the name main responsibility statement data and functions align q From Requirement to 00 Design I Identify from SRS Find analysis classes from use cases Create t 1 from use cases Refine CRC cards into Analyze and model the behaviors using See ATM Example I UML sequence diagrams I UML state diagrams I UML collaboration diagrams El Design the architecture using UML component diagrams Create UML deployment diagrams El Detailed Design EIEIEIEI El Drexel University UML Sequence Diagrams Drexel University UML Sequence Diagrams Used during requirements anal sis ll Torefine use case descriptions 1 Tofind additional objects 3 participating objectsquot Used during system design to refine subsystem interfaces f Tare represented by columns firstcolumn is actorthat initiatesuse case 39 are represented by arrows of an operation are represented by narrow rectangles No significance to the horizontal orderings of the objects Remm values are optionallyindicated using a dashed anow with a label indicating the return value Suggestion not to indicate the return values when itis obvious what is being returned Drexel University 1O Scenario A player rolls the dice and gets a 6 The player moves 6 cells The player lands on a cell that is an unowned property The player s turn is over Not all nouns become objects such as turn Uta isonneuwuperyrrzisei Drexel University I I I If the player lands on a cell that IS an uni C d t I L ownedproperty the player s turn I5 over 0 n I I O n a If the player lands on a cell that IS owned the player must pay rent to the owner of the property Then the player s turn I5 over m Dice E m Mimi niii w EiCEValLEm mew cllcm istvnedFmperty ise i mtdl mpenyt itemyr r Fay ne Drexel University UML State Diagram Drexel University State Diagram 0A state diagram also called state machine diagram depict the various states that an object may be in and the transitions between those states oAppropriate to be developed for complex objects k2 turned candlein la ensate sateciased V l l kevmvned candle am lvelease killer vabbn Drexel University States States are represented by the values of the attributes or data members of an object Terminal state he med candle am lrelease hller rahhn state itial tran5ition Drexel University Transitions oTranSItions are the result of the Invocation of a method that causes an importantchange in state oEach transition has a label that comes in three parts All the parts are optional 7 nature guardac candle rmove oor c osedreveal lock oThe triggersignature is usually a single event that triggers a potential change of state oMissing triggersignature rare you take the transition immediately oThe guard if present is a Boolean condition that must be true for the transition to be ta en oMissing guard always take the transition oThe activity is some behavior that s executed quotduring the transition oMissing activity don39t do anything during the transition Drexel University kevmrned candle lni lapen sale to malawnmowerrealm 39 9 ua rd i chimed We am release no rabbi oolean trigger signature condition that event that causes a must be true potential changeof for transition state to happen From UML Distilled pp 107108 A lock in a haunted house keep valuables in a safe that39s hard to find To reveal the lock to the sate Ihave to remove a strategic candle trorn lte holder but this Will reveal the lock only While the door is closed In the Walt state it the candle is removed the lock 1 can lnsert rnv v to open the safe For extra satet I make sure that I can open the safe onl ltI replace the candle first Ita thletneqlects this precaution I39ll unleash a killer rabbit to hirn Drexel University Rules for State Diagrams There is initial state can be multiple final states Every state can be reached from the initial state From each state there must be a path to a final state Every transition between states must be labeled with an event that will cause that transition in When an event occurs you can take only one transition If you have multiple transitions with the same event the guards must be mutually exclusive ii Transitions that are not shown are mil OR show transitions that cause errors U U U U Drexel University From Requirement to 00 Design 7 39tr Cr V Re ne CRO card We A t Anatyze and modet the benavwors usth I UML sequence diagrams I UML state diagrams I UML colaborarion diagrams Destgn the arcnttecture usan UML oomponenrdiagrams Create UML deploymenidlagiams El Detatted Destgn Donna on Drexet Unwemcy UML Component Diagram Drexet Unwersttv Model a component Drexet Unwemcy Model a component s interfaces OrderEn Y momponem a AmounzFaynms 0 rder Reqwed Interfaces Wovtded Interface Drexet Unwersttv Model a component s relationship Cuaom erLookup tug 3 CLstDmethiokup Repositoly Drexel University From Requirement to 00 Design El EIEIEIEI El Identify a from SRS Find analysrs classes from use cases Create 539 i from use cases Refine CRC cards into L quot 39 Analyze and model the behaviors using I UML sequence diagrams I UML state diagrams I UlliL collaboration diagrams Design the architecture using UML component diagrams Create UML deploymentdiagrams Detailed Design Drexel University Model Software Architecture Drexel University Deployment Diagram Drexel University 14 From Requirement to 00 Design 1 Identify from SRS 1 Find analyse classes from use cases 1 Create m use cases i Refine CRC cards into 1quot r n Analyze and model the behaviors using I UML sequence diagrams I UML state diagrams I UML colabora a39on diagrams Design the architecture using UML componentdiagrams Create UML deploymentdiagrams a Detailed Design See ATM Example Eli Drexel University