0% found this document useful (0 votes)
11 views3 pages

Summarized Notes

Uploaded by

shiphrahjob
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
0% found this document useful (0 votes)
11 views3 pages

Summarized Notes

Uploaded by

shiphrahjob
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/ 3

1.

Analysis Techniques:
o Observation: Watch users interact with the system to understand its
workings.
o Interviews: Conduct one-on-one conversations with users to explore issues
and practical difficulties.
o Questionnaires: Collect opinions from a larger group using predetermined
questions.
o Examination of Existing Documents: Review system documentation and
identify known issues.
2. Identifying Key Aspects of the Current System:
o Identify data flow (input, processing, output).
o Identify problems and user requirements.
o Define information requirements.
3. New System Requirements Specification:
o Systems analysts understand current system limitations.
o Design a new system to address identified problems.
o Create a Requirements Specification for the new system.
4. Hardware and Software Selection:
o Choose suitable hardware (e.g., barcode readers, touch screens).
o Select software based on functionality, compatibility, and user requirements.
5. ile/Data Structures:
o Field length, name, data type, and coding.
6. Input Formats:
o Data capture forms (paper-based or electronic).
o User-friendly layout and clear instructions.
7. Output Formats:
o Screen and report layouts.
o Consider readability and visual appeal.
8. Validation Routines:
o Range, character, length, type, format, presence checks, and
check digits.
9. Development and Testing:
o Ensure functionality and error removal.
10. Test Designs and Strategies:
o Verify components and overall system performance.
11. Test Data Types:
o Normal, abnormal, and extreme data.
12. Live Data:
o Data used with the current system.
13. Implementation Methods:
o Direct Changeover: Immediate replacement of the old system
with the new system.
1. Advantages: Fast implementation, cost-effective.
2. Disadvantages: High risk of failure, no fallback, lack of user
training.
o Parallel Running: Both current and new systems run
simultaneously for a period before the old system is phased out.
1. Advantages: Lower risk, easy system comparison.
2. Disadvantages: Time-consuming, resource-intensive.
o Pilot Running: Trial implementation in a controlled environment
before full-scale rollout.
1. Advantages: Low risk, fine-tuning, staff training.
2. Disadvantages: Slower implementation, potential
inconsistencies.
o Phased Implementation: Gradual replacement of parts of the
old system with the new system.
1. Advantages: Reduced risk, manageable process.
2. Disadvantages: Longer duration, potential compatibility
issues.
14. Documentation:
o Technical Documentation:
1. Detailed information for developers and IT staff.
2. Includes program listing, flowcharts, hardware/software
requirements.
o User Documentation:
1. Instructions for end-users on system operation.
2. Covers purpose, limitations, setup, and usage guidelines.
15. Efficiency Assessment:
o Analyze system efficiency in time, money, and resource use.
o Identify areas for optimization.
o Consider whether it operates faster and reduces staff time and
costs.
16. Ease of Use Evaluation:
o Assess usability and accessibility.
o Describe the user interface and address user feedback.
o Ensure users can easily make bookings, changes, and
cancellations.
17. Solution Suitability:
o Contrast the implemented solution with original task criteria.
o Discuss how well it meets departmental, customer, and staff
needs.
18. User Feedback Collection:
o Summarize testing process and outcomes.
o Address user concerns and suggestions.
19. Identify Limitations and Improvements:
o List limitations and explain each one.
o Recommend specific enhancements based on feedback and
analysis.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy