Synopsis 2

1

USABILITYRQUIREMENTS IN E-TENDERING

ABSTRACT

Electronic Tendering is carrying out the traditional tendering process in an electronic form, using the internet. The tendering process is a key business process that helps businesses find a suitable contractor.

In the building and construction industries, clients invite tenderers to submit an estimate of prices, detailing the costs associated with completing a building. In this way, the client can base their decision on the result of the tenders to select the most suitable contractor.

Currently, many of such tendering processes are still mainly manual and paper based. The tenderers need to collect the tender's booklet, price it, and bring it back to the client's office before the deadline.

Usability is the ease of use and learnability of a human-made object and includes methods of measuring usability such as need analysis.A tendering system can have adequate functionality, but inadequate usability because it is too diificult to use.Usability requirements is too guard against that.

We present a design and implementation of an e-tendering system by using Web services for the automation of such tendering processes.This helps the stakeholder to make use of this system in a proper manner.

INFORMATION TECHNOLOGY

2


1.0 INTRODUCTION

Electronic Tendering system is a web-based application which helps customer & Tender Potentials members to convert their manual process in. Automation or automatic control is the use of various control systems for operating various applications with minimal or reduced human intervention. Paper base tendering consist a lot of work which is done manually and it is time consuming. Thus the E-Tendering Automation system is invented to reduce the efforts and time.

Tendering Application is converted into automation thus it require less human effort and it automated hence it is not time consuming. It consists of modules like Login system for customer & sheckholderst for managing process electronically in convenient manner, Tender opening & closing for the Competitors is online to reduce efforts as well as time.

Present E-Tendering Application consist more problems which are resolved in new System i.e. E-Tendering automation. Mainly E-Tendering automation system is web-based automation which has the following purposes:

1. Reduce the Manual work.2. Ease of use.3. Ease of keeping track.4. Reduce time away from regular customer and competitors activities.5. Improve the process of Tendering onto the automated System.6. Improve security administrative systems.7. Record all information for official operations on a central database.


3


1.1 Aim

Our aim is To develop application for tendering process that will benefit (Stakeholders)in less amount

Our aim is to develop a web-based application which helps Customers and Stakeholders to convert their manual process in automation. It consists of modules like all Tendering process which can be operated on the web from anywhere, anytime.

Tendering and ascertain the barriers and enablers from both a technological and end-user perspective

It efficiently keeps the track of useful information of the customers and stakeholders maintains their records in database, which can be retrieved anytime to refer the past history. It automates the management system and eliminates the paper work to a great extent. It also lessens the manual work and helps to perform complex task with ease.

1.2 Objectives:

Our objectives are:

1. Save effective time by automationPresent Institute application is mainly performed by employees and the work is very conflicting. Thus by the automation, time and physical strain is reduced.

2. Improve processing timeBy automating manual work, the operations are performed electronically. Hence less processing time is taken for performing the complex operations.

3. To Eliminate paper workThe present application is based on a lot of paper work which are eliminated.

4. Ease of keeping trackAll work is done electronically and is automated; it is easy to keep the track of every operations and information regarding users

5.Computerize The Manually Operated System


4


2.Literature survey. Four decades of international construction industry reports reinforce poor communication, information transmission; coordination; and teamwork issues are the cause of countless performance problems in the construction industry. Failure to achieve significant improvements in what are well-identified issues can be linked to the hitherto limited capacity to conceptualize and manage the very complex dynamics in project processes throughout the project’s life cycle.

Debatably, today’s industries, businesses and personal worlds are dominated by a wide range of technologies and e-activities, including: computers, email, Internet, Web sites, etc., finding it more and more difficult to function without them. Yet, the success of any profession is described as going beyond simply exchanging electronic information. Successful implementation of information and communication technology (ICT) and innovative web-based e-solutions (such as e-Tender) requires careful consideration to meet industry needs. Where future research and developments (R&D) in determining new and improved ways of doing business through the Internet is dependent on the innovation of the industry (and end user), not only the technology itself – that is, matching technological innovation with the perceived needs and preparedness for change on the part of the industry.

