Trước khi xác định bất kỳ hệ thống, bạn nên phân tích và hiểu được vấn đề, xác định các bên liên quan cần, và tài liệu tất cả các yêu cầu. Điều này sẽ giúp hiểu rõ hơn về hệ thống hiện tại và mục tiêu cần phải đạt được bởi hệ thống phần mềm mới. UML cung cấp các kỹ thuật mô hình để phân tích và ghi lại các yêu cầu của một hệ thống phần mềm. Chương này bao gồm quá trình phân tích một vấn đề bằng cách sử dụng kinh doanh và mô hình. | Understanding Requirements Modeling Before defining any system you should analyze and understand the problem identify the stakeholders need and document all the requirements. This will help in better understanding of the current system and the goals that need to be achieved by the new software system. UML provides modeling techniques for analyzing and documenting the requirements of a software system. This chapter includes the process of analyzing a problem by using business and system modeling. In addition it explains the creation of use case diagrams for system modeling. Objectives In this chapter you will learn to fl Analyze a problem by using business and system modeling fl Create use case diagrams for system modeling Chapter 3 Defining the System You should not commission a software project until you have all the requirements of the project available for preliminary planning. Lack of clarity in understanding the requirements of the existing process leads to rework in the designing of the new software system. Defining a new software system consists of the following phases Analyzing a problem Identifying stakeholders Identifying gathering organizing and documenting the requirements Analyzing a Problem The problem analysis phase of a software project involves preparing a concise problem statement that specifies the problem in the existing software system or the workflow of the organization and the constraints that exist for the proposed solution. A problem statement should include the description of the existing processes and the goals that need to be achieved by the new software system. In addition you should define a problem statement in the terminology understood by the customer instead of the software jargon. This ensures that the proposed software system will conform to the customer requirements. You can analyze the existing process or software system to create a problem statement by using the following modeling techniques Business modeling System modeling .
