Course: Requirement Engineering

$($Purpose

The purpose of this User Requirements Document $($URD$)$ is to articulate the specific needs and expectations for the development of a digital system to address the challenges faced by Azim AIC SDN$.$ BHD$.,$ a service$-$based company providing car detailing and cleaning services.Currently their reliance on manual processes on various aspects of car wash shops, including business records, appointment scheduling, payment processing and inventory tracking using paper$-$based systems. The goal is to streamline operations and enhance customer experiences by developing a digital solution that addresses these challenges. The primary aim is to replace the conventional method of handling services, which involves repetitive verbal communication and manual booking, with a digital solution. With that the system is being developed and aims to have a booking system, customer portal which contain service details, feedback and finance management with recording all of the sales which can generate reports. In essence, this URD serves as a guiding document for software development, ensuring that the resulting system aligns closely with the company's requirements and objectives. The online system build would provide a web$-$based application that could be utilized for this business and benefit the clients.

The intended audience for this URD includes stakeholders involved in the development process. This encompasses end$-$users who will interact with the digital system, software developers responsible for its creation, project managers overseeing the development, quality assurance teams conducting testing, and other relevant decision$-$makers within the organization. Furthermore, Azim AIC SDN$.$ BHD$.$ Company manager Mr$.$ Sathia also participated in an interview to gather requirements of the system and also become tester for the system to be developed and it also involved several people to gather requirements and their interest about the system that was to be developed. All their needs will record and document to provide a common understanding of user requirements for all stakeholders involved.$)$

Question:

I was in the final stages of my project related to the development of the digital system for Azim AIC SDN$.$ BHD$.$ Your expertise in UML diagramming is crucial for the project's completion.

Could you please assist by creating $($DRAWING$)$ the following UML diagrams based on the provided project details:

Activity Diagram of "Book the Service" $($Section $2\mathrm{.}3\mathrm{.}1)$

Sequence Diagram of "Book the Service" $($Section $2\mathrm{.}3\mathrm{.}2)$

Activity Diagram of "Feedback" $($Section $2\mathrm{.}4\mathrm{.}1)$

Sequence Diagram of "Feedback" $($Section $2\mathrm{.}4\mathrm{.}2)$

For use case specification should be on related requirement area:

REQ $100-$ Login$/$Register

FR$01-01$ The system shall provide a login form to users.

FR$01-02$ The system shall allow users to register for a new account.

FR$01-03$ The system shall authenticate user credentials during login$.$

FR$01-03$ The system shall save user details during the registration process.

ER$01-03$ The system shall handle exceptions during login and registration.

CR$01-01$ The system shall enforce password complexity requirements.

CR$01-02$ The system shall not allow registration with an existing username.

Note that: Simple say admin need to create vehicle first and choose isEstimate or not and after that on the service create have dropdown to select which vehicle that service for and then the duration will depend on the vehicle isEstimate. if it isEstimate, then the system will give duration on number format if it set as $2$ means when user book time $9\mathrm{.}00$ a$.$m $,$ so the system will book that time $9$ plus with duration which $2(1-30$ minutes$),$ so it book for $9-10.$ on that time no one can book. But if that vehicle dont have isEstimate, then when book they wont plus anything and can book anytime no restriction. PLEASE DRAW THE DIAGRAMS!