Andstart a new project ,the first to introduce ,below we will learn the DRP ( distribution resource planning distribution resource planning ) .DRP :distribution requirement planning extension ,relating to the distribution system the key resources ,such as storage space ,labor ,money, transport and so on the plan ,we will from the software design theory to log analysis and realize these problems .
A software start software requirements ,and DRP is no exception .DRP business needs in Wang video stresses the very detailed,Beats By Dre, I will not write a detailed .But don is not important .Demand in general, Software Analyst resolved what to do ,how to do ,tell customers and developers need to do ,in what way ,what platform to operate after the end ,development ,should be delivered to those things .
Needs analysis is the analysis of software what is the demand of the user ,if the input large amount of manpower ,material resources ,financial resources ,time ,developed the software but nobody wants, that all inputs are futile ,if cost a great deal of energy ,the development of a software ,but do not meet the requirements of the user ,thereby to new development ,this is to let a person with deep hatred and resentment of the rework .
Demand analysis is important, because he has a decision ,direction ,strategic role ,he is in the process of software development play a decisive role in the requirement analysis ,Moncler Women Vest,we must have enough attention ,in a large system project development, its role is much larger than the program design .
A :demand analysis 1 understand customer requirements 2 analysis system data requirement two: requirement analysis process problem recognition :1 from the system perspective to understand software ,determine the development system of the integrated requirements ,and puts forward the realization conditions ,as well as the demand should reach what kind of standard ,including :demand function demand ,( do ) performance requirements ( what goals ) ,environmental needs ( such as type ,operating system and so on ) ,reliability (not the probability of failure ) ,security and confidentiality requirements ,user interface requirements ,resources use demand ( software needed to run the memory ,CPU etc.
) ,software development cost and schedule ,to estimate in advance after the system may achieve 2 Analysis and synthesis: stepwise refinement all functions ,finding out the connections between each element ,interface characteristics and design constraints ,analyzed whether they meet the requirements, unreasonable request section ,increased demand ,integrated system solutions ,given the development of detailed system logic model ( do model ) .
3 regulations made & # 26684 ;Description :software requirements specification review on functional correctness ,completeness and clarity ,and other needs for evaluation ,with customers through talk another time to confirm three :demand analysis error to say what is good demand analysis ,rather than what is not good demand analysis ,to know what is not good ,natural also know what is good .
The following is some bad situations :( 1) the creative and realistic and no doubt ,everyone will own a new Idea and excitement, especially when the Idea by some didn you had to do the amazing when .
But please note ,when you get the good time ,you may have forgotten that you are in the description of a demand ,but not in the planning of a creative ,creating a concept .Many are just beginning to do needs analysis personnel are more or less will make such a mistake ,reveling in their new ideas and new ideas, but contrary to the needs of the original objectivity and authenticity principle .
Never forget :need not be castles in the air ,is the real brick .( 2) the anatomy of the thrill of almost all software, to do needs analysis ,one would have to tell you the user requirements ,complete the anatomical ,cut into several pieces ,subdivided into several blocks ,and then make a careful and detailed analysis .
But when the user looks puzzled you hard to do the analysis results to ask you :I want to make a backup task ,how to do ?At this time, you ,need has opened a window of three to complete this task .
Never forget :decomposition is required, but the final purpose is to better the combination ,but not for decomposition .( 3) point of view and thinking often hear such complaining :how does the user can put forward such harsh requirements ?.
I understand ,you ,the user is only required to build an two clicks of the function ,instead of only one click .This will result in the need to change ,change the code ,even to the demand of test ,Coach Bag Outlet,the increased workload .
But ,if change an angle to think ,this function ,development time in only a few times ,Cheap Oakley sunglasses Shop,a dozen times ,but users every day by hundreds to thousands of times even tens of thousands of times ,you change it to reduce by half of the workload ,to him, such a demand would be harsh ?Never forget :there is no demand is wrong ,not just your demand analysis .
Try to stand in the user thinking way, your needs analysis will be more close to the user ,more reasonable .The software should be people-oriented .( 3) the programmer from the logic of programmers growth as a systems analyst is a common path ,but not a good programmer will become a good analyst .
Some programmers curing logic ,causing them to do needs analysis often into some horns .For example 1 / 0 logic ( or say black and white logic ) ,do not think so just like that ,no third situations .
But the actual situation is often ,in a certain time is such ,Nike Running Shoes Men,other time is such .For instance the exhaustive logic ,like to put all one two three possible cases are listed out ,and then a handle respectively ,each occupying 1/3 of the time ;but the actual situation is often ,1/3 accounts for the proportion of 99%, other two cases a year never meet again .
In practice there are many examples of this, not one one lists .Never forget :demand analysis and program design are not the same ,reasonable ,feasible is important .Jump out of the circle of program design ,stand in the angle of system problems ,your conclusion will be different .
Related articles：
没有评论:
发表评论