Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
34 views2 pages

Review Questions

The document discusses several topics related to systems analysis and design: 1. It outlines steps for gathering requirements including defining needs, prioritizing them, prototyping, and evaluating alternatives. 2. It defines functional requirements as relating to user services and non-functional as technical specifications. 3. It states that a structured walkthrough aims to find errors in work to improve quality, not evaluate employees.

Uploaded by

Rajneet Chand
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
34 views2 pages

Review Questions

The document discusses several topics related to systems analysis and design: 1. It outlines steps for gathering requirements including defining needs, prioritizing them, prototyping, and evaluating alternatives. 2. It defines functional requirements as relating to user services and non-functional as technical specifications. 3. It states that a structured walkthrough aims to find errors in work to improve quality, not evaluate employees.

Uploaded by

Rajneet Chand
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Review Questions

1. Gather information
Define system requirements
Prioritize requirements
Prototype for feasibility and discovery
Generate and evaluate alternatives
Review recommendations with management
2. Functional requirements define the functions or user services that will be supported by the
system. Such things as support of business processes and reports are included in functional
requirements.
Non-functional requirements are other technical specifications and include such things as
technical, performance, usability, reliability, and security requirements.
3. The objective of a structured walkthrough is to find errors in a piece of work. In other words,
it is a quality control activity to improve the quality of a piece of work, such as a data flow
diagram or data model.
The objective is not to be a performance review or an evaluation of an employee.
4. Establish an objective for the interview session.
Determine the persons who should be involved in the interview, both users and team
members.
Develop a list of questions and issues to be discussed.
Review any related documentation. Existing reports or procedure manuals are a good source
of questions and issues to discuss.
Set time and location.
Inform all participants of objective, time, and location. It is especially important that the
users be informed of the objectives so that they can come to the meeting prepared
5. BPR stands for business process reengineering. Business systems are always a combination
of manual and automated processes. A change in the level or approach of automation will
have an important impact on the total business process. Increasing levels of automation
have also provided opportunities to shift many manual processes to automated processes.
Additional information and services are also possible with increased automation. Thus,
information technology has provided opportunities for companies to reengineer their
business processes.
6. Because user requirements cannot be tested in the programming sense of the word, another
method must be used to validate the requirements. A widely used method is a structured
walkthrough. When a piece of work is completed that describes some user requirements,
either in the form of a diagram or textual description, a walkthrough is conducted. In the
walkthrough the work is reviewed with the objective of finding missing pieces, checking for
accuracy, and verifying that the diagram is internally consistent
7. Review existing reports, forms, and procedure descriptions.
Conduct interviews and discussion with users.
Observe and document business processes.
Build prototypes.
Distribute and collect questionnaires from stakeholders.
Conduct joint application design (JAD) sessions.
Research vendor solutions.
8. An activity diagram is used to document the detailed steps of a business process or
workflow.
Thinking Critically

Same as Week 4 Tutorial diagram.

You might also like