Consequently, there is an urgent need to address those key issues that will most significantly influence the construction industry and the way in which it contributes to our society and the economy as a whole in the future. By focusing on the potential of ICT and innovative web-based e-solutions, to better integrate project team members and the construction industry in general.


5


3.Existing system

• Troubleshooting

• Subscriptions to the site

• Email notifications

• Collection or downloading of tender documents

• Electronic lodging of tender response

The SA Tenders & Contracts website went live on 19 April 2003, intending to provide a series of future training sessions and workshops (SA Government 2003).

4.1Tender link - Australasia


6


Tender link claims to be Australasia's first ful y automated electronic tendering system (established in 1994), providing its users a strictly business-to-business (B2B) and business-to-government B2G) service (Figure 4-14). With offices in Australia and New Zealand, the Tender link service is independent and neutral, aiming to facilitate the procurement and supply of services, consultancy, and products regarding prices, quotes, tenders and information.

Organizations wishing to engage in tender transactions via TenderLink have to be registered (Tenderlink 2002).

Tenderlink acknowledges the fact that a number of local and regional councils and government departments make use of various other online tender services, stating these

systems are generally limited to published information about their own current tenders. What makes Tenderlink unique in this case is that it is a ‘commercial system’, providing both purchasers and suppliers fully automated functionality and greater access to a complete range of tenders (both in a local and international market) via its own built in communications centre. Tenderlink provides its registered members a secure and fully encrypted transaction environment with a full audit trail, password-protected entry, a secure payment gateway, and 128-bit security (believed to be one of the strongest levels of security available and generally accepted by the banking fraternity throughout the world). Figure 4-15 provides a graphical representation of the Tenderlink process.


7


1. PROBLEM STATEMENT AND SCOPE

5.1 Context:

Institute Automation is a web-based application which helps staff members and students to convert their manual process in automation.

5.2 Problem:

In present time, all the office work is done manually which includes registration ,tender entry, opening & closing tender & tender submissions etc.This requires a lot of manual paperwork, which is also very time consuming.Require lots of Man power. Problems are:

1. Physical Strain 2. Less Interactive 3. Time Consuming

5.3 Solution:

Institute Automation to convert all manual and paper work into an automated system which will lessen the burden of customer and stakeholders by saving on the effective time

5.4 Problem Issues

Network Issues:

• requirements for adequate network bandwidth

• any likely/actual bottlenecks in accessing data during peak loads?

• critical need for reliability of system

• robust – any network problems at tender submission time?

• audit trails - tracking source of any problem (theirs or ours?)


8


People Issues: • develop trust in security

• develop confidence in use

• minimize user interface issues

• provide access to appropriate help – online, 24 x 7 assistance?

Security Issues: • acknowledgement of receipt of communications

• authenticity concerning the source of the communication - does it come from the apparent author?

• integrity - whether or not the communication received is the same as that sent - has it been altered either in transmission or in storage?

• confidentiality - controlling the disclosure of and access to the information contained in the communication.

Access Issues: • Ease of access for users

• clarity of user interface

• networking constraints


9


Scope of the system

Inclusion:

1.Use web base application

2.Use asp.net technology & sql to develop the system

3.UseRSA algorithm for security purpose

4.Usemaster forms technology that is extend to existing tendering system

Exclusion:

1.Reduce the paper work &manual work

2.Reduce only module for system in E-Tendering

3.Reduce customer & stakeholder manual work


10


The price of the product on auction increases with every incremental bid.

The price increases as per the minimum bid increment set by the seller. The seller

must sell the item to the highest bidder at the close of the auction. For example, if a

seller has put up product 'A' for sale with a reserve price of Rs.10 and five buyers

bid for it with the highest bid coming in from buyer 'B' who bids Rs.12, the

product is sold to 'B' for Rs.12. This is an auction where the number of units of a

particular product for sale is more than one. This simply means that a number of

identical products have been put up for sale by the seller. In an auction like this,

there will obviously be more than one winner. Buyers can also bid for more that

one unit of that product. At the end of the auction all the bidders pay the same

price - the lowest winning bid amount (subject to the reserve price being met) for

