Full UnderGrad Project Report : Tender Timeline Tracker

A PROJECT REPORT
ON
TENDER TIMELINE TRACKER
DEVELOPED BY
PRAJWAL CHAUDHARI (110050131121)
PRUTHA MULEY (110050131101)
PALLAV SHAH (110050131127)
POOJA SOLANKI (110050131063)
Guided By:
Prof. Sonu Choudhary
Assistant Professor
Department of Computer Science & Engineering
BITS edu Campus
Babaria Institute of Technology
Department of Computer Science and Engineering
At: Varnama, Ta: Vadodara, Dist: Vadodara, Pin: 391240
PROJECT ID: BITS/CSE/UDP/2014-2015/46
DECEMBER 2014

Table of content
Title Page No.
Abstract i
List of Figure ii
List of Tables iv
Notations v
Acknowledgement x
CHAPTER-1 Introduction
1.1 Project Summary 1
1.2 Purpose 1
1.2.1 Objective 1
1.3 Problem Specification 2
1.4 Literature Review 2
1.5 Project Planning 3
1.5.1 Project Plan 3
1.5.2 Gantt Chart 3
1.5.3 Roles and Responsibilities 4
1.6 Materials/Tools Required 4
1.6.1 Hardware and Software Requirements 5
1.6.1.1 Hardware Requirements 5
1.6.1.2 Software Requirements 5
CHAPTER-2 Design
2.1 Canvases 6
2.2 Methodology 8
2.3 System analysis 11
2.3.1 Study of Current System 11
2.3.2 Problem and weakness of the current system 11
2.4 Requirements of New System 12
2.4.1 User Requirements 12
2.4.1.1 Functional Requirement 13
2.4.1.1.1 Configuration Management 13
2.4.1.1.2 Account Management 13
2.4.1.1.3 Project Progress 14
2.4.1.2 Non Functional Requirement 15
2.5 System Design 16
2.5.1 Data Modelling 16
2.5.1.1 Data Dictionary 16
2.5.2 ER Diagram 18
2.5.3 Use Case Diagram 19
2.5.4 Class Diagram 26
2.5.5 Sequence Diagram 27

2.5.6 Activity Diagram 30
CHAPTER-3 Implementation
3.1 System Architecture 40
3.1.1 Presentation tier 41
3.1.2 Logical Tier/Business Logic Tier 41
3.1.2.1 Business Tier 42
3.1.2.2 Data Access Tier 42
3.1.3 Data Tier 42
3.2 Security Features 42
3.3 Coding Standards 43
3.4 Screen Shots 46
3.5 Testing/Verification 58
3.5.1 Testing Plan 59
3.5.1.1 Test Coverage 60
3.5.1.2 Test Methods 60
3.5.1.3 Test Responsibilities 60
3.5.2 Testing Strategy 61
3.5.3 Testing Methods 61
3.5.3.1 Unit Testing 62
3.5.3.2 Module Testing 62
3.5.3.3 Integration Testing 63
3.5.3.4 Acceptance Testing 63
3.5.4 White Box Testing 63
3.5.5 Black Box Testing 64
3.5.6 Grey Box Testing 64
3.5.7 Stress Testing 65
3.6 Test Cases 66
CHAPTER-4 Conclusion
4.1 Summary of Results 70
4.2 Advantages 70
4.3 Scope of Future Work 70
REFERENCE 71

BITS/CSE/UDP/2014-2015/46
BIT(CSE) i
Abstract
The application will be an integrated web based application which will behold all
the information and handling of the tenders passed and proposed by the government of
India. Here the vendors will be able to look up the upcoming tenders. As per the project
title suggests one will be able to see the tender’s project progress throughout the project
run time.
Other than these information, a government official which is assigned for a
particular project will be able to see the progress report of the project and compare it
graphically with the one committed by the contractor, through this the official can give
further guidelines to the contractor for the further approach in the project and contractor
will be able to make the changes accordingly.
Other facility which will be provided is an Android application which will keep
on updating the contractors about the new tenders and to the government official about
the progress report of a particular project.

BIT(CSE) ii
List of Figures
Number Figure Name Pg. No.
1.5.2.1 Gantt Chart 3
2.2.1 Iterative Lifecycle model 7
2.5.2.1 ER Diagram 16
2.5.3.1 Use case Diagram: Domain 17
2.5.3.2 Use case Diagram: User Account Search 18
2.5.3.3 Use case Diagram: Vendor Registration 19
2.5.3.4 Use case Diagram: Tender Filling 20
2.5.3.5 Use case Diagram: Project Progress Mobile
Tracking
21
2.5.3.6 Use case Diagram: Project Progress Web
Tracking
22
2.5.3.7 Use case Diagram: Project Allocation and
Officer Accounts
23
2.5.4.1 Class Diagram 24
2.5.5.1 Sequence Diagram: Admin 25
2.5.5.2 Sequence Diagram: Vendor 26
2.5.5.3 Sequence Diagram : Officer 27
2.5.6.1 Activity Diagram : Admin Activity 28
2.5.6.2 Activity Diagram : Vendor Activity 29
2.5.6.3 Activity Diagram : Officer Activity 30
2.5.6.4 Activity Diagram : Registration 31
2.5.6.5 Activity Diagram : New Tender 32
2.5.6.6 Activity Diagram : Vendor Applies For
Tender
33
2.5.6.7 Activity Diagram : Admin Approves
Tender
34
2.5.6.8 Activity Diagram : Tracking 35
2.5.6.9 Activity Diagram : Forgot Password 36
2.5.6.10 Activity Diagram : Notification 37
3.1.1 3-Tier Architecture 38

BIT(CSE) iii
3.4.1 Login Page 44
3.4.2 Registration Page 45
3.4.3 Vendor Home Page 46
3.4.4 Admin Home Page 46
3.4.5 New Tender Page 47
3.4.6 New Project Page 48
3.4.7 Manage Project 48
3.4.8 Create Officer 49
3.4.9 View Tenders 49
3.4.10 Vendor Search 50
3.4.11 Manage and Assign Officer 50
3.4.12 Vendor Profile 51
3.4.13 Project Search 51
3.4.14 Ongoing Projects 52
3.4.15 Vendor Tenders 52
3.4.16 Project Details 53
3.4.17 Add Tenders 53
3.4.18 Vendor Progress 54
3.4.19 Change Officer Details 54
3.4.20 Allotted Projects 55
3.4.21 Officer Progress 55
3.5.1 Testing 60

BIT(CSE) iv
List of Tables
Table number Table name Page no.
1.5.3.1 Roles and Responsibility 4
1.6 System Requirements 4
2.5.1.1.1 Vendor 14
2.5.1.1.2 Officer 14
2.5.1.1.3 Tender 14
2.5.1.1.4 Project 15
2.5.1.1.5 Project Progress 15
2.5.1.1.6 Domain 15
2.5.1.1.7 Review 16
3.3.1 Naming Convention 42
3.6.1 Project Details 64
3.6.2 Tender Details 65
3.6.3 Officer Details 66
3.6.4 Progress Details 66
3.6.5 Assign Tender 67

BIT(CSE) v
NOTATIONS
NOTATIONS FOR USE CASE DIAGRAM

BIT(CSE) vi
NOTATIONS FOR ACTIVITY DIAGRAM

BIT(CSE) vii
NOTATIONS FOR SEQUENCE DIAGRAM

BIT(CSE) viii
NOTATIONS FOR CLASS DIAGRAM

BIT(CSE) ix
NOTATIONS FOR E-R DIAGRAM

BIT(CSE) x
ACKNOWLEDGEMENT
We would like to thank Prof.Sonu Chaudhary for accepting our project and for his prolonged
interest in our work and guidance. He has been a constant source of motivation for us. By his
uncompromising demand for quality and his insistence for meeting the deadlines, we could
show such an excellent work. He provided us with a friendly environment in the institute.
We would also like to thank Dr. Avani Vasant (HOD Computer Dept) for introducing us to
the project definition.

CERTIFICATE
This is to certify that the project entitled “Tender Timeline Tracker” is a bonafied report of
the work carried out by Mr./Miss (1) Prajwal Chaudhari (01/CE/121) (2) Pallav Shah
(01/CE/127) (3) Prutha Muley (01/CE/101) (4) Pooja Solanki (01/CE/063) for User
Defined Project in Semester VIII under the guidance and supervision of Prof. Sonu
Chaudhary for the partial fulfillment of award of the Degree of Bachelor of Computer
Science and Engineering at Babaria Institute of Technology, Varnama, Vadodara, Gujarat.
To the best of my knowledge and belief, this work embodies the work of candidate
themselves, have duly completed, fulfills the requirement of the ordinance relating to the
Bachelor Degree awarded by Gujarat Technological University and is up to the standard in
respect of content, presentation and language for being referred to the Examiner.
Prof. Sonu Chaudhary Dr. Avani Vasant
Project Internal Guide Head of Department
BITS EDU CAMPUS
Babaria Institute of Technology
Department of Computer Science and Engineering
At: Varnama, Ta: Vadodara, Dist: Vadodara, Pin: 391240

GUJARAT TECHNOLOGICAL UNIVERSITY
CERTIFICATE FOR COMPLETION OF ALL ACTIVITIES AT ONLINE PROJECT PORTAL
B.E. SEMESTER VIII, ACADEMIC YEAR 2014-2015
Date of certificate generation : 24 May 2015 (21:44)
Plagiarism Search Report
Final Project Report
Patent Drafting Exercise (PDE)
Business Model Canvas (Report)
Business Model Canvas (Image)
Submitted Four Periodic Progress Reports (PPR)
Uploaded
Uploaded
Completed
Uploaded
Uploaded
Completed
This is to certify that, Prajwal Kishor Chaudhari (Enrolment
Number-110050131121) working on project entitled with Tender
Timeline Tracker from Computer Science & Engineering
department of Babaria Institute Of Technology, Varnama had
submitted following details at online project portal.
Name of Student :
Signature of Student :
Prajwal Kishor Chaudhari
*Signature of Guide :
Name of Guide : Mr. Sonu Baleshwar
Choudhary
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt
that GTU has received a copy of the data that you have uploaded and submitted as your project work.
Disclaimer :
*Guide has to sign the certificate, Only if all above activities has been Completed / Uploaded.

pdfcrowd.comPRO version Are you a developer? Try out the HTML to PDF API
Contact us | Universities | History | Testimonies | Press | About us | Sitemap | Help | Essay help | RSS | Log in
Plagiarism Report For 'Project report.docx'
How does Viper work.....?
[+] Read more..
Location Title
Words
Matched
Match
(%)
Unique
Words
Matched
Unique
Match
(%)
http://www.extremeprogramming.org/rules/pair.html Pair Programming 104 4 104 4
http://en.wikipedia.org/wiki/Project_planning Project planning - Wikipedia, the f ree ency clopedia 90 3 90 3
http://www.conceptdraw.com/examples/project-plan-timeline
Project timeline diagram - New business project plan
...
166 6 76 3
http://cav ehill.uwi.edu/staf f /eportf olios/paulwalcott/courses/comp2145/2009/sof tware_process_models.htm Sof tware Process Models 31 1 31 1
http://link.springer.com/chapter/10.1007%2F978-3-540-24659-6_20
Ef f ort Estimation Based on Collaborativ e Filtering -
Springer
27 1 27 1
http://docslide.net/documents/project-report-on-atm-sy stem.html Project Report on ATM Sy stem - Documents 76 3 49 2
http://www.conceptdraw.com/examples/gantt-chart-f or-project-example
Gantt chart examples | Gant Chart in Project
Management ...
90 3 0 <1
http://en.wikipedia.org/wiki/Extreme_Programming
Extreme programming - Wikipedia, the f ree
ency clopedia
99 3 99 3
http://www.conceptdraw.com/examples/project-process-f low-chart
Flowchart Programming Project. Flowchart Examples |
Flowchart ...
90 3 0 <1
http://www.conceptdraw.com/examples/sample-project-plan-gantt-chart
Gantt chart examples | Gantt charts f or planning and
...
90 3 0 <1
http://www.bing.com/knows/project%20planning?mkt=zh-cn Project planning - å¿…åº”ç½‘å…¸ 85 3 0 <1

Documents found to be plagiarised
http://www.f indeen.co.uk/pair_programming.html pair programming 27 1 0 <1
http://www.essay .uk.com/f ree-essay s/inf ormation-technology /the-card-processing-sy stem.php
The Card Processing Sy stem : Free Inf ormation
Technology Essay s
53 2 0 <1
http://www.simplilearn.com/resources/project-management/what-is-a-project-management-plan What is a Project Management Plan - Simplilearn 15 1 0 <1
http://sof t-engineering.blogspot.com/2010/12/spiral-model.html Sof tware Engineering: The Spiral Model 23 1 0 <1
http://pmp.groupsite.com/beta/discussion/topics/41162/messages
Is there any dif f erence between "Project Plan" and
"Project ...
67 2 2 <1
Matching Content: 17%
Master Document Text
CANDIDATE'S DECLARATIONWe declare that final semester report entitled "Tender Timeline Tracker" is/are my/our own work conducted under the
supervision of the guide (Dr./Prof) Sonu Chaudhary.We further declare that to the best of my knowledge the report for B.E. final year does not
contain part of the work which has been submitted for the award of B.E. Degree either in this or any other university without proper citation
Candidate's Signature)(Prajwal Chaudhari)(11CE126)(110050131121)(Pallav Shah)(11CE)(110050131127)(Prutha Muley)(11CE105)(110050131101)(Pooja Solanki
CE138)(110050131063)CERTIFICATE This is to certify that the project entitled "Tender Timeline Tracker" is a bonafied report of the work carried out
by Mr./Miss (1) Prajwal Chaudhari (01/CE/121) (2) Pallav Shah (01/CE/127) (3) Prutha Muley (01/CE/101) (4) Pooja
Defined Project in Semester VIII under the guidance and supervision of Prof. Sonu Chaudhary for the partial fulfillment of award of the Degree of
Bachelor of Computer Science and Engineering at Babaria Institute of Technology, Varnama, Vadodara, Gujarat.To the best of my knowledge and belief
this work embodies the work of candidate themselves, have duly completed, fulfills the requirement of the ordinance relating to the Bachelor Degree
awarded by Gujarat Technological University and is up to the standard in respect of content, presentation and language for being referred to the
Examiner. Prof. Sonu Chaudhary Prof. Saurabh ShahProject Internal Guide Head of DepartmentBITS EDU CAMPUSBabaria Institute of
of Computer Science and EngineeringAt: Varnama, Ta: Vadodara, Dist: Vadodara, Pin: 391240ACKNOWLEDGEMENTWe would like to thank Prof.Sonu Chaudhary
for accepting our project and for his prolonged interest in our work and guidance. He has been a constant source of motivation for us. By his
uncompromising demand for quality and his insistence for meeting the deadlines, we could show such an excellent work. He provided us with a friendly
environment in the institute.We would also like to thank Prof. Saurabh Shah (HOD Computer Dept) for introducing us to the project definition.TABLE OF
CONTENTSTitlePage No.ABSTRACTiCOMPANY PROFILE (If Applicable)iiList of FiguresiiiList of Tables ivABBREVIATIONSvNOTATIONSviCHAPTER-
1010103CHAPTER
So on...APPENDICES60REFERENCES62EXPERIENCE63AbstractTender Timeline TrackerThe application will be an integrated web based application which will

behold all the information and handling of the tenders passed and proposed by the government of India. Here the vendors will be able to look up the
upcoming tenders. As per the project title suggests one will be able to see the tender's project progress throughout the project run time.Other than
these information, a government official which is assigned for a particular project will be able to see the progress report of the project and
compare it graphically with the one committed by the contractor, through this the official can give further guidelines to the contractor for the
further approach in the project and contractor will be able to make the changes accordingly.Other facility which will be provided is an Android
application which will keep on updating the contractors about the new tenders and to the government official about the progress report of a
particular project. List of FiguresIntroductionProject SummaryNow days different government organizations are getting there work environment online
The Indian government over past few years have developed many of its working bodies online. Department of government Projects for India is one such
department that needs to be on line for the better functionality and easy to access data. Our system "Tender timeline tracker" helps the government
as well as the vendors seeking to fill up tenders for new project.This system helps the government official to keep track of the project progress
other than this it also helps the admin to look over and compare the project progress reports of officer allocated to the project and that of
submitted by vendor. Vendors will be able to keep themselves updates with the new projects plans proposed by the Government and fill up for the same
Other facility which will be provided is a mobile application that will be handy to use by all the users of the applicationPurposeThe basic purpose
is to see that the every tender passed by the government gets completed on time and henceforth reducing the corruption as well as to keep a track of
work done throughout the project. ScopeThe basic purpose is to see that the every tender passed by the government gets completed on time
henceforth reducing the corruption as well as to keep a track of work done throughout the projectTo ensure that the project completes on time, to see
that there is no corruption between the government officials and the vendors having the tender. Also the our main intention is to provide easy way to
government to keep the track of the ongoing projects.The application will generate a progressive timeline of the project which
the government to check if the work is properly done. Actual photographs containing latitude and longitude of the construction site can be uploaded
on the portal.ObjectiveThe objective for developing this application is to provide the government of India with the ease of use and handling of the
whole project and tenders system. Also as this system provides the live tracking of the project which help in reduction of corruption and also
illegal documents.2. Project Management2.1Project PlanningProject planning is part of project management, which relates to the use of schedules such
as Gantt charts to plan and subsequently report progress within the project environment. Initially, the project scope is defined and the appropriate
methods for completing the project are determined. Following this step the durations for the various tasks necessary to complete the work are listed
and grouped into a work breakdown structure. Project planning is often used to organize different areas of a project, including project plans, work
loads and the management of teams and individuals2.1.1Project development approach and JustificationSoftware process model is a description of the
sequence of activities carried out in a Software Engineering Project, and the relative order of the activities. It is a simplified description of a
process, presented from a particular perspective. In essence, each stage of the software process is identified and a model is then employed to
represent the inherent activities associated within that stage. Spiral Model is a suitable model for the development of our project. It couples the
iterative nature of prototyping with the controlled and systematic aspects of the waterfall model. It provides the potential for rapid development of
increasingly more complete versions of the software. It is a risk-driven process model generator. It has two main distinguishing features:??Cyclic
Approach: Incrementally growing a system's degree of definition and implementation while decreasing its degree of risk??A set of anchor point
milestones: A combination of work products and conditions that are attained along the path of the spiral We are also using the Pair Programming

technique and the Extreme Programming (XP) Methodology in our project.In Pair programming all code to be sent into production is created by two
people working together at a single computer. Pair programming increases software quality without impacting time to deliver. It is counter intuitive
but 2 people working at a single computer will add as much functionality as two working separately except that it will be much higher in
With increased quality comes big savings later in the project. The best way to pair program is to just sit side by side in front of the monitor
Slide the key board and mouse back and forth. Both programmers concentrate on the code being written.Extreme Programming (XP) is intended to improve
software quality and responsiveness to changing customer requirements. It advocates frequent "releases" in short development cycles, which is
intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. Other elements of Extreme Programming
include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually
needed, a flat management structure, simplicity and clarity in code, expecting changes in the customer's requirements as time passes and the problem
is better understood, and frequent communication with the customer and among programmers.2.1.2Project PlanA Project Plan is a formal, approved
document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and
decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be summarized
or detailed. The objective of a project plan is to define the approach to be used by the Project team to deliver the intended project management
scope of the project.2.1.3Roles and responsibilityOur team structure is a Democratic Decentralized Team structure. There is no permanent leader
Communication between the team members is Horizontal. Decision on problem and approach are made by group consequences. All the members work equally
in analysis, designing, coding and testing of the software.Table 2.1 Roles and ResponsibilityTask ResponsibilityRequirement
Pooja, PruthaSystem DesignPrajwal, Pallav, Pooja, PruthaImplementationVisualizationCommunication infrastructureDatabasePrutha, PoojaPrajwal
PallavPrajwal, PruthaValidationVisualizationCommunication infrastructureDatabasePrutha, PoojaPrajwal, PallavPrajwal, PruthaTestingPrajwal, Palav
Pooja, PruthaFinal DocumentationPrajwal, Palav, Pooja, Prutha2.2EstimationThe accurate estimation of the problem size is fundamental to estimation of
effort, time duration and cost of the software. We need to define some appropriate metric or unit in terms of which the project size can be expressed
Effort EstimationEffort estimation methods are one of the important tools for the project managers in the controlling human resources of ongoing or
the future software projects. The estimations require historical project data including process and product metrics that characterize past projects
Software cost and effort estimates will never be an exact science. Too many variables human, technical, environment can affect the ultimate cost of
software and effort applied develop to it.2.2.2Cost AnalysisSoftware project estimation in today's era result in company's profile and loss. Function
Points can be counted using the following information domains:??Number of external inputs(EIs):- Inputs given by the user or another system.??Number
of external outputs(EOs):-Outputs delivered within the system or givento another system??Number of external inquires(EQs):-User Input??Number of
internal logical files(ILFs):-Logical grouping of data that resideswith the application's boundary and is maintained via external inputs.??Number of
external interfaces files(EIFs):- Logical grouping of data that residesexternal to the application but provides data that may be of use to the
application.2.3Feasibility studyThe feasibility study is an evaluation and analysis of the potential of a proposed projectwhich is based on extensive
investigation and research to support the process of decisionmaking.Feasibility studies aim to objectively and rationally uncover the strengths and
weaknessesof an existing business or proposed venture, opportunities and threats present inthe environment, the resources required to carry through
and ultimately the prospects forsuccess In its simplest terms, the two criteria to judge feasibility are cost requiredand value to be attained.A well
designed feasibility study should provide a historical background of the businessor project, a description of the product or service, accounting

statements, details ofthe operations and management, marketing research and policies, financial data, legalrequirements and tax obligations
Generally, feasibility studies precede technicaldevelopment and project implementation.A feasibility study evaluates the project's potential for
success; therefore, perceivedobjectivity is an important factor in the credibility of the study for potential investors andlending institutions It
must therefore be conducted with an objective, unbiased approachto provide information upon which decisions can be based.2.3.1Does the system
contribute to the overall objectives of the organization?Yes, it will contribute to the overall objective of the organization. It will allow the
organization to control and monitor the processes and procedures happening within the system.Since the system is dynamic and easy to use, the
organization will be able to automate most part of its work without any loss of the procedures that used to happen in the organization before
introduction of this system.2.3.2Can the system be developed using the current technology within the given cost and scheduled constraints?As all the
technologies that are being used in this project are in trend and are used extensively throughout and the cost of the project mainly depends on how
we as a developer can develop this system as compact as possible so, yes it can be developed using current technology within the given
and cost.2.3.3 Can this system be integrated with the other system which are already in place?No, this system cannot be integrated with other system
as it is a complete automation of the current system and also many additional features and functionalities have been added to it3.System analysis
Study of current systemCurrent systems gather and store data from field devices and make such data available for acquisition, processing and
presentation to users. However, while these systems gather and store a variety of information about and from field devices, typically only a fraction
of the usable information is presented and made available to users. This may be so for a variety of reasons: some useful data may not be captured
some useful data may not be properly characterized; some useful data may be trapped in a proprietary database that limits distribution and analysis
etc. As a result, key decision-makers operate in a context of too little information, inaccurate information, or information that is old or stale
Detail working of the systemCurrent government project department works in conventional way where paper work is a major part, other then this there
is no timely supervision available overhead. In current system the project is announced by the government, these projects are then open for the
bidders to bid for, the project is allotted to the company or the bidder with the most cost efficient plan. This plan that the bidder submits is
called tender. Once the project is allotted the work starts and to supervise it a government official is allotted to that project.Now a days
government has moved towards the internet and has made the tender system online. There's a government as well as private sector websites which keeps
the bidders and vendors updated about the new projects proposed by the government. These websites provide details of the projects proposed by the
government such as project type, budget, location, etc. One can also apply for the project through these websites but no timely tracking is provided
on those websites. Overall no post project allocation procedures are taken care of, those things are still done conventionally.All the above
mentioned functionalities are also provided in this project, other than this many more functionalities have been added in this project as mention
above "post project allocation procedures". This procedure includes most input from government side as in allocating a government official to a
project, tracking of the project by the officer, updating the progress. As this all things now works online, lot of paper work as well as time is
saved. The officer will update the project progress report by timely visiting the project site and upload the photo which will show the GPS location
of the project and can compare the actual progress with the one proposed by the vendor. The head authority i.e. Tender Authority of India can
supervise the applicant who got the project as well as on the government official allocated to that project. This may result in reduction in
corruption and yield better results3.2Problem and weakness of the current systemLack of presentation of the useful information: Current system
gathers and stores variety of information but only a fraction of information is showed to the user at first.No Post allocation Procedure: current

Plagiarism Detection Softw are
Plagiarism Test
Plagiarism Detector
Detect Plagiarism
Essay Checker | Free Check for Plagiarism
Lesson plans
Avoid Plagiarism
Plagiarism Check
Plagiarism Prevention
Turnitin | Check for Plagiarism Free
Editing Services
Coursew ork w riting
system only provides facility till the project is allocated to a vendor.No project tracking: Current system does not allow the government official to
track the project progress.No automatic report generation: Current system doesn't have any automated procedure that can perform dynamic report
generation.3.3Requirements of New System3.3.1User RequirementsThe user requirements for a system should describe the functional and non-functional
requirement so that they are understandable by system users who don't have much technical knowledge. They should specify the external behaviour of
the system and should avoid the design characteristics as far as possible. User requirements should not be defined using implementation modes. The
requirements include both conceptual and detailed information. It expresses the concept that there should be configuration control facilities
provided as an inherent part of the system. It is good to practice to separate user requirement from more detailed system in requirement document
Otherwise non-technical reader of the user requirement may be overwhelmed by details which are really only relevant for technicians.Following are the
Primary users of the System : Admin, Vendor, OfficerAdminAdmin must define domain rules Admin must upload Agreement documentsAdmin must
the projects.VendorVendor must Register himselfVendor should have internet access and android for using mobile applicationVendor should have internet
connection and basic computer knowledgeOfficerOfficer must be capable to upload timely progress reportOfficer should have internet access and android
for using mobile applicationOfficer should have internet connection and basic computer knowledgeOfficer should have access to vendor tender
and plans4.SYSTEM DESIGN4.1 USE CASE DIAGRAMFig 4.1.1 Usecase Diagram: DomainFig 4.1.2 Usecase Diagram: User Account Search
Diagram: Vendor RegistrationFig 4.1.4 Usecase Diagram: Tender FillingFig 4.1.5 Usecase Diagram: Project Progress Mobile
Diagram: Project Progress Web TrackingFig 4.1.7 Usecase Diagram: Project Allocation and Officer Accounts4.2 CLASS DIAGRAMFig 4.2
SEQUENCE DIAGRAMFig 4.3.1 Sequence Diagram: Admin Fig 4.3.2 Sequence Diagram: Vendor Fig 4.3.3 Sequence Diagram :
Activity Diagram : Admin ActivityFig.4.4.2 Activity Diagram : Vendor ActivityFig.4.4.3 Activity Diagram : Offiicer
RegistrationFig.4.4.5 Activity Diagram : New Tender Fig.4.4.6 Activity Diagram : Vendor Apples For TenderFig.4.4.7 Activity Diagram
TenderFig.4.4.8 Activity Diagram : TrackingFig.4.4.9 Activity Diagram : Forgot PasswordFig.4.4.10 Activity Diagram : Notfcation4.5
Entity Relationship Diagram4.6 COMPONENT DIAGRAM Fig 4.6 Component Diagram4.7 DEPLOYMENT DIAGRAMFig 4.7 Deployment DiagramProject_id
CSE)vii
Copyright © 2012 All Rights Reserved. Scan My Essay - Free Plagiarism Scanner, Checker and Detection Tool. Viper and ScanMyEssay.com are trading names of
Angel Business Limited, a Company registered in England and Wales w ith Company Registration No: 07344835, The Loft, 3 Plumptre Street, The Lace Market,
Nottingham NG1 1JL | Warning - Viper Keygen / Viper Crack

BITS/CSE/UDP/2014-2015/46 Introduction
BIT(CSE) 1
1.
2. INTRODUCTION
1.1 Project Summary
Now days different government organizations are getting there work environment
online. The Indian government over past few years have developed many of its
working bodies online. Department of government Projects for India is one such
department that needs to be on line for the better functionality and easy to access
data. Our system “Tender timeline tracker” helps the government as well as the
vendors seeking to fill up tenders for new project.
This system helps the government official to keep track of the project progress,
other than this it also helps the admin to look over and compare the project
progress reports of officer allocated to the project and that of submitted by vendor.
Vendors will be able to keep themselves updates with the new projects plans
proposed by the Government and fill up for the same.
Other facility which will be provided is a mobile application that will be handy to
use by all the users of the application
1.2 Purpose
The basic purpose is to see that the every tender passed by the government gets
completed on time and henceforth reducing the corruption as well as to keep a
track of work done throughout the project.
1.2.1 Objective
The objective for developing this application is to provide the government of India
with the ease of use and handling of the whole project and tenders system. Also
as this system provides the live tracking of the project which help in reduction of
corruption and illegal documents

BIT(CSE) 2
1.3 Problem Specifications
“Tender Timeline Tracker” is a web based application to assist the tendering body
of the government to govern the project tracking and efficiency.
The existing system that government follows large scale manual work and paper
work, other than this all inspections are to be made in person. Tender timeline
tracker assists government to overcome all these manual work. Tender timeline
Tracker is a system for three main users i.e. Admin, Officer and Vendor.
In conventional method the vendor has to visit government offices to fill up there
tenders for the project. Moreover they have to keep up with the newspaper or
public notices for the new projects proposed by the government. By using Tender
Timeline Tracker vendor can apply for any project proposed by the government
without visiting the government office and can manage all his/her project.
In the procedure of tendering and project an officer is assigned to each ongoing
project for the timely inspection of the project progress. For the ease of use for
officer an android app is provided so that officer can make inspection updates
easily.
1.4 Literature Review
The tools and technologies used in preparing this system are:
• Front-end : Microsoft Asp.net (with c#)
• Back-end : MYSQL Server Database
• Environment : Microsoft Visual Studio 2010
• Documentation : Microsoft Office Word 2013
• Presentation : Microsoft Office PowerPoint 2013
• System Design Diagrams : VISIO-2003

BIT(CSE) 3
1.5 Project Planning
Project planning is part of project management, which relates to the use of
schedules such as Gantt charts to plan and subsequently report progress within the
project environment. Initially, the project scope is defined and the appropriate
methods for completing the project are determined. Following this step the
durations for the various tasks necessary to complete the work are listed and
grouped into a work breakdown structure. Project planning is often used to
organize different areas of a project, including project plans, work load and the
management of teams and individuals
1.5.1 Project Plan
A Project Plan is a formal, approved document used to guide both project
execution and project control. The primary uses of the project plan are to
document planning assumptions and decisions, facilitate communication among
stakeholders, and document approved scope, cost, and schedule baselines. A
project plan may be summarized or detailed. The objective of a project plan is to
define the approach to be used by the Project team to deliver the intended project
management scope of the project.
1.5.2 Gantt Chart

BIT(CSE) 4
Figure 1.5.2.1 Gantt Chart
1.5.3 Roles and Responsibilities
Our team structure is a Democratic Decentralized Team structure. There is no
permanent leader. Communication between the team members is Horizontal.
Decision on problem and approach are made by group consequences. All the
members work equally in analysis, designing, coding and testing of the software.
Table 1.5.3.1 Roles and Responsibilities
Task Responsibility
Requirement Analysis Prajwal, Pallav, Pooja, Prutha
System Design Prajwal, Pallav, Pooja, Prutha
Implementation
• Visualization
• Communication infrastructure
• Database
Prutha, Pooja
Prajwal, Pallav
Prajwal, Prutha
Validation
• Visualization
• Communication infrastructure
• Database
Prutha, Pooja
Prajwal, Pallav
Prajwal, Prutha
Testing Prajwal, Palav, Pooja, Prutha
Final Documentation Prajwal, Palav, Pooja, Prutha

BIT(CSE) 5
1.6 Materials/Tools Required
Table 1.6.1 System Requirements
Minimum Requirement Recommended
Internet
Connection
Cable or DSL, Internet Explorer
11
Cable or DSL, Firebox
(Version 24 or above),
Google Chrome (version 31
or above), JavaScript enabled
browser
Operating
System
Windows XP or above Windows 7
Computer
Processor
Pentium 233-megahertz (MHz)
processor or faster (300 MHz is
recommended)
1 gigahertz (GHz) or faster
32-bit (x86) or 64-bit (x64)
processor
Computer
Memory
At least 64 megabytes (MB) of
RAM (128 MB is recommended)
At least 1.5 gigabytes (GB) of
available space on the hard disk
1 gigabyte (GB) RAM (32-
bit) or 2 GB RAM (64-bit)
16 GB available hard disk
space (32-bit) or 20 GB (64-
bit)
SDK Compatible with above OS Compatible with above OS
1.6.1 Hardware and Software Requirements (Minimum Requirements
to run your system)
1.6.1.1 Hardware Requirements
• Intel Pentium 4 or above / AMD Athlon or above
• 1 GB RAM
• 1.5 GB of free Disk Space
These are basic requirements to build an infrastructure for running this
system. You will need Power Supply and Switch

BIT(CSE) 6
1.6.1.2 Software Requirements
• Operating System: Microsoft Windows XP, Microsoft Windows
Server 2003, Windows Vista, Windows 7, Windows Server 2008.
• Web Server: IIS 6.0 and higher
• Server Side Scripting: .NET Framework 3.5 and Higher
• SQL Server 2005 and higher
• Microsoft Word 2007 and higher

BITS/CSE/UDP/2014-2015/46 SYSTEM DESIGN
BIT(CSE) 6
2. SYSTEM DESIGN
2.1 CANVASES
1) Ideation Canvas:
Ideation canvas is basically representing the set of ideas we had for our project.
We decided on who all will use the project and who all are related, then the
activities on how the project flow will happen, then locations that is where all the
project will e located and where it will be used. The solutions are not the exact
solutions but the possible set of solutions which may be the best for the project.

BIT(CSE) 7
2) Observation Matrix:
The observation matrix focuses on the solving and reaching to conclusion of a
problem. The existing system problems are taken into account and a brief
explanation and justification is provided as to why the system we designed is best
for the working

BIT(CSE) 8
3) Idea Funnel Canvas:
This canvas is divided and correlates all the necessary aspects of the project. It is
similar to the ideation canvas but it is more refined and to the point. Ideation is a
first step and then after further analysis idea funnel is created.
2.2 METHODOLOGY
Model Used For Project Development: Iterative Lifecycle Model
Justification for Using Iterative Lifecycle Model:
Software process model is a description of the sequence of activities carried out in
a Software Engineering Project, and the relative order of the activities. It is a
simplified description of a process, presented from a particular perspective. In

BIT(CSE) 9
essence, each stage of the software process is identified and a model is then
employed to represent the inherent activities associated within that stage.
An iterative lifecycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just
part of the software, which can then be reviewed in order to identify further
requirements. This process is then repeated, producing a new version of the
software for each cycle of the model. Consider an iterative lifecycle model which
consists of repeating the following four phases in sequence:
Fig 2.2.1 Iterative Lifecycle Model
Requirement phase is in which the requirements for the software are gathered and
analyzed. Iteration should eventually result in a requirements phase that produces
a complete and final specification of requirements. - A Design phase, in which a
software solution to meet the requirements is designed. This may be a new design,
or an extension of an earlier design.
- An Implementation and Test phase, when the software is coded, integrated and

BIT(CSE) 10
tested. A Review phase, in which the software is evaluated, the current
requirements are reviewed, and changes and additions to requirements proposed.
For each cycle of the model, a decision has to be made as to whether the software
produced by the cycle will be discarded, or kept as a starting point for the next
cycle (sometimes referred to as incremental prototyping). Eventually a point will
be reached where the requirements are complete and the software can be
delivered, or it becomes impossible to enhance the software as required, and a
fresh start has to be made.
The iterative lifecycle model can be likened to producing software by successive
approximation. Drawing an analogy with mathematical methods that use
successive approximation to arrive at a final solution, the benefit of such methods
depends on how rapidly they converge on a solution.
The key to successful use of an iterative software development lifecycle is
rigorous validation of requirements, and verification (including testing) of each
version of the software against those requirements within each cycle of the model.
The first three phases of the example iterative model is in fact an abbreviated form
of a sequential V or waterfall lifecycle model. Each cycle of the model produces
software that requires testing at the unit level, for software integration, for system
integration and for acceptance. As the software evolves through successive cycles,
tests have to be repeated and extended to verify each version of the software.
Cyclic Approach: Incrementally growing a system’s degree of definition and
implementation while decreasing its degree of risk. A set of anchor point
milestones: A combination of work products and conditions that are attained along

BIT(CSE) 11
the path of the spiral. We are also using the Pair Programming technique and the
Extreme Programming (XP) Methodology in our project.
2.3 SYSTEM ANALYSIS
2.3.1 STUDY OF CURRENT SYSTEM
Current systems gather and store data from field devices and make such data available for
acquisition, processing and presentation to users. However, while these systems gather
and store a variety of information about and from field devices, typically only a fraction
of the usable information is presented and made available to users. This may be so for a
variety of reasons: some useful data may not be captured; some useful data may not be
properly characterized; some useful data may be trapped in a proprietary database that
limits distribution and analysis; etc. As a result, key decision-makers operate in a context
of too little information, inaccurate information, or information that is old or stale.
2.3.2 PROBLEM AND WEAKNESS OF THE CURRENT SYSTEM
• Lack of presentation of the useful information: Current system gathers and
stores variety of information but only a fraction of information is showed to the
user at first.
• No Post allocation Procedure: current system only provides facility till the
project is allocated to a vendor.
• No project tracking: Current system does not allow the government official to
track the project progress.
• No automatic report generation: Current system doesn’t have any automated
procedure that can perform dynamic report generation.

BIT(CSE) 12
2.4 Requirements of New System
2.4.1 User Requirements
The user requirements for a system should describe the functional and non-functional
requirement so that they are understandable by system users who don’t have much
technical knowledge. They should specify the external behaviour of the system and
should avoid the design characteristics as far as possible. User requirements should not be
defined using implementation modes. The requirements include both conceptual and
detailed information. It expresses the concept that there should be configuration control
facilities provided as an inherent part of the system. It is good to practice to separate user
requirement from more detailed system in requirement document. Otherwise non-
technical reader of the user requirement may be overwhelmed by details which are really
only relevant for technicians.
Following are the Primary users of the System : Admin, Vendor, Officer
1. Admin
• Admin must define domain rules
• Admin must upload Agreement documents
• Admin must categorize the projects.
2. Vendor
• Vendor must Register himself
• Vendor should have internet access and android for using mobile
application
• Vendor should have internet connection and basic computer knowledge

BIT(CSE) 13
3. Officer
• Officer must be capable to upload timely progress report
• Officer should have internet access and android for using mobile
application
• Officer should have internet connection and basic computer knowledge
• Officer should have access to vendor tender details and plans
2.4.1.1 FUNCTIONAL REQUIREMENTS
2.4.1.1.1 Configuration Management
Input
Project Details
Processing
Project details are to be filled to create a new project, this represents the different
attributes of a project.
Output
A new project will be created
Input
Tender Details
Processing
These details are filled by vendor with respect to a particular project created by
the admin.
Output
A new tender will be created.
2.4.1.1.2 Account Management

BIT(CSE) 14
Input
Officer Details
Processing
These details are filled by admin to create a new officer. Afterwards these details
are forwarded to officer to manage his/her account.
Output
New officer will be created.
Input
Profile information (Admin, Vendor)
Processing
Basic information such as username, password, address, email id, phone number
etc filled up in the form, are stored and confirmation mail will be sent.
State
User Registering
Output
Profile generated, account created.
2.4.1.1.3 PROJECT PROGRESS
Input
Project Completion.
Processing

BIT(CSE) 15
This Symbolises the Completion i.e. work completed of the project. This helps to
build the completion graph for the project.
Output
Project Completion graph
2.4.1.2 NON FUNCTIONAL REQUIREMENT
EXTERNAL INTERFACE REQUIREMENTS
1. Hardware Interfaces
• The Android device is supposed to be of minimum 4.0 version to carry out
all the required operations.
• Net technology.
• Client Side:
1. (For best performance) Any GUI based terminal having at least 800 *
600 256-color displays.
2. 1024 X 768 32 bit recommended.
• Server Side:
3. Supported architectures: x86, x64, ia64(Windows Server 2008).
4. RAM: 96 MB (256 MB Recommended).
5. 400 MHz CPU (1.0 GHz Recommended).
6. 250 MB of Hard Disk space
2. Software Interfaces
• Operating System: Microsoft Windows XP, Microsoft Windows Server
2003, Windows Vista, Windows 7, Windows Server 2008.
• Web Server: IIS 6.0 and higher
• Server Side Scripting: .NET Framework 3.5 and Higher

BIT(CSE) 16
• SQL Server 2005 and higher
• Microsoft Word 2007 and higher
2.5 SYSTEM DESIGN
2.5.1 DATA MODELLING
2.5.1.1 Data Dictionary
Table 2.5.1.1.1: Vendor
Column Name Type Size Key Nullable
VendorID Int 100 Primarykey Notnullabe
Name Varchar 100 - -
Mobile no. Int 100 - -
EmailID Varchar 100 - -
Username Varchar 100 - -
Password Varchar 100 - -
Photo Varchar 5000 - -
domainID Int 100 ForeignKey -
CompanyName Varchar 100 - -
CreationTime Date-time 400 - -
Table 2.5.1.1.2: Officer
OfficerID Int 100 Primarykey Notnullable
MobileNo Int 100 - -
EmailID Varchar 100 - -
ProjectID Int 300 Foreignkey -
UserName Varchar 100 - -
Password Varchar 100 - -
Allocation Time Date-time 200 - -
Table 2.5.1.1.3: Tender
TenderID Int 200 Primarykey Notnullable

BIT(CSE) 17
VendorID Int 200 Foreignkey -
Details Varchar 5000 - -
Documents Varchar 5000 - -
ProposedCost Int 200 - -
Status Varchar 100 - -
ManPower Int 100 - -
EstimatedTime Date-time 200 - -
Table 2.5.1.1.4: Project
ProjectID Int 100 Primarykey Notnullable
DomainID Int 200 Foreignkey -
TenderDeadline Date-time 200 - -
ScheduledStartTime Date-time 200 - -
ScheduledEndTime Date-time 200 - -
StartTime Date-time 200 - -
EndTime Date-time 200 - -
Budget Int 5000 - -
Document Varchar 5000 - -
Status Varchar 100 - -
OfficerId Int 200 Foreignkey -
Table 2.5.1.1.5: Project Progress
ProjectProgressID Int 100 Primarykey Notnullable
OfficerID Int 200 Foreignkey -
ProgressTime Date-time 200 - -
PercentCompletion Int 100 - -
Photo Varchar 5000 - -
Latitude Int 200 - -
Longitude Int 200 - -
Table 2.5.1.1.6: Domain
DomainID Int 100 Primarykey Notnullable

BIT(CSE) 18
Rules Varchar 5000 - -
Agreement
Document
Varchar 5000 - -
Table 2.5.1.1.7: Review
ReviewID Int 100 Primarykey Notnullable
OfficerID Int 200 Foreignkey -
ReviewTime Date-time 200 - -
ReviewDetails Varchar 5000 - -
Rating Varchar 100 - -
2.5.2 ER DIAGRAM

BIT(CSE) 19
2.5.3 USE CASE DIAGRAM
Use case 1: Domain

BIT(CSE) 20
Figure 2.5.3.1: Domain
Use Case 2: User Account Search

BIT(CSE) 21
Figure 2.5.3.2: User Account Search
Use Case 3: Vendor Registration

BIT(CSE) 22
Figure 2.5.3.3: Vendor Registration
Use Case 4: Tender Filling

BIT(CSE) 23
Figure 2.5.3.4: Tender Filling
Use Case 5: Project Progress Mobile Tracking

BIT(CSE) 24
Figure 2.5.3.5: Project Progress Mobile Tracking
Use Case 6: Project Progress Web Tracking

BIT(CSE) 25
Figure 2.5.3.6: Project Progress Web Tracking
Use Case 7: Project Allocation and Officer Accounts

BIT(CSE) 26
Figure 2.5.3.7: Project Allocation and Officer Accounts
2.5.4 CLASS DIAGRAM

BIT(CSE) 27
Figure 2.5.4.1: Class Diagram
2.5.5 SEQUENCE DIAGRAM
Sequence 1: Admin

BIT(CSE) 28
Figure 2.5.5.1: Admin
Sequence 2: Vendor

BIT(CSE) 29
Figure 2.5.5.2: Vendor
Sequence 3: Officer

BIT(CSE) 30
Figure 2.5.5.3: Officer
2.5.6 ACTIVITY DIAGRAM

BIT(CSE) 31
Activity 1: Admin Activity
Figure 2.5.6.1: Admin Activity
Activity 2: Vendor Activity

BIT(CSE) 32
Figure 2.5.6.2: Vendor Activity
Activity 3: Officer Activity

BIT(CSE) 33
Figure 2.5.6.3: Officer Activity
Activity 4: Registration

BIT(CSE) 34
Figure 2.5.6.4: Registration
Activity 5: New Tender

BIT(CSE) 35
Figure 2.5.6.5: New Tender
Activity 6: Vendor Applies for Tender

BIT(CSE) 36
Figure 2.5.6.6: Vendor Applies For Tender
Activity 7: Admin Approves Tender

BIT(CSE) 37
Figure 2.5.6.7: Admin Approves Tender
Activity 8: Tracking

BIT(CSE) 38
Figure 2.5.6.8: Tracking
Activity 9: Forgot Password

BIT(CSE) 39
Figure 2.5.6.9: Forgot Password

BIT(CSE) 40
Activity 10: Notification
Figure 2.5.6.10: Notification

BITS/CSE/UDP/2014-2015/46 IMPLEMENTATION
BIT(CSE) 40
3. IMPLEMENTATION
3.1 SYSTEM ARCHITECTURE
'Three-tier' is a client-server architecture in which the users interface, functional process
logic ("business rules"), data storage and data access are developed and maintained as
independent modules, most often on separate platforms. The term "three-tier" or "three-
layer", as well as the concept of multitier architectures, seems to have originated within
rational Software.
The three-tier model is considered to be software architecture and a software design
pattern. Apart from the usual advantages of modular software with well-defined
interfaces, the three-tier architecture is intended to allow any of the three tiers to be
upgraded or replaced independently as requirements or technology change. For example,
a change of operating system from Microsoft Windows to UNIX would only affect the
user interface code.
Three nodes: client, application servers which process data for the clients and database
servers which store data for the application servers. This configuration is called three-tier
architecture.
The 3-Tier architecture has the following 3-tiers.
1. Presentation Tier
2. Logical Tier/Business Logic Tier/Application Tier
3. Data Tier

