ACKNOWLEDGEMENT

I would like to thank my internal guide Tushar for all the help &
motivation provided to me without which I could not have completed my
project in such a short span of time.

I also owe a debt of gratitude to many colleagues & teachers specially

Chunki mam from whom I have learnt many things.

This project has given me immense experience & has exposed me to the
latest technologies & has helped in enhancing my technical skills.

I am also thankful to all the persons in who directly or indirectly helped

me in achieving my goal of completing the project successfully. I also
thank all my friends & family members for their kind co-operation &
providing me moral support all through this course.

Last, but not the least; I take this opportunity to thank my friends &
colleagues, who played a part directly or indirectly in helping me
throughout my BSC IT course.

Yours,

Place ______________

Date _______________

1
INDEX

SRNO CONTENT PAGENO

1. Synopsis Of The Project 1 To 4
2. The Theoretical Background 5 To 7
3. System Analysis 8 To 13
4. System Design 14 To 16
5. Detailed Life Cycle Of the 17 to35
Project
6. Screens 36 To 47
7. Methods For System Testing 48 To 53
8. System Implementation 54 To 55
9. Source code 56 To 115
10. Limitations and Future 116 To
Enhancement 117
11. Conclusions and Discussion 118 To
129
12. References 130To
131

2
1
 1. SYNOPSIS OF THE PROJECT

1.1 TITLE OF THE PROJECT

KANHA MILK .COM

1.2 STATEMENT ABOUT THE PROBLEM

Present system is manual where project metrics has to enter all the details of
project, documents, and tasks manually. To persist the team information and efforts
estimation organization needs to maintain the huge size of the document and update
the information about team member’s details manually whenever needed. It is very
tedius and time consuming process and more importantly it leads to error. Drawbacks
Of the Manual system.

It consumes lots of time

It leads to errornous result

It requires lot of manpower for better results

It has very less data security

Data retrieval takes lot of time

Less accurate system

Reports generation requires human effort
Thus Computerization of the existing system is proposed and new system
completely removes all manual burdens to provide improved and efficient entry
system.

1.3 WHY IS THE PARTICULAR TOPIC CHOSEN?

This topic is chosen to make supplier, admin and employee access through a same
medium to manage their work and business in more efficient way. From the point of
view of applicant, who applies for job and face difficulties related to requirement and
status of resume, they can access all information through online. This will help me to
garner new knowledge & skills which I can apply & gain a competitive edge which

1
will help to boost my career graph through proper requirement gathering and giving
proper input for successful project.

1.4 OBJECTIVE AND SCOPE OF THE PROJECT

1.4.1 OBJECTIVE
1. OBJECTIVE :

To study the various activities in milk cneter including scale of operations with
their modus operandi as well as styles and the manner of functioning, their
profiles, their upswing and their downfall and last but not the least their
position in the advertising world on the basis of the contributions to the ad
world and society at large.
 To generate the quick reports
 To improve accuracy and efficiency in calculations
 To provide accurate information on timely manner
 To provide secure data
 To provide maintenance of huge records
 Flexibility of transactions

1.4.2 SCOPE
This application provides various functionalities to supplier and administrator.
For supplier, it provide all the information related to collection center, it can
view the history of milk supplied, lodge complaint against collection center
etc. for admin, it provide option for product addition, price changing and
quotation generation.

1.5 METHODOLOGY
 Supplier

1. Every member first has to activate his/her membership by registering him/her

self. People will provide their email id and other details for registration and
their account will be created.

2. On Creation of account user name will be used for login which he/ she has
registered with the website.

2
 3. A provision of password recovery module will be there. And also the user can
edit or update their records.

4. Supplier can view the history of milk supplied

5. Change password module is provided to him so, he/she can change the
password

6. They can lodge their complaint about the collection center or vehicle

 ADMINISTRATOR

1. Administrator will have admin login account and can keep track of accounts
registered on site.

2. Administrator adds the product,change the price of product,add collection

center and so on

3. It gives the solution to the complaint of supplier about the collection center

Prototyping methodology shall be used as it allows the developer to create solutions

in parts to demonstrate functionality and then make needed refinements before
developing the final solution

1.6 HARDWARE & SOFTWARE TO BE USED

1.6.1 HARDWARE

Processor: Pentium-4 or above

Processor Speed: 2.00 GHz CPU

RAM: 512 MB or above

Hard Disk Utilization: 40 GB or above

1.6.2 SOFTWARE (S)

 Operating System: Windows
 Microsoft Visual Studio Ultimate 2010

3
1.6.3 PROGRAMMING & PRESENTATION TECHNOLOGY
 C#
 ASP.NET
 ADO.NET

1.7 TESTING TECHNOLOGIES USED

Both Functional and Nonfunctional testing will be used.
Nonfunctional testing includes:
1) Stress testing
In order to determine how many clients can be handled at a time.
2) Performance testing
To reduce the hardware and software costs by predicting application
scalability and capacity.

1.8 WHAT CONTRIBUTION WOULD THE

PROJECT MAKE?

This site will provide one place for most of the interest for supplier,
administrator and employee. The career section, provide information related
to various opportunities for employees. This application provide proper,
ontime information sharing between supplier, admin and employee’s

4
5
 2. THE THEORETICAL BACKGROUND
KanhaMilkcenter provide a way to centralize the work of company and their
respective clients.

2.1 KEY FEATURES

 Auto solution generation
 Supplier can provide complaint of service provided

2.2 OVERVIEW OF THE FRONT END


The system is developed in ASP.NET with C# using Visual Studio 2008
Ultimate (DOT NET Framework 4.0)


DOT NET FRAMEWORK 4.0


The .NET Framework is Microsoft's comprehensive and consistent programming
model for building applications that have visually stunning user experiences,
providing seamless and to provide secure communication, and the ability to a
design range of business processes.

The .NET Framework has evolved & grown over a period of time to be the one of
the preferred technology for developing robust & scalable applications.

Earlier Framework versions based applications do not get affected & continue to
run on the version targeted for them.

DLR(Dynamic Language Runtime) is built on top of CLR which opens common
set of technologies to interoperate inside a common framework.


VISUAL STUDIO 2010

6
 
Microsoft Visual Studio 2010 is an integrated development environment
provided by Microsoft for Dot Net framework which simplifies the entire
application development process.

It provides a host of features such as intelligence support, background error
checking, etc to developer for increasing productivity.

It provides integrated testing & debugging tools to find and fix bugs quickly
thus allowing to create high quality solutions & bring down the cost of
solution development.


ASP.NET


ASP.NET is a unified Web development model that includes the services
necessary for you to build enterprise-class Web applications with a
minimum of coding.


ASP.NET is part of the .NET Framework, and while coding ASP.NET
applications you have to access classes in the .NET Framework. You can code
your applications in any .net compatible language with the common language
runtime (CLR), including Microsoft Visual Basic, C#,F# and so on. These
languages allows you to design and code ASP.NET applications that benefit from
the clr, type safety, inheritance, and oops features.


C#

C# is programming language introduced by Microsoft for the .NET platform.


It combines some of the best features of modern programming languages.


C# is an object-oriented language with single inheritance but supports multiple
interfaces per class. It supports component-based programming by properties
(smart fields), events and delegates (enhanced function pointers).


C# is fully interoperable with other .NET languages.

7
8
 3.1 PROBLEM DEFINITION

Teams or Organizations which maintain multiple copies of databases almost
always have the cumbersome task of maintaining schema consistency between
them.

Person to person meeting for giving assignment of employee

History of milk supplied are sent via physical medium

Supervisors has to report to office location to provide the details of his
employees

No proper management of employees

3.2 PROPOSED SYSTEM


The solution for such problems is to use some sort of software or application
which centralizes the databases and give access to employees and clients

The main solution provided is that it aims at minimizing the tiresome efforts of
manual intervention of physical work and management of employee and
clients efficiently

The proposed system will have the facility of letting the users view product
detail and collection centers detail online.

The proposed system will have the facility of saving hectic task of searching
verification documents of an employee as, all documents related to an
employee are stored

The proposed system will provide a very fast & easy way for employee and
supplier management

9
3.3 FEASIBILITY ANALYSIS
A feasibility study is an varification of a proposal designed to determine the difficulty
in carrying out a proposed task. A feasibility study looks at the corretness of an idea
with an emphasis on identifying potential problems and tries to answer one main
question: Will the idea work and should you proceed with it?

Importance of Feasibility Studies

The information we gather and represent in our feasibility study will help us in
following ways:

Provides in detail all the things you need to make the business grow;

Helps to identify logistical and other business-related problems and solutions ;

Supports to plan marketing strategies to convince a bank or investor that your
business is worth considering as an investment; and

Serve as a solid foundation for developing your business plan. Even if you
have a great business idea you still have to find a cost-effective way to market and sell
your products and services. This is very important for store-front retail businesses
where location could make or destroy your business.

10
Technical Feasibility

The assessment is based on design of system requirements in units of Input,

Processes, Output, Fields, Programs, and Procedures. This can be classified in terms of
amount of data, trends, frequency of modification, etc. in order to estimate whether the
new system will perform well or not. Technological feasibility is carried out to determine
whether the company has the capability, in terms of technical(sw), physical(hw),
personnel and expertise, to manage the completion of the project.

Operational Feasibility

Operational feasibility is a calculation of how well a new system gives solution to

the problems, and grab the advantages of opportunities identified during scope definition
and how it fulfill the requirements specified in the requirements analysis phase of system
development.

Economic Feasibility

Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system which is often known as cost/benefit analysis, the process
is to determine the benefits and savings that are expected from a candidate system and
compare them with costs incurred. If benefits are much more as compared to costs then
the decision is made to design and implement the new system in the organisation. An
entrepreneur must correctly i.e with cent percent accuracy weigh the cost versus benefits
before taking any action. This is an analysis of the costs to be incurred in the system and
the benefits derivable from the system. It is important to identify cost and advantegeous
factors, which can be differentiated as Development Costs and Operating Costs.

11
 3.4 SOFTWARE DEVELOPMENT MODEL

A software development practice which allows developers to develop solution in
parts to show functionality and make required refinements before developing the
final solution.

Prototyping Defined:-
Prototyping is the process of rapidly putting together a working prototype in order to
test various aspects of a design, illustrate ideas or features and gather early user
feedback from cleint.

Need for prototyping:-


Enables us to explore the problem space with the stakeholders.

As a requirements artifact to initially envision the system.

As a design artifact that enables us to explore the solution space of your system.

A vehicle for you to communicate the possible UI design(s) of your system.

12
3.6. Gantts Chart

13
4. SYSTEM DESIGN
4.1 STUDY OF THE SYSTEM

 It is always essential to study thoroughly and recognize the problems of existing system,
which become the building blocks & help to find out the requirements for the new
system.

 Study of the system helps in coming up with different alternatives for a better & viable
solution.
Given below are the stages performed in preliminary study of the system:
 Initially, information related to working of security agencies
 Then, information or functions needed by employees and client are recognized
 Then, which part of the system can be made paper free work are unearthed
 With the help of this data, a basic idea as to how this system can be used & be turned
effectively into automation was determined.

4.2 HARDWARE & SOFTWARE SPECIFICATION

4.2.1 HARDWARE
i. Processor Type: Pentium 4 or above
ii. Processor Speed: 2.0 GHz or faster
iii. Hard Disk Space: Minimum 15 GB Free Hard Disk Space
iv. RAM: Minimum 2 GB (Recommended 4 GB)

14
4.2.2 SOFTWARE (S)
 Microsoft Visual Studio 20
 Microsoft Dot Net Framework 4.0 & 3.5 Service Pack 1
 Microsoft SQL Server
 Operating System: Windows 7 (32/64 bit) or Windows XP Service Pack 3
 Web Browser (Mozilla Firefox, Internet Explorer 6.0 + , etc)
 IIS ( Internet information services)

4.2.3 PROGRAMMING TECHNOLOGY

 VB.NET
 ASP.NET
 ADO.NET

4.3 INPUT & OUTPUT

Input would be taken from Keyboard & Mouse & will not require any other special device.
Output would be in the form of files & screen reports.

4.4 ACCESS CONTROL

The system need access control or login screen of its own since, there are different users such as
administratorand client. Each has different access rights.

15
16
 5. DETAILED LIFE CYCLE OF THE PROJECT

5.1 PROJECT MODULES

A module for a software project is a group of programs working together to achieve a common
objective.

 Product Module
o In this module admin can add the product and can chage the price of product
whenever needed
o Users can view the detail description of the product

 Career Module
o In this applicant can apply for the job
o Admin can view the details of application

 Complaint module
o In this module supplier can lodge complaint about services
o Admin can use these complaints to take action

 Transport Module
o In this module the admin can perform the various operation related to vehicle
o In this admin can view and solve the problems related to vehicle

 Supplier Module
o In this module supplier can register itself
o It can select the collection center where he/she want to delver the milk
o Supplier can view the history

17
5.2 ARCHITECTURE DESIGN

5.2.1 Two-Tier Architecture

The two-tier architecture is like client server application. The direct communication takes place
between client and server. There is no intermediate between client and server.
The above figure shows the architecture of two-tier. Here the communication is one to one.
Let us see the concept of two tier with real time application. For example now we have a need to
save the employee details in database. The two tiers of two-tier architecture is
1. Database (Data tier)
2. Client Application (Client tier)

So, in client application the client writes the program for saving the record in SQL Server and
thereby saving the data in the database.

Advantages:
1. Understanding and maintenances is easier
18
 2. Separated from client

3. Easy to switch to a different database.

Disadvantages:
1. Performance will be reduced when there are more users.
2. Heavy load on server

3. Potential congestion on network

4. Presentation still tied to business logic

5.3 SYSTEM DIAGRAMS

5.3.1 E-R DIAGRAMS

Data models are tools used in analysis to describe the data requirement and assumptions in the
system from a top-down perspective. They also set the stage for design of databases later on in
the SDLC.

There are three basic elements in ER model:

Entities are the “things” about which we seek information.

Attributes are the data we collect about the entities.

19
Relationships provide the structure needed to draw information from multiple entities.

Entity: It represents a collection of objects o things in the real world whose individual members
or instances have the following characteristics:

Each can be identified uniquely in some fashion.

Attributes: They express the properties of entities. Attributes having unique values are called
candidate keys (Primary key).

Relationships: They describe the association between entities. They are characterized by
cardinality as follows:

A. One-to-One relationship means an instance of the first entity is associated with only one
instance of second entity.

B. One-to-Many relationship means that one instance of the first entity is related to many
instance of second entity, while an instance of second entity is associated with only
instance of the first entity

C. Many-to-Many means that an instance of the first entity is related to many instances of
the second entity and the same is true in the reverse direction also.

20
21
5.3.2 Use Cases

A use case in a use case diagram is a visual representation of distinct business functionality in a
system. The key term here is "distinct business functionality." To choose a business process as a
likely candidate for modeling as a use case, you need to ensure that the business process is
discrete in nature. As the first step in identifying use cases, you should list the discrete business
functions in your problem statement. Each of these business functions can be classified as a
potential use case. Remember that identifying use cases is a discovery rather than a creation. As
business functionality becomes clearer, the underlying use cases become more easily evident. A
use case is shown as an ellipse in a use case diagram.

System Boundary

A system boundary defines the scope of what a system will be. A system cannot have infinite
functionality. So, it follows that use cases also need to have definitive limits defined. A system
boundary of a use case diagram defines the limits of the system. The system boundary is shown
as a rectangle spanning all the use cases in the system.

Relationships: The following relationships can be established among use cases

Extends: Indicates that an existing use case is extended by additional behavior to obtain another
use case. The extend relationship exists among use cases when the function of a use case, which
is implemented in initial iterations, are enhanced in successive iterations

Includes: Indicates function of one use case are included in the function of another. They
include relationship exists among use cases when the function of a particular use case are
required by another use case

22
 System

<<include>>
Register

Raw Material Details

Check History

Check Growth
SupplierUC

Receive Payment

Launch Complaint

UseCase for Supplier

23
 System
Add Collection Center

Check Transport Service

Check Complaint

Admin

Give Solution

Launch Product

Change Price

UseCase for Admin

24
 System

Check Milk Quantity

Update Record

Receptionist
Calculate Amount
<<include>>

Transport Amount
Calculate Insentive

Usecase for receptionist

25
5.3.3 Sequence diagram

A sequence diagram is a kind of interaction diagram that shows object interactions arranged in

time sequence. It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of the scenario.

Admin Product Supplier Collection Center

1 : Add connection center()

2 : Register()

3 : supplier Information()

4 : Provide RawMaterial()

5 : Deliver RawMaterial()
6 : Launch Product()

7 : view Product()

8 : Check Supplier()

9 : return result()

26
5.3.4 Class diagram

Supplier
Collection Center
+sid: int
+sname: string +cid: int
+cname: string
+Registration()

Payment

+sid: int
Product +cid: int
+Pid: int +PayAmt()
+PName: string

Tnansport Raw Material

+VID: int +RMID: int
+Vno: string +RMName: string
+Receive() +()

27
5.3.5 Object diagram

S: Supplier
C: Collection Center
+sid: 1001
+sname: Mahesh +cid: 101
+cname: Mumbai
+Registration()

P: Payment
+sid: 1001
Pr: Product +cid: 101
+Pid: int +PayAmt()
+PName: string

T: Tnansport R: Raw Material

+VID: 100 +RMID: 1001
+Vno: MH60 +RMName: Milk
+Receive() +()

28
5.3.5 Activity diagram

Register

Select Service Center

Select type

Check history

29
 Login

Add Collection Center

Add vehical forCenter

Add Product

Change Price

Add Employee

Change Password

30
5.4 DATABASE DESIGN
 Database design is the process of producing a detailed data model of a database.
This logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a Data Definition Language,
which can then be used to create a database. A fully attributed data model contains
detailed attributes for each entity.
 The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the
logical design of the base data structures used to store the data. In the relational
model these are the tables and views. In an object database the entities and relationships
map directly to object classes and named relationships. However, the term database
design could also be used to apply to the overall process of designing, not just the base
data structures, but also the forms and queries used as part of the overall database
application within the database management system (DBMS).

5.4.1 DATA DIRECTORY

 Applicant_Master
It store the data related to applicant who applies for job.
Sr No Field Name Field Data Type Size Description

1 AppID Number 10 It is the Primary Key for this

table. It indicated unique ID
for applicant
2 Appname Text 50 Name of the applicant
3 AppEmail Text 50 Email-ID of the applicant
4 Code Number 20 Indicate Job code
5 AppPath Text 10 Path where resume is stored
6 AppContact Text 50 Applicant contact number
7 AppDate Date Date of applying
8 AppStatus Text 50 Status of applicant

31
 Supply_Master
It store the data related to Supplier

Sr No Field Name Field Data Type Size Description

1 SId number 10 It is the Primary Key for this
table. It stores the Supplier ID
2 Sname nvarchar 50 Stores Supplier name
3 Milk Amount number 10 Stores amount of milk supplied
by Supplier
4 SContactNo nvarchar 50 Stores number of Supplier
5 CollectionCenter int Stores collectionCenter
Number
6 SAdd nvarchar 50 Stores address of Supplier
7 UserName nvarchar 50 Stores username of Supplier

 Collection_Master
It store the data related to CollectionCenter

Sr No Field Name Field Data Type Size Description

1 Id number 10 It is the Primary Key for this
table. It stores the
CollectionCenter ID
2 Collection Center nvarchar 50 Stores CollectionCenter name
name
3 Capacity number 10 Stores amount of milk stored
by CollectionCenter
4 ContactNo nvarchar 50 Stores number of
CollectionCenter
5 Num of vehicles int Stores number of vehicle for
collectionCenter
6 Address nvarchar 50 Stores address of
CollectionCenter
7 PayperLiter int Store amt paid by collection
center for per liter of milk
8 RegNo nvarchar 50 Stores Reg of CollectionCenter

32
 Employee_Master
It stores the details of employee

Sr No Field Name Field Data Type Size Description

1 EID Number 10 It is the Primary Key for this
table. It stores unique id for
each employee
2 Ename nvarchar 50 Stores the name
3 Qualification nvarchar 50 Stores qualification details
4 Gender nchar 10 Indicates gender
5 Desg nvarchar 50 Indicates designation
6 ContactNo nvarchar 50 Stores contact number
7 Address nvarchar 50 Stores the address of emp
8 Path nvarchar 4000 Indicates path where
employee’s photo is stored

 LogIn_Master
It stores all the username and password of users i.e. CollectionCenter, admin,
and rounder

Sr No Field Name Field Data Type Size Description

1 UserName nvarchar 10 It is the primary Key for this
table. It stores the username
2 Password nvarchar 50 It stores the password
3 Email nvarchar 50 It stores the email id
4 SQ nvarchar 10 It indicates the security
question
5 ANS nvarchar 50 Stores answer related to
security question
6 TYPE nvarchar 50 It indicate type of user

 product_Master

33
 It store the data related to product

Sr No Field Name Field Data Type Size Description

1 PId number 10 It is the Primary Key for this
table. It stores the Product ID
2 Pname nvarchar 50 Stores Product name
3 Pqunatity number 10 Stores quantity of Product
4 UsefulPeriod int Stores useful period of Product
5 Content varchar 150 Stores content of product
6 PImage nvarchar 4000 Stores image path of Product
7 pprice decimal 18,3 Stores price of Product

34
35
Add Vehicle Validation

Add Vehicle

36
LogIn validation

Career validation

37
Career form after submission

38
ApplicantDetail

Changing price of product

39
Changing price of all product

View Product

40
Remove Product

Add product

41
View Collection Center

Add Product

42
Remove Collection Center

Add Product

43
View Product

SignUp

44
View Employee

RemoveEmployee

Modify EmployeeDetail

45
Remove Vehicle

46
47
7. METHODOLOGY FOR SYSTEM TESTING

7.1 TEST CASE DESIGN

Scenario Test Case
Scenarios Test Case description
ID ID

To check the user input valid User

name and Password
To check the validation for the User
name input string
To check the validation for the
SC_OSS_01 Login Page TC_OSS_01 Password input string
To check the user input valid User
name and Password
To check the validation for user name
To check the validation for security
question
To check the validation for security
answer
To check the validation of reset button
To check the validation for submit
Password button
SC_OSS_02 recovery TC_OSS_02
To check the validation for applicant
name
To check the validation for Email
To check the validation for proper
email password
To check the validation for contact
number
To check the validation for auto
Applicant ID
To check the validation for auto
system date
To check the validation for upload CV
To check the validation for postback
of selectCode dropDown box
Apply for To check the validation for submit
SC_OSS_03 job TC_OSS_03 button and cancel button

48
 To check the validation of center
name
To check the validation of contact
number
To check the validation of capacity
To check the validation of address
To check the validation of payment
per liter
Collection To check the validation of save and
SC_OSS_04 center TC_OSS_04 cancel button
To check the validation of vehicle
number
To check the validation of model
number
To check the validation of engine
number
To check the validity of save and
SC_OSS_05 Trnasport TC_OSS_05 cancel button
To check the validation of enter
password
To check the validation of new
password
To check the validation of re-enter
password
change To check the validation of change
SC_OSS_06 password TC_OSS_06 button
To check the validation of percentage
incerment
To check the validation product id
Change To check the validation of edit and
SC_OSS_07 Price TC_OSS_07 save button

To check the validation of comapliant

date
To check the validation of comapliant
against
To check the validation of submit and
SC_OSS_08 Compaint TC_OSS_08 reset button

7.2TESTING STRATEGIES
49
 7.2.1 Critical success factors
 End-to-End business functionality
The objective of E2E is to look at the state of the system as well as its behavior. The End-
to-End cases would be tested to ensure the business functionality is working as expected.

The steps to be carried out would be checking the functional check-point across all the
modules and interfaces

 Navigation
Navigation testing is to test whether the availability levels of various options and features
in the software are at the acceptable navigation depth levels or not. Test team to ensure
that navigation across all should be based on access rights to users.

 Links
The Goal is to test each and every link that forms part of the design once the initial code
is developed. All the link and re-direction links will be covered as part of this
functionality.

 Performance
It is done to determine how a system performs in terms of responsiveness and stability
under a particular workload. The overall performance of the website should be at
acceptable level.

 Integration between modules

Individual software modules are combined and tested as a group. Test cases are
constructed to test that all components within interfaces interact correctly.

 Data Integrity
Assuring that the accuracy and consistency of data within the application and throughout
all the interfaces. The details of one particular user once entered in the system should be
correct for the other modules. User rights will also be considered to access a particular
link/Data/Web page

7.2.2 Types of Testing needs to be covered

 System Integration Testing (End To End Testing)

Our Role: Tester
As a tester, we would be involved in the overall testing cycle to cover the Business
scenario cases and its functionality for across the modules.

 SIT approach
 Initially will understand the user stories and get an update from Business Analyst team
about their priorities.

50
  Once all the inputs are finalized, we will try to understand the complete End-to-End
functionalities from Business process point of view. We will then come up with End-to-
End Test scenarios, which will encompass all Systems and all Modules. Then we will get
this reviewed from Business Analyst. Once we have the signed off test scenario suit, we
will start preparation of detailed Test Cases. While preparing the detailed Test Cases, the
approach would be Top-Down approach.
 As mentioned above, initially we will prepare End-to-End business scenarios, which will
then split into sub-scenarios and again into system/Application level Test Cases. After
completion of Test Cases, will get them reviewed and signed off from Business Analyst.
 In Contrast, while executing these scenarios we will have a Bottom-Up approach along
with Risk based approach. So as per the priority (Critical to Low) we will get a sprint for
particular User Story. We will try to execute the test cases, then sub-scenarios and then
End-to-End scenarios respectively.
 So we will be testing a sprint at a time which is High Priority, so conceptually we will be
using Hybrid approach which is a combination of Time-boxed and Risk based testing
approach.

 Entry Criteria
Before Test Items are made available for the Test Team to test it’s expected that:

 All test tools are available and test infrastructure are available for use during testing such
as the User story list, Testing environment (Staging) and relevant documents.
 We will start SIT only when given module/User Story is completely developed and unit
tested.
And there are no Unit test defects.

 Access to Youtrack for Defect management is required.

 The correct versions of the code have been deployed to the correct test environments.
 Test Data should be provided before testing.

 Exit Criteria
For the Test Items to exit testing the following conditions will have to be met:

 All the assigned high priority User stories will be tested.

 The Test Summary/Defect log Report will be completed.
 All planned testing activities have been completed to agreed levels.
 All high priority bugs have been fixed, retested and passed.
 Low priority bugs can be allowed max of 5-10% of the entire testing.
 Any outstanding defects or deviations must have been accepted by the Business,
Operations and Technology organizations.
 Sign-off by Testing management

51
 User Accepatance Testing
Our Role: Support (We are not repsonsible to carry the UAT testing)
 Tester would provide support to the end user in terns of application navigation,
walkthrough if required.
 Support would be given if any Re-testing is required.

Performance Testing
 It is done to determine how a system performs in terms of responsiveness and stability
under a particular workload. The overall performance of the website should be at
acceptable level.
 We recommend performance testing should be done, However as discussed with all
stakeholders, it is Out Of Scope.

 Regression Testing.
 Regression testing is to determine whether a change in one part of the application affects
other parts of the software or not.
 In this release, we will not be doing regression testing as it is 1st phase. However, we will
be doing it from next phase and we will use the current SIT test cases/Scenarios as a
baseline for Regression suit.

 Automation Testing.
 We would perform this testing using Regression suit in Phase 2 as a baseline and prior to
it we would be doing proof-of concept to decide the exact tool for automation.

52
53
 8. SYSTEM IMPLEMENTATION

8.1 HARDWARE REQUIREMENTS

 Processor Type: Pentium 4 or above
 Processor Speed: 2.0 GHz or faster
 Hard Disk Space: Minimum 15 GB Free Hard Disk Space
 RAM: Minimum 2 GB (Recommended 4 GB)

8.2 SOFTWARE REQUIREMENTS

 Microsoft Visual Studio 10
 Microsoft Dot Net Framework 4.0 & 3.5 Service Pack 1
 Microsoft SQL Server
 Operating System: Windows 7 (32/64 bit) or Windows XP Service Pack 3
 Web Browser (Mozilla Firefox, Internet Explorer 6.0 + , etc)
 IIS ( Internet information services)

8.3 DIFFICULTIES FACED IN IMPLEMENTATION

Difficulties are part of any system implementation. During this project implementation I’ve
faced difficulty during creation of the survey form.

54
55
9. LIMITATIONS & FUTURE ENHANCEMENTS

LIMITATIONS

 Payroll management system is not defined

 Training module is missing
 Employee photo should be less than 10 MB

FUTURE SCOPE/ENHANCEMENTS
 Inventory management for the equipments
 Auto assignment of employees to survey
 Well payroll and training module
 Scheduling of meeting through mails

56
57
 10.CONCLUSION & DISCUSSION

10.1 PROJECT COST/EXPENSES

For developing project, cost is an important factor for consideration.
As per with industry standards, the cost of developing the project was estimated at 4220 rupees
which included a capital cost of 1040 rupees for purchasing software & hardware & a cost of
3180 rupees as tangible non recurring cost towards developer’s salary, expenses, etc.
10.2 PROJECT BENEFITS
 Access to all information through online

 Administrator can get all the information of employees all in one place

 Company can verify the documents submitted by all the employees

 Products can view their service expiration date and give feed-back of service provided

 Solution generation

 Save Time & Money.

 Very Simple & Intuitive Interface.

10.3 PROJECT COST/EXPENSES

Project Costs track project-related material costs and revenue for items other than labor. These
items may or may not be billed back to the customer. Often, it will depend on the billing contract
applied to the project whether material items are billed separately. You may track hardware or
software as a material cost with a project, or it could be incidentals such as delivery charges. Any
Change Orders for project tasks will also appear as a project cost.

58
Project Expenses track reimbursable expenses generated by project resources while working on
the project, for example, travel or entertainment expenses. Expenses may or may not be billed
back to the customer account.

For developing project of such scale, cost is an important factor for consideration.

On par with industry standards, the cost of developing the project was estimated at 3230 Rupees
which included a capital cost of 1160 Rupees for purchasing software & hardware & a cost of
2870 Rupees as tangible non recurring cost towards developer’s salary, expenses, etc.

10.4 SELF-ANALYSIS OF PROJECT VIABILITIES

Cost-benefit analysis as well as function-point analysis was done. The cost benefit analysis was
done taking into consideration the quantum of work & resources that would be required in an
organization for undertaking such a project.

10.4.1 COST-BENEFIT ANALYSIS

Cost benefit analysis (CBA), sometimes called benefit–cost analysis (BCA), is a systematic

process for calculating and comparing benefits and costs of a project, decision or government
policy (hereafter, "project"). CBA has two purposes:

To determine if it is a sound investment/decision (justification/feasibility),

To provide a basis for comparing projects. It involves comparing the total expected cost of each
option against the total expected benefits, to see whether the benefits outweigh the costs, and by
how much.

CBA is related to, but distinct from cost-effectiveness analysis. In CBA, benefits and costs are
expressed in monetary terms, and are adjusted for the time value of money, so that all flows of
benefits and flows of project costs over time (which tend to occur at different points in time) are
expressed on a common basis in terms of their "net present value."

59
CAPITAL COSTS

TOTAL
COST DESCRIPTION 2013 2014 2015 2016 COSTS

Data Processing
Equipment  

Computer 600 600

Software  

Applications 400 400

Systems 40 40

   

Total Capital Costs 1040 1040

             

60
TANGIBLE COSTS - NON RECURRING

TOTAL
COST DESCRIPTION 2013 2014 2015 2016 COST

Salaries and Benefits 2000 2000

System Studies 50 50

Data Collection/Internet 50 50

Hardware (non capital) 10 10

Software (non capital) 10 10

Incidental Expenses and

Overhead 60 60

Facility Costs(Internet, Snacks) 1000 1000

   

Total Non-Recurring Costs 3180 3180

             

61
TANGIBLE COSTS - RECURRING

TOTAL
COST DESCRIPTION 2013 2014 2015 2016 COST

S/W Support 2400 2520 2646 2778 10334

Incidental Expenses 400 320 330 350 1400

   

Total Recurring Costs 2800 2840 2976 3128 11744

             

