Member Login

E-mail:    Password:  




 TitleDate AddedCompany
whitepaper Picturing Program Design2006-10-13 01:00:15 Oracle
  For millennia, people have been using graphical approaches - stick figures and the like - to communicate ideas. When the first programmers started creating applications for business users (and it quickly became clear that neither party understood the other's language), once again stick figures (along with boxes, lines, bubbles, and the occasional word) came to the rescue. Over time, various graphically oriented techniques, such as producing the data definition diagrams used by structured programmers and the entity relationship diagrams used for relational database applications, became mainstream approaches to facilitating analysis and design as well as a means of recording and communicating system requirements. Today, in the world of object-oriented and distributed computing, Unified Modeling Language (UML) diagrams serve these purposes.   
whitepaper What's new in UML 2.0?2005-11-09 01:00:02 IBM
  So-called 'model-driven' development (MDD) methods, which are based on higher levels of abstraction and greater use of automation compared to traditional methods, have already demonstrated their potential for radical improvements in the quality of software and the productivity of development. While several important new modeling capabilities were added -- such as the ability to more accurately capture software architectures -- the dominant characteristic of this revision is the heightened precision of the language definition that enables greater levels of automation. This paper explains how this was achieved and also describes other highlights of UML 2.0.   
whitepaper An Internet Accounting System: A Large Scale Software System Development Using Model Driven Architecture2005-10-25 03:00:03
  Software development should be changed from a handcraft industry to industrialization like manufacturing to obtain high productivity. In knowledge creating industry of software development, engineers have to concentrate on core works. Peripheral works should be avoided as much as possible. Model driven architecture helps programmers work mainly in analysis and design without considering much about implementation. Internet Accounting System, which is a standard model of enterprise systems have been developed with model driven architecture with high productivity.   
whitepaper Developing UML Diagrams From XMI in Oracle JDeveloper2006-10-13 01:00:15 Oracle
  Unified Modeling Language (UML) is based on the use of diagrams to visually represent business process flows as well as interactions among software and data components. XML Metadata Interchange (XMI), designed to streamline data integration, is a popular format for representing UML objects; a UML diagram may be stored in XMI format, and conversely, a UML diagram may be created from an XMI file. For this reason, XMI facilitates the transmission of UML diagram data, and many UML tools support this interchange capability. This paper describes the method for manually creating an XMI file from an XSLT, importing it into a UML tool (Oracle JDeveloper 10g), and then constructing a UML class diagram from the XMI file.   
whitepaper Practical Model Driven Development Process2006-04-20 07:01:04
  Nowadays many organizations are adopting MDA to describe their systems. This fact forces organizations to transform their software development process into a Model-Driven Development process. This paper proposes a software development methodology focused on MDA, and describes both the MDD process as well as the main process workflow. The UML Profile SPEM is used to describe the process. This paper presents a MDD process and a set of System Family Engineer concepts to adapt the MDD process according to user and functional requirements. This methodology has been developed in a European IST project (MASTER project IST-2001-34600).   
whitepaper Issues of Structured Vs. Object-Oriented Methodology of Systems Analysis and Design2006-04-27 07:05:49
  In recent years, there has been a surge of interest in Object-Oriented (OO) methodology in the analysis and design of a system. However, there is a dilemma as to how best fit the OO topics with the existing coherent discussion of structured approach of developing a system. This paper addresses some issues related to the two design paradigms.   
whitepaper Business Value of Software Quality2004-11-09 15:18:05
  Software quality should not be considered an optional luxury. In fact, successful software development organizations find that a commitment to high quality speeds development, reduces costs and increases flexibility. This white paper details how.   
whitepaper Business Alignment - Working With Requirements2006-05-26 01:00:26 Select Business Solutions
  Most IT projects fail. An insufficient understanding of the requirements that are driving the project causes most of these failures. Lack of understanding can have many causes - lack of communication with the user community is a common fault. Select Perspective has always emphasized the importance of gaining and maintaining a very clear view of the project requirement - of achieving alignment with the business need. Business Alignment is one of the core consume-side workflows that must be executed in a Perspective-based project. This paper describes the approach to modeling the project requirement adopted by projects that use Select Perspective.   
whitepaper Select Perspective and the Capability Maturity Model2006-05-26 01:00:26 Select Business Solutions
  This paper describes the journey taken by a development organization in improving both its development activities and its business software product. To guide development improvements The Capability Maturity Model (CMM) for Software is used. This model describes the principles and practices underlying software process maturity and is intended to help software organizations improve the maturity of their software processes in terms of an evolutionary path from ad hoc, chaotic processes to mature, disciplined software processes. The CMM is organized into five maturity levels: 1- Initial, 2 - Repeatable, 3 - Defined, 4 - Measured, and 4 - Optimizing.   
whitepaper .NET Solution Architectures: Gathering and Analyzing User Requirements2006-06-23 01:00:29 Pearson Education
  This paper helps to learn how to gather and analyze users' specific requirements in .NET Solution Architectures. The reader will learn the benefits of UML as well as how to use it and will see how to develop world-ready applications. To address the need for a commonly accepted method of object-oriented modeling, the Unified Modeling Language (UML) has been developed. The notations in UML are meant to be straightforward and consistent, and a minimal number of symbols are used. It was purposely designed to be readable on almost any medium, such as whiteboards, paper, or computer displays. IN UML, nine types of diagrams are used to represent the various modeling viewpoints.