Chapter 1: Introduction Omar Meqdadi SE 2730 Lecture 1 Department of Computer Science and Software...
-
Upload
chester-eaton -
Category
Documents
-
view
225 -
download
1
Transcript of Chapter 1: Introduction Omar Meqdadi SE 2730 Lecture 1 Department of Computer Science and Software...
1
Chapter 1: Introduction
Omar MeqdadiSE 2730 Lecture 1
Department of Computer Science and Software Engineering University of Wisconsin-Platteville
2
Topic Covered
FAQs about software engineering Professional and ethical responsibility
3
FAQs about software engineering
What is system? What is software? What is software engineering? What is the difference between software engineering and
computer science? What is the difference between software engineering and
system engineering? What is a software process?
4
FAQs about software engineering
What are the costs of software engineering? What is CASE (Computer-Aided Software Engineering) What are the attributes of good software? What are the key challenges facing software engineering?
5
What is a system?
A purposeful collection of inter-related components working together towards some common objective
A system may include software, mechanical, electrical and electronic hardware and be operated by people
System components are dependent on other system components The properties and behaviour of system components are
inextricably inter-mingled
6
What is software?
Computer programs and associated documentation Software products may be developed for a particular
customer or may be developed for a general market Software products may be
Generic - developed to be sold to a range of different customers
Bespoke (custom) - developed for a single customer according to their specification
7
What is software engineering?
Software engineering is an engineering discipline which is concerned with all aspects of software production
Software engineers should Adopt a systematic and organised approach Use appropriate tools and techniques depending on the
problem to be solved Follow the development constraints and the resources
available
8
What is the difference between software engineering and computer science?
Computer science is concerned with theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software
Computer science theories act as a complete underpinning for software engineering
9
What is the difference between software engineering and system engineering?
System engineering is concerned with all aspects of computer-based systems development including hardware, software and process engineering. Software engineering is part of this process
System engineers are involved in system specification, architectural design, integration and deployment
10
Software Engineering
Quality Focus
Process
Methods
Tools
11
What is a software process?
A set of activities whose goal is the development or evolution of software
Generic activities in all software processes are: Specification - what the system should do and its
development constraints Development - production of the software system Validation - checking that the software is what the
customer wants Evolution - changing the software in response to changing
demands
12
What is a software process model?
A simplified representation of a software process, presented from a specific perspective
Examples of process perspectives are Workflow perspective - sequence of activities Data-flow perspective - information flow Role/action perspective - who does what
Generic process models Waterfall Evolutionary development Formal transformation Integration from reusable components
13
What are software engineering methods?
Structured approaches to software development which include system models, notations, rules, design advice and process guidance
Model descriptions Descriptions of graphical models which should be produced
Rules Constraints applied to system models
Recommendations Advice on good design practice
Process guidance What activities to follow
14
What is CASE (Computer-Aided Software Engineering)
Software systems which are intended to provide automated support for software process activities. CASE systems are often used for method support
Upper-CASE Tools to support the early process activities of
requirements and design Lower-CASE
Tools to support later activities such as programming, debugging and testing
15
What are the attributes of good software?
The software should deliver the required functionality and performance to the user and should be maintainable, dependable and usable
Maintainability Software must evolve to meet changing needs
Dependability Software must be trustworthy
Efficiency Software should not make wasteful use of system resources
Usability Software must be usable by the users for which it was designed
16
Problems with Software Production
Complexity Conformity - conform to the existing process or have the process
conform to the software Changeability - Software can “easily” be changed, but a bridge is
almost impossible to move Invisibility - software is very hard to visualize Brook’s “No Silver Bullet” [IEEE Computer 9(4), 1987]
Software is very difficult to develop, and most likely will not get easier. Reuse is one solution suggested. In 20 years, 6% per year production improvement.
17
What are the key challenges facing software engineering?
Legacy systems Old, valuable systems must be maintained and updated Coping with legacy systems, coping with increasing diversity and
coping with demands for reduced delivery times Heterogeneity
Systems are distributed and include a mix of hardware and software Delivery
There is increasing pressure for faster delivery of software
18
What are the costs of software engineering?
Roughly 60% of costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs 50% of all software projects fail
Never delivered/completed Do not meet requirements or user needs Excessive failures (bugs) Excessively over budget or late
Costs vary depending on the type of system being developed requirements of system attributes such as performance and system
reliability
19
Professional and ethical responsibility
Software engineering involves wider responsibilities than simply the application of technical skills
Software engineers must behave in an honest and ethically responsible way if they are to be respected as professionals
Ethical behaviour is more than simply upholding the law
20
Issues of professional responsibility
Confidentiality Engineers should normally respect the confidentiality of
their employers or clients irrespective of whether or not a formal confidentiality agreement has been signed
Competence Engineers should not misrepresent their level of
competence. They should not knowingly accept work which is out with their competence
21
Issues of professional responsibility
Intellectual property rights
Engineers should be aware of local laws governing the use of intellectual property such as patents, copyright, etc. They should be careful to ensure that the intellectual property of employers and clients is protected
Computer misuse Software engineers should not use their technical skills to misuse other
people’s computers. Computer misuse ranges from relatively trivial (game playing on an employer’s machine, say) to extremely serious (dissemination of viruses)