...UML是Unified Modeling Language的簡稱,中譯為「統一塑模語言」。其中: Unified:UML是一種標準語言,廣泛運用於全世界。 Modeling:UML用途在於塑模(Modeling),也就是畫軟體藍圖。 Language:UML是一種塑模語言,而非程式語言或標示語言。 也就是說,UML是軟體系統發展人員用以建造模型,而這些模型使得工作團隊能夠:將系統具象化(Visualization)、將系統結構及行為規格化(Specification)、建構(Construction)系統、以及記錄(Documentation)發展系統過程中之各項決策。 什麼是塑模? 作曲家會將其腦袋中的旋律譜成樂曲,建築師會將其設計之建築物畫成藍圖,行銷廣告人員會將其創意製作成簡報;這些樂曲、藍圖及簡報就是模型(Model),而建構這些模型的過程就稱為塑模(Modeling)。 軟體開發如同音樂譜曲及建築設計,其過程中也必須將需求、分析、設計、實作、佈署等各項工作流程之構想與結果予以呈現,這就是軟體系統之塑模。 為什麼要塑模? 絕大部份的音樂演奏都需要樂譜(除了少數即性式表演外)! 絕大部份的建築施工都需要藍圖(除非要蓋的是一間狗屋)! 同樣的,所有軟體系統的建構最好都有適當的分析設計藍圖,因為軟體開發的過程絕對不是任意的、隨性的、且戰且走的、天馬行空的。 UML在軟體塑模中所扮演的角色是什麼? 1.軟體發展之方法論中包含了程序(Process)及表示法(Notation)兩個部份,其中: 程序指的是系統開發的流程,例:瀑布模式、漸增模式、擴展模式、雛型模式、螺旋模式等。 2.表示法指的是建構軟體模型中所會用到之符號及規則。 3.UML所涵蓋的內容是表式法而非程序,UML是與程序無關的(Process Independent),也就是說,無論以任何程序來開發軟體系統,都可以使用UML來建構軟體模型。 UML與物件導向方法之關係 1.UML之訂定與物件導向方法的確有非常密切之關係。 2.UML中的各種符號及規則與物件導向語言(Java,C++)之結構有完整對應。 但是,UML絕對不僅限用在物件導向軟體開發,UML中有些概念與圖形甚至可說是與物件導向無關 例:Use Case Diagram及Statechart Diagram 因此,軟體開發時無論是否採用物件導向方法,UML都是適用的。 UML的重要性 1.UML是OMG公佈的官方標準。 2.UML已為全世界軟體業者所廣泛採用,各大軟體公司(Microsoft、IBM、Oracle等) 3.在其產品中均支援UML。 4.UML的應用領域越來越廣(資料庫設計、韌體設計、資訊管理等)。 UML的現行版本 UML現行版本為1.5版(http://www.omg.org/technology/documents/formal/uml.htm),但2.0版將近完成,應會在短期內正式公佈(http://www.omg.org/uml)。 UML的內容到底是什麼? UML對於軟體開發相關人員而言,其實就只是一組符號及規則,其中包括: 1.Basic Building Blocks(都有其相對的符號) (1) Things Structura˙Things:Class、Interface、Collaboration、Use...
Words: 5884 - Pages: 24
...OBJECT-RELATIONAL DATABASE MODELING USING UML Table of Contents Introduction……………………………………………………………………………………..4 Overview of ER Modeling and UML…………………………………………………………...4 UML Meta-model……………………………………………………………………………… 6 UML Components………………………………………………………………………………7 UML Data Profile……………………………………………………………………………….9 UML Diagrams……………………………………………………………………………….....10 UML Diagram Classification – Static, Dynamic, and Implementation…....................................12 4+1 View of UML Diagrams……………………………………………………………………13 Object-oriented Class Model and Relational Database Model..............................................…...14 Use of UML to develop Ontologies…………………………………………………………..…17 References……………………………………………………………………………………….19 Abstract The Unified Modeling Language (UML) is being used as the de-facto standard in the software industry. With the adoption of UML 2.0, the new enhancements allow this version to describe many of the elements found in today's software technology as well as Model Driven Architecture and Service-Oriented Architecture. Many existing software applications involve complex application layer implemented in object-oriented programming languages and at the same time use relational database systems as the back-end data store. Modeling the whole system in a consistent manner will help developers and end users better understand the application. The Unified Modeling Language (UML) is a standard language for modeling software and database systems...
Words: 3708 - Pages: 15
...WHAT IS THE FUNCTION OF UML? UML, standing for Unified Modeling Language is a programming language that changed the world of modeling software overnight due to its developments in setting industry standards in the modeling of software programs holding intensive programming. The design standard mentioned was developed and created by the Object Management group and was standardized in 1997, which since that time has become the industry standard for software and modeling developments. Using UML in software developments is important when visualizing, creating, documenting modifications, and designing a process flow within software development down to a unified architectural level. This changed the force of programming because there was no single standard for object related programming in the object oriented design market and there were multiple standards across unified markets and geographical boundaries. WHY WAS UML PROGRAMMING DEVELOPED? UML was developed because organizations and developers of the time needed simple relationships between software models and a universal approach to development practices. The level of detail that was put into UML coding was much greater than its predecessors and allowed for a much higher level of architecture drawings than the previous various models. UML made it easy for new people joining an organization to have a clear and concrete understanding of what is being mapped out due to the fact that the modeling language used during the development...
Words: 425 - Pages: 2
...Review of UML The purpose of this chapter is to set the scene by reviewing the key UML concepts, the main diagram types, and the role of those diagrams within the software development process. If you're quite new to UML this will serve as a practical introduction that will help you make sense of the rest of the book, before you move on to further reading. If you're experienced with UML the chapter will serve as handy revision and you might just find some nuggets of information that have so far eluded you. Either way we'll all be moving on from roughly the same starting point: with the same appreciation of UML notation, with an understanding of relevant software development processes, and with a common bias towards .NET and the Visio for Enterprise Architects tool. The final point is quite important, and the raison d'être for this book. In recent years the body of UML literature has focused mainly on Java development and the use of modeling tools such as Rational Rose. In this book we're applying a .NET development perspective at the same time as demonstrating the so far under-documented Visio modeling tool that comes bundled with the Visual Studio .NET Enterprise Architect. With all this in mind we can now press on with the introduction to – or revision of, depending on your background – the Unified Modeling Language. What is the Unified Modeling Language? When discussing UML, we need to establish one important point right up front. The Unified Modeling Language...
Words: 8185 - Pages: 33
...INTRODUCTION TO PROGRAMMING Competency 430.1.2: Algorithm Design and Development - The graduate designs and develops algorithms for problem solving and implements those algorithms using appropriate program code. Competency 430.1.3: Use of Data Structures - The graduate develops working programs that use appropriate data structures for problem solving. Competency 430.1.4: Modeling Systems Using Unified Modeling Language (UML) - The graduate develops and interprets Unified Modeling Language (UML) diagrams which model object-oriented designs. Competency 430.1.5: Object-Oriented Concepts - The graduate applies object-oriented concepts, develops object-oriented designs, and uses object-oriented programming techniques. Competency 430.1.6: Software Testing and Troubleshooting - The graduate applies software testing and troubleshooting strategies to determine programming errors and recommend appropriate solutions. Introduction: As a competent programmer, your ability to design and develop algorithms, your proficient use of data structures, and your ability to use the Unified Modeling Language (UML) to communicate and develop object-oriented designs will help you design and develop applications to meet customer requirements. A solid understanding of object-oriented concepts will help you develop applications that are maintainable and extensible. Strong competence in software testing and troubleshooting will allow you to validate and verify your applications to ensure you...
Words: 2139 - Pages: 9
...Assignment 1 – UML What is UML? UML stands for Unified Modeling Language. It is a tool created by three renowned computer scientists; James Rumbaugh, Grady Booch and Ivar Jacobson between the years 1994 to 1996. It began as an attempt to combine all the good points from all the current modelling systems into one system that was coherent and better understood. These three men joined their ideas up at the Rational Software Corporation and evolved it into what it is known as today. I would describe UML to be a type of structure. It is used by large business applications and companies in order to provide a standard way for them to look at the design of the system that they are using. The system that these companies and businesses use must be designed...
Words: 438 - Pages: 2
...Model Driven Development – Future or Failure of Software Development? Ruben Picek, Vjeran Strahonja University of Zagreb, Faculty of Organization and Informatics, Varaždin ruben.picek@foi.hr, vjeran.strahonja@foi.hr Abstract. This article discusses some issues of the software development paradigm called Model Driven Development (MDD). Its basic idea is to move software development to a higher level of abstraction by using models as primary artifacts, and to transform models into the source code, with the aid of tools. Currently, there are several approaches to the realization of MDD paradigm which should bring a lot of benefits. However there are still problems to be solved, which will be discussed here. The authors are also going to analyze developers pros and cons, and give their own opinion about today's open question: Will MDD become a failure in trying to deal with software crisis, like the idea of CASE tools in 80's or will it become the future of software development? Keywords. MDD, MDD approaches, Software Factories, Software Development 1. Model Driven Development Paradigm In the last few years, software development has been faced with many challenges. Requirements of new and/or existing systems are growing, systems are complex and it is hard to build them on time and on budget. As an answer to these challenges, a wide spectrum of new approaches occurred, varying from buzzwords to comprehensive methodologies. One of the most prominent paradigms is Model Driven Development...
Words: 5437 - Pages: 22
...Chapter 3 – Conceptual Design: An Overview of Methodologies, Models and Notations CHAPTER OBJECTIVES (YOU SHOULD BE ABLE TO): 1. Define and describe a methodology. 2. Define and describe traditional, structured analysis & design, information modeling, and object-oriented methodology classifications. 3. Define and describe a Data Flow Diagram (DFD) and an Entity-Relationship Diagram (ERD). 4. Define and describe attributes, operations and relationships in an object-oriented methodology. 5. Define and describe the foundational characteristics of an object-oriented methodology. 6. Describe two classic information systems development challenges and their potential resolution. 7. Discuss Classification Theory and its relationship with object-oriented methodologies. 8. Describe Rational Corporation's Unified Software Development Process. 9. Define parallelism, substitution and omission. 10. Describe the Unified Modeling Language (UML) and describe Use Case, Class Diagram and Interaction Diagram. 11. Describe a simplistic object-oriented methodology for applying and using the UML. 12. Describe the foundational characteristics of the UML’s Class Diagram DESIGN A generic systems development life cycle (SDLC) was presented in an earlier chapter. You may recall that the purpose for this version of a SDLC was to give you a simplified way of sequentially studying the activities that are utilized to produce software-intensive information systems. In reality the SDLC...
Words: 13243 - Pages: 53
...HOSTEL MANAGEMENT SYSTEM (HMS) WAN NUR HIDAYU BINTI WAN JA’AFAR Report submitted in partial fulfilment of the requirements For the award of the degree of Bachelor of Computer Science (Software Engineering) Faculty of Computer Systems & Software Engineering Universiti Malaysia Pahang JUNE, 2012 vi ABSTRACT Hostel Management is an application developed to manage the various activities in hostel. The particular project is deal with the problems on managing the a hostel and avoids the problem occurs when carried out manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system which is more friendly and more GUI oriented. The objective of this project is to present a design of Hostel Management System for SMA Pahang. Our research is a comparative study of software design in development HMS for SMA Pahang. The study is focusly on fully utilize the OO Diagram and functional-based diagram. Our focus is comparing the utilization and significant of software design while developing the system using PHP for development of HMS. vii ABSTRAK Pengurusan asrama adalah satu aplikasi yang dibangunkan untuk menguruskan pelbagai aktiviti di asrama. Projek tertentu berurusan dengan masalah menguruskan asrama dan mengelakkan masalah ini berlaku apabila dijalankan secara manual. Pengenalan kelemahan system yang sedia ada membawa kepada mereka...
Words: 3646 - Pages: 15
...When the first object oriented programming language was introduced, it gathered lots of interest and began to grow rapidly. This led to the emergence of many object oriented design methods. With all these design methods came numerous modeling languages and by the early 1990s, many object-oriented modeling techniques were being developed to model software. There were different approaches to using different modeling techniques. Some techniques were designed just for application modeling, and others were targeted at specific areas such as database design. Each one had its strengths and weaknesses. Darwinian forces in the marketplace led to three dominate methods, each having its own modeling language. With three of these methodologies leading, Rational software hired James Rumbaugh after he developed object modeling technique while working for General Electric previously. With Rumbaugh on board, the company was known for two of the most popular object-oriented modeling approaches. The first one being Rumbaugh’s object modeling technique and the other being Grady Booch's object oriented design. Next they were assisted by Ivar Jacobson who developed object-oriented software engineering and Jaconson joined Rational shortly. The three of them together at Rational developed the unified method version 0.9 in 1996. The aim is not to create a new series of symbols but to but to adapt, expand, and simplify the existing and widely used object oriented methods. Other well-known companies...
Words: 269 - Pages: 2
... Information Technology for Teams Course Team Programming Environments Programming teams are achieving advances in deployment of more modular software products through the use of adaptive techniques in software development. Companies implementing large scale enterprise planning and control systems, product data management tools and complex back office systems for global service and support are finding these techniques to be more cost effective, adaptable and lean improving user requests for changing software functionality, processes and improved deployment strategies (Applegate, Austin, & McFarlan, 2002). This paper will compare and contrast three team oriented programming environments including Rational, Unified Modeling and Extreme Programming and will describe the impact of these programming environments on group software development. Literature Review of Software Trends The traditional methods of systems planning and investment decision making in the last century have given pause to leaders who witnessed costs in design, implementation and deployment of software skyrocket, created armies of support teams to operate and manage the software products and forced many firms into bankruptcy. Companies who have successfully implemented enterprise systems are now seeking more adaptive infrastructure deployments, software end-user functional value, and more adaptable learning approaches from the traditional waterfall design and deployment approach of the 90s...
Words: 1921 - Pages: 8
...HOSTEL MANAGEMENT SYSTEM (HMS) WAN NUR HIDAYU BINTI WAN JA’AFAR Report submitted in partial fulfilment of the requirements For the award of the degree of Bachelor of Computer Science (Software Engineering) Faculty of Computer Systems & Software Engineering Universiti Malaysia Pahang JUNE, 2012 vi ABSTRACT Hostel Management is an application developed to manage the various activities in hostel. The particular project is deal with the problems on managing the a hostel and avoids the problem occurs when carried out manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system which is more friendly and more GUI oriented. The objective of this project is to present a design of Hostel Management System for SMA Pahang. Our research is a comparative study of software design in development HMS for SMA Pahang. The study is focusly on fully utilize the OO Diagram and functional-based diagram. Our focus is comparing the utilization and significant of software design while developing the system using PHP for development of HMS. vii ABSTRAK Pengurusan asrama adalah satu aplikasi yang dibangunkan untuk menguruskan pelbagai aktiviti di asrama. Projek tertentu berurusan dengan masalah menguruskan asrama dan mengelakkan masalah ini berlaku apabila dijalankan secara manual. Pengenalan kelemahan system yang sedia ada membawa kepada mereka bentuk system berkomputer...
Words: 3646 - Pages: 15
...I. INTRODUCTION This IDoc describes use of the Unified Modeling Language (UML) to model and document Accounting Information Systems (AIS). The objective of modeling AIS is multifaceted and can be to: visualize, understand, summarize, detail, analyze, design, develop, implement, operate, secure, control, or audit the AIS. UML is a powerful modeling language and technique for all of these modeling tasks and is more robust and semantically superior to the commonly used Structured Analysis (SA) modeling tools of flowcharts (FC), data flow diagrams (DFD), and entity-relationship diagrams (ERD). Dr. White suggests that using UML diagrams as a tool to document AIS is a viable alternative to the Structured Analysis’s diagrams of FC, DFD, and ERD. What follows in Section II is a brief comparison of the two alternative approaches to systems documentation: Structured Analysis (SA) and Object Orientation (OO). Section III presents the definition and description of the major structural and behavioral elements used in UML including classifiers, instances, relationships, collaborations, activities, interactions, and states. Section IV discusses the organization and presentation of UML documentation of AIS as a collection of diagrams and packages. Section V contains various UML diagrams of the business revenue cycle (system) as examples of how to use UML to document a business system. Section VI contains examples of UML models of two special systems of great importance to accountants:...
Words: 9812 - Pages: 40
... Conceptual Modeling for Virtual Reality Olga De Troyer, Frederic Kleinermann, Bram Pellens, and Wesley Bille WISE Research Lab Vrije Universiteit Brussel Pleinlaan 2, B-1050 Brussel, Belgium {olga.detroyer,frederic.kleinermann,bram.pellens, Wesley.Bille}@vub.ac.be Abstract This paper explores the opportunities and challenges for Conceptual Modeling in the domain of Virtual Reality (VR). VR applications are becoming more feasible due to better and faster hardware, and due to new technology and faster network connections they also start to appear on the Internet. However, the development of such applications is still a specialized, time-consuming and expensive process. By introducing a Conceptual Modeling phase into the development process of VR applications, a number of the obstacles preventing a quick spread of this type of applications can be removed. However, existing Conceptual Modeling techniques are too limited for modeling a VR application in an appropriate way. The paper will show how Conceptual Modeling can be done for VR and how this may make VR more accessible to non VR-specialists. Furthermore, the paper will explain how Conceptual Modeling embedded in a semantic framework can provide the basis for semantically rich VR application, which may be essential for its success in the future and its use in the context of the Semantic Web. The paper will also point to some open research problems.. Keywords: Semantics. Virtual Reality, Conceptual Modeling, that the...
Words: 13392 - Pages: 54
...Journal of Web Engineering, Vol. 2, No.3 (2004) 193-212 © Rinton Press Requirements Engineering for Web Applications – A Comparative Study M. JOSÉ ESCALONA University of Seville. Spain escalona@lsi.us.es NORA KOCH University of Munich (LMU) and F.A.S.T. GmbH, Germany kochn@informatik.uni-muenchen.de koch@fast.de Received (to be filled by the JWE editorial) Revised (to be filled by the JWE editorial) The requirements engineering discipline has become more and more important in the last years. Tasks such as the requirements elicitation, the specification of requirements or the requirements validation are essential to assure the quality of the resulting software. The development of Web systems usually involves more heterogeneous stakeholders than the construction of traditional software. In addition, Web systems have additional requirements for the navigational and multimedia aspects as well as for the usability as no training is possible. Therefore a thoroughly requirements analysis is even more relevant. In contrast, most of the methodologies that have been proposed for the development of Web applications focus on the design paying less attention to the requirements engineering. This paper is a comparative study of the requirements handling in Web methodologies showing trends in the use of techniques for capturing, specifying and validating Web requirements. Keywords: Requirements Engineering, Web methodology, survey Communicated by: (to be filled...
Words: 8661 - Pages: 35