You are on page 1of 12

Problem Definition

Electronic services are solutions of the future. They are offered online and cater to needs which used to
be catered to only through local means. Due to the rapid growth of information technology, many
companies have made the shift, or are planning to make the shift from traditional services to an
electronic environment.
Fixing electronic devices during a pandemic would have been as easy as requesting an uber. A user
would only have to request for a service, describe the nature of their problem, sort through various
price ranges, and have a courier pick it up for repair and drop it off after it's fixed. As complicated as that
may sound, the system is very simple. It would be accessible on a web application or by putting a call
through and describing to the person on the other end of the line, what the problem is.
The current method of fixing electronic devices is by going to a store or a fix-it outlet, which may
sometimes be crowded with up to 10 people. This wastes the time of the user who is seeking to fix their
device, which is terrible. Users expend energy going to a fix-it outlet and they’re not attended to
immediately, it can take up to an hour before they are attended to because the repair person works on a
first come first served basis
Nowadays, consumers use new technologies to create and consume services without direct personal
contact with companies. E-services can be used to deliver goods and services effectively, therefore,
firms and certain sectors have begun to develop and implement e-services to expand their effectiveness
and efficiency.
In a pandemic, fixing electronic devices proves impossible with its current method, this indicates the
need for a shift. Users wouldn’t be able to get their devices fixed because there are restrictions
surrounding gatherings, movement is limited, ultimately, it may take twice or three times the original
time it took for them to get their devices fixed before the pandemic- this negatively impacts the repair
person who relies on cases in order to make a living.
Our electronic devices have become very important in the modern world, they are similar to necessities,
they help keep us updated on the go, with electronic devices comes maintenance that we must attend
to, quite like a pup.

Currently, there are a few solutions to fixing electronic devices on sites such as Konga, which offers a
warranty on select purchased devices and has a courier person transport the goods to and from the
repair person back to the user. However, this is very basic, it does not give room for the user to select
from a wide range of prices, one that could suit their budget, as well as does not cover a wide range of
products, just a few. I don't want to have to purchase a device of 100,000 naira before I'm entitled to a
warranty, that just doesn't seem fair. In spite of its basicness, it gets the job done easily and efficiently
for premium users of the application.
Requirements Specification

3.1 Introduction
This will be a simple ‘walk up and use’ system , which is intended to bridge the gap between you
and your repair person. It consists of a backend, a database which will hold customers’ data,
their account- which will grant the user extra features- exclusively reserved for account holders,
repair person accounts, a.k.a the service providers, which will be a mandatory requirement of all
repair people as well as a front end, the users interface.
This system is one of a kind and helps to reduce the stress involved in getting one’s gadgets
repaired as well as creates an interface where both the repair person and the system which
serves as the middleman is rewarded with ease as well as provides comfort for the end-user.

3.2 Purpose
The purpose of this system is to create a virtual fix-it which will serve the end-user in acquiring a repair
person during a pandemic as well as after, by evolving the system with the latest technologies, adapting
and redesigning, basically- by using agile methodology in its development and maintenance.
It is geared toward people within the ages 18-35 students and workers majorly, and 36-50’s persons
secondly.

3.3 Scope
Anty will serve as the softwares name. It will allow users to get access to services without signing up,
create accounts for users, accept and send out users’ repair needs to various repair persons, present the
user various solutions and prices to pick from, contact a delivery person to pick up the gadget and drop
it off after fixing and final payment.
The rest of the system contains the discounts offered to account holders only and an accessories shop,
as well as an optional warranty on every fixed gadget for an additional fee, and its front end design.

3.4 Functional Requirements


Functional requirement 1: Onboarding
Description: This is the set of pages which integrates the first time user into the system.
Justification: The user has to be integrated into the system and these sets of pages do that in order for
the user to have an easy time navigating the app for the first time.

Functional requirement 2: Sign up


Description: This is the page for the user to sign up.
Justification: The user should be able to sign up in order to use the application. This is the primary way
of identifying users who frequently make use of the services.

Functional requirement 3: Sign in


Description: This page is for the user to sign in
Justification: The user has to sign in for them to be identified as frequent users of the system and
offered discounts on services based on the users profile

Functional requirement 4: Forgot Password


Description: This page is for the user to retrieve their password if forgotten.
Justification: Users can sometimes forget their login details and this page is required for them to
retrieve their password in order for them to login to their account

Functional requirement 5: Fix My Device


