Web base personal counselling system. design document, Lab Reports of Web Application Development

Download Web base personal counselling system. design document and more Lab Reports Web Application Development in PDF only on Docsity!

Web Based Personal Counseling

System (PCS)

Software Requirements Specification

Version 1. Group Id: S20027E71A Supervisor Name : Qaiser Shabbir

Table of Contents

1. Introduction of Design Document

2. Entity Relationship Diagram (ERD)

3. Sequence Diagrams

4. Architecture Design Diagram

5. Class Diagram
6. Database Design
7. Interface Design
8. Test Cases

1. Introduction of Design Document This section contains all the necessary preparation that was required in order to make the implementation phase of this development as easy and efficient as possible. The section was broken down into a number of areas. The first discussed potential designs for data storage. This involved an analysis into normalization and how it would be implemented to improve data manipulation. The second section involved UML diagrams to identify all the use cases required for the final solution. ERD diagrams were produced for these use cases to assist understanding and thus provide a guide for implementing these features into the new system. The following section further discusses usability issues, followed by a look at and how counter measures could be implemented into the system. The system was analyzed and designed before implementation began. In this section, Entity Relationship Diagram, Sequence diagrams, Architecture Design Diagram, Class Diagram, Database Design, Interface Design and Test Cases webpage diagrams are described in details.

Specify the number of relationship is instance that an entity can participate in.

3. Sequence Diagrams Admin Sequence Diagram Counsellor Sequence Diagram

User Sequence Diagram Reading a sequence diagram is very simple. Start at the top left corner with the "driver" class instance that starts the sequence. Then follow each message down the diagram. Remember: Even though the example sequence diagram in Figure 4 shows a return message for each sent message, this is optional. Basic The main purpose of a sequence diagram is to define event sequences that result in some desired outcome. The focus is less on messages themselves and more on the order in which messages occur;

5. Class Diagram Admin Class Diagram

Counsellor Class Diagram User Class Diagram

Messages are arrows that represent communication between objects. Use half-arrowed lines to represent asynchronous messages. Asynchronous messages are sent from an object that will not wait for a response from the receiver before continuing its tasks.

6. Database Design 7. Interface Design Home Page

Form Login Page

T/C Priority: “ Medium” High ”Low” Preconditions: The User create a Account using email. SN Action Inputs Expected^ Actual^ Test^ Test^ Test Outcome Output Applicatio n result comments 1 Create Account @gmail.com Create Account Create Account PC PASS

[

User 27/02/ Successful 2 Enter Create Account Create Account PC PASS User Email @mail.com Successful Successful 27/02/ Password: **** Create Account Successful T/C ID : 2 T/C Name: Login T/C Priority: “ Medium” High ”Low” Preconditions: The User/Admin login into the System.

SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 Login @gmail.com Login Login PC PASS User/Admin 27/02/ Successful 2 Enter Login Login PC PASS User/Admin Email @mail.com Successful Successful

Password: **** Login Successful T/C ID : 3 T/C Name: Induct Counsellor T/C Priority: “ Medium” High ”Low” Preconditions: The Admin can induct fresh Counsellor SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 induct fresh Counsellor induct fresh Counsellor induct fresh Counsellor induct fresh Counsellor PC PASS User 27/03/ Successful 2 Enter induct fresh Counsellor induct fresh Counsellor PC PASS User Email @mail.com Successful Successful

Password: **** Successful T/C ID : 4 T/C Name: Add Question T/C Priority: “ Medium” High ”Low”

T/C Name: View Profile T/C Priority: “ Medium” High ”Low” Preconditions: The User can view Profile SN Action Inputs Expected^ Actual^ Test^ Test^ Test Outcome Output Applicatio n result comments 1 view Profile view Profile view Profile view Profile PC PASS User 27/04/ Successful 2 Enter view Profile view Profile PC PASS User Email @mail.com Successful Successful

Password: **** Successful T/C ID : 7 T/C Name: View Valid Creditentials T/C Priority: “ Medium” High ”Low” Preconditions: The user can access valid creditentials. SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 access valid creditentials access valid creditentials access valid creditential s access valid creditential s PC PASS User 27/04/ Successful 2 Enter access valid creditential a access valid creditential s PC PASS User Email @mail.com Successful Successful

Password: **** Successful

T/C ID : 8

T/C Name User can take test T/C Priority: “ Medium” High ”Low” Preconditions: The User can take test. SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 User can take test. User can take test. User can take test. User can take test. PC PASS User 27/05/ Successful 2 Enter User can take test. User can take test. PC PASS User Email @mail.com Successful Successful

Password: **** Successful T/C ID : 9 T/C Name: User can view own score history T/C Priority: “ Medium” High ”Low” Preconditions: User can view own score history. SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 View score history View score history View score history View score history PC PASS User 27/06/ Successful 2 Enter View score history View score history PC PASS User Email @mail.com Successful Successful

Password: **** Successful