Curriculum Design and Instruction To Teach
Systems Analysis and Design: Systems Analysis
Fundamentals: Assuming The Role Of The Systems
Analyst:
Author: Charles Hayes:
* Summary: Systems analysts are responsible
for designing computer information systems,
modifying systems to improve production or
work flow, or expanding systems to serve new
purposes. The information they deal with
relates to all aspects of an employer's
operations planning, monitoring, testing,
accounting, forecasting, coordination,
scheduling, etc. They must understand the
capabilities of a firm's equipment and
software, and may be asked to provide
recommendations about selection of new
equipment or software packages. They
may be responsible for a firm's entire
system or part of it, or work from
project to project. They also may
analyze systems for their employer or
for client firms.
Special Features Include:
Phases For Conducting a Needs Assessment:
Curriculum Design Supplement:
|a|. Subject-Questions-Answers:
Curriculum Design Plan:
Curriculum Design Goals:
Curriculum Design Objectives:
Instructional Goals:
Instructional Objectives:
Instructional Activities:
Instructional Evaluation Techniques:
Lesson Plans:
Standard Vocabulary:
Key Words/Phrases:
Learning Objectives:
A Limited Glimpse:
Topics Include:
* Introduction:
A. Assuming The Role Of The Systems Analyst:
I. Information As an Organizational Resource:
A. Managing Information as a Resource:
B. Managing Computer-Generated Information:
II. Systems Analysis and Design Concepts:
A. Transaction Processing Systems:
B. Office Automation Systems and Knowledge
Work Systems:
C. Management Information Systems:
D. Decision Support Systems:
E. Expert Systems and Artifical Intelligence:
F. Group Decision Support Systems:
G. Executive Support Systems:
H. Need For Systems Analysis and Design:
I. End Users:
III. Role of the Systems Analyst:
A. Systems Analyst as a Consultant:
B. Systems Analyst as Supporting Expert:
C. Systems Analyst as a Agent of Change:
D. Qualities of the Systems Analyst:
IV. The Systems Development Life Cycle:
A. Identifying Problems, Opportunities,
and Objectives:
B. Determining Information Requirements:
C. Analyzing System Needs:
D. Designing The Recommended System:
E. Developing and Documenting Software:
F. Testing and Maintaining the System:
G. Implementing and Evaluating the System:
H. The Impact of Maintenance:
V. Using CASE Tools:
A. Increasing Analyst Productivity:
B. Improving Analyst-User Communication:
C. Integrating Life Cycle Activities:
D. Accurately Assessing Maintenance Changes:
VI. Upper and Lower CASE:
A. Upper CASE Tools:
B. Lower CASE Tools:
VII. Software Reverse Engineering and
Reengineering:
VIII. Object-Oriented Systems Analysis
and Design:
IX. Need for Structured Analysis and Design:
X. Alternative Methodologies:
XI. Summary:
XII. CPU Case Episode 1: The CASE Opens:
XII. HyperCase Experience:
* STATE OF THE ART CURRICULUM DESIGN:
* NEW:
* BIBLIOGRAPHICAL REFERENCES & INDEX:
* ILLUSTRATIONS:
* B & W & COLOR PHOTOS:
* PAPERBACK:
* TRANSPARENT FRONT PAGE:
* BLACK-WHITE-RED OR BLUE BACK PAGE COVER:
* BINDED WIRE-0: BLACK-WHITE-RED OR BLUE:
* 75 WHITE PAGES: 8x11"
* ALLOW 10 TO 14 DAYS TO RECEIVE ITEM:
