This article written by Scott Barber ( Matineh Bin Kundan Reference Author in Website )
Abstract touch such as web development organization" What is the industry standard response time a web page?"
Generally accepted standards large web because different personal have unidentify whether a particular wabe page. Any responsibly detect an "acceptable".This paper demonsratrate standard term design a criteria and explores critical items considered in determining appropriate respone time goals with out websites.
1.Introduction
-The author, active member International Performance testing community and as an experienced practitioner.
-He find what the industry standard responses status in times until target.
-Relate by moment Web sites acceptable, Its 1.5 seconds a reasonsable benchmarks.
-His personal answer are just "depends on"
-The answer also depend by his friend Joe Strazzere.
-He determine how fast your application,convert information into explicit, testable requirements- might the addresses
2.Considerations Affecting Performance Expectations
-3 broad categories:
*User psychology
*System considerations
*Useage considerations
*2.1 User psychology- overhidden with most critical part of evaluating performance
- navigate base by user are internet expert
- Pages return in less than 5 seconds.
- notice performance 5 and 8 second, at about 15 seconds.
- Personal tolerance -be patient before quite or requested a section.
- Received message -wasn't submitted properly,server gone down or
the internet connection had been dropped.
- psychology- several key factors that determine what is and isn't
acceptable performance
- First respone accustomed to based on previous experience- mother high
tolerance
- Activity type MP3 or MPEG video- waiting next page
- Tax preparation system
- surfling intent-research newest technology gadgets
- variable are no industry standard but describe rules later-compare against.
collecting information performance requirements.
2.2 System Considerations
- How fast enough
- doomed to fielding a system with poor perfomance
- perfomance costs.Example- system hardware
- network and/ or internet bandwidth of the system
- geographical replication
- software architecture
- dedicated- well- documented and well- understood aspect of engineering- he want spend more time it here.
( other can we view inside )
-stakeholders need to decide what kind of perfomance
-based purely on the cost to achieve
-cost and feasiblity are important
-cost difference between building a system and building a system with"fast"- sometime
prohibitive.
-performance against the cost
-invest to improve performance
-System consideration include
- system,network and/or Internet bandwidth of the system,geographical replication and
software architecture
-well-documented and well - understoond aspect performance engineering.
2.3 Usage Considerations
-consideration usage but separate from user psychology
-way the Web site
-asking any application a shopping-fast- primarily by employees
-asking financial
-asking a site containing current news
-An internal human resource data entry
-satisfied than shopping site
-news site be fairly slow as appears before graphies
-Interactive site need to be faster than most static site
-work-related activities need to be faster for recreational purpose
-this consideration are very specific
-documentation available by individual
-application and associated user base
-to determine the performance toletance of expected users as compared overall
-user psychology and system considerations.
3.Collecting Information About Performance Requirements
3.1 User Expectations
3.2 Resource Limitations
3.3 Stakeholder Expectations
4.0 Determaning and Documenting Performance Requirements
4.1 Speed Requiements
4.2 Scalability Requirements
4.3 Stability Reguirements
5.0.Composite Requirements
5.1 Composite Requirements
5.2 Composite Goals
6.0 Conclusion
7.0 About the Author
8.0.References
==============================
Jabatan Multimedia Pendidikan
Fakulti Pendidikan
Universiti Teknologi Malaysia
Skudai
Johor
e-learning site: http://elearning.utm.my/
Course : Web-Based Multimedia Development
Code : MPT 1393
Credit : 3
Students: Masters of Educational Technology
Session : Semester 1 ( 2009/2110 )
Lecturer: Dr. Dayang Hjh Tiawa Awang Hj Hamid
Room : C15-101-0, Fakulti Pendidikan, UTM.
Phone : 07-5534397
e-mail : drdayang@utm.my
GIVE ANY COMMENT IF YOU NEED OR NECESSARY BELOW SITE.THANK YOU!
==================================
Subscribe to:
Posts (Atom)