tanzeel & abbas project report (repaired)

7/31/2019 Tanzeel & Abbas Project Report (Repaired)

1/78

MOBILE WORLD

Developed by

Tanzeel ur Rehman Qazi(AH-525452)

Mazhar Abbas(AH-523719)

Supervised by

Mr. Muhammad Qamar Usman

Department of Computer Science

Allama Iqbal Open University Islamabad

H-8, Islamabad.

Year 2012


2/78

______________________ Final Approval

ii

Declaration

We hereby declare that this software, neither as a whole nor as a part thereof has been

copied out from any source. It is further declared that we developed this software and this report

entirely on the basis of our personal efforts made under the sincere guidance of our project

supervisor.

If any part of this software proved to be copied or found to be a report of some other, we

shall standby the consequences.

No portion of the work presented in this report has been submitted in support of any

application for any other degree or qualification of this or any other University or institute of

learning.

We further declare that this software and all associated documents, reports, and records

are submitted as partial requirement for the degree of MBA-IT.

We understand and transfer copyrights for these materials to Allama Iqbal Open

University, Islamabad.

We shall not sale this software and documents and shall not get any financial gains from

these.

Tanzeel ur Rehman Qazi _______________

(10-FID-02905)

Mazhar Abbas _______________(10-PVI-01798)

Project Supervisor _______________


3/78

______________________ Final Approval

iii

Final Approval

This is to certify that we have read the project report submitted by Tanzeel Qazi, and Mazhar abbas and it

our judgment that this report is of sufficient standard to warrant its acceptance by Allama Iqbal Open

University, Islamabad, for MBA-IT degree.

Examination Committee

Internal Supervisor Muhammad Qamar UsmanLecturerUNITECH.

Internal Examiner _______________________Designation

Study Center.

External Examiner ________________________Designation

Study Center


4/78

Project in Brief

iv

PREFACE

This project was made because it was our final semester project, as it is a new field for us

so we have to put all our strength to complete it. The project work was done during

approximately 4 months (July-October 2012), which of course was a little bit short timefor such a difficult learning project. During the project we had to change our time

planning several times as we encountered some problems that forced us to change our

solution dramatically. Of course this meant a lot of work, but we learned a lot from it.

During this project we enhanced our web engineering knowledge as we developed an

entire concept prototype from scratch, which meant that we had to solve many problems,

ranging from implementing design templates to difficult PHP and JavaScript coding.


5/78

Project in Brief

v

Acknowledgement

We express our gratitude to our project supervisor Mr. Muhammad Qamar Usman whoprovided us opportunity to learn and enhance our knowledge. As our project supervisor,

he had been ready to help and guide us throughout the project development.

We have learned a lot throughout this semester, with many challenging yet valuable

experiences in order to complete this task. Our endless thanks to Mr. Muhammad Qamar

Usman for giving us the chance to explore a new knowledge of mine, as well as for

giving us precious advices in order to improve our self to become a better person.

We would like to express our eternal appreciation towards our parents and family who

have always been there for us no matter where we are, for all unconditional supports and

patience. Thank you for being ever so understanding and supportive.

We would like to thank our dear friends and colleagues, especially fellow students ofMBA-IT; it has been great to know all of you during our time here in AIOU UNITECHCampus.

Tanzeel ur RehmanQazi

(10-FID-02905)

Mazhar Abbas

(10-PVI-01798)


6/78

Project in Brief

vi

Project in Brief

Project Title: Mobile World

Version: 1.1

Objective:

Reliability is ourmain objective, that the products shown in or website must bevalid products.

Relationship with our customer must be strong, they can view our product, orderus and even they can send us their views.

Data must be correct and up-to-date. Interests of customers must be checked.

Developed By: Tanzeel ur Rehman Qazi

(10-FID-02905)

Mazhar Abbas

(10-PVI-01798)

Supervised By: Muhammad Qamar Usman.

Allama Iqbal Open University, Islamabad.

Tools Used: Macromedia Dreamweaver CS 5, Wamp

Server, Photoshop CS 5.

Operating System: Microsoft WindowXP.

System Used: Core I-3 Laptop.


7/78

Project in Brief

vii


8/78

TABLEOF CONTENTS

Table of Contents

Acknowledgement .............................................................................................................. v

1 Introduction ............................................................................................................... 11

1.1 Mobile World .....................................................Error! Bookmark not defined.

1.2 Project Overview ...............................................Error! Bookmark not defined.

1.3 Project Scope .....................................................Error! Bookmark not defined.

1.4 Proposed System Components ...........................Error! Bookmark not defined.

1.5 Tools and Technologies .....................................Error! Bookmark not defined.

2 Literature Review ..................................................................................................... 14

2.1 Reason for Selecting Online Mobile Shopping webiste ................................... 15

2.2 Selection of Web Based Solution ..................................................................... 15

2.3 Selection of Development Tool ........................................................................ 153 System Design Detail ................................................................................................ 17

3.1 Functionality and Requirements ....................................................................... 18

3.1.2 Mobile view..................................................................................................17

5.2 Administrator view: ........................................................................................17Non-functional Requirement...........................................................................................17

6.1 Usability...........................................................................................................18

6.2 Security............................................................................................................186.2.1Privacy...............................................................................................19

6.2.2 Access rights.....................................................................................19

6.3 Scalability........................................................................................................19

6.4 Extensibility.....................................................................................................206.5 Maintainability.................................................................................................20

6.6 Testability........................................................................................................20

6.7 Platform compatibility.....................................................................................204 Software Design ........................................................................................................ 21

Use Cases .......................................................................................................................... 22

Login ......................................................................................................................... 22

Add User ................................................................................................................... 23

Update user ............................................................................................................... 24

Block user ................................................................................................................. 25

Delete user ................................................................................................................ 26

Search Users.............................................................................................................. 27Front End .................................................................................................................. 29

Update profile ............................................................Error! Bookmark not defined.

4.1 Search Users...................................................................................................... 31

4.2 Use Case Diagram............................................................................................. 32

4.3 ERD....................................................................Error! Bookmark not defined.

4.4 Relationship Diagram .......................................Error! Bookmark not defined.

4.5 Sequence Diagrams ........................................................................................... 34


9/78

Login Sequence ......................................................................................................... 34

New User Sequence .................................................................................................. 36

Search User Sequence ............................................................................................... 37

Update User Sequence .............................................................................................. 38

Block User Sequence ................................................................................................ 39

Delete User Sequence ............................................................................................... 40Search Sequence (Front End) .................................................................................... 41

5 Data Flow Diagram ................................................................................................... 42

5.1 DFD................................................................................................................... 43

Context Diagram ....................................................................................................... 43

5.2 Activity Diagram .............................................................................................. 44

5.3 Data Dictionary ................................................................................................. 45

Table name: User .......................................................Error! Bookmark not defined.

Table: Admin User .................................................................................................... 46

Table: User Record ....................................................Error! Bookmark not defined.

Table: Visitor .............................................................Error! Bookmark not defined.

Table: Rating ............................................................................................................. 49

Table News ............................................................................................................... 49

6 Implementation ..........................................................Error! Bookmark not defined.

6.1 Index Page (Front End) ......................................Error! Bookmark not defined.

6.2 User Sign up Page ..............................................Error! Bookmark not defined.

6.3 Forgot Password.................................................Error! Bookmark not defined.

6.4 Admin Control Panel .........................................Error! Bookmark not defined.

6.5 Admin Main Page ..............................................Error! Bookmark not defined.

6.6 Add Donor .........................................................Error! Bookmark not defined.

6.7 Add Borrower ....................................................Error! Bookmark not defined.

7 Testing ...................................................................................................................... 56

7.1 Introduction ....................................................................................................... 57

7.2 Software Testing ............................................................................................... 58

7.3 Verification ....................................................................................................... 58

7.4 White box, black box testing ............................................................................ 58

Black box .................................................................................................................. 58

White box .................................................................................................................. 59

7.5 Levels of testing ................................................................................................ 59

Functional Testing .................................................................................................... 59

Unit testing ................................................................................................................ 60

Unit testing is performed by the developers before the setup is handed over to the

testing team to formally execute the test cases. Unit testing is performed by the

respective developers on the individual units of source code assigned areas. The

developers use test data that is separate from the test data of the quality assuranceteam. .......................................................................................................................... 60

Integration testing ..................................................................................................... 60

The testing of combined parts of an application to determine if they function

correctly together is integration testing. In a comprehensive software developmentenvironment, bottom-up testing is usually done first, followed by top-down testing.

The process concludes with multiple tests of the complete application, preferably in


10/78

scenarios designed to mimic those it will encounter in customers, computers,

systems and network. ................................................................................................ 60

Regression Testing .................................................................................................... 60

Acceptance testing .................................................................................................... 60

Alpha testing ............................................................................................................. 61

Beta testing.................................................................Error! Bookmark not defined.Beta test is performed after Alpha testing hasb successfully performed. In beta

testing a sample of the intended audience tests the application. In beta testing

audience will be testing the following: ......................Error! Bookmark not defined.

Users will install, run the application and send their feedback to the project

team. ...........................................................................Error! Bookmark not defined.

7.6 Non-Functional Testing .................................................................................... 61

Performance Testing ................................................................................................. 61

7.7 A sample testing cycle ...................................................................................... 63

7.8 Test Cases ......................................................................................................... 64

Black Box Testing..................................................................................................... 64

Register ......................................................................Error! Bookmark not defined.

Update ....................................................................................................................... 65

Test Cases for Front End........................................................................................... 66

Update ....................................................................................................................... 67

7.9 User ....................................................................Error! Bookmark not defined.

Ratings ...................................................................................................................... 68

Test Cases (Admin Panel) ......................................................................................... 69

Block/Un Block ........................................................................................................ 70

News ......................................................................................................................... 70

White Box Testing .................................................................................................... 71

Unit Testing .............................................................................................................. 72

Recovery Testing ...................................................................................................... 73

7.10 Test log.............................................................................................................. 74

8 Conclusion and Future Work .................................................................................... 76

8.1 Achievements .................................................................................................... 77

8.2 Future Enhancement ......................................................................................... 78


11/78

1 Introduction


12/78

Chapter No.1 __________ Introduction

Mobile World Page 12

1.1 Mobile World

Main objective of is to give mobiles a platform from they can easily able to buy a mobile

of their best choice online in an efficient and mobile friendly manner. It also keeps track

