Category: Flow of development

Development flow – System development process and process flow –

I would like to explain in a general example how to follow the flow (phase) in product development etc.
The development act requires a lot of resources. For details, please see before developing design.
The content to be described is a development process that can be used for both software and hardware.

First of all, why is there a trend in development activities is to “improve efficiency”. It is better to create the best one while keeping resources as low as possible. It is a common example to explain from now on. I think that there are also better ways depending on the contents that can be easily done without actually proceeding with such development, the size of development and the items to be developed. Please check it in each development.

Development overview

It is not necessary to go through the development process by taking steps in content developed at the individual level and development in a small scale / short term.
As I said, there is a development process as a way to keep the resources as low as possible while not mistaking the direction.

Even as a method of development, if there is no problem at all from the beginning of development to the completion of development, various things will not come out.
Although it is not limited to this, the following part comes out as you develop it, so you need the opportunity to consider the design itself.

Before the development process

PDCA cycle

The PDCA cycle is very important in improving it.

It is one of the methods for smoothly advancing the administrative work, but it can also be used at the personal level.
I repeat the following 1 to 4, improve and improve and repeat spiral up.

By doing these, we can feed back the content that came up next, which is very useful for improvement and improvement.
It will become better by repeating the number of times.

I will explain the flow of development, but it is no exaggeration to say that all parts of the loop are PDCA cycles.
This cycle can be used at any point in development and demonstrates its effectiveness in development.
Let’s make plans properly, execute, review and make improvements.

The PDCA cycle is not only for development, but also for a very important cycle to make it better

DR (design review)

Although I have said it several times, the development acts very much use resources (people, things, money, time). It will be very exhausted if you go forward in the wrong direction. For that, we need to stop once and see if the direction is right. We call it DR (design review).
We will work on collective intelligence to find out what we can not find in individuals or specific groups.

It is heavily used in the waterfall model development which is difficult to return to development.
However, in Agile development, we may also consider development direction by gathering non-members and developing members as a whole.
Let’s have the opportunity as much as possible because it will be an important point to confirm.

What is DR (Design Review)
Planning, development, design, manufacture, quality, purchasing collectively gather in the next step as to whether the criteria are met at the point of each development (before going to the next step of the development process) or the direction is wrong It is deciding whether to proceed.

The timing of the holding is mostly at the end of each development (before the next step), but there are places where the holding is skipped depending on importance.

Content to be determined by DR
Does the content that you did in that process fulfill the criteria at the point?
Is the remaining problem crushed as much as possible?
Direction and purpose are not wrong?

Especially the remaining task will be doubled if you postpone it, the next process will correct the problem.
Let’s proceed with completion of our process as much as possible.

Points to advance DR
I said the point to advance DR, but the points are the same at any meeting.
The meeting is very expensive as a company. (Because man-hours for the number of people is necessary for the meeting time)

There is also a thesis that the conference rate declines by 10% at every conference when there are more than seven at any conference.
The decision rate will also decrease, but the participants’ sense of responsibility will also fall.
It is abnormal that some people do not speak.
You have to speak some thought and find the best policy and compromise among them.

We also collect specialists from several departments.
Whether there is no problem in progressing development, we will reconfirm whether there is any problem in the relation item of the participating department in the point that it changed from before.

Points above materials
Although data tends to be more frequent, it is necessary to keep a minimum amount of materials necessary.
It is impossible to understand even if it is too much, and it is the purpose of the material to convey information accurately.
Also, it is a place to judge whether to proceed next, so if you set it up with lie materials you may cause serious damage to the company.
Please note the neighborhood and make the material, please announce it.

Issues Points in remarks / suggestions
People who make statements that take fried legs (people are good at taking a fault) inevitably tend to become inevitably, but as the first voice is positive as to make a constructive discussion in as short a time possible Let’s try something else.
For details, please read DESC talk .

DR is an important point.
The direction of decision and the way the company should go will differ if the attendees do not desire to have the necessity of holding itself.

DR (design review) stops once and really develops what you need development review point

It also describes the development process in detail.
DESIGN REVIEW〈2016〉

Development method

I will explain three kinds of development process as a development method.
It can not be said that this is generally good, each has its own characteristics.

Recently, I stressed the testing process very much and I am in the direction to avoid rework as much as possible.
Therefore, it has been said that Agile type is better than Waterfall model.
However, development of V, W model incorporating the test process into the waterfall model is also frequently conducted.

· Waterfall model development (V-shaped model development) (W-shaped model development)

We divide top-down into work processes such as “request definition” “overview design” “detailed design” “development” “test and evaluation”.
In most cases there is no specific customer or customer interaction is only the first.

Since the flow of development through the stage is very easy to manage, it is a flow of development that has been used since a long time ago.
If there is no specification change in resources and duration, it will be estimated on a rough estimate.

· V character model development
V-shaped model development, W-shaped model development will be a variation of waterfall model development.
These are development processes, but strictly speaking, they are trying to incorporate the testing process to reduce backtracking.
I will explain that.

“Request definition” “overview design” “detailed design” “implementation” “test and evaluation” flow.
It is to carry out “test and evaluation” which makes pairing of “test and evaluation” here more concretely upper process.
It is called a V model or V character model because it seems that development process is going backwards, as we go through “test and evaluation” to move from small test to large flow as a flow.

As a flow of development here
“Request definition” → “overview design” → “detailed design” → “implementation” → “unit test” → “integration test” → “system test” → “acceptance test”
It will be like a shape. (Items change according to development)

If this is sorted by the size of the range it will be V shaped as below.
In addition, as each test process is used to confirm the operation of consideration contents up to implementation, they are almost paired.

· W-shape model development
As I mentioned earlier, development of W-shaped model is a variation of waterfall model development.
Unlike the V type, the test process is further divided.

As a reason, even if there is an error in the examination contents prior to implementation and implementation in the V-shaped model, actual confirmation will be considerably later, so returning becomes very difficult.
It is a development / testing process that takes a lot of effort and takes the idea of ​​crushing them beforehand.

As an example of the flow of V-shaped model development up to the previous
“Request definition” → “overview design” → “detailed design” → “implementation” → “unit test” → “integration test” → “system test” → “acceptance test”
was.

As an example of the flow of W-shaped model development
“Request definition” ⇆ “Request test” ➝ “Overview design” ⇆ “Design test” ➝ “Detailed design” ⇆ “Detailed test” ➝ “Single implementation” ⇆ “Unit test” ➝ “Integrated implementation” ⇆ “Integration test” → ” System integration “⇆” System test “→” Introduction “⇆” acceptance test ”
It will take the form of examination in the form like the examination content and implementation range. (Items change according to development)

Repeated parts circulate in the PDCA cycle and feed back.
We will increase the accuracy by that.

Like the V-shaped model, rearranging it by the size of the range will result in W shape as shown below.
In addition, as each test process is used to confirm the operation of consideration contents up to implementation, they are almost paired.

Benefits

Disadvantage

A form that the product embodies from the design drawing at once

・Spiral model development

It is a model of the development process taking advantage of the top down design and the bottom up design.
It is a method to develop by repeating design and prototyping.
However, unlike Agile type, we will develop PDCA throughout the present while covering overall functions.
Communication with customers is often done closely so that they become gradually clear from the overview.
One loop period is relatively frequently about 6 months to 2 years.

As an example of the flow of spiral model development here
“Element design” → “Prototype design” → “Mass production prototype design” → “Mass production design”
It will be like a shape. I will cycle through each one. (Items change according to development)

Benefits

Disadvantage

Form that gradually embodies products that were blurred

· Agile development

It is a generic name of a development method group that develops software so that it adapts quickly.
However, not only software but also hardware is quite effective.
We will try to minimize the risk by turning PDCA (design → test → survey → improvement) in a short term called iteration and dividing into functions and parts.
 The period of one iteration is relatively many times from one week to one month.

