Demand and business model innovation - demand 6- stakeholder analysis and hard sampling

Book6- Stakeholder analysis and hard sampling

1. What are stakeholders

1.1. Source of acquisition

1. Knowledge outside the human brain ： Scientific law
2. Knowledge in the human brain
   1. difficult , There are many problems
      1. How to find the right person ？
      2. How to communicate effectively with them ？

1.2. Stakeholders

1. All that can affect the software system Realization ( System decision makers 、 developer 、 Stakeholders ) Or it will be implemented Affected by the software system Of ( Existing product updates 、 New product development ) The key Individuals and groups (stakeholder).

2. Overview of stakeholder analysis

2.1. Stakeholders in enterprise information systems ： Business driven

1. Stakeholder analysis revolves around the business that employees in various departments of an organization are responsible for ： All descriptions and winning and losing conditions are consistent with Business Direct correlation
2. The difficulty of such stakeholder analysis varies with the organization 0 Increase with growth

2.2. Differences in stakeholder analysis efforts — Depending on the system being developed

Four types of information systems

1. small System (Small System)
   1. Small systems are those that support the organization Part of the work , But not influence The information system of the basic work of the whole organization , For example, enterprise personnel management .
   2. Focus on a particular problem
   3. The function is relatively fixed , The boundaries are clear
   4. Limited and obvious stakeholders , Default stakeholders are ready , There is no need for dedicated stakeholder analysis .
2. Organization level System (Organization-Wide System)
   1. Its function can affect the whole Organizational foundation Working system , There is a significant difference in the quality of its functions from that of a small system .
   2. It may affect organizations outside the user community Other groups , Even change the existing power structure of the organization
   3. Users are no longer limited and obvious , And other groups besides users Especially not obvious
   4. Find out Direct and indirect Groups , prevent boycott , In particular, find those that do not interact directly with the system , But it will introduce the groups that affect or are affected by the system .
   5. Analyze the interaction between various groups in the organization
3. Strategic information System (Strategic Information System)
   1. As Organizational strategic decisions And the system developed
   2. unable According to the existing business and technical conditions determine The future application effect of the system
   3. The scope of influence of the system is also difficult to determine ,
   4. The number of stakeholders is larger and more difficult to determine
   5. Analyze all possible... Within the business environment Opportunities and risks , And identify possible stakeholders , Prevent resistance
   6. Analyze the interaction between various groups in the organization , Various risks / The impact of opportunities on existing interactions
4. Interorganizational System (Inter-Organizational Systems)
   1. Through the implementation of the system itself Build or strengthen an organization The partnership between
   2. Many decisions of the system are not Single What the organization can control
   3. There are more questions about active participation and resistance to the system difficult
   4. Stakeholders are more than stakeholders in the system within the organization Difficult to find and choose
   5. Consider the cooperation relationship and benefit distribution scheme between organizations , Search and select stakeholders within the framework of the organization
   6. Analyze the interaction between organizations , Analyze the interaction relationship of various groups related to Inter Organizational interaction within the organization

2.3. Stakeholders of Internet products ： Human driven , But there are also conflicts of interest around the business

1. Add ： Popular products
   1. Search engines, for example 、 Electronic Commerce 、 Mobile Internet applications, etc
   2. Analyze the product positioning crowd ( User draw )
   3. The relevance of product functions in users' social networks , Whether it can help solve the problems in life
   4. Analyze the interaction between users and society ( scene )
2. Internet products also require business based stakeholder analysis
   1. How to... In the platform business model subsidy Revenue streams from multiple customer groups
   2. Whether the new features of a product will impact Of the same company Other products

2.4. The process of stakeholder analysis

2.5. The process of stakeholder analysis

1. Suzanne Robertson： Stakeholder analysis is intertwined with the definition of vision and scope , They are interdependent

2. Stakeholder identification : Looking for stakeholder categories for software systems .
3. Stakeholder description :
   1. Describe the different stakeholder categories Simple features , Including personal and job characteristics .
   2. Describe the different stakeholder categories complex features , Including focus and interest orientation , Influence and importance , Winning and losing conditions and the degree of influence .
4. Stakeholder assessment :
   1. Prioritizing stakeholder categories .
   2. Assess the risks of different stakeholder categories , Defuse risks .
   3. Analyze stakeholder conflicts , Achieve win-win results .
5. Stakeholder representatives choose : Select representatives from each stakeholder category .
6. Formulate the participation strategy of stakeholder representatives in requirements development and even software system .

3. Stakeholder identification

3.1. Identify all key stakeholder categories

3.1.1. Find all stakeholder categories

1. Stakeholder categories need To subdivide , Find out All categories ： All members of each class of stakeholders are able to Cause 、 Stable From the same standpoint 、 Same perspective Look at the same software system ： Different stakeholders view the system from different perspectives
2. Found more The key Stakeholders ： It is necessary to analyze their respective profit conditions , Try to achieve a win-win outcome through mutual compromise , The simplest distinguishing feature is the task .
3. Stakeholder groups are not fixed , need Continuous maintenance ： The understanding of stakeholders is not an activity that can be completed after completion , Instead, you should continue to pay appropriate attention after you finish

3.1.2. Filter categories of non key stakeholders ： Decision method stakeholder interaction

1. If the interaction and its concerns fall within the objectives and scope of the project , And its influence is related to the success or failure of the software system , Then stakeholders are key stakeholders
2. Filter criteria ： Analyze the tasks of a stakeholder category or their interactions with the outside world , If these fall within the scope of the project , Serve the system objectives ( Business needs ) The satisfaction of , It is .
3. for example , The initial stakeholder categories and their interactions established in the development of ambulance dispatching system in a social service field are shown in the figure 6-3 Shown . because “ Ambulance assignment ”“ Description of the incident ” and “ Event warning ” Are important business requirements envisaged by the system , So the emergency operator 、 Ambulance team 、 Hospitals are all key stakeholders . The system doesn't have “ Make it easier to ask for help ” The goal of , So patients and police are non key stakeholders , You can filter it out .

3.1.3. Maintain stakeholder categories

1. The stakeholders of a software system are not fixed .
2. There may be a shift of interest and concern among stakeholders , Even conflict .

3.2. Stakeholder identification methods

1. Simple method ： Expand first and then contract (Expand $\Rightarrow$ Shrink)
2. Empirical method ： Checklist (Checklist)
3. Classical method ： Stakeholder networks

3.2.1. Expand first and then contract

1. inflation ： In this phase , After the requirement engineer has collected the background information , With your own experience , List as many stakeholder categories as possible , The more the better .
2. shrinkage ： In this phase , The requirements engineer determines whether two or more categories of stakeholders share the same position , Merge the same categories .
3. Simple and easy to use ： If the stakeholder group is complex , There may be missing .

3.2.2. Checklist ： Classic list

1. user : The person who ultimately uses and operates the product , Focus on software functions , Users are the main source of information , As long as the user community can determine , Should be taken seriously .
2. Customer : People who pay for the development of software systems ： Focus on economic cost 、 earnings , To the system operating environment 、 Technical restrictions and laws and regulations have their own requirements , It can be used as an alternative source for users .
   1. Custom software development ： The leader or representative in the user
   2. Commissioned software development ： There is a certain connection with the user due to the software system to be developed , But they are not users of the software system .
3. developer : The person responsible for implementing a software system ： Focus on technical costs and benefits , Pay attention to special technology processing technology .
4. managers ： People involved in the management of software system development affairs , Pay attention to the development process of the system
   1. Investor Manager ： Care about the development process of the whole software system , Regard time as the first element .
   2. Executive Director ： The representative of the investor in the project management .
   3. project manager ： The developer is responsible for managing the daily work of the project .
5. Domain expert : Experts with rich knowledge in the problem domain , Focus on knowledge in software , More general and comprehensive , Not limited to your own perspective .
6. Government power ： Laws and regulations 、 Long term planning 、 Policy intention, etc ： Play a role of restraint and guidance
7. market forces ： People in the marketing department of the organization ： Pay attention to users' ideas , It can also be an important alternative source for users .
8. maintenance staff ： Non functional attributes of the system , For example, quality , Care about maintainability .

3.2.2.1. advantage

Clear 、 clear 、 Easy to use , Relatively comprehensive 、 System

3.2.2.2. shortcoming

Some categories are too thick , In particular, the user as a category is far from enough

3.2.3. Stakeholder networks

1. Applicable to stakeholder identification in very complex situations , And it can ensure the correctness and integrity of the identification results .
2. commonly 2-3 Time is enough .

3.2.3.1. The basic idea

1. The interaction of all stakeholder groups can form a network , Every kind Stakeholders It's all one Network nodes , If there is... Between the two categories Interaction There is one edge .
2. The stakeholder network is a Connected graph .
3. Traverse from any point in the stakeholder network , You can find all the nodes and all the references Various categories .

3.2.3.2. Basic process

1. Start with some stakeholders that are easy to find , It usually includes customers 、 Managers and related investors , also called Stakeholder baseline .
2. from Initial stakeholders Group discussion , Brainstorm , Make a list of stakeholder categories , Be careful to use names that represent features , To achieve the purpose of stakeholder segmentation .
3. Analyze the list of stakeholder categories generated in the previous step , Determine its relevance to the software system . When analyzing , Link stakeholders to the software system based on their list behavior , Build a Interactive networks , This network contains Stakeholders and software systems Interaction between , It also includes Between stakeholder categories Interaction . Through the interactive network , It can intuitively determine the relevance of various stakeholder categories and software systems and their criticality to software systems . Last , Reduced to a list of key stakeholder categories
4. Select representatives from each of the key stakeholder categories in the previous step , Focus on , List new stakeholder categories , If the list of stakeholder categories stabilizes , End the stakeholder identification process , Otherwise, turn to the second 2 Step

4. Stakeholder description

4.1. What should be described

1. As far as possible, stakeholder characterization should include all stakeholders' contributions to the success of product development , The following figure shows the intervention model , It is used to explain how to make the development and application of software system successful .
2. Organizational success means that an organization can create value by meeting its own requirements and completing its own tasks .
3. The satisfaction of requirements and the completion of tasks depend on the satisfaction of a series of detailed functions and the completion of a series of detailed activities , in other words , The satisfaction of requirements and the completion of tasks come from some basic decisions and actions , These basic decisions and actions illustrate the nature of the organization , Guide the activities of the organization , Reflect the purpose of the organization .
4. The generation of basic decisions and actions requires further content :
   1. Organize participants effectively , Enable them to implement these decisions and actions .
   2. Identify important interventions in the process of finding solutions to identified problems , Ensure that the basic decisions and actions are those that can help solve the problem .
   3. Build a winner's alliance around interventions , Enable participants to proactively implement basic decisions and actions .
   4. Give power to the participants of the winner alliance , Ask them to help achieve 、 Monitor and evaluate important forecasts , That is, to mobilize their spirit of ownership .

5. L1： Look for stakeholders based on the functional prospects of the software system
6. L2： Get requirements from stakeholder objects
7. L3： Analyze stakeholders' win / lose conditions , Implement a win-win strategy
8. L4： Understand stakeholder implementation 、 Ability to monitor and evaluate software systems , analysis The power and sphere of influence of stakeholders ; Understand stakeholder implementation 、 Willingness to monitor and evaluate software systems , That is, analyze the concerns and interest orientation of stakeholders .
9. L5： understand The personal and work characteristics of the stakeholders , So as to reasonably adjust the functions of the software system when the stakeholders are fixed .

4.2. Simple stakeholder characterization

1. Focus on tasks 、 Frequency of use , Experience

4.3. Stakeholder depth information description

1. For the project Concerns and interests Where , attitude Is it against or for
2. For the project expect , The conditions for becoming a project winner
3. Probably suffer The impact of the project , Affected Specific content and influence degree
4. Sure Yes The impact of the project , Of power The point of application and its strength

5. Stakeholder assessment

5.1. Priority assessment

1. Stakeholders are not completely equal , Some stakeholders More important than other stakeholders
2. Prioritize the basic characteristics of stakeholders , In especial Mission characteristics ： Stakeholders who don't have to pay more are important , More or more important functions of the system may be used 、 Use the system more frequently 、 Larger user groups have higher priorities .

3. Evaluation of stakeholder priorities based on stakeholder extension characteristics ：Power/Interest chart
   1. participants ： The actual user of the system , It has a great influence on the success of the system , It also has a great influence on the system , The highest priority .
   2. Environment setter ： Rarely use the system , But because of politics 、 Economic and other factors have a great impact on the system , Priority level is second , The most common are governments and managers .
   3. The affected ： It may be the direct user of the system , It may also be because there are losers in the system who are deprived of some benefits , Greatly affected , Can affect less , The priority is generally lower than the environment setting , But in special cases, it may also be higher than the environmental setter .
   4. The audience ： Unaffected , Also does not affect the , The lowest priority , For example, environmental experts and market forces .

5.2. risk assessment

5.2.1. Analytical attitude Power/Attitude chart

1. Strong opponents need to focus on analysis .
2. The concerns and interests of stakeholders are also important , The general environmental setter is the high-risk factor of the project .
3. For high-risk stakeholder categories , As far as possible, clarify the roles and implications of each stakeholder category , Discover the project's dependencies and assumptions , Analyze the possible risks when the actual situation is inconsistent with the expectation , And resolve it in advance .

5.2.2. Strategies to mitigate stakeholder risk

1. On the one hand, improve the attention of environmental setters to the system , Convert to participants
2. On the one hand, eliminate the opposition reasons of strong opponents , Become a strong supporter
3. Give the affected people some opportunities to express and realize their own opinions , Link worry .

5.3. Win win analysis

5.3.1. Find conflict ( establish Stakeholder/Issue The diagram )

1. List the systematic All stakeholder categories , Clearly describe their Interest in and Expectations for the system
2. From the stakeholders Interests and expectations Behind the discovery Common problems (Issue)
3. Establish stakeholder categories and issues relation , If a stakeholder category is related to a Issue There is interest , So this stakeholder category and this Issue There is a relation Relationship
4. For each Stakeholder-Issue Relationship , Indicate what the relationship is above Expectations

1. If a Stakeholder-Issue The expectations placed on the relationship cannot be consistent with the business needs of the project , Then its associated stakeholders are in the Issue Conflict with the overall objectives of the project
   1. Stakeholders and project leaders interact with each other adjustment 、 compromise
   2. Re evaluate the project The feasibility of
2. If Stakeholder/Issue A in the diagram Issue The associated Different relationship identifiers Have conflicting expectations , Then it means that its associated stakeholders are in the Issue There is a demand conflict on
   1. Analyzing the conflicting parties becomes Project Winners Conditions
   2. To adjust properly , Conflict Resolution
   3. The analysis project is in this Issue Goal on 、 Constraints and alternatives , And provide Conflicting parties Make a trade-off , Promote the negotiation and settlement between them

5.4. Can the free mode of reading articles win with the subscription mode ？

1. Issue： More traffic for free And Writer identity conversion
2. Stakeholder：
   1. Head and bottom Writers 、 Ordinary readers ： Acceptable
   2. Waist writer ： Affect income , Further weaken the guarantee
   3. Core readers ： Worried about the decline in the quality of the article
3. Whether we can win ： To what extent do free and subscription coexist
   1. Separate free writing from subscription writing , But coexistence
   2. Become a free and subscription writer at the same time , Or start by writing for free
   3. It is possible to achieve a win-win situation Issue： utilize Free reading mode Drainage for the platform
   4. It is difficult to achieve a win-win situation Issue： The platform is right IP Strong control of With the author Own copyright opinion

6. Stakeholder representatives choose

6.1. Representative sampling

1. Complete sampling : Each stakeholder category has its own representation , The selected representatives should be able to fully represent the stakeholders , In particular, do not omit key stakeholder categories , Do not substitute one class for another .
2. Have a positive attitude : Ensure that stakeholders are willing and able to help , Especially field experts .
3. Moderate quantity
   1. too little ： Personal views upset the common views of the group
   2. Too much ： It is difficult to reach an agreement
   3. The exact number representing the quantity depends on the context of the project , commonly 6-10
4. In the right proportion ： The benchmark of distribution is the personal characteristics of the representatives , Mix the following two skills .
   1. Computer skills
   2. Business skills
5. If a stakeholder class representative is not found , You can use User alternative sources

6.2. User replaces source

1. People who are in frequent contact with users because of business relations , Be able to speak for them
   1. System analysts with similar system experience
   2. Technical support personnel who contact users directly
   3. Service consultants
   4. Internal or external consultants , Usually refers to a domain expert
   5. User manager
   6. Marketing people
   7. Development source with relevant knowledge
2. Avoid using

7. Stakeholder participation in strategy development

7.1. Develop a basic strategy for stakeholder engagement

1. Correct strategy ： Let delegates participate in the right work at the right time
2. Stakeholders A It's only at the beginning that I tell you , And stakeholders I Is to participate in the full name .

7.2. Agile methods - User participation (User Involvement)

1. The basic idea ： Establish direct contact with users , Users participate in the whole process of software system development
   1. Pay attention to users and user execution as early as possible
   2. Adjust according to user feedback
2. The impact of user participation
   1. Design for it
   2. It's not about design
   3. Designed by it
3. Feedback design ： The final software system is closely related to the activities of users

8. Use the goal model for stakeholder analysis

8.1. Use the topic dependency model to describe stakeholder interactions

8.1.1. Principal dependency model ADM(Actor Dependency Model)

1. Target dependence (goal dependency)： The dependent wants to be satisfied by the dependent A condition , But it will not stipulate How to Meet this condition .
2. Soft target dependency (soft goal dependency)： A special type of target dependency , On the condition that Can't quantify Description of the .
3. The task depends on (task dependency)： Dependents want The dependent Perform specific tasks . Task dependency is more important than goal dependency More specific , Because meeting the conditions can Perform many tasks , The dependent has his own choice . Task dependency directly defines tasks for the dependent .
4. Resource dependence (resource dependency)： The dependent wants to be provided by the dependent Resource entities ( Abstract information or physical materials ) For your own use , But don't pay attention to the actions and problems that need to be performed by the relying person to provide resources .
5. The expectations of each topic need to be met by other topics , Resources provided by each topic 、 Responsibilities are consumed by other topics , Together, we can fully 、 Fully describe the interaction between stakeholders , Understand the social interaction of stakeholders .

8.1.2. B Key stakeholder categories for the station

1. commonly Up The Lord and the audience ： The goal is fluency 、 Interesting Video viewing , The task is to bring... To the platform Traffic and attention , Consume a lot of bandwidth and audit resources , Subsidized
2. " Secondary yuan " The core Up The Lord and the audience ： The goal is vertical 、 Core animation content consumption , The task is to bring... To the platform Benefits and core communities , Strong sticky consumption subsidy platform for other users
3. The former pursues a smooth video experience ( Soft targets )、 Take up more bandwidth ( resources ), Product stickiness and consumption power are weak ( Mission ); The latter is the opposite ( High viscosity game operation , Main income )
   1. The latter actually subsidizes the former , We need to pay attention to (A Welcome home )
   2. B Stop strategy ： Big member + Community + Online retailers VS Focus on content and marketing

8.1.3. ADM Example 2

8.2. Use the goal model to evaluate stakeholders in depth

1. Target model framework I*
2. Put the target model's Goal Assigned to Actor
   1. according to Goal Prioritization of Actor The priority of the
   2. according to Goal Risk determination Actor The risk of
3. Analyze deeply according to the target analysis Actor The interaction between
   1. Find out Actor The conflict between
   2. according to Goal The conflict shall be settled through negotiation Actor Inter conflict
4. Arrange the priority of the subject according to the priority of the target .
5. Determine the risk of the subject according to the risk of the target .
6. According to the goal analysis, we can deeply analyze the interaction between subjects :
   1. according to Goal conflict You can find deep-seated Subject conflict .
   2. According to the conflict of objectives negotiation solve Conflicts between subjects .

9. Hard data type

1. The result of processing and abstracting the actual business , It is a kind of refined knowledge .

9.1. Quantitative hard data

1. Data collection form
   1. Reflects the organization's information flow
   2. Collect each blank form that you are using 、 Fill out and distribute instructions
   3. Compare the completed form
      1. Are there any data items in the table that have never been filled in
      2. Did the person who should have received the form actually receive it
      3. Whether they use according to normal procedures 、 Storing and discarding tables
      4. wait
2. Statistical report
   1. It reflects the past of the organization Main business and business objectives
   2. Statistical rules are also a kind of Rich knowledge , The process of decomposing statistical items into detailed business data is often Organizational goals are broken down into specific businesses The process of
   3. Statistical statements filled in according to actual work , You can find the actual business execution status of the organization , Find out the specific problems faced by the organization

9.2. Qualitative hard data

1. A description of the entire organization
   1. Organization chart ： Help identify key stakeholders in the project
   2. Portal site ： Reflect the business development of the organization
   3. Business guidance document ： Such as work instructions and rule books ： Explain the detailed execution process of the business , Reflect the details of the business
   4. Business memo
      1. Reflecting the business Actual implementation
      2. Form an understanding of the organization's work process Understand clearly

9.3. Number of samples

1. $sampleBenBigSmall=p\ast (1-p)\ast (\frac{indeedsetsexbecauseSon}{canPick\; upsufferOfwrongBy\; mistake}{)}^2$
2. P Is the proportion of difference samples , Set to... In case of unknown 0.25

9.4. Sample quantity example

1. Every time 10 There is... In the invoice 1 This invoice is different from the normal situation
2. It is expected that all cases included in the invoice sample have 90% The certainty of
3. The sample size is ：$SS=0.10\times (1-0.10)\times (\frac{1.645}{0.10}{)}^2=25$

9.5. Sampling methods

1. Random sampling ： Sampling data randomly
2. Stratified sampling ： Consider the layering of the system , Take a sample at random from each layer

10. Summary of this chapter

1. Stakeholders are an important force in software projects
   1. The cooperation and participation of stakeholders is a necessary condition for the success of the project
   2. Stakeholder acceptance and satisfaction with the product is also a measure of success
2. For complex systems , The effective use of stakeholder power is not an easy task
   1. Attention to the necessary content and a complete process can help the project leverage the power of stakeholders
   2. Stakeholder analysis requires a lot of analytical methods and techniques
3. Hard data is also a very important source of demand acquisition
   1. Different hard data have different contributions
   2. Effective sampling of hard data is a necessary prerequisite for hard data to play its role

11. The example analysis

