Escolar Documentos
Profissional Documentos
Cultura Documentos
Ansar Siddique
27/09/X
Introduction
• Failed to address users’ needs and issues such as content management and
scalability (Business Issues)
• Difficulties in using the Web site and finding relevant information of
interest (Usability Issues)
• Slow response (Performance Issues)
• Web site crashes (Reliability Issues)
• Security breaches (Privacy Issues)
Ad hoc Approach
• Web application development is not just a simple web page creation, It
involves planning, web architecture and system design, testing, quality
assurance and performance evaluation, and continual update and
maintenance of the systems as the requirements and usage grow and
develop.
• So, Ad hoc approach is not a appropriate option for the development of
large and complex web based systems
Impacts of Faulty Web Over Business
• Lack of vision
• Shortsighted goals
• Flawed design
• Wrong team members
• Web Engineering uses scientific, engineering, and management principles and systematic
approaches to successfully develop, deploy, and maintain high-quality Web systems and
applications
functions
Essential Steps in Development
• Understand the overall function & environment in which system will be
used
• Identifying & specifying technical & non technical requirements
• Developing architecture
• Addressing non-technical issues
When building a web-based system there are a number of elements that need to be
carefully considered, a number of which relate to the fact that we are often exposing
our application to the entire Internet
Issues include:
• Security: Security needs to be carefully considered and addressed. We cannot assume that only
one user will have access to the software and the system may come under numerous attacks
from the greater Internet.
• Scalability: Many web-based systems must be able to scale considerably. Again it is not a case
of one application with one user. We may have 10 people using the system simultaneously or we
may have to handle millions of requests per second (think Google, Hotmail or Amazon).
• Robustness: A web-based application must be robust, that is it should not fail or if it does it
should fail gracefully. If a desktop application crashes it will often impact one user, whereas if a
commercial website becomes unavailable then business may be lost from thousands of clients
WWW Architecture…
• Ask questions
• Understand business needs and the product
• Identify users and user groups
• Build use cases, scenarios
• Develop a project plan, even if it is very brief
• Model what you are going to build and review it constantly
• Don't reinvent the wheel
• Use reusable components
• Don't rely on users to test your system; you better test it thoroughly first
• Don't be afraid to think ahead (e.g., does the company plan to merge with
another company in a year)
Design Modeling
• What tasks users will perform and the functionality required to support
them?
• Simplicity
• Consistency
• Aesthetics
• Interface
• Navigation
• Architecture
• Content and structure
• Functional components
• Security and privacy
Formulation