of orders reviews comments videos in a way so that there is no chance of missing a single

penny.

In designing of the system the main consideration was to make it foolproof and as mobile

friendly as possible while keeping the aesthetic sense by providing an eye catching

design. One more thing about is that it has been developed in a way that any future

enhancement can be incorporated very easily.Management System is fool proof system which allows not only administrator but the

mobiles of system as well to track latest reviews and videos regarding mobile.

1.2 Goals of Project:

Following are the goals of our project which we tried to accomplish them during our

project

Finish the project within the scheduled timetable. Finish the project with same quality as our teacher was expecting. Finish the project within the specific guidelines; means the project must not

deviate from the right path.

To make a website which will be mobile friendly Contain all latest information about mobiles All mobiles information from different brands whether they are old. It has facility of mobile comments.

1.3 Scope of Project:

Following are the list that defines the scope of our project.


13/78



1.3.1 Project Justification:

Mobile Management Website is an interesting and full of scope project. As it isour Web Engineering project, so we have taken this project to implement our all

web related knowledge in this project. This project is feasible and implement able

that is why we selected this project.

1.3.2 Project Product:

The product of our project is a website which would contain all mobile set

information. It would contain updates about new mobile sets, their qualities andtheir cost. The website would also have the facility that mobile can also comment.

1.3.3 Project Deliverables:Following are the deliverables of our project:

SRS (Software Requirement Specification) Demo of our Website. Complete Website, .

Project Report.

1.4. Objectives of Project:

Following are the objectives of our website:

Reliability is ourmain objective, that the products shown in or website must bevalid products.

Relationship with our customer must be strong, they can view our product, orderus and even they can send us their views.

Data must be correct and up-to-date. Interests of customers must be checked.

1.5. Tools and Technology:

1.5.1 Software:

Following are the software that will be in use during the making of our software:

Mysql Dreamweaver WAMP server

1.1.2 Language: The language we used for coding our website is PHP


14/78



JavaScript

2 Literature Review


15/78

Chapter No.2 __________ Literature Review

15

2.1 Reason for Selecting Online mobile shopping website

There are a lot of online shopping websites present today but most of them are so complicated

for the mobiles that they cant even sit and view the website for 1 minute and if website the

website is simple than the administration of website is not very efficient to coordinate with the

customer if she/he want to give an order of any particular product.

Our websites has all features like creating profiles and online ordering this will facilitates the

mobiles that they can get their mobile more easily and quickly. On the other hand it also

reduces the clerking job, because our system will automate the clerkale activities. Mobiles can

also track their order details by visiting online. Our system will also reduce miss management

and late order delivery transaction and corruption as well.

2.2 Selection of Web Based Solution

Now a days web application are used highly in world because we do not need to install

Application on all machine instead of this we just put whole application on web server and all

other machines use application by communication with web server.

The desktop solutions are useful if we want to use the system in a single organization and

desktop solutions are developed for single machines.

2.3 Selection of Development Tool

After visiting some of the software houses, we select PHP as development language for this

system because it is being used increasingly in market it is light weight and provide all

functionality which we need to develop this system.


16/78

Chapter No.2 Literature Review

Funds Management System 16


17/78

3 System Design Detail


18/78

Chapter No.3 ___________ System Design Detail

Mobile World 18

Overall Goal:

1. System efficiency2. On line ordering.3. Order tracking4. On line presence

This application will be for an (Online mobile Shopping website).

3.1 Functionality and Requirements

5.1 Mobile view:

Mobile can view a variety of mobile phones of different companies. Mobile can view the details (pictures and specifications) of any specificmobile phone of any company.

Mobile can add comment about any mobile phone. Mobile can view comments of different mobiles about any mobile phone. Mobile can order any mobile phone by giving his/her details for contact. Mobile can order new as well as used mobile phones. Mobile cannot access the database. Mobile can view and order mobile accessories like chargers, covers, hands

free, data cable, memory card, Bluetooth etc.

5.2 Administrator view: The administrator can update the database by adding new mobile phones. The administrator can view the orders for different mobile phones.

6. Non-functional requirements:

In contrast to functional requirements, non-functional requirements do not make a

statement about the behavior of the system, but about its quality. They are an essential

part of the requirements definition. In the following, we will thus present the qualitativerequirements that should be met by our website.

6.1 Usability: The usability of a website is a critical aspect that demands special

attention. Usability is defined as the extent to which a product can be used by


19/78


Mobile World 19

specified mobiles to achieve specified goals with effectiveness, efficiency and

satisfaction in a specified context of use.

In the context of our website, these demands are detailed as follows:

Our website should allow mobiles to reach their goals without digressions.It should quickly react to the mobiles actions, be non-distracting andshould allow mobiles to operate the website in a linear way.

Our website should aid the mobile in extracting the right results out of thedatabase and should assist mobiles in finding the results they need. Thisincludes a clear layout of the display and an unambiguous navigation

through the various functions of the website.

The mobiles interaction with the website should be satisfying, with astrong emphasis on the mobiles feelings when using the website and afterusing the website. To reach the goal of satisfaction, mobiles need to be

supported in finding the results they need. This includes aspects as a

straightforward interface design and the minimization of necessaryinteractions by the mobile, as bandwidth and speed of some internet

connections are usually limited. Interface should be self explanatory and

