.jpg)
We live in a problem-oriented world.
We live in a product-oriented world.
We live in a process-oriented world.
We live in a world where problems are fixed by products and processes.
Every technological process contributes to either manufacturing a new product, repairing an existing product, or using products to make other products.
The basic technological process is Investigate, Design, Make and Evaluate.
Investigate is a human characteristic where we are able to sit and think for a while before embarking on some sort of activity. In these modern times, investigation might be carried out by one person or an entire team, using one piece of paper, or perhaps one computer or perhaps a whole lot of computers - perhaps even the power of the entire internet.
Once the problem has been investigated, a lot of information is gathered about the problem and possible solutions. It is in this phase that we begin to design a solution to our problem. This solution must comply with a number of limitations. These limitations could be the number of people available to do the work, it could be the amount of money available to finance the solution, it could also be the number and type of machines required to make the solution and lastly it could be the limitations of the type of materials available to us. All these factors are brought together in the next cycle.
The make cycle consist of a bit of experimenting, some errors and bad choices, and finally some successes which see a product coming off the production line.
The product may look completely different to what we had originally thought about but if it solves the problem within the limitations, then we are successful. The evaluation phase will test our original problem against the product and see if it works.
So that is a simple technological process.
In reality it is a bit more complicated.
Development of a single product might require several technological processes, all running at the same time i.e. in parallel, and each process is developing a single element of a much bigger product.
At some point, single elements come together in another technological process to create a new single element that goes on to meet up with other complex elements.
The single characteristic that we have in common with all these processes, is that they are all end-to-end processes. This means that each process consists of all the elements of the simple technological process, they are all Investigated, Designed, Made and Evaluated.
We can divide the product development environment into a number of different technological areas, each of which has its own process for developing new products.
Typical areas include hardware engineering, software engineering, civil engineering, mechanical engineering, food science, agricultural products etc.
We cannot cover all the processes in this short time, so we are going to focus on two that we are most likely to encounter - electronic hardware (a mobile phone) and software engineering (an application for the smart phone). The processes included here are very similar in other fields, so the material is easily adaptable.
A technological process might include the following steps:
1. Problem identification
2. State the solution outcome
3. List the requirements
4. Design the product
5. Build the product
6. Test the product
7. Implementation
8. Training
9. Maintenance
Problems arise when there is a difference between what we want and what we get. It's the gap between what "should be" and what "is" that defines the problem.
Most of us will very quickly focus on solutions to the problem before we actually have a good understanding of the problem. In this case, the problem is not treated adequately, and only the symptom of the problem is attended to.
A good start to identifying the problem is to write it down. Once we have to put the problem into words on a piece of paper, we tend to concretise the problem, and it becomes a tangible thing. Answer the questions: 'What do we think the problem is?' "What information should be collected and assessed to confirm our understanding of the problem?"
Once the problem is very clearly defined then we embark on the problem-solving process.
The range of options that are considered may be very wide. The options are invariably derived from discussions between all the interested parties.
During this discussion, many different aspects of the solutions will be dealt with. These will range from material availability, through costs and timescales to appearances and aesthetic considerations.
A statement of what the solution to the problem will be can only be made once we have considered a range of options. The choice of options begins with a list of requirements. This list may start out being very short but by the time the final proposal for a solution is reached, there may be an extensive list of requirements.
This list of requirements is usually a list of User requirements. The product component, system or process user will know and understand what his requirements are. These requirements will lead to other requirements being noted and which deal with the internal issues in the component, system or process.
When a final choice is made, the solution outcome statement is compiled. It is this statement that the project manager will use to lead the further analysis of the proposed solution.
The design team will analyse the proposed solution and begin to develop the list of requirements.
Requirements are clarified by asking questions, lots of them.
Dependencies are determined – which requirement depends on any other requirements to be fulfilled correctly?
At this stage various standards may be applicable and will impact on the requirements. Similarly, various statutes and codes and possibly legislated procedures may be applicable.
The requirements list may grow to an inordinate length dependent on the complexity of the solution to the problem.
In the case of software, problems are normally numerous and very wide ranging, this requires multiple solutions to multiple requirements all working in parallel and dependent on one another.
The list of requirements is normally managed by specialists during the design and development phase.
Requirements management involves monitoring requirements and ensuring that they are met throughout the duration of the project. It will be necessary to define the test and acceptance criteria for each requirement.
Everything will be documented and categorised so that it can be located and retrieved at a later date.
The product is designed by specialists.
This process may go through several phases amongst which is a prototyping phase where models are built to visualise the product.
Working models may be built with some of the critical functionality modelled.
As more clarity is obtained, the product begins to take shape and starts to function as the user specified in his solution statement.
During this phase, some different development methodologies are used to speed up delivery to the client or alternately to ensure quality solutions are developed. These methodologies are normally run by experienced practitioners.
In software development, Rapid Application Development, Agile and Waterfall methodologies are common.
Dependent on the type of product, there may be several manufacturing processes that must be considered.
The processes may include all the basic functions of cutting, assembling, painting etc. or they may include development of software that will interface with new hardware that has been developed and constructed elsewhere.
Products must be tested prior to release to the consumer. In essence we are testing the properties and performance of the product.
Testing criteria will be derived from the original product requirement specification. Where we made a statement that the product should be able to deliver a specific outcome for a specific input, we will measure that and report on the degree of success in achieving the outcome.
Consumers depend on us to deliver products that perform as we have claimed.
Various standards have been developed against which products can be tested. The SANS authority is a recognised set of standards that the South African consumer can depend on. It makes a lot of sense to have our requirements drafted in line with existing standards and then test against the standard.
Once the product has been designed and built and tested and passed the test, it is ready to be used.
The release and implementation of the product is a controlled process that informs the customer of the product, explains how to use the product, and then makes the product available to the consumer.
Part of this process may be marketing, advertising and even the product literature that is included in the packaging.
In many cases the product is a lot more complicated than simply including some literature in the packaging.
It may involve a full-on release programme which includes training of installers, operators and maintainers.
Training may involve short courses, long courses, trainers on site and the use of simulators.
Once products are in use, they may fail or require constant maintenance to keep them going.
A motor car is a good example.
Regular maintenance keeps them going for a long time.
They do fail and there are specialists available to repair the vehicle if required.