the product. This is a perfect auction type for those who wish to sell many units of

the same product. Here is how it works: The Seller starts by listing a minimum

price or starting bid for a product and the quantity or number of units for sale.

Bidders specify both a bid price and the quantity they wish to buy. All winning

bidders pay the same price per item - the lowest successful bid. If there are more

buyers than items, the earliest successful bids get the goods. Higher bidders are

more likely to get the quantity they asked for. Bidders can refuse partial quantity.

For example, if you place a bid for 10 items and only 8 are available after the

auction, you are not obliged or bound to buy any of them. Example Case: A seller

places 10 pens on auction at Re.1 each. 10 people bid Re. 1 for one pen each. In

this case, all 10 bidders will win a pen for Rs. 1. However if, let's say, five people

bid Rs. 1.25 for a pen each and 10 others bid Re. 1. The minimum bid for the pen

will be raised to Rs. 1.25 because demand exceeds supply. Because the Rs. 1.25

bidders bid higher than the Re. 1 bidders, they will be guaranteed a pen. The other

5 pens will go to the earliest Re. 1 bidders. The final price for each pen will be Re.

1 (even though some participants placed a higher bid of Rs. 1.25) since all winning

bidders pay the same price - which is the lowest successful bid. In this format at

the time of allocation of the quantities the preference is given to the buyer who

puts in the highest bid and he/she will get the quantity he bid for and this flows

progressively down the bidding value stream.


11


1. Proposed System

Potential Tenders


12


Principal Potential Tenders

Potential Tenders

Fig 6.1.1Architecture of the system

This system architecture mainly contains three parts client i.e. 3potential tenders & principal. In this architecture the principal advertise for tender & then potential tenders registration for tender after that the principal pass the quotations value to the potential tender after that the potential tender fill there quotations & pass to principal after that the principal choose thequotations of the potential tender & give the tender to best one of best potential tenders

6.2 Flow Chart

Start Point

Login


Enter Username and Password

13


Incorrect

Correct

Logout

Finish Point

login()

validate()


Login Successfully

Accepted

Logout Successfully

Admin Login page Bl:Cl.Login DAL Database

14


ExecuteQry()

Cmd execute()

Return response()Return response()

1.Admin Login 2.Validate user

6.Response for validate user

5.return Qry result

3.execute non Qry


Admin Login Bl:Cl Login

15


4.executecmd

Methodology


DAL Database

16


SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.

The steps for Spiral Model can be generalized as follows:

The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users


17


representing all the external or internal users and other aspects of the existing system.

A preliminary design is created for the new system.

A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.

The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

The final system is constructed, based on the refined prototype.

The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.


18


AnalysisAfter analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution


19


In the flexibility of the uses the interface has been developed a graphics concept in

mind, associated through a browser interface. The GUI’S at the top level have been

categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information

that is practically, part of the organizational activities and which needs proper

authentication for the data collection. The interfaces help the administrations with

all the transactional states like Data insertion, Data deletion and Data updating

along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in

transactions through the existing data and required services. The operational user

interface also helps the ordinary users in managing their own information helps the

ordinary users in managing their own information in a customized manner as per

the assisted flexibilities

Modules

The project is mainly divided into 4 modules:

1). Administrator

This administrator will maintain all the master information like Items Information,

suppliers’ information, Employee information.

2).Employee

He is going to prepare the indent for the required product to the purchase

department, and also he checks indent status.


20


3). Purchase Department

Displaying indent information from different departments. Preparation of tenders

for the indents, Invitation to the supplier for the tender

4). Supplier

Supplier is going to bid the amount for tender with in the stipulated time, and will know the final status of the tender once it is closed.

Details of Hardware and Software

Hardware Requirements:

PIV 2.8 GHz Processor and Above

RAM 512MB and Above

HDD 40 GB Hard Disk Space and Above

Software Requirements:

WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

Visual Studio .Net 2005 Enterprise Edition

Internet Information Server 7.0 (IIS)


21


Visual Studio .Net Framework (Minimal for Deployment) version 2.0

SQL Server 2005 Enterprise Edition

The software, Site Explorer is designed for management of web sites from

