Copyright © 2003 by Trend Micro Inc. 建立世界級的軟體研發中心 Trend Micro Inc. Jeremy Liang 2003.02 2003 NTU Seminar.

Slides:



Advertisements
Similar presentations
Web Development Engineering Processes Introduction to Web Development Outsourcing Processes.
Advertisements

Test Automation Success: Choosing the Right People & Process
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
More CMM Part Two : Details.
Sixth Edition 1 M a n a g e m e n t I n f o r m a t i o n S y s t e m s M a n a g I n g I n f o r m a t i o n T e c h n o l o g y i n t h e E – B u s i.
PRJ270: Essentials of Rational Unified Process
Stepan Potiyenko ISS Sr.SW Developer.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Chapter 6 Systems Development.
System Development Life Cycle (SDLC)
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Oversight CHAPTER SIXTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Design, Implementation and Maintenance
Remedy, a BMC Software company Storyboarding the User Interface: Blueprint for an Application Shanaz Kanga | Michele Sarko Sr. UI Design Engineer | Manager,
Oversight CHAPTER SIXTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Copyright © 2003 by Trend Micro Inc. Introduction to Test Automation Terrence Chou 周存貹 趨勢科技研發部協理
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 1.1.
Human Interface Engineering1 Main Title, 60 pt., U/L case LS=.8 lines Introduction to Human Interface Engineering NTU Seminar Amy Ma HIE Global Director.
Effective Methods for Software and Systems Integration
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
Tyson’s Approach to Organizational Change Management
Trend Quality Assurance Edward Tsai 蔡木本 趨勢科技全球軟體研發部協理 April 22, 2003.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
N By: Md Rezaul Huda Reza n
Software Testing Life Cycle
System Development Process Prof. Sujata Rao. 2Overview Systems development life cycle (SDLC) – Provides overall framework for managing system development.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
PROJECT MANAGEMENT. A project is one – having a specific objective to be completed within certain specifications – having defined start and end dates.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Georgia Institute of Technology CS 4320 Fall 2003.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Chapter 1. Introduction.
Software Testing and Quality Assurance Software Quality Assurance 1.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
CSC444F'07Lecture 41 CSC444 Software Engineering Top 10 Practices.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Software Quality Control and Quality Assurance: Introduction
Software Engineering (CSI 321)
Quality Management Perfectqaservices.
System Development Life Cycle (SDLC)
IT Roles and Responsibilities
System Development Life Cycle (SDLC)
What do you need to know about XP?
Chapter Objectives To understand the operational environment in which you execute your project To understand the need and role of oversight in managing.
Engineering Processes
System Development Life Cycle (SDLC)
Software Engineering I
McGraw-Hill Technology Education
Case Study 1 By : Shweta Agarwal Nikhil Walecha Amit Goyal
Chapter 8 Prototyping and Rapid Application Development
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

Copyright © 2003 by Trend Micro Inc. 建立世界級的軟體研發中心 Trend Micro Inc. Jeremy Liang NTU Seminar

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.2 Essence of Software Development You May Not Know  Requirements  Planning  Design  Quality Assurance  Human Factor  Documentation

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.3 Requirements – What to build?  Requirement need to support your business model.  What features need to be included?  When the features need to be needed?  Do you need to consider the backward/forward compatibility?

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.4 Planning - When to do what?  Why is planning important?  Predictability  Running the project smooth / efficiency  Feasibility study/ prototyping  Scheduling and task estimation  How do you go running this project/ team formation?

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.5 Design – How to build it?  Architecture  Future expandability  Performance impact  Maintainability  Module reuse  Design review / alternatives

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.6 Implementation You know more than I do! Still Code review - Comments - Simple is beauty - Unit testing - Top down / pseudo code

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.7 Quality Assurance – Did we do it right?  The confusion over quality assurance vs. quality control vs. testing  Test plan/ test cases  Systematic  Test automation  Simulation

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.8 Documentation  Software need to be reproducible  Communication among different team members  Necessary for product sustain Why? Memory fades as time goes & people do come and go !

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.9 Human Factor – First impression is everything  Psychology / user behavior / learning curve (training cost, service cost)  Know your users : usability study  Culture/ user knowledge background/ Localization

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.10 Software Quality Assurance  QA ensure the product build fits the requirements; SQA ensure the product is build in the right way.  What’s the right way?  Predictable  Reproducible  Development process improvement need to be efficient and effective

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.11 Service Engineering  Take care product after-release life cycle  Bug fixes  Hot fixes/ patches  Product problem resolution

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.12 Organizational Options (1)  Functional oriented  Each function has its functional managers  Managers focus on its functional disciplines  Project lead act as coordinator for different function

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.13 Organizational Options (2)  Project oriented  A project team consist all functions necessary to conduct the project  Functional Manager only provide discipline and training when people are off the project  Project lead has full authority to make decisions, but not only project coordination.

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.14 Organizational Options (3)  Matrix  Functional managers make functional decisions and Project Lead make the project decisions.  Variations in who make the final call and reporting line.

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.15 Systematic Innovation – Vitality of a Software Company

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.16 Systematic Innovation – Vitality of a Software Company  Architect research team is the central place  Prototyping, feasibility study etc  Input comes from marketing, technology research, suggestions from Trenders, etc.  Technology roadmap defines the areas of interest  Technology roadmap vs. product roadmap  Example: wireless security  Not everything has to be built from within  Incentive program for patent applications

RUNNING HEADER, 14 PT., ALL CAPS, Line Spacing=1 line Copyright © 2003 by Trend Micro Inc.17 Software Engineering Career  Management track v.s. technical track (professional track)  Progression: Module -> subsystem-> product -> product line  Depth first, then broad