ดาวน์โหลดงานนำเสนอ
งานนำเสนอกำลังจะดาวน์โหลด โปรดรอ
ได้พิมพ์โดยKanok Thaibangouy ได้เปลี่ยน 10 ปีที่แล้ว
1
Course 254 451 Software Engineering SE Overview and Introduction
2
(c) Michael Brueckner 2005-2006 2 Introduction to Software Engineering Terminology คำศัพท์เฉพาะทาง : software, software engineering, software engineers, software products Difference ความแตกต่าง between software engineering and systems engineering Difference between software engineering and computer science
3
(c) Michael Brueckner 2005-2006 3 Software Software comprises รวมถึง computer programs and data plus technical descriptions used to run the programs. Def. 1957 (John W. Turkey): Software is everything in a computer which is not hardware. In legal เกี่ยวกับกฎหมาย / ได้รับอนุญาตตาม กฎหมาย view software is intellectual work ทรัพย์สินทางปัญญา
4
(c) Michael Brueckner 2005-2006 4 Software Engineering All activities which lead to a software product Get all requirements Design the system Programming Testing the system Track the versions Manage the people
5
(c) Michael Brueckner 2005-2006 5 Software Engineers People who apply SE methods Special Software Engineers Testing engineers System analysts Software designers ...
6
(c) Michael Brueckner 2005-2006 6 SE vs. CS Computer Science is the theory of programming SE is more the practice of doing it
7
(c) Michael Brueckner 2005-2006 7 Properties of Software Developed พัฒนา once หนึ่งครั้ง Maybe in many versions Can be distributed เผยแพร่ at low cost CD-ROM / DVD Download By „air“ Can be used without waste ของเสีย
8
(c) Michael Brueckner 2005-2006 8 Software Products-1 Generic โดยทั่วไป products Customized ซึ่งสร้างตามคำสั่งเฉพาะของ ลูกค้าคนเดียว products We have to manage versions
9
(c) Michael Brueckner 2005-2006 9 Software Products-2 Application software Office programs Utilities Multimedia software Security software Funware System software Operating systems Drivers
10
(c) Michael Brueckner 2005-2006 10 Software Development Process Processes for different types of software Application development Operating system development Embedded software (=programmed HW device) Maybe different processes Different customers, users Different requirement structure
11
(c) Michael Brueckner 2005-2006 11 Software Development Process Basic Ideas Requirements – Specification ข้อจำกัด Development – Implementation ทำให้มีผล Validation การให้เหตุผล – Distribution Evolution วิวัฒนาการ – more versions! Process models ต้นแบบ = simplified ทำให้ ง่ายขึ้น description of SW development
12
(c) Michael Brueckner 2005-2006 12 Overview of the course The following slides will be
13
(c) Michael Brueckner 2005-2006 13 Project Management Defining a process model Planning projects Structuring activities Team building Controlling
14
(c) Michael Brueckner 2005-2006 14 Requirement Management Asking questions Structure the requirements Create a reference-oriented requirements base Make requirements understandable
15
(c) Michael Brueckner 2005-2006 15 Design Management Find a solution to the requirements Software specification Reviewing Structured design methods Object oriented design
16
(c) Michael Brueckner 2005-2006 16 Special Topic: Component Based Development Internet based SE Company wide software development Many departments work together Application development Example: E business software
17
(c) Michael Brueckner 2005-2006 17 Quality Management Software Quality Assurance Verification Are we building the product right? Does the system meet the specification? Validation Are we building the right product? Does the system do what the user needs? Testing procedures
18
(c) Michael Brueckner 2005-2006 18 ISO 9000/9002 The standard Certification process ... and after certification?
19
(c) Michael Brueckner 2005-2006 19 Software Development Economy 60% development costs 40% testing costs Distribution varies with the process model adopted
20
(c) Michael Brueckner 2005-2006 20 Methods of Software Engineering Structured approach to Model descriptions Rules Recommendations การแนะนำ Process guidance การแนะแนว
21
(c) Michael Brueckner 2005-2006 21 Tools in Software Engineering CASE Upper CASE, used for Requirements engineering Design engineering Lower CASE, used for Programming Debugging and testing
22
(c) Michael Brueckner 2005-2006 22 Special Topic: Practices of Software Engineering In project management In working out an appropriate process model In applying software engineering methods In asking: What is good software?
งานนำเสนอที่คล้ายกัน
© 2024 SlidePlayer.in.th Inc.
All rights reserved.