1.1 Introduction: 1.2. Project Title: 1.3. Project ...€¦ · DCS&IT- UOS-Project Coordination Office Version: 1.0 Final Project Deliverable Guide Date: October 10, 2012

DCS&IT- UOS-Project Coordination Office Version: 1.0

Final Project Deliverable Guide Date: October 10, 2012

© Department of Computer Science & Information Technology.

1

1.1 Introduction:

We are proposing a platform which will manage the advertisements on different areas.

Time is money so efficient way of representing advertisements to the in such a way that

he should see his relevant advertisement, a automatic log will be maintained regarding

each and his impression will also be recorded by keeping an eye on his clicks.

Placements of advertisements are in such a way that can attract maximum impression of .

A report will also be generated on the basis of clicking.

1.2. Project Title:

Ad-servers (a smart way of generation of money)

1.3. Project Overview statement:

We will develop a system which manage and display many different types of Ads. This

will help any client to publish his ad on the social plate form. As the advertisement plays

a vital role to make people aware of one’s business. And ad sever will manage all this.

Packages and clicking information of advertisement are also available, when maximum

limit of particular ad will be reached, it will automatically expire.

We also provide platform for publishing advertisements. This platform facilitates online

accommodation for students of university of Sargodha. Students can apply online for

accommodations through provided online application form. Administrator will check

vacancy and a lot rooms.

Project Overview Statement Template Project Title: ad servers (a smart way of generating money)

Project Manager: Madam Atifa

Project Members:

Name Registration # Email Address Signature

M Naeem Khan BSSEF09E021 [email protected] Naeem

Sameer Sheikh BSSEF09E059 [email protected] Sameer

Project Goal: our main goal is to make a system which will control the advertisements and make people

aware of some advertised thing in very less time. The other goal of this project is to design and

implement a system that would provide “Room Allocation and Mess System” to the management, which

would help them in decision-making. This plat form also provides space for publishing ADS.

mailto:[email protected]

mailto:[email protected]




2

Objectives:

Sr.#

1 Develop platform for advertisement.

2 Advertisements will be managed through authenticated administrator.

3 The proposed system would be friendly.

4 The proposed system would minimize redundancy of data, which frequently occurs in non-

computerized systems.

5 We will automate accommodation and mess process of university.

6 The computerized Room Allocation and Mess System would have capability to maintain

information.

Project Success criteria:

If our project achieves all our goals and objectives it comes to a point of success. We must deliver the

project within time. The project deliverables have must meet the client expectation. Collectively as a team,

success is easy to achieve with proper guidance.

Assumptions, Risks and Obstacles:

We will research many new things which this system should have.

If we can’t collect data according to the needs of project and we will have to learn tools that used to

develop a ad server system then deadline may exceed.

Some features of specification missed in design.

Some needed attributes or operation missed from various objects.

Organization Address (if any):

Type of project: Research Development

Target End s: Clients

Development Technology: php dotnet

Platform: Web based Distributed

Desktop based Setup Configurations

Others ____________________

Approved By:

Date:

1.4. Project Goals & Objectives:

Our goal is to make an ad server system which is now recommended for almost type of

business to improve or make its publicity. When we make any website there is a question

arises in our mind that how can we make money from this website then we allow

advertisements. Our task is to maintain these advertisements in an organized and efficient

way so that we can obtain maximum impression of . An automatic log of will be

maintained and there will be record of every on the basis of his actions which he will

perform on advertisements. Basically we are monitoring that what he is going to do

regarding advertisements and we have to capture these actions

Our system will be reliable and free of ambiguities. It tells the effective

controlling techniques to control any sort of problem Tools and technology using for this

system is easy to use and understand.




3

1.5. High-level system components:

The basic supporting actors are software requirements, software design, software

implementation and software deployment. Software testing is also a high level system

component. Our system should be friendly and more reliable. These are high-level

components related to our project.

1. Data Collection

2. Knowledge base

Inputs: 1. requests for advertisement.

2. Student request for accommodation.

Outputs:

1. Publish ads.

2. Record clicks per ads.

3. Maintain record of students.

4. Room allocation.

