dibya_project specification form (1)

7/28/2019 Dibya_Project Specification Form (1)

1/22

Final Year Project Sales and Customer Tracking System

Student ID :PTL00782247

Intake ID :PTL00782

Student Name :Dibyajyoti Deka

Supervisor :Prof. Muthukumar

Assessor :Miss Aditi Mittal

Email :[email protected]

Cont :+919017674187

PROJECT SPECIFICATION FORM (PSF)

A.Project TitleSales and Customer Tracking System

B.Brief description on project background

Its a well known fact that the productivity and the success of an organization dependsubstantially on its Human Resource and the infrastructure. The better the HR and the infrastructure

better are the prospects for the company. Though HR and infrastructure are very important for

organizations, there seems to be a little less emphasis on assessing and evaluating them on various

scales and parameters. Organizations find it very hard to assess and evaluate their work force and

thus there are chances that the organization might end up with a weak work force. Usually the

organizations dont have enough time and also the tools to assess their workforce and rather they go

for the normal feedback which is not that fruitful and also often dont present the clear picture. With

the immense amount of capital and pride at stake there is a need to find out a very flexible and

efficient way of assessing and evaluating the workforce for having a very productive, efficient and

deserving work force. Organization most valued assets is its work force that is why it is so

important to manage your human capital efficiently and effectively and also data warehouse. A data

warehouse is a subject oriented, integrated, time variant and non volatile collection of data in

support of managements decision making process.
mailto:[email protected]:[email protected]:[email protected]:[email protected]


2/22


May also be defined as:

o A decision support database that is maintained separately from the organization's operational

database.

o Support Information Processing by providing a solid platform of consolidated, historical data

for analysis.

A centralized data warehouse is a single physical database that contains all of the data for a specific

functional area, department, division, or enterprise. Data warehouses are usually dedicated to the

processing of data and decision support queries. These queries are much more complex and

consequently the response time is much higher.

The problem context mentioned above caters for an efficient and automated Sales and customer

tracking System which different organizations could use to assess and evaluate their work force on

various scales and parameters. The system could help in many ways and could turn out to be a

revelation for the organizations and also for the employees.

The system would lead to several benefits. I am dividing the benefits in two categories- tangible

benefits and intangible benefits.

The tangible benefits of the proposed system would be:

1. The first and the foremost advantage of the system is that it is going to quantify the qualities

of the work force.

2. The organizations would have the opportunity to assess and evaluate their work force on

different scales which would allow them to take strategic decisions. The company would be

able to take decisions with lot more conviction and thus the chances of failure of project

would go down substantially.

3. One more important benefit of this sale and customer tracking system is that it can store

huge amount of data everyday.

4. This system takes less time and this makes analysis much easier and reaction time much

quicker.

5. Development of the proposed system does not require huge investments as required in the

development of other high end security software.

6. Simplicity the biggest single advantage of this system. There are no fancy algorithms to

develop, no signature databases to maintain. The simpler a technology, the less likely there

will be mistakes.


3/22


7. The sales and customer tracking system gives First update and retrieval of information.

8. Less tedious task.

9. To reduce the errors those are occurred in the manual system.

10.To generate the reports as per the management requirements.

11.To help in ordering of required items.

12.To provide maximum services to the users.

Intangible benefits:

13.Sales and customer tracking system is that it can make to keep note and track of your

company's workforce even by sitting in any corner of the world.

14.Sales and customer tracking system require minimal resources. This means an old Pentium

computer with 128MB of RAM can easily handle it and no need of more hard disk space.

The hardware and software requirements are not so bigger so it also saves money as well

resources.

The problem I observe in this area is that the user has to do all the operations

manually , by searching and analysing large amount of data, a miss-spelled digit or

character may create many hours of extra work and complicated correction procedure.

Necessary data validation checks are included to avoid mistakes.

Sales and customer tracking system is going to be a generalized and very effective

system and thus it is supposed to cater some general and set of problems. The major

problems that Sales and customer tracking system would address are:

