Homework #1

OO Model Integration

Due Weds, Jan 17, 2001 30 points

Please make your assignment paper-based and hand in exactly at 10:00am (yes, in the middle of class)! Homework submitted prior to this or after 10:05am will not be accepted.

For the questions below refer directly to your 577a project. This is an individual assignment and you may not collaborate with other students. You may use some of the same material from your project as your 577a teammates, however you must submit work that is significantly different than theirs.

If you didn’t take the 577a course before, you can use any of the projects done in previous semester. You can access to the documents of these projects in the following address: http://sunset.usc.edu/classes/cs577a_2000/index.html#Project Deliverables. If you couldn’t pick one, then use Project 22 for your homework.

1) [20 points] Provide a complete tracing from Domain Description through Implementation for a particular aspect of your system (if your system has no implementation yet then you may speculate on what it will be so long as it follows the Design models). Do this by creating a “trace map” diagram indicating what model elements trace to one another and the direction of the tracings (see example below). You must provide rationale and explicit references for each step. Your goal is to show how a particular concept in the organization domain is eventually realized as a software abstraction through MBASE model integration. Start by choosing an activity from the current organization activity model (OCD 3.3) then explain how this activity is compatible with the organization background (OCD 3.1). Next explain what entities are involved in the activity. Now explain which system capabilities (OCD 4.3) are involved in representing the activity within the system. Indicate which components (from SSAD 2.1) stem from the system capabilities and explain how they represent at least one of the entities you found earlier that are involved in the activity you chose. Keep following this line of reasoning and diagram (use any diagramming tool you wish or by hand) the connections. Your map and rationale must include all “strong” integrations. That is you should include model elements that are directly evolved or cover other elements even if they are not suggested by the MBASE guidelines (e.g. Win Conditions, Prototype elements, L.O.S. Goals, etc.). Your map must provide at least one “connected” directed path from the domain activity to implementation. It must also at least (you may have more than these) have paths from the domain activity to element from the following models:

a. OCD 3.1 Organization Background

b. OCD 3.3 Current Activity Model

c. OCD 3.5 Current Entity Model

d. OCD 4.1 Statement of Purpose

e. OCD 4.3 Capabilities

f. SSRD 3.1 System Definition

g. SSRD 3.2 System Requirements

h. SSAD 2.1 Component Model

i. SSAD 2.2 Behavior Model

j. SSAD 3.2 Object Model

k. SSAD 3.3 Operations Model

l. Implementation Data structures (Java Classes, scripts, DB tables, web pages, COTS packages, etc.)

m. Implementation functions (methods, function calls, subroutines, SQL, HTML, JavaScript, COTS functions, etc.)

Note: you may find that your project has inadequate or incorrect tracings. In such cases identify or correct the tracings as needed

2) [5 points] Consider the trace map from above in reverse. Start with an implementation element (such as a function call) and trace it backwards to the domain description. Assume that no tracings currently exist.

a. Explain in detail why this would be easier, as easy, or more difficult to do than tracing forward as in question (1) above.

b. Is reverse tracing equivalent to forward tracing? Explain why it is or is not.

Partial example of a trace map: