Kantapään kautta tuotantoonsiirrosta tuotteenhallintaan Experiences of Software Configuration Management (see the story on notes pages) Heini Aarela.

Slides:



Advertisements
Similar presentations
Common Core Standards (What this means in computer class)
Advertisements

Beauty in a NutShell Business Management Software for Spa Consultants.
Test Design and Documentation. Test Design Test design is to ensure that all requirements are met through a series of test procedures, increasing the.
Database Planning, Design, and Administration
DriveWorks – Product Configurator
“What do you want me to do now?”
9/10/2004Use Case Workshop 1 CSC480 Software Engineering Workshop 1 Requirements Modeling.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
IE 423 – Design of Decision Support Systems Introduction to Data Base Management Systems and MS Access.
E-commerce Project Erik Zeitler Erik Zeitler2 Lab 2  Will be anounced and scheduled later  We will deploy Java Server Pages on a Tomcat server.
Management Support Systems A Hierarchy and a Guide.
Today’s Goals Concepts  I want you to understand the difference between  Data  Information  Knowledge  Intelligence.
CSCI 639 Topics in Software Engineering Assignment #5 Fall 2008.
Feb. 2, 2004CS WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004.
Teamwork C.Eng 491 Fall 2009.
Project Documentation and its use in Testing JTALKS.
Leading Edge Climbing Equipment
Effective Methods for Software and Systems Integration
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Valma Technical Aspects
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Chapter 8: Systems analysis and design
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
Introduction to information systems
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
CS 350 – Software Design The Object Paradigm – Chapter 1 If you were tasked to write code to access a description of shapes that were stored in a database.
Making a great Project 2 OCR 1994/2360. Analysis This is the key to getting it right. Too many candidates skip through this section. It’s worth 20% of.
Computing Fundamentals Module Lesson 19 — Using Technology to Solve Problems Computer Literacy BASICS.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
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.
© 2001 Business & Information Systems 2/e1 Chapter 8 Personal Productivity and Problem Solving.
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 8 Personal Productivity and Problem Solving.
Database System Development Lifecycle 1.  Main components of the Infn System  What is Database System Development Life Cycle (DSDLC)  Phases of the.
Usability Issues Facing 21st Century Data Archives Joey Mukherjee and David Winningham
Deliverable #9 – Detail Design Subsystem Design and Realization ALL of your design class model elements must have the package or subsystem they are associated.
1 Introduction to Software Engineering Lecture 1.
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Technology. What is your definition of TECHNOLOGY?
Information & Communication Technology (ICT) Books: 1. Management Information Systems James A. O’Brien & George M. Marakas 2. Introduction Of Information.
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
0 Content Management and the Need for Change in Technical Communication Written by: Scott P. Abel 20 June 2007 Nick Savillo ENG 393.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
“Content Management and the need for change in Technical Communication.” Written by: Scott P. Abel Presented by: Ayodele Smith.
An Introduction to Forms. The Major Steps of a MicroSoft Access Database  Tables  Queries  Forms  Macros  Reports  Modules On our road map, we are.
Streatham Wells Parents’ Evening Wednesday 14 October Parents, Children and Homework What can a parent do?
Technology in the Community
It is very important that every time you do a major piece of writing, you complete all of the stages of the Writing Process. Often, the steps of the process.
Fostering Autonomy in Language Learning. Developing Learner Autonomy in a School Context  The development of learner autonomy is a move from a teacher-directed.
Trends & Concepts in the Software Industry II Synthesis.
Fall CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Senior Design Lecture 7 Functional specifications Technical meetings.
Building the Corporate Data Warehouse Pindaro Demertzoglou Lally School of Management Data Resource Management.
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
David Adams ATLAS Hybrid Event Store Integration with Athena/StoreGate David Adams BNL March 5, 2002 ATLAS Software Week Event Data Model and Detector.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Appendix 2 Automated Tools for Systems Development
Coursework: The Use of Generic Application Software for Task Solution
THIS IS TO EVIDENCE YOUR WORK AND GET THE BEST GRADE POSSIBLE
Architecture Components
Introduction to Logic Lecture 5b More Fallacies
Chapter 1 The Systems Development Environment
Decomposition.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Database Systems: Design, Implementation, and Management Tenth Edition
Library Resources for PSYCH 28
ACSC 155 System Analysis and Design 4. Systems Design
Presentation transcript:

Kantapään kautta tuotantoonsiirrosta tuotteenhallintaan Experiences of Software Configuration Management (see the story on notes pages) Heini Aarela

Provide support for the activities you want to control. Do not try to forbid – you would only lose the trace. Kuri ja järjestys

Group the usage steps into work phases which allow a single user to perform a single task. Do not force a user to delegate her task to someone else by asking too much. Vuori Muhamedilla

Use original source of information; capture information into the system at its creation, from the one who knows it. Do not beg for inconsistencies; do not force the user to preprocess, communicate or store data behind your back. Onks tietoo

Standard serves its purpose when it is easier to follow it than to break it. Do not use standards as replacement for tools. Ohje & sääntö

You are responsible for transporting data from subsystem to another. Do not force the user to implement the integration of system components. Do not use automatic to force the user to integrate the system components! Hajauta ja hallitse

Store data in its raw format and derive from it when necessary. Do not ask the user to give again any data that already exists in the system, just because it is not in the right format. Sisäsiisti

Give feedback to the user by showing her own input in the appropriate context. Let the user see and know she has done it right. Do not hide the context from the user. Halinta

The purpose of a project is to produce something that outlives the project. Be prepared to it. Do not mislay data in program logic. Mitä jälkeensä jättää

Consumers of information are dependent on the producers and the choice of tools they make. Do not increase the variety of similar tools and databases the consumers have to wade through. Kuka on kuka

Concentrate on serving the producers of information. Give them a reason to use your solution. Do not worry about the consumers – they will come and tell you what they want. Kuka kysyy ja kuka käskee

The users do their work with the tools you provide, or without them – or despite them. Do not force any user into the role of The User – it is not her job. Totuus vai tehtävä