ตัวกรองผลการค้นหา
Requirements analysis
แปลว่า(Software Engineering) a modeling activity whose objective is to understand what the customer really wants
Line-of-code metrics
แปลว่า(Software Engineering) measures of quality or productivity that are normalized using lines of code produced
Formulation
แปลว่า(Software Engineering) a Web engineering action that identifies business need, describes WebApp objectives, defines major features and functions, and establishes mechanisms for requirements gathering
Component reuse
แปลว่า(Software Engineering) the ability to reuse a portion of a model, source code, test case, etc.
Resources
แปลว่า(Software Engineering) anything that is required to get the project done, people, hardware, materials, information, etc.
Coupling
แปลว่า(Software Engineering) an informal measure of the degree to which a software component is connected to other components, to data, and to the external environment
Interface design
แปลว่า(Software Engineering) a software engineering action that establishes the structure and workflow for a user interface; follows three "golden rules:" place the user in control, reduce the user's memory leoad, make the interface consistent.
B.E.= Bachelor of Engineering
แปลว่าปริญญาวิศวกรรมศาสตร์บัญฑิต
WebApps (Web Applications)
แปลว่า(Software Engineering) any application that delivers meaningful content or functionality to end users via the Web.
Data design
แปลว่า(Software Engineering) an activity that translates the data model developed during analysis into implementable data structures
Work flow
แปลว่า(Software Engineering) the sequence of tasks that are required to accomplish some activity or action; often (but not always) used in conjunction with software process models
OCL (Object Constraint Language)
แปลว่า(Software Engineering) a supplement to UML, this formal language allows a software engineer to construct unambiguous statements about the characteristics of various design model elements
