The document presented an auto repair and invoice system project. It summarized the key features for customers, customer service representatives, and mechanics. It covered requirement gathering and process modeling including data flow diagrams and an entity relationship diagram. It also discussed forms, reports, dialog sequences, and interface design considerations. The project was presented by a student at the University of Houston - Clear Lake for their MS in Management Information Systems degree.

1. System Analysis and Design
Project Presentation 2020
Auto repair and invoice system
Project Presentation By
Hinal P. Patel from
M.S. In Management Information Systems
For Academic Term at
University of Houston – Clear Lake
Spring, 2020

2. Users
We have features for every step of the way
Customer
Customer
service
Representative
Mechanic &
Manager

3. Part I – Requirement
Gathering & Process
Model
Plan, Analyze, Design

4. • Service representative Portal
• Customer vehicle check-in Portal
• IT Knowledge with auto
knowledge staff Base
• Mechanic log portal
• Customer Support Management
• API Integration
• Business Rules
• Customer Survey
Software Requirements Specification
SRS defines how an application will interact with system
hardware, other programs & human user in a wide variety of
real world situation.

5. Dataflowdiagram Process Model
Context diagram
This identifies the flows of information
between the system and external entities. The
entire software system is shown as a single
process.

6. Data flow diagram Level 0

7. Data flow diagram Level 1- Customer
login and invoice generation process

8. Data flow diagram Level 1 – Vehicle repair log
process

9. Data flow diagram Level 1- parts
replace/purchase process

10. .
A data-flow diagram (DFD) is a
way of representing a flow of
a data of a process or a system
(usually an information system).
The DFD also provides
information about the outputs
and inputs of each entity and the
process itself. A data-flow
diagram has no control flow,
there are no decision rules and
no loops.

11. PART II : ENTITY-
RELATIONSHIP DIAGRAM

12. Entities:
• customers,
• vehicles,
• mechanics,
• manager
• customer service assistants,
• reservation
• salaries
• invoices
• parts
• customer records.
• Vehicle insurance (weak entity)

13. Relationship between entity
• manager assigns mechanics
• mechanics service vehicles
• mechanics order/replace parts
• customer service representative
manage customer records
• mechanics receive salaries
• customer service representative
receive salaries
• customer service representative help
customers
• customers pay invoices.
• Customer login software

14. Cardinality (maximum number of instances,
either “many” or “one)
modality (minimum number of instances,
either “one” or “zero”) of the relationships:
• one mechanic services many vehicles
• one customer service representative manages many
customer records
• one mechanic receives one salary
• one customer service representative helps many
customers
• one customer pays one invoice.

15. Define just entities and relationship first

16. Define entities, relationship, cardinality, attributes in
crow foot diagram

17. Entities, Relationship, Attributes
An entity relationship
diagram (ERD) shows the
relationships of entity sets
stored in a database.
An entity in this context is
an object, a component of
data. An entity set is a
collection of similar
entities. These entities can
have attributes that define
its properties.
By defining the entities,
their attributes, and
showing the relationships
between them, an ER
diagram illustrates the
logical structure of
databases.
ER diagrams are used to
sketch out the design of a
database.

18. Forms
Report
Dialogs
Interface Designing

19. A BUSINESS DOCUMENT THAT CONTAINS SOME PREDEFINED DATA AND MAY
INCLUDE SOME AREAS WHERE ADDITIONAL DATA ARE TO BE FILLED IN
AN INSTANCE OF A FORM IS TYPICALLY BASED ON ONE DATABASE RECORD.
Login form
Forms

20. Registration form

21. Appointment Form

23. Invoice Report

24. Work order Report

25. Vehicle inspection Report

26. DialogSequenceDiagram

27. Interface layout design

28. ?
Thank you.
Feel free to ask any question