1. The existing system is studied to know the extent of computerization required.

Therefore, a detailed analysis of the existing system should be conducted. For this

purpose , system should be broken down into various subsystems and these

subsystems were analysed closely to identify the problem areas.2. As we studied the existing system, it was found that there is a File Management

system which gives the facility for accessing the product details . In a File

Management all works are done manually. The main problem of the manual operation is,

it is time consuming and error prone than the computerized system. There exists

wastage of data retrieved time as in the case of search and further processing. There

was no efficient system to manipulate the existing records.


4/22


The main challenges for building this type of application:-

1. Establish a centralized database server system for retrieve, update and manipulate different

type of information building a centralized database system is one of the huge task .because

of I have replicate (copy of existing information into new one), build a generalized form of

the database for so that accessibility of large amount of data become easy and information is

successfully available on time.

2. The authentication and security of such huge database system is itself a big challenge for

me. I have applied different levels of security to access the private data and keep updated

information with high level of security concepts (e.g. integrity constraint) .the authentication

of private should be needed for getting right information to the authorized person the data

warehouse provide access control so that it would helpful for analyze company annual

report, different sales figure of its marketing of different figures, so that I can predict exact

information for this company.

3. I am novice to business and business processes. So it will be biggest challenge to collect

information from working organizations as no one will be ready to share and allow time for

such. What types of processes and tasks are being performed there every day? What are their

requirements? What do they need to run their business smoothly and successfully?

4. There is an almost explosive growth in data resulting more trials are conducted, eachtrial collects more data and trial designs have become more complex. Companies as

well regulatory agencies are moving towards highly standardized study reporting and

data exchange such as SDTM (Study Data Tabulation Model) and this becomes

more challenging as data volumes grow

The next challenge is to come up with a secure system as the end results of the system would be

used to take decisions. A web based project can be threatened in all sorts of ways and thus the

security of the complete system is a big challenge for me.

The next developmental challenge is to create a variety of reports based on the collected

information. I am considering it as a challenge because the system has wide range of product and I

need to maintain different type of report.

Lately there has been quite hype in the area of web engineering. I am making a web based project

and its obvious and self explanatory that the web based projects are different from normal stand

alone or distributed software and therefore adapting an evolutionary approach I am planning to

follow the principles of the web engineering rather than the traditional software engineering


5/22


practices. Though the differences are not voluminous but still the differences exist and I take the

study of web engineering as my challenge and depend upon technicality we are planning to use new

development technique of the C# .NET platform some new concept introduce into the market if

time permitted then I will ready to use that concept such as Ajax.

The Type of Target Audience / User who using the system.

The main target to develop this sale & customer tracking system mainly deals with automating the

tasks of maintaining and transacting the goods.

Anyone doing businesses are going to require this Sales & Customer Tracking System in future

- All business organizations looking forward to expansion

- Business organization providing after sales services to customers

- Business organization providing services to customers

- Business organization looking forward to sales promotion and growth in productivity

C. Brief description of project objectives. (i.e. scope of proposal and

deliverables)

The existing system leads to many errors like time consuming, leads to error prone results,

consumes lot of manpower to better results, lacks of data security, Retrieval of data takes lot of

time, Percentage of accuracy is less, Reports take time to produce

Keeping this in mind we decided to develop a software and named as

SALES AND CUSTOMER TRACKING SYSTEM which is very user-friendly and

helps to make research a real chore. This computerization improves efficiency of office

work, and also helps to keep data too many years without damage and can be recollected

as and when needed without much time.

The Proposed system solves problems related to data accessing problems,

because it help the user to add details of the goods to the firm database easily ,improving

data recovery speed, easy searching and also provide editing of datas in the database.

To generate the quick reports

To make accuracy and efficient calculations

To provide proper information briefly

To provide data security


6/22


To provide huge maintenance of records

Flexibility of transactions can be completed in time

After understanding the existing system and understanding the need for developing a new

system different people involved in the related activities have been consulted. The data needed

