Presentation is loading. Please wait.

Presentation is loading. Please wait.

Course 254 451 Software Engineering Michael Bruecknerphone055-261 000-4 (ext. 3233) อ. มิช่า officeSC2-417, by appointment.

Similar presentations


Presentation on theme: "Course 254 451 Software Engineering Michael Bruecknerphone055-261 000-4 (ext. 3233) อ. มิช่า officeSC2-417, by appointment."— Presentation transcript:

1 Course Software Engineering Michael Bruecknerphone (ext. 3233) อ. มิช่า officeSC2-417, by appointment

2 (c) Michael Brueckner 2005/ Software Engineering 2 Software Engineering  uses appropriate engineering principles in order to obtain economically software that is  reliable  works efficiently on real machines  studies such principles

3 (c) Michael Brueckner 2005/ Software Engineering 3 Basic Questions of SE  What is the problem to be solved?  Which characteristics do the problem related entities have?  How will the solution be realized?  How will the solution be constructed?  How can errors be uncovered?  How to deal with support after release to the customer?

4 (c) Michael Brueckner 2005/ Software Engineering 4 SE Process Model-2  Basic SE process models  Linear Model (Waterfall)  Evolution Model (Prototyping)  Formal Transformation Model  Reusable Components Model

5 (c) Michael Brueckner 2005/ Software Engineering 5 Project Management  We focus เพ่งความสนใจ on IS projects  We focus on practical ที่ขึ้นอยู่กับความเป็น จริง steps  We cover the whole lifecycle of a project  We don‘t want to use many software tools

6 (c) Michael Brueckner 2005/ Software Engineering 6 Project Management / Overview  Introducing Project Management  Some Terms  The Lifecycle of Projects Lifecycle All processes from the start till the end of a project. Usually the lifecycle is divided into phases with certain milestones. Some phases maybe have to be worked out two or more times.

7 (c) Michael Brueckner 2005/ Software Engineering 7 Project Management / Introduction  First question: Do we need a project?  Standard Software Solution  Outsourcing  Co-operation  To much to do (feasibility ซึ่งเป็นไปได้ )  New processes = no software Outsourcing Give some work out of the company and let it be done by special partners. This leads to a concentration on your main business. Feasibility The ability to do a complex work or project: technical, economic, legal, operational, schedule.

8 (c) Michael Brueckner 2005/ Software Engineering 8 Standard Software Solution  Can you solve แก้ปัญหา the problem by a standard software?

9 (c) Michael Brueckner 2005/ Software Engineering 9 Project Management / Introduction  Project Management is Information Management applied ที่ประยุกต์ได้ to projects  Problem analysis (getting information)  Requirements (analyse วิเคราะห์ problem solutions)  Design the solution  Programming & Implementation  Testing & Quality Assurance  Installation & Service  Migration Specification

10 (c) Michael Brueckner 2005/ Software Engineering 10 Software Migration  Migration: make software available in a different environment  Example: MS Access to MySQL

11 (c) Michael Brueckner 2005/ Software Engineering 11 Project Management / Some Terms  Project  Project Management  Phase  Milestone  Deliveries = Project Document  Work Breakdown Structure  Time scheduling  Work scheduling

12 (c) Michael Brueckner 2005/ Software Engineering 12 Project Management / Project  Examples: I build my own PC from spare parts: 1 person with limited budget, 1 month time schedule Bring a man on the moon: people with Mio. USD-budget, 7 years time schedule Implementation of an information system: 50 people, 1 Mio. budget, 6 months time schedule A project is a temporary ที่เป็นการชั่วคราว endeavor ความ พยายาม with a budget งบประมาณ and a timeline to achieve สำเร็จ particular aims and to which project management can be applied.

13 (c) Michael Brueckner 2005/ Software Engineering 13 Project Management / Definition  PM standardizes ทำให้เป็นมาตรฐาน and structures สร้างโครงสร้าง the basic จำเป็นที่สุด tasks in a project  PM aims at completing a project in the most cost- effective and efficient ซึ่งมีประสิทธิภาพ way Project Management is the application of knowledge, skills, tools, and techniques to the activities in a project. Project management comprises five basic tasks – Initiating ริเริ่ม, Planning วางแผน, Executing ดำเนินการ, Controlling ตรวจสอบ, Closing จบ

14 (c) Michael Brueckner 2005/ Software Engineering 14 Project Management / Phase  Example: Project Start (Phase)  Activities: get the manpower กำลังคน, get the money, get the room and equipment, define the project‘s deadline กำหนดเวลา สุดท้ายที่ต้องทำให้เสร็จ  Milestone: Project application การขอ is signed  Documents: „Project Structure“, „Project Plan“ (time and budget), „Project Mission“ จุดมุ่งหมาย A Project Phase is a set of activities in a project which form a major ส่วนใหญ่ part of the work. The project phase is completed with a project milestone and defined documents that have to be delivered.

