3/10 & 3/12 notes :)
3/10 & 3/12 notes :) MIS 441
Popular in Global eCommerce
Popular in Computer Science and Engineering
This 2 page Class Notes was uploaded by Becca Savino on Friday March 13, 2015. The Class Notes belongs to MIS 441 at Washington State University taught by Mr. Vithayathil in Winter2015. Since its upload, it has received 52 views. For similar materials see Global eCommerce in Computer Science and Engineering at Washington State University.
Reviews for 3/10 & 3/12 notes :)
Report this Material
What is Karma?
Karma is the currency of StudySoup.
Date Created: 03/13/15
Chapter 6 36 12 Common Mistakes article 1 Not picking the right manager Not getting the team behind the project Not getting executive buy in Too many projects implemented production at once Lack of communication Allowing scope to change Providing unrealistic timelines Not being exible Not having systems in place for trackingapproving changes 10 Micromanaging projects 11 Expecting too much of the software 12 Not having metric to define success omxeweww Analysis Phase in Systems development lifecycle Determining Requirements 0 Be Impartial Try to understand problems from the users point of view 0 Relax constraints don t let the constraints put a limit on what the system could do 0 Attention to detail Deliverables and outcomes to determine requirements 0 Interview the people on the system or observe doing it firsthand immerse yourself in the environment of the users 0 From existing documents 0 From computerized systems to look at existing systems and see what the newimproved system should be doing 0 Traditional methods I Interviewing individualsgroup I Observing workers Problem is that users tend to change their behavior when their being observed I Study business documents Attempting to get a historical and formal view of system requirements Can see what all information the system is taking into account ie Sales receipt shows time spent cash credit ect Contemporary Methods for Determining System Requirements joint Application Design IAD OOOOO Brings together all the users and they collect all the system requirements needed for the system Everyone gets to hear what each other have to say about the system They meet for an extended period of time Resource intensive Very formal agenda Participants I Session leader I Users I Managers I Sponsor I Systems Analyst I Scribe I IS Staff Group Support System CASE Tools 0 Tools that automate the process System Prototypes O O Iterative development process Rough draft of the system built so users can have a sense what the product will be Customers can give feedback on different extra features they would wouldn t like Used when I Users requests aren t clear I Only a few users involved in the system I When there are communication problems I Documentation is generally not great