IS 581 Entire Course
For more course tutorials visit
www.is581.com
IS 581 Milestone 1 and 2 Case study Coastline Systems Consulting
IS 581 Milestone 3 and 4 Case study Coastline Systems Consulting
IS 581 Milestone 5 and 6 Case study Coastline Systems Consulting
IS 581 Milestone 7 and 8 Case study Coastline Systems Consulting
IS 581 Milestone 9 and 10 Case study Coastline Systems Consulting
IS 581 Milestone 11 and 12 Case study Coastline Systems Consulting
--------------------------------------------------------------------
IS 581 Milestone 3 and 4 Case study Coastline Systems Consulting
For more course tutorials visit
www.is581.com
There’s an old saying that suggests, “Don't try to fix it unless you understand it.” With those words of wisdom, the next milestone of our project is to study and analyze the existing system. There is always an existing business system, regardless of whether it currently uses a computer. The problem analysis phase provides the project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. Indeed, the analyst frequently uncovers new problems and opportunities. The problem analysis phase may answer the questions, “Are the problems worth solving?'' and “Is a new system worth building?''
The purpose of the problem analysis phase is threefold. First and foremost, the project team must gain an appropriate understanding of the business problem domain. Second, we need to answer the question, “Are these problems (opportunities and directives) worth solving?” Finally, we need to determine if the system is worth developing. The problem analysis phase provides the systems analyst and project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. In the process, they frequently uncover new problems and opportunities.
In this milestone you will perform a cause-effect analysis on the...