Principles of Engineering System Design Dr T Asokan

Slides:



Advertisements
Similar presentations
Project Management.
Advertisements

Project Management Concepts
Modern Systems Analyst and as a Project Manager
Project Management Techniques and tools Move mouse over arrow to enter presentation End Show.
Facilitated by Joanne Fraser RiverSystems
Introduction to Systems Development and Systems Analysis
Chapter 3 Managing the Information Systems Project
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Chapter 17 Project Management 1Saba Bahouth – UCO.
1 Team Characteristics Group committed to a common goal or purpose Clear roles and responsibilities that are interdependent Communication structure that.
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Project management A whistle-stop tour Toot!. Places to see Overview Project design in detail Task analysis example Design documentation examples Terminus.
T /5115 Software Development Project I/II Project Planning Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
(second logo) Teamwork! (second logo) Teamwork!. (second logo) Teamwork! 2 There were four people, Everybody, Somebody, Anybody and Nobody. There was.
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Chapter 3 Managing the Information Systems Project
Lecture 3 Managing your project How? Milestones Deliverables Meeting tutors.
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Chapter 11 - Project Management ME101 Dr. Nhut Tan Ho 1.
Project Management and Scheduling
Project Evaluation and Control Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Computer System Analysis
Chapter 3 : Managing the Information Systems Project.
Time Management Week 7 - Learning Objectives You should be able to: n List and describe the processes, activities, inputs, and outputs in time management.
1 Lab Teaching 1. 2 Role of Laboratory Teaching How various persons see it Aims of Laboratory Teaching Pedagogical levels A Typical Laboratory Exercise.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
Appendix A Project Management: Process, Techniques, and Tools.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
Software Project Management Lecture # 7. Outline Project Scheduling.
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
Software Project Management
Module 7 Session 7.3 Visual 1 Module 7 Planning and Scheduling with the Critical Path Method Session 7.3 The computer and project management.
Project Management. Lecture 5-2 Introduction This lecture discusses the key components of project management, role of project manager and techniques to.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
Software Project Management By Deepika Chaudhary.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Day 23.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
© 2014 Pearson Education, Inc., Upper Saddle River, NJ. All rights reserved. This material is protected by Copyright and written permission should be obtained.
Business Management. 2 “Copyright and Terms of Service Copyright © Texas Education Agency. The materials found on this website are copyrighted © and trademarked.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Project Management Organization Scheduling 31 January.
Project Management Why do projects fail? Technical Reasons
Overview of Software Project Management cont Review – Class 6 Scheduling Tasks Project Management Activities CEN 4010 Class 8 – 09/22.
Tools to Help  Product flow Dependencies and relationships of deliverables  Work breakdown structure The parts  PERT charts Program Evaluation and.
Systems Analysis and Design in a Changing World, 4th Edition
REQUIREMENTS Project management tools
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Chapter 3 Managing the Information Systems Project
Project Time Management
Project Management.
Families, Workplaces and Communities
Families, Workplaces and Communities
Modern Systems Analysis and Design Third Edition
REQUIREMENTS Project management tools
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Principles of Engineering System Design Dr T Asokan

Activity 1: Tangram Exercise Objective: Create identical square shapes, four per team of 5 members Rules for communication: 1.Tans may only be offered by hand to other members (no grabbing from others) 2.No tans may be requested, verbally or otherwise 3.No communication may exist, verbal or otherwise, except for offering of tans Evaluation: Teams responsiveness, communication, leadership, and commitment. How does each team member react? Who tried to solve everyone’s puzzle? Who worked without looking at any other person? Who overly assisted all others?

Hint: Use 5 triangles, one square, and one parallelogram

Activity 2: Helium Tubes Objective: Lower a hollow tube held by the team members Rules : 1.No member should loose contact with the tube 2.If any member looses contact, start from beginning. Evaluation: Teams responsiveness, communication, leadership, and commitment. How does each team member react? Who tried to solve everyone’s puzzle? Who worked without looking at any other person? Who overly assisted all others?

