You are here: UK Essays » Essays » Information Technology » Daffodil Software Ltd

Daffodil Software Ltd.

Preface

Software has become the key element in the evaluation of computer based systems and products. Over the past four decades, software has evolved from a specialized problem solving and information analysis tool to an industry area. Information processing is the largest single software application area. The software development process involves the skills and experience of the people involved.

Industrial training explores a student to an individual treasure of experience and offers an exposure to real time management in an organization. It is a period during which a student is introduced and familiarized to the industrial environment. With the advancement in computer technologies and increased automation, the software industry has become all the more important. The introduction of computers and electronics in the field of processing has made it essential that the inputs be much more accurate and the controllers must faster in response. The state-of-art used in all the processes manually, thus ensuring improved operating efficiency and full protection.

Industrial training is a major part of theoretical studies as it covers all that remains uncovered in the classroom; that is, without it, the studies remain ineffective and incomplete. The objective of training is to raise the level of performance of the students in one or more of its aspects. This may be achieved by providing new knowledge and information relevant to a job, by teaching new trends, by imbuing an individual with new attitudes, motives, coordinates, cooperation and other personality characteristics. Often these technologies are utilized with segments of the work force regardless of the existing performance level to operate efficiently.

Since gaining theoretical knowledge is just not sufficient for sure success in life, especially in an ever-growing industry, like this, practical training plays a very important role in building the future of an individual.

IT Policy

Introduction:

