System Analysis and Design Case Study: Search for Technician Online

This case study report focuses on the development of a Management Information System (MIS) called "Search for Technician Online" (STO). The system aims to connect customers with IT technicians for on-site support. The report details the system's three user roles: customers, technicians, and administrators. Customers post job requests, technicians submit bids, and the administrator manages the system. The report outlines the aims and objectives, including solving customer problems in finding technicians, reducing costs, and eliminating manual processes. It covers the project's scope, budget, and methodology, including the System Development Life Cycle (SDLC), data collection, system design, coding, testing, and implementation. The report includes diagrams such as the System Development Lifecycle Diagram, Context Diagram, Data Flow Diagram, Entity Relationship Diagram, and Gantt chart to illustrate the system's functionality and development stages, referencing the project's development process and methodology. The report concludes with references and appendices including diagrams.

System Analysis and Design 1
Management Information System Case Study
Affiliate Institution
Professor’s Name
Student
Date

System Analysis and Design 2
Executive summary
Management information system is a software program hosted on a computer system to help the
various companies manage their staff and customers in an easy way. Management information
system is an overall management tool which manages everything including inventories. In this
report we will develop an information system which will help the system users to look for
technicians through online platform called, “Search for Technician Online.” In this kind system,
all technicians are registered over the STO system and they will have to be standby online. In
this case whenever the customer need any assistance from the technician, he or she will post the
job online. All the technician will be send an alert message and they will have to place the bid on
the order. (Glover, Sarma & Overbye, 2017)
Introduction
In this report, the management information system will have three users, the customers, the
technician and the administrator. Customers post new jobs and the technicians made their
proposals. The client has approved the winning bid, the availability of the job is removed from
the system and the other applicants will be send an automatic message that they are unsuccessful.
The qualified technician will immediately visit the customer to provide the solution at home.
After the technician is done with the work, the customer will now approved that the work is
completed and the administrator will release payment to the technician account through online
platforms.
The administrator is in control of everything going on within the system. He can regularly update
the system by deleting and adding technician. STO is an online information management system
which helps IT technicians to interact and get work from customers. The technician is conducted
through the system and the solution is provided at home.

System Analysis and Design 3
Aims and Objectives of the research
 The research is conducted to identify the problem existing with customers while needing
the IT technician to solve the problem
 To develop a system which will help to solve the problem of accessing and finding
reliable technicians through online
 To ensure that the customers look for technicians wherever they without incurring
travelling cost
 To enable the technicians to meet reliable customers who may need their solutions and
getting a secure payment on the same
 To get rid of the manual system of looking for technicians manually and instead the
customer has to connect to the internet and search for client.
 To reduce the cost and the time wastage
The scope of the Project
The scope of this project is to provide a solution in an IT oriented information system that helps
to connect IT technician to customers. The information system to be developed is working on all
computing devices but limited to internet users only.
Project budget
Category Budget for Period in USD
Week
1
Week
2
Week
3
Week
4
Week
5
Week6
Human Resources
(internal)
Human Resources
(external)
Purchases (COTS)
Equipment
Premises
Tools
Travel costs

System Analysis and Design 4
Training
Review activities
Other
Total 100 100 200 500 200 100
Total cumulated 100 100 200 500 200 100
Methodology
Project development life cycle
During the development process steps will be followed to ensure that all the system requirements
are met. The stages which were followed during the development process include the following
explained below; (Roth, Dennis & Wixom, 2013)
1. Problem identifications – the problem was identified and the necessary discussion took
place to ensure that the team members will be able to find out the solution for the
problem. The problem was that using the manual way to look for technicians to assist in
the maintenance and repair of gadgets is too local and tiresome. Customers waste a lot of
time looking for these technicians and spending a lot travelling from one place to another.
2. Problem definition – the problem identified is put on the table to be discussed by the
project team members. And the solution on the same will be defined for implementation
3. Data collection and analysis – after the problem has been defined the data are then
collected and the same data will be analyzed without any modifications. This will help us
to acquire the correct value of the analyzed results. (Glover, Sarma & Overbye, 2017)
4. System design – during this stage the design is designed so that the layout will be figured
out. The data flow diagrams will be drawn so that it will be able to describe how the
system will work

System Analysis and Design 5
5. System coding – the system is coded according to the design drawn by the system
analyst. While coding unit testing is being done to minimize bugs when the software will
be deployed
6. Implementation of the new system. STO is in this stage deployed to be used for the first
time. The training on the use of system is carried out to ensure that the users can get to
know how to use the system. (Glover, Sarma & Overbye, 2017)
7. System testing and documentation – the system will be tested through system testing
technique to ensure that the system develop is free from bugs
System development lifecycle diagram
The development lifecycle diagram was sketch as shown below.

System Analysis and Design 6
From the diagram above is a description of how the system was being developed. The system
was developed following the procedures indicated in the diagram above. Programmers developed
Gantt chart and DFD diagrams to show the stages in which the system is going to work.
References
Roth, R., Dennis, A., & Wixom, B. (2013). System analysis and design. Hoboken, N.J.: Wiley.
Ramana, N. (2011). Power system analysis. Noida, India: Pearson.
Munro, N. Symbolic methods in control system analysis and design.
Glover, J., Sarma, M., & Overbye, T. (2017). Power system analysis and design. Boston, MA:
Cengage Learning.
Glover, J., Sarma, M., & Overbye, T. (2017). Power system analysis and design. Boston, MA:
Cengage Learning.

System Analysis and Design 7
Appendices
Context Diagram
Online Search for
Technician System
Technician Login
Payments
Amount
Orders
Description & deadline
Admin Login
Username
Password
User Login
Username
Password
Owners management

System Analysis and Design 8
Data Flow Diagram
Online Search For
Technician System
Customer
Request Technician
Post Job
Approve the bid
Technician
Apply for jobs
Possess skills
Make bids
Admin
Mange All users
Update database
Update users
System Moderation
System Owner
Manage payments
Manage Technicians
Request Customers

System Analysis and Design 9
Entity relationship diagram
Gantt chart
Period Highlight: 1 Plan Duration Actual Start % Complete Actual (bey ond plan) % Complete (beyond plan)
ACTIVITY PLAN START PLAN
DURATION
ACTUAL
START
ACTUAL
DURATION
PERCENT
COMPLETE PERIODS
1 2 3 4 5 6 7 8 9 10 11
Problem Identification 1 5 1 4 25%
Problem Definition 1 6 1 6 100%
Data collection and analysis 2 4 2 5 35%
System design 4 8 4 6 10%
Coding 4 2 4 8 85%
Software Testing 4 3 4 6 85%
Implementation and
Documentation 5 4 5 3 50%
Management Information System
Select a period to highlight at right. A legend describing the charting follows.

System Analysis and Design 10
User Input screen
Main menu Screen
Report screen