We are here with you hands in hands to facilitate your learning & don't appreciate the idea of copying or replicating solutions. Read More>>

Looking For Something at vustudents.ning.com? Click Here to Search

www.bit.ly/vucodes

+ Link For Assignments, GDBs & Online Quizzes Solution

www.bit.ly/papersvu

+ Link For Past Papers, Solved MCQs, Short Notes & More

CS706 Assignment No 02 Solution & Discussion Due Date: Dec 07, 2016

CS706 - Software Quality Assurance Assignment No. 2 Solution Fall 2016 Due Date: Dec 07, 2016

 

                                                                       Assignment No. 02


                                     SEMESTER Fall 2016
                

                  CS706 – Software Quality Assurance

 

                                                                                              Due Date: December 07, 2016

 

Instructions to Solve Assignments

 

The purpose of assignments is provide you with hands on practice. It is expected that students will solve the assignments themselves. Following rules will apply during the evaluation of assignment.

 

  • Cheating from any source will result in zero marks in the assignment.
    • Any student found cheating in any two of the assignments submitted will be awarded "F" grade in the course.
    • In case of question No. 03 direct copy and paste from the research paper will be awarded zero marks.
    • No assignment after due date will be accepted.

 

 

 

 

 

 

 

Question No. 1

Suppose you are part of a review team, your role is that of a “Reviewer” and the work product to review is a software requirement specification (given with assignment folder). The document was given to you one week prior to review meeting and now you need to make notes of defects/deficiencies that you will discuss in the review meeting. Write down list of at least five points (defects/deficiencies) that you think, you need to discuss in upcoming review meeting.

 

Question No. 2

Please read the paper titled “Achieving Quality in Open Source Software” given with this assignment folder and answer the following:

  1. How the approaches to deliver high quality OSS differ from those of closed source software?

 

  1. Write down summary of paper in your own words.

 

=============================== Ended==============================

For any query about the assignment, contact at CS706@vu.edu.pk

GOOD LUCK

 

 

 

Software Requirement Specification

 

Air-Ticket Reservation System

 

 

 

 

 

 

 

 

 

 

 

 

 

Document No.

SRS_ARS_1

Version No.

1.0

Created on:

01-Nov-16

Last modified on:

30-Nov-16

Last modified by:

X,Y,Z

 

Section 1: Introduction

 

1.1            Vision Statement:

 

 

1.1.1        Software Purpose

 

The main purpose of this software is to reduce the manual errors involved in the airline reservation process and make it convenient for the customers to book the flights as when they require such that they can utilize this software to make reservations, modify reservations or cancel a particular reservation.

 

1.1.2        Software Scope

 

This software provides options for passengers to view and search different flights available with different timings for a particular date and provides the administrators with the facility to manage the root schedule (adding, editing, canceling and viewing routs), manage reservations (booking, modifying, canceling and viewing) and to manage the staff.

 

1.1.3        Software Perspective

 

The Air line reservation system software is an independent application. It is a self-contained product, designed for Local Area Network (LAN) with easy-to-use, interactive, and intuitive graphical interfaces. The ARS will also provide an interactive GUI, on the Linux based KIOSK for the general customers and administrators of the system. Separate interface will be provided for passengers and administrators. General customers will be able to use the interface within the office premises to view, search and print the flight schedules, see flash news and news alert. The administrators on the other hand will be able to use the given interface to issue, reserve and edit the tickets, and schedule routs. However, all the information will be stored on a central database and all the both the client side and administrator will use this information to perform the permitted activities. Also note that access to administrator interface will be role based, while the client side (passenger interface) will not require any authentication and will have open interface.

 

Passenger

 

 

 

1.2      Document conventions and definitions:

 

ARS - Airline Reservation System

LAN - Local Area Network

GUI  - Graphical User Interface

OS    - Operating System

 

1.3      Intended audience and reading suggestions

 

The intended audience for this document includes the designer team and customer supervisory committee approved by the client organization to monitor and interact with developing organization regarding software development.

 

 

Section 2: Overall description

 

2.1            User characteristics

 

No technical experience is required basic knowledge of handling system is sufficient.

Users will use the system at three levels

1) Super admins

2) Sub admins

3) Passengers

Super admins will have full rights of the system, including all the sensitive tasks e.g. add, edit route schedule.

Sub admins will have full rights of passenger reservation including reserving, editing, canceling tickets.

Passengers, on the other hand will be given separate interface with access to display and search route schedules, available seats and print the schedule.

 

2.2            Operating environment

 

ARS will be a client/server based system, running on LAN. Both clients and servers will be linux based system; however the client systems for passengers will be KIOSK based systems for the sake of security.

Entire application along with database will be installed on the central server and clients system will be able to perform the intended functionality through GUI interfaces provided on client machines.

 

 

2.3            Design and implementation constraints

 

 

1) System will be developed using Java and MySql

2) Systems for passengers will be KIOSK based systems

3) Tickets will not be cancelled before the 4hrs of scheduled flight time.

4) It must be a Client/Server based system

5) Requires 256 MB on-board memory.

6) Based completely on Unix based functionality platform.

7) The software should be inaccessible to unauthorized users.

8) The system should support multiple users at the same time.

9) Tickets will be issued, edited and cancelled only by admin.

 

 

 

 

 

 

2.4            Assumptions and dependencies

 

It is assumed that passengers first see the flight schedules, fare details from the client machines dedicated for the passengers, and any breaking news e.g. modification of flight timing etc. will be immediately added to the system by admin, and will immediately be visible through passenger interface.

 

Section 3: External interface requirements

 

3.1            Hardware Interfaces

 

The system must basically support certain input and output devices. Their descriptions are as follows.

 

Name of Item

Description of Purpose

Source of Input/

Description of output

Key board

To accept data for reservation of ticket, for entering flight schedules etc.

Source of Input

Printer

To print the flight schedules for passengers, print tickets etc.

Destination of Output

 

Internet may be available to admin users on their machines but ARS will have no interaction with internet except to send mails specified in section 3.3. All the communication with in the systems will be encrypted using shared key.

 

3.2            Software Interfaces

 

Not applicable since the product under considerations is an independent one.

 

3.3            Communication Interfaces

 

Every client system connected through LAN establishes a communication only with the server and not with any client system. However, after reservation, modification and cancellation of ticket the system will send an email to the concerned person (to whom the ticket is issued). Similarly, after modification of flight schedule, the system will send emails to all the persons who have reserved tickets for that flight, and system will also display an immediate alert at all the interfaces (interfaces for admin, for passengers etc).

 

 

Section 4: System features

 

4.1 The ability of the software is to provide the details of the flights available.

 

PURPOSE

 

The purpose of this is to enable the passenger to view the different flights available so as to make it convenient for him to make a reservation. System will ask the passenger to enter the source and destination, after user enters both source and destination the system will search the direct and indirect flights available between two locations, immediately system will show the schedule of coming two weeks in table format. By selecting any of the routes with help of mouse, the system will display the list of reserved and available seats of all categories in the selected flight. Passenger will select one or more seats and the selected seats will be highlighted.

 

4.2 The ability of software to print the selected information (in section 4.1)

 

PRUPOSE

 

Purpose of this feature is to enable the passenger to take hardcopy of the routs/tickets available or selected, so that it may help passenger to use this information later e.g. to give it at booking counter for reservation etc.

 

4.3 The ability to reserve the ticket for passenger.

 

PURPOSE

 

The purpose of this feature is to reserve the ticket for the passenger. After the passenger has selected the rout and seats from the passenger machine, he/she will give the printed information to the booking counter and the operator at the counter will reserve the booking for the passenger by entering the passenger details etc. The ticket will then be printed and will be issued to the passenger. An immediate email notification will also be sent to the passenger at his email address.

 

4.4 The ability to edit/cancel reserved the ticket for passenger.

 

PURPOSE

 

The purpose of this feature is to edit or cancel the already reserved ticket. For this purpose the passenger will provide the ticket number, the admin at the counter, will enter the ticket number and all the details about the ticket will be displayed on the screen in edit mode. After modification made by the admin, the changes will be updated and email will be sent to the passenger, regarding changes. However, in case if the passenger wants to select different flight, the system will first confirm that either the newly selected flight along with the selected seats is available or not. If yes the modification will be made otherwise denial message will be displayed.

 

4.5 The ability to enter flight schedule

 

PURPOSE

 

The purpose of this feature is to enable admin to enter flight schedule for one month. The admin will enter flight name, date, time, source/destinations, and crew members. Initially for each flight entered, all the seats will be available by default. As soon as the any flight is scheduled, its details will immediately be available for the passengers at client PC’s.

 

4.6 The ability to Edit, delete flight

 

PURPOSE

 

Purpose of this feature is to edit or delete a flight once it is scheduled. To edit a flight, admin will enter the flight number and the data about the flight will be displayed in edit mode. Admin will be able to change flight schedule including time and crew members. How ever for any change the modifications made will immediately be visible to the client machines, and notification emails will be sent to all the passengers having reservation in that flight.

For the purpose to delete a flight, the flight can not be deleted once 15% of seats are reserved.

 

4.7 view periodic flights status

 

PURPOSE

 

This feature will enable the admin to view the flights schedule between two dates. For each flight the admin should be able to view the flight date, crew members and reservation status of that flight.

 

4.8 Add, Edit, Delete user

 

PURPOSE

 

The purpose of this feature is to manage the users. This admin must be able to add new user along with defining his roles, editing already existing users or deleting the employee that has left.

This feature will only be available to super admin

Section 5: Use Case Model

5.1 Use case diagram

 

5.2. Use Case Description

 

 

Use Case Name: Add Flight

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to enter the flight schedule.

 

Precondition:  Admin is already login

 

Post-Condition: Flight schedule is entered

 

Extends: none

 

Uses: None

 

Normal Course of Events:

 

 

User

System

1

 

System displays the admin home page.

2

Admin clicks the add flight link

 

3

 

System displays the input screen

4

Admin enters flight data and clicks submit button

 

5

 

System saves the flight and displays the success message

 

Alternative Path:

At step (4) admin does not click the “submit” button but clicks the cancel button, system displays the home page again.

 

Exception:

At any stage server is disconnected, system displays “Server not connected” message.

 

Assumption: None

 

 

 

Use Case Name: Edit Flight

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to edit already scheduled flight.

 

Precondition:  Flight is already entered in database

 

Post-Condition: Flight data is updated

 

Extends: none

 

Uses: SendEmail

 

Normal Course of Events:

 

User

System

1

On home page admin clicks the “Edit/Delete flight” button

 

2

 

System displays the list of future scheduled flights in table format.

3

Admin double clicks on the flight he/she want to edit

 

4

 

System displays the flight data in edit mode

5

Admin modifies the data and clicks the “Update” button

 

6

 

System sends the mail to all the passengers having reservation for that flight, and displays the success message.

 

Alternative Path:

At step (3) admin does not double click on flight but clicks the cancel button, system displays the home page again.

At step (5) admin does not click the update button but clicks cancel button, flight will not be updated, and system displays the home page.

Exception: At any stage server is disconnected, system displays “Server not connected” message. At step (6) mail sending fails, system displays message, “mail sending failed”

Assumption: None

 

 

Use Case Name: Delete Flight

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to delete already scheduled flight.

 

Precondition:  Flight is already entered in database

 

Post-Condition: Flight data is deleted

 

Extends: none

 

Uses: SendEmail

 

Normal Course of Events:

 

 

User

System

1

On home page admin clicks the “Edit/Delete flight” button

 

2

 

System displays the list of future scheduled flights in table format.

3

Admin double clicks on the flight he/she want to delete

 

4

 

System displays the flight data in edit mode

5

Admin clicks the “delete” button at the end of flight data

 

 

 

System deletes flights, sends the mail to all the passengers having reservation for that flight, and displays the success message.

 

Alternative Path:

At step (3) admin does not double click on flight but clicks the cancel button, system displays the home page again.

At step (5) admin does not click the delete button but clicks cancel button, flight will not be updated, and system displays the home page.

Exception: At any stage server is disconnected, system displays “Server not connected” message. At step (6) mail sending fails, system displays message, “mail sending failed”

Assumption: None

 

 

Use Case Name: Reserve Ticket

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to reserve ticket for passengers.

 

Precondition:  Flight is already scheduled and seats are available

 

Post-Condition: seats is/are reserved.

 

Extends: none

 

Uses: SendEmail

 

Normal Course of Events:

 

 

User

System

1

On home page admin clicks the “Reserve Seat” button

 

