1. UML and Systems Analysis MIS3502: Application Integration and Evaluation David Schuff David.Schuff@temple.edu

2. Review: What is Systems Analysis and Design? Systems Analysis Analysis of complex, large-scale systems and the interactions within those systems http://en.wikipedia.org/wiki/Systems_analysis Systems Design The process of defining the hardware and software architectures, components, models, interfaces, and data for a computer system to satisfy specified requirements http://en.wikipedia.org/wiki/Systems_design Notice that they are not the same!

3. Basically… Systems Analysis is the process of modeling the problem Requirements-oriented What should we do? Systems Design is the process of modeling a solution Functionality-oriented How should we do it?

4. Why model? Creating a blueprint for an application Before you start coding The idea is to minimize having to go back and make changes later

5. Why consider SAD in a programming course? The business analysts The development team AnalysisDesignDevelopment

6. What this means A developer must be able to turn the design into code But a good analyst should be able to understand all parts of system development Conduct an analysis Develop a design Implement the design (coding)

7. Example: Bjork’s ATM example An Example of Object Oriented Design, An ATM Simulation, Russell Bjork http://www.math- cs.gordon.edu/local/courses/cs211/ATMExample/

8. What we’ll look at… Use case diagrams Use case descriptions Activity diagrams :Controller:Customer:Order Interaction diagrams Analysis ModelsDesign Models Class name Attributes Operations Customer name findName() Design class diagrams All diagrams adapted from “Systems Analysis and Design in a Changing World”, 3rd Edition Satzinger, Jackson, Burd, Thompson Publishing, 2004.

9. Problem Statement What is the application supposed to accomplish? Use words, not code Be as descriptive as possible Potential sources of information Forms, reports Engineering drawings Real world object specifications Interviews

10. Problem statement for ATM application Services one customer at a time Must be able to handle 10 customers an hour Customer inserts ATM card and enters PIN to begin Transactions Cash withdrawals --- in $20 increments Deposits Transfers Balance inquiries Immediate transaction validation with the bank Standard error procedures Pin error, rejection due to inadequate balance Reports

11. Use Case Diagram Use case: sequence of events that represents an interaction between the user and the system Cash Withdrawal Deposit Transfer Invalid PIN Session Partial list of use cases from Bjork example Customer (actor) Bank (actor)

12. Use Case Descriptions For each use case, include The services the system provides to the user The sequence of events The desired outcome Users of systems (called actors) can be people organizations other systems

13. Use Case Description: Deposit transaction (ATM) A deposit transaction is started from within a session when the customer chooses deposit from the menu of possible transaction types. The customer chooses a type of account to deposit to (e.g. checking) from a menu of possible accounts, and then chooses a dollar amount by typing it on the keyboard. The system sends the customer's card number, PIN, chosen account and amount to the bank, which either approves or disapproves the transaction. If the transaction is approved, the machine accepts an envelope from the customer containing cash and/or checks and then issues a receipt. (If the customer does not insert the envelope within a specified period of time, this operation times out and the deposit transaction is aborted.) If the transaction is disapproved due to an incorrect PIN, the Incorrect PIN extension is executed. All other disapprovals are reported to the session, which initiates the Failed Transaction Extension. The bank is notified whether or not an approved transaction was completed in its entirety by the machine; if it is completed then the bank completes crediting the customer's account for the amount - contingent on manual verification of the deposit envelope contents by an operator later.

14. Activity diagram Show which activities occur during a use case This is for the deposit use case The customer initiates the transaction CustomerATM Choose deposit Ask which type of account Choose account type Send customer information to bank Bank Incorrect PIN? Credit customer account Transaction completed Incorrect PIN exception Transaction failed Approve transaction yes no yes no Ask deposit amount Choose deposit amount

15. Design class diagrams Shows the attributes and methods of each class Get the object names and attributes from the noun-phrase analysis What is the object? Get the methods from the activity diagram What should it do? Class DepositTransaction toAccount Amount DepositTransaction(session, atm, bank) getTransactionSpecificsFromCustomer() sendToBank() finishApprovedTransaction()

16. Working from the design class diagram The DepositTransaction class will have Two attributes Four methods We can tell from this what methods the class will have but not what they do Refer to the use cases, activity diagrams, and interaction diagrams for detail Class DepositTransaction toAccount Amount DepositTransaction(session, atm, bank) getTransactionSpecificsFromCustomer() sendToBank() finishApprovedTransaction()

17. Interaction Diagrams Show how the objects in the application “use” each other Which methods are called What data is returned

18. ATM application: Deposit Use Case :Session:Bank DepositTransaction (session, atm, bank) sendToBank() (approval) finishApprovedTransaction() (confirmation) checkIfCashAvailable(amount) (confirmation) initiateDeposit(account, amount) (confirmation) :DepositTransaction (self) getTransactionSpecificsFromCustomer() Session (session, atm, bank) :ATM Customer

19. Fitting everything together Use case diagram List of all use cases in the application Use case diagram List of all use cases in the application Use case descriptions Textual description of what happens in each use case Use case descriptions Textual description of what happens in each use case Activity diagram Picture of the activities described in each use case Activity diagram Picture of the activities described in each use case Design class diagrams List of all methods and attributes in each object Design class diagrams List of all methods and attributes in each object Interaction diagram Diagram of how the objects work together for each use case Interaction diagram Diagram of how the objects work together for each use case Scenarios Objects

20. Integration and UML: Web Services We’ll be working with this application later in the course It uses the MSN Live Search web service to search the web Microsoft’s web service is a distributed object

21. Partial interaction diagram for “Search Google” use case :MSNSearchService MSNSearchService() :Form Customer Search(SearchResponse) (search results) :Label Text property* * Because of C#’s convention that uses properties like methods

22. Things to think about What if you have to code something not accounted for in the design diagrams? Does the diagram have to match the code exactly? What does it mean when… …additional detail is required? …specified methods go unused? …different sequencing is required?