15 (c) Michael Brueckner 2005/ Software Engineering 15 Project Management / Milestone Example: End of Project (Milestone):  Completes the phase "Installation and Maintenance“  Delivered documents: "Project Completion Approval" signed by Project Board A Milestone completes a project phase. It is defined as a date at which required ต้องการ documents have to be delivered. MS1 Phase 1Phase 2 MS2...

16 (c) Michael Brueckner 2005/ Software Engineering 16 Project Management / Deliveries, Project Document For some results in the project there must be substitute คนหรือสิ่งที่เข้าแทนที่ documents, such as for executable code. A Project Document is a document which has a defined scope ขอบเขต and content สาร relevant เข้า ประเด็น to the project. Every Project Document must have an author (responsible for delivering ส่ง at time เกิดขึ้นเหมาะสมกับเวลา and in sufficient พอเพียง quality) and a review การทบทวน team (one or many persons).

17 (c) Michael Brueckner 2005/ Software Engineering 17 PM / Work Breakdown Structure-1 The Work Breakdown Structure (WBS) is a plan which defines all the work that has to be done until the project is completed. Information investigation 10 days Keywords from "Principles of IS" "Journal of IM" / Web Scheduling (16 lectures, 15 labs) 2 days How many slides per class, types of exercises Excel Outline of slides days Analyzing keywords Brainstorming..... Example / Part of the WBS of a course

18 (c) Michael Brueckner 2005/ Software Engineering 18 PM / Work Breakdown Structure-2  Sometimes you add รวม the dependencies การพึ่งพาอาศัย / เมืองขึ้น to the WBS  This called a task network (Pressman, p. 180/181) Here you see the dependencies of the tasks and a timeline

19 (c) Michael Brueckner 2005/ Software Engineering 19 Project Management / Work Scheduling  During work scheduling you assign มอบหมาย people (project staff) to every task in the work breakdown structure.  You have to take into account พิจารณา the skill ความเชี่ยวชาญ and the availability ใช้ประโยชน์ได้ of the staff. Writing the storyboard Review Setting up the budget Casting

20 (c) Michael Brueckner 2005/ Software Engineering 20 Project Management / Time Scheduling The Time Scheduling results เป็นผล in a time plan that shows the work breakdown structure on a calendar ปฏิทิน / รายการแสดงเวลานัด. Take into account how many people work on a specific task. Let‘s say: 40 days for slide creation 1 person needs 40 days 40 persons need 1 day. But: This is not always true. Think: On woman needs 9 months to give birth. And 9 women?

21 (c) Michael Brueckner 2005/ Software Engineering 21 Project Management / Time Scheduling  Another example: Document review  People need to read the document carefully  Depends on the difficulty  Depends on the page number  => it will take a least time to review a document, you cannot share the work

22 (c) Michael Brueckner 2005/ Software Engineering 22 The Project Lifecycle 1 / Waterfall  Systems Investigation (Start of Project)  Requirements  Design  Implementation  Rollout & Installation  Maintenance  End of Project Deliveries (Stop of Project)

23 (c) Michael Brueckner 2005/ Software Engineering 23 The Project Lifecycle 2 / Prototyping  Determine requirements  Analyze alternatives  Specify design  Implementation  User review Iteration 1  Determine requirements  Analyze alternatives  Specify design  Implement design  User review Iteration 2...

24 (c) Michael Brueckner 2005/ Software Engineering 24 Controlling  Plan (schedule) against reality  Ways of controlling  Percentage ready („90% Reports“)  Number of modules ready for test

25 (c) Michael Brueckner 2005/ Software Engineering 25 Systems Investigation / Start of Project  Is the most critical phase in a project / Possible problems  Poor problem definition and analysis  Solving the wrong problem  Do things right – of course, but also: Do the right things!  Poor communication  Project is not feasible (too ambitious)  Lack of top management support

26 (c) Michael Brueckner 2005/ Software Engineering 26 Project Management Success Tips ;-) Every task seems easy if you don’t have to do the work. Things should be as simple as possible but no simpler. Good engineering is expensive; poor engineering is more so. Never be where you are not wanted. If you have a “yes man” working for you, one of you is redundant. If everybody thinks alike, nobody thinks at all.


Download ppt "Course 254 451 Software Engineering Michael Bruecknerphone055-261 000-4 (ext. 3233) อ. มิช่า officeSC2-417, by appointment."

Similar presentations


Ads by Google