2

 

System displays input screen for seat reservation

3

Admin selects the flight from dropdown menu, selects seat numbers, enters the passengers data and clicks save button

 

4

 

System saves the data, sends email to the passenger, displays success message and prints the ticket.

 

Alternative Path:

At step (3) admin does not click the “Save button” but clicks the cancel button, system displays the home page again.

 

Exception: At any stage server is disconnected, system displays “Server not connected” message. At step (4) mail sending fails, system displays message, “mail sending failed”, in case of failure of printer, system displays “printing ticket failed”.

Assumption: None

 

 

Use Case Name: Edit Reservation

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to edit the already reserved ticket.

 

Precondition:  Ticket is already reserved.

 

Post-Condition: Reservation is updated..

 

Extends: none

 

Uses: SendEmail

 

Normal Course of Events:

 

 

User

System

1

On home page admin clicks the “Edit Reservation” button

 

2

 

System displays input screen for Editing reserved seat.

3

Admin enters the ticket number and presses edit button

 

4

 

System displays all the data of that ticket in edit mode.

5

Admin modifies the data and clicks the update button

 

6

 

System updates the data, sends email to the passenger, displays success message and prints the ticket with updated data.

 

Alternative Path:

At step (3) admin does not click the “edit button” but clicks the cancel button, system displays the home page again.

At step (5) admin does not click the update button but clicks “cancel” button. System does not update the ticket but goes to home page.

Exception: At any stage server is disconnected, system displays “Server not connected” message. At step (6) mail sending fails, system displays message, “mail sending failed”, in case of failure of printer, system displays “printing ticket failed”.

Assumption: None

 

 

Use Case Name: Cancel Reservation

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to cancel the already reserved ticket.

 

Precondition:  Ticket is already reserved.

 

Post-Condition: Reservation is canceled.

 

Extends: none

 

Uses: SendEmail

 

Normal Course of Events:

 

 

User

System

1

On home page admin clicks the “Edit Reservation” button

 

2

 

System displays input screen for Editing reserved seat.

3

Admin enters the ticket number and presses edit button

 

4

 

System shows all the data of that ticket in edit mode.

5

Admin modifies the data and clicks the “Delete” button

 

6

 

System Deletes the data, sends email to the passenger, displays success message.

 

Alternative Path:

At step (3) admin does not click the “edit button” but clicks the cancel button, system displays the home page again.

At step (5) admin does not click the “Delete” button but clicks “cancel” button. System does not update the ticket but goes to home page.

Exception: At any stage server is disconnected, system displays “Server not connected” message. At step (6) mail sending fails, system displays message, “mail sending failed”.

Assumption: None

 

 

Use Case Name: Print periodic Flights Status

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to print the total flights scheduled between two dates.

 

Precondition:  Valid dates must be specified.

 

Post-Condition: flights scheduled between said dates should be displayed.

 

Extends: none

 

Uses: SendEmail

 

Normal Course of Events:

 

 

User

System

1

On home page admin clicks the “View periodic flight status” button

 

2

 

System displays the input screen for entering two dates

3

Admin enters the start and end dates and clicks display button

 

4

 

System displays all the flights in table format between the said dates.

5

Admin double clicks any flight

 

6

 

System displays all the data of that flight.

 

Alternative Path:

At step (3) admin does not click the “display button” but clicks the cancel button, system displays the home page again.

At step (5) admin does not double click flights but clicks “cancel” button. System does show flight data but does to home page.

Exception: At any stage server is disconnected, system displays “Server not connected” message.

Assumption: None

 

 

Use Case Name: Add User

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to enter new user.

 

Precondition:  Admin is already login

 

Post-Condition: user is entered in database

 

Extends: none

 

Uses: None

 

Normal Course of Events:

 

 

User

System

1

Admin clicks the “add new user” link

 

2

 

System displays the input screen for entering data of user

3

Admin enters data and clicks “save” button

 

4

 

System saves data and displays success message

 

Alternative Path:

At step (3) admin does not click the “save” button but clicks the cancel button, system displays the home page again.

 

Exception:

At any stage server is disconnected, system displays “Server not connected” message.

 

Assumption: None

 

 

Use Case Name: Edit User

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to edit data of already existing user.

 

Precondition:  user already exists in system

 