for the study has been collected from company records.

The computerization of this system would avoid the wrong interpretation and bad calculation of

data .The system help the user to see any documents, source code, tasks, activities, team

information with details at the click of a button. The record data is maintained and backed up

such a way that data is not loss. The speed of the system could also increase.

The above mentioned objectives refer to the features that I have planned for the system. I divide

these features based on the three categories and also add a few more in order to complete the

scope.

The below list of derivable given at the end of the project:

a. Softcopy of documentation

b. Hardcopy of documentation

c. Cd along with the source code of the system.

Goals:

1. To automate the WMS in an easy and efficient manner.

2. To make the jobs of admin, sub-location, retailer easy and trouble free.

3. To make the application user friendly.

Objectives:

1. To acquire up to date details about inventory.

2. To know the status of the Warehouse System.

3. To reduce the errors those are occurred in the manual system.

4. To generate the reports as per the management requirements.

5. To help in ordering of required items.

6. To provide maximum services to the users.


7/22


System Scope

This project mainly deals with automating the tasks of maintaining and transacting the goods.In the

is the key process.This process includes the activities such as maintenance of stock details,

maintenance of receipts and items etc. It is a tedious job to maintain all these details manually. The

Administrator has the priviligies to maintain different types of Products, Suppliers, Sub Location

Incharges Databases in the warehouse.He is concerned Suppliers, Sub Location Incharges

Databases in the warehouse.He is concerned. The Sub location Incharges has privilige to maintain

Products which are transformed from Administrator registration of Retailers and all operations on

this databases To date, little is known about brake performance of commercial motor vehicles

within the India. However, since faulty brakes are a primary cause of collisions in the trucking

industry and since brakes present a significant cost to trucking companies, brake life and wear are

of great interest to the transportation.

Core functionalities:

1. The system will be able to register data on a sale.

2. The supplier, sub location in charge and the retailers must be needed to register.

3. The admin has the authority to delete the supplier, sub location in charge and the retailers.

4. Admin has to maintain product and the stock details.

5. Admin can see all the report like view all suppliers, view all sub charge, view all stock, view

all retailers etc.

6. Sub location in charge can add retailers and they can be deleting also.

7. Sub location in charge must maintain purchase and sales order details.

8. Retailer maintains purchase order details and can see the payment details report.

9. The system will be able to produce statistics on sales, products, sales persons and revenue.

10.The system will be able to present the statistics on screen and on reports.


8/22


Enhanced Functionalities:

I have taken some module for the enhanced functionality.

11.The system would be a totally generalized one where all the functionalities could bemoulded according to the needs and wants of the organizations.

12.The system would be a secure one so as to make it more reliable and robust.

13.Graphical representation is given for sale.

14. Admin can email the other sub location in charge and the retailers due to exchange the

information means intra-mailing system.

Special functionalities:

1. The system would provide for the backup of the server data so that the collated data can be

used in future and also this would help in making a data secured system.

2. All the tracking info of the system is recorded in the database which is only accessible by

the authorized user.

1. Employee can email the other employee due to exchange the information means intra-

mailing system.

2. I implied some strong feature in the leave management.

3. Used Ajax technology.

4. Using Web-Parts.

5. Enhanced Security mechanism.

Module Descriptions

Warehouse Management System mainly consists of five modules.

1. Master maintenance

2. Receiving


9/22


3. Shipment

4. Billing

5. Reports

Master Maintenance:

Warehouse Management System maintains the following master details for various

purposes.

i) Suppliers Details

ii) Sublocation Incharges Details

iii) Retailers Details

iv) Parts Details

v) Products Details

Receiving:

Warehouse management System receives the stock in a validated manner against Purchase

Order & Receipt No. Warehouse management receiving process includes all the items necessary to

receive, from unloading the trucks to recording the account. Warehouse Management System can

perform the following receiving tasks ...

i) Purchase order

ii) Gouds goods

Shipment:

Warehouse Management System provides you a number of functions to maintain the flow of

