Software Engineering of Web Applications SE Team 6 & SE Team 13 4 -28 -05
Introduction of Team Members n n n Chris Gaul Ruth Miller Jefferson Hanifah Ryan Dunn Evan Tritsch Amanda Jantz
Overview n n n What is Web Engineering? Formulation and Planning for Web Engineers Analysis Modeling for Web Apps Design Modeling for Web Apps Testing Web Apps Comparison Between Normal Software Engineering vs. Web Engineering
Methods n n Communication Requirements Analysis Design Testing
Processes n n n Delivery Change Timelines
Customer Communication n n Business Analysis Formulation
Framework n n Planning Modeling Construction Deployment
Web Engineering Application Development Team n n Content Developers Web Publisher Web Engineer Business Domain Expert
Application Support Staff n Support Specialist • Enhancements and adaptations to the application itself n Administrator (Webmaster) • Update content and layout changes
Creating a Web App with Outsourcing n n n Analysis of functionality should be done internally Design a rough draft Project Schedule (dates & milestones) List of Responsibilities Degree of interaction between contractor and vendor should be identified
Creating a Web App “In-House” n n n n Clearly stated requirements and goals Incremental project strategy Perform a Risk Analysis Quick Time Estimate Development description Establish a schedule Defined project tracking mechanisms
Analysis Modeling for Web Apps Defined n Focuses on 3 questions: • What information is to be presented or manipulated? • What functions are to be performed for the end -user? • What behaviors will the Web. App exhibit as it presents content and performs functions? n Answers are represented as part of an analysis model containing UML representations.
Requirements n n n User Hierarchy Developing use-cases Refining the use case model
Models n n Analysis Model Content Model • Defining Content Objects • Content Relationships and Hierarchy • Analysis Classes for Web Apps n n n Interaction Model Functional Model Configuration Model
Relationship-Navigation Analysis n n Key Questions Navigation Analysis
Design Issues n Quality • • Security Availability Scalability Time-to-market n Goals • • Simplicity Consistency Identity Robustness Navigability Visual Appeal Compatibility
Visual Design n Interface Design • The structure and organization of the user interface. n Aesthetic Design • Graphic design • Look and Feel n Content Design • Layout, structure, and outline for all content • Relationship between objects
Control Design n Architecture Design • Both content architecture and Web App architecture n Navigation Design • The navigational flow between content objects and web app functions n Component Design • Processing logic required to implement functional components
How do we do it n n n Hypermedia Design Patterns Object-Oriented Hypermedia Design Method Design Metrics
Testing Web Applications n More Complex then normal Application Testing • Big difference is that technology variables multiply in web applications. • Different technologies are patch worked together to bring a web application to life. n Types of Testing • • Content Interface Navigation Component Configuration Security Performance
Testing Web Applications n Content Testing • Text Errors • Grammatical mistakes • Errors in consistency • Cross referencing errors • Graphical Representations • Dynamic contented delivered from databases
Testing Web Applications n Interface Testing • Implementation mechanisms or omissions • Inconsistencies • Ambiguities • Anything interfaced inadvertently into the interface
Testing Web Applications n Component Testing • Testing each component encapsulated within the web site. n Configuration Testing • Client and server environment problems. n n Create a matrix of hardware, operating systems, browsers, hardware platforms and communications protocols. Test each possible configuration to get all the errors associated with each configuration.
Testing Web Applications n Security Testing • Exploit vulnerabilities in the Web App and environment. • Demonstrate that a security breach is possible n Performance Testing • Response time and reliability effected by traffic n Identifying components responsible for the problems • Load Testing n n n N, concurrent users T, online transactions D, Data Load P, Overall throughput P=DXTXN
![Comparison Between Software and Web Engineering n n Planning [1] Design [1] Production [1]](https://present5.com/presentation/ca0a265f4f4d9d8e4d8d0b24151be134/image-25.jpg "Comparison Between Software and Web Engineering n n Planning [1] Design [1] Production [1]")
Comparison Between Software and Web Engineering n n Planning [1] Design [1] Production [1] Maintenance [1]
Planning n At this step, in both software and web engineering, they try to find the user needs, create schedule until the application is deployed
Design n n In the design of a software, the GUI has to be “user friendly, ” and reliable In the design of web applications, the user must be able to find data and links easily. Also, the user must be able to load the applications very fast.
Production n In software and web engineering, programmers need to test before the applications are launched or deployed
Maintenance n n In software engineering, the programmers provide updates and patches for the software every time bugs have been found In web engineering, the team members need to maintain the sites up-to-date
Resources 1. http: //www 3. ibm. com/ibm/easy/eou_ext. nsf/p ublish/572
Summary
Скачать презентацию Software Engineering of Web Applications SE Team 6
ca0a265f4f4d9d8e4d8d0b24151be134.ppt