Systems Development Project
Systems Development Project
ASSIGNMENT REPORT
Lecturer :
1
Table of Contents
1. Introduction...................................................................................................................................1
2. Functional requirements...............................................................................................................2
3. Non-Functional requirements.......................................................................................................3
4. Fact finding techniques..................................................................................................................4
5. Flow chart diagram…………………………………………………………………………………………………………………5
6. References.....................................................................................................................................6
2
1. Introduction:
3
2. Functional Requirements:
1. Customer Registration:
Users should be able to create accounts with personal information.
The system must verify and store customer details securely.
2. Service Request Submission:
Customers should be able to submit service requests for their laptops.
The system must capture details such as laptop model, issue
description, and warranty status.
3. Service Tracking:
Customers should be able to track the status of their service requests.
The system must update the service status in real-time.
4. Diagnosis and Repair:
Service technicians should have access to tools for diagnosing laptop
issues.
The system must support the documentation of diagnostic results and
repairs performed.
5. Service Appointment Scheduling:
Customers should be able to schedule appointments for in-person
service.
The system must display available time slots and confirm
appointments.
6. Inventory Management:
The system must keep track of available spare parts and repair
components.
Technicians should be able to request new parts when needed.
7. Communication:
The system should facilitate communication between customers and
service technicians.
Automated notifications should inform customers about service
progress and completion.
8. Customer Feedback:
After service completion, customers should be able to provide
feedback on the quality of service.
The system must store and analyze customer feedback.
9. Billing and Payment:
The system should generate invoices based on the services provided.
Customers should be able to make payments online or in-person.
10. Reporting:
4
The system should generate reports on service trends, technician
performance, and inventory levels.
Administrators should have access to comprehensive analytics for
decision-ma
Non-Functional Requirements:
1. Performance:
The system should respond to user interactions within 3 seconds.
It must support a minimum of 50 service requests concurrently.
2. Security:
Customer data, especially personal and diagnostic information, should
be encrypted.
The system must have role-based access control to ensure data privacy.
3. Scalability:
The system should handle a 20% increase in service requests without
degradation in performance.
It should be designed to scale as the number of customers and
technicians grows.
4. Reliability:
The system should have a 99.5% uptime.
Regular backups must be conducted to prevent data loss in case of
system failure.
5. Usability:
The user interface should be intuitive for both customers and service
technicians.
Training requirements for technicians should be minimal.
5
4. Fact Finding techniques:
Interviews:
Description: Interviews usually involve direct communication
between system analysts and individuals who have knowledge
about the system and its components. This includes stakeholders,
end-users, managers, and technical staff.
“does this system have key features?”
“How does your system communicate with customers?”
Document Analysis:
Description: Document analysis involves reviewing existing
documents, reports, manuals, and other written materials associated
with the system. This technique helps in understanding the state of
the system, its processes, and any documentation that may already
exist.
Identifying requirements:
document analysis allows us to identify requirements for our
system based off older similar systems
Gathering documents:
to analyse the documents we would need to gather any
documents that is related to servicing systems to give us flaws
we can improve upon
6
Flow chart diagram:
7
References:
"ASUSTek Computer Inc. Annual Report 2022" (PDF). ASUSTek. 11 April 2023. Archived (PDF) from the
original on 20 June
"Asus Story – Profile, CEO, Founder, History | Computer Hardware Electronics Companies |
SuccessStory". successstory.com. Archived
www.wibas.com. (n.d.). Service System Development (SSD) (CMMI-SVC). [online] Available at:
https://www.wibas.com/cmmi/service-system-development-ssd-cmmi-svc#:~:text=The%20service%20system
%20development%20process%20is%20driven%20by%20service%20and [Accessed 15 Feb. 2024].
Official Support | ASUS Malaysia. (n.d.). Official Support | ASUS Malaysia. [online] Available at:
https://www.asus.com/my/support/.