As an example of the flow of agile development here
“Function / Site” → “Function / Part” → “Function / Part” → “Function / Part”
It will be like a shape. I will cycle through each one. (Items change according to development)
Among them, interaction with customers is often done quite closely for each function / part.
When doing a combination, you must do a regression test (regression test: confirm a bug where usable functions can not be used).

Below is a flow of agile development while doing multiple simultaneous in parallel.
In the case of a single unit, it becomes one line in this figure.

Benefits

Disadvantage

Form in which products gradually add functions and parts

Which one should be used in the development method?

· When you can restrict functionality from customer’s request
(Delivery time · Cost priority, but when it is required for quality to the introduced function)
→ Agile development

· When you can limit the delivery date / cost from customer’s request
(Introduction function priority, delivery time and cost tend to be different from the original estimate)
→ Spiral model development

· If you want to raise the company’s own technology and develop a new product
(If there are many resources, the development scale is large, if you want to manage well, there is no specific customer)
→ Waterfall model development (including V character and W shape model)

The development process will be an example of the flow of development after all.
Because each has their own features, let’s step on the development process so that we can make the most of the strengths of development method and company development method according to it.

The development process is an example of the flow of development after all. It is best to find out how to develop our strengths

This is also a reference for the development process.

Avoid danger! Risk assessment

Risk assessment is a way to grasp whether the dangers of products and equipment made are not hidden as logical thinking.
Therefore, the risk here is not a risk of product strategy or product quality, simply speaking as a risk as “safety”.

1. Why is there a need to think about safety?

2. It is time to question CSR (corporate social responsibility).
→ International standards It is stipulated that manufacturing competition will be done with safety ensured as ISO

3. Large damage amount
→ It can be a civil lawsuit without having to be a criminal case. In that case, it will expand from tens of millions to billions of yen yen at the compensation responsibility

4. Can not sell overseas
 It is asked whether the risk assessment was carried out even overseas certification such as CE and CCC.

It is becoming an era where supplier liability is strictly questioned

2. Why are you making noise in Japan?

As for what it means, there are two ways of thinking about safety design.

· Danger detectable
When it becomes dangerous, send a signal and control and display
→ In the event of a sensor malfunction or the like, it does not detect danger and it operates.

· Safety confirmation type
Only when safety is secured, signal transmission control.
In case of sensor failure or the like, it does not operate because it does not detect safety.

Japan is rather dangerous sense type of the former.
In Europe and the United States, the latter safety confirmation type is mainstream.
Because it will not move unless it is safe,

Japan is a country undergoing security measures

3. What should the designer do?

Nevertheless, when the danger can not be avoided by any means, the designer must make efforts to reduce the danger according to the level of the risk.
It is a risk assessment that leaves them as a form.
The level of risk in this case is as follows.

As I will explain in detail later, it is to judge correctly whether this risk level can be accepted as a company.
It is the designer’s job to use the judgment to do the following.

· Minimize risk
· Make the user recognize the risk
· Present usage without risks

Essentially it does not have risks without making risks

4. Risk assessment flow

Risk assessment is done by multiple people so as not to miss as much as possible.
I will explain the flow easily.

Below is a diagram of the flow of risk assessment from safety design.

We will consider as early as possible in the design stage.
Because, if it is retrofitted, it will only protect the safety guards.
→ Cost rises, maintainability, operability is affected.

1. Intrinsically safe design

· It is not dangerous
· Do not approach danger
· Do not make danger
Is it supposed to be

“1. Intrinsic Safety Design” will not be explained as it will vary depending on the product, but let’s design it so as not to be dangerous.

2. Clarification on Product Usage

· Who, when and how to handle

“2. Clarification on Product Usage” becomes important in conducting risk assessment.
· Who is the product user?
· Are there any changes in hazards depending on the operating environment?
· How do I use it?
· Is there a possibility of encountering danger other than usage?
· Who maintains the product?
· Do you encounter maintenance danger?
· Hazards do not appear as synergies when using tools and other instruments?
· Are there any risks encountered by other third parties?
As we use it, we will identify the hazards along the flow of work.