62
DETAILS OF EXPECTED BENEFITS

TOTAL
COST DESCRIPTION 2013 2014 2015 2016 COST

Tangible Benefits  

Reduced staffing costs 4000 3100 3408 3564 8222

More effective use of staff

resources 500 530 550 580 2160

Saving from business process

improvements 7000 6400 6620 6950 21012

Decreased cost of services

provided 300 210 220 230 960

   

Total Tangible Benefits 11800 10240 10798 11324 44162

   

Cost Avoidance (Meetings,

Troubleshoot) 350 250 250 250 1100

             

63
SUMMARY OF COSTS AND BENEFITS

TOTAL
COST DESCRIPTION 2013 2014 2015 2016 COST

Costs of New Proposed Project  

Total Capital Costs 1090 1090

Total Non-Recurring Costs 1270 1270

Total Recurring Costs 2800 2830 2960 3130 11720

Total Costs of Proposed

Project(A) 5160 2830 2960 3130 14080

   

Benefits  

Business Benefits 11800 10240 10798 11324 44162

Net Business Benefits 11800 10240 10798 11324 44162

Cost Avoidance 350 250 250 250 1100

Total Benefits (Cash Inflows)

(B) 11450 9990 10548 11074 43062

Net Benefits(B-A) 6290 7160 7588 7944 28982

   

             

10.5 Problem encounter & possible solution

64
Problems were encountered while auto assignment of employee to Products service requests. For
this problem a auto assignment algorithm may be deployed.

10.6 Summary of project work

The objective of this project is to manage the Products, employees in a most effective manner.
All care has been taken to ensure smooth execution of project & to ensure that it meets the scope
of the work.
The system was verified by testing with valid as well as invalid data.
With its user-friendly & visually appealing screens, It will draw pull in anyone who uses it &
will match the expectations of the user from the system.
To meet this objective, the project included basic type of activities as in research of current
domain to identify current problem and to find solution to overcome.

10.7 SWOT ANALYSIS OF THE PROJECT

SWOT analysis (alternatively SWOT Matrix) is a structured planning method used to evaluate

the Strengths, Weaknesses, Opportunities, and Threats involved in a project or in
a business venture. A SWOT analysis can be carried out for a product, place, industry or person.
It involves specifying the objective of the business venture or project and identifying the internal
and external factors that are favorable and unfavorable to achieving that objective. The technique
is credited to Albert Humphrey, who led a convention at the Stanford Research Institute
(now SRI International) in the 1960s and 1970s using data from Fortune 500 companies. The
degree to which the internal environment of the firm matches with the external environment is
expressed by the concept of strategic fit.

Setting the objective should be done after the SWOT analysis has been performed. This would
allow achievable goals or objectives to be set for the organization.

Strengths: characteristics of the business or project that give it an advantage over others

Weaknesses: are characteristics that place the team at a disadvantage relative to others

Opportunities: elements that the project could exploit to its advantage

65
Threats: elements in the environment that could cause trouble for the business or project

Identification of SWOTs is important because they can inform later steps in planning to achieve
the objective.First, the decision makers should consider whether the objective is attainable, given
the SWOTs. If the objective is not attainable a different objective must be selected and the
process repeated.

Users of SWOT analysis need to ask and answer questions that generate meaningful information
for each category (strengths, weaknesses, opportunities, and threats) to make the analysis useful
and find their competitive advantage.

66
67
Strengths:

 Web-based, access anywhere, anytime

 Availability of information to all the Products

 Availability of resumes, quotation information

 Quotation generation

 Assignment of guards and house-keeping staff depending upon request of Product

 Administrator for control activities

Weaknesses:

 Auto assignment of guards and house-keeping staff depending upon request

 Making it an ERP based application

 Unauthorized access to quotation, Product information & employee information

Opportunities:

 Products needs are full-filled as early as possible, which provide to hold Product for long
time and to get new Product

 Posting of all available jobs and a way to fetch the status of application online itself. This
provide a good work force

Threats:

 Competitors are using better technology like data mining to read customer trends, which
helps to find more Products and knowledge of target areas

68
 11. REFERENCES

11.1 BOOK REFERENCE

69
 
Advertising Management Concepts by Manendra Mohan


Advertising Management by B.S Rathor


OGILVY on Advertising by David Ogilvy


4 Ps Buisness and Marketing Economic Times

11.2 WEB REFERENCE

 For CSS- http://www.cssmania.com

 For Sql connection- http://www.daniweb.com

 For CSS - http://www.quackit.com/css/css_color_codes.cfm
 For cost-benefit analysis-https://depts.washington.edu

 For upload-http://support.microsoft.com/kb/323246
 Using a link in CSS-http://www.computerhope.com/issues/ch000076.html

70