wayground logo

Free Printable Worksheets

Font size

S
M
L
XL
Worksheets

Management Information Systems Quiz H2

Total questions: 71

Worksheet time: 58mins

Name
Class
Date
1.

What is another name for Systems Development Life Cycle (SDLC)?

a)

Agile Development

b)

Waterfall Model

c)

Prototyping

d)

Spiral Model

2.

Which stage in the system life cycle involves translating system specifications into program code or software?

a)

Systems Analysis

b)

System Design

c)

Programming

d)

Testing

3.

What is the purpose of the Technical Feasibility Study in the system life cycle?

a)

Analyzing data

b)

Evaluating available technologies

c)

Determining information requirements

d)

Identifying problems

4.

Which testing phase is considered the most critical in systems development?

a)

Systems Testing

b)

Integration Testing

c)

Acceptance Testing

d)

Unit Testing

5.

What is the main focus of the Spiral Model approach in system development?

a)

System integration

b)

Software design

c)

Project planning

d)

Risk assessment

6.

What is the primary goal of Agile Development in system development?

a)

Minimize overall risk

b)

Encourage written communication

c)

Focus on face-to-face communication

d)

Deliver working software quickly

7.

Which approach relies on the skills and experience of individual staff for system development?

a)

Ad-Hoc Development

b)

Waterfall Model

c)

Prototyping

d)

Spiral Model

8.

What is the purpose of the Requirements Definition stage in the prototyping approach?

a)

Create a simple design

b)

Gather client needs

c)

Develop an actual prototype

d)

Assess the proposed system

9.

Which tool is used for visualizing, specifying, and documenting software in the System Design phase?

a)

Entity-Relationship Diagram (ERD)

b)

Flowchart

c)

Unified Modeling Language (UML)

d)

Data Flow Diagram (DFD)

10.

What is the final stage in the system life cycle where the system is reviewed and maintained?

a)

Implementation

b)

Production and Maintenance

c)

System Analysis

d)

Programming

11.

consists of well-defined phases that are followed methodically. Most of the larger organizations use the SDLC process in their development to check if the requirements are followed, including its progress.

(a)  

12.

is the oldest method when building information systems. It is a phased approach in creating or building a system by dividing systems development into formal stages. It is still used for large complex systems that require a formal requirements analysis, predefined specifications, and tight control in the process of creating a system

(a)  

13.

·       What is the business process needed to support a system?

·       What problems do you want to solve?

(a)  

14.

·       Is the technology available to create the system?

·       Which of the available technologies should be used?

(a)  

15.

·       What are the resources needed to implement the system?

·       Will the system’s benefits outweigh its costs?

(a)  

16.

·       Will the system be used to its full capacity?

·       Will the system be used appropriately by its intended users?

(a)  

17.

·       Does it support other systems such as web and mobile technologies?

(a)  

18.

In this phase, the system design shows how the system will fulfill the objectives based on the requirements that have come up. The designer of the system will be responsible for giving the details of the system specification, which will deliver all the functions that have been identified in the system analysis phase.

(a)  

19.

This phase is the most respected in systems development. Testing each module in every simulation does not mean that the functionalities are in good condition; rather, it is important to test the entire system. It should include attempts to get the system to fail and to violate processes and security controls.

(a)  

20.

In the new IS, implementation is referred to as delivery. This consists of conversion and training. Conversion takes place when an operation in an organization switches from using an existing or old system to the new system.

(a)  

21.

implementation is referred to as

(a)  

22.

When the new system is installed, it is said to be in production. In this stage, the system will be reviewed by both users and technical specialists to check if it meets the original objectives. If the system is fine and meets all the objectives, then it should be maintained.

When the system is in production, the errors will be corrected, meet all the requirements, or improve processing efficiency. If there are some changes or new requirements in software or hardware, or if there is an improvement of the process, it is called maintenance.

(a)  

23.

In this stage, the system will be reviewed by both users and technical specialists to check if it meets the original objectives. If the system is fine and meets all the objectives, then it should be maintained.

(a)  

24.

When the system is in production, the errors will be corrected, meet all the requirements, or improve processing efficiency. If there are some changes or new requirements in software or hardware, or if there is an improvement of the process, it is called

(a)  

25.

This approach relies on the skills and experience of the individual staff. It only refers to the small projects at which the staff is skilled.

(a)  

26.

This method is the most common and the earliest structured system development and is still widely used.

(a)  

27.

It is developed on the assumption that it knows all the requirements at the beginning of the project. When using this approach, the developer only builds a simplified version of the proposed system and presents it to the client. After presenting, the client will give feedback for revisions or adjustments based on the requirements.

(a)  

28.

This is where the client needs are gathered for developing the software. The requirements of the system are defined in detail.

a)

Requirements definition

b)

Design

c)

Assessment

29.

A simple design of the software is created, which gives a brief idea of the system to the user.

a)

Requirements definition

b)

Design

c)

Assessment

30.

A proposed system is presented to the client for assessment. The client will then look for the strength and weaknesses of the created software.

a)

Requirements definition

b)

Design

c)

Assessment

31.

o    An actual prototype is designed based on the information gathered from the design phase.

a)

Prototype creation

b)

Prototype refinement

c)

System implementation

32.

If the client is not satisfied, the software needs to be refined according to the client’s

feedback and suggestion.

a)

Prototype creation

b)

Prototype refinement

c)

System implementation

33.

The final system is developed based on the final prototype. It is already tested and deployed to production. Then, it undergoes routine maintenance.

a)

Prototype creation

b)

Prototype refinement

c)

System implementation

34.

·         This approach is designed to include the best features from the waterfall and the prototype models. It describes the process that is followed as the development takes place.



(a)  

35.

Requirements are gathered from the customers, and the objectives are identified.

a)

Project objectives

b)

Risk assessment

c)

Production

d)

Planning and management

36.

During the second quadrant, all the possible solutions are evaluated to select the best possible solution. Then the risks associated with that solution are identified and resolved using the best possible strategy.

a)

Project objectives

b)

Risk assessment

c)

Production

d)

Planning and management

37.

The identified features are developed and verified through testing.

a)

Project objectives

b)

Risk assessment

c)

Production

d)

Planning and management

38.

Customers evaluate the developed version of the software and check for improvements. They also manage the developed software while looking for possibilities of errors.

a)

Project objectives

b)

Risk assessment

c)

Production

d)

Planning and management

39.

·         This approach focuses on the fast delivery of the working software by dividing a large project into a series of small subprojects, which will be completed in short periods using iteration and continuous feedback.

Since the project is divided, each team works on a small project. It helps minimize the overall risk and allows the project to adapt to changes more quickly. In addition, there is face-to-face communication over written documents, so it encourages the members to collaborate and make decisions quickly.

(a)  

40.

Tasks in the Development Process Life Cycle (1)

(a)  

41.

Tasks in the Development Process Life Cycle (2)

(a)  

42.

To communicate ideas about the data that have been gathered, systems analysts and programmers use convention symbols, such as the ___ it's symbols are suitable for describing any information systems (IS) even if this is not computer-based. It helps pinpoint the weaknesses in an existing system. While ___ are easy to learn and use, these still have limitations like any diagramming method and cannot describe a system completely.

(a)  

43.

is a graphical standard for visualizing, specifying, and documenting software. This tool helps developers to communicate and logically validate desired features in the design phases of software development projects. It consists of diagrams that describe the use case, class, interaction, activity, and physical components

(a)  

44.

-          A number, statement, image, or video that may represent specific data.

(a)  

45.

Sale of goods and services, payment of payables to suppliers, investment of cash by the owners, or internal and external transactions

(a)  

46.

People, places, things, events, etc.

a)
Objective measurements of the characteristics of entities
b)

Business transactions and raw facts

47.

-          It refers to a collection of data, such as words, numbers, images or graphics.

-          This is a produced data that contains useful context for some users that may need it.

(a)  

48.

-          Every information must be up to date based on the requirements—not too early and not too late for the end user.

(a)  

49.

A system must have appropriate and relevant information in every module. It must be relevant to the user who is using it.

(a)  

50.

Information must be correct or precise. For example, systems performing calculations must produce the exact values.

(a)  

51.

-          Not all information must be displayed in the system. It should only contain the minimum detail that is appropriate to the user.

(a)  

52.

Any information should be understandable. The format and how the information is presented are important. Using colors can enhance the presented information to make it easier for the user to understand.

(a)  

53.

Any information must be complete based on the requirements. If an information is incomplete, it may lead to bad decisions

(a)  

54.

-          This refers to the components that are interrelated, working together with a common goal to accept inputs and outputs.

(a)  

55.

is the information or data a user adds in the system.

a)

Input

b)

Processing

c)

Output

d)

Feedback

e)

Control

56.

is the efficiency of data processing. It enables an organization to process millions of data.

a)

Input

b)

Processing

c)

Output

d)

Feedback

e)

Control

57.

refers to the data or information that has been processed and displayed to the end users.

a)

Input

b)

Processing

c)

Output

d)

Feedback

e)

Control

58.

refers to the comments or suggestions in the system. This is used to improve or make any process more manageable for end users.

a)

Input

b)

Processing

c)

Output

d)

Feedback

e)

Control

59.

is about managing the operations in every process of the system.

a)

Input

b)

Processing

c)

Output

d)

Feedback

e)

Control

60.

-          This is the scope of activities in which it is limited for viewing or accessing any module of a system.

-          Every user of the system has a specific access on each module. For example, the person who is responsible for the inventory can only access the inventory module, while the manager has access to all the modules of the system.



(a)  

61.

-          Every system consists of subsystems that have different objectives and interactions based on the given requirements.

All subsystem uses the given resources to meet the given objective.

(a)  

62.

It refers to the connection of each system or subsystem boundaries and serves as the connection to display the output from one (1) system to the input of another system

(a)  

63.

-          This refers to the people, organizations, and other systems that give and receive data from the system.

(a)  

64.

-          Every system always needs feedback to be able to do its job and to process accurately based on the requirements. Having an effective feedback and continuing to adjust the activities of the system assures the user that the system can achieve its goals.

(a)  

65.

-          It refers to a set of interrelated components that collect any information or data, process, store, and display the output to support decision-making.

(a)  

66.

This system is the most widely used information system. The function of this system is to record data which are collected at the boundaries of organizations. This system also records the transactions inside an organization.

(a)  

67.

Supply chain refers to the sequence of activities. It includes marketing, manufacturing and assembly, packing and shipping, and billing and collection.

(a)  

68.

This system manages the relationship of the organization to its customer.

Service representatives use this system to talk to their customers via phone.

(a)  

69.

Most of the organizations use business intelligence systems to compete better with other organizations. This system accesses massive data, usually larger databases called data warehouses

(a)  

70.

This system helps to find actions and answers most of the questions like "What if?"

(a)  

71.

This system uses artificial intelligence to be able to preserve the knowledge of an expert and to solve problems.

(a)