Вы находитесь на странице: 1из 28

Business Application Analysis and Design PROJECT REPORT

Submitted to: Sir, Ayub Latif

SUBMITTED BY: Hassan Ali (54980) Taha Yaseen (54488)

ACKNOWLEDGEMENT

With the name of ALLAH 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 Latif who 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

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 ............................................................................. 17 DEPLOYMENT DIAGRAM ....................................................................... 19 USD Chart: .................................................................................................... 21 Feature Traceability Chart: ........................................................................... 21 Gant Chart: .................................................................................................... 22 Pert Chart: ..................................................................................................... 22 SCREEN SHOTS OF FORMS ..................................................................... 23

PROJECT DESCRIPTION:

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 running through 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, and create 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.

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

CLASS DIAGRAM

USECASES DIAGRAM

STUDENT USE CASE DIAGRAM:

USE CASE ANALYSIS

Use case name


Actor

Description

DEFINE SALES PERSON AND ORDER Administrator The use case describes the process of sales person and sales order of the new customer.

Typical course events

Actor Action
Step 1: This use case initiated when CRM Manager wants to initiate the customer. Step2: CRM Manager logins the system enters the order. Step 4: Enters customer information.

System Response

Step3: System saves the order with customer number. Step5: System save customer information

Pre-condition Post condition Assumptions

Only a CRM Manager create a customer. CRM Manager can update customer information None at this time

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.

Sub Flow:

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.

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.

SEQUENCE DIAGRAMS

Create Campaign:

Create Leads:

ACTIVITY DIAGRAMS

DEPLOYMENT DIAGRAM

USD Chart: Process Work Flows


Mapping Requirements Gathering Analysis & Designing Implementing Testing Deploying

Inception Elaboration Construction Transition

Feature Traceability Chart:

Create Quotation Generate Lead

Function

Manage Quotation Manage Campaign Sales Person And Order CR Manager Sales Person

Actor

Gant Chart: Flow Work (SECTION)


Prototype Use Cases Functional & NonFunctional Requirements Feature Traceability Chart Activity Diagram Flow of Events USD Chart Class Diagram Realization Sequence Diagram Coding Testing User Acceptance

1 2 3

4 5 6 7

9 10 11 12 13 14 15

Pert Chart:
3-4 Section Definin g Syste m 1-2 Section Section 1-2 Section Prot o Type

7-13 Section Codin g

13-14 Section

Testin g

15 Section User Accepta nce

Functional & non Functional Requirements

Use Case s

3-5 Section 5-7 Section

Flow of Event s

Diagra ms

SCREEN SHOTS OF FORMS

Login:

Home:

Leads:

Potentials:

Quotations:

Вам также может понравиться