3. Identify hazards and hazardous conditions

· Type of danger: impact, entanglement, noise, vibration, electric shock etc.
· Danger status: size of disorder, frequency of contact, avoidance from danger

“3. Identification of hazards and hazardous conditions” will correctly describe the situation of hazards sources from the contents that were done in 2..
Here, the same hazards of the same part that spans use can be summarized.
However, even if it is the same part, if the type and state of danger differ, it should not be summarized.

4. Risk Estimate

  · Estimate the risk level

For “4. Risk Estimation”, we will quantify each risk level from the type and state of the danger done in 3.
By numericalization, we will visualize the priority of improvement against danger.
However, since it may be influenced by the values ​​of each designer in setting this risk level,
I think that it is better to decide certain rules in advance.

5. Evaluation of risk itself

· Determine whether it is acceptable or not for risk level
· If there is a range where the risk is unacceptable, repeat it from the beginning

“5. Evaluation of Risk itself” will decide how to respond from the risk level quantified in 4 in the future.
Depending on the value of the level, we will classify “unacceptable levels”, “remaining risk” and “acceptable levels”.
· If it is “unacceptable level”, review the design and lower the level or eliminate hazards.
· If it is “residual risk”, we will rethink the design and lower the level or notify the user of the risk and leave it as a user’s responsibility.
· If it is “acceptable level”, we will promote product design by notifying the user of the risk depending on the situation.

It is best if there is no risk to the product, but it seems that it can not be done anything to make it zero.

The following books are helpful for details of the flow of risk assessment and how to respond at the manufacturing site.
製造現場等におけるイラストで学ぶリスクアセスメント 第1集

5. Identify hazards and hazardous conditions

As I mentioned briefly earlier, after extracting hazards, we will consider risk levels one by one for hazards.
The following are the main items to look for hazards.
· Mechanical
Crushing, shearing, cutting or cutting, entanglement, retraction, impact, rubbing or scuffing, injection or ejection of high pressure fluid
· electrical
Direct contact, indirect contact, electrostatic phenomenon, thermal radiation or thermal phenomenon · short circuit, external influence on electric device
· Thermal
Burns caused by fire or explosion, burns and other disasters, causing health problems
· noise
Hearing loss, other physiological malfunction
· vibration
Hazard source by vibration
· light
Diminished vision and health problems due to light
· Failure of power source
Failure of energy supply, unexpected operation, loss of safety

These contents are not all.
Depending on the content you need to add. Also, depending on the company, I think that the contents to be prioritized and details to be viewed in detail are different.

Identifying hazards sources can lead to activities of risk reduction

6. Risk level thinking

As I explained a little bit earlier, the risk level can be expressed as follows.

However, this is one of the risk assessment methods.
As a method
· Addition method (add risk element)
The above method, the most used in Japan
· Integration method (accumulate risk factors)
Sometimes the effect of risk reduction seems to be large
· Matrix method (expression with risk as a table)
Can not be reflected in fragmented risk
· Lithograph method (Risk expressed as chart)
Risk comparison is easy. But I can not do much classification to evaluate
there is ………, ………, etc.
I will explain with addition method.
Other methods will be omitted.
Let’s explain each item of the addition method.

o Size of injury

The size of the injury will be based on “magnitude of force”, “space to escape” “range to be covered” and will create standards.
Size of force: impact, thrust, speed
Space to escape: space to relieve force
Area covered: Number of people, range of body at risk
It becomes important.
For example, “I pulled my arms in a place that was crushed to 2 mm of clearance at a speed of 5 mm / s with a force of 20000 N”
If you think, your arms will break.
But, “I got my fingers in the place where the force of 20,000 N, crushed to the gap of 300 mm at a speed of 5 mm / s”
It seems that it will not get caught when becoming. (I think impact will be added)
The concept of “escape space” and “range to be covered” is also included in the JIS standard.
As an example, the minimum clearance for avoiding crushing (JIS B 9711)
Body: 500 mm or more
Leg: 180 mm or more
Toe: 50 mm or more
Arm: 120 mm or more
Hands: 100 mm or more
Finger: 25 mm or more

