DOC PREVIEW
UT Dallas CS 6359 - Test_1 Review

This preview shows page 1-2-3-4-5 out of 16 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Slide 1What did we learn?UPAgile UPAgile UPAgile UPUse CasesUse CasesUse CasesSlide 10Slide 11Domain ModelSlide 13SSDSlide 15Operations ContractObject-Oriented Analysis and DesignRe v i e w f o r e x a m # 11What did we learn?The concept of UP – how it is different from Waterfall, how it worksHow requirements are capturedThe Use-Case Model: How it is created, how it is modified, what it isThe basics of Domain Modeling – how to create a domain model, how to read a domain model UML Diagram notation – static and dynamicHow to create SSDs and Operations Contracts2UPWhat are the four phases of Agile UP?Inception, Elaboration, Construction, TransitionWhat’s the difference between Elaboration and Construction?Elaboration concentrates more on requirements and use case development, Construction concentrates more on software development. 10% of code is usually done by the end of Elaboration, but 90% of requirements are done. By the end of Construction, most of the code is finished. What is the difference between a use case and a Domain Model Diagram?The use case is text, and describes a particular scenario for the system under design. The Domain Model Diagram is a diagram, indicating key conceptual classes and associations in the system.3Agile UP What is FURPS+?It is a classification system for requirements. The acronym stands for Functionality, Usability, Reliability, Performance, and Supportability, plus other requirements. When are requirements developed in Agile UP?They are primarily developed in the Inception and Elaboration phases, but they are never frozen and can be further enhanced throughout the lifetime of the project.4Agile UPName two activities that usually happen during the Inception PhaseThe Vision artifact is created and high risk use cases are identified and detailed.Name two activities that usually do not happen during InceptionUsually the Domain Model and the Design Model are not started in the Inception Phase, they are started in the Elaboration Phase.5Agile UPName four artifacts that can be used to capture requirements in Agile UPThe Use-Case Model, Supplementary Specification, Glossary, and Business Rules.Consider the following requirements: The system shall run on Unix, the system shall comply with SEC regulations for security. Where should these requirements be captured?The first is a non-functional requirement, usually captured in the Supplementary Specification. The second can be considered a business rule, but may also lead to requirements that may be captured elsewhere (Use-Case Model, for example).6Use CasesWhat is the difference between a Primary Actor and a Supporting Actor?The Primary is the actor that has his/her needs fulfilled by the system; the supporting provides a service to the system.What is the difference between the brief use case and fully dressed use case formats?The first is a short paragraph of text that describes a particular scenario; the second is a detailed table that includes the Main Success Scenario in detailed steps, and other information (such as extensions)7Use CasesCreate a brief use case description for checking your e-mail online successfullyThe User starts with a Login Page. The User enters their username and password. The System authenticates the username and password, and displays the Main Page GUI. This page displays an Inbox, showing all messages that have not been deleted, and also a folder list that shows collections of e-mails that have been deleted, sent, or saved. The User opens an e-mail in the Inbox by double-clicking on it.8Use CasesDescribe at least 3 extensions to the previous use caseThe User enters the wrong username or password and the System can not authenticate the User; the User deletes an e-mail from the Inbox; a new e-mail arrives while the User is viewing the Inbox.910•What class owns an Item?•Collection•How many Bundles make up and Item?•One or more•Name two compositions in this model•Bundles are composed of Bitstreams, Collections are composed of Items•What does the “Sub-community” line mean?•The Community may be composed of Sub-communities, which are themselves Communities11•Identify 2 operations associated with a Window object•close(), open()•Identify two operations associated with a Couch object•getType(), numSeats()•What is the only interface relationship in this model•The Room object implements the Drawable interface•Find one error in the diagram•The arrows from the Furniture and Structure objects into the Room object should be aggregation, not sub-classesDomain ModelConsider the following brief use case: “Our Bank services many Customers. Each Customer has an Account, and there are three type of Accounts: Savings, Checking, and Flexible Savings. For each of these types of accounts, there is a balance, account number, and interest rate. Each Customer is identified by name, and we have contact information which includes phone numbers and an address. Each Account has a Statement, which includes the current date and information such as recent activity and balances.” Describe the conceptual classes in this domainThe Bank, Customer, Account, StatementNow draw a domain model …1213BankAccountbalance: MoneyinterestRate: InterestRateaccountNumberChecking SavingsFlexible SavingsCustomerfirstName: StringlastName: Stringservices11…n11…nhas11…nContactphoneHome: PhoneNumberphoneMobile: PhoneNumberAddressstreet: StringhouseNumber: Stringcity: Stringstate: StringzipCode: Stringhas11 1 1StatementcurrentDate: DaterecentActivity: Stringhas11SSDExpand on the use case: “The Customer will request a new account. The Teller will ask the system to create a new account. The Teller will ask for the Customer’s contact information, and enter it into the system. The system will automatically assign an Account Number. The Customer will provide funds for the account, and the Teller will use this to indicate the initial amount in the account.” Draw an SSD for this use case1415:SystemTellercreateNewAccountenterCustomerContactInfoassignAccountNumberenterInitialAccountAmountOperations ContractCreate an Operations Contract for the enterCustomerContactInfo operation. Contract ECI-1: Enter Customer Information Operation: enterCustomerContactInfo(firstName, lastName, homePhone, mobilePhone, addressCross Reference: Use Cases: Create New AccountPreconditions: There is an account creation underwayPostconditions:-A Customer instance cust was created -cust.firstName, lastName


View Full Document

UT Dallas CS 6359 - Test_1 Review

Documents in this Course
Lecture2

Lecture2

63 pages

Lecture3

Lecture3

49 pages

Lecture4

Lecture4

48 pages

Lecture5

Lecture5

47 pages

Lecture6

Lecture6

45 pages

Lecture7

Lecture7

63 pages

Lecture8

Lecture8

77 pages

Lecture9

Lecture9

48 pages

Lecture10

Lecture10

84 pages

Lecture11

Lecture11

45 pages

Lecture12

Lecture12

134 pages

Lecture13

Lecture13

62 pages

Lecture14

Lecture14

76 pages

Project

Project

2 pages

Chapter_1

Chapter_1

25 pages

Load more
Download Test_1 Review
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Test_1 Review and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Test_1 Review 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?