goods in warehouse.

The following tasks are caused under this module ...

i) Transfer inventory

ii) Put inventory on hold

iii) View inventory balances

iv) View inventory transactions


10/22


Billing:

Warehouse billing process allows the retailer to generate new bills and also allows viewing

of existing bills.

Reports:

The reports process allows the user to produce the reports necessary for day to day

warehouse operations. The standard reports are ...

i) Inventory Reports

ii) Purchase Order Reports

iii) Administrative Reports

Learning Objective:Throughout system development the primary learning objective would be learn and apply

those software engineering, project management and human computer interaction usability concept

and principles and as well as components based development principles in order to produce highly

reusable quality software on time. Besides, another major learning objectives would also including

of performing thorough research and understand on the essential knowledge management

development principles and techniques that require for building a such knowledge based system.

Limitation of the system:1. There are many limitations to web design and reasons why it is not possible to simply

convert and existing company brochure to electronic form. Many people fail to realize

that unlike a brochure, a website is not a physical, unchangeable entity but the way awebsite displays on a person's computer will depend on many factors; type of computer,

type of browser and the individual settings chosen by the user. If you chose a font that is

not supported by browser, your website could end up rendering in a string of zeros and

ones instead of words. These type of problem comes under unwanted limitation that

doesnt having the solution because software developer develop the project on the own

machine it is not possible to fulfil the requirement of every machine.


11/22


2. Age group limitation, because this system is properly suited to the Employee so we canprovide the message to the user firstly to fulfil the required age group.

3. Physically Disable person (Blind person) cant able to use the system.D. Brief description of the resources needed by the proposal.

Sales and Customer tracking system is being proposed as a web based system and also

its domain is quite unique and different for a computer professional and as a result I would

need a lot of research and understand the domain.

For this project I will need to meet people from various backgrounds and fields. The

proposed system is focused on getting together two independent fields i.e. Information

Technology and the Employee policies and therefore I need to have a clear understanding of

both the fields.

For understanding the Employee policies and principles, I am planning to interview the

Employed professionals of a few corporate companies. These interviews would be focused

at finding how IT can be used to assess the Employee resources talent and also how can I

quantify and calculate the productive level for an organization with accuracy and precision.

To understand the possibilities and the expectations of the educational institute from the

proposed system, I am planning to interview the group leaders and the senior level officials

related to man management.

For having the knowledge employee expectations, I would like to find out appropriate

information using the data gathering techniques such as the questionnaires and interviews. I

have plans of getting information from the students using the questionnaires.

The Software requirements for the project:

As I feel that the project could be developed using the .net languages and if I use the .net

platform with the c# concepts for the development, I would like to have the following

software for the whole project:

1. .net framework

2. visual studio.net 2005

3. Internet Information Server(IIS 5.0)


12/22


4. MS XML parser 4.0.

5. Internet Explorer (5+), Opera (7+), Fire fox.

6. Fusion charts software with free license.(third party software)

7. crystal reports(built with visual studio.net 2005)

8. Microsoft Windows XP professional.

9. SQL Server 2000.

Hardware Requirements:

Table given below lists the .NET hardware requirements. These hardware requirements are divided

into requirements for client/desktop applications, as well as server-side ASP.NET applications. This

table lists the Microsoft minimum and recommended system specifications. In typical Microsoftfashion, they've low-balled their hardware recommendations. Although .NET applications may run

in these low-powered systems specified in the minimum columns, in my experience, Ill be a lot

happier with a faster system. I have included a "Better" column indicating a more desirable system

specification.

Platfor

mCPU CPU CPU RAM RAM RAM

Minimum(M

Hz)

Recommended(

MHz)

Better(M

Hz)

Minimum(

MB)

Recommended(

MB)

Better(M

B)

.NET

Client90 90+ 350+ 32 96+ 128+

.NET

Server133 133+ 450+ 128 256+ 512+

Operating System Requirements:

In addition to the hardware requirements, .NET applications also have a minimum required

