Please enable JavaScript.
Coggle requires JavaScript to display documents.
Systems Design, Implementation & Operation , How often to produce a…
Systems Design, Implementation & Operation
Introduction
Effective system analysis and design can help developers correctly define business problems and create a system to solve those problems
Conceptual System Design
- Evaluate Design Alternatives
-
-
-
-
-
- Prepare Design Specifications
-
-
-
- Processing procedures and operations
- Prepare the Conceptual Design Report
-
-
-
-
-
Physical System Design
-
- Special-purpose analysis report
- Triggered exception reports
-
-
-
-
-
iv, Procedures & Control Design
Procedure: Should cover input preparation, transaction processing, error detection and correction, controls, reconciliation of balances, database access, output preparation and distribution and computer operator instruction
Procedures documentation and training may take the form of system manual, user instruction classes, training materials or online help screens
Can be written by developers, users, or teams representing both groups
Control ensure effectiveness, efficiency and accuracy
Should minimize, detect and correct the errors
-
Physical system design report: Summarizes what was accomplished and serve as the basis for management's decision whether or not to be proceed to the implementation pahse
System Implementation
-
- Implementation Planning & Site Preparation
-
-
- Selecting & Training Personnel
-
The company can achieve the expected benefits and return on investment if the users are adequately trained.
-
Hidden cost of inadequate training: Decrease productivity of experts workers (to teach the inadequate) & increase company cost if something goes wrong
-
-
-
Operation & Maintenance
- Postimplementation review
- Postimplementation review report
- How often to produce a sales analysis report
- What the report should contain
- What it will look like
- Whether it is hard copy or screen output or both
- Which data elements must be stored to produce the sales report
- How they should be stored
- What type of file or database to use
1.Which sales data to enter
- Sale location
- Amount
- Where, when and how to collect data
- How to process the input and stored data to produce the sales report
- Which sequence the processes must be performed
Objective: To determine the nature, format, content and timing of reports, documents and screen displays
-
Report with no pre-specified content, format, or pre-specified schedule; usually prepared in response to a management request
Report with a pre-specified content and format, prepared only in response to abnormal conditions.
-
- System analyst consult with user to identify user needs and software requirement
- Standard contribute to program consistency, making it easier to read and maintain.
- Structured programming: A modular approach to programming in which each module performs a specific function and is coordinated by a central module
- Debugging: The process of discovering and eliminating errors
- Documentation explains how program works and is used to correct errors
- Includes flowchart, data flow program, E-R diagrams, data model, record layout, and narrative descriptions
- Stored in documentation manual
- Program maintenance: Updating a computer program due to changed user needs, fixed bugs, legal or regulatory changes or to make use of new technology
- Consist of implementation tasks, expected completion dates, cost estimates and who is responsible for each task.
- It specifies when the project should be completed and When AIS is operational.
- This includes completion time table, cost estimates, task milestones and who is responsible for each activity
-
-
-
-
Step by step reviews of procedures or program logic to find incorrect logic, errors, omissions, or other problems
Processing valid and erroneous transactions to determine if a program operates as designed and that valid transaction are handled properly and errors are detected and dealt with appropriately
Test of a new system using real transactions to determine if user-developed acceptance criteria are met
-
-
Changing from an old system to a new one by operating both systems simultaneously until the organization is confident the new system is functioning correctly
Changing from an old to a new system by gradually replacing elements of the old with the new until the old system has been entirely replaced
Changing from and old to a new system by implementing a system in one location using it until all problems are resolved and then implementing it in the rest of the organization
Review made after a new system has been operating for a brief period to ensure that the new system is meeting its planned objectives, identify the adequacy of system standards and review system controls
A report that analyzes a newly delivered system to determine if the system achieved its intended purpose and was completed within budget