Something is termed obsolescent when the manufacturer of the item no longer manufactures it. It is an increasing problem for systems because many components, particularly though not exclusively electronic components, have a life-cycle many times shorter than systems which may want to use them. Thus when items need replacement, it is no longer possible to get them, at least not at a reasonable cost. The drive towards use of Commercial Off The Shelf (COTS) components within systems exacerbates this problems.
Introduction
What is meant by an item being Obsolete/'Out of Date', and why does it occur
Consequences of items being Obsolete ('Out of Date')
Managing Obsolescence
An Obsolescence Plan
Obsolescence Checklist
Recording Potential Obsolescence
An office is a general facility used by projects and organisations, and how well it is thought about and managed can significantly affect the productivity of staff working within the office environment. It has a particular relevance to systems projects because it is frequently necessary to set up special purpose facilities for particular projects.
Introduction
Potential Scope of Office Administration
Office Environmental Factors Affecting Personal Performance
Checklist for Setting up, Relocating, or making Significant Changes to Office
Personal Conditions associated with Relocation
Causes of problems with relocations
Copier Checklist
Telecommunication Facilities
Operability is concerned with the ease with which a system can be used by its users. It is a particular concern of the specialist design discipline HUMAN FACTORS. Operability includes concerns such as whether or not there are enough people to use the system and whether or not they can effectively interface with the system in realistic operational circumstances.
Introduction
Notes pertaining to Operability Acceptance Scenarios
Notes pertaining to operability assessment whilst in use
The Operational Requirements for a system are those system requirements relating to its purpose and use. They are the highest level technical requirements.
Operational Requirements are specified in terms that consider the system itself as a single entity existing within its environment. They refer to what is expected of the system as a whole in terms of its behaviour or affect upon its environment.
Introduction
The Operational Concept
For every decision there are a number of alternatives. Opportunity Cost is used to refer to what has been lost by not following the best of the alternatives available. The term is also used in circumstances where an explicit decision was not made, but nevertheless a decision could have been made to do something different. Ie. there is an opportunity cost in continuing as you are rather than choosing to do something different.
This chapter gives just a little bit of the theory behind how organisations are structured, and discusses how an organisations structure can affect the effective operation of a systems project. It should be noted that this is far from academic. How best to organise to cope with system projects is a very real issue within many organisations.
Introduction
Organisational Structures
Functional Based Organisations
Product/Project Based Organisations
Customer or Geographically Based Organisations
Matrix Based Organisations
The 'Virtual' Organisation
Mechanistic/bureaucratic vs Organic Organisations
Organisational Culture
Management Span of Control
Constraints on setting up effective organisations
Structured Analysis of Organisations
Human Resources/Personnel Function
Accounts and Finance Function
Research and Development Function
Marketing and Sales Function
Operations Function
Being a good organiser is a vitally important management skill, something that is often not appreciated. It is particularly important in a system project context since such projects are often complex and being able to get people to work effectively towards common ends is often the difference between success and failure.
Being better organised is something most people would benefit from in general.