Team Evaluation Continuous evaluation of the team psyche is to be carried to assess the impact of changing personal relationships and outside factors on team setting. Unity, Self Direction, group climate, communication, distribution of leadership, responsibilities, problem solving, conflict management, decision making and self evaluation to be monitored. Team surveys through questionnaire or interviews are carried out to identify positive and negative characteristics. Self Study: Types of Surveys and Questionnaires used for team evaluation

This is a story about four people named Everybody, Somebody, Anybody, Nobody. There was an important job to be done and Everybody was sure that Somebody would do it. Anybody could have done it, but Nobody did it. Somebody got angry about that, because it was Everybody’s job. Everybody thought Anybody could do it, but Nobody realised that Everybody would not do it. It ended up that Everybody blamed Somebody when Nobody did what Everybody could have done. System Development Planning

REMEMBER 5P’s Proper Planning Prevents Poor Performance

Product Development Planning At a very basic level, product development entails a set of activities.Objective is to plan and manage these activities as a product development team. Estimation of Four basic aspects: “What”- tasks “when”-schedule “where”-equipment and facilities “how”-people, material, facility, and equipment costs.

STEPS: 1.Identify the tasks and milestones of the project. Milestones are important check points. They have clearly defined deliverables and should clearly show a projects success. 2. Supplement product tasks with team tasks. Identify and allot time for tasks like team building, team evaluation, etc. 3. Estimate project resources and time (continually updated) For each of the tasks, the resources and timing should be estimated. Realistic predictions giving clear bounds on the project.

4. Assign tasks to a time line, including parallel and sequential structure. The goal is to develop a schedule of the tasks for the project. Dependencies should be determined among the project tasks. What tasks can be started with current information and resources? What tasks rely on the results of other tasks? What subsystems have the least dependencies? What tasks are the most risky? 5. Monitor progress and assign additional tasks The original schedule should be continually monitored for progress. Progress should be graphed as a function of time and resources. In addition, the tasks should be revised, as more information is known.

Basic planning and scheduling tools GANTT charts, CPM (critical path methods), PERT (program evaluation and technical review). GANTT Charts (named after Henry Gantt) : Bar charts that relate product/system development tasks and activities to time.

Task/Schedule 1.Project Definition 1.Investigation and Planning 2 weeks 2.Customer input2 weeks 2.Design 1.Concept Development4 weeks 2.Embodiment Design3 weeks 3.Detail Design 4 weeks 3.Prototyping5 weeks

Task Lists Useful tool to augment GANTT chart Tasks, deadlines, coordinator and the status are listed Project task list and weekly task list TASKRESPONSE EMBODIMENTS/SYSTEMS DESIGNDinesh,Ani Measure bowling performance of Rosedale customers Sushant, Mani, Rajesh Build full-scale prototype table (foam)Sushant, Ani, Rajesh Beginning: October 2 Ending: October 31 Weekly Task list: Possibowlers

Analyze table strength for impact failure mode Sushant, Mani, Ramesh Construct flywheel graphical modelSushant, Mani, Ramesh Build electrically- actuated cam release mechanism Sushant, Mani, Ramesh Estimate steady-state flywheel rpmSrini, Suresh Calculate loads on flywheel conceptSrini, Suresh Purchase AC Motor to project spec.Srini, Suresh

Purchase prototype material for flywheel Srini, Suresh Purchase prototype material for flywheel Srini, Suresh, Murali Construct FLY I( ramp and flywheel) concept Srini, Suresh, Murali Integrate resultsSrini, Suresh, Murali Test FLY I (following experimental plan, notebook) Srini, Suresh, Mani --

SUMMARY Team formation and Team building are important activities in system/product design Tools like MBTI can be effectively used to allocate responsibilities in a team Continous evaluation of team performance helps to identify the strengths and weaknesses in a team Project planning plays an important role in project execution GANTT charts and tasks lists can be used effectively for proper planning.