This assignment is a task leading to additional useful data that can be applied to the final report and presentation, AND is a useful contribution to the expansion of CSE's MBASE knowledge base. It is to look back to CS577a and CS577b and do the identification based data gathering based on the course, your project and all guidelines and presentations. In addition, it is to apply the data gathering to what is going on at your summer employer. Please note that there may be various sets of responses based on the project you are working on, what the company "normally" does, and what may be going on in other projects that you hear about.

The second part is due to Monday July 31, 2000.

Below are detailed instructions for second assignment on what is desired and how to present the results:

Second assignment is a continuation of the first assignment. You can use the same table in the first assignment or use the new tables, which are separated into the MBASE models. You need to fill the second part of the table which wants you to identify in which MBASE life-cycle the artifacts you were identified are. If they are different than the given ones in the table, try to identify the phase that you think the artifact is belong to. Is that phase a Created (C), Expanded (E), Updated (U) or Referred to (R) type of the given phases. Maybe, they have different names or used in different phases. In addition, provide brief description about your identification of the phases for the artifacts.
 

Note:You can add new artifacts that you have identified after the first assignment with a brief description (what they are, and why they are used, etc.)
 

Add the following information into your first assignment while doing your second assignment:
 

1.4 Where in the life MBASE life-cycle is each "Artifact Name or Type"

            1.4.1    Created (C): generated for the first time. If this is a significant change to another Artifact Type, please indicate which one. For example, a data flow     diagram might be the basis for an entity relationship model.

            1.4.2    Expanded (E): an expansion implies more detail (NOT a transformation or change in representation, viewpoint, etc.). For example, a High-level Design might be expanded to a Detailed Design.

            1.4.3    Updated (U): changes are made to details, but not to structure or level of details (e.g. a draft might be updated to final document)

            1.4.4    Referred to (R): a team member other than the creator uses it for information

• For your project and the other for the company (or organization) you work for
• Additional responses for other projects that you become familiar with (these might be done as exceptions to the company/organization response).

        2    Alternative Results Representations:

                2.1    Tabular listing by Artifact: (OK, but not as useful)

 

Artifact Name or  Artifact Type	Related MBASE Model	I V O P	MBASE Phase (CEUR)
			Inception	Elaboration	Construction	Transition


 
 
      2.2    Multiple Tables by MBASE model (Preferred)