User profile

A new customer is requested to register in the site for utilizing the facilities provided. A Valid member can post the report about the services/ equipments of TCL. These reports are available to the agents of the Helpless. The requests which are open will be verified and resolved by the agent.

If the solution to the problem Is acceptable to the customer then they will close It. The unacceptable solution may lead to the modification of the Report where the process can take round trips and get closed at last by the customer. The closed requests will be then deleted by the agent there by removing it from the report collection.

Assumptions & Constraints The system assumes the following: The details provided by the users are correct. The problem type, sub category and the department entered by the user are correct. The customer can view only the Faults created by their own.

The agents can view all the Faults. The remarks updated by the agents are true. User Characteristics users: The Customers of TCL, who have registered in the system are the Users. Users can Create/ View/ update the Profile. They can Create/ View/ Update/ Close the Faults. Agents: The Employees of the TCL, Agents can View/ Update Remarks for all the Open Faults posted.

Agents can delete the closed faults. Modules Module: User Profiles CRUD Operation 1: Creation of a New User Profile. Primary user’s : Customer Primary user action’s : Create a New User Profile (register User). The customers should enter the details required to open an account in this system. The details include : Surname, Date Of Joining, Address, Email, Phone Number, Alternate Phone Number and Password. If the User Name or Email Exist in the Database, the user is informed with the Pop-Up and should be prompted to change the current Surname/ Email details.

After successful insertion an alert should be displayed to the customer tit the user name and User ID generated. Associated users : N. A Input Criteria : 1. User Name – should allow only Alphabets. 2.

