แนวคิด เรื่อง Unified Process (UP)

The concept of unified process (up), by definition it is a software engineering process that combines the expertise of software development (software engineer).But choosing a good technique and the main stage and effectively as well as the experts come together (unify), and define a new name. "The unified software development as a single (unified process)".Such as rational unified process (rup), a giant software company called "rational rose corporation" and is copyrighted by Principles or concepts are similar, but are different than the details of the process.up, including the development of cyclic (iterative development),.Management requirements (requirement management) and the use of software engineering tools to the drive software (casetools) so

.Goals or objectives up is to achieve software quality and in accordance with the requirements (need) of users, under budget and time predictability (predictable budget and time) up that will focus on the role. (role).Is said to have been established in each of the last (phase) of development is that Should include the one (who) each individual is responsible for what (what) is responsible to work on it (when), and how practices (how).(Abstract) or can be said that it is a high angle (bird eye view) of the process up, which may cause the picture is not clear. Strategies or tactics that are used up and then called it a "best practice model" or "best practice" that is, by it's nature up.As follows: 6.
1. Development Software development should be cyclic (iterative development)
2. Any software development should be managed demand (requirement management)
3. The concept of architecture components (component-based model architecture)
4.The prototype system can be seen (visual model) with a uml
5. Monitoring the quality of software developed continuously. (Continuously verify)
6., Change management (change management)



1.Software development should be developed cyclic (iterative development)
ie in each cycle (iteration) will contain one of these activities is to define, analyze, design,.And finally the testing needs of the user, the result is a software that can be run (executable product) which is different from traditional development processes (traditional development) that will not result in executable product.All systems are tested successfully. This is resulting in software development projects that have a high risk of failure over time. As the expression. "Than realizing too late that it is" that the development of the backwardAny of the following:.First. Structure is divided into rounds. (Iteration)
2. What has the development of each round. Program are under development for subsequent increases until it becomes a complete system
3.In each round, the team would rework (iterate) process analysis and design, application development, application testing of the interative and incremental development is characterized by the repeat loop made up. In each iteration, but it starts with planning.Analysis program was then used to collect and evaluate information to plan the next round. And with the need to add other parts of the system until the end.Will need to plan how the project will be divided into a few rounds. In each round the system more. To make a complete system. And can accommodate the needs of the system that can always change
.

2. Development of any software should be managed demand (requirement management)
"I have to deal with the needs that? In view of the documents or reports. Of the original work was finished!"This idea is the idea that the old legacy systems that we develop a singular (alone or standalone) and I found it in a software development house. In particular, it is often seen as the Ministry of Public Education of a view or report.And process (workflow) and then programming it is hard to see the problem we are experiencing is that. It is due to this kind of thinking that.Information shared hardly. If the information is used, it must be alchemy. The time waste workers and the software maintenance more difficult by what the problem is from the scene.Lack of education or the environment associated with the system itself, so we need to handle the great demand because of "demand" is considered the most important thing. If we can not deal with the need to change.And the risk of subsequent failure. For the management needs to focus on how to manage demand appropriately. The system can be changed on demand. Using resources in the least developed.In order to make sure that Our solution has been to create a system that appropriate and consistent with the needs of the user that needs to be managed. A systematic approach (systematic approach).
3. Using the architectural elements (component-based model architecture)
.Is software development experts. He said that in development of any system or software. But it has to be set or design of the system architecture, that is, it will always make the comparison clearer.

The concept of Re: Unified Process (UP) by defining the software engineering is a process that is due to include what software development specialist (Software engineer) By choosing the best technique, but the main steps and the same and use it more effectively in each of these experts come together. (Unify) and given a new name, "integrated software development process one (Unified Process)," he said. Such as Rational Unified Process (RUP), which is the company's software development industry giants called "Rational Rose Corporation" and is copyrighted. Principles or concepts are similar, but they differ over the details of the process. UP: development of Loopback (Iterative Development), Dealing with the needs (Management Requirement), and the use of tools and engineering sotwae activity (CASETools).

. The goal or purpose of the Software is to give UP and conform to the requirements (need) of the users are under budget and time. (Predictable budget and time) UP, it will focus on defining the role (Role) That is, it has been determined that in each period (Phase) of the development that would include anyone (Who) Each person is responsible for what (What) will do the job responsibilities when (When), and how operating (How) (Abstract), or in other words, whether it is a high-angle shots (bird eye view) of the process UP, perhaps, to understand the picture is still not clear. Strategy or thaekti which is used in the UP to call it a "Best Practice Model" or "Best Practice", that is, by the nature of UP. 6. as follows:

1. software development should be loopback development. (Iterative Development)
2. any software development should be handled. (Management Requirement)
3. using the concept of architectural elements (Component based Architecture – Model)
4. Prototype of a system that can be seen (Visual Model) with the UML language
5. checking the quality of software that is developed continuously. (Continuously Verify)
6. managing change (Change Management)



1. Software development should be loopback development. (Iterative Development)
that is, in each cycle (Iteration), often consisting of these activities is to define, analyze, design,To create a test and finally, the needs of the user. The result is software that you can run (Executable product), which differs from the traditional development process (Traditional Development) that will result in the product Executable format. The entire system has been successfully tested, this results in a software development project is a high risk of failure from time to time be rhetoric "over knowledge, late". Development of a reverse loop Many of the following characteristics:
1. the structure is divided into periods (Iteration)
2. what has been the development of the system in each round will be developed for subsequent sessions learn more ... until it becomes a complete system
3. In each round the team will have to repeat (Iterate). The analysis step, designing, developing, and testing programs, programs of Incremental Development and Interative characteristics of repeat loops do add up. In the past, but it starts with planning. Experimental analysis of program development and program implementation with evaluation information to plan action in the next round, but the round has to be added to other parts of the system until. To plan an entire project would be divided into a few around. In each round, the more the system will cause the system to have integrity and be able to accommodate the needs of users to environments where change is always constant.2. any software development

should be handled. (Management Requirement)
"why deal with? when see or learn from the report of the original system was ended!"This idea is the idea that the old legacy system that we developed is a unique system (Alone or Standalone), which I found most often in software development House, we, especially the Ministry of health was often considered merely see or learn from the report. And work processes (Workflow), and then comes another tough no programming. It is a problem that we have is that it was caused by this kind of thinking that. The shared information is hardly. If you were using it to Alchemy. Take the software as well as free labor, poor maintenance, respectively. What is the problem, it comes from the note: Lack of education, environment, system, or associated with it. Therefore, we must have a good demand management because "demand" is considered the most important. If we are unable to deal with the changing needs. And the risk of failure. The requirement for management to focus on how to manage demand appropriately. This system can be changed according to the requirement. By using the resources in the least developed. In order to make us confident that we can solve the problem right, and create a system that complies with the requirements of the user. This demand management must be. Guidelines (Systematic Approach).
3. using the concept of architectural elements (Component based Architecture – Model)
.It is a specialist in software development. He said that in the development of the software, or any system, but there must be defined the system architecture or design. That is, if one compares to understand clearly. We will need to be determined before that House, we would like to have it should be you.

The idea of Unified Process (UP) by definition, is the process of software engineering as a result of the experts, as well as things to software development (Software engineer).By selecting a good but technical and main steps and use the same performance of each such experts as well as other (Unify) and assigned to a new name, the "Software development process, as well as a single (Unified Process)"For example Rational Unified Process (RUP) which is a big company in the industry of software development, the name "Rational Rose Corporation", and is licensed by the principles or concepts will be similar, but it will be different than the details of the process more thanUP include the development of a forest to return (Iterative Development),To handle the needs (Requirement Management), and the tools to help the engineering ซอตฟ์แวร์ (CASETools), etc.

is the goal or purpose of the UP Software, have a high quality and consistent with the needs (need) of the users are under budget and the time you can predict (Predictable budget and time) that will focus on the roles UP (Role).In other words, there will be a set that, in each period (Phase) of the development, that it should be combined with one (Who), each of them is responsible for what (What) will be responsible for the work ethic (When) and do (How).(Abstract), or may be it has to be said that it was a high-angle (bird eye view of the process which may be UP image to be made to understand the strategy is not clear or dtac UP as well as in the optical, and then called it "Best Practice Model" or "Best Practice", that is the nature of any UP6. as follows:

1. software development should be the development of a forest to return (Iterative Development)
2. Develop any software should be available to handle the demand (Requirement Management)
3. Based on the concept of architectural elements (Component - based Model Architecture)
4.Prototyping of the system that can be seen (Visual Model) with language UML
5. Check the quality of the software development (Continuously Verify)
6. Change Management (Change Management)



1.Software development should be the development of a forest to return (Iterative Development)
that is, in each round of work (Iteration) will include a specific activity with these is to define, analyze, design,To create a test and in the end the needs of the user, the result is software that can work (Executable product), which is different from a traditional development process (Traditional Development) will result in a better product images ExecutableThere will be a test system as a whole. This results in the software development project, there is a high risk of failure. Over time, like the phrase "than I knew it was too late." itself, the development of a forest backas well as from any of the following:
1. The structure is divided into a round (Iteration)
2. What is the development of systems in each round will be used to develop more for rounds. until it becomes a complete system
3.In each round teams will need to re-work (Iterate) process design Analysis program development and test program from the characteristics of Interative and Incremental Development is the characteristics of the surrounding forest to repeat it in each round will start with the planningdiagnostic test program development program, and then used to evaluate the results with data collected to plan in action next round and round but will be required to be added to other parts of the system until the endThe project will be required to plan, they will be divided into a few times in each round will be any part of the system, it will be added to the system. There are the integrity and can accommodate the needs of the user is always the system changes
.

2. To develop any software should have the management needs (Requirement Management)
"Why should I want to manage the a? In when viewing or learn from the report of the original work was finished!"The thought of it is an old, old idea that the system is a system that we develop autonomously, (Alone or Standalone), which I was frequently found in the software development, especially the Ministry of Public Health, our home, is often seen as just see or learn from a reportand the process of working (Workflow), and then to write a program, it will be difficult to finish, sir, the problem is not that we have is that it is caused by the thought that this.information sharing is hardly to be used, it must be, if alchemy again, wasting time, labor, as well as software maintenance is difficult in order that this is a problem, it is by reason of coming fromThe lack of education surrounding the system or associated with that, so we have to manage the need for "good" needs to be considered to be the most important if we are not able to handle the ever-changing needs.and risk of failure, for the management of the requirements will be to focus on how to manage the needs of a system can be changed to suit the needs by Using Resources in the least-developedIn order to make sure we can solve the problem that we have been properly and build a system that meets the needs of the user, depending on the management of the need to be as a guide to the system (Systematic Approach).
3. Based on the concept of architectural elements (Component - based Model Architecture)
It is a specialist software development he said that in the software development or any system, but it will have to be prescribed, or architectural design of the system before you always. In other words, if you compare to understand clearly.We will have to be defined before the house that we would like it, that you should have.