Reference no: EM132412694 , Length: word count:3000
ISM 3113 Systems Analysis and Design Assignment - University of South Florida, USA
Part I - (Review Questions for your personal assessment of what you have learned here)
These questions are not being graded. The purpose of this section is to send you off from this course with a reminder of the minimum terms and concepts you will be expected to know on the job. It should take no more than 4 or 5 sentences to answer each of these questions, and probably one simple sentence is not enough to communicate adequate knowledge in the area.
1. What is a requirement?
2. Explain how features and functions relate to requirements?
3. Explain stakeholders.
4. Explain end-users.
5. What is a user story?
6. How do we develop a requirement from a user story?
7. Explain the difference between user story and use case.
8. What is SDLC?
9. What is CMM? Describe all its levels.
10. Explain the difference between Waterfall and Agile.
11. What is Devops?
12. Explain how DevOps differs in focus than SDLC.
13. What is CICD?
14. Explain micro-services architecture.
15. Explain the server topology of: Dev - Test - Stage - Prod.
16. What is a user acceptance test?
17. Explain the difference between black box and white box testing.
18. What is a Service Level Agreement (SLA)?
19. What does "Five 9s" mean?
20. How many minutes per year is "Five 9s"?
Part II - The Purpose of this section is to assess whether you can demonstrate the following skills effectively at the end of this course:
1. Based on your own user experience, create a user story that describes your user need currently not being met by the Canvas system.
2. From that user story, write the requirement that the Canvas system shall do.
3. List a feature or features for the requirement.
4. List a function or functions for the feature.
5. Create a user acceptance test for the requirement.
6. Describe a non-functional (quality) criteria for this requirement.
7. Create a user acceptance test that could measure the quality described above.
Part III - It is intended to assess your ability to evaluate a case study.
1. Evaluate the Heineken Case posted in the final exam module.
2. Use the same evaluation questions we have been using for the other case studies this term.
Case Study - Heineken USA: Reengineering Distribution with HOPS
Case Study Analysis Questions -
Basic: Describe a system, its processes and requirements
What are the 2 - 3 strategic goals for the project discussed in this case?
What is the business problem they are trying to solve here?
Restate the problem as an IT research question: "How can we create/design a system to ... (solve the problem)?"
List the most obvious requirements of the system based on the strategic goals - (the business processes or user experience the system must perform).
- List features of each requirement (what the system does).
- List Functions of each requirement (how the system does it).
Write a user story or use case for each requirement.
Write a user acceptance test for each requirement.
Who are the primary stakeholders in this system? (Use bullets)
Describe this system with a narrative.
Identify and draw the system processes with a model.
Intermediate: Requirements Elicitation
List the interview questions you would ask the end-users to develop the user stories for the requirements.
List the interview questions you would ask the stakeholders to develop the SOW, scope of the project, time horizon, budget.
Advanced: Gap Analysis
If this is a BPR effort list the requirements that are not being met by the current system.
List and describe the legacy requirements that will continue in the new system.
Create a model and narrative that closes the gaps between the old system and the new system.
Attachment:- Heineken Case.rar