Data storage: Database containing records of advertisements and student details.

1.6. List of optional functional units:

Our system should have high features and strong capabilities. Usability, reliability,

performance and supportability are the necessary features to make a service quality

system.

• Performance of our system.

• Usability of system.

1.7. Exclusions:

A list of the functional units are mentioned here which will not discuss in our project.

1. Impressions of ads

2. Providing the IP addresses regarding clicking with recorded time

3. It would be able to generate output reports according to the requirements of the

management.




4

1.8. Application Architecture:

1.9. Gantt chart:

The Gantt chart enumerates the activities to be performed on the vertical axis and their

corresponding duration on the horizontal axis. It is possible to schedule activities by

either early start or late start logic. In the early start approach; each activity is initiated as

early as possible without violating the precedence relations. In the late start approach;

each activity is delayed as much as possible as long as the earliest finish time of the

project is not compromised.

Based on the Work Breakdown Structure (WBS), a timeline or Gantt chart showing the




5

allocation of time to the project phases or iterations should be developed. This Gantt

chart would identify major milestones with their achievement criteria. It must contain

duration estimation of all the necessary activities to be carried out during the project

development along with the human resources responsible for the respective tasks.

Activity dependencies are also required to be mentioned in it.

Sample Gantt chart

Figure 1: Gantt Chart

1.10. Hardware and Software Specification:

For our project following hardware specification will be required:

1. 512mb RAM

2. 40Gb Hard

3. 2.80GHZ processor

And software will be required:

1. Window XP or above

1.11. Tools and technologies used with reasoning:

1. Adobe dreamveawer cs5

2. php

3. Xamp

4. mysql.




6

Chapter 2: First Deliverable

2.1. Introduction

First deliverable is all about planning and scheduling of project. This deliverable must

contain following artifacts:

a. Project Feasibility

b. Project Scope

c. Project Costing

d. Task Dependency Table

e. Critical Path Method Analysis (CPM Analysis)

f. Gantt Chart

g. Introduction to team members

h. Tasks and member assignment table

i. Tools and Technologies

j. Vision Document

k. Risk List

l. Product Features

2.2. Project/Product Feasibility Report

When a project is started the first matter to establish is to assess the feasibility of a

project or product. Feasibility means the extent to which appropriate data and information

are readily available or can be obtained with available resources such as staff, expertise,

time, and equipment. It is basically used as a measure of how practical or beneficial the

development of a software system will be to you (or organization). This activity recurs

throughout the life cycle.

There are many types of feasibilities:

• Technical

• Operational

• Economic

• Schedule

• Specification

• Information

• Motivational

• Legal and Ethical

2.2.1. Technical Feasibility

The application tool which we are used on the front and back end of

the system to be developed are given below:




7

1: Window

2: Adobe Dreamweaver

3: HTML

4: CSS

5: JAVA SCRIPT

6: PHP

Our technical feasibility of Ad server is complete. And all project members are

capable to use these technologies and languages and are capable to produce our

respective project.

2.2.2. Operational Feasibility

The facilities that our system is providing are demanding by the current market. This

project will be a great help for the personnel (student) in room allotment and Ad

management procedures. Client really feels the need of the computerized system since

there is no proper record keeping and it is difficult for the client to manage under heavy

load. Manual generation of statistical reports are generated which is not an efficient way.

The proposed system will automate most of their daily, time consuming tasks and

therefore it should not change their pathways or information flow, thus offering easiness

as it save lots of time and handle more number of s, and can make money as well in smart

way. So proposed system is truly feasible.

2.2.3. Economic Feasibility

i. Cost feasibility:

The development cost of this system is the only understanding and development of

technique and algorithms but its maintenance cost will be high because it will be

necessary to update the Ads or to add new Ads into the database or

2.2.4. Schedule Feasibility

The total time to complete the project is roughly seven months we

have divide into segment and Tasks are given to each member of the group and they are

accountable to complete the task before Dead line up. As we mentioned the time period

in the Gantt chart, with official meetings and within resources we will complete our

project in that given period of time. so project is also feasible with respect to schedule

2.2.5. Specification Feasibility

The required specification of hardware and software for this