1. Excise and Taxation Department - The implementation of the taxation system prevailing in the UT shall be modified in accordance with the increasing usage of I.T. Online connectivity shall enable simplified procedures for levying of commercial taxes. This shall eliminate delays and bottlenecks in the taxation procedures. A database of registered dealers shall be maintained. Issuance of licenses (ST No. shall be computerized and STV registers (Both CHA and CST) shall be automatically updated. Automatic generation of notices, defaulters and pending payments shall be possible.
2. Education Department - All colleges and schools shall be fully computerized and all students shall be encouraged to be I.T. literate. The Education department shall be connected online with all educational institutions including Medical and Engineering colleges. A data bank of students who are I.T. literate shall be maintained and a tie-up with industry for employment shall be ensured. More courses will be introduced in all institutions to produce I.T. Professionals.
3. Municipal Corporation - The residents of Chandigarh shall benefit from the introduction of the I.T. culture in the Municipal Corporation of Chandigarh. All services provided by the Corporation shall be computerized and residents shall be able to access the various departments of the corporation online from the kiosks, which shall be set up throughout the UT. Public grievances shall be given priority and shall be resolved speedily by the use of computers and interconnectivity. Mapping of the whole area of the UT shall be done and co-ordination between the various departments shall be ensured to prevent repeated inconvenience to the public as and when digging or construction activities are carried out.

Estate Office - For the benefit of the residents of Chandigarh, the Estate office shall provide information to all residents via terminals, which shall be set up throughout the UT. Procedures shall be simplified through the use of computers and interconnectivity. Various forms and instructions shall be available online to the general public. All the files of the Estate office shall be computerized and information from them as per requirement shall be made available to the public, while keeping in view the necessity for keeping certain documents confidential.

Driving Licenses and Registration - All driving licenses and Registration certificates shall be computerized and procedures for issuance of new licenses and registration certificates and also for their renewal shall be made convenient for the public through online connectivity. Delays shall be totally eliminated and an effort shall be made to provide these documents the same day as the application is made. Smart Cards shall be introduced for registration certificates and driving licenses.

4. Treasury - The government treasury shall be computerized and connected online with the UT secretariat and other important offices. All bills and other documents shall be computerized and manual processes shall be minimized. Necessary security checks shall be carried out and a foolproof system shall be introduced.

Chapter I - Case Study

• Introduction to Portal
• Study of Existing System
• Features of Proposed System

INTRODUCTION TO PROJECT:

Portal is a web enabled system that allows the peoples with in the organization and outside it to access information as per their requirements i.e. It aims at providing various services to public and employees with in the organization.

This Project is divided into two modules:

MODULE 1(STATIC MODULE):

This module is further divided into sub modules. Each sub module further consists of sub modules each of which provides certain information related to it.

The various sub modules included in this module are given below:

• Integrated Scheme & Budget Monitoring System:
• Personal Desktop Assistant:

Study of Existing System

DISADVANTAGES OF EXISTING SYSTEM

• NO INFORMATION FOR THE CITIZENS ON THE WEB
• CITIZENS HAVE TO PHYSICALLY LOCATE THE DEPARTMENT FOR COLLECTING INFORMATION REGARDING THEIR WORK.
• SUFFERS FROM DISADVANTAGES OF USING PAPER FILES
• CITIZEN - ADMINISTRATION INTERACTION IS DIFFICULT
• COMMUNICATION PERTAINING TO TENDERS,QUOTATIONS AND NOTIFICATIONS WAS ONLY THROUGH NEWSPAPERS

Features of Proposed System

VARIOUS FEATURES OF PROPOSED SYSTEM ARE:

• MAKE A WEB ENABLED SYSTEM FREE FROM DISADVANTAGES OF MANUAL SYSTEM
• SHOULD PROVIDE RELEVENT INFORMATION TO GENERAL PUBLIC
• SHOULD BE DYNAMIC
• SHOULD BE USER FRIENDLY

Chapter II - System Requirements

• Product Definition
• Feasibility Study: Economic, Technical & Operational
• Project Plan
• Development Schedule

The software requirement specifications document includes the requirement definition and the requirement specification.

System Requirements

PRODUCT DEFINITION

Software requirements are expressed in a software requirement document. The software requirement document (also called SRS) is the official statement of what is required by system developers. This requirements document includes the requirement definition and the requirement specification. In some cases, these may not be presented separately but integrated into a single description. Sometimes the requirements definition is the most effective approach to present the detailed specification as an appendix The objective is to make a web enabled system, which should provide citizens the facility to gather information by sitting at there home. The requirement is to build a portal, which should provide all the information to the general public and employees with in the organization. Also the web-enabled system will no longer suffer from the disadvantages of the manual system. The new system will be dynamic as it will get the information from database and the pages will no longer be hard coded. The requirement is to build a portal that contains a lot of information so that the citizens and employees with in the organization will be able to access varied information as per their requirement. The portal is required to give the citizens the facility to access the information for which, otherwise, they would have to go to the different offices, which may be located at different locations. Thus accessing the required information becomes very convenient for the general public. They may just sit at their homes and access the information by simply connecting to the Internet.

APPROACH/SOLUTION STRATEGY

This project was developed by following the principles of software engineering passing through the various phases of the System Development Life Cycle (SDLC) methodically to answer the key questions and to achieve results in each stage. The various phases that the system passed through were:

Requirement Analysis

• Planning
• Analysis
• Design
• Implementation

PROBLEM ANALYSIS

If the company does not have a dynamic web site for the citizens. There is no information for the citizens on the web. So for getting any information regarding any aspect the citizens have to go to the office of the concerned department. It is very inconvenient for the citizens. The employees of the company have to do a lot of the manual work. They have to maintain the records physically in the files and have to update these records by searching through all the records. So they have to physically do a lot of work. Also the maintenance of the records is a difficult job. There are many other problems faced by these old file systems which are listed below:

• Data Redundancy

A record regarding a particular employee may be maintained more than once. For instance, if an Executive Engineer is in charge of a more than one department his record will be maintained in both the departments. So the same data is maintained more than once.

• No control over unauthorized access

The files are stored on normal shelves and any person can pick up the files and modify its contents. This can become dangerous for confidential information.

• No protection against accidental loss of data

The data cannot be protected against accidents like fire and flooding. It is only possible if proper backup is kept and is stored at a different physical location.

• Difficult to recover data once lost

Once the data is lost, it is almost impossible to recover it because no back up is being maintained.

• Loss of data consistency

If a record relating to a particular entity is maintained more than once than data inconsistency occurs as data needs to be updated at more than one place. If a person forgets to update the data at all the places regarding a particular entity then the data will become inconsistent.

• Difficulty in searching within records

For searching any particular records multiple files have to be manually searched which is a time consuming job.

• More data security is required.

Also nowadays a website for every institute has become a necessity. People have become aware of the advantages of computerized system. So a new web enabled system was proposed. The need was to build a web site, which should provide the citizens with all the required information.

The various tender notices, quotations and notifications pertaining to the departments are communicated to the public only through the various newspapers. As a result a person, who misses reading the newspaper, on the date the notice is published, misses some important information which could have been profitable to him.

For obtaining the application forms for the various tasks such as registering for website, tender forms etc a person is required to visit the concerned office. This is very difficult and time consuming.

To overcome the above-stated shortcomings in the existing system, the need for a new system was felt.

FUNCTIONS TO BE PROVIDED-STATIC

The portal will contain both the static as well as the dynamic contents. The dynamic contents will help the employees within the organization to access the information according to their needs. The static contents will provide the information relating to the following fields:

• Court Case Monitoring System
• File Management System
• Visitor Information System
• Integrated Scheme And Budget Monitoring System
• Personal Desktop Monitoring Assistant
• Rent Controller
• Estate Office Accounting System
• Quotations
• Architect Department
• Notifications

1. Site Details
2. Web Hosting Services of company
3. Website Audit Policy
4. Site Registration Form for company
5. Website Audit Form
6. Disclaimer Form
7. Site Registration Form for gov.in

1. Disclaimer Form
2. Site Audit Form
3. Site Registration Form for company

FUNCTIONS TO BE PROVIDED-DYNAMIC

The dynamic contents to be included in the portal aim at providing ease to the employees with in the organisation. The employees will not have to leave the physical platform for every little task or for getting some information. This module is further divided into smaller modules. The various modules included in this module are:

• Approvals/Orders
• Project Information
• Staff Information
• Website Information

ACCEPTANCE CRITERIA

The developer will make sure that all the information provided on the portal is up to date and all the links provided are connecting the pages along the appropriate route. The developer will also make sure that the dynamic modules are working properly. In the nutshell all the conditions specified in requirements are met.

Processing Requirements h/w & s/w

Hardware Requirements

Processor

Intel Pentium-based (Pentium II, Pentium III or Pentium IV) or other compatible running at 450 MHzOr faster.

RAM

64 MB or more.

Hard Disk Space

2 GB or more.

CD-ROM

A CD-ROM drive is required to install Software

Software Requirements

Operating System

Windows NT Workstation/Server 4.0 with Service Pack 4.0 or higher, Windows 9x/Me, Windows 2000 Professional or Windows 2000 Server, Windows XP(Pro)

Internet Browser

Users require a minimum version of Microsoft Internet Explorer 4.01 with Service Pack 1. This is required for HTML, ASP Code to Work.

Network Software

Depending on the network support that you require you must ensure that the correct network drivers are loaded. Additional network support will not be needed unless you are using Banyan VINES or AppleTalk. Novell IPX / SPX support is provided by NWLink, IPX / SPX.

Database Backend

SQL Server 2000 is used as a database tool for Portal Development.

TECHNICAL FEASIBILITY

As the software is very much economically feasible, then it is really important for it to be technically sound. The software will be build using ASP, Java Script, HTML as front end and SQL Server as back end.

The technique being used is easily available as all the computers have these S/W installed many others are also available. Since it is very interactive language so users will not have difficulty learning and adapting it. Technical experts are also available who can guide the users as and when required.

OPERATIONAL FEASIBILITY

The project is operationally feasible as users are already using computers and are aware of various S/W implementations, thus instead of being reluctant to use the new system they will learn it very quickly.

Project Plan

The project plan sets out the resources available to project, the work breakdown and a schedule for carrying out the work. In some organizations the project plan is a single document including all different types of plan. In other cases the project plan is solely concerned with development process .The details of the project plan vary depending upon the type of project and organization. Most plans should include the following sections:

• Introduction
• Project organization
• Risk analysis
• Hardware and software resources requirements
• Work breakdown
• Project schedule
• Monitoring and reporting mechanisms

Web planning is a dynamic, continuous process that involves a constant balancing of opportunities and resources. Web planning often takes place within a context that is more general than just the concerns about the technical composition of a set of HTML pages. Planning is a crucial aspect of web development because it is when many decisions are made that affect the design, implementation, and later promotion of a web. The Web's dynamic characteristic tends to make planning an ongoing, continuous process in which issues of multiple authorship and rapidly changing information relationships come into play.

Project Management Plan

Project management plan Includes

PERT CHART

PERT is a program evaluation and review technique. It tells about the running of the project and its current status. This includes activities, their estimated times of completion and actual time that they took .It is simply a pictorial representation of the various activities carried out during the project.

PROGRAMING LANGUAGE AND DEVELOPMENT TOOLS

PLATFORM USED:

Windows XP Professional

The tools used for the development of the portal are:

FRONT END:

• HTML (Hyper Text Markup Language),
• ASP (Active Server Pages)
• JavaScript
• CSS (Cascading Style Sheets)
• DHTML

BACK END:

SQL-Server 2000

Chapter III - Software Requirement

Specifications

• Purpose
• Planning
• Software Requirement Analysis

The software requirement specifications document includes the requirement definition and the requirement specification.

System Requirement Specification Document

WHY IS IT NEEDED

Software requirements are expressed in a software requirement document. The software requirement document (also called SRS) is the official statement of what is required by system developers. This requirements document includes the requirement definition and the requirement specification. In some cases, these may not be presented separately but integrated into a single description. Sometimes the requirements definition is the most effective approach to present the detailed specification as an appendix to the requirement definition or presented in separate volumes.

The software requirement document is not a design document. It should set out what the system should do without specifying how it should be done. The requirement should be stated so that it is possible to take each specified requirement and map it into the part of the system design that implements that requirement.

Software Requirement Planning

Web planning is a dynamic, continuous process that involves a constant balancing of opportunities and resources. Web planning often takes place within a context that is more general than just the concerns about the technical composition of a set of HTML pages. Planning is a crucial aspect of web development because it is when many decisions are made that affect the design, implementation, and later promotion of a web. The Web's dynamic characteristic tends to make planning an ongoing, continuous process in which issues of multiple authorship and rapidly changing information relationships come into play.

SYSTEM PLANNING

The first step in web systems planning was to explore how the Web could play a role in an organization's communications needs. The Web does not need to replicate or replace all of these existing communications methods; instead, it should enhance, supplement, or replace only some of them. After a role is defined for what communication tasks an organizational web or set of webs might fill, the next step in web systems design is integrating the web or webs into the existing organizational communication infrastructure. The key was that a plan for web systems integration should link the elements in web development to existing organizational communication flows. After definition and integration, the next step was differentiation. A system of webs might, at first, simply replicate or supplement other activities. These webs must provide value over these other forms, however, or an organization should discontinue the web activity. This is a process of differentiation, in which communication tasks are best left to the media that most satisfactorily serve those tasks. Instead of promoting a system of webs as the solution to all of an organization's needs, only those communication tasks that seem best suited to the web should be planned or continued.

When developing a web and making it available to the public to freely browse, a range of factors cannot be controlled. The first step of the planning process was to recognize these factors and consider how they might limit planning for the portal. These factors include user behavior, browser display, links to the web, and the resources outside the web.

USER BEHAVIOUR

Because the Web is a dynamic, competitive system based on user choices and selectivity, it is difficult to control how users are going to access and use a web's information. The web's porous quality, in particular, means that users do not need to enter a web from a designated home page; instead, they can enter from any arbitrary page. There is the need to guide users down a series of pages

USER BROWSER'S DISPLAY

The client/server organization of the Web allows for a wide variety of browsers to be available to users. As a web planner, we can't know what kind of browsers users will have. Moreover, new browsers are in development, and future browsers are certain to provide more and different features than the ones presently available. Therefore, different users, based on their browser's operation, will experience a web differently but share common navigational needs. Some users might perceive a web using a text-only browser, whereas others might use the most current graphical browser that supports extensions to HTML. Therefore, in planning the portal, it was considered what information would be essential so that it will not be lost to users who have text-only browsers or browsers that don't support HTML extensions. If some essential information is placed in a graphics file, for example, some users might never see it, because not all Web browsers support graphics. So an alternative to this must be provided. The essential information should be placed as:

All essential information should be placed in text (or in the ALT fields of images in a document) so that a user with any browser can access it.

Important communications functions should be placed within forms.

LINKS INTO AND OUT OF A WEB

In a web, many links might be made to resources on the network that are beyond a web developer's control. These resources may move, making the link no longer valid (the link then is said to be stale). Users following a stale link from a document will encounter an error message and not get the information the developer originally had intended for them to access, thus degrading the experience of the users of the web. Any of the following strategies can be followed to overcome this problem.

This is the most stringent option. It states that no links will be made from the web to resources that are not under the direct control of the web developers. The benefit of this policy is that there is absolute control over the resources that are the destination points of the links in a web.

In this option, a core group of web pages that are separated from outside links by a layer of local web pages of a minimum depth is designated. It was made sure that there are no outside links closer than three links away from the home page of the web. In this case, the home page constitutes the core set of pages, and there are at least three links between a page within this core set and a link outside the web.

In this option, a single page or set of pages may be designated to contain all the links outside the web. A common practice for webs is to include a page containing interesting external links of this type, listing Web links to external resources on a single page. The benefit of this strategy is that users can have a good idea when they will be leaving the local web. This helps users who arrived at the web for a specific purpose to avoid getting "thrown out" of the web before finding the information they want.

In this option, no restrictions are placed on making links outside the web. This approach allows the particular page developer to determine when outside links should be made. This is the most flexible option, but it might send users out of a web quickly.

POROUS QUALITY

This quality of the Web works in favor of a design in which information structures are modular and self-contained, and that contain a sufficient number of navigation and context cues for the user. These kinds of information structures, whether they are individual pages or groups of related pages (a package), can have multiple uses for different places in the same web or for different webs of the same organization. These multiple-use information components reduce production and maintenance costs, because information creation and updates can take place in a single location within a web, and the updates can benefit all the links where this information is referenced.

DYNAMIC QUALITY

This quality of the Web works in favor of a design in which key parts of a web meet the users' time-dependent needs. A news organization creating a web for mass communications can have a page that contains the current headlines, which are updated throughout the day, for example. A user accessing this page can expect to see different contents from day to day and even throughout a single day, or over several hours or minutes. This dynamism works in favor of meeting the needs of the users for current information. In contrast, poor planning for information updates results in out-of-date information on a web, and the dynamic possibilities are lost. The level of dynamism on a web depends on what kind of information a web offers. Stable information might require no updating. Other information might be valid for periods of time-perhaps years or months-and might require only periodic updating.

INTERACTIVE QUALITY

This quality of the Web can engage users and provides a way to customize information to meet users' needs. Planning for interactivity involves a careful process of audience identification and analysis in which these needs and the mechanisms by which they can be met are defined.

ADMINISTRATIVE PLANNING

An important part of developing a web involves considering how we want to create our presence on-line.

This presence should include a domain name (to permit switching of Internet service providers when necessary as well as for identity reasons) and adequate Web server performance.

When developing a web, we're not just making a home page. Our goal should be to develop sustainable, reliable processes that continuously improve the content of your site. The Web, like life, is always under construction. Our goal is to take steps to the excellence of the content of your construction. Our users then will begin to rely on you to always do better in the flux of Web communication.

WEB ELEMENT PLANNING

The planning techniques described here address particular aspects of each of the web-development elements: Employees information, purpose statement, objective statement, domain information, web specification, and web presentation.

It is extremely important that we know who is going to use the portal. This will enable us to put meaningful information that is useful for that set of people. In the case of the portal being developed, the target audience is the general public and employees of the organisation.

The definition of critical information depends largely on the purpose statement for the web. For some purposes and some audiences, different information is important.

PURPOSE STATEMENT

The statement of purpose serves as the driving theme throughout web development. To define the portal's purpose, the following elements were considered:

• The subject area
• The audience
• The level of detail at which information is presented
• The user's expected benefit or response

OBJECTIVE STATEMENT

After the purpose of the web is planned, the audience is determined; the next step is to combine all this information to arrive at a specific statement of web objectives.

The portal will contain both the static as well as the dynamic contents. The dynamic contents will help the employees to access the information according to their queries. The static contents will provide the information relating to the following fields:

The dynamic contents to be included in the portal aim at providing ease to the employees with in the organisation. The employees will not have to leave the physical platform for every little task or for getting some information. This module is further divided into smaller modules. The various modules included in this module are:

• Approvals/Orders
• Rate Contracts
• Project Information
• Staff Information
• Website Information

DOMAIN INFORMATION

Domain information refers to information and knowledge about the subject area of the web, including both on-line and off-line sources of information. Domain information includes not only information that will be presented to users of the web, but also all information and knowledge that is required to develop the system. Therefore, the collection of domain information serves as an "information store" from which both the developers and users of the web will draw. The purpose of the web itself might be to provide an interface to this information store. Planning for domain information is essential.

It is essential to define what domain information is necessary for the development and what information will be provided to users. Are there specialized databases to which developers or users must gain access? Is there an existing store of on-line material that will serve as a basis for user information? In the case of NIC there does exist server based database or the online material which can be used. So the database is not to be designed and build up.

However in NIC there is a paper-based information source. So the requirement is to read through the files to get the required information.

It's not enough to define and acquire a database. If it is time-dependent information, when will it lose its usefulness? How will it be updated? Who will update the information? What will be the costs of this updating and maintenance? It has been planned to provide the provision for the administrator's to login and update the database according to the required needs.

WEB SPECIFICATION

The web specification is a refinement of the objective statement in more specific terms, adding a layer of constraints or other requirements. These requirements restrict or further describe in detail what the web will offer and how it will be presented. The specification statement also characterizes limitations on the information and its presentation. The specification acts as a guidebook for the creation of the actual files of the web itself.

Constraints on Portal:

• Only the administrator can make any changes to the database.
• The information that is subject to periodic change should be picked up from the database
• The database should be periodically updated.
• Link to the home page should be provided on the each page.
• The essential information should always be available irrespective of the browser type used.

WEB PRESENTATION

Although the audience definition, purpose and objective statements, and domain information are most closely associated with the planning process of developing a web, the development of a web's presentation also must be planned. The web's presentation is the whole look and feel of the web, along with its actual implementation. Planning for web presentation involves verifying that resources that comprise the Web are and will be available to support the files on the server. Allocating space and setting any special file or directory permissions were planned so that the web presentation can be implemented.

Need for the web's presentation was anticipated by doing the following:

• Generating a set of possibilities for web presentation based on current or possible specifications. These possibilities included sample HTML pages, graphical image maps and forms to help the user interact with the information.
• Planning the work schedule necessary to implement the web according to specifications, including how much time it will take to implement and test web pages, verifying links, and implementing changes based on new specifications.
• Creating and maintaining a pool of generic web components.
• Creating a mock-up of the web based on an initial specification.

Software Requirement Analysis

PURPOSE

Analysis is the process of gathering and comparing information about the system and its operation and use in order to improve the overall quality and to identify problem areas.

Portal of any company should be consistent with the following principles:

Because a characteristic of an operating public web is that it is available worldwide, 24 hours a day, an analysis of its content and operation takes into account a multinational, multicultural audience and its needs for continuous access. The portal is being developed for the general public so it must be available all the time and must be accessible easily to the general public.

As networked hypermedia, a web extends and augments its meaning through internal and external links. External links tightly bind a web within larger contexts of communication, culture, and social practice that extend beyond an organization's outlook. The links must contribute to the portal's meaning. Technical analysis of links must ensure their operation and availability to the degree possible.

The Portal must ensure porousness

A web that contains more than one page offers multiple entry points for its users. An analysis of the usefulness of a web must examine how each of these multiple pathways offers a user the right amount and level of information to use the web well.

A web operates in an environment in continual flux in terms of meaning and technologies. Not only are new webs introduced all the time that try to accomplish the same purpose and/or reach the same audience of a given web, but methods for implementing and experiencing webs continually are introduced and upgraded. So the portal must be upgraded periodically.

Because the intended audience of the portal is the general public, it becomes necessary to ensure that the portal presents a comprehendible and user-friendly interface. The portal should not require that its users are technically sound. A person with any background should be able to easily navigate the portal.

The goal is to create a web that works with the characteristics and qualities of networked hypermedia to best accomplish the web's purpose for its audience.

This analysis process covers the technical validation of a web's HTML implementation as well as analysis of the web's planned or existing content and design. This process also touches on usability and style issues. Because of the dynamic information environment in which a web operates, these ongoing efforts to evaluate web quality and usability may be the key to increasing the effectiveness of an organization's Web communication.

The aim is to make sure that the web works:

• Rhetorically: The portal must accomplish its stated purpose and meet its objectives for its intended Users.
• Technically: The portal's presentation should be functionally operational and consistent with its specifications and design as well current HTML practices and syntax.
• Semantically: The portal's domain information content should be correct, relevant, and complete. The portal's user interface must be usable and effective.

INFORMATION ANALYSIS

The portal's technical and rhetorical aspects were evaluated by analyzing the portal's elements - audience information, purpose and objective statements, domain information, web specification, and web presentation and performance - information about how users have used or are expected to use the web. The information about other competitor webs that were accomplishing a similar purpose or reaching a similar audience was gathered and evaluated.

The information content that was required to be put on the portal was collected by studying the various hand-written records and reports generated in the company. The officials employed in the company were interviewed to gather the information about each department that needed to be put on the portal.

The figure below shows an overview of information derived during the process of analysis. In the figure, the web's elements are in rectangles, and supporting or derived information is in ovals. Key checkpoints for analysis are shown in small circles, labeled A through F. At each checkpoint, information about the elements or information derived from the web elements is compared to see whether the web will work effectively.

INFORMATION ANALYSIS

The various checkpoints shown in the diagram are:

One of the most important elements for the integrity of the web is the purpose, objective, and specification triad. These three elements spell out why the web exists and what it offers. The check of the purpose-objective-specification triad is to make sure that something wasn't lost in the translation from the purpose (an overall statement of why the web exists) to the objective statement (a more specific statement of what the web will do) to the web specification (a detailed enumeration of the information on the web and constraints on its presentation). The portal developed fulfills the purpose-objective-specification triad. The purpose of the portal is to provide online information to the general public and so it should have all the features which enable the citizens to get the information they require.

The quality of the domain information affects the users' perceptions of the web's overall quality. Inaccurate or incomplete information leads to dissatisfaction by the web's users. Periodic checks were made to ensure that the domain information was accurate, updated, and complete. Another prospect was to verify the freshness of links. If the web is operational, the links provided in the web must not be stale and the resource should not have moved. It is important to make sure that the data in the databases is as current as they possibly can be.

EXTERNAL INTERFACE REQUIREMENTS:

User interface: The User Click is required to select an option displayed on the index page. He can browse through the entire portal by following the desired links. The dynamic applications are to be displayed in the main menu bar. User is provided with a navigation bar that will contain links to all the related pages.

FUNCTIONAL REQUIREMENTS:

• The portal should provide citizens the facility to gather information by sitting at their home as pet their requirement.
• The various forms pertaining to various departments should be available online.
• All the application forms should be available on portal and can be downloaded so that there is no need for the citizens to go to the various government offices for the forms.
• The portal should provide the employees of the organization the facility to access information any time as per their need, without any inconvenience.

PERFORMANC REQUIREMENTS:

• Online results obtained from the database should be generated in a short time

DESIGN CONSTRAINTS:

Software Constraints:

1. Only the administrator can make any changes to the database.
2. The information that is subject to periodic change should be picked up from the database
3. The database should be periodically updated.
4. Link to the home page should be provided on the each page.

Chapter IV - Software Design

• Objectives
• Web design principles
• Software Model Used
• Design techniques used
• Data Flow Diagram
• Database Tables

System Design

OBJECTIVE

Design is this process by which a web designer, working within the web's specification, makes decisions about how web components will accomplish the web's objectives. The web's purpose and users are taken into account during the design phase. The aim is to find out how to achieve the effects called for in the most flexible, efficient, and elegant way. Thorough grounding in implementation processes and possibilities as well as knowledge about how particular web structures affect an audience is required.

The following points were considered:

• To create a consistent look and feel for the web.
• Information to be separated into manageable page-sized chunks.
• Cues to be provided for the reader about the web's information structure and contents, context, and navigation.
• Links to be used to connect pages along the routes of use and user thinking.

The overall goal is to create a look and feel for the portal that has the right information at the right level of detail and an arrangement of pages that efficiently guides users to needed information. Although a user's positive experience of a web depends on many subjective factors, certain techniques can be used to increase the probability of user satisfaction with a web. The web must balance user needs with trade-offs in performance, aesthetics, and usability. And users differ in their abilities, tastes, and even the Web browser and Internet connection they use, so it is impossible to design a web that perfectly meets all needs for all users. Based on an understanding of the Web's media characteristics and qualities, and using design techniques and an awareness of common design problems, a plan for the web was created to meet the specific user's needs for the particular purpose.

The design process is essentially user centered. A web's design is essentially its look and feel. A good design should take into account all the web elements-audience information, purpose and objective statements, domain information, and web specifications (as shown in the figure)-and combine them to produce a plan for implementing the web.

A successful web requires that all processes and all elements work together. The web design process takes information from all elements of web development and combines them to produce a look-and-feel design that then is used by the implementation process to create a working web. By separating the design from the implementation process, information about the web's structure and operation can be cast in a hypertext, language-independent form. Whereas the design process is influenced by knowledge of what is possible in the target design language, its product can be implemented in any language that can capture the features used in the design. In this way, this design process can be used with successors or alternatives to the widely used Hypertext Markup Language (HTML).

System Design

PRINCIPLES OF WEB DESIGN

Aside from having a set of design methodologies to flexibly draw upon, a set of techniques for packaging, linking, and cueing information is also made. The best way to manipulate the user's experience is by judiciously packaging the information in the right amounts on pages and in sections of pages, linking these pages to support the user's needs, and cueing the user to information and navigation aids.

Based on the media and user-experience principles, the following general principles are kept in mind when creating a design:

Take advantage of the power of hypertext to link related information. Designs can contain links to further context information as well as chunk information.

Because the Web is so competitive, it must be made sure that the designs include the lowest possible costs to the users. User costs include download time, information-retrieval time, and the effort required to use and understand information.

During the design and implementation of a web, features that meet the users' needs with the least amount of space, access time, graphics, and long-term maintenance requirements are selected. Web features that are efficient to operate, elegant to use, and easy to maintain are aimed for.

A web should not be built for the personal taste of the designers, the convenience of the implementers, or the whims of the planners. Instead, the web serves the audience for which it is designed. Meeting the needs of the users is the first priority of the web. Focus should be on user needs by using the purpose statement and audience information to make decisions about page organization and layout.

A web should not be built for the personal taste of the designers, the convenience of the implementers, or the whims of the planners. Instead, the web serves the audience for which it is designed. Meeting the needs of the users is the first priority of the web. Focus should be on user needs by using the purpose statement and audience information to make decisions about page organization and layout.

A web should not be built for the personal taste of the designers, the convenience of the implementers, or the whims of the planners. Instead, the web serves the audience for which it is designed. Meeting the needs of the users is the first priority of the web. Focus should be on user needs by using the purpose statement and audience information to make decisions about page organization and layout.

At the minimum level, users should have a way to contact the web developers for questions or problems with a web. Based on the purpose of the web, there might be greater levels of interactivity, ranging from forms interfaces to computation and gateway programs. These user needs must be met by providing cues (such as an e-mail contact address) about interactive features (for example, identifying the security of forms transactions).

METHODOLOGY & S/W MODEL

When creating the database application, it's important to take structured approach by proper planning. The key steps in creating this application are as follows:

• Designing the database and various data structures.
• Designing the user interface as per user requirements

In analyzing the existing system, we collected a great deal of relatively unstructured data through interviews, forms and manuals. So in order to convert the gathered information into a data flow diagram an approach called structured analysis was followed.

Structured analysis is a set of techniques and graphical tools that allow the analyst to develop a new kind of system specifications that are easily understandable to the user.

We have used data Flow Diagram and data dictionary for logical design of the system. The diagram shows how system specifications were described through DFD and then that DFD is changed to Application program.

BOTTOM UP APPROACH

If web designers don't have a good idea of what the final web will look like, but they know how specific pages will look and work, working from these specific pages to the top page might be the way to proceed. This approach has been followed in the development of the portal.

Design Techniques

Design techniques relate to information-shaping skills to meet users' needs.

PACKAGE INFORMATION

Humans can process only a specific amount of information at a time. A specific task in web design is to package or "chunk" information in pieces that don't overwhelm users. The key idea is to chunk information so that

• Information content control
• The amount of information on any one page should not overwhelm the user or cause long download times for a page.
• Creation of reusable pages.
• If each page accomplishes one specific purpose, it can be a useful link throughout the entire web for that purpose. In this way, a page of information can be flexibly included in as many places as appropriate to the user's needs but be created only once.
• Focus the user's attention.
• The chunks of information, when created around ideas, concepts, and ways of thinking familiar to users, helps users focus on one topic at a time and build their knowledge incrementally.

The portal is mainly divided into two modules. The first module deals with the static contents and the second module deals with the dynamic part. The dynamic contents will help the employees to access the information according to their queries

The first step was to gather the documents that represent the information to be presented in the web. The information that was gathered in analysis phase was organized into chunks during this phase.

LINK PAGES TOGRTHER

The various pages can be linked individually to the home page or a group of pages i.e. the packages can be linked to the homer pages. In the portal being developed there are several pages as well as the packages. Some pages are directly linked to the home page while others are linked through the packages.

OVERALL LOOK AND FEEL OF THE WEB

The look and feel of the home page and contents page was decided at this point. The contents page would be split into three frames: the first frame horizontal - containing the header and the main menu bar; and the second and third vertical - one containing the navigational bar and the other containing the contents. The header will be an image containing the name of the organization and some pictures. The navigational bar will contain links to all related pages.

The home page would not be split into frames. The header for the home page will be the same as that of the contents page. There would be three vertical columns in which the links to the various pages will be arranged.

PLATFORM USED

The tools used for the development of the portal are:

FRONT END:

• HTML (Hyper Text Markup Language),
• ASP (Active Server Pages)
• JavaScript
• CSS (Cascading Style Sheets)
• DHTML

BACK END:

SQL-Server 2000

WEB-WIDE NAVIGATION LINKS

Navigation cues and links help users move through an entire web. The navigation links would be created by making an index page that links to every page of the portal. The concept is to provide a central point for users to locate a page that they know is in the web somewhere but can't remember how to get to it. Also a navigation bar would be made available on all the contents pages to provide easy access to related pages.

MODULE 2-DYNAMIC CONTENTS

The dynamic contents to be included in the portal aim at providing ease to the employees of the organisation. The employees will not have to leave their desks for every little task or for getting some information. This module is further divided into smaller modules. The various modules included in this module are:

• Approvals/Orders
• Project Information
• Staff Information
• Website Information

DFD, Database structure, Database Tables

• DFD
• Database Structure
• Database Tables

This chapter describes the database design and table specifications.

System Design- Database Design

DYNAMIC MODULES

In this module an interface will be designed for the administrators to enable easy data modifications. A login screen shall be provided to the administrators. Only the persons having a valid username and password can log into the application and make changes to the databases of different applications that are a part of the portal.

System Design- Database Design

Approvals/Orders

There are many government departments that the citizens have to deal with on regular basis for their requirements. It gets difficult for the people to find out the telephone numbers of the various officials of different departments from the telephone directory if they do not know the name of the person and his/her address. It is cumbersome to locate the official's phone number by searching the department diary (if it is printed by the department). The online directory is made for the convenience of the people so that they do not have to search the directory or the department diary if they are looking for the telephone number of some official in the Chandigarh Administration. All they have to do is to enter a search criterion and they will get the details of the person they are trying to locate.

Focus on user needs:

Main features of the application are:

• Comfort of searching for the telephone numbers of government officials online.
• Information of employees is available in the database.
• Ease of data entry using drop down lists and default values.
• Data Validations at entry level.

Constraints:

• The directory should have complete information of employees regarding their department, designation, addresses, phones and emails address etc.
• The application should generate response for the visitors' queries.

APPROVALS/ORDERS

This module is made to enable the employees to access and maintain all the orders and their approvals. The database of all the orders and their approvals is maintained and is updated timely. With the help of this module the employees can add new office orders, add a financial approval, and list all the orders and approvals. This module will enable the employees to maintain the information of all the office orders and financial approvals in a very efficient and easy way, overcoming the disadvantages of paper work.

Features:

Main features of the application are:

• User can upload (.PDF extension) any of the orders and its approvals.
• User can view any of the orders and its approvals.

Objective:

The main objective of this module is to enable the employees to maintain all the office orders and financial approvals in an efficient way while overcoming the disadvantages involved in the paper system.

WEBSITE INFORMATION

This module is made to enable the employees to maintain all the information relating website development. With this application the employees can add new website developed, update the details of sites etc. The database of all this application is maintained timely.

Features:

Main features of the application are:

• User can add name of new website developed by the organization.
• User can update the details of the site.
• Generate bill.

Objective:

The main objective of this module is to make the work of employees easier.

Implementation

INTRODUCTION

Implementation is the process of building the web according to its design. A web implementer creates hypertext markup language (HTML), Common gateway Interface (CGI) programs and Java scripts or applets. The implementation process resembles software development because it involves using a specific syntax for encoding web structures or a programming language in a formal language in computer files. Although there are automated tools to help the web implementer's expertise.

User Interface

• Chandigarh Online Services:The various services areas follow:
• File Management System: File Management System (FMS) is a web-based application, which aims for having a proper monitoring on the flow of files in various Departments & Sub-departments of Chandigarh Administration.
• Visitor Information System: The Project, Visitor Information System (VIS) is a web-enabled application developed in JSP (Java Server Pages), HTML, Java Script and Access as a backend for Chandigarh administration. It runs on web servers supporting the Java Server Pages. The application is platform independent. The application can even run on Microsoft Servers having java web server installed, Lynx (which has inbuilt JSP support) and other server, which support Java Server Pages. It's Salient features are as follow:

1. Maintains the visitors Information, visiting UT Secretariat and complete information of employees of UT secretariat.
2. Generates passes for the visitors.
3. Has complete information of employees regarding their department, designation, addresses, phones and emails address etc.
4. Provides information to officers of UT Secretariat regarding passes issued to visitors.
5. Facilitates officers and officials to enter their availability in office. If officer or official is on leave, then the visitor is informed at the counter that particular officer or official is on leave.

• Integrated Scheme & Budget Monitoring System:
• Personal Desktop Assistant:

Rent Controller: It provide an online up to date status of all the houses allotted/vacated .The complete rent record of rent assessed and paid is available at just a key stroke away after selecting the sector and the house number. The features of this software are:

DYNAMIC CONTENTS

The dynamic contents are included in the portal for the convenience of the employees with in the organization. The employees can do their work without leaving the physical platform. This module has a sub module which further has various sub modules each of which provides certain information related to it.

FOR INTERNAL USE

Each of the sub modules of this module is governed by a login window. A login window is an interface that has been designed for the administrators to enable easy data modification. A login screen is provided to the administrators. Only the persons having a valid username and password can log into the application and make changes to the databases of the different applications that are a part of the portal.

After a user has successfully logged into the application, the following screen consisting of links to severals sub-modules is displayed.

The various sub modules of are as follow:

Online Forms

APPROVALS/ORDERS

On clicking the link of this sub-module following screen is displayed. The screen allows the user to upload a Financial Approvals and Office Orders into the database, view or list all the approvals and orders from the database.

PROJECT INFORMATION

On clicking the link of this sub-module following screen is displayed. The screen allows the user to add new project into database, associate an employee with project, update project status, and list all the projects from database.

Online Forms

STAFF INFORMATION

On clicking the link of this sub-module following screen is displayed. The screen gives the user information about all the employees of the organization, to update its own profile, to apply and cancel leaves and to access various forms required.

Chapter VI - Test plan and Installation

• Test Plan
• Levels of testing

This chapter prepares the final step in system development, testing the system for correctness and installation.

TEST PLAN

In a software development project, errors can be injected at any stage during development. For each phase, we have discussed different techniques for detecting and eliminating errors that originate in that phase. However, no technique is perfect, and it is expected that some of the errors of the earlier phases will finally manifest themselves in the code. This is particularly true because in the earlier phases, most of the verification techniques are manual because no executable code exists. Ultimately, these remaining errors will be reflected in the code. Because code is frequently the only product that can be executed and whose actual behavior can be observed, testing is the phase where the errors remaining from all the previous phases must be detected. Hence, testing performs a very critical role for quality assurance and for ensuring the reliability of software.

During testing, the program to be tested is executed with a set of test cases, and the output of the program for the test cases is evaluated to determine if the program is performing as expected.

In general, testing commences with a test plan and terminates with acceptance testing. A test plan is general document for the entire project that defines the scope, approach to be taken, and the schedule of testing as well as identifies the test items for the entire testing process and the personnel responsible for the different activities of testing. The test planning can be done well before the actual testing commences and can be done in parallel with the coding and design phases.

TEST PLAN

The project plan is needed to make sure that the test plan is consistent with the overall plan for the project and the testing schedule matches that of the project plan. The requirements document and the design document are the basic documents used for selecting the test units and deciding the approaches to be used during testing. A test plan should contain the following:

• Test unit specification
• Features to be tested
• Approach for testing
• Test deliverables
• Schedule

LEVELS OF TESTING

Now let us turn to the testing process. As faults can occur during any phase in the software development cycle. Due to this, different levels of testing are used in the testing process; each level of testing aims to test different aspects of the system.

The basic levels are:

• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing

LEVELS OF TESTING

UNIT TESTING

In this, different modules are tested against the specifications produced during design for the modules. Unit testing is essentially for verification of the code produced during the coding phase, and hence goal is to test the internal logic of the modules. This is done by both of us by considering that a module can be used by others only after it has been unit tested satisfactorily. Due to its close association with coding, the coding phase is frequently called "coding and unit testing".

INTEGRATION TESTING

In this, many unit tested modules are combined into subsystems, which are then tested. The main goal here is to see if the modules can be integrated properly. Hence, our emphasis is on testing interfaces between modules. Thus, this testing activity can be considered testing the design.

SYSTEM TESTING AND ACCEPTANCE TESTING

Here the entire software system is tested. The reference document for this purpose is the requirements document, and the goal is to see if the software meets its requirements. This is essentially a validation exercise, and in many situations it is the only validation activity. Acceptance testing is sometimes performed with realistic data of the client to demonstrate that software is working satisfactorily. Testing here focuses on the external behavior of the system; the internal logic of the program is not emphasized. Consequently, mostly functional testing is performed at these levels.

The two basic approaches of testing are:

• Black box or Functional Testing
• White box or Structural Testing

FUNCTIONAL TESTING

In functional testing the structure of the program is not considered. Test cases are decided solely on the basis of the requirements or specifications of the program or module, and the internals of the module or the program are not considered for selection of test cases. Due to its nature, functional testing is often called "black box testing". The basic for deciding test cases in functional testing is the requirements or specifications of the system or module. For the entire system, the test cases are designed from the requirements specifications document for the system. For modules created during design, test cases for functional testing are decided from the module specifications produced during the design. There are no formal rules for designing test cases for functional testing. In fact, there are no precise criteria for selecting test cases. However, there are a number of techniques that can be used to select test cases that have been found to be very successful in detecting errors. Here we mention some of these techniques:

• Equivalence Class Partitioning
• Boundary Value Analysis
• Error Guessing

STRUCTURAL TESTING

The functional testing is concerned with functionality rather than implementation of the program. Here, test cases are generated based on the actual code of the program or module to be tested. This structural approach is sometimes called "glass box testing". The intent of structural testing is not to exercise all the different input or output conditions but to exercise the different programming structures and data structures used in the program. To test the structure of a program, structural testing aims to achieve test cases that will force the desired coverage of different structures. Various criteria have been proposed for this. Unlike the criteria for functional testing, which are frequently imprecise, the criteria for structural testing are generally quite precise as they are based on program structures, which are formal and precise.

FUTURE RECOMMENDATIONS

The project id feasible, dynamic modules can be added easily to the project in case THE COMPANY needs to enhance the online facilities. All the information can be easily updated as per recent information.

The project is developed in ASP, which is aimed at making the project web-enabled. This project PORTAL DESIGN AND DEVELOPMENT aims at providing various services to the users.

Chapter VIII - Bibliography

This chapter gives account of various Books and websites referred during the development of my project

BIBLIOGRAPHY

All the Online forms in ASP provide a way to enter data into the database, and various reports and summaries can be Various books and some sites are referred during the development of the project are written below:

1. ASP
2. ASP for Dummies
3. SQL Server 2000
4. HTML 4.0 No Experience Required
5. HTML Complete Reference
6. Learning JavaScript from books and Notes
7. www.w3schools.com
8. www.aspfree.com

Need an essay? You can buy essay help from us today!

Please rate the quality of this essay:

Thanks for your rating :)

Good

Neutral

Poor

Request the removal of this essay.

Sign up and be the first to receive our latest offers: