web engineering

1. Web Engineering
Lecture-03

2. Lecture Outline
 Web Project Management
 Steps to Successful Development
 Web System Design: Challenges
 Web Testing and Evaluation

3. Web Project Management

4. Web Project Management
Project management is the discipline of initiating, planning,
executing, controlling, and closing the work of a team to
achieve specific goals and meet specific success criteria.
Poor project management will defeat good
engineering; good project management is a
recipe for success

5. Web Project Management (Cont.)
 Project management is the application of processes, methods,
knowledge, skills and experience to achieve the project
objectives.
 The purpose of project management is to ensure that all the
key processes and activities work in harmony.
 Building successful Web-based applications requires close
coordination among various efforts involved in the Web
development cycle.

6. Web Project Management (Cont.)
 Attributes that a good web project manager should ideally
have
 Leadership skills
 Skill in negotiating win-win solutions between stakeholders and the
project team
 Staying calm particularly during turbulent times
 Desire to hold the team accountable for deliverables
 Ability to earn the respect of the team regardless of reporting
relationships
 Good Web Project Manager should have:
 Web project management experience
 Web development experience
 Ability to communicate with everyone

8. Steps to Successful Development

9. Steps to Successful Development (Cont.)
 Successful development of Web systems and applications
involves multiple interactive steps:
 Understand the system’s overall function and operational environment,
including the business objectives and requirements, organization
culture and information management policy.
 Clearly identify the stakeholders — that is, the system’s main users and
their typical profiles, the organization that needs the system, and who
funds the development.
 Elicit or specify the (initial) functional, technical, and nontechnical
requirements of the stakeholders and the overall system. Further,
recognize that these requirements may not remain the same; rather,
they are bound to evolve over time during the system development.
 Develop overall system architecture of the Web-based system that
meets the technical and nontechnical requirements.

10. Steps to Successful Development (Cont.)
 Steps (Cont.)
 Identify subprojects or subprocesses to implement the system
architecture. If the subprojects are too complex to manage, further
divide them until they become a set of manageable tasks.
 Develop and implement the subprojects.
 Incorporate effective mechanisms to manage the Web system’s
evolution, change, and maintenance. As the system evolves, repeat the
overall process or some parts of it, as required.
 Address the nontechnical issues, such as revised business processes,
organizational and management policies, human resources
development, and legal, cultural, and social aspects.
 Measure the system’s performance, analyze the usage of the Web
application from Web logs, and review and address users’ feedback
and suggestions.
 Refine and update the system.

11. Web System Design: Challenges

12. Web System Design: Challenges
 Satisfying diversified user needs
 Users do not tolerate much margin of error or failure. Web system slow down, failure, or
security breach may cause a loss of its customers — probably permanently
 Web applications are becoming mission-critical, there is greater demand
for improved reliability, performance, and security of these applications
 Large-scale Web system design is a complex and a challenging activity as it
needs to consider many different aspects and requirements
 Successful Web application deployment demands consistent Web site
availability, a better understanding of its performance, scalability, and load
balancing.
 Terms like scalability, reliability, availability, maintainability, usability, and
security to describe how well the system meets current and future needs
and service-level expectations

13. Web System Design: Challenges (Cont.)
 Challenges to design and develop sustainable Web systems for
better can be categorized into following:
 Usability — interface design, navigation (Becker & Mottay 2001),
 Comprehension,
 Performance — Responsiveness,
 Security and Integrity,
 Evolution, Growth, and Maintainability
 Testability

14. Web Testing and Evaluation

15. Web Testing and Evaluation
 Testing plays a crucial role in the overall development process
 However, testing and evaluation are neglected aspects of Web
development. Many developers test the system only after it had met with
failures or limitations have become apparent, resorting to what is known
as retroactive testing.
 What is desired in the first place is proactive testing at various stages of the
Web development lifecycle.
 Benefits of proactive testing includes:
 Assurance of proper functioning
 Guaranteed performance levels
 Avoidance of costly retroactive fixes
 Optimal performance
 and Lower Risk

16. Web Testing and Evaluation (Cont.)
 Testing and validation is difficult and expensive task.
 Should not be seen as one time activity
 Needs to consider a broad view and follow a more holistic approach
to testing
 From design all the way to deployment, maintenance, and continual
refinement.
 The test planning needs to be carried out early in the project
lifecycle.
 A test plan provides a roadmap so that the Web site can be evaluated
through requirements or design stage. It also helps to estimate the time
and effort needed for testing — establishing a test environment, finding
test personnel, writing test procedures before any testing can actually
start, and testing and evaluating the system.

17. Web Testing and Evaluation (Cont.)
 Web Testing Categories Lam (2001)
 Browser compatibility
 Page display
 Session management
 Usability
 Content analysis
 Availability
 Backup and recovery
 Transactions
 Shopping, order processing
 Internationalization
 Operational business procedures
 System integration
 Performance
 Login and security

18. Assignment # 2
Write a comprehensive note on Non-Functional requirements
for your term web applications with focus on scalability,
reliability, availability, maintainability, usability, and security.
Rules:
Provide examples relevant to your project.
Maximum two pages with font size of 11.
Document should follow a structure with proper heading and paragraph spacing.
CR collect all documents and compile them into a zip file and email me
File name and subject of e-mail should read like this: Assignment 1_13-Arid-1218_Syed Faizan
Haider
Deadline: Next week in web engineering class

19. Reading Material
 http://www.pmhut.com/characteristics-of-great-project-manager
 https://cdn.projectsmart.co.uk/img/website-development.png