Professional Documents
Culture Documents
Singla)
Organization charts are a tool for the systems analyst to use to increase their knowledge of operational
processes, job responsibilities, and information flow.
Qualifications.
technical specialist
a leader
able to secure cooperation
non-threatening to others - ie. human relations
creative - designers
good speaker and writer (good communication skills)
The analyst must be able to give good presentations to explain and sell ideas.
Background.
Bachelors or D.E.C + working experience.
Work experience is essential for on the job experience, expertise and management confidence.
programmer/analyst
Salary
increased programmer
responsibility
technician
1
SYSTEMS & SUB-SYSTEMS
A system is a combination of resources working together to convert input into output.
A business information system is a system that uses resources to convert data into information needed to
accomplish the purposes of a business.
Product Flow
The physical flow of goods.
ex. raw materials go to assembly and then to finished goods.
Information flow
The flow of support documents through a system.
ex. purchase order prepared in Purchasing, sent to receiving, then to inventory ....
ex. payroll receives time cards then prepares paychecks
A management information system spans at least on vertical level, and has feedback and control.
Feedback is comparing output to desired input.
Control is action taken to bring the difference within acceptable range.
2
SUMMARY OF THE ACTIVIES IN EACH STEP OF THE LIFE CYCLE (SDLC)
The Analysis Phase.
The problem is defined.
Alternate solutions are studied.
Recommendations are made to commit resources to the design of the system.
Each phase is documented and reviewed before moving forward. At each phase there can also be a step
back to repeat part or all of a preceding phase.
DOCUMENTATION.
It is not a task done to "wind-up" an activity.
It is the product and it is continuous and cumulative throughout the project.
The most essential documents are called the base-line specifications.
Performance specification
Design specification
System specification.
It is the visible and measurable end product and is the key to the successful management of the life-cycle.
3
The SDLC first step.
A problem or user need.
A written request originating from the user either on a memo or a standard document is received by the MIS
department. This request serves as an authorization for an initial investigation.
The manager initiating the request informs staff and superiors of the investigation and requests their cooperation.
The result of the initial investigation or information gathering is a document which serves as the project directive
requesting approval for the system design. Other names for this document - business specification, performance
specification.
FEASIBILITY ANALYSIS
1) Technical Feasibility?
Can it be done with existing technology?
2) Economic Feasibility?
Will the cost be offset by the benefits?
3) Operational Feasibility?
Will it work in the organization?
Economic feasibility or cost justification. At what point will the system become profitable.
Methods. Break-even analysis and ROI - Return on Investment
Note: Economic feasibility cannot be the only factor in a feasibility study as many benefits are intangible
and hard to quantify.
TANGIBLE BENEFITS INTANGIBLE BENEFITS
Increased sales Improved customer goodwill
Reduced expenses Improved employee morale
Reduced credit losses Better decision making
4
1) Form the system team. Users, management, technical staff.
2) Develop overview flowcharts. DFD from initial investigation.
3) Determine candidate systems. Hardware, processing, software.
4) Eliminate obvious candidates which:
- are too costly
- overkill the task
- beyond the technical knowledge
of the company
5) Detail the remaining candidates.
Input, output, processing, and storage requirements, and constraints.
6) Identify criteria for evaluation.
Performance criteria:
-reliability, accuracy, control, growth, flexibility, response time, usability
Costs:
-equipment, training, development, operation
7) Use a matrix to evaluate candidates with respect to the criteria. Assign a weight to each criteria.
- Rate each candidate (1 to 5)
- Multiply by the weight
- Add the scores for each candidate
8) The analyst should look at the closest highest scores, select the "best" system, and prepare a
recommendation.
DESIGN PHASE
INPUT DESIGN
Equipment
KEY-ENTRY - keyboard
DOCUMENT SCANNERS
- OCR - optical character reader (grocery checkout - bar codes)
- MICR - magnetic ink character reader (bank cheques)
- OMR - optical mark reader (exam scoring)
APPLICATION DEPENDENT TERMINALS
- ATM - automated teller machines
OTHER
- voice - touch-screen - light-pen
Evaluation
EVALUATE USER - application dependent terminal for general public
EVALUATE APPLICATION - speed considerations, volume of data, accuracy, control
EVALUATE COST
SCREEN DESIGN
Design considerations
- sequence must match input form
- place related items together
- field length and format must be known (MM/DD/YY)
- be consistent with field identifiers, messages, screen headers, and footers
- place data in same location on similar screens
- do not overcrowd the screen
- for columns of data, note that the cursor usually moves from left to right before top to bottom
- left justify text and alphanumeric data, right justify numeric data, line-up the decimal points
5
FILE DESIGN or DATABASE DESIGN
Steps involved in file design:
1) Establish the application support files, adding any required intermediate files needed to pass data between
the processing steps. Establish controls - backup files.
For each file,
2) Specify the access method required for each processing step.
3) Specify the organization required.
4) Specify the equipment needed to store the file. (disk, tape)
5) Determine the contents.
6) Determine the size.
Characteristics evaluated during file design.
- processing method
- required response time
- activity rate (number of transactions per processing run)
- volatility (number of adds, deletions)
- backup requirements
- device capacity
- costs (storage, maintenance, processing)
Some design considerations for placement of elements within a file:
- group keys at the beginning
- group related items together
- group most frequently used elements at the beginning
Types of files:
MASTER FILES Basic information about identified entities. Fairly static.
TRANSACTION FILES Records of source transactions used to update master files.
REFERENCE FILES Constant data used in an application run.
Tables not coded in programs since they can require updates occasionally. Tax tables.
ARCHIVAL OR HISTORY FILES Files kept for statistical or research purposes.
Transaction files that have been processed.
BACKUP FILES Copies of master or transaction files for the purpose of recovering lost
or damaged files. Several generations may be kept.
TRANSACTION LOG FILES Electronic journals kept for an audit trail on on-line systems.
Used for recovery during an on-line update.
Access Methods
PHYSICAL SEQUENTIAL OR SERIAL
Records are read in the same order in which they were recorded.
LOGICAL SEQUENTIAL OR KEY SEQUENCE
Records are read in a logical order according to a key field.
DIRECT Records are accessed by a value or key.
File Organizations
SEQUENTIAL Records are written one after the other. The file must always be read in the same order and always
from the beginning. To update, a new file must be created.
INDEXED Records can be accessed both sequentially or randomly by a key. Index files are maintained to support
the random access.
DIRECT Records are stored and located according to an address calculated by a mathematical formula applied to a
key. Fastest access. Does not handle large quantities of additions and deletions well.
DBMS - DATA BASE MANAGEMENT SYSTEM A group of logically related files. A method used to reduce
redundant data between files and systems. Allows sequential and direct access. Requires a data base
administrator to control application usage of data, to synchronize backup procedures and to maintain the
data base. The design of a database includes data modeling (normalization and entity-relationship
diagrams).
EQUIPMENT SPECIFICATION
6
DECISION TABLES
A decision table is a tabular representation of:
1) Conditions: factors to consider in making a decision.
2) Actions: steps to be taken when a certain combination of conditions exist.
3) Rules: specific combinations of conditions and the actions to be taken
DESIGN OF CONTROLS
System controls are defined as "a plan to ensure that only valid data is accepted and processed completely and
accurately."
Controls must be built into the system and become an integrated part of the design of the system.
The user has a major responsibility towards defining adequate controls. Walk-throughs provide an effective means
of evaluating controls. Controls must be documented in the design specifications for the system.
7
TEST LOG
PROGRAM: ________________
------------- OR --------------
PROGRAM: ________________
TEST: _________________________________________
_________________________________________
ERROR: _________________________________________
_________________________________________
----------------------------------------------------------------
CORRECTION: ____________________________________
____________________________________
____________________________________
8
CONVERSION
To implement a system there are different methods which are referred to as conversion methods. This is the process
of converting from the old system to the new system.
Conversion methods:
1) Parallel conversion. Both the new system and the old system are run in parallel. It is time
consuming, may require additional personnel or effort, is expensive, errors may be difficult to
detect, and may delay the adoption of the new system. It has the least risk.
2) Immediate cut-over Also known as crash conversion. The old system is no longer used and the new
system takes over. It is the most risky. May be used when other methods are not possible, if the
system is not critical, or if a fallback to another procedure is available. Sometimes may be used
because of user pressure.
3) Pilot conversion The new system is used for a select group of transactions (example: one
department or one product line) and the old system is used for the majority of the transactions.
The volume on the new system can then be increased.
4) Phased conversion The system is phased-in by running some programs in the new system with the
rest of the processing on the old system. Gradually all phases of the new system are in place.
(example: orders entered on the new system and the invoicing done on the old system.)
Performance Review
Change Requests