project is feasible. The software specification is internet explorer/chrome/Firefox. And

hardware specification is hard disk min 40 GB, RAM, Processor. These all are available.

2.2.6. Information Feasibility

We have covered all the information regarding to the Ad SERVER

as it is based on website integration. This system will allow to have different information

for several advertisements.




8

2.2.7. Motivational Feasibility

The probability that the organization is sufficiently motivated to support the

development and implementation of the application with necessary participation,

resources, time etc

1: The web application is intended to provide complete solution for the s through single

gate-way using the internet as a sole medium.

2:It will be friendly and reliable.

3:Easy interface and predictable service system in which the understand this application

and gets all information.

2.2.8. Legal & Ethical Feasibility

This project supports legally and ethically to all clients. We provide

a privacy policy to all client and staff. This application provides specific legal right to all

the staff. This system will keep the record of s highly confidential.

2.3. Project/Product Scope:

Our goal is to make an ad server system which is now

recommended for almost type of business to improve or make its publicity, and online

room allocation system for the student of university of Sargodha. Our task is to maintain

these advertisements in an organized and efficient way so that we can obtain maximum

clicking of and maintain the record of all student registered for accommodation. There

will be record of every on the basis of his actions which he will perform on

advertisements. Basically we are monitoring that what he is going to do regarding

advertisements and we have to capture these actions




2.4. Project/Product Costing

2.4.1. Project Cost Estimation By Function Point Analysis

Type of

Components Complexity of Components

Low Average High Total External Inputs 2x 3 =6 2x 4 = 8 7x 6 =42 56

External Outputs 5x 4 =20 3 x 5 = 15 5x 7 =35 70

External Inquiries 2x 3 =6 4 x 4 = 8 2x 6 =12 26

Internal Logical Files 0x 7 =0 1x 10 = 10 0x 15 = 10

External Interface Files 2 x 5 = 10 9x 7 =63 2x 10 =20 93




9

Once these data have been collected, a complexity value is associated with each count.

Organizations that use function point methods develop criteria for determining whether a

particular entry is simple, average, or complex. Nonetheless, the determination of

complexity is somewhat subjective.

To compute function points (FP), the following relationship is used:

FP est. = unadjusted function point*VAF = 84*0.31

= 26.73

Where count total is the sum of all FP entries obtained from above figure and (Fi) is

value adjustment factor (VAF) is based on 14 general system characteristics (GSC's) that

rate the general functionality of the application being counted. Each characteristic has

associated descriptions that help determine the degrees of influence of the characteristics.

The degrees of influence range on a scale of zero to five, from no influence to strong

influence.

1. Data communications 5

2. Distributed data processing 0

3. Performance 5

4. Heavily used configuration 0

5. Transaction rate 3

6. On-Line data entry 4

7. End- efficiency 4

8. On-Line update 0

9. Complex processing 2

10. Reusability 4

11. Installation ease 5

12. Operational ease 5

13. Multiple sites 0

14. Facilitate change 4

TOTAL 41

VAF=0.65+count total*0.01

= 0.65+41*0.01

=0.31

2.4.2. Project Cost Estimation by using COCOMO’81 (Constructive Cost Model)

The level include in education management is EMBEDDED




10

1. Semi-Detached:

Our application is semi-detached because we are dealing with two

domains.

Basic COCOMO

Type Effort Schedule

Semi-Detached PM= 3.0 (6)1.12 TD= 2.5(PM)0.35

=22.21 =7.4 PM= person-month (effort)

KLOC= lines of code, in thousands

TD= number of months estimated for software development (duration)

2.5. Task Dependency Table

T1: Finalizing the project

T2: Selection of title

Activity: Proposal

T3: Preparing the proposal

T4: Submit proposal

T5: Requirement gathering

Activity: Design

T6: Interface

T7: System Design

T8: Design verification

Activity: Development

T9: Coding

T10: Testing and implementation

T11: Correcting errors

T12: Closing the project

T13: Project end

Task Duration (days) Dependencies

T1 2

T2 3

T3 6

T4 11

T5 10 T3

T6 21 T5

T7 30 T5,T5

T8 45

T9 18 T7




11

T10 22 T9

T11 17 T9, T10.

T12 13 T1

T13 24

2.6. CPM - Critical Path Method

A: Software concept

B: Requirements Analysis

C: Design

D: Algorithm

E: Development

F: Testing

Activity Immediate Predecessor Duration (Weeks)

A None 5

B A 3

C B 8

D B 7

E B,C,D 7

F E 4




12

Network Diagram for the above-mentioned activities




13

Activity Duration ES EF LS LF TS FS

A 5 0 5 0 5 0 0

B 3 0 3 3 6 3 2

C 8 5 13 5 13 0 0

D 7 5 12 6 13 1 1

E 7 0 7 6 13 6 6

F 4 13 17 13 17 0 0

The parameters and slacks are calculated as follows:

2.7 Gantt Chart: Method:




14

.

2.8. Introduction to Team member and their skill set

TEAM MEMBERS SKILLS

M1: Muhammad Naeem Khan designing, coding, documentation

M2: Abu Sameer designing coding, documentation

2.9. Task and Member Assignment Table

A table should be formed which consists of a list of tasks and correspondingly allocation

of members to that task. The basic aim of this table would be an indication of the amount

of work the members would be performing.

Example for Task Durations and Dependencies, Activity Network Diagram, Gantt chart,

and Allocation of People to Activities

TASK

TASK NAME

DURATION(days)

DEPENDENCIES

T1 Gathering req

60

T1(M1,M2)

T2

Research about project

14

T1(M2)

T3

Finalize requirments

21

T1,T2(M1,M2)




15

T4

Documentation

22

T3(M1)

T5

Project porposal

16

T4(M2)

T6

Test plan

11

T4(M1)

T7

SRS

16

T4,T5(M1,M2)

T8

Analysis of tools

5

T7(M1)

T9

Designing phase

52

T8(M1,M2)

T10

Implementation

61

T7,T9(M1,M2)

T11

coding

70

T10(M1,M2)

T12

closing

31

Depend on all

Consider the set of activities shown in figure. This table shows activities, their duration,

and activity interdependencies. From figure, you can see that Task T3 is dependent on

Task T1. This means that T1 must be completed before T3 starts. For example, T1 might

be the preparation of a component design and T3, the implementation of that design.

Before implementation starts, the design should be complete.

Task durations and dependencies




16

FIG01 Task durations and dependencies

Activity Bar Chart




17

Allocation of People to Activities

TASK

ENGINEER

Gathering requirements

Naeem, Sameer

Research papers

Naeem

Finalize requirements

Sameer

Documentation

Naeem, Sameer

Project porposal

Naeem, Sameer

Test plan

Naeem, Sameer

SRS

Naeem

Analysis of tools

Naeem, Sameer

Designing phase

Naeem

Implementation Naeem, Sameer

Coding Naeem, Sameer

Closing Naeem




18

2.10. Tools and Technology with reasoning

The application tools, which are to be used on front and back end of the system to be

developed, are given below with reasons.

1. Adobe Dreamweaver

We use Dreamweaver because this tool is efficient and friendly

JavaScript, CSS and HTML Coding

2. PHP

PHP is a query language. We use this to store, retrieve and delete data

from database.

3. Java Script

Java script is an object oriented language. We use this in form validation.

4. CSS

We use CSS for designing, to make style Sheets etc.

5. HTML

We use html to align something.

2.11. Vision Document

Our goal is to make an ad server system which is now recommended for almost type of

business to improve or make its publicity. When we make any website there is a question

arises in our mind that how can we make money from this website then we allow

advertisements. Our task is to maintain these advertisements in an organized and efficient

way so that we can obtain maximum impression of . An automatic log of will be

maintained and there will be record of every on the basis of his actions which he will

perform on advertisements. Basically we are monitoring that what he is going to do

regarding advertisements and we have to capture these actions




2.12. Risk List

2.12.1 Security:

As our application is based upon clicks so it may be possibility that

virus or external threats may affect it

2.12.2 Schedule:

Our application consist of two domains so it can be overrun.

2.12.3 Loadshading:

We are developing this in a environment where electricity problem

So it may also affect our development.

2.12.4 Complex:




19

There are two types of domains involved in our project on is easy

other is new so it can be complex while taking these two domains

side by side

2.12.5 Experts:

We may face expert risk also because we are doing this as our first

Project of this level.

2.12.6 Attraction for customer:

It may be possible that if customer might not be interested in our a

Domain so we cannot achieve our benift as we are expecting.

2.13. Product Features/ Product Decomposition

The main feature of task is to maintain these advertisements

in an organized and efficient way so that we can obtain maximum impression of . An

automatic log of will be maintained and there will be record of every on the basis of his

actions which he will perform on advertisements. Basically we are monitoring that what

he is going to do regarding advertisements and we have to capture these actions.

➢ Provide a platform for advertisement of business.

➢ Provide online room accommodation system.

➢ Display information about different areas of city.

➢ Categorize the hostel in different room types.

➢ Provides detail(contact,location,phone and address) information related to

particular hostel.

➢ Customer will advertise advertisement on the application.

➢ Application will provide advertisements impressions for customer’s business.

➢ Advertisements will be clicked.

➢ Clicked advertisements will provide further detail of relevant add.

➢ User will apply for hostel.

➢ Room will be allotted to him.

Admin View Requirements

➢ Login will be provided for administrator.

➢ Separate control panel will be provided for the admin.

➢ Admin will upload customer’s business detail.




20

➢ Admin will delete particular detail.

➢ Admin will manipulate any information related to customer.

➢ Different advertisements will change after specific interval of time.

➢ Admin will approve advertisements.

➢ Admin will approve room.

➢ Admin will add , delete and edit record of students.

Chapter 3: Second Deliverable For Object Oriented Approach




21

3.2.6. Capture "shall" Statements:

Para

#

Initial Requirements

1.0 GUI “shall” be provided.

1.0 The information regarding the hostels “shall” be provided.

1.0 A platform “shall” provide by the admin for the advertisement of any business.

1.0 Application “shall” provide detail information regarding particular hostel.

1.0 Application “shall” display the fee and rent of hostels.

1.0 Application “shall” categorize the different hostels according to room.

1.0 System “shall” provide detail (contact, location, phone, fax, address ) / information

about particular hostel.

1.0 Form page in the application “shall” be provided to customer for posting detail.




22

1.0 Advertisment details “shall” be uploaded against relevant category.

1.0 Admin “shall” search any details

2.0 Admin “shall” provide the payment criteria /procedure through paypal.

2.0 Customer “shall” make payment through cash or credit card.

2.0 System “shall” generate invoice, confirmation receipt and finally will place order

2.0 Customer “shall” advertize business on application.

2.0 Application “shall” provide advertisement impression for the customer’s business.

2.0 Advertisement “shall” be clicked also.

3.0 Clicked advertisements “shall” provide further detail of relevant Ads.

3.0 Clicked advertisement “shall” lead to the particular URL of advertisement.

3.0 Login “shall” be provided for the administrator.

3.0 Separate control panel “shall ” provide for the admin.

3.0 Admin shall upload customers business detail.

3.0 Admin shall update customers business detail.

Admin shall delete customers particular detail.

Admin shall manipulate any information related to customer.

Different Ads shall be change after different interval of time.

Admin “Shall” edit, delete or add record of students.

Admin “Shall” allocate room.

Admin “Shall” approve or reject advertisements.

Admin “Shall” approve or reject hostel request.




23

Use Cases:

<Use-case001: View Categories > Actors: , Admin,

Feature: Functionality to view hostel and information.

Use case Id: Use-case001

Pre-condition: The platform should be open.

Scenarios:

Step# Action Software Reaction

1. will open webpage System displays the webpage.

2. will view the information regarding

hostels.

System will show all the information

3. will view different categories of

hostel rooms.

System displays the webpage.

4. will select particular category. System will display detail of that category.

5. Customer will view the information

of selected category.

System show the information.

Alternate Scenarios: Use-case002

Post Conditions:

Step# Description

1. successfully gets information about hostel and its room’s categories.

Use Case Cross Reference: None

Interface Reference: None

Concurrency and Response:

Number of concurrent s:1

Expected response time of the use case: 4 sec




24

<Use-case002:Post Advertisement> Actors: User

Feature: Functionality to post Ad of different domains.


Pre-condition: wants to upload Ad by giving domain.

Scenarios:


1. User view select the webpage System will display the webpage

2. User will select the post

advertisement option.

System will display the form for posting

advertisement.

3. User will enter detail accordingly

and press ok

System will verify the details.

4. User will pay dues through payment

criteria.

System will provide account ID for the

payment.

Alternate Scenarios: Use-case001

Post Conditions:

Step# Description

1. Ad will be posted to admin and ready to be ready to uploaded on platform.









25

<Use-case003: Upload Ads> Actors: Admin, User,

Feature: Functionality to upload the Ads on the platform / webpage


Pre-condition: User has submitted the form to request for the Ad.

Scenarios:


1. Admin will upload the

Advertisement.

Application will displayed advertisement on

specific panels on the page.

2. User will view his posted

advertisement on the main platform.

Application will display different Ads

iteratively

3. will click/select particular Ads. Application will display the detail of that

particular Ad.

Application will record number of clicking on

specific Ad.

Alternate Scenarios: None

Post Conditions:

Step# Description

1. Admin successfully upload Ad.









26

<Use-case004: Room Allotment> Actors: Admin, User,

Feature: Functionality to allocate room in hostel


Pre-condition: User has submitted the form to request for the room allocation.

Scenarios:


1. User will request for room

allocation.

Application will provide a form to fill.

2. User will fill the form. Application will validate the form and send to

admin for approval.

3. Admin will approve the particular

request.

Application will a lot the room

Application will maintain the record of

student.


Post Conditions:

Step# Description

1. Admin successfully upload Ad.









27

<Use-case005: Modify detail> Actors: Administrator.

Feature: Functionality to modify detail.


Pre-condition: Details had been uploaded.

Scenarios:


1. Admin will open the webpage Application will display the webpage.

2. Admin will select the login option Application will display the login form.

3. Admin will enter name and

password

Application will verify the login.

Application will show the admin control

panel.

4. Admin will select, delete, edit option

from the panel

Application will show all the record stored in

database.

5. Admin will select the particular

record option from panel

Application will delete the selected record and

update the record.

6. Admin will select modify detail

option

Application will display customer detail for

manipulation.

7. Admin will select particular record

for editing,

Application will fetch and display record in

the text field for modification.

8. Admin will update the record Application will update the record in the

database.


Post Conditions:

Step# Description

1. Admin successfully modify details.









28

2.1




29

Chapter 4: Third Deliverable For Object Oriented Approach




30

4.1. Introduction:

Third deliverable is all about the software design. In the previous deliverable, analysis of

the system is completed. So we understand the current situation of the problem domain.

Now we are ready to strive for a solution for the problem domain by using object-

oriented approach. Following artifacts must be included in the 3rd deliverable.

1. System Sequence Diagram

2. Sequence Diagram

3. Collaboration Diagram

4. Operation Contracts

5. Design Class Diagram

6. State Transition Diagram

7. Data Model

Now we discuss these artifacts one by one as follows:




31

4.3. System Sequence Diagram

4.4. Sequence Diagram

Admin:




32




33




34

4.5. Collaboration Diagram

4.6. Operation Contracts

Name: Post Advertisement

Responsibilities: Functionality is to upload advertisement in relevant category.




35

Cross References: Use Cases001-002

Exceptions: Form may not properly fill.

Preconditions: Clients wants to post advertisement

Post conditions:

• The Ad will upload successfully

Name: View category

Responsibilities: Functionality is to view category.

Cross References: none.

Exceptions: category may not be there

Preconditions: should come on website to view

Post conditions:

• The category will be displayed

4.7. Design Class Diagram




36

3.8. State chart diagram




37

Admin

Documents

1.1 Introduction: 1.2. Project Title: 1.3. Project ...€¦ · DCS&IT- UOS-Project Coordination Office Version: 1.0 Final Project Deliverable Guide Date: October 10, 2012