Date Of Joining – 3. Address – AN 4. Email -should be a Valid Email ID. 5. Phone Number- should allow only digits and hyphen ( 6. Alternate Phone Number – should allow only digits and hyphen (-).

7. Should contain a digit, lowercase and Uppercase character. Minimum length 8. Maximum length 10. Password – Output or success guarantee : A Pop-Up to show the User ID generated along with User Name.

All the fields in the registration should be cleared.

Data requirements : I Data Element Name I Format I I User_ID I I User_name Should be in I Address I Email I I Contact_Ph I Parch (30) I Daytime Pritchard (100) I Parch (50) I I Contact_Ph_Alt I Description I Unique old generated for User. I To store the name of the User I To store the Date of Joining. I Format. I To store the address of the User TIT store the email id of the user I To store the contact number. I To store the Alternate Contact number. Password.

I I Password I To store the Possible exception/error scenarios : If user ID already exists then a pop up message [pick] LU for Output/ Success: Message Box CRUD Operation 2: Search for a Particular User from the Users Profiles Collection. Primary user’s : Customer. Primary user action’s : View the User Profile. The User can search for the Profile by entering a valid User ID. The entered User ‘d, if exist should display all the details entered while registering. There should be a link to display “Edit User Profile”, if the logged on user id and the Search User old are the same, clicking on this Link must redirect to “Update User Profile” page.

If the current User ID and the Search User ID are not the same, then hide the link “Edit User Profile” . User ID – Unique Identifier. I Unique Identity of the user. Possible exception/error scenarios : The Entered User old if does not exist Prompt the User with the appropriate message. LU requirements : View User Details CRUD Operation 3: Update the User Profile.

Primary user action’s : Update the User Profile. The Update User Profile Page will help the User to modify some of the values entered while registering, except their User ID and Account generated.

Here, the user can modify the Surname and Email, so again check whether the Surname and Email Exist or not. If the Surname or Email exist, prompt the user for new values. F not Exist, then the user can update his profile with the new values. Associated users : N.

A 2. Address – AN 3. Email -should be a Valid Email ID. 5. Alternate Phone Number – should allow only digits and hyphen (-).

Data requirements : Data Element Name I To store the name of the User. Take only alphabets. I Address address of the User store the Valid email id of the user I To store the contact number I To store the Alternate Contact number.

I To Possible exception/error scenarios : The user can modify the Surname and Email, before submitting the page check whether the Surname and Email Exist. If Exist, prompt the user to use the new values.

LU requirements : Update User Details Modules: Fault Creation. CRUD Operation 1: Create new Faults. Primary user’s : Customers Primary user action’s : Create a New Fault. The Customer should verify the system that their details exist in the database for the further enquiries, so Enter the customer is asked to enter the valid Phone Number to get the User Details.

If the Phone number exists the customer details are then displayed in the User details Pane along with the Options to move to “Raise a Fault” and View the Faults”. If the Customer moves on to the “Raise a Fault” page, then they should enter the Problem Type, Sub category type, Assigned department and remarks regarding the Fault and can submit the details.

A successful insertion will lead to the Successful insertion page, where the customer can see the Fault ID and the Account generated while creating the User Profile for the new fault created.

And the movie’s Faults” page, will list all the Faults submitted by the current User. If the phone number does not exist, the customer can be prompted with an error in the entry and can ask to enter the details that are required. Problem Type : Select one among the Problem Type: Line Issue, Service Issue, Equipment Issue and Billing Issue. Sub category : Line Issue – Noisy Line, Call Interference, Line damage. : Service Issue – Major service outage at Provider.

Equipment Issue – Noisy, No Dial Tone, Damaged Equipment. : Issue – Billing paid not updated, Wrong Billing. Department Type: Infrastructure, Billing.

Remarks : User’s Remark. Billing Output or success guarantee : Show View Fault Page, only with Open Status for the customers. Data requirements : I I Problem_Type I Sub_Category I I Department I I Remarks I Status 0-> Close.

I Parch (200) I Bit | Open TIT store the main Problem type. I To store the Sub category. I To store the Department. I To store the Remarks. M; Possible exception/error scenarios : If the Problem type is assigned to the wrong department prompt the user with an alert. LU requirements:: Create New Fault CRUD Operation 2: View Faults.

Primary user action’s : View Faults created by own.

If the User have already raised any Fault , then he/ she should be able to view all the Faults and the corresponding details as well. In the View Faults page, there is a provision to enter the User old and Select the Status, these options will not be available to the customers. The customers can view only the Account, Phone number and the relevant details of the Fault created by the customer. The details of each Fault should be shown in the View Fault Detail page.

Here, the customer should be able to modify the Fault details or Close the status of the Fault which makes the visibility of the Fault to false.

By making the status to close makes the fault ready to delete from the Fault Collection(This is done current user then prompt the customer that “No Faults Found. “, in this page. Fault ‘d: Select any one among the List of the Faults. Output or success guarantee : Show View Faults Page.

The Faults having the status as Open are only seen here. Output or success guarantee : Show View Fault Page, for the selection of view. Data requirements : I Fault_old I To show the Fault details. I-Jell requirements: View Faults LU Output/ Success: View Fault Detail CRUD Operation 3: Update a Fault. Primary user action’s : The customer can modify the Open Fault.

The customer can choose one among the Faults displayed in the View Faults Page. This selection should lead them to the View Fault Details page, where they can Either Update or Close the Fault. Here, the customers can either choose Update or Close the Fault. If the customer selects the Update, it should lead to the Update Fault Page, where the customer can view the current values for the problem type, sub category type, Department and remarks along with the submit button. After the desired modifications the customer can submit the details to make the changes and thereby can seek the remedy from the helpless with the updated values.

If the customer selects the close, it should change the status of the fault as false.

This status change makes the fault invisible to the customer from next attempt onwards. Later, when the Other user, Agent views all the Fault, the closed faults are made available to delete. ) Output or success guarantee : Show View Faults Page with Open Status. Data I To store the modified Problem type. Modified Sub category. I To store the modified Department.

I Parch (200) Possible exception/error scenarios : Alert for the faults that does not exist. II requirements: Update Fault Detail CRUD Operation 4: Close a Fault.

Primary user action’s : Closing a Fault. The customer can choose the Close, from the View Fault Details page and thus makes it hide from next attempt onwards. This ensures that the customer does not have any more issues with the Service/ Equipment provided.

Associated users : N. A Status :Make the Status Open to Close. Output or success guarantee : Show View Faults Page. (This will not contain the Closed Faults. ) Data requirements : Possible exception/error scenarios : Alert the customer, if there doesn’t exist any fault now. LU requirements: Close Fault Modules: Fault Management CRUD Operation 1: View the Faults.

Primary user’s : Agents Primary user action’s : View Faults according to the Status(Open, Closed or Both) of he Customers according to the selection of the Status(This status selection in the View Faults page is only available to the Agent, not to the Customer). The agent can also specify the User ID to view the Faults submitted by a single Customer(This User ID facility should only be available to the Agent, not to the customer. See the assumptions & constraints). The agent can then view the Faults defined in connection with the selection of the status. In the faults listing, the agent is provided with some more options.

All the Open faults are available with View and Update option and All he Closed faults are available with the View and Delete option.

For the Agent the View Option will help them to View the details of the Faults Listed in the View Fault Details page. Associated users N. A Input Criteria- User old – Enter the User old to View The Fault. Filter by Status – Status can be Open/ Closed/ Both. Output or success guarantee: I I User_old I Parch (20) TIT search the Faults created by User.

I To specify Open/Closed Possible exception/error scenarios : User does not exist. LU requirements : View Faults. CRUD Operation 2 : Update the Fault.

Primary user action’s : Update the Fault. The customer after selecting the View of the Fault detail, moves on to the View Fault details page where there is an Update button(The Close Fault button should be invisible for an agent, because the agent doesn’t have the option to close the fault. ).

Then the agent should be redirected to the Update Fault page, where the agent updates only the remark and Submits it. This new Modification will be reflected to the the view Faults page for the customers as well. (This remark acts like the remedy to the Fault raised by the Customer. ) . Associated users N.

A Remarks : Agent’s Remark.

Output or success guarantee: Show the Screen of the View Faults Page. Data LU requirements: Update Fault Details CRUD Operation 3: Fault Deletion. Primary user action’s :Delete the Closed Faults. All the Faults which are closed by the customers should be listed to the agent in the View Faults Page by selecting either the status as Closed/ Both.