taha baad final report

8/13/2019 Taha Baad Final Report

1/28

Business Application Analysis and Design

PROJECT REPORT

Submitted to: Sir, Ayub Latif

SUBMITTED BY:

Hassan Ali (54980)

Taha Yaseen(54488)


2/28

ACKNOWLEDGEMENT

With the name ofALLAH who is most loving and merciful.

All praises and thanks to Almighty Allah. The Lord and Creator of this universe

by whose power and glory all good things are accomplished. He is also the most

merciful, who best owed on us the potential, ability and an opportunity to work on

this project.

We would like to extend our sincere thanks to our respected teacher Sir Ayub

Latifwho is well known for his vast expertise, for giving us an opportunity to

learn and enhance our skills through this project.Indeed, without his kind

guidance we may not be able to even start this project.

TABLE OF CONTENTS

ACKNOWLEDGEMENT ..................................................................................... 2


3/28

PROJECT DESCRIPTION: ............................................................................... 3

OVER VIEW SYSTEM:....................................................................................... 4

REQUIRMENT BY CLIENT:.................................................................................... 4

SYSTEM:.................................................................................................... 4

KEY OBJECTIVES............................................................................................ 4

REQUIREMENTS:........................................................................................... 4

PROBLEM:.................................................................................................. 4

PROPOSAL BY VENDOR:...................................................................................... 5

KEY FUNCTIONS:........................................................................................... 5

CLASS DIAGRAM ........................................................................................ 6

USECASES ..................................................................................................... 8

DIAGRAM ...................................................................................................... 8

STUDENT USE CASE DIAGRAM:.............................................................................. 9

USE CASE ANALYSIS ............................................................................... 10

SEQUENCE DIAGRAMS ........................................................................... 14

Create Campaign:.......................................................................................... 15

Create Leads:............................................................................................... 16

ACTIVITY DIAGRAMS ............................................................................. 17DEPLOYMENT DIAGRAM ....................................................................... 19

USD Chart: .................................................................................................... 21

Feature Traceability Chart: ........................................................................... 21

Gant Chart: .................................................................................................... 22

Pert Chart: ..................................................................................................... 22

SCREEN SHOTS OF FORMS ..................................................................... 23

PROJECT DESCRIPTION:


4/28

The project is all about how we collect the information from client and give them

a system designed and analyzed according to their requirements. Here we have

discussed and studied an CRM and how are the things managed in this old system

and made proposed recommendations for their old system.

OVER VIEW SYSTEM:

It provides an efficient and effective tool for organization to operate. It has been

designed to manage and look after all over processing of the customer. It is

capable of managing campaign detail, lead detail, potential detail and Quotation

detail. It provides very helpful report for managing the institute in easy and

accurate way. It is a system to consolidate the vast flow of information runningthrough the organization.

REQUIRMENT BY CLIENT:

SYSTEM:

CUTOMER RELATIONSHIP MANAGEMENT SYSTEM.

KEY OBJECTIVES

The key objective is to know the ADD a customer and customer information, andcreate campaigns, leads, potentials and quotations. Manage the all data records

and data.

REQUIREMENTS:

There previous system consisted most of the paper work, now they have asked

us to make their environment paperless. NO change in current infrastructure

required. To have up-date records, they wanted to know about their defaulters all

records.

PROBLEM:

There are two problem that occurred in his organization, first is that he was

unable to know about the defaulters and second is that due to the scarcity of time

he was unable to manage the organization.


5/28

PROPOSAL BY VENDOR:

Along with the fulfillment of our client we have proposed additional

functionalities for their system:

KEY FUNCTIONS:The project includes the following functions:

Add , update and delete the information Store and manages campaign information Store and manages lead information Store and manages potential information Store and manages quotation information View the information Collection of detailed information of specific individual


6/28

CLASS

DIAGRAM


7/28


8/28


9/28

STUDENT USE CASE DIAGRAM:


10/28

USE CASE

ANALYSIS


11/28

Use case name DEFINE SALESPERSON AND ORDER

Actor Administrator

Description The use case describesthe process of salesperson and sales orderof the new customer.

Typical courseevents

Actor Action System Response

Step 1:

This use case initiatedwhen CRM Manager

wants to initiate thecustomer.Step2:

CRM Manager loginsthe system enters theorder.Step 4:

Enters customerinformation.

Step3:System saves the order withcustomer number.

Step5:

System save customerinformation

Pre-condition Only a CRM Managercreate a customer.

Post condition CRM Manager canupdate customerinformation

Assumptions None at this time


12/28

USE CASE LOG ON

Preconditions:The Precondition of the following Use-Case is the existence of the User in the

System. User should be recognized and should be given an ID and

Password.

Main Flow:The System Will Verify the Password and ID, And Log the User on to the

System.

Alternative Flow:The System will be terminated if the User is not recognized.

USE CASE Manage Campaign

Preconditions:

The Precondition of the Use Case is that user should be Valid and Must

Logon to the System.

Main Flow:The System will manage the campaign and create and records all the

necessary information.

SubFlow:The System will allow user to see the previous or recorded details of

campaign.

Alternative Flow:The system will be exceptions when the user enters any wrong details.


13/28

USE CASE Create Leads

Preconditions:The user should be logged on to the System & must be Valid.

Main Flow:The System will generate documents for user and helps the user by

providing all the campaign convert into leads.

Sub Flow:

The System will Check the Availability of campaign and allows generation of

documents as per requirements.

Alternative Flow:

The User can update or delete the information of the Documents.


14/28

SEQUENCE

DIAGRAMS


15/28

Create Campaign:


16/28

Create Leads:


17/28

ACTIVITY

DIAGRAMS


18/28


19/28

DEPLOYMENT

DIAGRAM


20/28


21/28

USD Chart:

ProcessWork Flows

Inception Elaboration Construction Transition

Mapping

RequirementsGathering

Analysis &

Designing

Implementing

Testing

Deploying

Feature Traceability Chart:

Function

Create Quotation

Generate Lead

Manage Quotation

Manage Campaign

Sales Person And

Order

CR Manager Sales Person

Actor


22/28

Gant Chart:

Flow Work(SECTION)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Prototype

Use Cases

Functional & Non-FunctionalRequirements

Feature

Traceability Chart

Activity Diagram

Flow of EventsUSD Chart

Class Diagram

Realization

SequenceDiagram

Coding

Testing

User Acceptance

Pert Chart:

Definin

g

Prot

oCodin

Use

Case

Functional & non

Functional

Flow

of

Testin

Diagra

3-4

7-13 13-14

1-2

1-2

3-5 Section

5-7

15 Section

User

Accepta


23/28

SCREEN

SHOTS OF

FORMS


24/28

Login:


25/28

Home:


26/28

Leads:


27/28

Potentials:


28/28

Quotations: