Cloud

CHAPTER - 1 INTRODUCTION
Cloud computing is a process of outsourcing all business requirements to a single provider and there were no investment in hardware, licenses, or implementation to be made but just a single fee based on the usage of the application. That is the flexibility that cloud computing offers. Cloud computing is an evolving technology that brings together all the elements of hardware, software in a single package. This project is the development and implementation of a cloud computing system. The growing interest of customers and entry of large players into cloud computing is making cloud based services more robust and suitable for enterprise use. Cloud computing is Internet- ("cloud-") based development and use of computer technology ("computing"). In concept, it is a paradigm shift whereby details are abstracted from the users who no longer have need of, expertise in, or control over the technology infrastructure "in the cloud" that supports them. Cloud computing describes a new supplement, consumption and delivery model for IT services based on the Internet, and it typically involves the provision of dynamically scalable and often virtualized resources as a service over the Internet. The term cloud is used as a metaphor for the Internet, based on the cloud drawing used to depict the Internet in computer network diagrams as an abstraction of the underlying infrastructure it represents. Typical cloud computing providers deliver common business applications online which are accessed from a web browser, while the software and data are stored on servers. A technical definition is "a computing capability that provides an abstraction between the computing resource and its underlying technical architecture (e.g., servers, storage, networks), enabling convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with
1
minimal management effort or service provider interaction." This definition states that clouds have five essential characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service
1.1 PROBLEM STATEMENT

In todays work scenario, we need a way to track tasks and jobs for our organizational teams. The objective of this project is to automate the process of the Task Tracking to manage workloads easily, quickly, and efficiently, closely monitor task deadlines, allocate work fairly between team members and tracks overall and project progress. Automatic e-mail reminders, customizable work reports, charts of work allocation, forums for discussion and progress are the essential features now a days time is very precious, everyone is busy with ones work, and everyone wants to save their time. Todays and tomorrows world is of internet, people are becoming more and more internet dependent so considering these all things this site is planned to develop which will provide facility to the customer to find a project development in easy way . Now-adays, Time is money; everyone is too busy with their own work and their lives. Everyone wants to save their time and earn more money for ourselves and their family for their better future. People forgot how to enjoy their life.
1.2 OBJECTIVE OF THE PROJECT

The objective of the project includes the following points: Reduction of manual calculation of developer works, Code implementations, Project Division to its Project Heads, etc. To reduce the paper work, means instead of maintaining the information of each person (PM, TL, Developers with Hrs. calculations) & all the information related to person and Designation, information with huge registers storage may have chances of loss of that data.
To reduce time consumption means operations performed manually by different peoples take a lot of time. It can be reduced to a large extent by computerized system. It will help in saving the time of Staff/Client/vendor. For providing better facilities to the Staff/Vendor it is necessary to provide such features in software so that Vendor/Client/Staff will be able to get or view the information immediately when they want without going to a particular section /office /department with different Project Manager, Team Leaders etc. Safe data storage so that in future if any record is needed it will be searched easily without wastage of time. Today time factor is crucial. So this software provides the information about the person working on the specific Project Under TL and Project Manager
The basic theme behind the development of this project is that the facilities provided by the Software Development Company to its Staff and Vendor /Client check Project Development Status and the Staff Progress Performa also improves the work efficiency over the control of the project. Thats why the management wanted to automate the process with On Line Time sheet Management System.
1.3 FEATURES OF THE APPLICATION

1. The Application enables Staff/Team Leader/Project Manager to search in any record from the data bank, to check staff Progress, efficiency of the Staff. 2. Calculate hours spent on a Project for Cost estimation. 3. Application sends the acknowledgement to the person to confirm the receiving of his /her details, New Project, Completion of Code sections etc. 4. It includes a homepage containing a snapshot of all the projects under the user including the list of tasks, milestones, meetings, calendars and current developments in a tabular format.
3
5. Tasks: Assign multiple members to a task, set start/end dates & send email notifications. 6. Document Sharing: Share and manage project related files centrally to ensure efficient group collaboration. Ability to view, edit, and share & save back documents directly from the browser without downloading. 7. Forums: Forums for the project teams to openly interact and collaborate.
1.4 ADVANTAGES OF THE SYSTEM

Convenience: Application Works with Whole Staff to provide them Inter linking for Work Progress Searching Code and Code No: Project Code can easily be linked with another Team Leader or Project Manager. Efficiency: We can access and manage all of Company /Client /Vendor /Project Manager /Team Leader /Developer Status any Time Any Where while logging and Checking ID. Effectiveness: This application brings all staff with vendor/client to the center for making and providing fast and accurate news and progress chart status.
1.5 OPTIONAL FEATURES

24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension
CHAPTER 2 FEASIBILITY STUDY

4
The success of a system depends largely on how accurately a problem is defined, thoroughly investigated, and properly carried out through the choice of solution. User need identification and analysis are concerned with what the user need rather than what he/she wants. Not until the problem has been identified, defined, and evaluated should the analyst think about solutions and the problem is worth solving. This step is intended to help the user and the analyst understand the real problem rather than its symptoms. Identification of the needs greatly simplifies the system development. This is the pre analysis stages, which will gathers the reasons for requests made for a particular application and the origin of the application proposal. Requests for new application development are typically motivated by one of these general objectives: Business firms or individual users requests new application proposals for increased capability like improving processing speed, ability to handle increased volume, and faster retrieval of information. In our investigation we found several needs of the project, B-C Portal (Cloud Computing). Using the computers inherent ability to calculate, sort, and retrieve data and information when greater speed than that of people doing the same task is desired. Providing the capacity to process a greater amount of activity, perhaps to take advantage of new business opportunities. Needs locating and retrieving information from storage and conducting complex searches. Carrying out computing steps, including arithmetic, correctly and in the same way each time. Safeguarding sensitive and important data in a form that is accessible only to authorized personnel. Speeding the flow of information and messages between remote locations as well as within offices. Includes the transmission of documents within offices need for Coordinating business activities taking place in separate areas of an organization, through capture and distribution of information. Tracking the cost of labor, goods, and facilities to determine how actual costs compare with expectations. Using computing capability to process data at a lower cost than possible with other methods, while maintaining accuracy and performance level .
Changing the relationships with and services provided to customers in such a way that they would not choose to change to other dealers. Reducing the likelihood that competitors will be able to enter the same market because of the way organization uses information systems. Changing the pricing, service, or delivery arrangements, or relationship between suppliers and the organization to benefit the firm. Introducing new products with characteristics that use or are influenced by information technology.
2.1 PRELIMINARY INVESTIGATION

The purpose of the preliminary investigation is to evaluate project requests. It is not a design study, nor does it include the collection of details to completely describe the application. Rather, it is collecting the information that permits to evaluate the merits of the project request and make an informed judgment about the feasibility of the proposed application. The data that the analyst collected during preliminary investigation are gathered through two primary methods: reviewing existing applications and collecting opinions of the users throw different methods. 2.1.1 REVIEWING ORGANIZATION DOCUMENTS The analyst conducting the investigation first learns about the organization involved in, effected by, the project. We did this throw reviewing the organization charts of organization. And also we studied the operating procedures of each and every operation in the organization. 2.1.2 CONDUCTING INTERVIEWS Written documents tell the analyst how the system should operate, but they may not include enough detail to allow a decision to be made about the merits of system proposal, nor do they present user views about current operations. We did interviews with organization employees regarding several topics. As a result of both these, we extracted the drawbacks of the existing system and the merits of the proposed system. They are listed below.
6
2.2 ADVANTAGES OF PROPOSED SYSTEM

Good sales invoices and better transactions information. A good record of Sales history A fast and efficient database of customers. A good cost accounting system. A good profit planning system. A good sales forecasting system. A good inventory reordering mechanism, which intimates when a product falls in less standard stock quantity. A better automatic and fast way to record and maintain stock daily. Planning employee responsibilities and specifying employee targets is no more difficult. A faster way to produce employee performance reports and to maintain their daily reports. Now formal communications between organization and customers is easy in the form of automated document generations and printings. Maintaining daily expenses and generating monthly reports is not a tedious job. Generating financial reports like pending bills, monthly income and turn over is faster and automatic. Finally the proposed system is faster, accurate and needs less man power.
2.3 PROJECT FEASIBILITY

Preliminary investigation examines project feasibility; the likelihood the system will be useful to the organization. Feasibility report is the important outcome of the preliminary investigation.
7
2.4 OPERATIONAL FEASIBILITY

There is lot of support from management; in fact they request it. Because of the persons in the organization has been facing problems with the existing system there is no resistance to the change. And also the current methods are not acceptable to the users that are why they are welcoming to the new system. From the beginning of this new system we made users to involve in some way reducing the resistance.
2.5 TECHNICAL FEASIBILITY

There is no technology and equipment to implement the new system but it can be acquired. It is not a burden rather than that of existing system. The proposed equipment can safely handle the data required to use the new system. The proposed new system can easily be expanded to satisfy the new requirements in future. There is lot of security, accuracy and reliability in the new system rather than existing system. By considering the above reasons the proposed new system is technically feasible.
2.6 ECONOMIC FEASIBILITY

The cost to implement this new system includes cost of full systems investigation, cost of hardware and software and the cost of user training. The cost that may spend if the new system was not developed is greater than the cost of the new system. The cost to implement the proposed system is one time investment later they need not spent any more. The organization must get benefit if they invest on the proposed system development. By considering the above reasons the proposed new system is economically feasible. As this proposed system has passed all the three aspects of feasibility study we can declare it as a feasible project.
2.7 SOFTWARE ENGINEERING PARADIGM APPLIED

Several popular software engineering approaches are based on the notion of data flow. The structured analysis/structured design (SA/SD) methodology is representative of
the data flow approach. SA/SD begins with a single process or function that represents the overall purpose of the desired software. SA/SD recursively divides complex processes, until one is left with many small functions that are easy to implement.SA/SD and OMT modeling have much in common. Both methodologies support the three orthogonal views of a system the object, dynamic, and functional models. The difference is that SA/SD emphasizes the functional model while OMT emphasizes the object model. We believe that for most problems an object-oriented approach is superior to a data flow approach. An object-oriented design is more extensible, provides better trace ability, and better integrates database and programming code. Michael Jackson advocates a different approach to system development, called JSD. A JSD model begins with consideration of real world. One culls out the most important entities and actions in the real world, from the perspective of the application. The remaining JSD steps develop detailed pseudo code that precisely specifies desired software behavior and their correspondence to real world actions. We regard JSD as a valuable approach, as are SA/SD and OMT. Each methodology has its niche where it clearly excels. JSD is an excellent methodology for real-time and micro code applications. We consider JSD a poor approach for high-level analysis and database design. We have compared OMT object modeling to the entity-relationship (ER) informationmodeling notation. In essence, OMT object modeling is an enhanced form of ER. OMT object modeling improves on ER in the areas of expressiveness and readability. The OMT methodology builds on earlier object-oriented work and benefits from insights that have come with experience. As seen from above discussion we had decided that SA/SD is suitable for our application design. So, the software engineering paradigm we used is SA/SD methodology.
CHAPTER 3 PROJECT PLANNING

In planning section purpose is planed according to the web site customer because this system is going to work as web based application. As now a days world is going on
9
web and more and more number of people using web application, our application will provide the facility to search a suitable life partner in India. While planning a web based application certain things have been kept in mind like: It will be for a very large number of customers. We have to take care of situations like rare conditions, lost connections, timeouts and the tiresome realities of wide area networks. It is also frequently necessary to have scalable architecture that can be upgraded as application loads rise with the growing popularity of the site.
3.1 GANTT CHART

A Gantt chart is perhaps the simplest form of formal project management. The Gantt chart (also known as a Timeline Chart and Bar Chart) is used almost exclusively for scheduling purposes and therefore controls only the time dimensions of the project. Gantt charts, developed by Henry L. Gantt, are a project control techniques that can be used for several purposes, including scheduling, budgeting and resource planning. A Gantt chart is a bar chart, with each bar representing an activity. The bars are drawn against a time line. The length of each bar is proportional to the length of time planned for the activity. A Gantt chart helps in scheduling the activities of a project, but it does not help in identifying them. Once can begin with the activities of a project, but it does not help in identifying them. One can begin with the activities identified in the work breakdown structure. During the scheduling activity, and also during implementation of the Project, new activities may be identified that were not envisioned during the initial planning. The manager must then go back and revise the breakdown structure and the schedules to deal with these new activities. Thus helps in curving out the best way to manage the project.
GANTT CHART:10
Gantt Chart Tasks Data Collection Synopsis Submission Analysis Design Prototype Revision & Redesign Coding Testing & Implementation Project Submission
Jan 10 17 25 2
Feb & Mar 12 17 23
Feb & Mar 5 18
Fig 3.1(GANTT CHART)
3.2 PERT CHART

Unlike Gantt chart, Pert (Program evaluation and review technique) chart can be both a cost and a time management system, pert is organized by events and activities or tasks. Pert has several advantages over bar chart and is likely to be used with more complex projects. One advantage of pert chart it is scheduling device that also shows graphically which task must be completed before other are begin. Also, by displaying the various task path, Pert enable the calculation of critical path. Each path consists of combination of task which must be completed. the time and cost associated with each path along a path are calculated, and the path that require the greatest amount of elapsed time is the critical path calculation of the critical path enable project manager to monitor this series of task more closely than other and to shift resources to it if it begins to fall behind schedule .
11
Pert control time and cost during the project and facilities finding the right balance between completing a project on time it within the budget. Advantages: It forces the manager to plan. It shows the interrelationship among the task in the project and, in particular, clearly identifies the critical path of the project, thus helping to focus on it It expose all possible parallelism in the activities and thus help in allocating resources It allow scheduling and stimulation of alternative schedule It enable the manager to monitor and control the project
PERT CHART
12
Oct 20
Oct 22
Oct 22
Oct 28
Oct 29
Nov 16
start
Synopsis
Problem Definition
Feasibility Study
Nov 5 Nov 11
Dec 12
Nov 4
Nov 5
Oct 27
Nov 29
Nov 16
Performance Study, Final Documentation and Maintenance
Coding Of Individual Modules
Designing of login page
Design Analysis
Finish
FIG 3.2(PERT CHART)
CHAPTER 4
13
SYSTEM ANALYSIS
For software development very first and essential requirement is the availability of software and hardware. The software `Service Automation System' requires the following software and hardware for its successful implementation
4.1 Software Requirement

Client Side (Recommended) Any Operating System With Web Browser. Internet or LAN connection Server Side (Recommended) Operating System Scripting Language Back-End Mark-up Language Web-Server : : : : : WINDOWS XP /98/2000 JAVA SCRIPT JSP AND JDK1.6 SQL-SERVER 2000 HTML4.0, DHTML WEB-LOGIC 8.10
Front-End Language :
4.2 Hardware Requirement

Client Side (Recommended):Processor RAM Hard Disk Keyboard Mouse Processor RAM Hard Disk Keyboard : : : : : : : : : Pentium-III or above 256MB 40GB Any Any Pentium-IV 1 GB 40 GB Any
Server Side (Minimum):-
CHAPTER 5 SYSTEM DESIGN

14
One view of analysis modeling, called structured analysis, consider data and the process that transform the data as separate entities. Data object are modeled in a way that defines their attributes and relationship Design is the first step in the development phase for any engineered product or system. It can be defined as the process of applying various techniques and principles for the purpose of defining a device, a process or a system in sufficient detail to permit its physical realization. Design is basically the technical kernel of software engineering. During design, progressive refinements of data structure, program architecture, interfaces and procedural detail are developed, retrieved and documented. Design results in representations of software that can be assessed for quality. Design model creation requires information provided by each element of the analysis model. The design step produces a DATA DESIGN, an ARCHITECTURAL DESIGN, an INTERFACE DESIGN and a PROCEDURAL DESIGN. Data Design: It transforms the information domain model created during analysis into the data structure that will be required to implement the software. Architectural Design: It defines the relationships among major structural elements of the program. Interface Design: It describes how the software communicates within itself, to systems that interoperate with it and with humans who use it. Procedural Design: It transforms the structural elements of the program architecture into a procedural description of software components.
5.1 MODULARIZATION DETAILS

To provide the top down or divide and conquer approach to the software the systems are divided in to the different modules. Thus the overall problem is divided in to
15
manageable modules and each part or the module is developed separately. After developing all the modules they are integrated into one module or the required system. The project has been divided into ten main modules. The different modules of this system along with their functionality are following: i. Search module ii. Login module iii. Administrator module iv. Manager module v. Developer module vi Customer module vii. Projects service module viii. Suggestions module
i. Search module:This module is use to search anything about Project Development or you can search about its customers, engineer and administrator. You can only search but cannot service anything and cannot edit any information. The all persons who are an existing customer or any non-existing customers can use this module.
ii. Login module:This module is use to provide the conditional access to the system to different kind of customers based on their categories. Since the system has different working environment for customers, administrator and engineer. So this module will accept the customer id and password from the customer. After that the module searches the database for the category. Finally the corresponding set of forms will be displayed. This is the stating module of the software that prevents the unauthorized access of the software.
iii. Administrator module:This module is use to provide the all rights to the administrator. Administrator can access all the information about engineer and other customers. Administrator can add a new customer, a new manager or engineer. Administrator can delete exiting
16
engineer or another administrator. Administrator can also see the accounts of customer's. Administrator can service projects to customers.
iv. Developer module:This module is use to provide access rights to the Developer. Developer can add a new project and service projects. Manager cannot edit any record.
vi. Customer module:This module is use to provide access rights to the customer. Customer can search about the status of their service. Customer can also service projects for himself after login id and password validation. Customer cannot edit anything, they can only see them.
vii. Project module:Through this module customers can service any projects. But projects can service only some conditions when that is available in the Service Automation and there is no fine in customer's account. And the most important thing is servicer must be the customer of this Service Automation.
viii. Suggestions module:In this module customers can give any suggestion for improving the Service Automation. They can give projects information which they are needed. And give any other suggestion for management system.
5.2 Data Flow Diagram

The Data Flow diagram enables the software engineer to develop models of the information domain and functional domain at the same time. As the DFD is refined
17
into greater levels of detail, the analyst performs an implicit functional decomposition of the system.
5.3 Entity-Relationship (ER) Diagram

The ERD was originally proposed by Peter Chen [CHE77] for the design of relational database systems and has been extended by others. A set of primary components are identified for the ERD: data objects, attributes, relationships, and various type indicators. The primary purpose of the ERD is to represent data objects and their relationships.
Update Project Information
Generate Reports Maintain Project Details 18

DEVELOPER
R Code Development
PROJECT PARTICIPANT S
View all Details
View Project Status
Login Maintain User Account
CLIENT ADMINISTRATO R
Reset System
Fig 5.1 (USE CASE SURVEY MODEL)
View Project
Managem Managem ent ent 19 Authenticati Authenticati on on
ADMIN ADMIN
Security Security
Updating Updating Validation Validation
ADMIN MODULE
Fig 5.2 (USE CASE DIAGRAM)
Login New Client/Vendor
info info info
Employee
Payment info
Project
Time Sheet Management
info Project Queue info
20
Reporting
Context Level DFD
Fig 5.3 (CONTEXT LEVEL DFD)
Nam e Addr ess Id Client/Ven dor Industry type Nam e
Dept ID Departmen t
Design ation Code Categ ory
Id Employee
Nam e
Develop ment Id Project
Company
Nam e No of Hours.
Id Cate gory
Nam e
Job
Statu s Id
Work
Date Statu s Payment
21
Fig 5.4(ER DIAGRAM)
This E-R diagram depicts the relationship between the different entities present in this system.
5.4 DATABASE DESIGN:

S.NO . 1 2 3 4 5 6 7 8 9 10 11 12 Customer_ID FirstName MiddleName LastName C_ID Phone Email AddressLine1 AddressLine2 City State Country NUMBER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR 10 30 30 30 30 20 50 50 50 20 20 20 NOT NULL PRIMARY KEY FIELD NAME DATATYPE SIZE CONSTRAINTS
Table 5.1
(Customer Table)
22
S.NO . 1 2 3 4
FIELD NAME
DATATYPE
SIZE
CONSTRAINTS
l_id M_password Login_type Reg_date
VARCHAR VARCHAR VARCHAR DATETIME
10 20 20
PRIMARY KEY
Table 5.2 (Login Table)
S.NO . 1 2 3 4 5 6 7 8 9 10 11 12
FIELD NAME
DATATYPE
SIZE
CONSTRAINTS
Admin_ID A_ID FirstName MiddleName LastName Cellno Email AddressLine1 AddressLine2 City State Country
NUMBER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR
10 30 30 30 30 15 50 50 50 20 20 20
PRIMARY KEY NOT NULL
Table 5.3 (Administrator Table)
S.NO .
FIELD NAME
DATATYPE
SIZE
CONSTRAINTS
23
1 2 3 4 5 6 7 8 9 10 11 12
Man_ID M_ID FirstName MiddleName LastName cellno Email AddressLine1 AddressLine2 City State Country
NUMBER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR
10 30 30 30 30 15 50 50 50 20 20 20
Table 5.4(Employer Table)
S.NO . 1 2 3 4 5 6 7 8
FIELD NAME
DATATYPE
SIZE
CONSTRAINTS
Dev_ID D_ID FirstName MiddleName LastName cellno Email AddressLine1
NUMBER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR 24
10 30 30 30 30 15 50 50
9 10 11 12
AddressLine2 City State Country
VARCHAR VARCHAR VARCHAR VARCHAR
50 20 20 20
Table 5.5(Jobseeker Table)
S.NO . 1 2 3 4 5 6 7 8 9 10
FIELD NAME
DATATYPE
SIZE
CONSTRAINTS
f_id MessageType Subject Other feed_date Comments Username C_ID TelNo Fax
NUMBER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR NUMBER VARCHAR 20 20 20 20 20 500 30 30
PRIMARY KEY
NOT NULL NOT NULL
Table 5.6 (Feedback Table)
25
5.5 EXCEPTION HANDLING

To ensure that system doesn't halt in case of undesired situations or events, the following Exception conditions were taken care of by providing the corresponding exception responses while developing the system: While selecting an alternative from a menu, the user enters his choice. He goes ahead Only if the selected choice is convincing. While executing the screen, if the user tries to skip a field, which cannot have a null value, an appropriate message is displayed, conveying to the user that the data has to be entered into that field. Once the value has been entered into a field, the cursor moves to the next field. While A user enters date in invalid format; the system displays a message showing the valid format he/she should enter.
Security: The system provides the protection of information through the mechanism Of password incorporated into it. Therefore, only authorized user can access that database. Accuracy: The system is accurate. Thus, productivity/utility is high.
26
Flexibility: The system is such that likely changes/modification can be easily incorporated. Portability: The system has been written in HTML & Java Script as front end & SQL Server as back end and is portable to any platform-supporting SQL. Here we have used Weblogic 8.1 server for storage and working environment is Windows98/2000/XP. Throughput: The system gives a reasonably high throughput.
5.6 VALIDATON CHECK

The major decisions of a validation stage are concerned with handling errors and distribution of data. validation procedures. The data relevant to the system enters it through a set of Often they are caused by a generalized input validation
package tailored for the needs of a particular system. There are various ways of handling errors open to the designer which includes rejection of the item of input or processing the next item, writing error record and signaling the appropriate message to the user. Error procedures must be specified in detail showing decisions, actions and exceptions. In On-line Project Management, a few alternatives will be arranged. In most of the cases where error occurs an error message is popped to the user who is supposed to realize the fact and do the necessary steps. The program developed is checked thoroughly for errors by testing it with data and the errors that are raised during this can be clarified. The program may halt during an unpredictable error.
27
CHAPTER 6 CODING
6.1 PROGRAMMING LANGUAGE USED:
6.1.1 JAVA About the Java Technology Java technology is both a programming language and a platform.
28
The Java Programming Language
The Java programming language is a high-level language Each of the preceding buzzwords is explained in The Java Language Environment , a white paper written by James Gosling and Henry McGilton. In the Java programming language, all source code is first written in plain text files ending with the .java extension. Those source files are then compiled into .class files by the Java compiler (javac). A .class file does not contain code that is native to your processor; it instead contains bytecodes-- the machine language of the Java Virtual Machine. The Java launcher tool (java) then runs your application with an instance of the Java Virtual Machine.
FIG 6.1(JAVA PROGRAMMING STEPS) Because the Java Virtual Machine is available on many different operating systems, the same .class files are capable of running on Microsoft Windows, the Solaris
TM
Operating System (Solaris OS), Linux, or MacOS. Some virtual machines, such as the Java HotSpot Virtual Machine , perform additional steps at runtime to give your application a performance boost Easy development and deployment of Java Technology-based application that are:Transactional, distributed, multi-tier, portable, scalable, secure. 6.1.2 Java Server Pages (JSP) JSP is an exciting new technology that provides powerful and efficient creation of dynamic contents. It allows static web content to be mixed with Java code. It is a technology using server-side scripting that is actually translated into servlets and
29
compiled before they run. This gives developers a scripting interface to create powerful Java Servlets. Java Server Pages (JSP) allows development of dynamic web-bases user interfaces. Enables separation of business logic from presentationn Presentation is in the form of HTML or XML/XSLT Business logic is implemented as java Beans or custom tags Better maintainability, reusability Extensible via custom tags Builds on Servlet technology
FIG 6.2(JSP) Java Servlets provides a mechanism for extending the functionality of the web server to access the business systems. Java objects, which extend the functionality of a HTTP server Dynamic contents generation Better alternative to CGI, NSAPI, ISAPI, etc. -Efficient --Platform and server independent --Session management
30
Fig 6.3(Working of Web Server)
JDBC Servlet provides services for connectivity with relational databases. Privides standard java programming API to relational database --Use SQL Vendors provide JDBC compliant driver, which can be invoked via standard java programming API Java Message Services (JMS) version 1.0.2 is a standardized API for accessing Message-Oriented Middleware (MOM), and supports the Point-to-Point and Publish/Subscribe models. Messaging systems (MOM) provide -Decoupled communication --Asynchronous communication --Plays a role of centralized systems Benefits of Messaging systems
31
--Flexible, Reliable, Scalable communication systemsPoint-to-Point, Publish and Subscribe JMS defines standard Java APIs to messaging systems
Fig 6.2(Working of J2EE Server)
Java Remote Method Invocation, RMI-IIOP, part of the java 2 SDK version 1.3, Standard Edition, provides the ORB services and enables transparent remote method invocation between distributed objects and components. The ORB is protocol-independent and currently supports the RMI native protocol (JRMO) and the CORBA-compliant IIOP protocol. Java Interface Definition Language (IDL), part of the java 2 SDK version 1.3, Standard Edition, is a CORBA-compliant ORB that enables interoperability with external CORBA distributed objects using the IIOP protocol. Java Transaction API (JTA) version 1.0.1 and Java Transaction Services (JTS) version 1.1 provide support for transactions and provides interfaces for applicationlevel transaction demarcation. Java Authentication and Authorization Service (JAAS) version 1.0 provides security services, particularly authentication and authorization. It provides the
32
Pluggable
Authentication
Module
(PAM)
framework
implementation
for
authenticating users. Java Naming and Directory Interface (JNDI) version 1.2 part of the java 2 SDK version 1.3,Standard Edition, is a standardized API for accessing naming and directory services. Utilized by J2EE applications to locate resources and objects in portable fashion --Application use symbolic names to find object references to resources via JNDI --The symbolic names and object references have to be configured by system administrator when the application is deployed. Java API for XML Parsing (JAXP) version 1.1 provides support for handling XML-formatted data. It provides DOM (Document Object Model) and SAX (Simple API for XML) parsers and an XSLT (XML Style Sheet Language for Transactions) transformation engine. J2EE Connector Architecture version 1.0 is a service provider interface that enables the development of resource adapters through whi8ch the access to enterprise information systems is enabled. It defines a standard set of system-level contracts between a J2EE-compliant server and a resource adapter. JavaMail version 1.2 provides and API for managing e-mails and requires the JavaBeans Activation Framework (JAF).
6.1.2.1 JSP Scripting Elements JSP scripting elements are used to create and access objects, define methods, and manage the flow of control. Since one of the goals of JSP technology is to separate static template data from the code needed to dynamically generate content, very sparing use of JSP scripting recommended. JSP technology allows a container to support any scripting language that can call java objects. If you wish to support any scripting language other than the default, java, you must specify it in a page directive at the beginning of a
33
JSP page: <page language=scripting language %> Since scripting elements are converted to programming language statements in the JSP pages served class, you must import any classes and packages used by a JSP page. If the language is java, you import a class or package with the page directive: <%page import=package name.*fully_qualified_classname %> Declarations A JSP declaration is used to declare variables and methods in a pages scripting language. The syntax for a declaration is as follows:
<%! Scripting language declaration %> When the scripting language is the programming language, variables and methods in JSP declarations in the JSP pages servlet class. Script lets A JSP Scriptlet is used to contain any code fragment that is valid for the scripting language used in a page. The syntax for a scripting is as follows: <% scripting language statements %> When the scripting language is set to java, a scriptlet is transformed into a java programming language statement fragment and is insert into the service method of the JSP pages servlet. A programming language variable created within a scriptlet is accessible from anywhere within the JSP page. Expressions A JSP expression is used to insert the value of a scripting language expressions converted into a string, into the data string returned to the client. When the scripting language is the Java programming language, an expression is transformed
34
into a statement that converse the value of the expression into a String object and inserts into the implicit out object: The syntax for an expression is as follows: <%=scripting language expressions % > Note that a semicolon is not allowed within a JSP expression, even if the same expression has a semicolon when you use it within a scriplet. Using Tags This section describes how a page author specifies that a JSP page is using a tag library and introduces the different types of tags. Declaring Tag Libraries You declare that a JSP page will use tags define in a tag library by including a tag library directive in the page before any custom tag is used: <%@taglib uri=/WEB-INF/tutorial-template.tldprefix=tt %> This taglib directive uses a short logical name to indirectly reference the TLD: <%@taglib uri=/tutorial-templateprefix=tt %> What is Custom Tag ? A custom tag is a user define JSP language element. When a JSP page containing a custom tag is translated into a servlet, the tag is converted to operation on an object called tag handler. The web containers than invokes those operation when the JSP pages servlet is execute. Custom tags have a rich set of features. Be customized via attributes passed from the calling page. Access all the objects the available to JSP pages. Modify the response generated by the calling page. Communicate with each other. You can create and initialize a Java Beans component, create vriable that refers to that bean in one tag, and then use the bean in another tag.
35
Be nested within one another ,following for complex interaction within a JSP page Types of Tag JSP custom tags are written using XML syntax. They have a start tag and end tag, and possibly a body: <tt:tag> Body </tt:tag/> A custom tag with no body is expressed as follows: <tt:tag /> Simple Tags A simple tag contains no body and no attributes: <tt:simple/> Tag with Attributes A custom tag can have attributes. Attributes are listed in the start tag and have the syntax attr=value. Attribute values serve to customize the behavior of a custom tag just as parameters are used to customize the behavior of a method. You specify the types of a tags attributes in a tag descriptor. You can set an attribute value from String consent or a runtime expression. The conversion process between the constants and runtime expression and attribute types follows the rules described for Java Beans component properties in Setting JavaBeans Component Properties . The attributes of the Struts logic: present tag determines whether the body of the tag is evaluated .In the following example, an attribute a specifies a request parameter named clear: <logic: present parameter=Clear>
36
The Dukes Bookstore application page catalogs use a runtime expression to set value of the attribute that determines the collection of books over which the Struts logic: iterate tag iterates: <logic: iterate collection=<%=bookDB.getBooks () %> id=book type =database.bookDetails> Tag with Bodies A custom tag can contain and core tags, scripting elements, HTML text, and tag dependent body content between the start and end tag. In the following example, the Dukes Bookstore application page showcart.jsp uses the Struts logic: present tag to clear the shopping cart and print a message if the request contains parameter named clear: <logic: present parameter=Clear> <%cart .clear ();%> You just cleared your shopping cart! </logic: present> Choosing between Passing Information as Attributes or Body As shown in the last two sections, it is possible to pass a given piece of data as an attribute of the tag or as the tags body. Generally speaking, any data that is a simple string or can be generated by evaluating a simple expression is best passed as an attribute. Tag That Define Scripting Variables A custom tag can define a variable that can be used in scripts within a page. The following example illustrates how to define and use a scripting variable that contains an object returned from a JNDI lookup. Examples of such objects include enterprise beans, transaction, database, environment entrees, and so on: <tt:lookup=txtype=User Transaction
37
name=java:comp/User Transaction/> <%tx.begin();%> In the dukes bookstore application, several pages use bean oriented tags from struts to define scripting variables. For example, book details .jsp uses the bean: parameter tag to create the book Id scripting variable and set it to the value of the book Id request parameter. The jsp: setProperty statement also sets the book Id property of the book DB object to the value of the book Id request parameter. The bean: define tag retrieves the value of the bookstore database property book details and defines the result as the scripting variable book. <bwan: parameter id=book IDname=bookID/> <jsp set Property name=bookDBproperty=bookID/> <bean: defined id=bookname=bookDBproperty=book Details Type=database. Book details/> <h2><jsp.property name=book property=title></h2>
Cooperating Tags Customer tags can cooperate with each other through shared objects. In the following example, tag1 create an object called obj1, which is then reused by tag 2.<tt:tag1 attr1=obj1value1=value/> <tt:tag2 attr1=obj1> In the next example, an object create by the enclosing tag of the group of nested tag is available to all the inner tags. Since the object is not named, the potential for naming conflicts is reduced. This example illustrates how a set of cooperating nested tags would appear in a JSP page. <tt:outerTag> <tt: innerTag/> <tt: outerTag>
38
Including Content in a JSP page There are two mechanism for including another web resource in a JSP page:the including directive and the jsp:including element. The including directive is processed when the JSP page is translated into a servlet class. The effect of the directive is to insert the text contained in another file-either static content or another JSP page in the including JSP page. You would probably use the including directive to include banner content, copyright information, or any chunk of the content that you might want to reuse in another page. The syntax for the including directive is as follows: <%@include file=filename %> For example, all the bookstore application pages include the file banners containing the banner content with the following directive: <%@include file=banner.jsp%> In addition, the pages bookstores, bookdetails.jsp, catalogs, and showcart.jsp include JSP elements that create and destroy a database bean with the following directive: accessed through %@include file=initdestroy.jsp% Because you must statically put an include directive in each file that reuses the resource referenced by the directive, this approach has its limitation. For a more flexible approach to building pages out of content chunks, see A Template Tag Library. The jsp:include element is processed when a JSP pages is executed. The include action allows you to include either a static or dynamic resource in a JSP file. The results of including static and dynamic resources are quite different. If the resource is static, its content is inserted into the calling JSP file. If the resource is dynamic, the request assents to the included resource, the included page is executed, and then the result is included in the response from the calling JSP page. The syntax for the jsp:include element is as follows: <jsp: include page=included Page/>
39
The date application introduced at the beginning of this chapter includes the page that generates the display of the localized date with the following statement: <jsp:include page=date.jsp/> Extending the JSP language You can perform a wide variety of dynamic processing tasks including accessing data base, using enterprise service such as e-mail and directories, and managing flow control with java beans components in conjunctions with script lets, one of the drawbacks of the script lets, however, is that tend to make JSP pages more difficult to maintain. Alternatively, JSP technology provides mechanism called custom tag that allows you to encapsulate dynamic functionality in the objects that are extension to the JSP language. Custom tags bring the benefits of another level of componentization to the pages. For example recall the script let used to loop through and display the content to the dukes Bookstore shopping cart: <% Iterator I=cart. getItems().iterator(); While(i.hasNext()){ ShoppingCartItem item=(ShoppingCartItem)i.next(); %> <tr> <td align=right bgcolor =#ffffff> <%=item.getQuantity()%> </td> <% } %>
40
An iterate custom tag eliminates the code logic and manages the scripting variable item that reference elements in the shopping cart: <Logic: iterate id=item> collection =<%=cart.getItems()%> <tr> <td align=right bgcolor =ffffff> </td> </logic:iterate> Custom tags are packaged and distributed in a unit called a tag library. The syntax of custom tags is the same as that used for the JSP elements, namely, <prefix:tag>;however, For custom tags, prefix is defined by the user of the tag library and is define by the tag developer. Creating Static Content You create a static content in a JSP page by simply writing it as if you where creating a page that consisted only of that content. Static content can be expressed in any text based format such as HTML, WML and XML. The default format is HTML. If you want to use a format other than HTML, you include a page directive with the content Type attribute set to the format type at the beginning of your JSP page .For example, if you want a page to contain data expressed in the wireless mark up language (WML),you need to include following directive:%@page contentType=text/vnd.wap.wml% Creating Dynamic Content You create dynamic content by accessing Java Programming Language objects from with in scripting element. Using Objects within JSP Pages
41
You can access a variety of objects, including enterprise beans and JavaBeans components with in a JSP page. JSP Technology automatically makes some objects available, and you can also create and access application-specific objects. Application Specific Objects When possible, application behavior should be encapsulated in objects so that page designers can focus on presentation issues. Objects can be created by developers who are proficient in java programming language and in accessing database and other services. There are four ways to create and use objects with in a Java Page: Instance and class variable of the JSP pages servlet class are created in declarations and access in script let and expressions. Local variable in the JSP pages servlet classes are created and use in scriptlets and expression. Attribute of scope object are created and use in scriptlets and expression. JavaBeans components can be created and accessed using streamlined. You can also create JavaBeans components in a declaration of scriptlet and invoke the method of JavaBeans components in a scriptlet or expression. Shared Objects When is thread safe is set to true, the web container may choose to dispatch multiple concurrent client requests to the JSP page. This is default setting. If using true, you must ensure that you properly synchronize access to any shared objects defined at he page level. This Include objects creates within declarations, JavaBeans components with page scope, and attributes of the page scope objects. If is thread safe is set to false request are dispatched one at a time, in the order they were received, and access to page level objects does not have to be controlled. How ever you still must ensure that access to attributes of the applications or session scope objects and to JavaBeans components with application or session scope is properly synchronized. BACK END
42
We have used SQL Server 2000 as the back end. SQL Server provides efficient/effective solution for major database tech. This database technique has following advantages: Large database and space management. Many concurrent database users. High transaction processing requirement. High Availability. Industry accepted standards. Manageable security. Portability Compatibility Connectivity
6.2 DATABASE CODING

--------dsn name occs create database ccsDB; use ccsDB; create table login( l_id varchar(30) not null primary key, m_password varchar(20), login_type varchar(20), reg_date datetime); insert into login values('chetan','chetan','Administrator','02/15/2012');
43
insert into login values('akhil','ravi','Customer','02/15/2012'); insert into login values('aaa','cccccc','Customer','02/15/2012'); insert into login values('bbb','cccccc','Customer','02/15/2012'); insert into login values('ccc','cccccc','Customer','02/15/2012'); insert into login values('ddd','cccccc','Customer','02/15/2012'); insert into login values('eee','cccccc','Customer','02/15/2012'); create table User_Info ( User_ID integer primary key, l_id varchar(30)not null , FirstName varchar(30), MiddleName varchar(30), LastName varchar(30), phone varchar(20), Email varchar(50), AddressLine1 varchar(50), AddressLine2 varchar(50), City varchar(20), State varchar(20), Country varchar(20) ); insert into User_Info values(10001,'ravi','Ravi','','Kumar','9837111299', 'ravi@rediffmail.com','302/2','Saket','Meerut','UP','India' ); create table Admin_Info ( Admin_ID integer primary key, l_id varchar(30)not null, FirstName varchar(30), MiddleName varchar(30), LastName varchar(30), cellno varchar(15), Email varchar(50), AddressLine1 varchar(50), AddressLine2 varchar(50),
44
City varchar(20), State varchar(20), Country varchar(20) ); Insert into Admin_Info values(11,'chetan','Chetan',' ','Kumar','9837211112', 'chetan@gmail.com','30','Jagriti Vihar','Meerut','UP','India' ); insert into Admin_Info values(12,'akhil','Akhil',' ','Kumar','9837211122', 'akhil@gmail.com','1/4','Shastri Nagar','Meerut','UP','India' );
/*******************************************/ create table textedit ( editid int not null primary key, l_id varchar(30) not null, efilename varchar(100), efile varchar(6000), edate datetime ); insert into textedit values(10001,'ravi','abc.txt','abc',getdate());
/*******************************************/ create table ChatBoard ( chat_id integer not null primary key, l_id varchar(30) not null, cdate datetime, AllMessages varchar(6000), AddresTo varchar(30) not null , Message varchar(500) );
45
insert
into
ChatBoard
values(11001,'ravi','04/11/2012','hdfhgxfcgdhgdrgdrgdr','chetan','dfgpdrpogjdf'); /*******************************************/ create table feedback ( f_id integer not null primary key, MessageType varchar(20), ent_date datetime, Comments varchar(20), Username varchar(20), l_id varchar(30) not null, TelNo varchar(15) not null , email varchar(50), ); Insert 0','ravi@gmail.com'); /*******************************************/ select * from login select * from User_Info select * from Admin_Info select * from textedit select * from ChatBoard select * from feedback /*******************************************/ into feedback values(8000,'Suggestion','03/11/2012','klngldfjgdfjgl;jdf','Ravi','ravi','987652010
46
HOMEPAGE.JSP
<html xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>CLOUD COMPUTING</title> <base target="_self"> </head> <body topmargin="0" bgcolor="#FFFFFF" >
47
<table style="position: <tr>
border="3" absolute;
width="895"
bordercolorlight="#CACAFF" collapse; left:10; top:19"
bordercolordark="#000080" bgcolor="#DDDDFF" height="600" cellspacing="0" border-collapse: bordercolor="#111111" cellpadding="0"> <td width="1000" valign="top" height="450"> <blockquote> & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; WELCOME COMPUTING</MARQUEE> > > size="5"><MARQUEE CLOUD TO
color="#000080"
<table border="0" cellpadding="0" cellspacing="0" style="bordercollapse: collapse; position: absolute; left: 232; top: 165" bordercolor="#111111" width="227" id="AutoNumber1" height="200"> <tr> <td width="408" style="position: absolute; left:0; top:7" height="287"> 
48
 <IMG SRC="images/image001.png" align="left" width="402" height="301"></td> </tr> </table> </blockquote> </td> </tr> </table>
ADMIN LOGIN.JSP
<%@ page import="java.util.*" %> <%@ page import="java.sql.*" %> <%@ page import="java.text.*" %> <%@ page import="java.sql.Date" %> <%@ page language = "java" %> <%@ page session="true" %> <%session.removeAttribute("username");%>
<%! String username=new String();%> <%! String password=new String();%> <% username=request.getParameter("username"); password=request.getParameter("password"); try{
49
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection connect; connect=DriverManager.getConnection("jdbc:odbc:occs","",""); Statement stmt; stmt = connect.createStatement(); String strQuery1 = "select m_password ,login_type from login where l_id='"+username+ "'"; ResultSet result1 = stmt.executeQuery(strQuery1); String pass=new String(); String type=new String(); if(result1.next()) { pass=result1.getString("m_password"); type=result1.getString("login_type");
if(pass.equals(password) && type.equals("Administrator")) { session.setAttribute("username", username); session.setAttribute("type", "Administrator"); response.sendRedirect("admin_home_page.jsp"); } else { response.sendRedirect("InvalidPassA.htm"); } } else { response.sendRedirect("InvalidUserA.htm"); } }
50
catch(Exception e){ response.sendRedirect("error.htm"); } %>
ADMIN HOME.JSP
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>CLOUD COMPUTING</title> <base target="_self"> </head> <body topmargin="0" bgcolor="#FFFFFF" > <table border="3" width="895" bordercolorlight="#CACAFF" bordercolordark="#000080" bgcolor="#DDDDFF" height="600" cellspacing="0"
51
style="position: <tr>
absolute;
border-collapse:
collapse;
left:10;
top:19"
bordercolor="#111111" cellpadding="0"> <td width="1000" valign="top" height="450"> <blockquote> & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; WELCOME COMPUTING</MARQUEE> <%@ page import="java.sql.*" %> <%@ page import="java.text.*" %> <%@ page import="java.sql.Date" %> <%@ page language = "java" %> <%@ page session="true" %> > > > size="5"><MARQUEE CLOUD TO
color="#000080"
52
<table
border="2"
width="895"
bordercolorlight="#702BFF" collapse"
bordercolordark="#000080" <tr>
style="border-collapse:
bordercolor="#111111" cellpadding="0" cellspacing="0" height="33"> <td width="130" height="33" valign="middle" align="center"> <a href="ChgPwdAdmin.htm"> Change Pass</a></td> <td width="130" height="33" valign="middle" align="center"> <a href="RegisteeAdmin.htm"> New Admin</a></td> <td width="158" height="33" valign="middle" align="center"> All Files</a><a href="ViewAllTextAdmin.jsp"> Account</a></td> <td width="245" height="33" valign="middle" align="center"> <a Feedback</a></td> <td width="98" height="33" valign="middle" align="center"> <a action="invalidate" href="logout_page.jsp"> Logout</a></td> </tr> </table> <table <tr> <td width="82%" valign="top"> <%! String name;%> <% try { name=(String)session.getAttribute("username"); session.setAttribute("username",name); border="0" width="895" bordercolorlight="#FF9966" bordercolordark="#800000"> href="ViewAllFBAdmin.jsp">View Customers face="Arial" color="#702BFF"><a
53
} catch(Exception e) { } %> Dear&nbsp <%=name %>, Welcome. ADMIN Select an appropriate menu. </table> color="#702BFF"> <%= new java.util.Date() %> </td>
 <table border="0" cellpadding="0" cellspacing="0" style="bordercollapse: collapse; position: absolute; left: 620; top: 265" bordercolor="#111111" width="227" id="AutoNumber1" height="200"> <tr> <td width="227" style="position: absolute; "> <img border="0" src="images/image001.png" width="226" height="261"></td> </tr>
54
</table> </blockquote> </td> </tr> </table>
</body> </html>
CLIENT LOGIN.JSP
<%@ page import="java.util.*" %> <%@ page import="java.sql.*" %> <%@ page import="java.text.*" %> <%@ page import="java.sql.Date" %> <%@ page language = "java" %> <%@ page session="true" %> <%session.removeAttribute("username");%>
<%! String username=new String();%> <%! String password=new String();%> <% username=request.getParameter("username"); password=request.getParameter("password"); try{ Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection connect; connect=DriverManager.getConnection("jdbc:odbc:occs","",""); Statement stmt; stmt = connect.createStatement();
55
String strQuery1 = "select m_password ,login_type from login where l_id='"+username+ "'"; ResultSet result1 = stmt.executeQuery(strQuery1); String pass=new String(); String type=new String(); if(result1.next()) { pass=result1.getString("m_password"); type=result1.getString("login_type"); if(pass.equals(password) && type.equals("Customer")) { session.setAttribute("username", username); session.setAttribute("type", "Customer"); response.sendRedirect("user_home_page.jsp"); } else { response.sendRedirect("InvalidPass.htm"); } } else { response.sendRedirect("InvalidUser.htm"); } } catch(Exception e){ response.sendRedirect("error.htm"); }
56
USER HOME.JSP
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>CLOUD COMPUTING</title> <base target="_self"> </head> <body topmargin="0" bgcolor="#FFFFFF" > <table style="position: <tr> <td width="1000" valign="top" height="450"> <blockquote> border="3" absolute; width="895" bordercolorlight="#CACAFF" collapse; left:10; top:19" bordercolordark="#000080" bgcolor="#DDDDFF" height="600" cellspacing="0" border-collapse: bordercolor="#111111" cellpadding="0">
57
 & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; WELCOME COMPUTING</MARQUEE> <%@ page import="java.sql.*" %> <%@ page import="java.text.*" %> <%@ page import="java.sql.Date" %> <%@ page language = "java" %> <%@ page session="true" %> > > > size="5"><MARQUEE CLOUD TO
color="#000080"
<table
border="2"
width="895"
bordercolorlight="#702BFF" collapse"
bordercolordark="#000080" <tr>
style="border-collapse:
bordercolor="#111111" cellpadding="0" cellspacing="0" height="33"> <td width="154" height="33" valign="middle" align="center"> <a href="ChgPwd.htm">
58
Change Pass</a></td> <td width="330" height="33" valign="middle" align="center"> <a Application</a></td> <td width="239" height="33" valign="middle" align="center"> <a href="ViewAllText.jsp">View Files Account</a></td> <td width="239" height="33" valign="middle" align="center"> <a href="ChatRoom.jsp">Chat Forum</a></td> <td width="239" height="33" valign="middle" align="center"> <a href="feedback.jsp">Feedback</a></td> <td width="142" height="33" valign="middle" align="center"> <a action="invalidate" href="logout_page.jsp"> Logout</a></td> </tr> </table> <table <tr> <td width="82%" valign="top"> <%! String name;%> <% try { name=(String)session.getAttribute("username"); border="0" width="100%" bordercolorlight="#FF9966" bordercolordark="#800000"> href="demo/index.jsp">Request For
} catch(Exception e) {
59
} %> Dear&nbsp <%=name%>, Welcome. CUSTOMER Select an appropriate menu. <%= new java.util.Date() %> </td> </tr> </table> 
 <table border="0" cellpadding="0" cellspacing="0" style="bordercollapse: collapse; position: absolute; left: 620; top: 265" bordercolor="#111111" width="227" id="AutoNumber1" height="200"> <tr> <td width="227" style="position: absolute; "> <img border="0" src="images/image001.png" width="226" height="261"></td> </tr> </table> </blockquote> </td> </tr> </table>
60
</body> </html>
CHATROOM.JSP
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>Register Page</title> </head> <%@ page session="true"%> <%@ page import="java.util.*" %> <%@ page import="java.sql.*" %> <%@ page import="java.text.*" %> <%@ page import="java.util.Date" %> <%@ page import="javax.servlet.http.HttpSession" %> <%@ page language = "java" %> <%! String name;%> <% try { name=(String)session.getAttribute("username"); session.setAttribute("username",name);
} catch(Exception e) {
61
response.sendRedirect("error.htm"); } %>
<% String chatroom=""; String cname=""; String message=""; Connection conn=null; Statement stat=null; ResultSet rs=null; try { chatroom=request.getParameter("chatroom"); cname=request.getParameter("cname"); message=request.getParameter("message");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); conn = DriverManager.getConnection("jdbc:odbc:occs","",""); stat= conn.createStatement(); int r_id=0; String AllMessages=""; String querry="select chat_id,AllMessages from ChatBoard"; ResultSet rset=stat.executeQuery(querry); while(rset.next()) { r_id=rset.getInt("chat_id"); AllMessages=rset.getString("AllMessages");
62
} r_id=r_id+1; AllMessages=AllMessages+"\n\n CAHT_ID : "+r_id+" "+cname+" MESSAGE : "+message ; TO :
FROM : "+name+"\n DATED : "+new java.util.Date()+"\n
String strQuery1 = "Insert into ChatBoard values("+r_id+",'"+name+ "',getdate(),'"+AllMessages+"','"+cname+ "','"+message+"')"; int ii=stat.executeUpdate(strQuery1);
conn.close(); } catch(Exception ee) { System.out.println(ee); response.sendRedirect("error.htm"); } %> <jsp:include page="ChatRoom.jsp"/> </body> </html>
63
FEEDBACK.JSP
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>CLOUD COMPUTING</title> <base target="_self"> </head> <body topmargin="0" bgcolor="#FFFFFF" > <%@ page session="true"%> <%@ page import="java.util.*" %> <%@ page import="java.sql.*" %> <%@ page import="java.text.*" %> <%@ page import="java.util.Date" %> <%@ page import="javax.servlet.http.HttpSession" %> <%@ page language = "java" %> <%! String name;%> <% try { name=(String)session.getAttribute("username"); if(name==null){response.sendRedirect("Login.html");} session.setAttribute("username",name); }
64
catch(Exception e) { response.sendRedirect("error.htm"); } %> <table border="3" width="895" bordercolorlight="#CACAFF" bordercolordark="#000080" bgcolor="#DDDDFF" height="600" cellspacing="0" style="position: absolute; border-collapse: collapse; left:10; top:19" bordercolor="#111111" cellpadding="0"> <tr> <td width="1000" valign="top" height="450"> <blockquote> & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; <MARQUEE bgcolor="#DDDDFF">WELCOME TO CLOUD COMPUTING</MARQUEE> >
65
 Tell us what you think about our web site, our plan, our organization, or anything else that comes to mind. We welcome all of your comments and suggestions. <form method="post" action="feedbackproc.jsp"> What kind of comment would you like to send? <dl> <dd><input type="radio" value="Complaint" name="MessageType">Complaint <input type="radio" value="Problem" name="MessageType">Problem <input type="radio" CHECKED value="Suggestion" name="MessageType">Suggestion <input type="radio" value="Praise" name="MessageType">Praise </dd> </dl> What about us do you want to comment on? Entry Date : <SELECT class=nicefield name="db2"><OPTION value=0 selected>MM</OPTION> <OPTION value=01>01</OPTION> <OPTION value=02>02</OPTION> <OPTION value=03>03</OPTION> <OPTION value=04>04</OPTION> <OPTION value=05>05</OPTION> <OPTION value=06>06</OPTION> <OPTION value=07>07</OPTION> <OPTION value=08>08</OPTION> <OPTION
66
value=09>09</OPTION> <OPTION value=10>10</OPTION> <OPTION value=11>11</OPTION> <OPTION value=12>12</OPTION></SELECT> <SELECT class=nicefield name="db1"> <OPTION value=0 selected>DD</OPTION> <OPTION value=01>01</OPTION> <OPTION value=02>02</OPTION> <OPTION value=03>03</OPTION> <OPTION value=04>04</OPTION> <OPTION value=05>05</OPTION> <OPTION value=06>06</OPTION> <OPTION value=07>07</OPTION> <OPTION value=08>08</OPTION> <OPTION value=09>09</OPTION> <OPTION value=10>10</OPTION> <OPTION value=11>11</OPTION> <OPTION value=12>12</OPTION> <OPTION value=13>13</OPTION> <OPTION value=14>14</OPTION> <OPTION value=15>15</OPTION> <OPTION value=16>16</OPTION> <OPTION value=17>17</OPTION> <OPTION value=18>18</OPTION> <OPTION value=19>19</OPTION> <OPTION value=20>20</OPTION> <OPTION value=21>21</OPTION> <OPTION value=22>22</OPTION> <OPTION value=23>23</OPTION> <OPTION value=24>24</OPTION> <OPTION value=25>25</OPTION> <OPTION value=26>26</OPTION> <OPTION value=27>27</OPTION> <OPTION value=28>28</OPTION> <OPTION value=29>29</OPTION> <OPTION value=30>30</OPTION> <OPTION
67
value=31>31</OPTION></SELECT> <SELECT class=nicefield name="db3"><OPTION value=0 selected>YYYY</OPTION> <option value="2011">2011</option> </SELECT> Enter your comments in the space provided below: <dl> <dd><textarea name="Comments" rows="5" cols="42"></textarea> </dd> </dl> Tell us how to get in touch with you: <dl> <dd> <table id="table4"> <tr> <td> Name </td> <td><input maxLength="256" size="35" name="Username"></td> </tr> <tr> <td> Login Id </td> <td>
68
<input title="Your Google Toolbar can fill this in for you. Select AutoFill" style="BACKGROUND-COLOR: #ffffa0" maxLength="256" size="35" name="id"></td> </tr> <tr> <td> phone</td> <td><input maxLength="256" size="35" name="phone"></td> </tr> <tr> <td> email</td> <td><input maxLength="256" size="35" name="fax"></td> </tr> </table> </dd> </dl> <dl> <dd> </dd> </dl> <input type="submit" value="Submit Comments"> <input type="reset" value="Clear Form"> </form> 
<table border="0" cellpadding="0" cellspacing="0" style="bordercollapse: collapse; position: absolute; left: 632; top: 165" bordercolor="#111111" width="227" id="AutoNumber1" height="200"> <tr> <td width="227" style="position: absolute; ">
69
<img border="0" src="images/image001.png" width="228" height="261"></td> </tr> </table> </blockquote> </td> </tr> </table>
</body> </html>
INVALID PASS.JSP
70
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>CLOUD COMPUTING</title> <base target="_self"> </head> <body topmargin="0" bgcolor="#FFFFFF" > <table border="3" width="895" bordercolorlight="#CACAFF" bordercolordark="#000080" bgcolor="#DDDDFF" height="600" cellspacing="0" style="position: absolute; border-collapse: collapse; left:10; top:19" bordercolor="#111111" cellpadding="0"> <tr> <td width="1000" valign="top" height="450"> <blockquote> & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; <MARQUEE bgcolor="#DDDDFF">WELCOME TO CLOUD COMPUTING</MARQUEE> > 
 Invalid User Password : &nbsp ;
71
 &nbsp ; &n bsp; &nbsp ; <a Target="main" href="Login.htm"> Click me To Try Again </a> 
<table border="0" cellpadding="0" cellspacing="0" style="bordercollapse: collapse; position: absolute; left: 632; top: 165" bordercolor="#111111" width="227" id="AutoNumber1" height="200"> <tr> <td width="227" style="position: absolute; "> <img border="0" src="images/image001.png" width="228" height="261"></td> </tr> </table> </blockquote> </td> </tr> </table> </body> </html>
INVALID USER.HTML
72
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="Content-Language" content="en-us"> <title>CLOUD COMPUTING</title> <base target="_self"> </head> <body topmargin="0" bgcolor="#FFFFFF" > <table border="3" width="895" bordercolorlight="#CACAFF" bordercolordark="#000080" bgcolor="#DDDDFF" height="600" cellspacing="0" style="position: absolute; border-collapse: collapse; left:10; top:19" bordercolor="#111111" cellpadding="0"> <tr> <td width="1000" valign="top" height="450"> <blockquote> & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; &nbs p; & nbsp; WELCOME TO COMPUTING</MARQUEE> <MARQUEE CLOUD
> > 
 Invalid User Login : &nbsp ; 
73
 &nbsp ; &n bsp; &nbsp ; <a Target="main" href="Login.htm"> Click me To Try Again </a> 
<table border="0" cellpadding="0" cellspacing="0" style="bordercollapse: collapse; position: absolute; left: 632; top: 165" bordercolor="#111111" width="227" id="AutoNumber1" height="200"> <tr> <td width="227" style="position: absolute; "> <img border="0" src="images/image001.png" width="228" height="261"></td> </tr> </table> </blockquote> </td> </tr> </table> </body> </html>
CHAPTER 7 TESTING
One of the main requirements of the software development is to develop bug free, reliable system. During the process of development of any application there is always
74
a possibility of some errors being developed. And also the software may not be as user asked for. Thus, it becomes imperative that, the software should be checked at every step. This helps in a bug free reliable system. If there is any bug or alterations that have to be made that can be done at the preliminarily level as the application gets more complicated after every step. The objective of the testing is to discover bugs and malfunctioning of the application. To fulfill the objective, a series of test steps such as Unit testing, Validation testing, system testing were planned and executed. Testing objective includes: Testing is a process of executing a program with the intent of finding an error. A good test case is one that has a high probability of finding an undiscovered error. A successful test is one that uncovers an undiscovered error.
Various testing approaches Following are main types of tests software undergoes:
7.1 BLACK BOX TESTING

Black box testing relates to tests that are performed at the software interface. Although they are designed to identify errors, black box tests are used to demonstrate that software functions are operational; that inputs are correctly accepted and the output is correctly produced.
7.2 WHITE BOX TESTING

White box testing is test case design approach that employs the control architecture of the procedural design to produce test cases. Test case can be derived such that they:
75
Guarantee that all independent paths within a module have been exercised at least once Exercise all logical decisions on their true and false sides, Execute all loops at their boundaries and within their operational bounds and Exercise internal data structures to ensure their validity.
7.3 UNIT TESTING

This test focuses verification effort on the small unit of design module. Here using test plans prepared in design descriptions as guide, important control paths are tested to uncover errors within boundary of the module. Boundary condition are tested to ensure module operate properly at boundaries established to limit or restrict processing. All paths in the control structure are exercised to ensure all statements in a module are executed at least once and finally all errors handling paths are tested to see message are intelligent. Corresponds to errors, encountered and provide enough description for the cause of error.
7.4 INTEGRATION TESTING

The focus of the test here is on, the design and construction of software architecture. This is a systematic technique for construction the program structure and conducting tests to uncover errors associated with interfacing. The objective here is to take unit tested module and build a program that is dictated by signs. All fractions are integrated successfully after successful completion of development and unit testing.
7.5 VALIDATION TESTING

At the culmination of integration testing, software is completed assembled as a package, interfacing errors have been uncovered and corrected and a final series of software testing, validation test begins.
76
Validation succeeds when the software functions in manner that can be reasonably expected by the customer. Software validation is achieved through a series of black box tests that demonstrates the conformity of the requirements. After validation testing have been conducted one of the two possibility exits. The performance characteristic confers to specification and acceptance. A deviation from specification is uncovered and deficiency list is created. Deviation or errors discovered at the step in this system with the help of the user by negotiating to establish a meeting for resolving differences.
7.6 OUTPUT TESTING

After performing the validation testing, the next step is output testing of the proposed system, since system be useful if it does not produce the required output in the required format. Hence the output format is considered in two ways: one is on the screen and another is the printed format. Both need to be shown to the user for his comments.
7.7 USER ACCEPTANCE TESTING

User acceptance of a system is the key factor for the success of any system. This is done with regard to following points: Input screen design. Output screen design. On-line guide to the user. Menu driven system. Format of output, both on the screen and on the hard copy.
7.8 IMPLEMENTATION OF TEST CASES

Test Case1: Login Form: Valid User name and Password
77
Input=Login Id, Password Output: Corresponding Form Show Implementation of Test Case: User Enters valid User name and Password (administrator, User).Login Values are mapped in database table to check login id and password is ok. If entry exit then Login process will be successful.
Test Case 2: SWrong user Id and Password: Input :Wrong Login Id and Password: Output: Error Message generated Implementation of Test Case: User enters wrong user name and Password. Error message will be shown to show the corresponding message. Test Case3: Availablity: Automatic generation of Job ID Input: Enters the details Output: Automatic generation of Job ID Implementation of Test case: User enters the details and customer id is automatically generated from the back end .User cannot able to make any modification in the Customer ID . Customer ID text box is disable at run time and user can only view the Customer ID
78
A job id will de generated after successful registration of service.
CHAPTER 8 SYSTEM IMPLEMENTATION

A crucial phase in the system life cycle is the successful implementation of the new system design. Implementation simply means converting a new system design into operation. In system implementation, user training is crucial for minimizing resistance to addict to the new system. Training aides, such as user-friendly manuals, a data dictionary, and help information should be provided.
79
The implementation phase is less creative than design. It is primarily concerned with user training, site preparation, and file conversion. When the candidate system is linked to terminals or remote sites, the telecommunications network and tests of the network along with the system are also included under implementation. Implementation is used here to mean the process of converting a new or a revised system design into an operational one. Our situation is the implementation of a computer system to replace an existing manual system. This involves several steps: System Installation User training
8.1 INSTALLATION GUIDE

Register for www domain name. Establish 2 MBPS leased line foe net connectivity. Install Oracle 8 as back end. Create admin account in database. Create admin data source name in the server Export the data base table to the oracle database. Start the Web server process. Host the design site to the server.
8.2 USER TRAINING

The analysis of user training focuses on two factors: user capabilities and the nature of the system being installed. Users range from nave to the highly sophisticated. Developmental research provides interesting insights into how nave computer users
80
think about their first exposure to a new system. They approach it as a concrete learners, learning how to use system without trying to understand which abstract principle determine which function. The distinction between formal and concrete learning says much about what one can expect from trainees in general. The training aids we used to train the staff of the organization are listed below: . The user manual. . Help screens. . Data dictionary. . Job aids
8.3 TOP-DOWN IMPLEMENTATION

Top down implementation begins with the user invoked module and works toward the modules that do not call any other modules. The implementation may proceed depthfirst or breadth-first.
8.4 BOTTOM- UP IMPLEMENTATION

Implementation begins with modules that do not call any other modules and workds toward the main program. Test harnesses (see below) are used to test individual modules. The main module constitutes the final test harness.
8.5 STUBS
Stub programming is the impementation analogue of top-down and stepwise refinement. It supports incremental program development by allowing for error and
81
improvement. A stub program is a stripped-down, skeleton version of a final program. It doesn't implement details of the algorithm or fulfill all the job requirements. However, it does contain rough versions of all subprograms and their parameter lists. Furthermore, it can be compiled and run. Extensive use of procedures and parameter are the difference between stub programs and prototypes. Quick and dirty prototypes should be improved--they should be rewritten. A stub program helps demostrates that a program's structure is plausible. Its procedures and functions are unsophisticated versions of their final forms, but they allow limited use of the entire program. In particular, it may work for a limited data set. Often the high-level procedures are ready to call lower-level code, even if the more detailed subprograms haven't even been written. Such sections of code are commented out. The comment brackets can be moved, call by call, as the underlying procedures are actually written.
8.6 INCREMENTAL PROGRAM DEVELOPMENT

As program become more complex, changes have a tendency to introduce unexpected effects. Incremental programming tries to isolate the effects of changes. We add new features in preference to adding new functions, and add new function rather than writing new programs. The program implementation model becomes: ------ define types/compile/fix; ------ add load and dump functions/compile/test; ------ add first processing function/compile/test/fix; ------ add features/compile/test/fix; ------ add second processing function/compile/test/fix; ------ keep adding features/and compiling/and testing/ and fixing.
82
CHAPTER 9 SECURITY SYSTEM MEASURES

Because Web applications are available via network access, it is highly important to provide tight security mechanism to the concern applications. In this application, in order to protect sensitive content, provide security to every level and provide secure modes of data transmission, strong security measures are implemented throughout the infrastructure that support outside and within the application itself. Every new customer has provided a customer ID. Before login, each customer must enter the correct ID and password, which prevent unauthorized access. As far as internal security is concern, each employee has provided an employee ID. In order to access
83
data from the database, each employee must enter the correct ID and password, which prevent unauthorized access of internal data. Apart from the database level security, there must be an application level security. Therefore, it is envisaged to provide application level security as per the recommendation. To server the purpose, the level architecture of security is suggested keeping in mind the following types of users: Administration level This type of the user will be the super user of the application The Human resource System can have the power to perform every type of operation provided in the system. He/She will derive the power from the application to create new user, drop the existing user and change the permission of a particular user. Intermediate level This type of user will be explicitly created by super user of the application and will be provided certain types of permission like: Generation of reports Editing portion of data with the consult of super user. Analysis of data Printing report.
Operator level This type of user will also be created by super users with the permission of only feeding data into the system. It has no other permission available at their end. Although, it is possible that wrong set of records may entered by the operator. Therefore, to solve this problem, two types of techniques may be used. If the operator thinks that some of record entered are erroneous. He may pass information to the super user about the erroneous records and the administration will take care of those records. Customer Level This type of user will be created by themselves but they have the permission of only feeding data about their personal information and regarding their required service. It
84
has no other permission available at their end. Moreover they also have the permissiom to check the status of their service. They can not interact with the internal database of the company.
CHAPTER 10 INPUT/OUTPUT SCREEN
85
Fig.10.1 (CLOUD COMPUTING HOME PAGE)
Fig.10.2 (COMPANY PROFILE PAGE)
Fig 10.3 (CLIENT LOGIN PAGE)

86
Fig.10.4 (CLIENT HOMEPAGE)
87
Fig 10.5 (CLIENT LOGOUT PAGE)
Fig 10.6 (ADMIN LOGIN PAGE)
88
Fig 10.7 (ADMIN HOME PAGE)
89
CHAPTER 11 CONCLUSION
In my view, there are some strong technical security arguments in favour of Cloud Computing - assuming we can find ways to manage the risks. With this new paradigm come challenges and opportunities. The challenges are getting plenty of attention Im regularly afforded the opportunity to comment on them, plus obviously I cover them on this blog. However, lets not lose sight of the potential upside. Some benefits depend on the Cloud service used and therefore do not apply across the board. For example; I see no solid forensic benefits with SaaS. Also, for space reasons, Im purposely not including the flip side to these benefits, however if you read this blog regularly you should recognise some. We believe the Cloud offers Small and Medium Businesses major potential security benefits. Frequently SMBs struggle with limited or non-existent in-house INFOSEC resources and budgets. The caveat is that the Cloud market is still very new - security offerings are somewhat foggy - making selection tricky. Clearly, not all Cloud providers will offer the same security. Increases business responsiveness Accelerates creation of new services via rapid prototyping capabilities Reduces acquisition complexity via service oriented approach Uses IT resources efficiently via sharing and higher system utilization Reduces energy consumption Handles new and emerging workloads Scales to extreme workloads quickly and easily Simplifies IT management
90
Chapter 12 FUTURE SCOPE

1.This software can be easily upgraded in the future. And also include many more features for existing system. 2. It is connected with the network for easily retrieved data and many location or many districts or cities in different states. 3. All the information can be easily accessed the Customer like their details, service status, product, job allocation etc. It can be modify and the others details can be easily provided to customer. 4. Report on the different basis will be easily created on the demand.
12.1 FURTHER ENHANCEMENT

1. It can be further enhanced to handle much wider range of customers. 2. It can be further enhanced to give more information and facility to Customer. 3. Rate of services to the Developers can be updated dynamically.
REFERENCES
91
1. JavaScript by Wrox Publication 2. HTML in 24 Hours by Techmedia. 3. Core Java By Complete Reference -"Herbert Shieldt". 4. J2EE1.3 by Complete Reference -"Jim Keogh". 5. Head First Java servlet and JSP-"O'Reilly". 6. Software Engineering by "Roger S. Pressman". 7. Fundamental of database -"Elmasrt and Navathe,Pearson Education Inc".
92

Cloud

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Cloud

Transféré par

Droits d'auteur :

Formats disponibles

CHAPTER - 1 INTRODUCTION

1.1 PROBLEM STATEMENT

1.2 OBJECTIVE OF THE PROJECT

1.3 FEATURES OF THE APPLICATION

1.4 ADVANTAGES OF THE SYSTEM

1.5 OPTIONAL FEATURES

CHAPTER 2 FEASIBILITY STUDY

2.1 PRELIMINARY INVESTIGATION

2.2 ADVANTAGES OF PROPOSED SYSTEM

2.3 PROJECT FEASIBILITY

2.4 OPERATIONAL FEASIBILITY

2.5 TECHNICAL FEASIBILITY

2.6 ECONOMIC FEASIBILITY

2.7 SOFTWARE ENGINEERING PARADIGM APPLIED

CHAPTER 3 PROJECT PLANNING

3.1 GANTT CHART

Feb & Mar 12 17 23

Feb & Mar 5 18

Fig 3.1(GANTT CHART)

3.2 PERT CHART

Performance Study, Final Documentation and Maintenance

Coding Of Individual Modules

Designing of login page

FIG 3.2(PERT CHART)

4.1 Software Requirement

4.2 Hardware Requirement

Server Side (Minimum):-

CHAPTER 5 SYSTEM DESIGN

5.1 MODULARIZATION DETAILS

5.2 Data Flow Diagram

5.3 Entity-Relationship (ER) Diagram

Update Project Information

Generate Reports Maintain Project Details 18

View all Details

View Project Status

Login Maintain User Account

Fig 5.1 (USE CASE SURVEY MODEL)

Managem Managem ent ent 19 Authenticati Authenticati on on

Updating Updating Validation Validation

Login New Client/Vendor

info info info

Time Sheet Management

info Project Queue info

Context Level DFD

Fig 5.3 (CONTEXT LEVEL DFD)

Nam e Addr ess Id Client/Ven dor Industry type Nam e

Design ation Code Categ ory

Develop ment Id Project

Date Statu s Payment

Fig 5.4(ER DIAGRAM)

5.4 DATABASE DESIGN:

l_id M_password Login_type Reg_date

VARCHAR VARCHAR VARCHAR DATETIME

Table 5.2 (Login Table)

PRIMARY KEY NOT NULL

Table 5.3 (Administrator Table)

PRIMARY KEY NOT NULL

Table 5.4(Employer Table)

Dev_ID D_ID FirstName MiddleName LastName cellno Email AddressLine1

NUMBER VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR 24

PRIMARY KEY NOT NULL

AddressLine2 City State Country

VARCHAR VARCHAR VARCHAR VARCHAR

Table 5.5(Jobseeker Table)