Post-Condition: user data is updated

 

Extends: none

 

Uses: None

 

Normal Course of Events:

 

 

User

System

1

Admin clicks the “edit user” link

 

2

 

System displays the input screen for entering user id

3

Admin enters the user id and clicks “display” button

 

4

 

System displays the user data in edit mode.

 

Admin modifies the required data and clicks the “update” button

 

 

 

System updates the data and prints the success message.

 

Alternative Path:

At step (3) admin does not click the “display” button but clicks the cancel button, system displays the home page again.

At step (5) admin does not click the “update” button but clicks the cancel button, system displays the home page again.

Exception:

At any stage server is disconnected, system displays “Server not connected” message.

Assumption: None

 

 

Use Case Name: Delete User

 

Priority: Normal

 

Actors:  Admin

 

Summary:  This use case enables admin to delete an already existing user.

 

Precondition:  user already exists in system

 

Post-Condition: user is deleted from database

 

Extends: none

 

Uses: None

 

Normal Course of Events:

 

 

User

System

1

Admin clicks the “edit user” link

 

2

 

System displays the input screen for entering user id

3

Admin enters the user id and clicks “display” button

 

4

 

System displays the user data in edit mode.

 

Admin modifies the required data and clicks the “delete” button

 

 

 

System deletes the data and prints the success message.

 

Alternative Path:

At step (3) admin does not click the “display” button but clicks the cancel button, system displays the home page again.

At step (5) admin does not click the “delete” button but clicks the cancel button, system displays the home page again.

Exception:

At any stage server is disconnected, system displays “Server not connected” message.

Assumption: None

 

 

Use Case Name: View News Flash

 

Priority: Normal

 

Actors:  Passengers

 

Summary:  this use case will enable the passenger to view the flash news on the client screen

 

Precondition:  Flash news exist in system

 

Post-Condition: Flash news are displayed on client interface

 

Extends: none

 

Uses: SearchNewsFlash

 

Normal Course of Events:

 

 

User

System

1

 

System displays flash news headings in scrolling manner, each heading contains “more details” link.

2

User clicks the “more details” link

 

3

 

System displays the news details

4

User clicks the “Back” link

 

5

 

Main screen appears.

 

Alternative Path:

At step one (1) No news are there in database, system does not display any news

At step two (2), user does not click any link. The system continues on displaying the news headings.

 

Exception:

Server disconnected, system displays “Information Not available at the Time” message.

 

Assumption: None

 

 

Use Case Name: SearchFlight

 

Priority: Normal

 

Actors:  Passengers

 

Summary:  this use case will enable the passenger to search the flight as per his/her convenience

 

Precondition:  flights exist in database

 

Post-Condition: Flight schedule is displayed for the said date(s)

 

Extends: none

 

Uses: none

 

Normal Course of Events:

 

 

User

System

1

On home page passenger selects “search flight” link

 

2

 

System displays the input screen for entering the date

3

User enters the date(s) and clicks “display” button

 

4

 

System displays all the flights scheduled on the said dates

5

Passengers clicks the “print” button

 

 

 

System prints the schedule.

 

Alternative Path:

At step (3) user does not click the display button but clicks the cancel button, system does not display the flight schedule, but goes to home page

At step (5), user does not click pint button but clicks “go back” button and system goes to home page.

 

Exception:

Server disconnected, system displays “Information Not available at the Time” message.

Assumptions: none

 

 

Use Case Name: SearchSeat

 

Priority: Normal

 

Actors:  Passengers

 

Summary:  This use case enables passenger to search flight as per his/her convenience

 

Precondition:  flights exist in database

 

Post-Condition: Flight schedule is displayed for the said date(s)

 

Extends: none

 

Uses: SearchFlight

 

Normal Course of Events:

 

 

User

System

1

On home page passenger selects “search flight” link

 

2

 

System displays the input screen for entering the date

3

User enters the date(s) and clicks “display” button

 

4

 

System displays all the flights (with available seats) scheduled on the said dates

5

Passengers double clicks one flight.

 

6

 

System displays the number of available seats for the selected flight

7

Passenger selects seat(s) and clicks the “print button

 

8

 

System prints the flight no. along with selected seats.

 

Alternative Path:

