Вы находитесь на странице: 1из 5

CS360 Study Guide for Exam 1

Fall 2016
The exam will consist of the following types of questions:
Matching of terms and definitions (25 @1 each)

Short essays (3 @5 each)

Use case diagram diagnosis (10 @1 each)

Use case diagram interpretation (10 @1 each)

The total will be 60.
The exam will last for 75 minutes.

SDLC Terms / Concepts

1. Information Systems
Definition of information systemsAn information system is a well-coordinated collection of resources that gather
and transform data into information products and services that help the enterprise
perform its designed functions
Keep track of customers
Process orders
Manage inventory
Handle employee payrolls
Facilitate marketing operations
Optimize supply chains
Raw facts
Derived from data
Organized in a manner that humans can understand
Derived from information
System is an interrelated set of business procedures used within one or more business
units working together for a purpose

An information system should be able to add values (increase profits) to an
organization by
Improving productivity
Lowering costs
Reducing errors
Enhancing customer relationships
Increase competitive advantage
Six components of information systems:
Operational instructions for users
Industry standards, regulations, laws
Tangible components, peripherals
Most of the tailoring of systems occurs in the software where machines are
directed to act in user desired ways
P2P, LAN, WAN, Internet, intranet
System input and output
All systems respond to the needs of people even those which appear to be
automatic systems
Types of IS:
Transaction Processing Systems (TPS)
Focusing on capturing transaction data, e.g.,
ATM, cash register, point-of-sales
Management Information Systems (MIS)
Focusing on generating reports
Decision Support Systems (DSS)
Focusing on strategic decisions, what-if analysis, etc

The process of breaking down a system into smaller components
Allows the systems analyst to:
Focus on one component at a time
Build different components at independent times
Localize problems and errors

Reuse previously developed components

Results of dividing a system into modules of a relatively uniform size
Modules simplify system design
The extent to which subsystems are dependent upon each other


The extent to which a subsystem performs a single function

Sources of software

Reuse-Reuse previously developed components

2. Systems Development Li fe Cycle:

SDLC is a common methodology for systems development
A series of steps used to manage the phases of development for an information system

Selection and planning


Roles of System Analysts:

An agent of change
How to handle users resistance to change
A problem-solving strategist
Analytical skills
Technical skills
A group facilitator
Interpersonal skills: conflict management, group dynamics
Management skills: resource management, risk management
Computer-Assisted Software Engineering (CASE)
Used for increasing productivity and improving overall quality of system

Help automate the entire SDLC process

Assist analysts in managing project complexity
Drawing diagrams such as DFD, ERD, UC, class diagrams, sequence diagrams, etc.
Creating prototype systems for uses to look and feel
Automatically checking for incompleteness, inconsistency, or incorrectness between
specifications, diagrams, reports, and forms
Central repository
Integrated storage of specs, diagrams, reports, etc.
Documentation generation
Producing technical and user documentation in standard formats
Code generation
Automatically generating codes based on diagrams
3. Project Planning and Selection
Request for System Services (purpose, contents)

Baselin e Project Plan

Project Scope Statement (purpose, contents)

Incremental commitment

Aspects of feasibility

Feasibility Analysis (purpose, contents)

Costs and Benefits of information systems

Calculation of break-even point, ROI

4. Requirement Determination
Purpose of requirement gathering

Functional and nonfunctional requirements

Traditional methods for determining requirements

Modern methods for determining requirements

Business process reengineering

OO Modeling
1. Be prepared to identify syntactical errors in UML use case diagrams. (Hint: You should
pay special attention to the diagram examples on the slides.)
2. Be able to interpret a use case diagram and determine if a statement is true or false based
on your interpretation.