operating system level to support the various .NET features. The Table shows the .NET Framework

software requirements.

Platform Operating System Additional Software

.NET Client Windows 98

Windows 98 SE


13/22


Windows ME

Windows NT 4.0 Workstation Service Pack 6a

Windows NT 4.0 Server Service Pack 6a

Windows 2000 Professional

Windows 2000 Server

Windows 2000 Advanced Server

Windows 2000 Datacenter Server

Windows XP Home Edition

Windows XP Professional

.NET Server Windows 2000 Professional Service Pack 2

Windows 2000 Server Service Pack 2

Windows 2000 Advanced Server Service Pack 2

Windows 2000 Datacenter Server Service Pack 2

Windows XP Professional

Windows 2003 Server Family

Database Access Requirements

In addition to the previously mentioned hardware and software prerequisites, certain database

access features used by the .NET Framework have minimum MDAC (Microsoft Data Access

Components) levels that are required. MDAC is included in the installation process for the .NET

Framework and Visual Studio.NET, so you don't need to worry about it in a development

environment.

Platform Middleware Notes

.NETClient MDAC 2.6 Needed by the SQL Server .NET Data Provider

.NETServer MDAC 2.7 Needed by the SQL Server .NET Data Provider


14/22


The other information or the data sets required:

1. The internet standards are to be known in advance to develop the application according to

the standards for the internet. If I fail to do so the application would fail in various

environments which is certainly undesirable.

2. The various cyber laws and obligations are to be known as the system has to deal with

privacy and also the emails of the users and thus rules regarding the bulk mails and the

emails privacy should be known.

3. For the organizations whose personnel I would interview, I would require their current

employee assessment techniques and formula and I may and may not use them for my

project.

E. Academic research being carried out and other information, techniques beinglearnt.

As far as Sales and customer tracking system is concerned, research is the back bone of

the system and more rigorous the research is, more are the chances of building a useful and

acceptable application.

The academic research is a way to find out the things from the work of the others. This work

may be in several forms.

The project has variety of requirements and I would need assistance on many topics and

from all sorts of the resources. I need to understand and explore the HR policies for better

understanding of the project. I need to learn the project management and software

engineering techniques for managing and building the project in a right and corrective way.

I also need to learn the concepts and principles of the web engineering.

Coming to the technical part, as I have felt that ASP.net might be useful for me, I need to

learn the tips and techniques of the language. To use charts and reports along with the third

party tool, I need to learn xml so as to make the data for graphs and reports universally

acceptable. Also I have to research on the internet and the web application security so as to

develop a highly secure, robust and reliable application. Since the application would involve

a complex database, I need to study the DBMS and also learn how to manage data and Data

Mining and Data Warehousing


15/22


Programming Language

Books

Brian Larson, Microsoft SQL Server 2000 Reporting Services, 2004, McGraw Hill.

Matthew MacDonald, Pro ASP.NET 2.0 In VB 2005, Special Edition, McGraw Hill.

Marco Bellinaso,Kevin Hoffman, ASP.NET Website Programming: Problem - Design -

Solution, C# Edition, 2002 , Wrox

ASP.net: The complete referenceMatthew MacDonald.

Web Sites

www.asp.net

http://www.w3schools.com/aspnet/aspnet_intro.asp

http://www.learn-asp.net/ASPTutorials/

http://www.aspspider.com/tutorials/

http://www.sql-tutorial.net/

http://www.w3schools.com/sql/default.asp

http://www.quackit.com/sql/tutorial/

http://www.1keydata.com/sql/sql.html

F: Brief description of the development plan for the proposed project

Sales and customer tracking system is a web based project and thus its going to be

developed in a very fruitful manner according to software development projects.

I have decided to follow the web and software engineering principles for the proposed

project and thus all my choices for various stages of the project would be influenced by the

software and web engineering principles. So, we have chosen the Waterfall Model for our

project.

Waterfall Model:-The Waterfall approach to software development has the following

salient aspects. It boasts a structured, well documented and disciplined process while being

non-iterative, it allows multiple projects to run in parallel it is predictive and largely used for

more stable projects.
http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Matthew%20MacDonald&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Matthew%20MacDonald&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Marco%20%20Bellinaso&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Marco%20%20Bellinaso&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Kevin%20%20Hoffman&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Kevin%20%20Hoffman&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Kevin%20%20Hoffman&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.asp.net/http://www.asp.net/http://www.w3schools.com/aspnet/aspnet_intro.asphttp://www.w3schools.com/aspnet/aspnet_intro.asphttp://www.learn-asp.net/ASPTutorials/http://www.learn-asp.net/ASPTutorials/http://www.aspspider.com/tutorials/http://www.aspspider.com/tutorials/http://www.sql-tutorial.net/http://www.sql-tutorial.net/http://www.w3schools.com/sql/default.asphttp://www.w3schools.com/sql/default.asphttp://www.quackit.com/sql/tutorial/http://www.quackit.com/sql/tutorial/http://www.1keydata.com/sql/sql.htmlhttp://www.1keydata.com/sql/sql.htmlhttp://www.1keydata.com/sql/sql.htmlhttp://www.quackit.com/sql/tutorial/http://www.w3schools.com/sql/default.asphttp://www.sql-tutorial.net/http://www.aspspider.com/tutorials/http://www.learn-asp.net/ASPTutorials/http://www.w3schools.com/aspnet/aspnet_intro.asphttp://www.asp.net/http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Kevin%20%20Hoffman&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Marco%20%20Bellinaso&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911http://www.amazon.com/exec/obidos/search-handle-url/index=books&field-author-exact=Matthew%20MacDonald&rank=-relevance%2C%2Bavailability%2C-daterank/104-1362633-8351911


16/22


For its part, Testing has its own stage within this process and benefits largely from the

above. Using Waterfall model as a Test Management System in such an environment is very

beneficial and the above diagram shows the correlation between the various stages and the

appropriate applications.

Sales and customer tracking system uses waterfall model is in the process involved in the

creation of software. The progress in the development of the software flows from the top to the

bottom, like a waterfall through the phases of requirement analysis, design, implementation, testing,

integration and maintenance and hence the name waterfall methodology. Waterfall methodology

is a structured, well documented and a disciplined process allowing multiple projects to run at a

time (being non-iterative). It is predictive and is therefore mainly used for stable projects. Testmanagement tools are helpful when using the Waterfall methodology. As it is contextual based, it


17/22


allows multiple releases within each project. So without changing processes, major, minor and

patch releases can be planned, executed and tracked in parallel. It tracks everything automatically

and also produces live metrics on all key aspects of the testing cycle which helps the managers as

well as leads to comment on the quality of the software under test. We have used the six

important stages for our project creation.

The Sales and customer tracking system consists of six distinct stages, namely:

1 .In the requirement analysis phase.

(a) The problem is specified along with the desired service objectives (goals)

(b) The constraints are identified

2. In the specification phase the system specification is produced from the detailed

definitions of (a) and (b) above. This document should clearly define the product function.

Note that in some text, the requirements analysis and specifications phases are

combined and represented as a single phase.

3. In the system and software design phases, the system specifications are translated into

a software representation. The software engineering at this stage is concerned with:

Data structure

Software architecture

Algorithmic detail

Interface representation

The hardware requirements are also determined at this stage along with a picture of the

overall system architecture. By the end of this stage the software engineer should be able to

identify the relationship between the hardware, software and the associated interfaces. Any

faults in the specification should ideally not be passed down stream.

4. In the implementation and testing phase stage the designs are translated into the software

domain


18/22


Detailed documentation from the design phase can significantly reduce the coding

effort.

Testing at this stage focuses on making sure that any errors are identified and that the

software meets its required specification.

4. In the integration and system testing phase all the program units are integrated and tested to

ensure that the complete system meets the software requirements. After this stage the

software is delivered to the customer [DeliverableThe software product is delivered to

the client for acceptance testing.]

6. The maintenance phase the usually the longest stage of the software. In this phase the

software is updated to:

Meet the changing customer needs

Adapted to accommodate changes in the external environment.

Correct errors and oversights previously undetected in the testing phases.

Enhancing the efficiency of the software.

Observe that feed back loops allow for corrections to be incorporated into the model. For example a

problem/update in the design phase requires a revisit to the specifications phase. When changes

are made at any phase, the relevant documentation should be updated to reflect that change.

The project development plan:

Stage Tasks to be Performed Approx Time

1 Project initiation:-

The formulation is the first

activity of the project and

deals with the project

initiation.

The task under this stage

would be:

1. Finding project

Draft Proposal Form

Project Proposal form

Project Specification Form

5 Weeks


19/22


objective, rationale

for the project and

target users. This

would require one

week time.

2. Formulating the

goals of the

proposed system.

This would require

one week time.

3. User profiling which

would be an

extension to the first

point. This would

require another one

week time.

2 Requirement analysis ,Project planning and

Research

The tasks under this stage

would be:

1. Perform the project

management. This

would include tasks

such as creating

project proposal,

project scope,

project charter, risk

management plan

Problem analysis

Requirement specification

Cost estimation

Schedule and milestones

Quality assurance plans

11 Weeks


20/22


and other

documents. This

would require 6

weeks of time.

2. The research phase

would run parallel to

the planning activity

and most of the time

they would

complement each

other. The research

would include the

academic research,

secondary research

and primary

research. This phase

will also continue

for 5 weeks.

3 System design and detailed

design

System design

Detailed design

7 weeks

4 Coding, system integration

and testing

Coding

Testing

8 Weeks

5 Documentation An On-going process 2Weeks(Throughout)

G. Brief description of the evaluation and test plan for the proposed

project

Testing is the process of exercising software with the intent of finding and correcting errors.

This fundamental doesnt change for the web applications but the search for the errors is a

significant challenge for the web engineers due to the complex nature of the web based

system. Testing is


21/22


A process of finding error

Finding Undiscovered error

Role of testing

Levels of testing

I have chosen following testing for mine Sales and customer tracking systemproject

that is:-

Unit Testing:-

Unit testing is a testing in which the individual units of the software are

tested in isolation from other parts of a program. It is type of testing for

which we test the all type of the module that is working according to need

or not.

Advantages:

To catch the defects that occurs at the early stage of software development.

To minimize the ration of defects before moving to next level.

Integration Testing:- Integration is a systematic approach to building the complete software

structure specified in the design from unit-tested modules.

Integration plan must specify the order in which the modules are integrated

System Testing:-

System testing is an activity to validate the software product against the

requirement specification.

This stage is intended to find defects that can be exposed only by testing the

entire system.

Acceptance Testing:-

Acceptance and installation is the phase in the software life cycle during

which a software product is integrated into its operational environment and

tested in this environment to ensure that it performs as required.

The two basic tasks- getting the software accepted and installing the software

at the customer site.


22/22


Security Testing: -

The Process to determine that an IS (Information System) protects data and

maintains functionality as intended, because it is a online project which runs on the

browser and internet so, very good

The six basic security concepts that need to be covered by security testing are:

confidentiality, integrity, authentication, authorization, availability and non-

repudiation.

We have chosen the testing for the Sales and customer tracking system for the

following term using

1. Selected processing components and web pages are unit tested.

2. The architecture is constructed and integration tests are conducted.3. The assembled web application is tested for over all functionality and content delivery.

4. The web application is implemented in a variety of different environmental configurations

and is tested for the compatibility with each configuration.

5. The web application is tested by a controlled and monitored population of the end users.

DATABASE SIZE

The database size is not to appropriate configured now the time and it is partial database

system because the functionality saved into the database through the user input such as

supplier info, retailer detail, stockdetail etc.

So, the database size is increased with the time of system develop along with scheduled.

dibya_project specification form (1)

Documents