Market Trends Require Transaction Of Products

Published Date: 02 Nov 2017

The current market trends require transaction of products every now and then. Majority of the organizations have business demands for which they have to hire persons, train them and implement the system. Instead of this time taking process, most of the corporate are now inclining towards online E-Procurement systems for cost-effective solutions. It allows organizations to save time and money as well as expand their area of work building corporate relations from local to global scale.

The term e-procurement is basically used to address procurement activities supported by the use of computers and the internet communication facilities. E-procurement is more than just a system for making purchase online. E-procurement system should also connect organizations and their business processes with suppliers while managing all interaction between them. This includes management of correspondence, bids, organisations participating in procurer related activities and actual process of procurement.

From the prospective of development, the huge steps of planning such a system providing a fully interactive and communicative interface would provide a great experience to the developer. The gradual steps of analyzing, designing and implementing a system with diverse functionalities using latest technologies and concepts would provide an opportunity to the developer to have hands-on experience on the corporate level. The project would enrich the developer with both domain knowledge of the concept of E-Procurement and enterprise resource planning, the tools used to develop the system and various software development and project management methodologies.

1.1.2 Topic of the System

The project provides insight into building an effective and efficient online procurement platform for software consultancy services. It will help in carrying out the procurement related activities with the help of internet and would assist the users with added functionalities. This project will provide a common platform for software consultancy services to the organizations (procurers and coders), while facilitating all the interaction between them.

Fig 1.1 General Structure of the System [1] 

E-Procurement project includes management of correspondence, bids, procurer related activities, and supplier related activities and other supporting activities. This project can be used by two types of users: procurer organizations and coder organizations. Procurer organizations may use this online platform in finding out best consultant organisation, which can develop a software project/product for them in affordable cost. Coder organisations may use this platform for providing needed services by the procurer organisations.

1.1.3 Purpose of Implementation

The current demand of products in IT sector is overwhelming and organisations need to use resources and experts every now and then in variety of IT fields. The same organisation may need to develop a system of purely software implementation or multimedia based or a total networking based system. Similarly a single organisation may not have expertise in all the domains and would need a third party support for work. The process of E-Procurement provides an ultimate solution acting as an interactive interface between the organisations. The industries need not hire new employees or train existing employees for the specific work domain. This reduces sufficient amount of time and money which are the two most valuable assets in corporate world.

1.1.4 Target Audience

The project can be used by two types of users: procurer organizations and coder organizations. Procurer organizations may use this online platform in finding out best consultant organisation, which can develop a software project/product for them in affordable cost. Coder organisations may use this platform for providing needed services by the procurer organizations. Apart from organisations, group of developers may also use the system to provide services in return of profit.

1.1.5 Problem Context

Today there is no good and vast on line procurement platform for software consultancy services.

The native method generally involves a lot of paperwork, consumes time and has geographical limitations.

The products developed are not reusable. Thus there is requirement for availability for reusable products, as permitted.

No proper and frequent communication. Hence there is a requirement of communication modules (messaging, SMS).

1.1.6 Rationale behind the System

There are presently some of the E-Procurement systems deployed over the web but none of them provide all facilities and functionalities required. Some of them don’t have a required level of user interface and interactivity. Many of them are missing proper communication facilities among the organisations. For example a system over the web has finalized a deal between two organisations and then just provides their addresses to each other and closes the deal. Hence an efficient E-Procurement solution is needed with good communication facilities, good user interface with customizable organization profiles and themes.

1.1.7 Tangible Benefits

Saving of resources as most of the paperwork is reduced, right from publishing of tenders to the final deal. It even saves man – power as there is heavy involvement of people with documents who carry out deal in geographically separated areas.

The system aids in decision-making process, like it aids in opting the best consultant among the numerous listing of consultants by arranging all information tidily organized and time stamped.

The forums would assist in discussion of solutions related to problems that the users may face or have faced earlier. It may help in discussing new ideas or projects.

The chatting facility would help both the procurers and coders to clear all their doubts and ambiguous assumptions.

1.1.8 Intangible Benefits

The people involved in E-Procurement/Bidding process would be in comfort zone as all the process is automated. This will save their time

The users would be aware of latest technologies and current demand of type of projects in the market.

1.1.9 Goal of System Development

1.1.9.1. Project Goal

The overall goal of the project is to create a better business environment by analyzing, designing and implementing a full-fledged web based E-Procurement ERP for Software Consultancy Services. The chief functionality of the system is to provide an online platform among organisations to participate in E-Procurement process with efficient communication facilities. The system will also send notifications and alerts related to updates through e-mails and SMS alerts.

1.1.9.2 Academic Goal

The main academic goal of the project is to acquire new skills, intellect, knowledge and practical experience in developing an enterprise level project.

The next academic goal is to manage the project within the specified time-frame and budget to fulfil the said objectives and produce the required deliverables of the system. Careful documentation of the system is required along with development of the system.

Learning industry standards to implement technologies, programming languages, database administration is of primary significance.

1.1.10 Objectives of System Development

1.1.10.1 Project Objectives

Provide Common Platform: A fair and competitive platform for organizations to enable purchase and supply.

Demand Aggregation: The capacity to aggregate different departments of single or different organizations to enhance supply and demand of market.

Minimize Resource Costs: Improved planning and management to reduce the cost of resources traditionally required.

Consistent vendor development: Facilitate pre-qualified vendors the opportunity to access of other departments/organizations.

Effective Bid Processing: Effective use of bids to get better deals.

Increase Transparency: Monitor and control of procurement processes.

1.1.10.2 Academic Objectives

The developer needs to follow IT principles and standards in developing the system. Principles of Human Computer Interaction and Usability and interface design techniques needs to be taken care of. The developer will learn software development and project management skills with high level programming techniques in .NET, AJAX and other technological concepts.

1.1.11 Success Criteria

The success of the project will be determined the final documentation and final system prototype, judged by the in-depth understanding of the concepts and technologies. The detail of the documentation and quality of design and final system would be tested to check for the success of the project.

1.1.12 Scope and Functionalities of the Project

The proposed system is designed to meet the E-Procurement requirements of organisations and assist in the whole process with an interactive user interface, through various functionalities. The functionalities of the project are listed out as follows:

1.1.12.1 Functionalities of the Project

1.1.12.1.1 Core Functionalities

Creation of requirement specification by procurer organization and invitation to other organizations for bidding.

Bidding process by consultant/coder organizations.

Bid assessment by for procurers and choice of the best bid.

Communication among the parties.

Contract agreement for procurer and consultant organization.

Verification and delivery.

1.1.12.1.2 Enhanced Functionalities

Provide communication facilities: - Messaging

User Account/Profile management/Themes

Automatic notification facility.

Rating facilities.

1.1.12.1.3 Special Functionalities

Ajax technology for quick access and smart validations.

Basic chatting between organizations.

SMS Alerts.

1.1.12.2 Evidence for Limiting the Project Scope

The current system can incorporate more web functionalities in it but it is wise to limit the project scope as should be completed within the specified time with mentioned functionality and cost. The customization of mobile settings, SMS alerts and some third party content will not be discussed, but would be required in deployment of the application. Although most of the modules developed will be flexible but still some of the modules will not customizable.

1.1.13 Major Deliverables of the Project

Project Proposal Form

Project Specification Form

Research documents and other resources

E-Procurement Web Application

Complete Documentation

User Manual

Final Presentation

1.2 Project Planning

1.2.1 Project Management

A proper project management plan will assist the developer to in chalking out the actual plan to be carried out in the development of the system. The developer has to check for the complete functionality of the system completed within the specified time-frame with the gradual step wise analysis, execution, monitoring and controlling of the project. The developer has to develop various prototypes of the system gradually checking them thorough the development phases until the final prototype.

1.2.2 Scope Management

The scope of the proposed system is to offer an online platform through which users can perform and deal with all procurement associated activities for procuring software consultancy services from the best consultant. The system is web based, so that it works like a tool that automates all procurement process and reduces the procurement cycle.

1.2.3 Time Management

The dates of individual modules completion has been carefully planned according to the specified time-frame. The deadlines for each of the modules have been arranged in sequence to create a GANNT chart that would take care of the time management.

1.2.3.1 GANNT Chart

The efficient management of time slots has been arranged in the GANNT chart. Tool used to develop is Microsoft Project 2007. This chart will check all the modules of the project and the project as a whole. It provides a monitoring tool to monitor the status of tasks to be completed.

1.2.3.2 Key Milestones and Deliverables

Requirement Analysis : 3 weeks

Planning and Research: 4 weeks

System Design: 3 weeks

Prototype: 3 weeks

Review and Prototypes: 14 weeks

Testing: 3 weeks

Final Implementation: 2 weeks

1.2.4 Quality Management

The quality of the system is one of the major point which determines whether success of the system. The quality of a system can be checked through testing its parts and process. The developer has chosen a number of tests to perform upon the system to check the quality of the system and to enhance it. The test plan devised is shown as follows.

1.2.4.1 Test Plan

Testing is one of the most essential phases of system development. Testing reports the major loopholes in the system and helps eradicate error and bugs thus leading to development of a robust and efficient system. There are various testing techniques available to judge a system. The techniques that the developer has decided to follow are described as below.

Unit Testing and White box Testing

The first and foremost testing that the developer would be using is unit testing and white box testing. The whole system will divided into units even the existing prototypes. Each and every unit would be subjected to testing individually. This would ensure that each unit (such as login, register etc.) live up to the expectations of its specification. Lack of functionality and logical inconsistency could be checked at a minute level. White box testing would be performed as soon as the code is written for the prototype. A thorough analysis of the code would be performed.

Black box Testing

The next testing to be performed would be black box testing. The probable inputs and the expected outputs would be tested in all the sections to check for errors and functionality. All the inputs and outputs would be critically evaluated for accuracy and correctness.

Integration Testing

The next type of testing would be integration testing. The units which were tested in unit testing phases would be checked for their operational consistency among other units. The units such as messaging module and bidding modules would be checked for integration. The integration of these units and their proper functioning would be checked during the integration testing phase.

System Testing

The next type of testing would be system testing. After integration testing all the modules would be combined to form a complete system. The complete system would then be checked for errors and functionalities.

Regression Testing

The particular modules which resulted in error would be tested again and again to identify the exact source of error. They would then be corrected and checked as needed by regression testing.

Estimated Size of the Database

Estimated size of the test database would be around 100 MB as for now.

1.2.5 Risk Management

Each and every project has a certain number of risks involved in it. The developer has made sure to minimize the number of risk, but nevertheless there is always some or the other risk involved in development of a project. The creation of risk plan will help to reduce the risks that may be faced during the development phase, whether the impact of the risk maybe huge or negligible. A risk management plan is thus needed to be in the safe side.

1.2.5.1 Methods followed to identify risks

Risks associated to a project are very common to point out while some of them maybe hidden risks. The earlier projects completed by the developer can help to identify risks i.e. projects of similar nature with risks involved in timing or technological errors. The previous records may also help in identifying risks involved in the project. Thinking for possible risk cases by the developer may lead to one or more instances where risk is involved and proper measure can therefore be taken, to avoid the risk.

1.2.5.2 Identified Risk and Response Plan

Risk 1: All the promised functionalities not reaches

Probability : 30%

Impact: Marginal

Measure: The system scope is to be reduced.

Risk 2: Data gathering methods did no deliver necessary information

Probability: 50%

Impact: Marginal

Measure: Properly designed questionnaires and interview with a pre-defined set of targeted users for survey.

Risk 3: Schedule not feasible

Probability: 40%

Impact: Critical

Measure: Check for important tasks and reschedule some of the modules to balance the schedule.

Risk 4: Technology problem

Probability: 40%

Impact: Critical

Measure: Update knowledge with online sources, video tutorials, books and other resources

Risk 5: Project failure due to hard disk crash or storage media failure

Probability: 50%

Impact: Disastrous

Measure: Follow Back-Up policies

1.2.6 Ethics Commitment

The project encourages end user participation in various phases of its development. The survey of questionnaires, interviews and feedback about the prototypes would require to users to be actively involved with the project. Hence the developer is required to provide an ethics commitment by filling in the Fast –Track Ethics approval form in order to safeguard the opinions and interests of the users and have full academic support.

2. Problem Description

2.1 Introduction to Problem Area

The primary research revealed many areas of problem where the proposed system can be implemented. Today there is no good and vast on line procurement platform for software consultancy services. The native method generally involves a lot of paperwork, consumes time and has geographical limitations. The aim of project is to implement online e-procurement application in a way that this application will pass the geographical boundaries, be more reusable, maintainable and user interactive.

2.2 Why the problem should be studied

The developer has found out the major problems as highlighted earlier. The main problem is to effectively implement an e-procurement solution with all the features as mentioned earlier and its user acceptance. The second problem is a challenge to learn the new technologies to analyze, design the system and efficiently implement it with integration of various diverse modules.

2.2.1 Importance of Identified Problem

The developer has identified the major problem areas which has their own importance. The developer needs to bridge in the gap among the organizations facing the problems of efficient procurement. The online platform would assist the user with advanced features of profile management and maintenance of good relation among the organizations. The communication and alerts system is required as a reminder to them so that the users stick o their schedule.

2.2.2 Availability and Feasibility of Technology

The development technology primarily uses .NET platform to build the application. The features of cellular technology like SMS is quite feasible as nearly all the people posses cell phones. The system would basically use internet resources and e-mails which again nearly all the people use in daily life. The expense would be of domain and hosting packages for deployment of the web application which is quite feasible and nominal.

2.2.3 Challenges and Learning Opportunities

2.2.3.1 Nature of the Challenge

The nature of challenge is of computing domain, the solutions of which present everywhere now-a-days. The developer has decided to develop a web based solution to the problems mentioned. This includes an online procurement platform with communications and notification facilities. The challenges faced in the system are discussed as follows:

2.2.3.2 General and Computing Challenges

There are numerous challenges to be faced while developing the system. Some of the computing problem faced would be the learning of newer concepts and technologies, finding and devising effective algorithms to achieve accurate results. The research related to the domain concepts would provide valuable knowledge and skills that would count in future development of applications.

2.2.3.3 Technology, Concept and Theories

Concepts of enterprise resource planning and web based applications are to be implemented using the chosen technology of .NET platform. The developer needs to integrate various modules as required taking the aforesaid concepts while implementing the system. The modules clubbed together have to be fully functional with each other.

2.2.3.4 Programming Skills

Advanced programming level concepts of C#.NET should be learnt and implemented in specified time frame of development. Newer technologies like AJAX must be dealt with special care to enhance usability of the system and increase performance level. The security of the system must also be taken care of by using CAPTCHA authentication and other possible techniques. Again integrating all the modules into one is itself a complicated and challenging process.

2.2.3.6 Other Challenges

The proposed system finally delivered should be cost-effective and feasible so as to determine its success. The customization of the system also needs special attention as the modules are inter-related. The system should check for account privileges and proper authentication. The system should be feasible enough for a normal user to use considering the fact that most advanced technologies have been used in development of the system.

3. Literature Review

The "literature" of a literature review points to any selection of materials on a topic, not essentially the great literary texts of the world. The literature review of the project provides brief information about the knowledge area of the subject being discussed. It basically focuses on the ideas and opinions on the summary collected from primary research and investigation. Literature review also signifies the research carried out in lieu of project development.

3.1 Domain Research

The domain of the proposed system deals the concept of ERP (Enterprise Resource Planning) and E-Procurement solutions. The elementary benefits of Enterprise Resource Planning systems do not in fact come from their inherent "planning" capabilities but rather from their abilities to process transactions efficiently and to provide controlled record keeping structures for such transactions. This kind of consciousness often comes as a surprise to academics and practitioners alike, having anticipated superior decision support intellect to be built into ERP modules.

ERPs are cross-functional and enterprise wide. All functional departments that are involved in operations or production are integrated in one system. For example, Mabert, Soni and Venkataramanan (2000) describe a "concept"-based definition of Enterprise Resource Planning as involving the "seamless integration of processes across functional areas with improved workflow, standardization of various business practices, improved order management, accurate accounting of inventory and better supply chain management". ERP "systems" on the other hand are merely the vehicles through which this is accomplished.

Apart from the research of ERP the research on the architecture of network is also of prime importance. The proposed system will run on 3-tier architecture. The 3-tier architecture consists of:

Presentation Layer

Business Logic Layer

Data Access Layer

Presentation layer deals with the user interface as the general user views it. The views of the users are customized and can be changed easily. However the change in presentation layer made does not affects the data in data access layer.

Business logic layer is the layer that deals with the business processes such as user authentication and other operations. The decision of the system depends upon the logic established here in business logic layer.

Data access layer is the fundamental layer where the actual data is stored. Any change made here is visibly instantaneously in the presentation layer. The entire database is located centrally in here.

3.2 Critical Evaluation of Literature Review

The literature review helps to continue research in the right directions and various sub topics that deal with the system. According to the domain research the developer has mainly carried out research related to the domains: ERP and E-Procurement and web deployment architecture. The concept of E-Procurement is implemented through the ERP backbone. The developer user a 3-tier architecture for implementing the web solution which is a better and secure measure.

Since the application domain of the system is the internet itself so huge number of peoples will participate as it is cost-effective, affordable and easily available. The communication methods will motivate the user to use the system at an optimum level. The SMS alerts are a great way to inform users about their updates. The current growth of internet and IT technologies promise a positive growth and profit as far as the proposed system is concerned. With this the developer is keen to continue the part of primary and secondary research, in order to chalk out the design prototype of the system to be implemented soon.

4. Research Methods

4.1 Primary Research

Primary research is crucial for the proper development and implementation of the project. The report of primary research will help in completing the user analysis about the project. The domain research, literature review provided a great benchmark for forming the opinion regarding the project.

The two important parts of data gathering methods are distribution of questionnaires and interviews. The developer distributed the developed questionnaire among peoples and interviewed some of the user as accordingly as the questions were prepared.

4.1.1 Questionnaires

Questionnaires are conducted as a part of primary research which is used to gather data from a large number of users in a short duration of time. This method is generally used to target the busy but important users of the proposed system. The questionnaires created are designed in a way so that it takes minimum time to be filled with maximum conceptual input from the users. They are made paper based rather than online to ensure positive participation and it’s more comfortable to fill in the survey manually for the user too. The goals of distributing questionnaires are:

To grasp a generalized opinion of a mass of users.

To check the limitations of the system.

To identify the problem areas.

To get feedback and suggestions.

The finally designed questionnaires which have been approved by the project supervisor, is shown below:

E – Procurement Questionnaire

Questionnaire ID: E-Proc/001/01

Name:

Signature:

Designation:

Date:

City:

Gender:

 Male  Female

Brief summary of the E – Procurement ERP

The project involves building an effective and efficient online procurement platform for software consultancy services. This project includes management of correspondence, bids, procurer related activities, and supplier related activities and other supporting activities. This project has communication features such as messaging, chatting, forums and blogs. It provides individual profile for organizations along with profile management/themes. The project also has automatic notification facility with SMS alerts.

Have you come across an online E-Procurement Solution?

Yes

No

If yes, please mention ………………………………………………………………

How would you rate the present system of E-Procurement: www.getafreelancer.com?

Excellent

Good

Fair

Poor

Would you like to have an online E-Procurement solution?

Yes

No

How would you rate the inclusion of forums and blogs for discussion of projects and bids?

Extremely Necessary

Necessary

Optional

Not Required

How would you like to communicate with other organizations?

Through Messaging

Through Chatting

Through Forums and Blogs

Through Phone

Would this system benefit you in your day-to-day transactions?

Yes

No

How important is the interface design for you in this system?

Extremely Important

Important

Optional

Not Needed

How do you gather information about the procurer/coder organization, with whom you want to deal?

Through Websites

Through Phone

Through Visit

Through Trusted Links

Will this system save your time in regard to the current way of your business?

Yes

No

Would you like pre-built templates for publishing bids?

Yes

No

What problems/hindrances can be faced in this system?

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Please provide your valuable suggestions for the system being developed?

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Disclaimer: The information collected by this questionnaire will be used for development of the system "E – Procurement ERP for Software Consultancy Services". The information gathered will not be used illegally anywhere in any form. The users are assured that their data will be kept strictly confidential and will be used only for academic research purposes only.

Thank you very much for your precious time and valuable suggestions.

Date: ________________

Signature: ______________

(PS: The justification & analysis of the questionnaires is provided in Analysis section of documentation.)

4.1.2 Interview

The process of interviewing is a more detailed process of data gathering methods. This makes the problem domain clearer and defines the user requirements in detail. Face to face interaction also provides verbal and non-verbal feedback which is missing in questionnaires. The developer’s intention of carrying out an interview survey is to know the understanding of the users about the process of the proposed system. This would help to develop a more usable system with rich user interface and a required level of interactivity. The interview questions chosen are provided as below:

Interview Questions

In your opinion how would an E-Procurement system be useful for your organization?

How would forums and blogs be useful to the system?

How would the option of chatting be helpful in the system?

What information would you require while opening a bid or while bidding?

How do you search about the profile of other companies and what important details do you need?

In your opinion, how would an E-Procurement network increase the performance of a corporate network?

According to you, how the users should be trained to use the system?

What are the problems that the users might face while using the system?

Please provide your suggestions about the system.

4.2 Academic Research

The academic research section comprised of reading books, journals, articles, technical magazines and whitepapers. The research topics searched mainly were concepts of web development, enterprise resource planning, procurement platforms, programming languages and database systems. Research based on software development methodologies and practices also constituted the academic part. The research required was quite extensive, the brief of which is being provided in the following sections.

4.2.1. Technical Research

4.2.1.1 System Development Methodology

4.2.1.1.1 What is System Development Methodology?

The discipline of software engineering is the practice of using chosen process techniques to improve the quality of a system/software development effort. System development methodology consists of research, tools, methods and reasonable documentation which are beneficial as a whole for the development and implementation of the system, from the prospective of the developer. Software development methodology aims to deliver software applications/systems within the specified time and on budget while adjusting for varying requirements along the development phase.

4.2.1.1.2 Need for a Methodology

A software development methodology helps to monitor the project, assist in scheduling and budgeting of the project. The success of a project critical to the software development methodology selected. The basic steps of planning, analysis and design are innate to most of the methodologies, while the actual structure of how to carry on further development is exceptional to the software development methodologies. Each of the available methodologies is best suited to specific kinds of projects, based on various technical, organizational, project and team considerations.

4.2.1.1.3 Selected Methodology

After research of the project development methodologies the following models were found suitable for developing the system:

Waterfall Model

Spiral Model

Prototype Model

Why not Waterfall Model

The waterfall model needs all entire specification and requirements for the system explicitly. This is difficult to chalk out as users may demand change in system after using it or the system may not be up to the mark in functionality after development. This would require the specification to be slightly changed for better functionality of the system.

It leaves testing for later phases which creates a risk factor as the whole system may be altered as a result of fault identified in testing phase.

Modular approach: Each of the specific modules cannot be checked until the final system is developed. But I need to check modules such as bidding, messaging, forums, and chats individually.

Why not Spiral Model

It demands expertise in risk evaluation and reduction.

It is a complicated process and is difficult to follow.

It is time taking also as same modules are checked again and again.

Why Prototype Model

The software methodology which the developer has chosen for developing the system is Prototype model. This model involves creation of prototypes i.e. incomplete version of the system being developed. The prototype basically consist only few features of the actual system being developed. This prototype is further refined according to the feedback received from the users and according to the advance requirements. Thus it would help me to build individual prototypes of modules like messaging, bidding, chatting.

The prototype model consists of following steps:

Identification of basic requirements: Determination of basic requirement such as the input output information expected. The validation and security details can be ignored initially.

Development of the first prototype: The initial basic prototype which involves the user interfaces.

Review: The users including system users provide feedback about the system. This results in addition or changes accordingly.

Enhancement of prototype: Based of the feedback and system performance the system is amended and an improved prototype is developed, which is again reviewed. If additions or changes are required then steps 3 and 4 are followed repeatedly till the final system is developed.

Similarly the proposed project being developed would be built in prototypes. The developer would first develop a prototype consisting of the core functionalities only. This prototype would be examined for its performance and efficiency. The prototype would be refined accordingly for better performance and output. This prototype would be refined again by adding the enhanced functionalities of the system such as messaging, user account/profile management, automatic notification facility and rating facilities. This prototype would again be reviewed and refined. The refined prototype would then include the special features such as basic chatting and SMS alerts. AJAX would be implemented in all the prototypes as required. Since the project is a web based ERP, the best possible prototype model for it is extreme prototyping model. Extreme prototyping is especially used for web based applications. It fundamentally divides web development into three phases, each based on its preceding one. The first pages consist mainly of HTML pages. The second phased involves designing of the functional screens such as creation of project requirements and submission of bids. The third phase is the actual implementation phase where the services are implemented. Thus modules like messaging and basic chatting would be tested individually as prototypes in second phase.

4.2.2 Technical Research

4.2.2.1 Programming Languages

This section deals with the technical research carried out in respect to possible programming languages which are apt for the development of the proposed system. The proposed system being a web application has a variety of languages to choose from namely ASP.NET, JSP and PHP. The technical research that follows has been carried out to check for the most appropriate technology to be used in system development.

4.2.2.1.1 PHP

PHP is a server-side scripting language used to develop web applications. Its programming style is similar to the widely used C++ programming language. PHP mostly uses UNIX and LINUX server to run rather than Windows servers. It generally uses mySql database for its data handling operations. PHP is easy to use to use for new users as it offers great performance. But PHP has poor error /exception handling capabilities. The essential use of authorization redirection is to be done indirectly through code whereas other languages facilitate in easily. Moreover PHP required immense coding to be done by the developer. Apart from these there is no good dedicated visual tool to facilitate programming in PHP

4.2.2.1.2 JSP

Java is a widely used platform independent language. Java has huge repositories/libraries to be used in development of web or desktop based applications. JSP short for java server pages is used for web programming in Java. JSP is also a server side scripting language. The key features of the technology are:

Simple to learn: Java is simple to learn as a new programmer as many of the common programming requirements are automatically taken care of by the language itself.

Free Products: Java provides many free applications that can be integrated with other system. JSP provides freely accessible specification for extending Java Servlet API to generate dynamic web pages.

Difficult to Debug: It is difficult to debug java programming code as there is a conversion from java files to jsp files during compilation.

Syntax Problems: The JSP syntax has problems when used with different servlet engines.

4.2.2.1.3 ASP.NET

ASP.NET is a web application framework developed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. ASP.NET provides the choice of major programming languages including between VB.NET and C#.NET.

ASP.NET has various advantages over other languages. The main benefits are its rich services and in-built components for flexibility in coding. It is an event oriented language which includes nearly all the advantages of an object-oriented programming. Microsoft’s Visual Studio IDE has a huge number of tools for

Better functionality

Ease of programming

Faster development

ASP.NET codes are compiled rather than interpreted which results in much faster performance of web pages. ASP.NET supports creating reusable components through the creation of User controls. A user control follows the same structure as a Web form, except that such controls are derived from the UserControl class, and are stored in ASCX files.

4.2.2.3 Database Research

Database research is required to choose a reliable and inter-operable database with other technologies being used. The database of Microsoft Access, Microsoft SQL server and mySql were researched upon to determine the compatibility issues and operability for the proposed system.

4.2.2.3.1 Microsoft Access:

Microsoft Access is a proprietary package of Microsoft Office suite. MS-Access is easier to use and understand because of its simple user friendly graphical interface. Even new users can perform database administration tasks and use reporting services. It is mostly used by an average user to store light weight data.

MS-Access though easy to use with good interface but is not an apt choice when number of connected users increases. The time of execution increase as the number of user increases. MS Access has a limited storage capacity. In corporate scenario where immnensely huge number of transactions takes place the database will accumulate large amounts of data at a very small amount of time and would ultimately result in a crash. Apart from these MS-Access is also open to vulnerabilities as compared to others.

4.2.2.3.2 MySQL

MySQL is a free open source database that can be used in web development. MySQL is the most commonly used database in the website/application development along with PHP. The key features of the database are as follows:

Freely Available: MySQL database is an open source database management system.

Nice Performance: MySQL uses least hardware resources during execution to entertain database queries.

Security: Although MySQL is an open standard, it is still secure till date to use.

4.2.2.3.3 MS-SQL

Microsoft SQL server is the most widely used database along with .NET platform. It is a relational database server produced and marketed by Microsoft Corporation. MS-SQL is supported by all operating systems of windows and some of the UNIX, Linux operating systems. The basic languages supported are T-SQL and ANSI SQL. The key features of MS-SQL are as follows:

Simple to use: MS-SQL can be easily managed and deployed. An administrator can easily manipulate data and further manipulation can be monitored.

Data Mirroring: MS SQL stores a copy of transaction log from one machine to another which is extremely useful in data recovery.

Scalable: MS SQL is fully scalable and compatible with newer database concepts such as table partitioning and others.

Security: MS-SQL provides encryption services along with windows user account. It maintains a reasonable level of security.

Low Failure rate: MS-SQL server is available 24x7. The concept of database mirroring renders MS-SQL a reliable and efficient database management system.

4.2.3 Conclusion of Technical Research

According to the research carried out earlier the programming language of ASP.NET is the most suitable because of its faster development, dynamic web page designs and user controls. The most suitable database server is MS-SQL server database as it is highly compatible with .NET platform and provides excellent functionalities, apart from being reliable.

5. Analysis

The research carried out in preliminary investigation phase is of utmost importance. The result of the data gathering methods should be analyzed thoroughly to know the impact on the proposed system development. Most of the analysis has already been covered earlier. The following section would deal with the analysis of data gathering methods.

Questionnaires Analysis

Have you come across an online E-Procurement Solution?

Yes

No

If yes, please mention ………………………………………………………………

Justification: This question will help the developer know about other existing E-Procurement websites that may be needed for analysis of the system.

Analysis: Answer of this question says that only 70% organizations/corporate are aware of E-Procurement solutions and 90% organizations/corporate still are ignorant about the current R-Procurement systems. Thus developer gets an idea to improve the functionality of E-Procurement system to reach out to all of the corporate.

How would you rate the present system of E-Procurement: www.getafreelancer.com?

Excellent

Good

Fair

Poor

Justification: This question will help the developer know about the current standard of online E-Procurement and therefore define the requirements and standards of developing the system.

Analysis: Most of the users like the system, hence the developer has to provide better user interface and functionality.

Would you like to have an online E-Procurement solution?

Yes

No

Justification: This question will help the developer know the current demand of this system. More is the demand, more would be the expectation.

Analysis: Majority of the users require the proposed system. Hence the cost of the system can be calculated according to the demands.

How would you rate the inclusion of forums and blogs for discussion of projects and bids?

Extremely Necessary

Necessary

Optional

Not Required

Justification: This question will help the developer to know the importance of forum and blogs and similarly the design and implementation would follow.

Analysis: Majority of the users require the forums and blogs. Hence the deliverables should be positively met with required functionalities.

How would you like to communicate with other organizations?

Through Messaging

Through Chatting

Through Forums and Blogs

Through Phone

Justification: This question will help the developer to understand the priority of modules to be developed.

Analysis: Majority of the users require the forums and blogs. Hence they occupy the highest priority after the core functionalities.

Would this system benefit you in your day-to-day transactions?

Yes

No

Justification: This question will help the developer to understand the importance of the system in user’s daily life.

Analysis: Majority of the responses are positive. Hence the demand again increases in even in the daily life of the person.

How important is the interface design for you in this system?

Extremely Important

Important

Optional

Not Needed

Justification: This question will help the developer to analyze the design of the system.

Analysis: Majority of the users require better user interface design. Hence the developer has to work more on the user interface design and interactivity.

How do you gather information about the procurer/coder organization, with whom you want to deal?

Through Websites

Through Phone

Through Visit

Through Trusted Links

Justification: This question will help the developer to design the profile of the organization.

Analysis: Majority of users chose websites, hence profile management should be made with respect to average users.

Will this system save your time in regard to the current way of your business?

Yes

No

Justification: This question will help the developer to understand the design of user interface so as to comply with time spent on pages by individual user.

Analysis: The user interface design is to be made with special care so as to save time and resources.

Would you like pre-built templates for publishing bids?

Yes

No

Justification: This question will help the developer to know the importance of templates and estimate the number of templates to be provided.

Analysis: Majority of them require templates for ease and comfort. Hence templates should be made selectively by the developer.

What problems/hindrances can be faced in this system?

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Justification: This open-ended question would help to know the limitations of the system.

Analysis: This question identifies the problems, and the scope has been limited assordingly in the documentation.

Please provide your valuable suggestions for the system being developed?

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Justification: This open-ended question would help to know extra ideas and functionalities that can be implemented in the system.

Analysis: This question was helpful to the developer to know the mass-interests of the users.

5.2 Interview Analysis

In your opinion how would an E-Procurement system be useful for your organization?

Justification: This question would help the developer to know the advantages and its implementation of the system.

How would forums and blogs be useful to the system?

Justification: This question would help the developer to design the forums and blogs.

How would the option of chatting be helpful in the system?

Justification: This question would let the developer know the basic requirements of the users of chatting.

What information would you require while opening a bid or while bidding?

Justification: This question would let the developer estimate the no. of templates and decide the criteria required for bidding.

How do you search about the profile of other companies and what important details do you need?

Justification: This question would help the developer to design the profile of organizations.

In your opinion, how would an E-Procurement network increase the performance of a corporate network?

Justification: This question would help the developer to know about other features that would be helpful.

According to you, how the users should be trained to use the system?

Justification: This would help the developer to keep in mind the level of targeted users and develop the system accordingly.

What are the problems that the users might face while using the system?

Justification: This question would help the developer to know the limitations of the system and ways to overcome them.

Please provide your suggestions about the system.

Justification: This is an open-ended question which would provide the overall feedback of the system.

Analysis: The overall analysis was that the developer got to know the level of priority of the modules. Apart from the core functionalities the forums and blogs should be given top priority and then messaging and chatting modules. The user interface design has to be of considerable level as the users have high expectations from the proposed system.