14 Feasibility study Requirements elicitation and analysis Requirements specification Requirements validation Feasibility report System models. User and system requirements[r]
Trang 11
Trang 22
Trang 33
Trang 41. Introduction to Web Technologies
2. The web application development
process
3. Web Project Management
4. Requirement Engineering
5. Modeling web applications
6. Implementing and testing web
applications
7. Web application architecture4
Trang 58. Introduction to HTML
9. HTML Links and navigation
10. Adding Image, audio and video files to
web pages
11. Tables in HTML
12. HTML FORMS
13. HTML 5 Form elments
5
Trang 614. Introduction to Cascading
Style-sheets (CSS)
15. Page Layout
16. CSS Properties
17. CSS 3
6
Trang 7• What is web?
• Web applications
• The case for web engineering
applications
7
Trang 8• Web engineering extends Software
Engineering to Web applications
• Why web engineering?
• Web applications
• Integration:
– Internal : with existing legacy systems
– External : with Web services
– Integration issues: correct interaction
8
Trang 9• Development Process model
• Requirement for a web development
process model
– A modern process model derived from the
work on the UML and associated process
incremental and iterative process
9
Trang 10• Software specification:
defined
– critical stage (can lead to problems in design and implementation)
10
Trang 11• Project management is the process of planning, organizing, motivating and controlling resources and procedures
to develop a software/web project
• Projects need to be managed
– to ensure budget and time constraints
Trang 12• Project Managers Tasks
ü Project planning
ü Risk management
ü People management
ü Reporting
ü Proposal writing
12
Trang 13• Requirements Engineering: the principles, methods,
& tools for drawing, describing, validating, and managing project goals and needs
• It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.
the application domain, the people involved and the organisation developing the requirements.
• Functional requirements
• Non-functional requirements
common to all processes
– Requirements elicitation;
– Requirements analysis;
– Requirements validation;
– Requirements management
13
Trang 14Feasibility
study
Requirements elicitation and analysis
Requirements specification
Requirements validation
Feasibility
report
System models
User and system requirements
Requirements document
The requirements engineering process
Trang 15• Process of developing abstract models
of a system
notation - UML
• Requirement modeling
• Content modeling
• Navigational modeling
among them
• Presentation modeling
15
Trang 16<<page>>
User registration
page
<<presentationUnit
>>
Logo
<<image>>
logo
<<text>>
title
<<presentationUnit>
>
<<textinput>>
name
<<textinput>>
password
<<textinput>>
<<button>>
submit Presentation Modelling
Trang 17• When we have decided the ‘What’ of the web application i.e.
• We are ready for ‘how’ i.e to
implementation phase
17
Trang 18• Testing is an activity conducted to
evaluate the quality of a product and to improve it by identifying defects and
problems
• If we run a program with the intent to
find errors, then we talk about testing
• By testing we determine the quality state
of the system
18
Trang 19• Technologies for web development
19
Trang 20• Software system architecture
is the high-level (most general) design
on which the system is based
a program)
• It contains one or several routines
communicate)
20