there should be mobile centered design.

6.2 Security: One of the most important non-functional requirements is security.

Security requirements come in different forms:

6.2.1Privacy: The website shall not store any personal information about a

certain mobile that can not be changed by the mobile him/herself (e.g.personalized search settings or saved queries).

Access rights: The website shall not allow the mobiles to access the database directly or

shall not allow the mobiles to make changes in database.

6.3 Scalability: Scalability is a critical issue for a website because it can experience

heavy traffic from day to day. It thus needs to make sure our website will be scalable

according to the increasing traffic. But at starting point 50 concurrent logins are more

than enough for our website.

6.4 Extensibility: Extensibility is a quality of design that takes possible feature

advances into consideration and attempts to accommodate them. The mobile

management website shall therefore be able to allow the addition of features withoutimpact to the existing website functions.

6.5 Maintainability: The code developed in this task needs to be maintained by us.

So, we will also document all necessary features and parts of the code.


20/78


Mobile World 20

6.6 Testability: To ensure a proper testability of the code we will develop unit tests

for all critical parts of the software. Unit tests can be executed automatically to

confirm the correct operation of the code after changing parts of the system. We will

furthermore test the operation of the system manually to ensure proper operation from

a mobile centric point of view.

6.7 Platform compatibility: A wide range of browsers are available now. So, our

website should thus support all browsers.

6.8 Performance: Most of the internet connections still have to deal with lower

bandwidths, one of the main focus points for performance considerations should be

the amount of display data on one web page. So, our website shall only display data

relevant to mobiles query. E.g. a high resolution image should only be loaded if the

mobile wants to view and actively selects it. The website shall respond to mobiles

query immediately and as fast as possible. There can be an issue of lack in processing

power, so displaying hundreds of results could affect the mobiles experience.


21/78

4 Software Design


22/78

Chapter No.4 ___________ Software Design

Mobile World 22

Use Cases

A use case represent the list of tasks that actor can perform. Here all cases are described

in the expanded format.

Login

Use case name: Login.

Actors: Administrator .

Purpose: Access the system functionalities.

Precondition: Admin must have an account in the Mobile World.

Post condition: System verify the mobile, and mobile logs in successfully.

Type: Primary.

Overview: To login administrator, Mobiles are required to provide mobile name,

password. Login information is sent to server, server verifies the Mobile name and

Password information. Control panel for each mobile will be displayed, based on mobile

role.

Typical course of Actions

Actors Actions System Response

1. Administrator enters login information

(Mobile name, password) and clicks on

Login button.

i). The system connects to server and

verify the mobile name and

password.

ii). The system displays the Profiles of the

Administrator / _ / __ Mobiles.

Alternate course of Actions

Actors Actions Alternate System Response

1. Administrator/_/__ enters invalid logininformation (Mobile name, Password) and

clicks on Login button.

i). Connection to server established andthe login information is verified.

ii). Login information error is indicated.


23/78


Mobile World 23

Add Mobile

Use case name: Add mobile from admin panel.

Actors: Administrator.

Purpose: Mobile creation.

Precondition: Administrator must be logged in.

Post condition: Mobile World control panel should be displayed.

Type: Primary.

Overview: Our admin can create a mobiles, change, and block or deleted, this

management system will help in dealing with mobiles.


Actors Actions System Response1. Administrator 1

st login to system. i). The system connects to server and


password.

ii). The system displays the Control Panel

to the Administrator based on his role.

2. Add the mobile by clicking on to add

videos.

i) The system will display the form to add

the mobiles. The admin have to enter in

the required fields. After correct entering

the form the mobile will be created and an

email will be sent to the mobile email

address.



1. Administrator enters invalid login

information (Mobile name, Password) and


i). Connection to server established and

the login information is verified.


iii) Email address already exists.


24/78


Mobile World 24

Update mobile

Use case name: Update mobile.

Actors: Administrator

Purpose: Update.

Precondition: Mobile must be logged in.

Post condition: Profile will be updated.

Type: Primary and Real.

Overview:



1. Admin must be logged in to the system. i). The system connects to server and verify

the mobile name and password.


to the Administrator based on his role..

2. Admin can edit his own profile by

clicking on the edit profile button.

i) Edit Profile Page will be displayed to

mobiles.

3. Admin can edit the mobiles profiles by

click on the edit profile button.

i) Edit Profile page will be displayed.



1. Mobiles enter invalid information. i). System displays error and request to

provide proper and valid credential.


25/78


Mobile World 25

Block mobile

Use case name: Block mobile from admin panel.


Purpose: Blocking of mobile.



Type: Primary.

Overview: Our admin can block the mobiles this management system will help in

dealing with mobiles.



1. Administrator 1st

login to system. i). The system connects to server and


password.



2. Block the mobile by clicking on to

disable link.

i) The system will display the block the

selected mobile.










26/78


Mobile World 26

Delete mobile

Use case name: Delete mobile from admin panel.


Purpose: Delete mobile.



Type: Primary.

Overview: Our admin can delete the mobile this management system will help

in dealing with mobiles.




login to system. i). The system connects to server and


password.



2. Delete the mobile by clicking on to

delete icon.

i) The system will display the message

and then delete the selected mobile.










27/78


Mobile World 27

Search Mobiles

