Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Business Analysis
M1: S2-S3
| Question | Answer |
|---|---|
| A method that is classically thought of as the set of activities that analysts, designers, and users carry out to develop and implement an information system. | System Development Life Cycle (SDLC) |
| Is a systematic approach which explicitly breaks down the work into phases that are required to implement either new or modified Information System. | System Development Life Cycle (SDLC) |
| The basis for a candidate system is the recognition of a need to improve an information system or a procedure. | Project Selection |
| Environment-based ideas originate from customers, vendors, government sources, and the likes. | Impetus of System Change |
| What are the Stages of System Development Life Cycle | - Planning - Analysis - Design - Implementation - Testing and Integration Development and Maintenance Support |
| Obtain approval for the project, initiate, assess feasibility, plan, and schedule. | Planning Stage |
| In this stage you define the problem and scope of the existing system. | Planning Stage |
| In this stage you provide an overview of the new system and determine its objectives. | Planning Stage |
| In this stage you confirm project feasibility and produce the project schedule. | Planning Stage |
| In this stage you consider threats, constraints, integration, and system security during this phase. | Planning Stage |
| In this stage you create a feasibility report for the entire project at the end of this phase. | Planning Stage |
| Understand business needs and processing needs. | Analysis Stage |
| In this stage you gather, analyze, and validate the information. | Analysis Stage |
| In this stage you define the requirements and create prototypes for the new system. | Analysis Stage |
| In this stage you evaluate alternatives and prioritize the requirements. | Analysis Stage |
| In this stage you examine the information needs of end-users and enhance the system goal. | Analysis Stage |
| In this stage you prepare a Software Requirement Specification (SRS) document at the end of this phase, detailing the software, hardware, functional, and network requirements. | Analysis Stage |
| Define solution system based on requirement and analysis decision | Design Stage |
| In this stage you define a solution system based on requirement and analysis decisions. | Design Stage |
| In this stage you include the design of applications, networks, databases, user interfaces, and system interfaces. | Design Stage |
| In this stage you transform the SRS document into a logical structure, which contains a detailed and complete set of specifications that can be implemented in a programming language. | Design Stage |
| In this stage you create a contingency, training, maintenance, and operation plan. | Design Stage |
| In this stage you review the proposed design. Ensure that the final design must meet the requirements stated in the SRS document. | Design Stage |
| In this stage you prepare a design document that will be used during the next phases. | Design Stage |
| Construct and implement the design into source code through coding. | Implementation Stage |
| Combine all the modules into a training environment that detects errors and defects. And integrate the information system into its environment and install the new system. | Testing and Deployment/Integration Stage |
| Is prepared through a test plan that includes test-related tasks such as test case generation, testing criteria, and resource allocation for testing. | Test Report |
| Keep the system healthy and improve. | Maintenance and Support |
| In this stage it includes all the activities such as phone support or physical on-site support for users that are required once the system is installed. | Maintenance and Support |
| In this stage you implement the changes that software might undergo over a period of time or implement any new requirements after the software is deployed at the customer location. | Maintenance and Support |
| In this stage you handle residual errors and resolve any issues that may exist in the system even after the testing phase. | Maintenance and Support |
| Maintenance and support may be needed for a longer time for large systems and for a short time for smaller systems. | TRUE |
| A system project may be dropped at any time prior to implementation although it becomes more difficult (and costly) when it goes past the design phase. | Project Termination |
| The objective of __________ is to determine whether the request is valid and feasible before a recommendation is reached to do nothing, improve or modify the existing system, or build a new one. | Project Selection |
| Sources of Project Request: Requesters Inside the Organization | - Senior Executives - Department Managers - Analyst |
| Sources of Project Request: Requesters Outside the Organization | Government Agencies |
| Strategies for Determining Information Requirements: Key Strategies or General Approaches | - Asking - Getting information from the existing information system - Prototyping |
| Strategies for Determining Information Requirements: 3 Key Asking Methods | - Questions may be open-ended or closed - Brainstorming - Group Consensus |
| Has been called data analysis approach | Getting Information from the existing Information System |
| Is used when the user cannot establish information needs accurately before the information system is built. | Prototyping |
| The user needs to focus on real-life systems that can be adjusted. The iterative discovery approach involves capturing initial information requirements, building a system to meet them and adjusting based on user experience and additional requests | Prototyping |
| Someone must decide which requests to pursue and which to reject (or perhaps solve by other means) | Committee |
| One of the more common methods of reviewing and selecting projects for development is by __________. | Committee |
| What are the Committee Methods? | - Steering Committee Method - Information System Committee Method - User-Group Committee Method |
| In many organizations, _________ (also called operating committees, operating councils, or project selection boards) supervise the review of project proposals. | Steering Committee Method |
| This typically consists of key managers from various departments of the organization, as well as members of the information systems group. | Steering Committee Method |
| A typical seven to ten - person committee would consist of the following membership. What are those? | - Upper Management members - Departmental Managers - Technical Managers - Information System group |
| The __________ receives proposals and evaluates them. The major responsibility of the _________ is to make a decision. | Committee |
| Under this method, all requests for service and development are submitted directly to a review committee within the information systems department. | Information System Committee Method |
| This method can be used when many requests are for routine service or maintenance on existing applications. | Information System Committee Method |
| Under this method, the responsibility for project decisions is delegated to the user. | User-Group Committee Method |
| Individual departments or divisions hire their own analysts and designers, who handle project selection and carry out development. | User-Group Committee Method |
| Some organizations have management planning committee that proposed new projects, which are in tum evaluated by the systems department staff members, | Other Method |
| All proposals should be submitted to the selection committee for evaluation to identify which projects are most beneficial to the organization. | Preliminary Investigation |
| Methods used in data gathering during the preliminary Investigation | - Reviewing organization documents. - Interviewing selected company personnel |
| It examines projects feasibly and the likelihood that the system will be useful to the organization. | Preliminary Investigation |
| This feasibility test asks if the system will work when it is developed and installed. | Operational Feasibility |
| Is there sufficient support for the project from management? From users? Are current business methods acceptable to the users? Have the users been involved in the planning and development of the project? Will the proposed system cause harm? | Operational Feasibility |
| Does the necessary technology exist to do what is suggested (and can it be acquired)? Does the proposed equipment have the technical capacity to hold the data required to use the new system? Can the system be expanded if developed? | Technical Feasibility |
| The cost to conduct a full systems investigation. The cost of hardware and software for the class of application being considered. The cost nothing changes (i.e., the proposed system is not developed) | Financial and Economic Feasibility |
| “Financial Benefits must equal or exceeds the costs” | TRUE |
| Requests that do not pass feasibility tests are not pursued further unless they are revised and resubmitted as new proposals. | Handling Infeasible Projects |
| Is a conceptual model which includes policies and procedures for developing or altering systems throughout their life cycles. | System Development Life Cycle |
Created by:
lykieee