1. In the development process , Because they are the business scope they contact in their daily work , Therefore, it is thought that the functional requirements are met during development , The management and statistical functions of software reservation are realized , Then development is successful
2. As a result, , In the software testing phase , Users at all levels reflect relatively consistent opinions . among , The most common problem is that the system maintenance and operation are too complicated , There are even frequent reports of server and software instability , Mismatch . After careful investigation , Although there are a few problems found , But it is not as serious as the grassroots report , Software should be able to meet the daily work .
3. result ：2003 year , The informatization of our office has not been popularized , Especially the grass-roots leaders , Some are even computer blind . And our software , To improve efficiency , Set up a large number of shortcut key operations , This makes individual leaders feel difficult to accept . later , We optimized and simplified the operation interface and menu of the software , Instead of approval, radio box selection is used . Through a series of modifications and improvements , Opposition to the software is dwindling .
4. After the system goes online , The first to express dissatisfaction is the users who apply for water connection and business change . We found that , Because the counter personnel need to input the application information into the system and scan 、 Upload some important files , This prolongs the time for counter service , The waiting time for user business application increases .
5. When we identify stakeholders , Omit those who do not use the system ( Non participant ) But the people affected ,—— In this project, it is the person who directly applies for water connection and business change at the counter . However, the applicant for water connection and business change is the customer of the water supply company , It's very important .
6. After the system goes online , Front line users generally report to us that the style of system operation does not conform to their habits , Inconvenient to use , The operation efficiency is very low .
7. After understanding and Analysis , We found that ： Before the external service platform project , The internal developers of the water supply company have developed a simple external service management system . Although the system is very simple , Limited function , But the system has been used for quite a long time , Users are used to the operating style of the system . However, we directly judge that the system is backward , Dysfunctional , We're going to make a whole new system , So I didn't pay much attention to the system
8. When the business process enters the tasks related to the construction party , Most of the process stops , But in reality, it still continues to be handled . After understanding , We learned that ： As part of the information required to be filled in by the construction party in the system belongs to confidential information , However, these contents are not treated confidentially in the system .
9. Before the system goes online , We need to import the accumulated water meter information collected by users into the system . At the time of import , We found that the water meter number information provided by the user has a lot of repetition . In the system design , The water meter number is the primary key . This is a very serious problem .

11.1. Classroom analysis

1. In the current popular parent-child project ( Parent child class 、 Parent child movies 、 Parent child go, etc ), Who are the users ？ Who is the customer? ？ Users and customers who have higher priority ？ from Interest and Attitude From the angle of , How to resolve project risks ？
2. First, define the roles in the matrix , Secondly, the analysis is carried out according to the strategy

11.2. Classroom analysis

1. Participants in mobile games 、 Environment setter 、 The affected 、 The audience ？ How to resolve risks ？
2. A strong supporter of mobile games 、 Strong opponents 、 Weak supporters 、 Weak opponents ？ How to resolve risks ？

11.3. Thinking questions

1. Phil Ittup Is a member of the system analyst team , He was appointed to interview the members of the organization , Collect materials for systematic research . The enterprise is called Fall Back Industry , It has 5 Management . Besides , production 、 accounting 、 marketing 、 System 、 Logistics and senior management are the functional areas that will be affected by the proposed system . Each class has about 40 people . The production layer has 80 people , The accounting layer has 35 people , The marketing layer has 42 people , The system layer has 10 people , The logistics layer has 28 people . Top management has 5 people .Phil How to choose the interviewee ？ Why? ？
2. Maverick The company is a company with 15 A domestic freight transport company with a history of years , Suppose your team is Maverick The system analysis and design team of the company , by Maverick All businesses of the company design a computerized or enhanced design computerized project .Maverick It mainly carries out truck zero transportation , The management personnel shall process in real time (Just In Time) Principle work . Guided by this principle , They set up a system that includes shippers 、 The partnership between the consignee and the carrier , The purpose is to transport and deliver the materials needed in the production line on time .Maverick Advocate using 626 A tractor hauls goods , It has a 45000 Square foot warehouse and 21000 Square feet of office space .
   1. Develop analysis Maverick The information needs of the company , A list of hard data that should be collected .( Tips ： Imagine what the company is going to do , What registration forms should there be ).
   2. Design a sampling mechanism , So that the team doesn't have to look at the company 15 In the case of all documents produced over the years , Form a clear understanding of the company .