Use case name: Search mobiles.


Purpose: To search all the mobiles ordered in the Mobile World.Precondition: Enter first mobile name.

Post condition: Mobiles will be shown matched with search keyword.


Overview: When admin wants to search any mobile he has to give any field

through which system will search the desired mobile. If the desired mobile exists, his

record will be displayed; otherwise No Records message will be displayed in the search

page.




login to system. i). The system connects to server and verify

the mobile name and password.



2. Admin enters the first name or last name

or email address of the mobile.

i) Specified mobile will be displayed.

ii) In Mobile World, Mobiles of other

category will be displayed like that.



1. Administrator enters invalid information.i). System displays error and request to



28/78


Mobile World 28


29/78


Mobile World 29

Front End

Order mobile

Use case name: Order mobile from front end.

Actors: visitorsPurpose: Add.

Precondition: Users can order to Mobile World.


Overview:



1. Mobile will Order from front end by

clicking order.

i). The system will displays the Order form.

ii). The system will check the proper fields.

If mobile enters wrong information in the

form, the system will not submit the form.

iii) An email will be sent to the mobile

email address.

2. After Registration mobiles can see their

profiles.

i) Profile Page will be displayed to

mobiles.



1. Mobiles enter invalid information. i). System displays error and request to



30/78


Mobile World 30


31/78


Mobile World 31

Search Mobiles

Use case name: Search mobiles.

Actors: users/customersPurpose: To search all the mobiles ordered in the Mobile World.

Precondition: Enter any of the provided fields on the search form.

Post condition: Mobiles will be shown matched with search keyword.


Overview: When admin/_/__ want to search any mobile he has to give any

field through which system will search the desired mobile. If the desired mobile exists,

his record will be displayed; otherwise No Records message will be displayed in the

search page.



2. Mobiles from the Front end can search the

other _ or __ without login to the system.

ii) Mobile World has three categories of

Same is the case with other categories.



1. Mobile enters invalid information.i). System displays error and request to


Orders

Use case name: order.

Actors: customer

Purpose: give order for a mobile to Mobile World.

Precondition: Administrator must be logged in before taking the order.

Type: Primary and Real

Overview:


32/78


Mobile World 32

Use Case Diagram


33/78


Mobile World 33

7.2 Entity Relationship Diagram:


34/78


Mobile World 34

4.1 Sequence Diagrams

Login Sequence


35/78


Mobile World 35


36/78


Mobile World 36

New Mobile Sequence


37/78


Mobile World 37

Search Mobile Sequence


38/78


Mobile World 38

Update Mobile Sequence


39/78


Mobile World 39

Block user Sequence


40/78


Mobile World 40

Delete Mobile Sequence


41/78


Mobile World 41

Search Sequence (Front End)


42/78

5 Data Flow Diagram


43/78

Chapter No.5 ____________ DFD

Mobile World 43

5.1 DFD

The Data Flow Diagram is normally used for the visualization of data processing by a

system in terms of inputs and outputs. The normal flow is shown graphically. A designerusually draws framework level DFD showing communication between the system and the

outside entities.

Context Diagram


44/78

Chapter No.5 ____________ DFD

Mobile World 44

5.2 Activity Diagram


45/78

Chapter No.5 DFD

Mobile World 45

5.3 Data Dictionary

Table: _

Field name Data type & size Constraints Definition

ID int(20) Foreign Key,

Primary Key

It is a foreign key and primary key.

That is same as the mobile id.

Picture text null Stores the picture of the mobile.

Personal_info text null Stores the personal information of the

mobile.Story text null Stores the story of the mobile.

Category varchar(20) Not null Stores the category as above early.

Reason text null Stores the reason.

Table: __

Field name Data type& size Constraints DefinitionID int(20) Foreign Key,

Primary Key

It is primary key and foreign key that

is same as mobile id and it is primary

because it is used further in tables.

Picture text null Stores the picture of the mobile.

personal_info text null Stores the personal information of the

mobile.


46/78

Chapter No.5 DFD

Mobile World 46

Table: Admin


ID int(30) Primary Key It is auto incremented and unique id of

the admin.

Fname varchar(30) Not null Stores the first name of the admin.

Lname varchar(30) Not null Stores the last name of the admin.

Email varchar(30) Not null Stores email of the mobile.

Phone varchar(30) Not null Stores the phone number of the

mobile.

Mobilename varchar(30) Not null Stores the mobilename of the mobile.

This is required for login.

Password varchar(30) Not null Stores the password of the mobile that

is used for login.

Ccn Int(30) Not null Stores the ccn number of the mobile.


47/78

Chapter No.5 DFD

Mobile World 47

Table _ Record of users


Users id int(25) Primary key ,

Foreign key.

It is primary key and

foreign key that is same

as mobile id and it is

primary because it is used

further in tables.

Users name varchar(25) Null Stores the name of the

user.

Users name varchar(25) Null Stores the name of the _.

Reason varchar(250) Null Stores the reason fortaking mobile from

Mobile World.

___id int(250) Null Stores the __ id.

Category varchar(25) Null Stores the category as

described early.


48/78

Chapter No.5 DFD

Mobile World 48


49/78

Chapter No.5 DFD

Mobile World 49

Table: Rating


ID int(11) Not Null It is an auto

incremented id.

__id int(11) Foreign key It is foreign key.

Voter_ip varchar(20) Null Stores the voter ip.

Rating Rating Null Stores the Rating

information.

Table News


news_id int(11) Primary key It is an auto

incremented id.

subject varchar(1000) Not null Stores the subject of

the news.

description Text Not null Stores the

description of the

news.

news_link Text Not null Stores the news

link.

posted on varchar(25) Not null Stores the date of

posted.


50/78

6 Implementation


51/78

Home Page.


52/78

Admin Panel Access


53/78

Contact Managements


54/78

Orders Management


55/78

Mobile Catagories


56/78

7 Testing


57/78

Chapter No.7 ____________ Testing

Mobile World 57

7.1 Introduction

Generally, software engineers differentiate software faults from software failures. In case

of a failure, the software does not work. A fault is a programming error that and will

become a failure while exact computation conditions are met. An error can found when

the software is ported to another system or compiler.

Main benefit of software testing is to check the reliability of software so that the

organization is confident to accept it. When testing the software there are no of problems

occur. Viruses that occur occasionally are difficult to find in testing. Software faults

occur through the following processes. A programmer makes a mistake, which results in

a fault, bug in the software. If this defect is executed, the system will produce wrongresults .But the require system is that which work without fault/error. This has simple

consequences for projects to write long-lived reliable software, since it is not usually

commercially viable to test over the proposed length of time unless this is a relatively

short period. A few days or a week would normally be acceptable, but any longer period

would usually have to be simulated according to carefully prescribed start and end

conditions.

A shared practice of software testing is that it is performed by an independent group of

testers after the functionality is developed but before it is sent to the customer. This

exercise frequently results in the testing phase being used as project obstacle to

compensate for project delays, thus compromising the time devoted to testing. Another

practice is to start software testing at the same moment the project starts and it is a

continuous process until the project finishes.
http://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Fault_%28technology%29http://en.wikipedia.org/wiki/Failurehttp://en.wikipedia.org/wiki/Failurehttp://en.wikipedia.org/wiki/Fault_%28technology%29http://en.wikipedia.org/wiki/Software_engineering


58/78


Mobile World 58

7.2 Software Testing

Software testing is risk based exercise.

Testing cannot show that virus doesnt exist.

The more bugs you find, then more bugs there are.Not all the virus you find will be fixed.

Product specifications are never final.

It is impossible to test a program completely.

7.3 Verification

Software verification is used in association with testing and validation (T&V). Verification is the

checking or testing of items, including software, for conformance and consistency with an

associated specification. Validation is the process of checking what has been specified is what

the user actually wanted. Software testing is just one kind of verification, which also uses

techniques such as reviews, inspections, and walkthrough.

7.4 White box, black box testing

Black and White box testing are terms used to define the point of view that a test

engineer takes when designing test cases.

Black box

Black box testing is known as functional testing Black box testing method whereby the

internal workings of the item being tested are not known by the tester. For example, in a

black box test on software design the tester only knows the inputs and what the expected

outcomes should be and not how the program arrives at those outputs. The tester does not

ever examine the programming code and does not need any further knowledge of the

program other than its specifications. Testing treats the software as a black box without

any understanding as to how the internals work. This level of testing usually requires

through test cases to be provided to the tester who then can simply verify that for a given


59/78


Mobile World 59

output value (or behavior), is the same as the expected value specified in the test case.

White box

Also known as open box testing. A software technique whereby clear information of theinternal working of the item being tested are used to select the test data. White box

testing uses specific knowledge of programming code to examine outputs.

When the tester has access to the internal data structures, code, and algorithms. For this

reason, unit testing and debugging can be classified as white box testing and it usually

requires writing code, or at a minimum, stepping through it, and thus requires more skill

than the black box tester.

Grey box testing has common usage. This involves having access to internal data

structures and algorithms for the purpose of designing the test cases, but testing at the

user, or black box level. Manipulating input data and formatting output do not qualify as

grey box because the input and output is clearly outside of the black box we are calling

the software under test. This is mostly important when conducting integration testing

between two modules of code written by two different developers, where only the

interfaces are exposed for test.

7.5 Levels of testing

Levels of testing include the different methods that can be used while conducting software

testing. Following are the main levels of software testing.

Functional Testing

Non-Functional Testing.

Functional Testing


60/78


Mobile World 60

Functional testing is also known as black box testing that is bases on the specification of the

software that is to be tested. Below are different steps that are involved when testing an

application for functionality.

Unit testing

Unit testing is performed by the developers before the setup is handed over to the testing team to

formally execute the test cases. Unit testing is performed by the respective developers on the

individual units of source code assigned areas. The developers use test data that is separate from

the test data of the quality assurance team.

Integration testing

The testing of combined parts of an application to determine if they function correctly together is

integration testing. In a comprehensive software development environment, bottom-up testing is

usually done first, followed by top-down testing. The process concludes with multiple tests of the

complete application, preferably in scenarios designed to mimic those it will encounter in

customers, computers, systems and network.

Regression Testing

Whenever a change in a software application is made it is quite possible that other areas within

the application have been affected by this change. To verify that a fixed bug hasnt resulted in

another functionality of business rule violation is regression testing. The intent of regression

testing is to ensure that a change, such as a bug fix did not result in another fault being uncovered

