Tài liệu Module 2: Designing and Modeling docx

Module 2: Designing and Modeling Contents Overview Introduction to Analysis and Design Creating a Conceptual Design Lab 2.1: Reviewing the Requirements Document 17 Creating a Logical Design 19 Creating a Physical Design 38 Lab 2.2: Using the Visual Modeler 50 Best Practices 55 Review 57 Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  2000 Microsoft Corporation All rights reserved Microsoft, BackOffice, MS-DOS, Windows, Windows NT, PowerPoint, Visual Basic, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Other product and company names mentioned herein may be the trademarks of their respective owners Module 2: Designing and Modeling Instructor Notes Presentation: 120 Minutes Lab: 60 Minutes This module covers the major phases and deliverables in the Microsoft® Solutions Framework (MSF) Application model The conceptual, logical, and physical design phases are then discussed in relation to the Unified Modeling Language (UML) Students also use Microsoft Visual Modeler to model the Purchase Ordering solution After completing this module, students will be able to: ! List and describe the three design phases defined in the MSF Application model ! Employ UML use cases, scenarios, and use case diagrams in the conceptual design phase ! Use UML class diagrams and sequence diagrams in the logical design phase ! Use Visual Modeler to create class diagrams ! Use component diagrams and deployment diagrams in the physical design phase to generate code from Visual Modeler In the labs, students will review the Requirements Document for the Purchase Order Online application and then test their understanding of the proposed solution In the second part of the lab, students will use Visual Modeler to model aspects of the system and generate code Materials and Preparation This section provides you with the required materials and preparation tasks that are needed to teach this module Required Materials To teach this module, you need the following materials: ! Microsoft PowerPoint® file 1907A_02.ppt ! Module 2: Designing and Modeling ! Lab 2.1: Reviewing the Lab Solution ! Lab 2.2: Using the Visual Modeler Preparation Tasks To prepare for this module, you should: ! Read all of the materials for this module ! Complete the labs ! Read the instructor notes and the margin notes for the module ! Practice the demonstrations i ii Module 2: Designing and Modeling Demonstrations This module contains the following demonstrations Use the following instructions as the basis of your presentation to the students Although the demonstrations are indicated by a slide, you may wish to present them incrementally as you explain the concepts In this case, use the slide to summarize what you have demonstrated Using Visual Modeler ! Create a Visual Modeler model Start Microsoft Visual Modeler from the Microsoft Visual Studio® 6.0 Enterprise Tools program group Point out the different model views available in the browser window (Logical View, Component View, and Deployment View) Return to the Logical View and display the Three-Tiered Service Model ! Add classes to the model In this procedure, you will add two classes to the model Explain to students that this demonstration is unrelated to the lab scenario On the Tools menu, point at Create and choose Class from the submenu Click in the User Services section of the diagram to create the class Change the class name from New Class to Customer Click the Class button on the toolbar Click in the Business Services section of the diagram to create a second class Name the second class Account Right-click the Account class and choose Open Specification In the Documentation tab, type This class represents a customer’s account then click OK ! Add Properties and Methods to the Account class Right-click the Account class and choose New Property Name the new property AccountNo and click in free space to deselect the class (Pressing Return adds another property.) Right-click the Account class and choose New Method Name the new method Credit and click in free space to deselect the class Right-click the Account class and choose Open Specification Show the Properties and Methods tabs On the Methods tab, right-click in the list of methods and choose Insert Name the new method Debit Click in the Return Type column of the Debit method and point out that you need to click the column again to display the drop-down list of data types Choose Boolean from the list and explain that custom data types can be added by simply typing them Module 2: Designing and Modeling iii Double-click the Debit method in the list of methods to display its specification Note that the return class can also be set from this dialog box 10 On the Arguments tab, right-click in the empty list of arguments and choose Insert 11 Name the new argument curAmount 12 Click in the Type column for the curAmount argument and then click the column again to display the data type drop-down list Choose Currency from the list 13 Click OK to confirm the changes to the Debit method 14 On the Properties tab, double-click the AccountNo property Explain that the property is private by default 15 Change the Export Control setting to public 16 Point out that you can change the property’s data type here Change the Type to Long and click OK 17 Click OK again to close the Specification dialog box for the Account class ! Add class dependencies On the Tools menu, point at Create and choose Dependency from the submenu Click on the Customer class and drag to the Account class to create the dependency Save the model as bank.mdl in the \Democode\Mod02\CreateModel folder Generating Code with Visual Modeler ! Prepare Visual Basic® for code generation Start Visual Basic and create a new Standard EXE project On the Add-Ins menu, click Add-In Manager In the list of available add-ins, locate the Visual Modeler Add-In and the Visual Modeler Menus Add-In Select each of these add-ins and check the Load on Startup check box Click OK to close the Add-In Manager Close Visual Basic without saving the project ! Add a component to the model Open the bank.mdl model you saved in the last demonstration and expand the Component View folder in the browser window (If you did not complete the last demonstration, open bank.mdl from the \Democode\Mod02\GenerateCode folder.) Double click Main to view the components in the model (currently, there are none) On the Tools menu, point at Create and choose Component from the submenu iv Module 2: Designing and Modeling Click anywhere in the model window to create the new component Rename the component Bank ! Configure the component Right-click the Bank component and choose Open Specification Change the Stereotype to DLL and the Language to Visual Basic, then click Apply and point out that a Visual Basic tab has been added to the dialog box Click the Realizes tab and note that all of the classes in the model are listed Explain that this component will only contain the Account class Right-click the Account class in the list of classes and choose Assign Point out the red tick and the change of language for the Account class Clear the Show All Classes check box so that only classes assigned to this component are displayed Click the Visual Basic tab and click the Edit Set button Choose Class from the Type drop-down list and point out the default class settings In the list of settings, click Creatable and then click again to reveal the drop-down list of values Choose MultiUse from the list In the list of settings, click CollectionClass and then click again to reveal the value text box There are no collections associated with this class, so clear the text box 10 Click OK to close the Visual Basic settings dialog box and then click OK again to close the component specification dialog box ! Generate Visual Basic code Right-click the Bank component and choose Generate Code On the Welcome screen, click Next On the Select Classes screen, point out that more classes can be assigned to the component at this stage and then click Next On the Preview Classes screen, select the Account class and click Preview a On the Class Options screen, point out that the options you configured have been used Then click Next b On the Property Options screen, point out the code preview at the bottom of the screen Then click Next c On the Role Options screen, click Next d On the Method Options screen, select each method and point out the code preview at the bottom of the screen Then click Finish to return to the Code Generation Wizard On the Preview Classes screen, click Next On the General Options screen, ensure the Save model and project before generating code check box is checked Clear all of the check boxes in the Code Generation Options section and click Next On the Finish screen, click Finish Code generation will begin Module 2: Designing and Modeling v When the Delete Classes screen is displayed, click Form1 (Note that you not actually need to click the Delete button.) Then click OK Read the summary screen and then click Close to close it 10 Switch to the Visual Basic project that has been generated 11 Point out the code that has been generated and note that the model is listed as a Related Document in the Project Explorer window 12 Save the project in the folder containing bank.mdl Reverse Engineering a Component with Visual Modeler ! Modify the code created by Visual Modeler Explain that some of the default settings created by Visual Modeler should be changed if the project is to be used in a distributed application Open the Bank project you generated in the last demonstration (If you did not complete the last demonstration, open Bank.vbp from the \Democode\Mod02\ReverseEngineer folder.) In the Bank project, click Bank Properties on the Project menu On the General tab, make the following changes: a Change the Startup Object to (none) b Change the Threading Model to Apartment Threading Click OK ! Add a new method Open the code window for the Account class, and on the Tools menu, click Add Procedure In the Add Procedure dialog box, add a new public function named GetBalance Point out the new procedure signature added to the class module Add the code As Currency to the end of the function heading to determine the return type ! Reverse Engineer the model On the Add-Ins menu, point at Visual Modeler and select Reverse Engineering Wizard from the submenu On the Welcome screen, click Next On the Selection of Project Items screen, ensure only Class Modules is selected and then click Next Explain that the Assignment of Project Items screen is used to assign classes added in Visual Basic to logical tiers in the model We have not added any classes so simply click Next Review the Finish screen and then click Finish Reverse Engineering will begin When the summary screen is displayed, click Close to close it vi Module 2: Designing and Modeling Switch to Visual Modeler and examine the Account class in the Logical view window Point out that the GetBalance method has been added to the model Save the project and model and then Close Visual Basic and Visual Modeler Module Strategy Use the following strategy to present this module: ! Introduction to Analysis and Design Tell students that a critical part of developing enterprise solutions is to analyze the business problem that needs to be addressed When you properly analyze the business problem and create an appropriate design, you can deliver a solution that is scalable, robust, and meets user requirements You should also adopt a design strategy that is sufficiently flexible to incorporate changes throughout the software development process ! Creating a Conceptual Design Discuss the steps that are required to create a conceptual design The system requirements must be captured from the perspective of the end user and the business services The UML defines a set of best practices for capturing and representing the system requirements UML converts the requirements into a set of use cases and associated scenarios The scenarios are defined as the output of the conceptual design under the MSF Application Model ! Creating a Logical Design Explain that the next step in the design process after capturing the user requirements is to build a logical model of the system The model consists of two views: a static view showing how the parts of the system relate to each other, and a dynamic view showing how the system parts interact with each other The UML provides a variety of diagrams in which this information can be captured These diagrams help to refine the high-level information gathered in the conceptual design phase into more detailed information on which you can base your implementation ! Creating a Physical Design The final design phase defined by the MSF Application Model is to create a physical design for the solution Explain that changes can be made to the logical design during this phase After all of the design phases are complete, the solution can be made into a component, packaged, and implemented ! Best Practices Summarize the best practices that have been covered in this module Module 2: Designing and Modeling # Overview Slide Objective To provide an overview of the module topics and objectives ! ! Lab 2.1: Reviewing the Requirements Document ! Creating a Logical Design ! Creating a Physical Design ! Lab 2.2: Using the Visual Modeler ! A critical part of developing enterprise solutions is to analyze the business problem that needs to be addressed When you properly analyze the business problem and create an appropriate design, you can deliver a scalable, robust solution that meets user requirements Creating a Conceptual Design ! Lead-in Introduction to Analysis and Design Best Practices and Review A critical part of developing enterprise solutions is to analyze the business problem that needs to be addressed When you analyze the business problem properly and create an appropriate design, you can deliver a solution that is scalable, robust, and meets user requirements You should also adopt a design strategy that is flexible enough to incorporate changes throughout the software development process In this module, you will learn how the Microsoft Solutions Framework (MSF) application model defines an iterative design approach to n-tier applications You will also learn how you can use the Unified Modeling Language (UML) in each of the design phases of the development project Finally, you will learn how to use Microsoft Visual Modeler to produce UML models and generate Microsoft Visual Basic code Objectives After completing this module, you will be able to: ! List and describe the three design phases defined in the MSF application model ! Employ UML use cases, scenarios, and use case diagrams in the conceptual design phase ! Use UML class diagrams and sequence diagrams in the logical design phase ! Use Visual Modeler to create class diagrams ! Use component diagrams and deployment diagrams in the physical design phase to generate code from Visual Modeler Module 2: Designing and Modeling # Introduction to Analysis and Design ! Importance of Analysis and Design ! The MSF Application Model One of the ongoing challenges for developers is to build solutions that deliver the functionality the end user wants Building good solutions involves analyzing business requirements and designing a suitable software system to meet those requirements Although the detailed steps in analysis and design vary depending on the process and tools used, there are some common themes found in all software development endeavors When choosing a software development process for building enterprise systems, it is important to ensure that the process will enable the development team to identify the user requirements, design and build an appropriate solution, and adapt to changes in the requirements throughout the life of the development project In this section, you will learn about the phases in the design process You will also learn how to use an iterative approach to design to help ensure that the finished product meets the user's requirements This section includes the following topics: ! Importance of Analysis and Design ! The MSF Application Model 44 Module 2: Designing and Modeling The following illustration shows the initial screen for the Code Generation Wizard By using the Code Generation Wizard, you can confirm the classes for which you want to generate code and review their methods and properties The wizard provides code for the selected classes and a project for the target environment as shown in the following illustration You can then use this skeleton code as the basis on which to implement your component classes Module 2: Designing and Modeling 45 Creating Deployment Diagrams The UML also defines deployment diagrams to help show the relationships between the nodes on which components and processes are deployed Visual Modeler also supports deployment diagrams The following illustration shows a deployment diagram as produced by Visual Modeler To create a deployment diagram in Visual Modeler, select Deployment View To add nodes to the diagram, point to Create on the Tools menu and select Node 46 Module 2: Designing and Modeling Demonstration: Generating Code with Visual Modeler Slide Objective To demonstrate how to generate code by using Visual Modeler Delivery Tip The step-by-step instructions for this demonstration are in the instructor notes for this module In this demonstration, you will see how to use Visual Modeler to create a component diagram and generate Visual Basic code Module 2: Designing and Modeling 47 Iterating the Design ! Iterative Development ! Round-Trip Engineering One of the problems with traditional application development is the assumption that each preceding phase is complete before the next one starts With this traditional model, there is considerable pressure to be right the first time in every phase of the design In the real world, this objective is impractical because there are unknowns in any project The MSF Application Model prescribes an iterative design process so you can address the issues of uncertainty and change Iterative Development In MSF, the development process proceeds as a series of feedback loops between the conceptual, logical, and physical design phases Issues found in the physical design phase may necessitate a change to the logical design, or even identify a flaw in the requirements and analysis model, causing a return to the conceptual design Round-Trip Engineering Visual Modeler helps to simplify the iterative design approach by providing round-trip engineering capabilities After you have built your components by using the skeleton code produced by Visual Modeler, you not want to cut and paste your code back into new skeletons created from a slightly altered design With round-trip engineering, you can move backward and forward between your model and code without having to rewrite the code that you have added To use round-trip engineering capabilities in a Visual Basic implementation, point to Visual Modeler on the Add-Ins menu, and select Reverse Engineering Wizard You can then select which Visual Modeler model you want to reverse engineer 48 Module 2: Designing and Modeling The following illustration shows a sample screen from the Reverse Engineering Wizard After the Reverse Engineering Wizard is finished, your model will be updated so that it is consistent with the Visual Basic implementation You can then change the model and update the Visual Basic code with the changes Module 2: Designing and Modeling Demonstration: Reverse Engineering a Component Slide Objective To demonstrate how to reverse engineer a component by using Visual Modeler Delivery Tip The step-by-step instructions for this demonstration are in the instructor notes for this module In this demonstration, you will see how to reverse engineer a Visual Basic project by using the Visual Modeler Reverse Engineering Wizard 49 50 Module 2: Designing and Modeling Lab 2.2: Using the Visual Modeler Slide Objective To introduce the lab Lead-in In this lab, you will add a class to a Visual Modeler diagram and then generate code for that class In this lab, you will use Microsoft Visual Modeler to model aspects of the system and generate code for the bus_Order class Visual Modeler is a modeling tool provided with Microsoft Visual Studio Enterprise Edition You will use it to examine and complete a model of the Purchase Order system Objectives After completing this lab, you will be able to: ! Use Visual Modeler to create a class diagram and generate code Prerequisites Before working on this lab, you should be familiar with the following: ! UML modeling Exercises The following exercise provides practice in working with the concepts and techniques covered in this module: ! Exercise 1: Modeling the Solution In this exercise, you will add the bus_Order class to the Visual Modeler diagram for the Purchase Order application You will also use Visual Modeler to generate Visual Basic code for the bus_Order class Estimated time to complete this lab: 30 minutes Module 2: Designing and Modeling 51 Exercise 1: Modeling the Solution To complete the exercises in this lab, you must have the required software For In this exercise, you will add the bus_Order class to the Visual Modeler diagram for the Purchase Order application You will also use Visual Modeler to generate Visual Basic code for the bus_Order class ! View the model of the system On the Start menu, point to Programs, Microsoft Visual Studio 6.0, Microsoft Visual Studio 6.0 Enterprise Tools, and then click Microsoft Visual Modeler Open the PurchaseOrder.mdl model located in the \Labs\Lab02 folder Note the classes already in the model Locate the db_Order class Note that it contains two public methods and one private function Right-click the db_Order class and select Open Specification Read the documentation for the class In the Class Specification for db_Order dialog box, click the Methods tab Note that the Insert method returns a Long value The Insert method will be used to add a new order to the database and return the Order Number assigned to the order Double-click the Insert method to view its specification Read the documentation for the method and click the Argument tab to view the method parameters Click Cancel to close the Method Specification and Class Specification dialog boxes 10 Expand the Component View folder and then double-click Main Note the components that are listed 11 Right-click the POData component and then click Open Specification Note the stereotype and language settings, read the documentation, and view the contents of the Realizes tab You can select the Show All Classes check box to list all classes in the model or clear it to show only the classes realized in this component 12 Close the Component Specification dialog box and return to the ThreeTiered Service Model view 52 Module 2: Designing and Modeling ! Add the bus_Order class to the model In this part of the exercise, you will add the bus_Order class to the model The bus_Order class is used to implement the business rules that are used when dealing with orders It has one public method (Raise) and four private functions (Authorize, Announce, Place, and GetTotal) 13 On the Tools menu, point to Create and then click Class 14 Click in blank space in the Business Services column to create the new class Change the name of the new class to bus_Order and then click in blank space to remove the drop-down menu 15 Right-click the bus_Order class, click New Method, and name the method Raise 16 Add methods named Authorize, Announce, Place, and GetTotal 17 Right-click the bus_Order class and click Open Specification 18 Click the Methods tab 19 Double-click the Raise method to show its specification 20 Change the Return Class to a type Long and ensure that Public is selected under Export Control 21 Click the Argument tab 22 Add the following arguments by right-clicking in the arguments ListBox and then clicking Insert: • rsOrderDetails (of type Object) • DeptOrder (of type Boolean) 23 Configure the remaining methods as follows (If a data type does not appear in the drop-down list, you can type it.) Method Return type Export control Arguments Authorize Boolean Private curAmnt (Currency) Private arItems (Variant) Announce strDept (String) Place Private rsItems (Recordset) strUserID (String) lngOrderNo (Long) GetTotal Currency Private rsItems (Recordset) ! Add dependencies Dependencies in a model are used to show which classes use the services of other classes For example, note the dependency between the OrderForm.asp class and the bus_Product class In this part of the exercise, you will add the dependencies that relate to the bus_Order class 24 On the Tools menu, point to Create and then click Dependency 25 Click the PlaceOrder.asp class and drag a line to the bus_Order class to show that the intranet application uses the services of bus_Order Module 2: Designing and Modeling 53 26 Add the following dependencies to the model This class Uses services from this class bus_Order db_CostCenter bus_Order db_Order bus_Order db_Error bus_Order db_Vendor bus_Order db_BudgetLimit bus_Order db_ADUsers 27 Save your model ! Add a component to the model Classes are assigned to components In this part of the exercise, you will create a new component and assign the bus_Order class to it You will configure the component as a Visual Basic DLL Expand the Component View folder and then double-click Main On the Tools menu, point to Create and then click Component Click in a blank area of the diagram to add the component and then rename it POBusiness Click in blank space to clear any selected components Right-click the POBusiness component and then click Open Specification Change Stereotype to DLL, change Language to Visual Basic, and then click Apply (Note that a Visual Basic tab is added to the dialog box.) Click the Realizes tab and note that all the classes in the model are shown Right-click the bus_Order class and then click Assign This assignment indicates that the POBusiness DLL will contain the bus_Order class Assign the bus_Product class to the POBusiness DLL in the same manner Clear the Show all classes check box Click the Visual Basic tab Notice that a default set of properties for the component has been used Click Edit Set to begin changing them 10 For the Module Specification properties, select and then click the ProjectFile property, set its value to POBusiness, and then click Apply 11 Use the combo box to change the property type to Class 12 Change the Creatable property to MultiUse and then click OK 13 Click OK on the Component Specification dialog box to close it 14 Save the model 54 Module 2: Designing and Modeling ! Prepare Visual Basic for code generation There are two Visual Modeler add-ins for Visual Basic that must be loaded before code is generated from a model In this part of the exercise, you will configure Visual Basic to load them at startup Minimize Microsoft Visual Modeler and start Microsoft Visual Basic When prompted, create a Standard EXE project On the Add-Ins menu, click Add-In Manager At the bottom of the list of add-ins, locate Visual Modeler Add-In and Visual Modeler Menus Add-In Set both add-ins to Load on Startup and then click OK Close Visual Basic without saving the project ! Generate code from the model In this part of the exercise, you will generate a Visual Basic project from the POBusiness component in the model Right-click the POBusiness component and then click Generate Code Read the first screen of the wizard and then click Next In the Select Classes screen, make sure the bus_Order and bus_Product classes are selected, and then click Next In the Preview Classes screen, select the bus_Order class and then click Preview In the Class Options screen, make sure that MultiUse is selected and then click Next In the Property Options and Role Options screens, click Next In the Method Options screen, review the methods and then click Finish In the Preview Classes screen, click Next In the General Options screen, clear all the selected check boxes and then click Next 10 Read the Finish screen and then click Finish 11 When prompted to locate the POBusiness.vbp project file, click No (This step will cause the wizard to create the project.) 12 When prompted to remove forms, select Form1 to be deleted and then click OK 13 When the wizard finishes, click Close, switch to Visual Basic, and review the project it has created 14 In Visual Basic, click Save project on the File menu Navigate to the \Labs\ folder and then click Create New Folder in the Save File As dialog box Name the new folder Business Components and open it Save the classes as bus_Order.cls and bus_Product.cls, and then save the project as POBusiness.vbp Close Visual Basic 15 Save the model and close Visual Modeler Module 2: Designing and Modeling 55 Best Practices ! Involve the end user throughout development ! Capture requirements in UML ! Build a static model of the system in Visual Studio Modeler ! Use dynamic modeling to improve the static model ! Adapt the model for real-world, nonfunctional requirements ! Create coherent components ! Use an iterative approach to design When designing and modeling enterprise applications, you should observe the following best practices: ! Involve the end user throughout development There is strong evidence that involving the end user throughout the development cycle can significantly improve the chance of a project's success The MSF Team Model builds an advocate for the end user into the development team ! Capture requirements in UML UML provides a powerful mechanism for capturing end-user requirements Discovering actors, use cases, and scenarios is the first step toward developing a coherent model of the intended system ! Build a static model of the system in Visual Modeler By using the information captured in the use cases, you can build a UML class model to represent the static structure of the application You can use the Microsoft Visual Modeler to create a UML class model Visual Modeler also maps the model to the three tiers of services defined under the MSF Application Model ! Use dynamic modeling to improve the static model You can turn the scenarios created to exercise the use cases into sequence and state diagrams that reflect the dynamic interactions in the system These diagrams in turn can greatly enhance the detail contained in the class diagram ! Adapt the model for real-world, nonfunctional requirements It is vital that the model be mapped correctly onto the underlying architecture In particular, the choice of implementation technologies and the physical distribution of the system must be taken into account when performing this mapping 56 Module 2: Designing and Modeling ! Create coherent components The business services of a Windows DNA solution are implemented as COM components In some cases, the efficiency of the system and the ability to maintain it depend on correctly choosing which classes should reside in which components ! Use an iterative approach to design As the design of the system is refined, iterate through the design phases to ensure that the user requirements are being met Using Visual Modeler for round-trip engineering allows for a smooth transition between the model and the code and back again This advantage can greatly increase the speed of development and improve the response time to end users Module 2: Designing and Modeling 57 Review Slide Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module Please take a few minutes to answer the questions in your workbook, and then we will discuss them as a class ! List and describe the three design phases defined in the MSF application model ! Employ UML use cases, scenarios, and use case diagrams in the conceptual design phase ! Use UML class diagrams and sequence diagrams in the logical design phase ! Use Visual Modeler to create class diagrams ! Use component diagrams and deployment diagrams in the physical design phase to generate code from Visual Modeler Which of the following descriptions best describe the MSF application model? a A hierarchical approach to designing three-tier solutions that consists of the conceptual, developmental, and physical design phases b An iterative approach to designing two-tier solutions that consists of the conceptual, logical, and physical design phases c An iterative approach to designing three-tier solutions that consists of the conceptual, logical, and physical design phases d An iterative approach to designing three-tier solutions that consists of the conceptual, physical, and reverse engineering design phases C is correct Explain the difference between a use case and a scenario Use cases describe a high-level, generalized interaction between an external entity (called an actor) and the system Scenarios expand on use cases by describing specific instances of the interactions possible within a use case 58 Module 2: Designing and Modeling You are modeling a payroll system and want to represent an Employee class Employees have a unique integer identifier called an EmployeeID, a department specified as a string, and a salary Employees normally start with a yearly salary of $20,000, and you want to show this compensation as a default What should you enter in the Attributes section of the Employee class? EmployeeID: Integer Department: String Salary: Currency = 20000 You want to model a business process involving a dynamic interaction between several classes, showing the lifetime and activity of each class as the business process proceeds Which UML diagram is best suited to this type of modeling? A Sequence Diagram Which of the following UML diagrams can be created in Visual Modeler? a Use Case diagram b Class diagram c Sequence diagram d Collaboration diagram e Component diagram f Deployment diagram B, E, and F are correct ... operations and attributes You will identify the class attributes and operations by applying scenarios and by using the dynamic modeling process 24 Module 2: Designing and Modeling Modeling Static... Importance of Analysis and Design ! The MSF Application Model Module 2: Designing and Modeling Importance of Analysis and Design ! Analyze the Business Problem ! Understand the Business Logic... problem 4 Module 2: Designing and Modeling Understand the Business Logic As well as gaining a conceptual understanding of how users need to interact with the system, developers need to understand the