BIT(CSE) 41
Fig 3.1.1 3-Tier Architecture
3.1.1 Presentation Tier
The top-most level of the application is the user interface. The main function of
the interface is to translate tasks and results to something the user can understand.
This Tier is responsible for communication with the users and web service
consumers and it will use objects from Business Layer to response GUI raised
events.
3.1.2 Logical Tier/Business Logic Tier
The name Logical Tier is the combination of Business Tier and Data Access Tier.
This layer coordinates the application, processes commands, makes logical
decisions and evaluations, and performs calculations. It also moves and processes
data between the two surrounding layers. The advantages of separating the
Logical Tier into Business Tier and Data Access Tier are
Increases code transparency
Supports changes in Data Layer. You can change or alter database with out
touching the Business Layer and this would be a very minimum touch up.

BIT(CSE) 42
3.1.2.1 Business Tier
This sub tier contents classes to calculate aggregated values such like total revenue,
cash flow and this tier doesn’t know about any GUI controls and how to access
databases. The classes of Data Access Tier will supply the needy information from the
databases to this sub tier.
3.1.2.2 Data Access Tier
This tier acts as an interface to Data Tier. This tier knows how to (from which
database) retrieve and store information.
3.1.3 Data Tier
Here information is stored and retrieved from a database or file system. The information
is then passed back to the logical tier for processing, and then eventually back to the user.
We consider stored procedures as a part of the Data Tier. Usage of stored procedures
increases the performance and code transparency of an application.
3.2 SECURITY FEATURES
• The security consideration refers to the availability of the system to protect itself from
external attacks.
• Here during the login process anybody else except the three main users cannot log into the
system
• Location based tracing for the authentication of the project site.
• SHA-1 Algorithm used for encrypting the password.

BIT(CSE) 43
3.3 CODING STANDARDS
The coding standards is the well –defined and standard style of coding. With the help of
the coding standard any person can go into any code and figure out what is going on and
new people can get up to speedily. A coding standard sets out standard sets out standard
ways of doing several things such as the way variables are to be named, the code is to be
laid out, the comments are to be described, the work of function are to be carried out etc.
This section describes the coding standards, which we have used in the program. We have
adopted the following coding standards:
Variable Declarations
We have placed the local variable declarations at the beginning of the script.
Bock of declarations has aligned.
For multiple declarations we have used new declarations on the next line.
Creating the source code
We have added comments for each and every line of code that we have made.
We have added description of each and every function and their attributes and parameters.
General coding standards

BIT(CSE) 44
• It is acceptable to break up long statements on to multiple lines or leave it in one long
line.
• Do not put multiple statements in one line.
• Every coding lock must be indented.
• The standard indentation is three spaces.
• The use of white space and simple comments is strongly encouraged.
• Use switch statement if a large number of if conditions arise instead of using the number
of if-else statements.
• All the functions, variables and constants have to be declared on the top of the file in
particular form.
Naming conventions
Naming conventions make programs more understandable by making them easier to read.
They can also give information about the function of identifier.
Table 3.3.1: Naming Conventions
IDENTIFIER TYPE RULES OF NAMING EXAMPLE
Methods Methods should be verb;
in mixed case with the
first letter of the verb
should be lower case. And
after that every first letter
of consecutive word
should be upper case.
e.g. getData()
Variables All the variables should e.g. PersonName

BIT(CSE) 45
start with upper case
letters. It should not start
with _ or $ characters.
Comment standard:
• Every script should begin with a comment block, which describes the scripts purpose;
any arguments used (if applicable), and return values (if applicable), inputs-outputs, and
name of script.
• Comments may also be used in the body of the script to explain individual sections or
lines of code.
• It is also used to describe variable definition or declaration.
Programming conventions:
We have listed below some general conventions to be followed in programming.
• Statement: we have written only one statement per line.
• Indenting: Improve the reliability of script by using tabs to indent the body of statements
such as these:
DO……LOOP
FOR……NEXT
IF……THEN
• Also use a tab to indent statements continued onto new line.
• We have made separate module form for global variable declarations.

BIT(CSE) 46
3.4 SCREEN SHOTS

BIT(CSE) 47
Figure 3.4.1 Login Page

BIT(CSE) 48
Figure 3.4.2 Registration Page

BIT(CSE) 49
Figure 3.4.3 Vendor Home Page
Figure 3.4.4 Admin Home Page

BIT(CSE) 50
Figure 3.4.5 New Tender Page

BIT(CSE) 51
Figure 3.4.6 New Project
Figure 3.4.7 Manage Project

BIT(CSE) 52
Figure 3.4.8 Create Officer
Figure 3.4.9 View Tenders

BIT(CSE) 53
Figure 3.4.10 Vendor Search
Figure 3.4.11 Manage and Assign Officer

BIT(CSE) 54
Figure 3.4.12 Vendor Profile
Figure 3.4.13 Project Search

BIT(CSE) 55
Figure 3.4.14 Ongoing Projects
Figure 3.4.15 Vendor Tenders

BIT(CSE) 56
Figure 3.4.16 Project Details
Figure 3.4.17 Add Tender

BIT(CSE) 57
Figure 3.4.18 Vendor Progress
Figure 3.4.19 Change Officer Details

BIT(CSE) 58
Figure 3.4.20 Allotted Project
Figure 3.4.21 Officer Progress

BIT(CSE) 59
3.5 TESTING/VERIFICATION
Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test. Software testing
can also provide an objective, independent view of the software to allow the business
to appreciate and understand the risks of software implementation. Test techniques
include, but are not limited to the process of executing a program or application with
the intent of finding software (errors or other defects).
Software testing can be stated as the process of validating and verifying that a
computer Program/application/product:
• Meets the requirements that guided its design and development,
• Works as expected,
• Can be implemented with the same characteristics,
• Satisfies the needs of stakeholders.
Software testing, depending on the testing method employed, can be implemented at
any time in the software development process. Traditionally most of the test effort
occurs after the requirements have been defined and the coding process has been
completed, but in the agile approaches most of the test effort is on-going. As such, the
methodology of the test is governed by the chosen software development
methodology.
The following are the commonly used terms associated with the testing;-
• A failure is a manifestation of an error (or defect or bug).But the mere presence of

BIT(CSE) 60
An error may not necessarily lead to a failure
• A test case is the triplet [I,S,O],where I is the data input to the system, S is the state
of the system at which the data is input and O is the expected output of the system.
• A test suite is the set of all test cases with which a given software product is to be
tested.
3.5.1 TESTING PLAN
A test plan documents the strategy that will be used to verify and ensure that a
product or system meets its design specifications and other requirements
A test plan may include one or more of the following:
• Design Verification or Compliance test - to be performed during the development or
approval stages of the product, typically on a small sample of units.
• Manufacturing or Production test - to be performed during preparation or assembly
of the product in an ongoing manner for purposes of performance verification and
quality control.
• Acceptance or Commissioning test - to be performed at the time of delivery or
installation of the product.
• Service and Repair test - to be performed as required over the service life of the
product.

BIT(CSE) 61
• Regression test - to be performed on an existing operational product, to verify that
existing functionality didn't get broken when other aspects of the environment are
changed (e.g., upgrading the platform on which an existing application runs).
3.5.1.1 Test coverage
Test coverage in the test plan states what requirements will be verified during what
Stages of the product life. Test Coverage is derived from design specifications and
other requirements, such as safety standards or regulatory codes, where each
requirement or specification of the design ideally will have one or more
corresponding means of verification. Test coverage for different product life stages
may overlap, but will not necessarily be exactly the same for all stages. For
example, some requirements may be verified during Design Verification test, but
not repeated during Acceptance test. Test coverage also feeds back into the design
process, since the product may have to be designed to allow test access .
3.5.1.2 Test Methods
Test methods in the test plan state how test coverage will be implemented. Test
methods may be determined by standards, regulatory agencies, or contractual
agreement, or may have to be created new. Test methods also specify test
equipment to be used in the performance of the tests and establish pass/fail criteria..
3.5.1.3 Test Responsibilities
Test responsibilities include what organizations will perform the test methods and
at each stage of the product life. This allows test organizations to plan, acquire or
develop test equipment and other resources necessary to implement the test
methods for which they are responsible. Test responsibilities also includes, what
data will be collected, and how that data will be stored and reported (often referred
to as "deliverables"). One outcome of a successful test plan should be a record or

BIT(CSE) 62
report of the verification of all design specifications and requirements as agreed
upon by all parties.
3.5.2 TESTING STRATEGY
As we are working in pairs, we adopted the method of Pair Programming and thus
the testing method was Pair Testing wherein two team members worked together at
one keyboard to test the software application. One member did the testing and the
reviewed and analyzed the test. This helped both team members to learn more about
the application. It narrowed down the root cause of the problem while continuous
testing. We could find out which portion of the source code affected by the bug.
This track can help to make the solid test cases and narrowing the problem for the
next time. Less participation was required for testing and for important bugs root
cause could be analyzed very easily. This is more applicable where the requirements
and specifications are not very clear, the team is very new, and needs to learn the
application behaviour quickly.
3.5.3 TESTING METHOD
LEVELS OF TESTING
Testing is usually relying on to detect the faults on each phase, in addition to the
faults introduced during the coding phase itself. Due to this, different levels of testing
are used in the testing process, each level of testing aims to test different aspect of a
system.

BIT(CSE) 63
Fig 3.5.1 Testing
3.5.3.1 Unit Testing
Unit Testing will be done to test field validations, navigation, functionality of the
programs and its blocks. These tests are applied on various functions within each
program and other critical program blocks.
3.5.3.2 Module Testing
Module testing will be done to test the interaction between the various programs
within one module. It checks the functionality of each program with relation to other
programs within the same module. It then tests the overall functionality of each
module.

BIT(CSE) 64
3.5.3.3 Integration Testing
Integration testing is done to test the functionality and interfacing between the
modules. These modules should work together in a seamless way to achieve the
desired results. Integration testing will test for this property of the modules. The
modules display a cause and effect relationship, if data in one module is changed,
then it affects the data to change in some other module also. Integration testing
needs to check if the modifications do not adversely affect some other modules.
3.5.3.4 Acceptance Testing
Acceptance testing was done after the implementation of the system. The acceptance
testing will check if the system works correctly in the user environment and if the
entire user specified functionalities are present. It also tests if the system adheres to
the company policies and quality standard.
3.5.4 White Box Testing
Uses the control structure part of component-level design to derive the test cases
These test cases guarantee that all independent paths within a module have been
exercised at least once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.

BIT(CSE) 65
3.5.5 Black Box Testing
Complements white-box testing by uncovering different classes of errors.
Focuses on the functional requirements and the information domain of the
software.
Used during the later stages of testing after white box testing has been performed.
The tester identifies a set of input conditions that will fully exercise all functional
requirements for a program.
The test cases satisfy the following:
Reduce, by a count greater than one, the number of additional test cases that must
be designed to achieve reasonable testing.
Tell us something about the presence or absence of classes of errors, rather than
an error associated only with the specific task at hand.
3.5.6 Grey Box Testing
Grey-box testing involves having knowledge of internal data structures and
algorithms for purposes of designing tests, while executing those tests at the user, or
black-box level. The tester is not required to have full access to the software's source
code Manipulating input data and formatting output do not qualify as grey-box,
because the input and output are clearly outside of the "black box" that we are calling
the system under test. This distinction is particularly important when conducting
integration testing between two modules of code written by two different developers,
where only the interfaces are exposed for test.

BIT(CSE) 66
However, tests that require modifying a back-end data repository such as a database
or a log file does qualify as grey-box, as the user would not normally be able to
change the data repository in normal production operations Rey-box testing may also
include reverse engineering to determine, for instance, boundary values or error
messages.
By knowing the underlying concepts of how the software works, the tester makes
better informed testing choices while testing the software from outside. Typically, a
grey-box tester will be permitted to set up an isolated testing environment with
activities such as seeding a database. The tester can observe the state of the product
being tested after performing certain actions such as executing SQL statements
against the database and then executing queries to ensure that the expected changes
have been reflected. Grey-box testing implements intelligent test scenarios, based on
limited information. This will particularly apply to data type handling, exception
handling, and so on.
3.5.7 Stress Testing
Stress testing is to test the system for the emergent properties such as performance
and reliability .Performance tests have to be designed to ensure that the system can
process its intended load. Here, we checked out the multi user capability of our
system.

BIT(CSE) 67
3.6 Test Cases
Table 3.6.1 Project Details
Sr.No Test Case Input Expected
Output
Actual Output
1 If name is blank - Required Field Enter Valid
Name
2 If Domain is
blank
- Required Field Select Valid
Domain
3 If Scheduled
Start and End
time and
Tender
Deadline is
Blank
- Required Field Select Valid
Date
4 If Budget and
Details are
Empty
- Required Field Ender Valid
Values
5 If Document
Not Uploaded
Upload
Document
Required Field Select Valid
Document

BIT(CSE) 68
Table 3.6.2 Tender Detail
Output
Actual Output
1 If Tender
Details is blank
- Required Field Enter Detail
2 If Document
Not Uploaded
Upload
Document
Required Field Select Valid
Document
3 If Proposed
Cost is Empty
- Required Field Enter Cost
4 If Estimated
Time is Empty
- Required Field Enter valid date
5 If Status not
Selected
Dropdown Required Field Select Valid
Status
6 If Man Power
Required is
Empty
- Required Field Enter valid
Value

BIT(CSE) 69
Table 3.6.3 Officer Details
Output
Actual Output
1 Officer name is
blank
- Required Field Enter Name
2 Mobile number
is blank
- Required Field Enter Mobile
number
3 Email ID is
empty
- Required Field Enter valid
Email ID
4 If Username is
empty
- Required Field Enter Username
5 If Password Is
empty
- Required Field Enter Valid
Password
6 If Allocation
Time is empty
Date Picker Required Field Select valid
Date
Table 3.6.4 Progress Detail
Output
Actual Output
1 If Vendor
Progress is
blank
- Required Field Enter
Percentage
Completion
2 If Officer
Progress is
blank
- Required Field Enter
Percentage
Completion

BIT(CSE) 70
3.6.5 Assign Tender
Output
Actual Output
1 If Project Status
is Created
Click Edit
button
Save Button
Enabled
Save Button
Enabled
2 If Project Status
is Started
Click Edit
button
Save Button
Disabled
Save Button
Disabled

BITS/CSE/UDP/2014-2015/46 CONCLUSION
BIT(CSE) 70
4. CONCLUSION
4.1 SUMMARY OF RESULTS
Our project “Tender Timeline Tracker” is a system or rather a web portal where
government will be able to handle their project–tender body very easily. The government
will be able to handle all its projects select appropriate tender for it, assign officer to each
project. In short all the processes that has to be done in the government office can be
handled online via our project.
Moreover government will be able to track down the project progress throughout its
timeline and also an android app will be made available for the officers so that they can
easily upload their progress report irrespective of their location.
4.2 ADVANTAGES
• User interactive in nature
• Ease of use for government officials
• Reduces paper work
• Project tracking
• Reviewing system
4.3 SCOPE OF FUTURE WORK
For future enhancement of our project our focus will be on following points:
• Online Biding.
• Recommendation feature which means, admin will be able to see the recent
recommendation of officers for particular type of project
• Mobile app for all platforms

BITS/CSE/UDP/2014-2015/46 CONCLUSION
BIT(CSE) 71
REFERENCES
BOOKS
1) Android Apps for Absolute Beginners 2011.
2) The .NET framework Black book.
3) Professional ASP.NET 4 in C# and VB by Bill Evjen, Scott Hanselman and Devin
Rader.
WEBSITES
csharp.net-tutorials.com
developer.android.com
www.asp.netajax.com
www.codeproject.com
www.developer.android.com
www.jqueryui.com
www.google.com
www.stackoverflow.com
www.w3school.com
www.wikipedia.com
www.tutorialpoints.com
www.youtube.com

110050131121 Page 1
BMC Report
The Business Model Canvas is a pictorial representation of your creative process of envisioning one or
more prototype models in a process of transformation or development of a high-level characterization of
your firm/business
1. The whole BMC sheet:

110050131121 Page 2
2. Each canvas elements:
The elements are:
1. WHAT:
1.1
Value Proposition:
It describes that which problem are we going to solve given by the customer.
• Project Tracking
• Project Authentication
• Simplified Government Tendering System

110050131121 Page 3
2. WHO:
1.1.
Customer Segments:
It describes that who will be our most valuable customer for whom we are going
to develop the system.
• Vendors
• Development companies.
• Government

110050131121 Page 4
1.2.
Customer Relationships
It describes that how the customer segment aspect us to develop the relationship.
• Vendor Officer Review
• Email Alerts

110050131121 Page 5
1.3.
Channels
It describes that what channel we would like to use to reach to our customer
segment.
• Marketing

110050131121 Page 6
3. HOW:
1.1.
Key Partnerships
It describes the supplier from which our key components are been supplied which
are as follows:
• Not applicable to project.

110050131121 Page 7
Key Activities
It describes that what are the key activities need for revenue stream, distribution
channel and customer relationship.
• Timely payments due to regular update
• Cooperation.
• Loyalty

110050131121 Page 8
1.2.
Key Resources
It describes that what the key resources need for the establishing are a connection
and for the employees. It includes:
• Hardware support.
• Server Support
• Internet Support

110050131121 Page 9
4. HOW MUCH:
1.1.
Revenue Streams
It describes that for what do our customer current pay and which form of finance
scheme involves so as how would they be interested to pay to us.
• They don’t have to pay.
1.2.
Cost Structure
It describes that what will be the most important cost which would be included in
our System development.
• Domain Cost.
• Development Cost.
• Progress tracking Cost.

GIC Patent Drafting Exercise Team ID:
FORM 1
THE PATENTS ACT 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003
APPLICATION FOR GRANT OF PATENT
(FOR OFFICE USE ONLY)
Application No:
Filing Date:
Amount of Fee paid:
CBR No:
GTU Innovation Council
Patent Drafting Exercise (PDE)
15302
1. Applicant(s) :
ID Name Nationality Address Mobile No. Email
Prajwal Kishor
Chaudhari
GTU 9601400027 chaudhari.prajwal
0@gmail.com
Indian1
Prutha
Anilkumar
Muley
GTU 8460326748 pruthamuley@g
mail.com
Indian2
Pooja
Devshibhai
Solanki
GTU 9978872264 pooja.ahir1994@
gmail.com
Indian3
Pallav
Bhupenkumar
Shah
GTU 9722915809 pallavshah78@g
mail.com
Indian4
2. Inventor(s):
This is just a mock Patent Drafting Exercise (PDE) for semester 8, BE students of GTU.
These documents are not to be submitted with any patent office.
Note :
Page 1 of 5

Mobile No. EmailAddressNationalityNameID
Prajwal Kishor
Chaudhari
GTU 9601400027 chaudhari.prajw
al0@gmail.com
Indian1
Prutha Anilkumar
Muley
GTU 8460326748 pruthamuley@g
mail.com
Indian2
Pooja Devshibhai
Solanki
GTU 9978872264 pooja.ahir1994
@gmail.com
Indian3
Pallav
Bhupenkumar
Shah
GTU 9722915809 pallavshah78@
gmail.com
Indian4
3. Title of Invention/Project:
Tender Timeline Tracker
4. Address for correspondence of applicant/authorized patent agent in india
Name:
Address:
Mobile:
Email ID:
GTU
9601400027
chaudhari.prajwal0@gmail.com
5. Priority particulars of the application(S) field in convention country
Name of the Applicant Title of the InventionFiling DateApplication No.Country
N/AN/AN/AN/AN/A
6. Particulars for filing patent co-operation treaty (pct) national phase Application
International application number International filing date as alloted by the receiving office
N/A N/A
7. Particulars for filing divisional application
Original(First) Application Number Date of filing of Original (first) application
N/A N/A
Note :
Page 2 of 5

8. Particulars for filing patent of addition
Original(First) Application Number Date of filing of Original (first) application
N/A N/A
9. DECLARATIONS:
(i) Declaration by the inventor(s)
I/We, the above named inventor(s) is/are true & first inventor(s) for this invention and declare that the
applicant(s).
herein is/are my/our assignee or legal representative.
Date : 22 - April - 2015
Signature & DateName
1 Prajwal Kishor
Chaudhari
2 Prutha Anilkumar
Muley
3 Pooja Devshibhai
Solanki
4 Pallav Bhupenkumar
Shah
(ii) Declaration by the applicant(s) in the convention country
I/We, the applicant(s) hereby declare(s) that:-
(iii) Declaration by the applicant(s)
I/We, the applicant (s) in the convention country declare that the applicant(s) herein is/are my/our
assignee or legal representative.applicant(s)
Note :
Page 3 of 5

I am/We in possession of the above mentioned invention.
The provisional/complete specification relating to the invention is filed with this aplication.
The invention as disclosed in the spcification uses the biological material from India and the necessary
permission from the competent authority shall be submitted by me/us before the grant of patent to me/us.
There is no lawful ground of objection to the grant of the patent to me/us.
I am/we are the assignee or the legal representative of true & first inventors.
The application or each of the application,particulars of each are given in the para 5 was the first applicatin in
the convention country/countries in respect of my/our invention.
The application or each of the application,particulars of each are given in the para 5 was the first applicatin in
the convention country/countries in respect of my/our invention.
I/we claim the priority from the above mentioned applications(s) filed in the convention country/countries &
state that no application for protection in respect of invention had been made in a convention country before
that date by me/us or by any person
My/Our application in india is based on international application under Patent Cooperation Treaty (PCT) as
mentioned in para 6
The application is divided out of my/our application(s) particulars of which are given in para 7 and pray that
this application may be treated as deemed to have been filed on ___________under section 16 of the Act.
The said invention is an improvement in or modification of the invention particulars of ehivh are given in para
8.
(a) Provisional specification/Complete specification
(b) Complete specification(In confirmation with the international application) / as amended before the
international Preliminary Examination Authority (IPEA),as applicable(2 copies),No.of pages.....No.of
claims.....
(c) Drawings (In confirmation with the international application)/as amended before the international
Preliminary Examination Authority(IPEA),as applicable(2 copies),No.of sheets....
(d) Priority documents
(e) Translations of priority documents/specification/international search reports
(f) Statement and undertaking on Form 3
(g) Power of Authority
(h) Declaration of inventorship on Form 5
(i) Sequence listing in electronic Form
(j) ........................................ Fees Rs.XXX in Cash /Cheque/Bank Draft bearin No.XXX Date: XXX on XXX
Bank.
10. Following are the attachments with the application:
I/We hereby declare that to the best of my /our knowledge, information and belief the fact and mtters stated
herein are correct and I/We request that a patent may be granted to me/us for the said invention.
Dated this 22 day of April , 2015
Note :
Page 4 of 5

Name Signature & Date
1 Prajwal Kishor
Chaudhari
2 Prutha Anilkumar
Muley
3 Pooja Devshibhai
Solanki
4 Pallav Bhupenkumar
Shah
Note :
Page 5 of 5

FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
PROVISIONAL SPECIFICATION
15302
1. Title of the project/invention :
Tender Timeline Tracker
Prajwal Kishor Chaudhari , ( Indian )
Address :GTU
Prutha Anilkumar Muley , ( Indian )
Address :GTU
Pooja Devshibhai Solanki , ( Indian )
Address :GTU
Pallav Bhupenkumar Shah , ( Indian )
Address :GTU
2. Applicant(s) :
3. Preamble to the description :
The following specification describes the invention.
4. Description :
a. Field of Application / Project / Invention :
IT- Govt Website-Tender System
b. Prior Art / Background of the Invention / References :
1.) A framework of electronic tendering for government procurement: a lesson learned in Taiwan
2.) A process for securing tendering system
c. Summary of the Invention/Project :
Now days different government organizations are getting there work environment online. The Indian
government over past few years have developed many of its working bodies online. Department of
government Projects for India is one such department that needs to be on line for the better
functionality and easy to access data. Our system “Tender timeline tracker” helps the government
as well as the vendors seeking to fill up tenders for new project.
This system helps the government official to keep track of the project progress, other than this
it also helps the admin to look over and compare the project progress reports of officer allocated to
the project and that of submitted by vendor. Vendors will be able to keep themselves updates with
the new projects plans proposed by the Government and fill up for the same.
Other facility which will be provided is a mobile application that will be handy to use by all the
users of the application
d. Objects of the Invention/Project :
1) Vendor, Officer and Admin functionalities
2) Project Tracking
3) Reviewing
Note :
Page 1 of 3

e. Drawing(s) :
f. Description of the Invention
Project Tender Timeline Tracker as the name suggests it tracks the government projects, more
over it also helps in handling the Tendering system of the government. it manages tenders and
projects of the government. the Project consists of three main actors i.e. Vendor, Officer and Admin
-Vendor is the one who proposes the tender for a project
-Admin will create a project and will select the appropriate tender for the same and also will assign
an officer to look upon that project. admin can also review a vendor for future reference
-Officer is assigned to a project by the Admin. his work is to generate monthly or timely report of the
completion of the project which is easy for him through our mobile application.
g. Examples
h. Unique Features of the Project
-Project tracking
-Mobile App
-Vendor Reviewing
-Project Completion Graph
5. Date & Signature :
Date : 23 - April - 2015
Sign and Date
Prajwal Kishor
Chaudhari
Sign and Date
Prutha Anilkumar
Muley
Sign and Date
Pooja Devshibhai
Solanki
Sign and Date
Pallav Bhupenkumar
Shah
6. Abstract of the project / invention :
The application will be an integrated web based application which will behold all the information and
handling of the tenders passed and proposed by the government of India. Here the vendors will be able to
look up the upcoming tenders. As per the project title suggests one will be able to see the tender ’s project
progress throughout the project run time.
Other than these information, a government official which is assigned for a particular project will be able
to see the progress report of the project and compare it graphically with the one committed by the
contractor, through this the official can give further guidelines to the contractor for the further approach in
the project and contractor will be able to make the changes accordingly.
Other facility which will be provided is an Android application which will keep on updating the contractors
about the new tenders and to the government official about the progress report of a particular project.
Drawing Attachments :
Note :
Page 2 of 3

Note :
Page 3 of 3

FORM 3
THE PATENTS ACT, 1970
(39 OF 1970)
&
STATEMENT AND UNDERTAKING UNDER SECTION 8
15302
1. Declaration :
Prajwal Kishor Chaudhari ,
Prutha Anilkumar Muley ,
Pooja Devshibhai Solanki ,
Pallav Bhupenkumar Shah ,
I/We,
Prajwal Kishor Chaudhari ( Indian )
Address : GTU
Prutha Anilkumar Muley ( Indian )
Address : GTU
Pooja Devshibhai Solanki ( Indian )
Address : GTU
Pallav Bhupenkumar Shah ( Indian )
Address : GTU
2. Name, Address and Nationality of the joint Applicant :
Name of the
Country
Date of
Application
Application
Number
Status of the
Application
Date of
Publication
Date of
Grant
N/A N/A N/A N/AN/AN/A
(i) that I/We have not made any application for the same/substantially the same
invention outside India.
(ii) that the right in the application(s) has/have been assigned to,
Here by declare:
(iii) that I/We undertake that up to the date of grant of patent by the Controller , I/We
would keep him inform in writing the details regarding corresponding application(s)
for patents filed outside India within 3 months from the date of filing of such
application.
Dated this 23 day of April , 2015.
3. Signature of Applicants :
Note :
Page 1 of 2

Sign and Date
Sign and Date
Prutha Anilkumar Muley
Sign and Date
Pooja Devshibhai Solanki
Sign and Date
Pallav Bhupenkumar
Shah
To
The Controller of Patent
The Patent Office, at Mumbai.
Note :
Page 2 of 2

Full UnderGrad Project Report : Tender Timeline Tracker

Recommended

Recommended

More Related Content

What's hot

What's hot (8)

Similar to Full UnderGrad Project Report : Tender Timeline Tracker

Similar to Full UnderGrad Project Report : Tender Timeline Tracker (20)

More from Pallav Shah

More from Pallav Shah (6)

Recently uploaded

Recently uploaded (20)

Full UnderGrad Project Report : Tender Timeline Tracker