(Final)Deleverable I_Final

EM Planner

Deliverable I

1

Punjab University College Of Information Technology, Lahore Page 1

1. Introduction:

Event Management Planner is basically a platform in which people can find services according

to their upcoming events. The site should have all the information about arrangement services

and their packages in which particular services are provided. People who want to organize some

event and the people who make arrangements of these events are treated as our clients.

The Event Management Website will be accessible to all the people who want to make

arrangements and who want to do arrangements. The event organizers will have easy an access

to upload the services they are providing as well as the stuff and variety they have in their

services. They will also post the packages they are entertaining to the customers and the services

which they are providing in these packages.

The people who want to organize the event will have an easy access to upload their requirements

which they want to have in their event .They can also post their budget as well as the services

they want that will be provided within their budget. Moreover they can also post the picture, a

link to website on which some arrangements are being made and they want that arrangements.

The Event Organizer and the one who want to organize both will have his or her own personal

web page that will include a profile. On the profile the user can post their arrangements they

want or the arrangements they provide. The profile also includes all the information of the user

his name, his address, his email, his contact information, his CNIC number. The individual can

contact with one another if they want some information from each other.

The main point is to make such platform in which all the facilities about the arrangements

are provided and more variety of the arrangements and services are given on the single platform.

This will facilitate both organizer and the individuals who want to organize some event and they

will find more options to do whatever they require.

Project/Product Feasibility Report:

This topic determines the feasibility of application “Event Management Planner”. It is

basically measure how particular or beneficially the development of the application system will

be to team, organization and the customers. Event Management Planner is establish to make the

application and website as simple and easy to use as possible so that the user will facilitate and

satisfy and will use our EM planner website for multiple events.

The Feasibility of this website is discussed in detail below:

Technical

Operational

Economic

Schedule

Specification

Information

Motivational

Legal and Ethical

EM Planner

Deliverable I

2


1.1.1 Technical Feasibility:

This application has quick response time with the efficient performance. It is a user friendly

application and it doesn’t make wasteful use of system resources. We are implementing EM

Planner using ASP.NET (Web Application) and MVC. It contains secure log in with their email

address and they can also login with Facebook (Social Web Site). Individual who wants to

organize event will create post in which all the requirement will be given. Notification of New

Post created will be send to all the Organizers who are member of our website after sign up

through Email and Mobile services. The Organizers can bid on that post and can also give his

packages details they are providing on the comment box. The individual who wants to organize

can also comment or contact to the Organizer through chat box or the contact details given at the

profile of the organizer. Then they can interact with each other and can make the successful deal

easily.

1.1.2 Operational Feasibility:

Our application provides the user with the facility of posting their requirements they want

and services they provide using web application. Problems occurred when the internet

connection lost during posting the requirements or services. Session will be maintained so that if

the user reconnects then he/she can proceed further without going back to the start. Traffic load

is also the important factor that has to be managed if the server is too busy. Every phase will be

completely elaborated in the operational level and complete documentation will be provided for

the guidance of user. Hence the application would be scalable, stable, reachable, high capacity,

bandwidth efficient and flexible.

1.1.3 Economic Feasibility:

The project is economically feasible as it only requires a Computer (having Browser)

with sufficient internet connection. The application is reusable and is user friendly.

Cost Estimate:

Development or Acquisition Costs

Database

Interfaces

Operational Costs:

Support of Database, Hardware, Software.

Benefit Estimates:

Tangible Benefits

Application can satisfy the user needs and does not waste any of the system

resources.

EM Planner

Deliverable I

3


With the user of internet a person can search his/her requirements and customers

within no time.

Intangible Benefits

People stay connected at one place and search whatever they need and require.

Up to date new requirements and services.

Best match of desired requirements for events.

1.1.4 Schedule Feasibility:

The total time to complete this project is roughly Six to Eight Months. The project is

divided into different segments/deliverables and different tasks are given to each member of the

group and they are accountable to complete the task before the deadline up. The connectivity of

different modules is scheduled so project is also feasible with respect to schedule.

1.1.5 Specification Feasibility:

Required specifications of software for the completion of this project are:

MVC5

Visual Studio Express 2012

.Net Framework 4.5

Required specifications of hardware for the completion of this project are:

Computer System having browser

Good internet connection

1.1.6 Information Feasibility:

The application acts as an intermediate source between person who wants to do arrangements

and for person who can do these arrangements. The application is reliable as it fulfills

expectations of both, organizer and the individual who want to organize. The application will be

complete in reasonable time as resources required for completion of application are available.

1.1.7 Motivational Feasibility:

There are many motivating factors for creating “EM Planner”.

It will be user-friendly, quick to learn and reliable

Easy interfaces in which customers easily understands the complete flow of application

easily.

Helping people in searching their requirement and needs.

Creating and managing events effectively and in easy way.

Inform and invite people for events using social site or cell phone.

Reminder for new posts so that the user never miss it.

EM Planner

Deliverable I

4


Easy, fast, and advance searching for event arrangements for people who want to

organize events and for organizers who can make arrangements.

1.1.8 Legal & Ethical Feasibility:

This project supports legally and ethically to all customers. We provide our

disclaimer and our privacy policy to customers. This warranty gives user specific legal rights

and user may also have other legal rights that vary from state to state.

1.2 Project/Product Scope: The primarily scope of the project includes developing web app that will be the intermediate

source between the organizer and the individual who want to organize event. Following will be

within the scope of project

There will be facility to post the requirement of event.

There will be option to bid on the post.

There will be option to comment on the post.

Relative post of people invites them via email or Mobile services.

Post would be manageable i.e. user can edit and delete requirements.

There will be facility to set Reminder for events.

1.3 Project/Product Costing:

1.3.1 Project Cost Estimation by Function Point Analysis

No. of Inputs: 15

No. of Outputs: 21

No. of Inquiries: 11

No. of Files: 4

No. of External interfaces: 3

EM Planner

Deliverable I

5


Calculate Count-total:

Information Domain Value

Optimistic values

Most likely

Pessimistic values

Count FP Count

Number of Inputs

6*3=18 4*4=16 5*6=30 15 64

Number of Outputs

9*4=36 4*5=20 8*7=56 21 112

Number of Inquiries

5*3=15 4*4=16 2*6=12 11 43

Number of Files

2*7=14 1*10=10 1*15=15 4 39

Number of External Interfaces

0*5=0 2*7=14 1*10=10 3 24

Count-Total = 283

Data Communication 2

Distributed Data Processing 3

Performance 5

Heavily Used Configuration 3

Transaction Rate 4

On-Line Data Entry 3

End User Efficiency 4

On-Line Update 4

Complex Processing 3

Reusability 4

Installation Ease 5

Operational Ease 5

Multiple Sites 3

Facilitate Change 4

Total = ∑Fj 52

EM Planner

Deliverable I

6


Calculate Function Point:

FP est. = Count Total * [0.65 + 0.01 * (Fj)]

= 283 * [0.65 + 0.01 * (52)]

= 283 *[1.17]

FP est. = 331.11

For our project

Productivity = 37.3 LOC/pm

Labor Rate = 38000 per month

Effort = FP est. / productivity

= 331.11/ 37.3

= 8.88 pm

Now,

Cost/FP = Labor Rate/prod

= 38000/37.3

= 1018.77 Rs/Fp

Total Project Cost = FP est. * (Cost/FP)

= 331.11 * (1018.77)

= 337324.94 Rs

1.4 CPM - Critical Path Method

Activity Name Immediate Predecessor Duration in Weeks

A Initiation None 1

B Requirement

Gathering

A 3

C Feasibility Study B 2

D Costing B, C 2

E Scheduling D 1

F Requirement

Engineering

B , E 2

G Design B , F 3

H Implementation G 5

I Testing H , G 3

J Deployment H , I 2

EM Planner

Deliverable I

7


AON Diagram:

Activity Duration ES EF LS LF TS FS

A 1 0 1 0 1 0 0

B 3 1 4 1 4 0 0

C 2 4 6 4 6 0 0

D 2 6 8 6 8 0 0

E 1 8 9 8 9 0 0

F 2 9 11 9 11 0 0

G 3 11 14 11 14 0 0

H 5 14 19 14 19 0 0

I 3 19 22 19 22 0 0

J 2 22 24 22 24 0 0

J

End

I

H G F

E

D Start A B

C

EM Planner

Deliverable I

8


The Critical Path is as follows:

A B C D E F G H I J

1.5 Gantt chart

EM Planner

Deliverable I

9


1.6 Introduction to Team member and their skill set:

Group Members Skills Muhammad Umair Have good programming, planning skills and management skills.

Rana Umar Have good analysis, programming and research skills.

Arslan Mehmood Have designing, programming and schedule management skills

Muhammad Abubakar Have good analysis, research and software engineering skills.

1.7 Tools and Technology with reasoning:

Visual Studio Express 2012 To create our ASP.NET web application

My SQL This tool will be used to create database for

our web application.

Technologies:

Wi-Fi/GPRS

Internet in mandatory to use our web app

and android app.

Web Browser For Surfing our web application

1.8 Vision Document

This application will provide the option to plan and manage your event. Customer can

select a particular option for the events such as venue, lighting, catering, food etc. This website

will help the customer to find the best providers. Customer can explicitly mention his budget and

demands for a particular section.

This will also facilitate the providers (managers of hotels). They can upload their menu

and can bid on their desired section. For every event the providers will be informed by email,

message to their cell phones and by notification to their account on this website.

EM Planner

Deliverable I

10


Customers and providers both of them have to make their account on this website to avail

the facilities. They will have their own profile and they can maintain it accordingly. On the

providers profile there will be a default section where the customer can comment about their co-

operation and their management facilities. While on customer profile the providers can share

their views about payment or arrangements. For the communication between the customer and

provider website will provide the facility of chat box.

1.9 Risk List

Maintenance & design level risks

Health factor of staff (illness issues).

The size of project is under estimated.

Effects of changes in requirements of project.

Effects of restructuring in organization

Estimation: The development team might not be able to estimate the work time, preventing

customers from deciding priorities effectively. The rate of defects repair is underestimated.

Acceptance: Customer may accept delivery of the system although it does not really meet

their goals

.

Scope: The total features requested may be beyond what the development team can deliver in

the time available.

Software level risk:

Immature technology with rapid changes in standard.

Business logic may differ at presentation layer

Server down.

Development level risks:

Finance: There may be credit risk the question is whether they have sufficient resources

to manage the construction and operation of the project and to efficiently resolve any

problems which may arise. To minimize this risk human resources are important

(Limitation and resources).

Time:

o Limited time available to complete this whole project.

EM Planner

Deliverable I

11


1 Introduction to Requirement Engineering

1.1 Systems Specifications:

The following are the clauses that must be included while describing the system specifications.

Introduction:

This application is developed for the users of PC and laptop users. “EM Planner”

provides users with the facility to manage an event like birthday, marriage, anniversary, Business

Meeting, Seminars etc. PC (Pentium 4 or higher) provides the facility to use “EM Planner”

Application or mobile phones can also use this facility with their internet browser. It gives us

more facilities like online bidding, observe the price comparison, optimal location for event,

minimum cost, best services, best reviews etc.

Existing System

Currently there are many applications those have been built on “Event Management” idea

but the uniqueness of our application is it deals with both Buyers and Sellers. Both Buyers And

Sellers are our clients. Rather than guessing and choosing best Event Planer according to event,

why not provide a platform where client and event organizer directly see and bid on the given

deals and packages according to their requirements.

Scope of the System

The scope of the project can be divided into following phases:

Phase 1: Analysis and Design:

Analyse the requirements for EM Planner

Division of the architecture into small components or modules to specify the design with

the functionalities performed.

Phase 2: Implementation:

Drive the design plan of application and make integration with Event Management

websites for real time Client And Event Organizers Interaction.

Develop the interface of Application for both web app and android app.

Develop databases for the app.

Maintain consistency of components with the repository.

Phase 3: Integration and Testing:

Develop test plans for testing the complete project.

Unit testing of each component.

Test the complete scenario of the application.

Perform application testing.

EM Planner

Deliverable I

12


Summary of Requirements (Initial Requirements)

1) Create Event For Taking Services by authenticated User:

The very first requirement of application is to create event and Specify his/her

requirements via web app. Event Organizer will bid on the post created.

2) Create Event For Giving Services by authenticated Event Organizer:

The very second requirement of application is to create event for giving Services and

Specify his/her Services via web app. Organizers will Bid On “Given requirements”.

3) Invite People: When a client bid on specific deal or an organizer bid on client requirements an Email

and mobile notification will Sent to client and organizer Vice Versa.

4) Database Management: It will be able to manage a list of the upcoming events and managing events

profile. Event Planner history will be saved. Reminder time and date will be kept to

remind invitees on time.

5) Security Authentication:

Security and Privacy will be maintained on user profiles. Event creator profile

will be make completely private and will be visible only to that event organizer who bid

on client's post. This site will also provide complete information related to event

organizers.

Identifying External Entities

Over Specify Entities from Abstract

Pc/ Laptop(Pentium 4 or higher)

Organizer/Clients

Facebook

i) Perform Refinement

Users/Clients(Services Buyer, Services Seller )

Gmail/Hotmail/Yahoo

Mobile Services

EM Planner

Deliverable I

13


1.2 Context Level Data Flow Diagram

EM Planner

Deliverable I

14


1.4 Capture "shall" Statements and the external entities (Actors)

Para#

External Entity

Initial Requirements

1.0 User

A user “shall” make internet connection with cell phone or with the

device having browser.

1.0 User Users “shall” Sign up to the application.

1.0 Application Application “shall” create the account.

1.0 User The user “shall” sing in to the application.

2.0 User User “shall” create events For Getting Services From Event

Organizers.

2.0 Application Application “shall” allow user to create events For Getting Services .

1.0 User User “shall” create Services List As Service Provider For Events.

1.0 User A user ‘shall’ chat to Service Provider and Vice Versa.

1.0 Application An application ‘shall’ notify to client via Mail and SMS

1.0 User A user ‘shall’ see approaching events in News Feed.

2.0 Application An application ‘shall’ alert user about upcoming events.

2.0 Application Application “shall” guide the user to Bid On Related Events.

2.0 Application An application ‘shall’ make scheduling list for upcoming events.

1.0 Application An application ‘shall’ set reminder for upcoming events.

2.0 Application An application ‘shall’ send alert message to remind upcoming event.

2.0 Application An application ‘shall’ guide the Event's map.

1.0 User A user ‘shall’ change account information.

2.0 Application An application ‘shall’ update the account information.

EM Planner

Deliverable I

15


1.5 Allocate Requirements

Para# Initial requirements Use Case Name 1.0 A user “will” make Internet connection, wifi/GPRS UC_internet_connectivity

1.0 A user “shall” create account UC_create_Account

1.0 The Website “shall” allowed the user to create Event UC_Event_creation

1.0 The Website “shall” allowed the user to Edit Event UC_Edit_Event

1.0 The Website “shall” allowed the user to Remove Event UC_Remove_Event

1.0 A user “shall” send the notification message. UC_send_notification

1.0 website “shall” provide the chat facility to your client UC_Chat_Facility

2.0 Website “shall” guide in Event Plan place by Google

Map

UC_Google_Map

2.0 website “shall” provide privacy in user account UC_account_privacy

2.0 A user “shall” place & Bid on your appropriate Event UC_Bid_Event

2.0 Website “shall” provide the incident Event handling UC_Incident_Handling

2.0 Website “shall” provide the View My Events” is a search

result. UC_View_Event

2.0 Website “shall” Timeline visualization and reminder UC_Reminder

EM Planner

Deliverable I

16


1.6 Prioritize Requirements

Para# Rank Initial requirements Use case id # Use Case Name 1.0 Highest A user “will” make Internet

connection, wifi/GPRS

UC_1 UC_internet_connectivity

1.0 Highest A user “shall” create account UC_2 UC_create_Account

1.0 Highest The Website “shall” allowed the user

to create Event

UC_3 UC_Event_creation


to Edit Event

UC_4 UC_Edit_Event


to Remove Event

UC_5 UC_Remove_Event

1.0 Lowest A user “shall” send the notification

message.

UC_6 UC_send_notification

1.0 Medium website “shall” provide the chat

facility to your client

UC_7 UC_Chat_Facility

2.0 Lowest Website “shall” guide in Event Plan

place by Google Map

UC_8 UC_Google_Map

2.0 Highest website “shall” provide privacy in

user account

UC_9 UC_account_privacy

2.0 Highest A user “shall” place & Bid on your

appropriate Event

UC_10 UC_Bid_Event

2.0 Lowest Website “shall” provide the incident

Event handling

UC_11 UC_Incident_Handling

2.0 Medium Website “shall” provide the View My

Events” is a search result. UC_12 UC_View_Event

2.0 Medium Website “shall” Timeline

visualization and reminder

UC_13 UC_Reminder

EM Planner

Deliverable I

17


1.7 Requirements Trace-ability Matrix

Sr

#

Para# Initial requirements Build Use Case Name Categories

1 1.0 A user “will” make Internet

connection, wifi/GPRS

B1 UC_internet_connectivity

Business

2 1.0 A user “shall” create account B1 UC_create_Account

Business

3 1.0 The Website “shall” allowed

the user to create Event

B1 UC_Event_creation

Business


the user to Edit Event

B1 UC_Edit_Event

Business


the user to Remove Event

B1 UC_Remove_Event

Business

6 1.0 A user “shall” send the

notification message.

B1 UC_send_notification

Business

7 1.0 website “shall” provide the

chat facility to your client

B1 UC_Chat_Facility

Business

8 2.0 Website “shall” guide in

Event Plan place by Google

Map

B1 UC_Google_Map Business

9 2.0 website “shall” provide

privacy in user account

B1 UC_account_privacy

Business

10 2.0 A user “shall” place & Bid on

your appropriate Event

B1 UC_Bid_Event

Business

11 2.0 Website “shall” provide the

incident Event handling

B1 UC_Incident_Handling

Business

12 2.0 Website “shall” provide the View My Events” is a search result.

B1 UC_View_Event

Business

13 2.0 Website “shall” Timeline

visualization and reminder

B1 UC_Reminder

Business

EM Planner

Deliverable I

18


1.8 High Level Use case Diagram:-

EM Planner

Deliverable I

19


=

Documents

(Final)Deleverable I_Final