For this assignment, please turn in a Word document containing a table with six columns. List the following twelve figure numbers and their corresponding model types, down the left side. Then on the right side, decide what responsibility the Systems Analyst should have for each model. Does the Analyst gather, analyze, and record the information?
If so, write "Author" in the Analyst column. If not, write "Approve" or "Review" or "Utilize." Also show the responsibilities for Management (who provide funding, guidance, and approval) and the Software Engineers (who design, code, test, and deploy the system).
There are often more than one way to assign the responsibilities, and the answers are not in the textbook. So you will have to do some analysis to make the call. If you were in charge, who would you assign to construct each model? Please explain your reasoning in the sixth column as you make these assignments of responsibility.
Figure 1-8 is an example of a tough call. The way I filled it in for you is the norm at an internet startup. But in Microsoft Information Technology, Management (or the Project Manager) authors what we are calling the Vision Document, and the Systems Analyst receives it as a guide that sets the scope within which all the analytical
|
|
Responsibilities
|
|
|
Figure
|
Model Type
|
Management.
|
Analyst.
|
Software Engineers
|
Why?
|
|
1-8
|
Vision Document
|
Approve
|
Author
|
Utilize
|
Vision should come from the top of the organization and this allows for leaders to be champions of change
|
|
1-11
|
Use Case List
|
|
|
|
|
|
1-12
|
Domain Class List
|
|
|
|
|
|
1-13
|
Domain Class Diagram
|
|
|
|
|
|
1-14
|
Use Case Diagram
|
|
|
|
|
|
1-15
|
Activity Diagram
|
|
|
|
|
|
1-16
|
User Interface Sketch
|
|
|
|
|
|
1-17
|
Database Design
|
|
|
|
|
|
1-18
|
Software Components Diagram
|
|
|
|
|
|
1-19
|
Design Class Diagram
|
|
|
|
|
|
1-20
|
Software Architecture
|
|
|
|
|
|
1-21
|
Code
|
|
|
|
|
details are to be gathered.