Description: This page is for the user to fill in what sort of service they require.
Justification: The user has to specify what sort of service is required of us before any sort of service or
transaction is carried out.

Functional requirement 6: Cart


Description: This is the page which shows the user what services they’ve added to their cart.
Justification: This page is required for users to see all their desired services in one place, in an orderly
manner as well as how much their services would cost.

Functional requirement 7: Payment


Description: This is the page which allows the user to make payment for their selected service.
Justification: This page is required for the user to make payment for their goods and services.

Functional requirement 8: Progress Bar


Description: This is the page which shows the user the progress of their service and their delivery
timeline.
Justification: The user must know how far their service has gone in order to give the user a sense of
security and calmness in the system.

3.5 Non-Functional Requirements


- The system will be accessed through a http protocol, as it will be online.
- Each Request should be processed within 2 minutes.
- Reliability: The system is required to function 24/7, 365 days a year.
- Performance: The system should operate and process information very fast.
- Supportability: Support is provided in-house, 24/7 in the form of a live chat

3.6 UML Diagrams


UML diagrams, also known as Unified Modelling Language diagrams, are diagrams with the
purpose of visually representing a system along with its main actors, roles, actions, artifacts or classes, in
order to better understand, alter, maintain, or document information about the system.
It is a versatile visual language that is used to model a software system.
UML can be used to develop diagrams and provide users, programmers, with ready-to-use, expressive
modeling examples.
There are two primary categories of diagrams: Structure Diagrams and Behavioral Diagrams.

Structure diagrams are further divided into the following:


Class Diagram
Component Diagram
Deployment Diagram
Object Diagram
Package Diagram
Profile Diagram
Composite Structure Diagram

While Behavioral Diagrams are divided into the following:


Use Case Diagram
Activity Diagram
State Machine Diagram
Sequence Diagram
Communication Diagram
Interaction Overview Diagram
Timing Diagram

My work has been designed using Use Case Diagrams and Activity Diagrams.

Below are the activity and use case diagrams of the system

Activity Diagrams visually present a series of actions or flow of control in a system similar to a flowchart
or a data flow diagram.
Use Case diagrams model the behavior of a system and help to capture the requirements of a system.
Use-case diagrams describe the high-level functions and scope of a system. These diagrams also identify
the interactions between the system and its actors.
Figure 1
Below is the Use Case diagram for a general user:

Figure 2
Figure 3
3.7 Conclusion
The application is designed for a users comfort and satisfaction, while obeying covid-19 protocol in a
sector that originally hasn’t made such provision. The entire application is designed to give immediate
feedback to the user, hence the live chat feature rather than just a contact us page, so as to ease the
users mind and breed a certain level of trust between the platform and the users. It makes use of a
compulsory 2-Factor Authentication code when resetting the password and upon logging in, in order to
secure any registered users account as well as a messaging feature built into the app between the
delivery person and the user. It could be argued that the messaging feature would be more useful
between the repair person and the user, however, i believe the messaging feature between the repair
person and the user could serve as a distraction, and also breed miscommunications because the user is
interacting with the platform in charge of the repair people and not the repair people themselves. It's a
clear distinction.

Recommendation

4.0 Solution Design

4.1 Introduction
Anty is a simple system catering to the needs of the general user, the registered user and the repair
person. It's designed as a web-application only which should run fast and efficiently on any computer
with at least 2GB of ram and 100GB of ROM.
I believe that Anty would measure up as a standard application catering to the needs of the world right
now- a digital world. It makes use of digital devices for its functioning and it caters to the proper
functioning of digital devices, however, i believe there may be a difference of opinions of some others
who believe anty is just another application, not really needed but there anyway.
This section will be covering its design as well as its implementation, and will be broken down properly
to ensure that Anty is understood and dissected quasi-perfectly.

4.2 Functional Description


4.2 Wireframes
Wireframes provide the skeletal form of any user interface. It is a practice used by UX designers which
allows them to define and plan the information hierarchy of their design for a website, app, or product.
When designing for the screen you need to know where all the information is going to go in plain black
and white diagrams before building anything with code. Wireframing is also a great way of getting to
know how a user interacts with your interface, through the positioning of buttons and menus on the
diagrams.

Advantages of wireframes include:


Make Changes More Efficiently.
Display the Architecture of Your Site.
Clarify Website Features before You Build Them.
Focus on the User Experience.
Determine Website Responsiveness.
Make Content Development Better.
Save Time and Money

The following are some of the wireframes of the system:

Figure 4
Figure 5
Figure 6

You might also like