For this assignment, please turn in a Word document containing a table with six
ID: 3662555 • Letter: F
Question
For this assignment, please turn in a Word document containing a table with six columns. List the following twelve figure numbers (the numbers are taken from the figures you find in the pages of chapter 1 of our eTextbook) 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 details are to be gathered.
Responsibilities Figure Model Type Management . Analyst . Software Engineers Why?
1-8 Vision Document Approve Author Utilize Management hires creative talent to propose the scope.
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
Explanation / Answer
Figure
Model Type
Analyst
Responsibility of Management
Software Engineers
Why?(Reason)
Use Case List
Iterative/Agile
Records the information.
I.e. Author
Setup meeting with the clients/ end users
He writes the Use case diagrams. Designs system
This is the initial information for any system to understand the new system
Domain Class List
Iterative/Agile
Records the information and use it for the database attributes.
I.e. Author
Setup meeting with the clients/ end users
Design system
Attributes are pieces of information that helps define and describes details about domain classes.
Domain Class Diagram
RAD
I.e. Author
Approval
Divides the system into subsystem.
Domain Classes are very powerful and frequently used for undersetting the total system
Use Case Diagram
-
Completes Initial analysis. Reviews
Monitor the system and approval
Creates use case diagrams
It is a graphical portability and user involved in the subsystem
Activity Diagram
-
Reviews
Monitor the system and approval
He will create initial screens using activity diagrams. And also adds flow of the screens.
It shows the basic interaction between user and system.
User Interface Sketch
Iterative/Agile
Reviews
Reviews
Design the initial page layout
It shows the basic subsystems of the application schema.
Database Design
Iterative/Agile
Reviews and approves
Reviews
Design
Designs database schema.
Software Components Diagram
-
Reviews and approves
Reviews
Design
It shows overall structure of the new system.
Design Class Diagram
-
Reviews and approves
Reviews
Design
These are all the preliminary design class diagram .A design class diagram (DCD) identifies the OOP classes that will be needed for the system. The set of design classes includes problem domain classes, view layer classes, sometimes separate data access classes, and utility classes.
Software Architecture
-
approves
provide funding , Reviews and approves
Design the application and follow the rules
Once we had overall structure and an overall approach for implementing the new system, we begin to drill down to the subsystem design.
Code
Iterative/Agile
Approves
provide funding and approves
Codes the application and tests
As the programmers write the code, they also perform individual testing on the classes and functions they program.
Figure
Model Type
Analyst
Responsibility of Management
Software Engineers
Why?(Reason)
Use Case List
Iterative/Agile
Records the information.
I.e. Author
Setup meeting with the clients/ end users
He writes the Use case diagrams. Designs system
This is the initial information for any system to understand the new system
Domain Class List
Iterative/Agile
Records the information and use it for the database attributes.
I.e. Author
Setup meeting with the clients/ end users
Design system
Attributes are pieces of information that helps define and describes details about domain classes.
Domain Class Diagram
RAD
I.e. Author
Approval
Divides the system into subsystem.
Domain Classes are very powerful and frequently used for undersetting the total system
Use Case Diagram
-
Completes Initial analysis. Reviews
Monitor the system and approval
Creates use case diagrams
It is a graphical portability and user involved in the subsystem
Activity Diagram
-
Reviews
Monitor the system and approval
He will create initial screens using activity diagrams. And also adds flow of the screens.
It shows the basic interaction between user and system.
User Interface Sketch
Iterative/Agile
Reviews
Reviews
Design the initial page layout
It shows the basic subsystems of the application schema.
Database Design
Iterative/Agile
Reviews and approves
Reviews
Design
Designs database schema.
Software Components Diagram
-
Reviews and approves
Reviews
Design
It shows overall structure of the new system.
Design Class Diagram
-
Reviews and approves
Reviews
Design
These are all the preliminary design class diagram .A design class diagram (DCD) identifies the OOP classes that will be needed for the system. The set of design classes includes problem domain classes, view layer classes, sometimes separate data access classes, and utility classes.
Software Architecture
-
approves
provide funding , Reviews and approves
Design the application and follow the rules
Once we had overall structure and an overall approach for implementing the new system, we begin to drill down to the subsystem design.
Code
Iterative/Agile
Approves
provide funding and approves
Codes the application and tests
As the programmers write the code, they also perform individual testing on the classes and functions they program.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.