LECTURE 1 - Software & Web Engineering Processes and Design
Uploaded by
George MobisaLECTURE 1 - Software & Web Engineering Processes and Design
Uploaded by
George MobisaWEB DESIGN
• LECTURE 1 - Software & Web Engineering
Processes and Design
What is Software Engineering?
Definition:
"software engineering The entire range of activities
used to design and develop software, with some
connotation of "good practice"."
Oxford Dictionary of Computing (fourth edition)
Web Engineering
• Can be simply defined as "Software
Engineering for the web."
• The development of software which will be
used in a web or E-Commerce environment.
• Software Engineering principles and processes
can generally be applied to Web Engineering.
• Some additional processes are required.
Software
Engineering Layers
tools
methods
process
a quality focus
The life-cycle model
• Requirements Analysis
• Design
• Implementation - coding
• Testing
• ---------------------------------
• Support
• Maintenance
Requirements Analysis
• Discussions with the client
– What is the purpose of the website?
– Who will be accessing the website?
– What is the expected outcome?
– Agree timescales & testing criteria.
• Documentation
– Requirements specification.
– Functional Specification.
– Test specification.
Design
• Design issues in detail
– How will the website be structured and linked?
– What will be the content of the website?
– Will there be a common style/theme? Perhaps it must fit
in with a corporate image.
– Will there be any additional processing?
• Prototyping
• Documentation
– Design specification
STOP!!
• Before moving from Design to
Implementation:
– Ensure all the client's requirements are met.
– Ensure the tools you are planning to use are
appropriate.
Implementation - coding
• Development of the complete product.
• Use of appropriate development tools.
• Use of appropriate programming/scripting
languages.
• Documentation
– The deliverables here are the code and web pages
themselves.
Testing - Phase 1
• Websites are generally developed locally on a
client computer.
• Test that all content is correct. equivalent to
proof-reading a book.
• Test that all links work appropriately.
• Test scripts and code produce the desired
behaviour.
• Checks should be made that the website
performs correctly in target browsers.
Testing - Phase 2
• Transfer from the development environment
(local client) to the destination environment.
• If possible still isolate from public access.
• Check that all links (local & external) function
as expected.
• Check all scripts and code again for
unforeseen problems.
• Check speed of access (particularly graphics).
Testing - Phase 3
• Acceptance Testing
– Allow the client access to perform their own
testing.
– The client should formally test the software
according to the agreed Test Specification.
– When complete the project should be formally
signed off.
– At this point the website will be released for
operational use.
Support / Maintenance
• The client may require further support and
documentation / training.
• On-line documentation may be required.
• Maintenance will be required
– Updating web content.
– Regular checking of links to ensure they are still
available.
– Addition of new features.
Quality Control
• Quality Assurance
– design and monitoring of appropriate standards
and procedures to achieve high quality outcomes
from system development activities.
• Quality Control
– conformance to this regime by all members of a
system development team.
Operating a quality assurance regime
• Quality manual sets out:
– standards to be observed;
– procedures to be followed;
– quality control checks to be applied.
• Each development project will derive from this
a specifically tailored quality plan.
Change Control
• Why?
– Ensure that all changes can be tracked and
monitored.
– Vital when teams of developers are working on a
project.
– Quality.
• Tools
– Record and track changes to a system. e.g.
Microsoft SourceSafe
Website
Development Tools
• Web Content
– HTML (Hyper Text Markup Language)
– DHTML (Dynamic HTML)
– Java & Java Applets
– XML, Graphics, WAP
• Scripting
– Javascript (client scripting)
– CGI (server-side scripting)
• Integrated Development Environments
SUMMARY
• Web Engineering has a lot of similarities with
Software Engineering.
• Many of the same design and testing
processes can be applied.
• Many existing development & configuration
tools can be applied to Web Engineering.
• Some specific tools and techniques will be
covered in this module.