At step (3) user does not click the display button but clicks the cancel button, system does not display the flight schedule, but goes to home page

At step (5), user does not double click flight, but clicks the cancel button, system does not display the flight schedule, but goes to home page

At step (7), user does not click pint button but clicks “go back” button and system goes to home page

Exception:

Server disconnected, system displays “Information Not available at the Time” message.

Assumptions: none

 

Section 6: Nonfunctional requirements

 

6.1 Reliability Requirements

 

1)      ARS shall be available 24 hours a day, 7 days a week

2)      ARS shall always provide real time information about flight availability information.

3)      ARS shall be robust enough to have a high degree of fault tolerance. For example, if the user enters a negative number of passengers or a value too large, the system should not crash and shall identify the invalid input and produce a suitable error message.

 

6.2 Usability Requirements

1)      ARS shall provide an easy-to-use graphical interface similar to other existing reservation system so that the users do not have to learn a new style of interaction.

2)      The web interface should be intuitive and easily navigable Users should be able to understand the menu and options provided by ARS.

3)      Any notification or error messages generated by ARS shall be clear, succinct, polite and free of jargon.

 

6.3 Integrity Requirements

 

1)      Only the super admin has rights to change system parameters, such as pricing policy etc. The system should be secure and must use encryption to protect the databases.

2)      Passengers should not be able to access any administration related functionality.

 

 

6.4 Security Requirements

 

1)      It must be ensured that access will be provided to the authorized persons through user ID and password.

2)      Network security will be provided by the use of firewalls.

3)      Checks can be performed at regular internals to ensure data integrity.

 

6.5 Maintainability Requirements

 

The software will be developed by implementing the concept of modularity which in turn reduces the complexity involved in maintaining it. It will also help the make future modifications and customization easy.

 

 

6.6 User Documentation

 

Proper user document should be provided with the system along with troubleshooting manuals, so that in case if any issue arises, the airline itself becomes able to fix it. User manual along with live help on each input screen will be provided, so that user could be able to continue smooth interaction with the system without external assistance and in case if any operation is not clear to him/her.

Section 7: Data Dictionary

 

Airline maintains the following data in its data dictionary. Main entities and their possible characteristics are given here.

 

7.1 Airplane

 

Airline comprises of handsome amount of airplanes, for each air plane the airline maintains the following record:

 

Airplane ID

Economy Seats

Elite Seats

No of Crew Members

 

 

7.2 Flight

 

A flight is the scheduled route between some source and destination, passengers reserve seat as per their convenient flight timings. System stores following information for each flight

 

Airplain ID

Source

Destination

Date

Departure time

Arrival time

Domestic/international

Crew members

Passengers

 

7.3 Passenger

 

Passenger is the customer of the airline, who pays for the services he gets out of the airline.

 

Passenger id

Name

Email

Contact no

 

7.4 Staff

 

Staff members are the serving employees of the airline. For each staff member following information will be maintained.

 

Staff member id

Staff member name

CNIC

Designation

Email

Phone

 

 

+ Click Here To Join also Our facebook study Group.

+ How to Join Subject Study Groups & Get Helping Material?

+ How to become Top Reputation, Angels, Intellectual, Featured Members & Moderators?


See Your Saved Posts Timeline

Views: 399

.

+ http://bit.ly/vucodes (Link for Assignments, GDBs & Online Quizzes Solution)

+ http://bit.ly/papersvu (Link for Past Papers, Solved MCQs, Short Notes & More)

+ Click Here to Search (Looking For something at vustudents.ning.com?)

Replies to This Discussion

Please Discuss here about this assignment.Thanks

Our main purpose here discussion not just Solution

We are here with you hands in hands to facilitate your learning and do not appreciate the idea of copying or replicating solutions. Read More>>

 

Note:-

For Important Helping Material related to this subject (Solved MCQs, Short Notes, Solved past Papers, E-Books, FAQ,Short Questions Answers & more). You must view all the featured Discussion in this subject group.

For how you can view all the Featured discussions click on the Back to Subject Name Discussions link below the title of this Discussion & then under featured Discussion corner click on the view all link.

Or visit this link 

Click Here For Detail.

&

.•°How to Download past papers from study groups°•. 

Question 2 part 1 me kaya aya ga?? give idea.

RSS

© 2019   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service