in the application.

Acceptance testing

This is arguably the most impotence type of testing as it is conducted by the Quality

Assurance Team who will gauge whether the application meets the intended

specifications and satisfies the clients requirement. Acceptance conducted by the end-

user, customer, or client to validate whether or not to accept the product. By performing

acceptance test on an application the testing team will deduce how the application will


61/78


Mobile World 61

perform in production. There are also legal and contractual requirements for acceptance

of the system.

Alpha testing

Alpha testing is the first stage of testing and will be performed amongst the teams(

developer and QA teams). Unit testing, integration testing and system testing when

combined are known as alpha testing. During this phase, the following will be tested in

the application:

Spelling Mistakes Broken Links Cloudy Directions The application will be tested on machines with the lowest specification to test

loading times and any latency problems.

7.6 Non-Functional Testing

This section is based upon the testing of the application from its no-functional attributes.

Non-functional testing of Software involves testing the Software from the requirements

which are non functional in nature related but important a well such as performance,

security, user interface etc. . .Some of the important and commonly used non-functional

testing types is mentioned as follows:

Performance Testing

It is mostly used to identify any bottlenecks or performance issues rather than finding the

bugs in software. There are different causes which contribute in lowering the

performance of software.

Shutdown or restart of Network ports randomly. Turning the database on or off.


62/78


Mobile World 62

Security Testing

Security testing involves the testing of software in order to identify any flaws ad gaps

from security and vulnerability point of view.

Confidentiality Integrity Authentication Availability Authorization Software data is secure. Etc.

Portability Testing

Portability testing includes the testing of Software with intend that it should be re-useable

and can be moved from another Software as well. Following are the strategies that can be

used for Portability testing.

Transferred installed Software from one computer to another. Building executable to run the Software on different platforms.

Stress Testing

This testing type includes the testing of software behavior under abnormal conditions.

Taking away the resources, applying load beyond the actual load limit is Stress testing.

Load Testing

A process of testing the behavior of the Software by applying maximum load in terms of

Software accessing and manipulating large input data. It can be done at both normal and

peak load conditions. This type of testing identifies the maximum capacity of Software

and its behavior at peak time.


63/78


Mobile World 63

7.7 A sample testing cycle

Testing differs among organizations; there is a cycle to testing:

Testing should begin in the requirements phase of the software development life cycle.

Testers work with developer in determining what aspects of a design are testable andunder what parameter those tests work.

Planning Phase: Test Policy, Test Bed creation.

During planning phase a lot of activities well be performed, so that a plan is needed.

Development Phase: Test Procedures, Test Scenarios, Test Cases, and Test Scripts to use

in testing software.

Execution: Testers execute the software based on the plans and tests and report any

errors found to the development team.

Reporting: Once testing is completed, testers generate metrics and make final reports on

their test effort and whether or not the software tested is ready for release


64/78


Mobile World 64

7.8 Test Cases

Black Box Testing

Test type: Black Box Testing

Description: Black-box test design treats the system as a "black-box", so it doesn't

explicitly use knowledge of the internal structure. Black-box test design is usually

described as focusing on testing functional requirements. Synonyms for black-box

include: behavioral, functional, opaque-box, and closed-box.

In black box testing, the user interface is exercised over a full range of inputs and the

corresponding outputs are observed for correctness.

Environment: Win XP.

Test Case Name:Login

User Input Expected Result Actual Result

Enter login information (User name,

password) and clicks on Login button.

i). The system will

connect to server

and verify the user

name and

password.

ii). The system will

displays the Control

Panel of Mobile

World /Front End

Mobile World user.

Same as Expected

Result.

Result:

Pass Fail


65/78


Mobile World 65

Update

Test Case Name: Update


After successful login the user can edit

their profile.

A Edit Profile Page

will open.

Same as Expected

Result.

User enters new info and click on the

update button.

System will validate

and enters the info

into database.

Same as Expected

Result.

After successful updating. The system will

display the

message.

Same as Expected

Result.

Result:

Pass Fail


66/78


Mobile World 66

Test Cases for Front End

Test Case Name:Search


User can search all the mobiles. A relevant profilewill open.

Same as ExpectedResult.

User can search from first name, last name

and email of the user.

Records based on

the typed keyword

will be shown.

Same as Expected

Result.

User presses the View button to view the

complete details.

The system will

open the details of

the user.

Same as Expected

Result.

Result:

Pass Fail


67/78


Mobile World 67

Update

Test Case Name: Donate


User can view all the latest updates

regarding all mobiles in the Mobile World.

A relevant profile

will open.

Same as Expected

Result.

After user select the mobile for order

from Mobile World

The system will

display the

message.

Same as Expected

Result.

Result:

Pass Fail


68/78


Mobile World 68

Ratings

Test Case Name: Rating


A user can rate other user or visitor at

profile page.

A Profile Page will

open.

Same as Expected

Result.

User clicks on the rate button System will enters

the ratings

information into

database.

Same as Expected

Result.

The user cannot rate the user or visitor

with the same IP address.

The system will

display the

message.

Same as Expected

Result.

Result:

Pass Fail


69/78


Mobile World 69

Test Cases (Admin Panel)

Test Case Name: Delete


After Successful login admin can delete

any user or visitor .

A list of all the user

or visitor/ will be

displayed.

Same as Expected

Result.

Admin clicks on the delete link. The system will

display a

confirmation

message. After

clicking yes button

the record of the

user will be deleted.

Same as Expected

Result.

Result:

Pass Fail


70/78


Mobile World 70

Block/Un Block

Test Case Name: Block /Unblock User


After Successful login admin can block/unblock any user or visitor /_.

A list of all the useror visitor/_s will be

displayed.

Same as ExpectedResult.

Admin clicks on the block/unblock link. The system will

change the state of

the user and insert

the status into the

database.

Same as Expected

Result.

Result:

Pass Fail

News

Test Case Name: News


After Successful login admin add, edit

delete news.

Add news page will

be display.

Same as Expected

Result.

Admin writes the news. With related fields

i-e , news_id subject description

news_link posted_on.

News will be added

into the database.

Same as Expected

Result.

Result:

Pass Fail


71/78


Mobile World 71

White Box Testing

Test type:White Box Testing

Description: White-box test design allows one to peek inside the "box", and it focuses

specifically on using internal knowledge of the software to guide the selection of test

data. Synonyms for white-box include: structural, glass-box and clear-box.

This testing technique is used to do structure analysis, branch coverage, functional

coverage, boundary conditions checking and input conditions are used and run against thestatic code.


Steps Performed for Test:

We have performed the test for login module, if there is no valid user name or passwordthen the user will not log in the website and an error message will be displayed.

Result:

Pass Fail


72/78


Mobile World 72

Unit Testing

Test type:Unit Testing

Description: Unit testing is a procedure used to validate that individual units of source

code are working properly. A unit is the smallest testable part of an application. In

procedural programming a unit may be an individual program, function, procedure, etc.,

while in object-oriented programming, the smallest unit is a method; which may belong

to a base/super class, abstract class or derived/child class.

In unit testing, different modules of the developed system are tested independently. The

purpose is to determine that each module is functioning and to locate errors in the

modules.



We have done the unit test for each individual unit. An example test of module function

Login module is given below:

When user presses the sign in button from top of the page, the new page is opened

properly and user can login to the web site.

Result:

Pass Fail


73/78


Mobile World 73

Recovery Testing

Test type:Recovery Testing

Description: Recovery testing is the activity of testing how well the software is able to

recover from crashes, hardware failures and other similar problems. Recovery testing is

the forced failure of the software in a variety of ways to verify that recovery is properly

performed.

In this testing phase the software is tested that does it come back from faults and resume

to its normal flow. There are conditions like waiting for any specific event and if thatdoesnt happen then the application is crashed.



We have tested the software for recovery test. The software does not crashes if the user

presses any two keys simultaneously or if the user presses any key while the other was

being executed by the program.

Result:

Pass Fail


74/78


Mobile World 74

7.10 Test log

The IEEE std. 829-1998 defines the test log as a chronological record of relevant details

about execution of test cases. The purpose of the test log shown in Figure 7-1 is to share

information among testers, users, developers, and others and to facilitate the replication

of a situation encountered during testing.

IEEE std. 829-1998 for Software Test Documentation

Contents

Test Log Identifier

Description

Activity and event entries

In order for a test log to be successful, the people that must submit data into and

eventually use the log must want to do so. Forcing participants to use a test log when they

dont want to use it is seldom successful. In order to make it desirable, the test log must

be easy to use and valuable to its users.

Since the primary purpose of the test log is to share information rather than analyze data,

we recommend making the log free form, instead of using fields or buttons, which are

desirable in other areas such as defect tracking. If the testing team is small and co-

located, the test log might be as simple as a spiral notebook in which testers and /or

developers can make log entries. Alternatively, it might be more convenient to have a

word-processed document or e-mailed form. If the team members are geographically

separated, the test log would probably be better served in the form of a Web page or

company intranet. Wherever it is, the test log should be easy to access and update. One of

our clients, for example, has a continuously open active window on their monitor where a

thought can be entered at any time.


75/78


Mobile World 75

ID Name Description:

1

2

Tanzeel qazi

Mazhar Abbas

Checks the admin panel.

//


76/78

8 Conclusion and Future Work


77/78

i

8.1 Achievements

We feel very proud after development and implementation of our final project successfully.

Before developing through this project although we have a theoretical knowledge of software

engineering, being students of MBA(IT). We had a very good interaction with our internal

supervisor; Mr. Qamar helped us to develop the system well in time.

During the development of the project we have achieved the following benefits.

Project management and scheduling

How to interact with the user

System analysis and data collection

A good knowledge of system designing and modeling

Latest tools and technologies

Testing strategies

User documentation

During the modeling phase we learnt

Microsoft Visio 2010.

During testing and implementation finding a bug and its fixture was totally new and healthy

experience. One of the very important aspects of the project was how to document our project

properly. We have learnt new tools MYSQL, Macromedia Dreamweaver which will help us a

long way as we will be starting our careers as IT professional.


78/78

Chapter#1 ___________ _______________ Introduction

8.2 Future Enhancement

Since our system only gives efficient coordination to the user or visitor well in future we add

loan feature in our website. We also add mobile WAP feature in our website. And Further we

enhance our project by connecting it other online payment module i-e ; Google check out etc.

tanzeel & abbas project report (repaired)

Documents