I think that it is good to refer to.

Based on these assumptions, we will classify the following.
· mortal wound : injuries leading to death or permanent labor inability
· Severe : serious injury (injury requiring long-term care) and injuries remaining
· minor injuries : accidents involving lost work and injuries (injuries that can be recovered at all)
· minor injuries : injury injuries that can return to the original work immediately after the allowance
This is an example and I think that strict numerical values and standards are different for companies, but it will look like this.

Some companies assign “injury class” on the assumption that injuries remain after the accident.

○ Contact frequency

The frequency of contact is the frequency of approaching a hazard.
I will divide it as follows as a guide.
· Frequently : 3 times or more / 1 day
· occasionally : 1 to 2 times / day
· Rarely : at least 1 / week
Again as before, I think that strict numerical values and standards are different for companies, but it will look like this.

o Probability of injury

The probability of injury will be based on “detectability of danger” and “avoidance from danger”.
The probability of occurrence of risk depends on whether it is an easy-to-understand hazard.
Danger is perceived differently in “Blade in front of you” and “Blade in place hidden behind the shadows”. Of course it also leads to avoidability.
As avoidance from danger, consider whether you can avoid or encounter hazards.
· Safety distance to prevent reach of upper limbs / lower limbs (JIS B 9718)
Distance not reaching hazards
Arm: opening 120 mm or less, distance to hazardous source 850 mm or more
Hands: opening 30 mm or less, distance to dangerous source 200 mm or more
Fingertip: opening 6 mm or less, distance to dangerous source 10 mm or more
Leg: opening 95 mm or less, distance to hazardous source more than 1100 mm
Below is an illustration of an arm case
　　
· Response time of safety guards (JIS B 9715)
S = (K * T) + C
S: Distance from detection point to hazard source, K: Part approach speed (upper limb 2000 mm / s), T: Time to eliminate hazards, C:
If this is a detection device, if the safety protection device is activated or the machine is stopped and the hazards are gone, consider using this formula.

Based on these, we will divide it as follows.
· certainty : can not detect / can not be avoided
· highly likely : can not be detected unless careful / can not be avoided without expert knowledge
· There is a possibility : It can be avoided if you can recognize by noticing / knowing a method
· Almost none : Anyone can detect it / Avoid it if you notice it
I think that it is necessary to decide how to avoid and detect how to detect hazards.
Again as before, I think that strict numerical values ​​and standards are different for companies, but it will look like this.

○ Risk level

We add the score so far and figure out the risk level.
Respond according to risk level.
· Ⅴ: unacceptable risk
 Risk points 20 – 17, Implement measures to immediately reduce the risk
· IV: serious risk
Risk points 16 – 13, prioritize measures to reduce risk
· Ⅲ: moderate risk
Risk points 12 – 9, implement measures to reduce risk.
· Ⅱ: Somewhat problematic risk
Risk point 8-5, risk reduction is desirable. Study to reduce it is necessary
· Ⅰ: acceptable risk
Risk point 4-3, implement risk reduction measures as necessary
Again as before, I think that strict numerical values ​​and standards are different for companies, but it will look like this.
By implementing these, designs that reduce risk as much as possible will be designed to approach intrinsically safe.

Risk assessment can reduce risk as much as possible

Details of the flow of risk assessment and how to deal with the manufacturing site are easy to understand below.

Before developing, think about necessary things!

We must judge what is really necessary taking into consideration the situation / state of the organization (other than the company) and the trend of society.
Also, even if you are doing development design activities, it will be in vain due to changes in circumstances.

It is also important to establish monitoring so as to judge appropriately whether to continue or stop.

Based on these, there are some things to consider when developing and designing.

Grasp the situation and state of the company

The thing to think about when developing and designing is to first decide its own situation accurately. In other words, it is the first thing to grasp the situation and state of the company.

