BIS261 Final Exam Paper

BIS261: Final Exam Study Guide
Exam Structure
Class, the Final Exam consists of the following:
• 42 Questions worth 250 points, which breaks down as follows: o 34 Multiple-Choice questions @ 5 points each o 8 Essay questions @ 10 points each
• There are four pages in the exam.
• Covers all of the reading assignments for the course: o Chapters 1-5, 7, and 16 from the textbook o International Association of Facilitators Basic Facilitation Primer o The articles from the DeVry University Library: Managing Virtual Teams by LaBrosse; Successfully Transitioning to a Virtual Organization by Lockwood; and Technology Support for Enhanced Productivity in International Virtual Teams by Seilheimer, Ishman, & Seilheimer
• Covers TCOs 1-8
Multiple-Choice
These are questions that are taken from all of the reading assignments and the weekly lectures. The best way to study for these questions is to review the reading, lectures, and quizzes. The multiple-choice questions will address the following topics:
1. Roles and responsibilities of a business systems analyst
a. ensure that the needs and wants of the client are represented correctly so that a solution can be developed and implemented by capturing and documenting the requirements needed to (design and) implement a solution
i. Analyzes the business processes to identify areas of inefficiency ii. Analyzes business requirements iii. Translate business requirements into IT projects to increase efficiency or profitability then works with the IT people to ensure the solution meets client’s needs
2. Business analyst's problem-solving approach
a. A systems analyst solves business problems using information systems technology
b. Problem solving means looking into business problem in great detail, completely understanding problem, and choosing best solution
3. Systems Development Life Cycle (SDLC) phases
a.
or relationships in use case diagrams
22. Types of testing: definitions and when to use each
SHOULD BE DONE EVERY TIME
Test Type Description Purpose Performed By
Unit test (sometimes called stub test) Check each system component by itself. Ensure that each component was implemented correctly before integrating it into the larger system. Programmers (usually)
Integration test Check the components in combination with each other. Ensure that components work together, doing what they were designed to do. Programmers or QA staff
System test (sometimes called end-to-end test) Check the operation of the complete system in a controlled environment. Ensure that the system, as a whole, satisfies requirements. QA staff
Acceptance test Try out the system with actual users in a realistic setting. Determine if system meets user needs and will be accepted as complete by the user organization. Users
a. Functional - Does it meet functional requirments
b. Audit – performed by outside independent party to verify that a critical system complies with certain standards
c. Performance – speed and processing capacity of system
d. Load- examine how well system perfoms under high deman (# users)
e. Usability- ease of