CABLE OPERATOR MANAGEMENT SYSTEM PROJECT REPORT
CABLE OPERATOR MANAGEMENT SYSTEM PROJECT SOURCE CODE
CABLE OPERATOR MANAGEMENT SYSTEM PROJECT DOCUMENTATION
CABLE OPERATOR MANAGEMENT SYSTEM PROJECT DOCUMENTATION
1)
INTRODUCTION
·
INTRODUCTION TO
COMS
·
PURPOSE OF THE
PROJECT
·
PROBLEM IN
EXISTING SYSTEM
·
SOLUTION OF THESE
PROBLEMS
·
SCOPE OF THE
PROJECT
2)
PROJECT ANALYSIS
·
STUDY OF THE
SYSTEM
·
HARDWARE &
SOFTWARE SPECIFICATIONS
·
INPUT & OUTPUT
·
PROCESS MODELS
USED WITH JUSTIFICATION
3)
SELECTED SOFTWARE
4)
SOFTWARE
REQUIRMENT SPECIFICATION
·
FUNCTIONAL REQUIREMENTS
·
PERFORMANCE REQUIREMENTS
5)
PROJECT DESIGN
·
DATA DICTIONARY
·
E-R DIAGRAM
·
DATA FLOW DIAGRAMS
·
UML DIAGRAMS
6)
OUTPUT SCREENS
7)
PROJECT TESTING
·
COMPILING TEST
·
EXECUTION TEST
·
OUTPUT TEST
7)
FUTURE IMPROVEMENT
9)
CONCLUSION
10)
ERP
An ERP
solution aims to provide single software which will integrate all the divisions
in your organization planning, manufacturing, sales, marketing, finance, HR and
yet fulfill each division’s information and planning needs. ERP streamlines
processes within your organization and helps you meet business needs more
efficiently and quickly.
Clients
Sun
Informatics works with clients ranging from small, start-up organizations to
large, well-established corporations. The company’s client base represents a
wide variety of industries, including agriculture, Engineering Industries,
banking / finance, Telecommunications, healthcare, manufacturing, and of course
IT.
Client Services :
Sun
Informatics is a leading provider of full-service staffing solutions for a
broad range of companies throughout the Hyderabad and nationally. Our recruiters
can assist you with your specific staffing needs in all key-staffing areas:
Direct Placement: Our research capabilities, industry expertise, extensive network of contacts and determination allows us to find the top performers that best fit your particular requirements.
Interim Staffing: We recruit highly qualified
interim professionals for companies seeking an alternative to regular staffing
as a strategy for growth.
Right-Fit Services: Our staffing solutions deliver
the right talent to you with right-fit innovative services that include
compatibility assessment, private videoconferencing, outplacement and
relocation assistance.
We are
committed to providing our clients with unsurpassed levels of quality and
service. We have already accomplished this goal for numerous clients. It's a
mission we're ready to fulfill for you.
How We
Do It : As part of the Sun
Informatics network, Sun Informatics Nationwide commands state-of-the-art tools
that help you make the right decision about your company's most important
asset—your people.
Search
and Selection Process:
Ask about our proven comprehensive strategy for securing the best talent.
Confidentiality: Protect your company's
confidentiality with our confidential search services.
Compatibility
Assessment: Avoid
costly hiring mistakes with expert recruiters through Sun Informatics, our
reliable compatibility assessment tool.
International
Staffing: Leverage
our global network to meet your international recruiting needs.
Project
Outsourcing: Let us
create a nationwide project team for your large staffing assignments.
Videoconferencing: Conduct long-distance face-to-face
interviews with Videoconferencing by Sun Informatics.
Relocation
Services: Reduce
impediments associated with relocating candidates with Sun Informatics
innovative relocation services that include cost-of-living analysis, moving and
travel assistance.
How To
Engage Us : Our
flexible engagement options include retained search, priority search and
contingency search. Contact us to learn more and to determine which option is
right for your recruiting needs.
QUALITY : We have made Quality a way of life at Sun Informatics, the core of the
work we do, and the way we do it. This involves re-use of best and smart
practices, consistent improvement and improvisation of our methodologies and
processes, which inculcate a sense of doing things, right-the first time and
every time.
By
adopting new standards and a relentless pursuit of continuous improvement in
our quality management systems and processes, we continue to ensure commitment
to customer satisfaction.
ABSTRACT
Title
of the Project: CABLE OPERATOR MANAGEMENT
SYSTEM
Description:
Cable
Operator Management System is integrated and automation software for cable
operators. Cable operators will distribute TV channels to their customers for
that they charge some money monthly.
To
maintain their customers and number of users this software provides automation.
In this COM System they can main their staff member’s details and their
customer details. By using this COM System they can divide their areas macro
parts to micro parts. By using this system they can meet their business
requirements. Cable Operators once they divided their areas into micro parts
then they can assign their staff members to take care about their micro part
areas.
Cable
operators they can maintain their staff members like collection boys, helpers
and technicians. All the collection boys will have user id and password. At the
end of the every day they will login to the COM System they will feed their
collection details and remarks.
By using
this COM System they can know about their equipments located on which areas.
How many active / non active customers are there? all these details they can
view it by using the reports. MIS
reports were generated for the month of collections, expenses, pending amount,
complaints area wise and date wise, month wise.
Existing
System:
All the
work cable operator used to maintain
manually in books , vouchers, collection cards etc.,
System Design:
COM System (COMS) is an
integrated software deals with Cable Operators. Helps the Cable Operators
manage their customers and provides the information about various channels. It
makes easy to all operations of the Cable Operators and accurate.
Masters :
The
information specified in the Master is regarded static, in the sense that it is
“Permanent” or non-changing or stable. The updates are infrequent and may be
regarded as permanently stored in the Database. The Master Group has
functionality to View / Change.
The master
pages will have access to administrator only.
Transaction:
Transactions
deal with dynamic or transient data.
Transactions
do not affect the MASTER Data.
The
TRANSACTION Group of functionality is as follows:
Reports Module - CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
In this module we can generate the
various MIS Reports to keep track of the revenue, customer statistics area
wise, month wise, during the days and year wise etc.,
·
Area List
·
Employee List
·
Customer List
·
Collections Area wise
·
Total Collections
·
Collections between Dates
·
Customer A/c
·
List of Assets
SYSTEM
SPECIFICATION:
Software Requirements :
OPERATING SYSTEM
: WIN NT
FRONT END :
VB.NET
BUSINESS LOGIC :
VB.NET
DATABASE : MS.Access
Hardware Requirements :
PROCESSOR
: P3 or HIGHER
ram
: 512MB
HARD DISK : 20GB
1) PURPOSE OF THE PROJECT
Cable Operator Management System is integrated and
automation software for cable operators. Cable operators will distribute TV
channels to their customers for that they charge some money monthly.
To maintain their customers and number of users this software
provides automation. In this COM System they can main their staff member’s
details and their customer details. By using this COM System they can divide
their areas macro parts to micro parts. By using this system they can meet
their business requirements. Cable Operators once they divided their areas into
micro parts then they can assign their staff members to take care about their
micro part areas.
2) PROBLEMS IN THE EXISTING SYSTEM
An
extensive study of existing system was carried out. There is an existing system
available in branch. The system is run manually . It is difficult to run
efficiently by man power, and difficult to respond every user within short
period. Thus we came to know the essential need to make it automated.
3) PROPOSED SYSTEM: CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
To Automate
entire operations of the Cable Operator to maintain their customers list and
collections. In this COM System they can maintain their staff member’s details
and their customer details. By using this COM System they can divide their
areas macro parts to micro parts. By using this system they can meet their
business requirements. Cable Operators once they divided their areas into micro
parts then they can assign their staff members to take care about their micro
part areas.
By using
this COM System they can know about their equipments located on which areas.
How many active / non active customers are there? all these details they can
about it by using the reports. MIS reports were generated for the month of
collections, expenses, pending amount, complaints area wise and date wise,
month wise.
4)
SCOPE OF THE
PROJECT
To maintain
entire operations of the cable operator
to be Automated.
·
To maintain entire operations of the cable
operator to be automated.
·
The current system is
interactive with the database provides efforts can be made so that the system
can adopt the available database features of a new site.
PROJECT ANALYSIS - CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
1)
STUDY OF THE
SYSTEM
The complete system can be divided into five
halves on basis of access levels.
A) Account Management
B) Utilities
C) Authoring
D) Editing
E) Approving
F) Deployment
Account management:
Using this part of an application the administrator can view the list of
users and their area of specialization. The administrator can create a new
users, modify existing user. An administrator provides permission to the newly
created user by placing the new user into set of roles such as a author,
approver, editor or deploy. This part of
the application is only accessible to the administrator.
Utilities
:
Utilities section of the application is used to shut down the
application for the normal person to operate as well as to up the site back for
its use.
Authoring:
An administrator or a person with the
author privileges can access this part of the application. This part of the
application includes creating new content in the form of stories which is
normally done by the developers or content writers.
The newly created content may include no of
notes which will guide the editor at the time of editing the content. The newly
created content then can be posted to editor for editing.
Editor:
An
editor receives the content posted by the author. An editor can view the
content and later post the content to a new revision or to an existing
revision. If a content is found unsuitable to the cause the content is returned
back to the author. This part of the
application can be explored only by an administrator or the users who possess
an editor privilege. The editor can withdraw the content from being hosted if
found unfit for hosting.
Approver:
An approver is a person who will approve the
contents to be hosted on the site. An approver can approve the content to the
deploy section or Discontinue the content usage or return the content back to
the editor for revision. The returned content should accompany with a message
to the editor regarding the revision in the content. This part of the
application can be accessed by the administrator of the person who possess an
Approver privilege.
Deploy:
This area
of the application includes the deployment part of an application. A deploy
person can view the content before deploying it. The person can also return the
content if found unfit to be hosted on the site. The returned content is sent
back to the approver. The deployment of the content includes the content to be
placed in specific area of the hosting environment. The hosting environment is
divided into three categories. The Deploy content, the manager content, the
protected content. These categories are subdivided into no of sections.
Administrator:
An administrator has all the privileges
that of the guest as well as the normal registered user. Along with these common
features an administrator has the administrator related features such as
creating new users and granting roles to those newly created users. The roles
granted by the administrator cannot be changes by the user. An administrator
can create new user as a guest or as an user or an administrator. The access
levels are as per the grants done by the administrator.
An
administrator can also be part of a team and could lead a project team this is
possible only if administrator when building a team includes himself in the
team section. If included as a manager he is not a part of the team but
supervisor of the team.
The register option on the homepage of the application is provided only
to register a new user as a guest.
ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICATION
The following commands
specify access control identifiers and they are typically used to authorize and
authenticate the user (command codes are
shown in parentheses)
USER NAME (USER)
·
The user
identification is that which is required by the server for access to its file
system. This command will normally be the first command transmitted by the user
after the control connections are made (some servers may require this).
PASSWORD (PASS)
·
This command
must be immediately preceded by the user name command, and, for some sites,
completes the user's identification for access control. Since password
information is quite sensitive, it is desirable in general to "mask"
it or suppress type out.
SOFTWARE REQUIREMENT
SPECIFICATION -
REQUIREMENT SPECIFICATION:
The software, Electronic Document
Management system is designed for management of the content over a site.
INTRODUCTION
Purpose:
The main purpose for preparing this document is to give a general insight into
the analysis and requirements of the existing system or situation and for
determining the operating characteristics of the system.
Scope:
This Document plays a vital role in the development life cycle (SDLC)
As
it describes the complete requirement of the system. It is meant for use by the
developers and will be the basic during testing phase. Any changes made to the
requirements in the future will have to go through formal change approval
process.
Developers Responsibilities Overview:
The developer
is responsible for:
1)
Developing the system, which meets the SRS and solving all the requirements of
the system?
2)
Demonstrating the system and installing the system at client's location after
the acceptance testing is successful.
3)
Submitting the required user manual describing the system interfaces to work on
it and also the documents of the system.
4)
Conducting any user training that might be needed for using the system.
5)
Maintaining the system for a period of one year after installation.
Functional Requirements:
OUTPUT DESIGN
Outputs
from computer systems are required primarily to communicate the results of
processing to users. They are also used to provides a permanent copy of the
results for later consultation. The various types of outputs in general are:
·
. External
Outputs, whose destination is outside the organization.
·
. Internal
Outputs whose destination is with in organization and they are the
§ user’s
main interface with the computer.
·
Operational
outputs whose use is purely with in the computer department.
·
Interface
outputs, which involve the user in communicating directly with
Output Definition
§ Type
of the output
§ Content
of the output
§ Format
of the output
§ Location
of the output
§ Frequency
of the output
§ Volume
of the output
§ Sequence
of the output
It is not always desirable to
print or display data as it is held on a computer. It should be decided as
which form of the output is the most suitable.
For Example
·
Will decimal
points need to be inserted
·
Should leading
zeros be suppressed.
Output
Media:
In the next stage it is to be
decided that which medium is the most appropriate for the output. The main
considerations when deciding about the output media are:
.The suitability for the device to the
particular application.
.The need for a hard copy.
.The response time required.
.The location of the users
.The software and hardware available.
The
cost.
Keeping in view the above
description the project is to have outputs mainly coming under the category of
internal outputs. The main outputs desired according to the requirement
specification are:
The
outputs were needed to be generated as a hot copy and as well as queries to be
viewed on the screen. Keeping in view
these outputs, the format for the output is taken from the outputs, which are
currently beeing obtained after manual processing. The standard printer is to be used as output
media for hard copies.
INPUT DESIGN -CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
Input
design is a part of overall system design.
The main objective during the input design is as given below:
·
To produce a
cost-effective method of input.
·
To achieve the
highest possible level of accuracy.
·
To ensure that
the input is acceptable and understood by the user.
INPUT
STAGES:
The main input stages can be listed as below:
·
Data recording
·
Data
transcription
·
Data
conversion
·
Data
verification
·
Data control
·
Data
transmission
·
Data
validation
·
Data
correction
INPUT
TYPES:
It is necessary to determine the
various types of inputs. Inputs can be
categorized as follows:
·
External
inputs, which are prime inputs for the system.
·
Internal
inputs, which are user communications with the system.
·
Operational,
which are computer department’s communications to the system?
·
Interactive,
which are inputs entered during a dialogue.
INPUT
MEDIA:
At this stage choice has to be made about
the input media. To conclude about the
input media consideration has to be given to;
·
Type of input
·
Flexibility of
format
·
Speed
·
Accuracy
·
Verification
methods
·
Rejection
rates
·
Ease of correction
·
Storage and
handling requirements
·
Security
·
Easy to use
·
Portabilility
Keeping
in view the above description of the input types and input media, it can be
said that most of the inputs are of the form of internal and interactive. As
Input
data is to be the directly keyed in by the user, the keyboard can be considered
to be the most suitable input device.
ERROR
AVOIDANCE
At this stage care is to be taken to
ensure that input data remains accurate form the stage at which it is recorded
upto the stage in which the data is accepted by the system. This can be achieved only by means of careful
control each time the data is handled.
ERROR
DETECTION
Even though every effort is make to
avoid the occurrence of errors, still a small proportion of errors is always
likely to occur, these types of errors can be discovered by using validations
to check the input data.
DATA
VALIDATION
Procedures are designed to detect errors
in data at a lower level of detail. Data
validations have been included in the system in almost every area where there
is a possibility for the user to commit errors.
The system will not accept invalid data.
Whenever an invalid data is keyed in, the system immediately prompts the
user and the user has to again key in the data and the system will accept the
data only if the data is correct.
Validations have been included where necessary.
The system is designed to be a user
friendly one. In other words the system
has been designed to communicate effectively with the user. The system has been designed with pop up
menus.
USERINTERGFACE
DESIGN
It is essential to consult the system
users and discuss their needs while designing the user interface:
USER
INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:
1. User
initiated interface the user is in charge, controlling the progress of the
user/computer dialogue. In the
computer-initiated interface, the computer selects the next stage in the
interaction.
2. Computer
initiated interfaces
In
the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is
displayed and the user response of the computer takes action or displays
further information.
USER_INITIATED
INTERGFACES
User
initiated interfaces fall into tow approximate classes:
1. Command
driven interfaces: In this type of interface the user inputs commands or
queries which are interpreted by the computer.
2. Forms
oriented interface: The user calls up an image of the form to his/her screen
and fills in the form. The forms
oriented interface is chosen because it is the best choice.
COMPUTER-INITIATED
INTERFACES
The
following computer – initiated interfaces were used:
1. The
menu system for the user is presented with a list of alternatives and the user
chooses one; of alternatives.
2. Questions
– answer type dialog system where the computer asks question and takes action
based on the basis of the users reply.
Right
from the start the system is going to be menu driven, the opening menu displays
the available options. Choosing one
option gives another popup menu with more options. In this way every option leads the users to
data entry form where the user can key in the data.
ERROR
MESSAGE DESIGN:
The design of error messages is an
important part of the user interface design.
As user is bound to commit some errors or other while designing a system
the system should be designed to be helpful by providing the user with
information regarding the error he/she has committed.
This application must be able to produce output at different modules for
different inputs.
Performance Requirements: CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
Performance is measured in terms of the output
provided by the application.
Requirement
specification plays an important part in the analysis of a system. Only when
the requirement specifications are properly given, it is possible to design a
system, which will fit into required environment. It rests largely in the part of the users of
the existing system to give the requirement specifications because they are the
people who finally use the system. This
is because the requirements have to be known during the initial stages so that
the system can be designed according to those requirements. It is very difficult to change the system
once it has been designed and on the other hand designing a system, which does
not cater to the requirements of the user, is of no use.
The
requirement specification for any system can be broadly stated as given below:
·
The system
should be able to interface with the existing system
·
The system
should be accurate
·
The system
should be better than the existing system
The
existing system is completely dependent on the staff to perform all the duties.
MODULES OF THE APPLICATION - CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
Masters :
The
information specified in the Master is regarded static, in the sense that it is
“Permanent” or non-changing or stable. The updates are infrequent and may be
regarded as permanently stored in the Database. The Master Group has
functionality to View / Change.
The master
pages will have access to administrator only.
·
Area Master --–
Cable Operators they will divide their areas macro parts to micro parts like
huge area will be divided in to small areas, divisions. In this module admin
will add areas and code numbers.
·
Employee Master
-- Admin will add the staff and will provide the privileges as per the
staff designation. All the staff members cannot access all the modules. He can
add or delete the staff accounts.
·
Customer Master
-- Admin will add the new customers those who come in their areas and take new connection. Admin can add
or delete the customers and they can view the entire customers list in area
wise.
·
Monthly Charges
-- Admin will add or modify the monthly charges depends on the areas.
Some areas they will charge more and some areas less depends on the
channels they provide.
Transaction:
Transactions
deal with dynamic or transient data.
Transactions
do not affect the MASTER Data.
The
TRANSACTION Group of functionality is as follows:
·
Collection Screen -- In this module Cable operators
will generate the monthly wise collection statement for their particular areas
and customer wise. They can generate the date to date collection statements.
Staff wise collection statements and area wise statements will generate by
using this module.
·
Customer Status – Customer can take connection and remove connection due to various reasons
at any point of time. Once is disconnected we make him inactive . We can change
customer status any point of time.
·
Assets Entry --
Reports Module
In this module we can generate the
various MIS Reports to keep track of the revenue, customer statistics area
wise, month wise, during the days and year wise etc.,
1.
Area List
2.
Employee List
3.
Customer List
4.
Collections Area wise
5.
Total Collections
6.
Collections between Dates
7.
Customer A/c
8.
List of Assets
Feasibility Study: CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
Feasibility
Study is a high level capsule version of the entire process intended to
answer a number of questions like: What is the problem? Is there any feasible
solution to the given problem? Is the problem even worth solving? Feasibility study is conducted once the
problem clearly understood. Feasibility study is necessary to determine that
the proposed system is Feasible by considering the technical, Operational, and Economical
factors. By having a detailed feasibility study the management will have a
clear-cut view of the proposed system.
The
following feasibilities are considered for the project in order to ensure that
the project is variable and it does not have any major obstructions.
Feasibility study encompasses the following things:
·
Technical Feasibility
·
Economical Feasibility
·
Operational Feasibility
In this
phase, we study the feasibility of all proposed systems, and pick the best
feasible solution for the problem. The feasibility is studied based on three
main factors as follows.
2.1. Technical Feasibility:
In this
step, we verify whether the proposed systems are technically feasible or not.
i.e., all the technologies required to develop the system are available readily
or not.
Technical
Feasibility determines whether the organization has the technology and skills
necessary to carryout the project and how this should be obtained. The system
can be feasible because of the following grounds.
All
necessary technology exists to develop the system.
This system
is too flexible and it can be expanded further.
This
system can give guarantees of accuracy, ease of use, reliability and the data
security.
This
system can give instant response to inquire.
Our
project is technically feasible because, all the technology needed for our
project is readily available.
·
Front End : Vb.Net
·
Back End : MS Access
·
Host :
Windows-2000
2.2. Economical Feasibility:
In this
step, we verify which proposal is more economical. We compare the financial
benefits of the new system with the investment. The new system is economically
feasible only when the financial benefits are more than the investments and
expenditure. Economical Feasibility determines whether the project goal can be
within the resource limits allocated to it or not. It must determine whether it
is worthwhile to process with the entire project or whether the benefits
obtained from the new system are not worth the costs. Financial benefits must
be equal or exceed the costs. In this issue, we should consider:
·
The cost to conduct a full system investigation.
·
The cost of h/w and s/w for the class of application
being considered.
·
The development tool.
·
The cost of maintenance etc.,
Our
project is economically feasible because the cost of development is very minimal
when compared to financial benefits of the application.
2.3. Operational Feasibility:
In this step, we verify different operational factors of the proposed
systems like man-power, time etc., whichever solution uses less operational
resources, is the best operationally feasible solution. The solution should
also be operationally possible to implement. Operational Feasibility determines
if the proposed system satisfied user objectives could be fitted into the
current system operation. The present system Enterprise Resource Information
System can be justified as Operationally Feasible based on the following
grounds.
The methods of processing and presentation are completely accepted by
the clients since they can meet all user requirements.
The
clients have been involved in the planning and development of the system.
The
proposed system will not cause any problem under any circumstances.
Our
project is operationally feasible because the time requirements and personnel
requirements are satisfied. We are a team of four members and we worked on this
project for three working months.
PROJECT INITIATION:
In this
phase, we perform the preliminary investigation procedures like setting up
project goals, gathering requirements from client etc., this phase consists of
two sub-phases as follows.
3.1. Formulation of Goals:
In this
step, we formulate the goals to be achieved in the new system. As the
applications are web-based, the goals can be categorized into two types like
informatory goals and functional goals. Formulation of web-based systems and
applications represents a sequence of web engineering actions like
identification of business needs, description of objectives, definition of
major features and functions etc.,
Formulation Questions
Q. What is
the main motivation (business need) for the application?
For the present application, the
business needs are identified as follows. The companies need an online intranet
application to publicize their art galleries and put for auctioning. The
companies need an application to store and manage all the galleries details.
The agents need an application to search for good companies in a desirable
location. The users or bidders need an application to facilitate any-time
bidding. The users search for art galleries and select the desirable one. Then
the users can bid a price on their own. All these biddings can be seen by the
company. It can select the best bid from the list and can make a deal.
Q.
What are the
objectives that the application must fulfill?
The goals
for the present web-application are identified as follows.
1. Informatory Goals:
Informatory goals speak about what kind of information
must be served by the application. This application should fulfill the
following informatory goals.
·
This application should provide
complete information about the several companies which deal with art galleries
and their auctions.
·
This application should
provide complete information about the several agents who act as mediators in
helping find the right product for a right bidding price.
·
This application should
provide complete information about the several galleries added by the company.
This information includes the product name, description, bidding price, last
date etc.,
·
This application should
provide information about the complete catalog of the company.
The application should provide the complete information,
terms & conditions.
2. Functional Goals:
·
Functional goals speak about what kind of services or
functionalities must be provided by the application to the different categories
of users.
·
All kinds of users to the web-application should have
a proper login facility with password recovery option.
·
The companies, agents and users can register to the
portal using the registration forms.
·
The administrator should have a facility to view a
list of companies’ registrations. He can view the complete profile of the
company. Once all the payment formalities are finished, the administrator
approves the company. Or he may also reject the company. Only approved
companies can login to the portal.
·
The registered company should have a functionality to
add and manage art galleries.
·
The bidder or the user should have a search program
which can fetch the list of galleries and their products which are related to
different companies.
·
The user can view the details of the gallery products.
He can also search the products which are currently available for bidding.
·
The user can select a product and bid it with a
desired bidding price.
3.2. Requirements Gathering:
In this step, we gather the requirements from the client, which act as
inputs for the development of the application. To gather requirements from
different types of clients, we follow different techniques like personal
interviews, questioners, observation, record review etc., Requirements’ gathering
is a process of understanding the requirements of a problem. For a web-based
application, the requirements gathering objectives are proposed as follows.
·
Identify content
requirements
·
Identify functional
requirements
CONTENT REQUIREMENTS -
This
application should provide complete information about the several companies
which deal with art galleries and their auctions. This application should
provide complete information about the several agents who act as mediators in
helping find the right product for a right bidding price. This application
should provide complete information about the several galleries added by the
company. This information includes the product name, description, bidding
price, last date etc, This application should provide information about the
complete catalog of the company. The application should provide the complete
information, terms & conditions.
FUNCTIONAL
REQUIREMENTS
All kinds
of users to the web-application should have a proper login facility with
password recovery option. The companies, agents and users can register to the
portal using the registration forms. The administrator should have a facility
to view a list of companies’ registrations. He can view the complete profile of
the company. Once all the payment formalities are finished, the administrator
approves the company. Or he may also reject the company. Only approved
companies can login to the portal. .The registered company should have a
functionality to add and manage art galleries.
ANALYSIS:
In this
phase, we thoroughly study the requirements gathered from the client and
analyze them. Then we develop a model to the solution using different modeling
techniques. The following are the different sub-phases involved in this phase.
4.1. Requirement Analysis:
In this
step, the requirements gathered from the client in previous phase, are
thoroughly analyzed and the client requirement is understood properly.
Requirement analysis for web applications encompasses three major tasks:
formulation, requirements gathering and analysis modeling. During formulation,
the basic motivation and goals for the web application are identified, and the
categories of users are defined. In the requirements gathering phase, the
content and functional requirements are listed and interaction scenarios
written from end-user’s
point-of-view are developed. This intent is to establish a basic understanding
of why the web application is built, who will use it, and what problems it will
solve for its users.
4.2. System Requirement Specification:
In this
step, we generate a report on System Requirement Specification. This is a
document, which consists of the list of requirements and functionalities to be
provided in the new system. Here we also generate reports on software
requirement and hardware requirement for developing the application.
SELECTED
SOFTWARE
Microsoft.NET Framework - CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
The .NET Framework is
a new computing platform that simplifies application development in the highly
distributed environment of the Internet. The .NET Framework is designed to
fulfill the following objectives:
- To provide a consistent object-oriented
programming environment whether object code is stored and executed
locally, executed locally but Internet-distributed, or executed remotely.
- To provide a code-execution environment that
minimizes software deployment and versioning conflicts.
- To provide a code-execution environment that
guarantees safe execution of code, including code created by an unknown or
semi-trusted third party.
- To provide a code-execution environment that
eliminates the performance problems of scripted or interpreted
environments.
- To make the developer experience consistent
across widely varying types of applications, such as Windows-based
applications and Web-based applications.
- To build all communication on industry
standards to ensure that code based on the .NET Framework can integrate
with any other code.
The .NET Framework
has two main components: the common language runtime and the .NET Framework
class library. The common language runtime is the foundation of the .NET
Framework. You can think of the runtime as an agent that manages code at
execution time, providing core services such as memory management, thread
management, and remoting, while also enforcing strict type safety and other
forms of code accuracy that ensure security and robustness. In fact, the
concept of code management is a fundamental principle of the runtime. Code that
targets the runtime is known as managed code, while code that does not target
the runtime is known as unmanaged code. The class library, the other main
component of the .NET Framework, is a comprehensive, object-oriented collection
of reusable types that you can use to develop applications ranging from
traditional command-line or graphical user interface (GUI) applications to
applications based on the latest innovations provided by ASP.NET, such as Web
Forms and XML Web services.
The .NET Framework
can be hosted by unmanaged components that load the common language runtime
into their processes and initiate the execution of managed code, thereby
creating a software environment that can exploit both managed and unmanaged
features. The .NET Framework not only provides several runtime hosts, but also
supports the development of third-party runtime hosts.
For example, ASP.NET
hosts the runtime to provide a scalable, server-side environment for managed
code. ASP.NET works directly with the runtime to enable Web Forms applications
and XML Web services, both of which are discussed later in this topic.
Internet Explorer is
an example of an unmanaged application that hosts the runtime (in the form of a
MIME type extension). Using Internet Explorer to host the runtime enables you
to embed managed components or Windows Forms controls in HTML documents.
Hosting the runtime in this way makes managed mobile code (similar to
Microsoft® ActiveX® controls) possible, but with significant improvements that
only managed code can offer, such as semi-trusted execution and secure isolated
file storage.
The following
illustration shows the relationship of the common language runtime and the
class library to your applications and to the overall system. The illustration
also shows how managed code operates within a larger architecture.
PROJECT DESIGN - CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
SOFTWARE
ENGINEERING PARADIGM APPLIED- (RAD-MODEL)
The two design objectives continuously sought by
developers are reliability and maintenance.
Reliable System
There are two levels of reliability. The
first is meeting the right requirements. A careful and through systems study is
needed to satisfy this aspect of reliability. The second level of systems
reliability involves the actual working delivered to the user. At this level,
the systems reliability is interwoven with software engineering and development.
There are three approaches to reliability.
1. Error
avoidance: Prevents errors from occurring in software.
2. Error
detection and correction: In this approach errors are
recognized whenever they are encountered and correcting the error by effect of
error, of the system does not fail.
3. Error
tolerance: In this approach errors are recognized whenever
they occur, but enables the system to keep running through degraded perform or
by applying values that instruct the system to continue process.
Maintenance:
The
key to reducing need for maintenance, while working, if possible to do
essential tasks.
1. More
accurately defining user requirement during system development.
2. Assembling
better systems documentation.
3. Using
more effective methods for designing, processing, login and communicating
information with project team members.
4. Making
better use of existing tools and techniques.
5. Managing
system engineering process effectively.
Output Design:
One of the most
important factors of an information system for the user is the output the
system produces. Without the quality of the output, the entire system may
appear unnecessary that will make us avoid using it possibly causing it to
fail. Designing the output should
process the in an organized well throughout the manner. The right output must be developed while
ensuring that each output element is designed so that people will find the
system easy to use effectively.
The
term output applying to information produced by an information system whether
printed or displayed while designing the output we should identify the specific
output that is needed to information requirements select a method to present
the formation and create a document report or other formats that contains
produced by the system.
Types of output:
Whether
the output is formatted report or a simple listing of the contents of a file, a
computer process will produce the output.
·
A Document
·
A Message
·
Retrieval from
a data store
·
Transmission
from a process or system activity
·
Directly from
an output sources
Layout Design:
It is an arrangement of items on the output
medium. The layouts are building a
mock up of the actual reports or document, as it
will appear after the system is in operation. The output layout has been
designated to cover information. The outputs are presented in the appendix.
Input
design and control:
Input
specifications describe the manner in which data enter the system for
processing. Input design features will ensure the reliability of the systems
and produce results from accurate data, or thus can be
result in the production of erroneous information.
The input design also determines whenever the user can interact efficiently
with this system.
Objectives of input design:
Input
design consists of developing specifications and procedures for data
preparation, the steps necessary to put transaction data into a usable from for
processing and data entry, the activity of data into the computer processing.
The five objectives of input design are:
·
Controlling
the amount of input
·
Avoiding delay
·
Avoiding error
in data
·
Avoiding extra
steps
·
Keeping the
process simple
Controlling the amount of input:
Data
preparation and data entry operation depend on people, because labour costs are
high, the cost of preparing and entering data is also high. Reducing data
requirement expense. By reducing input requirement the speed of entire process
from data capturing to processing to provide results to users.
Avoiding delay:
The
processing delay resulting from data preparation or data entry operations is
called bottlenecks. Avoiding bottlenecks should be one objective of input.
Avoiding errors:
Through input validation we control the
errors in the input data.
Avoiding extra steps:
The
designer should avoid the input design that cause extra steps in processing
saving or adding a single step in large number of transactions saves a lot of
processing time or takes more time to process.
Keeping process simple:
If
controls are more people may feel difficult in using the systems. The
best-designed system fits the people who use it in a way that is comfortable
for them.
NORMALIZATION -
It is a process of converting a relation
to a standard form. The process is used
to handle the problems that can arise due to data redundancy i.e. repetition of
data in the database, maintain data integrity as well as handling problems that
can arise due to insertion, updation, deletion anomalies.
Decomposing is the process of splitting
relations into multiple relations to eliminate anomalies and maintain anomalies
and maintain data integrity. To do this
we use normal forms or rules for structuring relation.
Insertion
anomaly:
Inability to add data to the database due to absence of other data.
Deletion anomaly: Unintended loss of data
due to deletion of other data.
Update anomaly: Data inconsistency resulting from
data redundancy and partial update
Normal Forms:
These are the rules for structuring relations that eliminate anomalies.
First Normal Form:
A relation is said to be in first normal
form if the values in the relation are atomic for every attribute in the
relation. By this we mean simply that no
attribute value can be a set of values or, as it is sometimes expressed, a
repeating group.
Second Normal Form:
A relation is said to
be in second Normal form is it is in first normal form and it should satisfy
any one of the following rules.
1)
Primary
key is a not a composite primary key
2)
No
non key attributes are present
3)
Every
non key attribute is fully functionally dependent on full set of primary key.
Third Normal Form:
A relation is said to be in third normal
form if their exits no transitive dependencies.
Transitive Dependency: If two non key attributes depend on each
other as well as on the primary key then they are said to be transitively
dependent.
The above normalization principles
were applied to decompose the data in multiple table thereby making the data to
be maintained in a consistent state.
Data
Dictionary
After
carefully understanding the requirements of the client the the entire data
storage requirements are divided into tables. The below tables are normalized
to avoid any anomalies during the course of data entry.
DATA FLOW DIAGRAM: CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
A
data flow diagram is graphical tool used to describe and analyze movement of
data through a system. These are the
central tool and the basis from which the other components are developed. The transformation of data from input to
output, through processed, may be described logically and independently of
physical components associated with the system.
These are known as the logical data flow diagrams. The physical data flow diagrams show the
actual implements and movement of data between people, departments and
workstations. A full description of a
system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane
and Sarson notation develops the data flow diagrams. Each component in a DFD is
labeled with a descriptive name. Process
is further identified with a number that will be used for identification
purpose. The development of DFD’s is
done in several levels. Each process in
lower level diagrams can be broken down into a more detailed DFD in the next
level. The lop-level diagram is often
called context diagram. It consists a single process bit, which plays vital
role in studying the current system. The
process in the context level diagram is exploded into other process at the
first level DFD.
The idea behind the explosion of a
process into more process is that understanding at one level of detail is
exploded into greater detail at the next level.
This is done until further explosion is necessary and an adequate amount
of detail is described for analyst to understand the process.
Larry Constantine first developed the
DFD as a way of expressing system requirements in a graphical from, this lead
to the modular design.
A DFD is also known as a “bubble Chart”
has the purpose of clarifying system requirements and identifying major
transformations that will become programs in system design. So it is the starting point of the design to
the lowest level of detail. A DFD
consists of a series of bubbles joined by data flows in the system.
DFD SYMBOLS:
In
the DFD, there are four symbols
1. A
square defines a source(originator) or destination of system data
2. An
arrow identifies data flow. It is the
pipeline through which the information flows
3. A
circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
4. An
open rectangle is a data store, data at rest or a temporary repository of data
CONSTRUCTING A DFD:
Several
rules of thumb are used in drawing DFD’s:
1. Process
should be named and numbered for an easy reference. Each name should be representative of the
process.
2. The
direction of flow is from top to bottom and from left to right. Data Traditionally flow from source to the
destination although they may flow back to the source. One way to indicate this is to draw long flow
line back to a source. An alternative
way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it
is marked with a short diagonal.
3. When
a process is exploded into lower level details, they are numbered.
4. The
names of data stores and destinations are written in capital letters. Process
and dataflow names have the first letter of each work capitalized
A
DFD typically shows the minimum contents of data store. Each data store should contain all the data
elements that flow in and out.
Questionnaires
should contain all the data elements that flow in and out. Missing interfaces redundancies and like is
then accounted for often through interviews.
SAILENT FEATURES OF DFD’s
1. The
DFD shows flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
2. The
DFD does not indicate the time factor involved in any process whether the data
flows take place daily, weekly, monthly or yearly.
3. The
sequence of events is not brought out on the DFD.
TYPES
OF DATA FLOW DIAGRAMS
1. Current
Physical
2. Current
Logical
3. New
Logical
4. New
Physical
CURRENT
PHYSICAL:
In Current Physical DFD process label
include the name of people or their positions or the names of computer systems
that might provide some of the overall system-processing label includes an
identification of the technology used to process the data. Similarly data flows and data stores are
often labels with the names of the actual physical media on which data are
stored such as file folders, computer files, business forms or computer tapes.
CURRENT LOGICAL:
The physical aspects at the system are
removed as mush as possible so that the current system is reduced to its
essence to the data and the processors that transform them regardless of actual
physical form.
NEW LOGICAL:
This is exactly like a current logical
model if the user were completely happy with he user were completely happy with
the functionality of the current system but had problems with how it was
implemented typically through the new logical model will differ from current
logical model while having additional functions, absolute function removal and
inefficient flows recognized.
NEW PHYSICAL:
The
new physical represents only the physical implementation of the new system.
RULES
GOVERNING THE DFD’S
PROCESS
1) No
process can have only outputs.
2) No
process can have only inputs. If an
object has only inputs than it must be a sink.
3) A
process has a verb phrase label.
DATA
STORE
1) Data
cannot move directly from one data store to another data store, a process must
move data.
2) Data
cannot move directly from an outside source to a data store, a process, which
receives, must move data from the source and place the data into data store
3) A
data store has a noun phrase label.
SOURCE OR SINK
The
origin and /or destination of data.
1) Data
cannot move direly from a source to sink it must be moved by a process
2) A
source and /or sink has a noun phrase land
DATA FLOW
1) A
Data Flow has only one direction of flow between symbol. It may flow in both directions between a
process and a data store to show a read before an update. The later is usually indicated however by two
separate arrows since these happen at different type.
2) A
join in DFD means that exactly the same data comes from any of two or more
different processes data store or sink to a common location.
3) A
data flow cannot go directly back to the same process it leads. There must be atleast one other process that
handles the data flow produce some other data flow returns the original data
into the beginning process.
4) A
Data flow to a data store means update ( delete or change).
5) A
data Flow from a data store means retrieve or use.
A
data flow has a noun phrase label more than one data flow noun phrase can
appear on a single arrow as long as all of the flows on the same arrow move
together as one package.
Use
case Diagrams
1. Use case diagrams describe what a system does from
the standpoint of an external observer. The emphasis is on what a system does
rather than how.
2.
Use case diagrams are closely connected to
scenarios. A scenario is an example of what happens when someone
interacts with the system.
3.
A use case is a summary of scenarios for a single task or goal. An actor is who or
what initiates the events involved in that task. Actors are simply roles that
people or objects play.
4. A use
case diagram is a collection of actors, use cases, and their communications.
Use case diagrams are helpful in three areas:
Ø Determining
features (requirements). New use cases often generate new requirements as the system is
analyzed and the design takes shape.
Ø Communicating
with clients. Their notational simplicity makes use case diagrams a good way
for developers to communicate with clients.
Ø Generating
test cases.
The collection of scenarios for a use case may suggest a suite of test cases
for those scenarios.
Class Diagrams
1. A Class diagram gives an overview of a system by
showing its classes and the relationships among them.
2. Class
diagrams are static. They display what interacts but not what happens when they
do interact.
Notations:
Ø UML
class notation is a rectangle divided into three parts: class name, attributes,
and operations.
Ø Names
of abstract classes are in italics. [example: Payment]
Ø Relationships
between classes are the connecting links.
Relationships:
1. Association -- a relationship between
instances of the two classes. There is an association between two classes if an
instance of one class must know about the other in order to perform its work.
In a diagram, an association is a link connecting two classes.
2. Aggregation -- an association in
which one class belongs to a collection. An aggregation has a diamond end
pointing to the part containing the whole. In our diagram, Order has a
collection of OrderDetails.
3. Generalization -- an inheritance link
indicating one class is a superclass of the other. A generalization has a
triangle pointing to the super class. Payment is a super class of
Cash, Check, and Credit.
4. Composition
-- Each instance of type Circle seems to contain
an instance of type Point. Composition relationships are a strong form
of containment or aggregation. Aggregation is a whole/part relationship.
Composition also indicates that the lifetime of Point is dependent upon Circle.
This means that if Circle is destroyed, Point will be destroyed
with it.
Ø An
association has two ends. An end may have a role name
to clarify the nature of the association. For example, an OrderDetail is
a line item of each Order.
Ø A navigability arrow on an association shows which
direction the association can be traversed or queried. An OrderDetail
can be queried about its Item, but not the other way around. The arrow
also lets you know who "owns" the association's implementation; in
this case, OrderDetail has an Item. Associations with no
navigability arrows are bi-directional.
Ø The multiplicity of an association end is the number
of possible instances of the class associated with a single instance of the
other end. Multiplicities are single numbers or ranges of numbers. In our
example, there can be only one Customer for each Order, but a Customer
can have any number of Orders.
Ø Every
class diagram has classes, associations, and multiplicities. Navigability and
roles are optional items placed in a diagram to provide clarity.
Ø Packages
appear as rectangles with small tabs at the top. The package name is on the tab
or inside the rectangle.
Ø The
dotted arrows are dependencies. One package
depends on another if changes in the other could possibly force changes in the
first.
Object Diagrams
1. Object diagrams show instances instead of classes.
2. They
are useful for explaining small pieces with complicated relationships,
especially recursive relationships.
Ø Each rectangle in
the object diagram corresponds to a single instance. Instance names are
underlined in UML diagrams. Class or instance names may be omitted from object
diagrams as long as the diagram meaning is still clear.
Sequence
Diagrams
1. Class
and object diagrams are static model views. Interaction diagrams are dynamic. They
describe how objects collaborate.
2. A sequence
diagram
is an interaction diagram that details how operations are carried out -- what
messages are sent and when.
3. Sequence
diagrams are organized according to time. The time progresses as you go down
the page.
4. The
objects involved in the operation are listed from left to right according to
when they take part in the message sequence.
Collaboration Diagrams
1. Collaboration diagrams are also interaction diagrams.
2. They
convey the same information as sequence diagrams, but they focus on object
roles instead of the times that messages are sent.
3. In a
sequence diagram, object roles are the vertices and messages are the connecting
links.
Notations:
Ø The
object-role rectangles are labeled with either class or object names (or both).
Class names are preceded by colons ( : ).
Ø Each
message in a collaboration diagram has a sequence
number. The top-level message is numbered 1. Messages at the same level
(sent during the same call) have the same decimal prefix but suffixes of 1, 2,
etc. according to when they occur.
Statechart
Diagrams
1. Objects
have behaviors and state. The state of an object depends on its current
activity or condition.
2. A statechart diagram shows the possible states of
the object and the transitions that cause a change in state.
Ø This
diagram has two self-transition, one on Getting SSN and another on Getting
PIN.
Ø While
in its Validating state, the object does not wait for an outside event
to trigger a transition. Instead, it performs an activity. The result of that
activity determines its subsequent state.
Notations
Ø States
are rounded rectangles.
Ø Transitions
are arrows from one state to another. Events or conditions that trigger
transitions are written beside the arrows.
Ø The
initial state (black circle) is a dummy to start the action. Final states are
also dummy states that terminate the action.
Ø The
action that occurs as a result of an event or condition is expressed in the
form /action.
Activity Diagrams
1. An activity diagram is essentially a fancy
flowchart. Activity diagrams and statechart diagrams are related.
2. While
a statechart diagram focuses attention on an object undergoing a process (or on
a process as an object), an activity diagram focuses on the flow of activities
involved in a single process.
3. The
activity diagram shows the how those activities depend on one another.
Notations:
Ø The
process begins at the black start circle at the top and ends at the concentric
white/black stop circles at the bottom. The activities are rounded rectangles.
Ø Activity
diagrams can be divided into object swimlanes that
determine which object is responsible for which activity. A single transition comes out of each activity,
connecting it to the next activity.
Ø A
transition may branch into two or more mutually
exclusive transitions. Guard expressions (inside [ ]) label the
transitions coming out of a branch. A branch and its subsequent merge
marking the end of the branch appear in the diagram as hollow diamonds.
Component &
Deployment Diagrams
1. A component
is a code module. Component diagrams are physical analogs of class diagram. Deployment
diagrams show the physical configurations of software and hardware.
Notations:
Ø The physical hardware is made up of nodes. Each component
belongs on a node. Components are shown as rectangles with two tabs at the
upper left.
A system is simply a set of components that interact to accomplish
some purpose.
Systems are of two types.
·
Open Systems.
·
Closed Systems.
Systems that interact
with their environments are open systems. They receive input and produce output. In contrast; systems
that do not interact with their surroundings are
closed systems all ongoing systems are open. Closed systems exist only as
a concept.
System development can generally be thought
of as having two major components
·
System
Analysis.
·
System
Design.
System
analysis is the process of gathering and interpreting facts, diagnosing
problems, and using the information to recommend improvements to the system.
System Design is the process of planning a new business system or one to
replace or complement an existing system.
Systems analysis
is about understanding situations, not solving problems. Effective analysts
therefore emphasize investigation and questioning to learn how the system
currently operates and to identify the requirements users have for a new or
modified one. Only after analysts fully understand the system are they able to
analyze it and assemble recommendations for system design.
The manner in which a systems
investigation is conducted will determine whether the appropriate information
is gathered. In turn, having the right information influences the quality of
the application that follows .in other words, good system design, whether
developed through the SDLC method, prototyping, or structured methods, begins
by documenting the current system and proper diagnosing the systems
requirements.
7. TESTING: CABLE OPERATOR MANAGEMENT SYSTEM PROJECT
TESTING
Testing is the process of exercising
software with the intent of finding errors. The Web-app testing is a collection
of related activities with a single goal: to uncover errors in web application
content, function, usability, navigability, performance, capacity and security.
There are several areas of testing
involved in web applications. For the current web application, I used some of
them as follows.
CONTENT TESTING
Content testing attempts to uncover
errors in content of the web application. In addition to examining static
content for errors, this testing step also considers dynamic content derived
from data maintained as a part of database system that has been integrated with
the web application.
Content testing of all web pages is
evaluated for syntactic and semantic errors.
At syntactic level I have verified
the content for spelling, punctuation and any grammar mistakes of all pages
which contain the content of the website.
At semantic level I have verified
for the following aspects.
o
Whether the content is valid or not.
o
Whether the format of the content is good and readable
or not.
o
Whether all the web pages are showing consistent
content or not.
The content
includes the dynamic information about the companies, stock values and flowchart
details which is fetched from the database. The consistency of this information
is thoroughly tested.
DATABASE TESTING
Database
testing is done to uncover the errors which occur as a consequence of fetching
large equities of data from the database, extracting relevant data from the
database, accessing the database using several queries etc,
In this
project, I have tested the application for database errors in following areas.
o
While converting the user request into a database query
o
While fetching dynamic content to the web pages.
o
While opening and closing the active connections to the
database
o
While presenting the raw data fetched from database in
a formatted HTML output.
o
Communication between the web application and the
remote database.
USER INTERFACE
TESTING
All
the interfaces that have been designed are reviewed whether they meet the
customer requirement or not. While testing all interfaces I have verified for
errors as follows.
- Errors
related to specific interface mechanisms for example proper execution of
all menu links that are provided in each web page
- Errors
related to all semantics of navigation and web application functionally
that is provided in each web page.
- Errors
in consistency related to different aspects of the interfaces like font style,
color, size, screen background color etc.,
- Errors
in viewing the interfaces in different web browsers like Microsoft
internet explorer, Mozilla firefox etc.,
INTERFACE MECHANISM TESTING
When a
user interacts with a web application, the interaction occurs through one or
more mechanisms which are called interface mechanisms. Testing done within
theses mechanisms is the interface mechanism testing. This testing is done in
following areas.
Links:
Each navigation link is tested to
ensure that appropriate web page is linked or not. I have listed all the links
in each form to test whether each link is connecting the appropriate page or
not.
Forms:
Testing forms has been done at two
different levels i.e. at minimum level and at more targeted level. At minimum
level I have tested for:
- Whether
labels been correctly defined for fields or not.
- Whether
server is receiving all the information contained in the form and no data
are lost in the transmission between client and server.
- Whether
appropriate default values are available when the user does not select any
item in the selection box.
- Whether
scripts that perform data validation from the client-side are working
properly or not.
At more targeted level I have tested
for:
- Whether
text fields have proper width to enter data.
- Whether
text fields are allowing string length more than specified length.
- Whether
tab order among different controls is in required order or not.
Client Side Scripting:
Each and every function written in
scripting has been tested by Black Box Testing.
I have combined the forms testing
with this client-side script testing, because input for scripting is provided
from forms. Some methods of scripting will be performed in some particular
browsers and in others not. So I have also performed compatibility testing to
ensure that the scripting functions will work properly in all browsers.
USABILITY
TESTS
In this testing I have verified up
to, which level that, users can interact with the system effectively. Tests are
designed to determine the degree to which the web application interface makes
users easy to work with. I have designed test case so that usability testing
can be verified at different levels:
- Usability
test has been performed on each and every individual interface i.e. forms.
- Usability
test has been performed on total web page with related client side
scripting functions.
- Usability
test has been performed on total web application.
COMPATIBILITY
TESTS
As this
is a web application, it should run on different environments like different
computer architectures, operating systems, browsers and network connection
speeds.
As different computing
configurations can result in difference in client side scripting speeds and
display resolution, operating system variance may cause web application
processing issues.
Different browsers produce slightly
different result as we expected, in some cases this results may not be a
problem but in some cases there will be serious errors.
To perform these testing strategies
first we have prepared what are all the client side functions that encounter
problems with different compatibilities. In essence of those we have tested by
identifying different computing platform, typical display devices, the
operating systems supported on the platform, the browsers that are available
with me.
NAVIGATION
TESTING
Navigability
is tested to ensure that all navigation syntax and semantics are exercised to
uncover any navigation errors. (ex: dead links, improper links, erroneous
links). The job of navigation testing is to ensure that the navigation
mechanisms are functional, and to validate that each Navigation Semantic Unit
can be achieved by the appropriate user category.
We have done the navigation testing
in following areas.
·
Navigation links are thoroughly tested.
·
Redirects are properly checked.
·
Is the target page to a navigation link is correct or
not.
·
Is the link caption meaningful or not.
8. DEPLOYMENT:
The error-free project, which passed
all the tests, is now deployed at the client environment in this phase.
FUTURE ENHANCEMENTS
This project can be further enhanced to provide greater flexibility and performance with certain modifications whenever necessary.
1 comment:
Educational products suppliers
Post a Comment