ABSTRACT
Tender Monitoring System is an online web application used for monitoring the progress of different activities of construction projects like Buildings, Road, Bridges, ports etc from Planning to Execution Stage after passing the tender.
The system prepare online monthly progress report and progress graph of all projects and provides current status of project by videos and snapshot. The details, progress reports, progress graph, videos can be submitted by system and reviewed by all officers, Tender cell, collector of area and admin as well.
The system is established to ensure timely completion and maintain an effective planning, Monitoring and control system which including mobilization of required persons. The system is designed to get quickly and accurate information to ensure efficient and transparent working.
INDEX
Chapter Title Page No
ACKNOWLEDGEMENT i
ABSTRACT ii
COMPANY PROFILE iii
LIST OF TABLES iv
LIST OF FIGURES v
1 Introduction 1
1.1 Project Summary 1
1.2 Purpose 1
1.3 Scope 2
1.4 Technology and Literature Review 4
2 System Requirements Study 6
2.1 User Characteristics 6
2.2 Hardware and Software Requirements 9
2.3 Constraints
2.4 Timeline Chart and Process model 10
3 System Analysis 12
3.1 Study of Current System 12
3.2 Problem and Weaknesses of Current System 12
3.3 Requirements of New System 13
3.4 Feasibility Study 13
3.5 Requirements Validation 15
3.6 Functions Of System 16
3.6.1 Use Cases 17
3.7 Data Modeling 17
3.7.1 E-R Diagram
3.7.2 Class Diagram 18
3.7.2 System Activity or Object interaction Diagram 18
3.7.3 Data dictionary 20
3.8 Control flow diagram 24
3.9 Main Modules Of New System 29
4 System Design 35
4.1 Data Structure Design 35
4.1.1 Table and Relationship 37
4.2 System Procedural Design 40
4.2.1 Designing Pseudo code or algorithm for Method or operations (Algorithm use in your project ex for encrypt password)
4..3 Input/Output and Interface Design
4.3..1 Access Control and Security(Which form is accessed by user/admin and which type of security provided in your project)
4.3.2 State-Transition Diagram
4.3.3 Sequence Diagram 40
5 Implementation Planning and Details
5.1 Implementation Environment
5.2 Module Specification
5.3 Security Features
5.4 Coding Standards
5.5 Sample Coding
6 Testing
5.1 Test Plan
5.2 Test Strategy
5.3 Test Methods
5.4 Test Cases
7 Screenshots
8 Limitation And Future Enhancement
CONCLUSION 41
REFERENCES 42
1. INTRODUCTION
1.1 PROJECT SUMMARY
Project Definition:-
Tender Monitoring System(TMS):-
A TMS System (or Tender Monitoring System) facilitates the complete tendering process the entire tender and the corrigenda details can be viewed. Also the tender notices, tender documents, corrigenda notices can be downloaded from the website. The system prepare online monthly progress report and progress graph of all projects and provides current status of project by videos and snapshot.
1.2 PURPOSE
Existing System
Security:
The manual process is not very secure. In the new system, the passwords are generated automatically so only the members know their passwords.
Tender Status:
Finding out the tender status (Allocated/Non-Allocated) is time consuming.
No Searching Facility:
There are no searching facilities for tenders such as search by tendering department, category, amount, date, type, etc. in the existing system.
Limited Tender Details Available Online:
Only the name of work, issue date and bid closing date is available online. Other details like estimated cost, tendering department, category etc. are not displayed.
Not As Accurate And Fast:
Retrieving information is slower as everything is managed manually. Since, everything is managed manually; there might be a lack of accuracy.
Need for a new system
To check the status of Tenders:
Such a facility will enable the contractors to know the status (Allocated/Non-Allocated) of the tenders easily and quickly.
Security:
The existing system is not so secure. The new system is password protected so no any modification may do after assign the tender.
Faster retrieval of information:
Retrieval of information becomes easier compared to the manual system. Details regarding tenders, corrigenda, bidders, feedback etc are available easily.
1.3 SCOPE
• Table updates according to user input
Deleting and Modification of existing records update the table accordingly.
• Graphical User Interface Facility
• Improvised reports.
Reports have been improvised with the facility for individual and group items separately.
• Multiple Operations available in a single form.
Facility to add, modify, delete, update etc. are provided in the same form so that the user does not have to switch over from one form to another form to the same.
Tangible Benefits:
• Reduction of paper work as a result cost of stationary reduces.
• Category wise Tender reports.
Intangible Benefits:
• Accurate and timely reports are available as a result efficiency of the inspector increases.
• Since the application is accessible from anywhere the time in accessing the information is highly reduced.
• Security would be available from unauthorized users and each user’s access to the different parts of the application.
2. SYSTEM REQUIREMENT STUDY
2.1 USER CHARACTERISTICS
In our application, there are 3 types of users which are as below.
1. Admin
2. Inspector
3. Contact Person
2.2 HARDWARE AND SOFTWARE REQUIREMENT
NOTE: These requirements of the system are minimum. So to run this application on the system this is minimum required to execute application efficiently.
HARDWARE REQUIRED:
Application Server and Database Server
Pentium IV PC with 2.4 Ghz CPU
1024 MB of RAM
80 GB Hard Disk
CD read/write
Colour graphics Monitor
Key Board
Mouse
LAN connectivity by 10/100 MBPS Ethernet card/Internet Connectivity
For Client Machine
Pentium II/III/IV PC
Min. 64 MB of RAM (Recommended :256 MB)
Key Board
Mouse
LAN connectivity by 10/100 MBPS Ethernet card/Internet Connectivity
SOFTWARE REQUIRED:
Application Software : Browser (Mozilla Firefox, Internet Explorer, Google Chrome etc.)
Operating System : Window 8, Window 8.1,Window 7, Window XP, Linux
2.3 CONSTRAINTS
2.3.1 Regulatory Polices
As per the Company’s policy any developer has to maintain the Coding Standards. Also each and every user should maintain the subversion and commit the modification with appropriate comment so to have track of work and also of the code modification.
From the Admin’s perspective:
1. Developer should use well known Technology.
2. Developer should use well known Coding Standards.
2.3.2 Hardware Limitation
The hardware limitation is very low. The configuration of the Admin’s PC should be high memory wise.
From the Admin’s perspective:
Admin is having required system configuration to run the system
2.3.3 Interface to other Applications
There is no application using this application as an interface so-far.
2.3.4 Parallel Operations
There are no parallel operations as such executing during the operation of the current application.
2.3.5 Higher Order Language Requirement
In my service I have used C# as higher order language. It uses 3-tier architecture which follows pure MVC structure for implementation or maintenance.
2.3.6 Reliability Requirements
Reliability requirement of the system are one of the prime ones in the last. The system needs to be highly reliable in terms of performance but at this stage where the complete system is far completion we can’t judge its reliability. All could do is to make the individual module we have developed to be reliable as possible.
2.3.7 Criticality of the Application
The main criticality of this system is if the server goes down then this system won’t work. Or else in case of traffic increasing the server would not able to control the traffic system goes down.
Criticality means any occurrence of miss operating of the system or any accidental event in software which can damage the resources of software as well as hardware.
As per my knowledge there is no criticality in our Application.
2.3.8 Safety Security Consideration
The main concern for the safety is that only the users registered on this site should be able to access the tenders.
Moreover the pages to manage the working capital should only be accessible to the Data Soft employees having admin rights to the system.
Both these concerns have been attended to by using various measures.
3. SYSTEM ANALYSIS
3.1 STUDY OF CURRENT SYSTEM:
In Past, there is no any process online for issue a new tender. But all process work offline on paperwork. If any new tender is issue than organization gives an advertisement in a website, newspaper or any other resources. Newspaper contains only few detail of tender, if any more detail required than contractor physically visited the organization .All process from issue a new tender to allocate a tender to the contractor is on paper work. So the tenders and corrigendum’s, contractor’s Portfolio and bid details are managed manually. No online registration and subscription provided.
3.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM
The tenders have to download the documents from the website while the rest of the process is manual. The manual process is not very secure. In the new system, the passwords are generated automatically so only the members know their passwords. Retrieving information is slower as everything is managed manually. Since, everything is managed manually; there might be a lack of accuracy.
3.3 REQUIREMENTS OF NEW SYSTEM
Tender Monitoring System is an online web application used for monitoring the progress of different activities of construction projects like Buildings, Road, Bridges, ports etc from Planning to Execution Stage after passing the tender. The system prepare online monthly progress report and progress graph of all projects and provides current status of project by videos and snapshot.
The details, progress reports, progress graph, videos can be submitted by system and reviewed by all officers, Tender cell, collector of area and client as well. The system is established to ensure timely completion and maintain an effective planning, Monitoring and control system which including mobilization of required persons. The system is designed to get quickly and accurate information to ensure efficient and transparent working.
The system is designed to minimize the manual work and increases the efficiency of the work as possible as.
3.4 FEASIBILITY STUDY
A feasibility study is an evaluation and analysis of the potential of the proposed project which is based on extensive investigation and research to support the process of decision making. Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of an existing business or proposed venture, opportunities and threats present in the environment, the resources required to carry through, and ultimately the prospects for success.
A feasibility study evaluates the project’s potential for success; therefore, the perceived objectivity is an important factor in the credibility to be placed on the study by potential investors and lending institutions
It must therefore be conducted with an objective, unbiased approach to provide information upon which decisions can be based.
Feasibility study is an outline description of the system and how it will be used within an organization.
Three test of feasibility studied by us:
1) Technical Feasibility
2) Economical Feasibility
3) Operational Feasibility
1. Technical Feasibility:
The technical feasibility assessment is focused on gaining an understanding of the present technical resources of the organization and their applicability to the expected needs of the proposed system. It is an evaluation of the hardware and software and how it meets the need of the proposed system.
At this stage, we checked our website against the technical feasibilities. The website has been developed with ASP.NET fronted Tools with C# Framework and SQL server explorer as back end tools. It requires database interaction and good interface design this can be easily done. Hence, TMS would be technically feasible.
2. Economical Feasibility:
The purpose of the economic feasibility assessment is to determine the positive economic benefits to the organization that the proposed system will provide. It includes quantification and identification of all the benefits expected. This assessment typically involves a cost/ benefits analysis.
Economical feasibility looks at the financial aspects of the investments in a project. From the financial point of view the project is feasible. In this system we are using plans to acquire the necessary hardware and software require for the system and there is no economical hindrance towards its purchase. so, We guess there will not be any bigger monetary requirement for our project.
3. Operational Feasibility:
Operational feasibility is a measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development.
Test of operational feasibility asks if the system will work when it is developed and used. In addition to economical and financial, we checked our TMS project against the operational feasibility. As a conclusion, we found that user with basic computer operating skills would be able to understand and operate the TMS well. System provides the user friendly interface which helps new users in operating the project.
3.5 REQUIREMENTS VALIDATION
The computers must be equipped with web browsers such as Internet explorer.
The system shall be built using a standard web page development tool that conforms to either IBM’s CUA standards or Microsoft’s GUI standards.
Response time for loading the photos should take no longer than five minutes.
A general knowledge of basic computer skills is required to use the system.
All coding will be done in standard C#.
The Id no field should contain only 11 digits.
The Date format should be MM-DD-YYYY.
From date and to date must be past date.
To date must be greater than from date.
All forms id number must be 10 digits.
Email Id must have “.” And “@” symbol.
Website Name must be Start with “www.”.
Phone number must contain numeric value.
Mobile number must be verified
Mobile number must contain (+) before phone number
There are no memory requirements
3.6 FUNCTIONS OF SYSTEM
3.6.1 Use Case
3.7 DATA MODELING
3.7.1 ¬¬¬¬E-R Diagram
3.7.2 Class Diagram
3.7.3 System Activity or Interaction Diagram
3.7.3.1 Login
3.7.3.2 Admin
3.7.3.3 Inspector
3.7.4 Data Dictionary
1) Table: Inspector
Column Type Null Key Extra
InspectorId int(11) No PRI Auto_increment
InspectorName varchar(30) No
Gender varchar(10) No
Contact varchar(10) No
EmailAdd varchar(30) No
Uname varchar(20) No
Pwd varchar(20) No
DOJ Datetime No
IsActive varchar(1) No
2) Table: Company
Column Type Null Key Extra
CompanyId int(11) No PRI Auto_increment
CompanyName varchar(30) No
Address1 varchar(100) No
City varchar(15) No
Contact varchar(10) No
EmailAdd varchar(30) No
3) Table: ContactPerson
Column Type Null Key Extra
CntPersonId int(11) No PRI Auto increment
CntPersonName varchar(30) No
ComapnyId int(11) No RFS
Email varchar(30) No
Contact varchar(10) No
Dept varchar(20) No
Uname varchar(20) No
Pwd varchar(20) No
IsActive varchar(1) No
4) Table: ContractCategory
Column Type Null Key Extra
CategoryId int(11) No PRI Auto_increment
CategoryName varchar(30) No
CategoryDesc varchar(150) No
IsActive varchar(1) No
5) Table: Contract
Column Type Null Key Extra
ContractId int(11) No PRI Auto_increment
ContractName varchar(30) No
CompanyId int(11) No RFS
CategoryId int(11) No RFS
InspectorId int(11) No RFS
ContractType varchar(30) No
Location varchar(20) No
ContractDesc varchar(150) No
EntryDate Datetime No
StartDate Datetime No
TargetFinishDate Datetime No
ContractStatus varchar(10) No
ContractAmt decimal(15,2) No
IsActive varchar(1) No
6) Table: Inspection
Column Type Null Key Extra
inspctId int(11) No PRI Auto_increment
inspectorId int(11) No RFS
ContractId int(11) No RFS
inspectDate Datetime No
NextFollowDate Datetime No
inspectNote varchar(150) No
img1 varchar(150) No
img2 varchar(150) No
img3 varchar(150) No
IsActive varchar(1) No
7) Table: Query
Column Type Null Key Extra
Qno int(11) No PRI Auto_increment
Qdate Datetime No
CntPersonId int(11) No RFS
Question varchar(150) No
Anwser varchar(200) No
IsActive varchar(1) No
8) Table: Feedback
Column Type Null Key Extra
FbNo int(11) No PRI Auto_increment
FbDate Datetime No
FbDescription varchar(100) No
PersonName varchar(20) No
ContactNo varchar(150) No
Email varchar(30) No
IsActive varchar(1) No
3.8 CONTROL FLOW DIAGRAM
3.9 MAIN MODULES OF NEW SYSTEM
• Tendering
• Inspection
• Admin
• Report Generation
• Graph Representation
4. SYSTEM DESIGN
DATA STRUCTURE DESIGN
4.1.1 Table and relationship:
INPUT/OUTPUT AND INTERFACE DESIGN
Control and Security
Service Admin Inspector Contact Person
Handle Company Details Y N N
Handle Inspector Details Y N N
Manage Category Details Y Y N
Manage Contract Details Y Y N
Add/Remove Contract Y Y N
Inspection Details Handling Y Y N
Site Visiting Y Y Y
Upload Images And Details N Y N
Handling Feedback Y Y N
Response To Queries Y N N
Add/Remove Inspector Y N N
Add/Remove Company Y N N
View Inspection Details Y Y Y
Sequence Diagram
Login
Admin
Inspector