Apply design pattern in software analysis and design can reduce time and cost by reuse proven and validated solution to avoid redesign. Design pattern provide general solution to specific problem domain, it is best to adopt design pattern in Platform Intendant Model (PIM). Model Driven Architecture (MDA) lack of methodology to judge problem domain from UML Diagram like sequential diagram, timing diagram or class diagram and how to apply design pattern in PIM mode. To alleviate the forgoing problem, this study proposed methodology to describe rule and step to apply design pattern, and present the difference between adopt design pattern by UML diagram. The research methodology is articulated using the design science research methodology. A usability study evaluation is performed to demonstrate its applicability with test case. With this proposed method, system analyst will improve software system flexibility and accuracy by design pattern after first phase PIM modeling, and object designed in software system will be low cohesion and high coupling .

Modeling software with object-oriented technique and Unified Modeling Language (UML) has become the new paradigm of modern information systems analysis and design. Selonen et al. (2003) proposed a framework for transformation within UML. However, they do not precisely define the operations and the rules they use. This research presents a systematic method which enhances Selonen et al.¡¦s work to transform the sequence diagram into the class diagram. The transformation process consists of three phases: (1) mapping the given sequence diagram to a notation-independent and semantically equivalent minimal model, (2) transforming the minimal model of the sequence diagram into the minimal model of a class diagram, and (3) mapping the minimal model to a class diagram. A real-world case is used to illustrate the concepts, application, and the advantages of using the proposed method. With this approach, the system developer can transform sequence diagram into class diagram automatically and thereby enhance the efficiency of system development.

Today, modeling the software with unified modeling language (UML) and computer-aided software engineering (CASE) tool becomes the main stream for the objected-oriented systems analysis and design. To enhance the degree of ransformation automation and reuse in the system development process, prior research suggested that most parts of the class diagram can be transformed from the sequence diagram directly. However, the explicit guideline for the transformation is lacking. This study presents a methodology, extended from Selonen et al (2003), to transform the sequence diagram into the class diagram. A real-world case using the integrated techniques is presented to illustrate the concepts, application, and the advantages of using the proposed approach. With this approach, the system developer can transform most parts of the sequence diagram into its associated class diagram automatically and thereby enhance the efficiency of system development.

After well-known structured technology, object-oriented technology has become another paradigm of system development and a hot topic in the field of software engineering. The Unified Modeling Language (UML) has become a standard means for the analysis and design of object-oriented after it passed the certification of the Object Management Group (OMG) in 1997, and it was widely used in many industries. Although it becomes a standard of object-oriented modeling language, UML hasn¡¦t provided principles or guidelines for mapping classes to tables. The purpose of this study is to investigate the guidelines for transforming UML class diagram to object-relational model. The transferring methods include both static structure transfer and dynamic behavior transfer. An example of automobile ordering system is used to illustrate the guideline and application. With these guidelines, analysts can easily use the UML class diagram to express database designing and thereby improve the efficiency and effectiveness of UML modeling.

Software testing is a vital part of the software development process and is used for the purposes of quality assurance, reliability estimation and verification and validation. However, software testing is extremely costly and time consuming. For instance, prior research indicated that more than 50% of the software development cost is devoted to testing. Due to the increased use of the Unified Modeling Language (UML) and model driven architecture approach in systems analysis and design, Model-Based Testing has been discussed as a prominent solution for software testing to address the above problems. This study presents a methodology for determining the test path which can then be further used to determine the test case for Model-Based Testing. Three real-world cases are used to test the usability (including the concepts, application, and advantages) of the proposed methodology. With this approach, software errors can be found at the systems analysis and design stage and thereby reduce the cost of software testing and enhance the efficiency of system development.

<p>Rhapsody is a Model-Driven Development (MDD) tool for embedded and real-time system design. The purpose of this thesis is to determine if Rhapsody can be used for software development on small processor platforms such as the Atmel AVR. Rhapsody is normally used on platforms running an operating system. Therefore certain adaptations are needed in order to use it on platforms without an operating system. These adaptations and their affect on the usability of the tool, advantages and disadvantages are all studied while porting AVR-software to Rhapsody on one of CC Systems products, the robust on-board computer CC Pilot XL II.</p> / <p>Rhapsody är ett verktyg för modelldriven utveckling och design av inbyggda system och realtidssystem. Syftet med detta examensarbete är att undersöka om Rhapsody kan användas för att utveckla mjukvara till små processorplattformar som Atmel’s AVR. Då Rhapsody normalt används till plattformar med ett operativsystem behöver vissa modifieringar göras för att möjliggöra utveckling mot plattformar utan operativsystem. Dessa modifieringar, deras för och nackdelar samt påverkan på utvecklingsprocessen undersöks medan AVR-mjukvara porteras till Rhapsody. Mjukvaran som porteras är en del av styrsystemet till en av CC Systems produkter: CC Pilot XL II, en robust fordonsdator.</p>

輸血安全在國內外一直都是非常受重視的議題，然而輸血錯誤問題卻仍時有所聞。根據國內2003年調查顯示，醫療不良事件中，輸血錯誤比率高達4%。初步探究輸血錯誤發生之原因，除了發生在醫院內保存及輸血過程的疏失外，採血單位(捐血中心)採血、檢驗與血品分離過程、運送保存過程等等之人為疏失，所有環節只要稍有疏忽，就可能造成無法彌補的錯誤。 本研究目的主要探討藉由RFID技術的導入，對整體採血到輸血流程在「流程管理」、「時間效益」、「品質確保」及「經濟效益」等方面所可產生之效益。 為了解實際流程與真正影響效益的因素，選定採血及輸血單位，針對採血到輸血之流程現況進行個案訪談。訪談結果藉由UML統一塑模語言進行企業流程塑模(Business Process Modeling)，並進行血袋相關流程萃取，以個別探討血袋R化後之效益評估。 經由本研究分析，得到結論如下：RFID的導入對流程管理、時間效益、經濟效益等方面改善都很有限，只有在醫療品質確保方面，可獲得比較顯著的效益。但畢竟人命關天，只要因此就能多救活或少犧牲幾條寶貴的生命，也是相當值得。 本研究同時也建議由相關中央政府機關來統籌規劃建置以EPC網路架構為基礎的血袋資訊流通共通平臺，血袋才能獲得有效率的流通，而不會浪費了許多捐血人的善意。此外，在醫院中也必須擴大使用RFID，特別是病患識別腕帶，才能收到加乘綜效。

Reproduction de : Thèse de doctorat : Systèmes informatiques : Toulouse, INPT : 2007. / Titre provenant de l'écran-titre. Bibliogr. 89 réf.

Zugl.: Paderborn, Univ., Diss., 2008

Thesis (M.S.)--West Virginia University, 2004. / Title from document title page. Document formatted into pages; contains xiv, 97 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 93-97).