a remote location.

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general

insight into the analysis and requirements of the existing system or situation and

for determining the operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC) and

it describes the complete requirement of the system. It is meant for use by the

developers and will be the basic during testing phase. Any changes made to the

requirements in the future will have to go through formal change approval process.

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

Developing the system, which meets the SRS and solving all the requirements

of the system?

Demonstrating the system and installing the system at client's location after the

acceptance testing is successful.

Submitting the required user manual describing the system interfaces to work

on it and also the documents of the system.

Conducting any user training that might be needed for using the system.

Maintaining the system for a period of one year after installation.

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the

results of processing to users. They are also used to provides a permanent copy of

the results for later consultation. The various types of outputs in general are:


22


External Outputs, whose destination is outside the organization.

Internal Outputs whose destination is within organization and they are the

User’s main interface with the computer.

Operational outputs whose use is purely within the computer department.

Interface outputs, which involve the user in communicating directly.

OUTPUT DEFINITION

The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer.

It should be decided as which form of the output is the most suitable.

For Example

Will decimal points need to be inserted

Should leading zeros be suppressed.

Output Media:

In the next stage it is to be decided that which medium is the most

appropriate for the output. The main considerations when deciding about the

output media are:

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.


23


The location of the users

The software and hardware available.

Keeping in view the above description the project is to have outputs mainly

coming under the category of internal outputs. The main outputs desired according

to the requirement specification are:

The outputs were needed to be generated as a hot copy and as well as queries to be

viewed on the screen. Keeping in view these outputs, the format for the output is

taken from the outputs, which are currently being obtained after manual

processing. The standard printer is to be used as output media for hard copies.

INPUT DESIGN

Input design is a part of overall system design. The main objective during

the input design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

INPUT STAGES:

The main input stages can be listed as below:

Data recording

Data transcription

Data conversion

Data verification

Data control

Data transmission

Data validation

Data correction

INPUT TYPES:


24


It is necessary to determine the various types of inputs. Inputs can be categorized

as follows:

External inputs, which are prime inputs for the system.

Internal inputs, which are user communications with the system.

Operational, which are computer department’s communications to the system?

INPUT MEDIA:

At this stage choice has to be made about the input media. To conclude

about the input media consideration has to be given to;

Type of input

Flexibility of format

Speed

Accuracy

Verification methods

Rejection rates

Ease of correction

Storage and handling requirements

Security

Easy to use

Portability

Keeping in view the above description of the input types and input media, it

can be said that most of the inputs are of the form of internal and interactive. As

Input data is to be the directly keyed in by the user, the keyboard can be considered

to be the most suitable input device.

ERROR AVOIDANCE

At this stage care is to be taken to ensure that input data remains accurate

form the stage at which it is recorded up to the stage in which the data is accepted


25


by the system. This can be achieved only by means of careful control each time

the data is handled.

ERROR DETECTION

Even though every effort is make to avoid the occurrence of errors, still a

small proportion of errors is always likely to occur, these types of errors can be

discovered by using validations to check the input data.

DATA VALIDATION

Procedures are designed to detect errors in data at a lower level of detail.

Data validations have been included in the system in almost every area where there

is a possibility for the user to commit errors. The system will not accept invalid

data. Whenever an invalid data is keyed in, the system immediately prompts the

user and the user has to again key in the data and the system will accept the data

only if the data is correct. Validations have been included where necessary.

The system is designed to be a user friendly one. In other words the system

has been designed to communicate effectively with the user. The system has been

designed with popup menus.

USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while

designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

1. User initiated interface the user is in charge, controlling the progress of the

user/computer dialogue. In the computer-initiated interface, the computer

selects the next stage in the interaction.

2. Computer initiated interfaces


26


In the computer initiated interfaces the computer guides the progress of the

user/computer dialogue. Information is displayed and the user response of the

computer takes action or displays further information.

Performance Requirement

Right from the start the system is going to be menu driven, the opening

menu displays the available options. Choosing one option gives another popup

menu with more options. In this way every option leads the users to data entry

form where the user can key in the data.

ERROR MESSAGE DESIGN:

The design of error messages is an important part of the user interface

design. As user is bound to commit some errors or other while designing a system

the system should be designed to be helpful by providing the user with information

regarding the error he/she has committed.

This application must be able to produce output at different modules for different inputs.

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a

system. Only when the requirement specifications are properly given, it is possible

to design a system, which will fit into required environment. It rests largely in the

part of the users of the existing system to give the requirement specifications

because they are the people who finally use the system. This is because the

requirements have to be known during the initial stages so that the system can be

designed according to those requirements. It is very difficult to change the system

once it has been designed and on the other hand designing a system, which does

not cater to the requirements of the user, is of

Design Details


27


6.2 NORMALIZATION

It is a process of converting a relation to a standard form. The process is

used to handle the problems that can arise due to data redundancy i.e. repetition of

data in the database, maintain data integrity as well as handling problems that can

arise due to insertion, updating, deletion anomalies.

Decomposing is the process of splitting relations into multiple relations to

eliminate anomalies and maintain anomalies and maintain data integrity. To do

this we use normal forms or rules for structuring relation.

Insertion anomaly: Inability to add data to the database due to absence of other data.

Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial update

Normal Forms: These are the rules for structuring relations that eliminate anomalies.

FIRST NORMAL FORM:

A relation is said to be in first normal form if the values in the relation are

atomic for every attribute in the relation. By this we mean simply that no attribute

value can be a set of values or, as it is sometimes expressed, a repeating group.

SECOND NORMAL FORM:

A relation is said to be in second Normal form is it is in first normal form

and it should satisfy any one of the following rules.

1) Primary key is a not a composite primary key

2) No non key attributes are present

3) Every non key attribute is fully functionally dependent on full set of primary

key.


28


THIRD NORMAL FORM:

A relation is said to be in third normal form if their exits no transitive

dependencies.

Transitive Dependency: If two non key attributes depend on each other as well as

on the primary key then they are said to be transitively dependent.

The above normalization principles were applied to decompose the data in

multiple tables thereby making the data to be maintained in a consistent state.

Data Flow Diagram

DFD Level 1

Yes Yes


Open Login FormEnter username & pwd

Home user page

29


DFD level 2

Yes Yes Yes

No

DATA FLOW

1) A Data Flow has only one direction of flow between symbols. It may flow in

both directions between a process and a data store to show a read before an

update. The later is usually indicated however by two separate arrows since

these happen at different type.

2) A join in DFD means that exactly the same data comes from any of two or

more different processes data store or sink to a common location.


Open Login FormEnter username & pwd

Home user pageUser check

Verify data

Login master

30


3) A data flow cannot go directly back to the same process it leads. There must

be at least one other process that handles the data flow produce some other data

flow returns the original data into the beginning process.

4) A Data flow to a data store means update (delete or change).

5) A data Flow from a data store means retrieve or use.

A data flow has a noun phrase label more than one data flow noun phrase can

appear on a single arrow as long as all of the flows on the same arrow move

together as one package.

11. Implementation Plan

11.1 Gantt Chart


31


11.2 Time-line :

Activity Description Effort in person weeks

Deliverable


32


Phase 1P1-01 Requirement Analysis 2 weeks Requirement Gathering

P1-02 Existing System Study & Literature

3 weeks Existing System Study & Literature

P1-03 Technology Selection 2 weeks >NET

P1-04 Modular Specifications 2 weeks Module Description

P1-05 Design & Modeling 4 weeks Analysis Report

Total 13 weeks

Activity Description Effort in person weeks

Deliverable

Phase 2P2-01 Detailed Design 2 weeks LLD / DLD Document

P2-02 UI and user interactions design

Included in above

UI document

P2-03 Coding & Implementation 12 weeks Code Release

P2-04 Testing & Bug fixing 2 weeks Test Report

P2-05 Performance Evaluation 4 weeks Analysis Report

P2-06 Release Included in above

System Release

Total 20 weeks Deployment efforts are extra

REFRENCES


33



34



Date post:	20-May-2017
Category:	Documents
Upload:	aepatil74
View:	213 times
Download:	1 times

Synopsis 2

Documents