COIT20248: Information System Analysis and Design Report for RME

This report presents the information system design for Repair-Made-Easy (RME), a computer repair company. The assignment addresses the company's needs by analyzing its revenue and expenditure cycles. It includes the identification of critical use cases, the creation of a context diagram, and a level-0 data flow diagram (DFD) illustrating business processes. The report also features an entity-relationship diagram (ERD) showing data entities and their relationships, along with identified data elements. A CRUD (Create, Read, Update, Delete) diagram details system operations, and a website prototype demonstrates the system's design. The report concludes with individual group member contributions and references, providing a complete overview of the system's analysis and design.

INFORMATION SYSTEM:
REPAIR-MADE EASY
Name of the Student
Name of the University
Author Note

Introduction: Case-Study
2
John is the owner of Repair-Made-Easy, which is a
computer repairing company. The company is having
problems regarding the computers services and parts
management. As the staffs manages all the data and
processes of the system manually, John is thinking to
develop an effective information system. The business
requirements of the current system helped to develop the
system design and implementation.

Information system
3
 An information system is a computer based system, which
includes people, information technology and business
processes.
 Information system helps the business enterprises or an
individuals to collect, store, process and analyze the data
(Romiszowski 2016).
 For the Repair-Made-Easy company, the system will help
in managing the company’s expenditure and revenue cycle
data.

Expenditure Cycle
4
 The expenditure cycle describes the
inventory related purchases of RME.
The whole process includes order
placing, payment, shipment and 15
different suppliers for the company.
 The cycle is represented with the help
of level 0 Data-Flow diagram. The
system will manage company’s all
operational requirement related data
(Olayan et al. 2013).

Revenue Cycle
5
 On other hand, Revenue cycle is
describes the main business process
of the company. The cycle includes
the repairing services, appointments,
purchasing of parts, payment, pick
up with all the details.
 The revenue cycle is also
represented using level 0 DFD
where the system’s business process
and data management is shown.

Use-case Identification
6
A use-case is a systems process that describes a user
interaction to the system for achieving the system’s
particular goals (Salado and Nilchiani 2013). the
identification of the use cases are done with the help of
business process of RME company. Its shows the
interaction of the system with different type of users. It also
defines the data requirements for the system development
that includes the data attributes, types and ranges.

Logical Design: Database
The logical design of the
database represents the
entities and attributes used in
the system with the
relationship between them by
a ER diagram (Thalheim 2013).
The RME database stores the
information of their
customers, orders, services,
parts and staffs. The stored
data will increase the
efficiency in operating the
business.

Data Description
The Data description
describes the attributes of
the tables. It shows the
attribute’s data type,
name, range, size and
keys. The key attributes
are generally defined as
foreign and primary keys
(Abadi et al. 2016). The
referenced table of the
foreign key attribute is
also defined in data
description.

Crud Matrix
9
The CRUD matrix (create,
read, update and delete)
shows the SQL operations
of a system in a tabular
form. It is found to be a best
techniques to identify which
table is interacting in a
particular operation of a
system (Howey 2013). The
interaction is done using
website.

Place your screenshot here
10
Prototyping
Prototyping is a basic version of
the proposed system with basic
operation that allows the system
to run properly. One of the
benefits of using prototyping is
that user interaction gets easy
after the system deployment
(Rivero and Rossi 2013). A
prototype of RME system is
developed using software named
Balsamiq.

11
Conclusion
System requirements is a very first and vital phase in real
meanings of system development. System requirements is
identified and analysed according to the business processes that
helped in designing the system. The designing phase gives a basic
and logical structure to the system to accomplish its goals. Hence,
it can be said that implementation of the information system is a
long process and improves business process of any organisation.

References
Abadi, D., Bajda-Pawlikowski, K., Abouzied, A. and Silberschatz, A., Yale University,
2016. Processing of data using a database system in communication with a data
processing framework. U.S. Patent 9,495,427.
Howey, R., OptumInsight Inc, 2013. Apparatus, system, and method for identifying
redundancy and consolidation opportunities in databases and application systems. U.S.
Patent 8,364,651.
Olayan, N., Patu, V., Matsuno, Y. and Yamamoto, S., 2013, November. A dependability
assurance method based on Data Flow Diagram (DFD). In 2013 European Modelling
Symposium (pp. 113-118). IEEE.
Rivero, J.M. and Rossi, G., 2013, July. MockupDD: Facilitating agile support for
model-driven web engineering. In International Conference on Web Engineering (pp.
325-329). Springer, Cham.
12

Romiszowski, A.J., 2016. Designing instructional systems: Decision making in
course planning and curriculum design. Routledge.
Salado, A. and Nilchiani, R., 2013. Contextual-and behavioral-centric stakeholder
identification. Procedia Computer Science, 16, pp.908-917.\
Thalheim, B., 2013. Entity-relationship modeling: foundations of database
technology. Springer Science & Business Media.
13
References

14
THANKS!
Any
questions?