1 “Checking resources” is important in checking the health condition of the company. It is also necessary to raise the success rate of development itself . For example, doing large-scale new development without considering funds is very risky.

2 “Confirmation of the root cause of the problem” means that there is a need to resolve the problem facing by doing development design.
In the case of product development, we need to know whether it can be a product leading to innovation or whether the problem will be solved in product development. Perhaps it’s a matter of sales or supply. In the case of manufacturing process / equipment development, there is no point unless the bottleneck in manufacturing is eliminated in its development, or if it is impossible to improve the efficiency of the whole manufacturing (overall optimization).

3 “Standing position of developed product” is It is necessary to know how important the product is. There is also development that wonders whether development is really necessary. There is no such thing as there is no thing to develop or you have to develop continuously. As I mentioned earlier, the act of development is very resource intensive. Sometimes it is better to divide resources into other tasks if development is wastefully done.

By grasping the current situation of own company, it is possible to know whether preparation is ready for development.

Grasping the position of the company in society

Next is to check your opponents and situation. In other words, it is to know the objective position seen from competitors and society.

2 “How many stakeholders will be happy with development activities?” Is to confirm whether impossible for the development act itself and not annoying to stakeholders . “Customers first principle” was seen in many companies long ago. If you force employees to give priority to “customer first principle”, productivity will fall and profit will decline. Also, if you neglect other stakeholders, the social status of the company will decline. Care must be taken for that.

I will briefly explain the stakeholders. “Stakeholders” in Japanese, people concerned with companies such as shareholders, customers, customers, regions, employees, etc.

By confirming the position in society, we can know the advantage and social position from other companies.

Consideration of social trends related to development products

1 “Whether it is creating a new market” is a concept that is necessary in the case where there is no orderer of the product and the product itself is offered to the world for an unspecified majority. It is necessary to know whether development activities of the product itself are not wasted .

<2> “Do you satisfy the quality of people who need customers / products?” Judge whether customers are satisfied with the quality of the products using the product It is that. If it can not be judged, this is a waste of development.

I will describe in detail in the item of quality, but “quality = customer’s request + value added” will be. This is the same as what leads to satisfaction . I will explain in detail later, but not “satisfied ⇆ unsatisfactory”, it is different from “not satisfied ⇆ satisfied” or “unsatisfied ⇆ unsatisfied”. Even if you make these mistakes, even if you make the best offer to customers, if you do not have customers offering much, they will be inconsistent.

3 “How long is the trend” is to know the content related to the product Know how long it will be done in the world . When developing in pursuit of products of other companies that can be innovation, if the product is saturated or the product becomes obsolete at the completion of development, the cost effectiveness will be diminished.

I think that the duration of the trend can somehow be judged from the trend of innovator theory and similar products, but it is very difficult to judge. The trend period is getting shorter considerably than in the past.

In order to prevent big companies from falling into the dilemma of innovation, or when not allowing SMEs to follow up as one of the Ranchestar theories, we may ignore the direct cost effectiveness of development.

Please also take into consideration that “Can you draw a product road map” in 4, leading to future product development and own technology. It would be even better if it would be technologies that take social trends into account.

By reviewing the product before development, we minimize resource waste and maximize the return on investment.

What will you do for that?

“Knowing yourself and knowing others (· world)” , “Knowing what to do” . There are different ways of doing it, there are times when you think independently. But, if you do not understand, I would like you to try especially.

· “Know yourself, know the other party (world)”

SWOT analysis : Used when your company knows what is the strength and what is weak compared to competitors. Originally it is used to seek optimization of resources in response to business change, but after deciding the development product, you can use it to confirm the extent of resources required from other companies.

& Nbsp;

· “Know what to do”

Anzov’s Growth Matrix Analysis : Understand the position of the developed product in product and market analysis and use it to decide future growth strategies. It is used here to draw a product roadmap.

I will explain in detail at that time.

These are necessary not only for development design activities but also for management management.
If you try to know more regularly than usual, these man-hours will be relatively small.

I think I understood the difficulty of development.
Next, I will explain the development in detail by development flow and development process .