The tutorial is designed to be self-contained. The afternoon session will focus on business case development and case studies. The morning session will focus on fundamental valuation concepts as well as economics of flexibility in technical and process-related choices. The goal of the tutorial is to expose the audience to this line of thinking and introduce the tools pertinent to its pursuit.
Expert choice 11 tutorial software#
The premise of the field is that software development is an ongoing investment activity in which developers and managers continually make investment decisions requiring the expenditure of valuable resources, such as time, talent, and money, and the overriding aim of which is to maximize added value for each participant. The field of software economics seeks to develop technical theories, guidelines, and practices of software development based on sound, established, and emerging models of value and value-creation, adapted to the domain of software development as necessary. Warren Harrison, Portland State Universityĭonald J. Hakan Erdogmus, National Research Council of Canada Software Engineering Economics: Background, Current Practices, and Future Directions This is a full-day tutorial held on Monday May 20th. The topics are extensively illustrated by examples and experiences from many industrial cases. These topics are, in addition to the technical perspective, discussed from process and organizational viewpoints. Topics include software architecture design in the presence of existing components and infrastructure (top-down versus bottom-up), architecture evaluation and assessment, software artefact variability management, software product lines and the role of the software architect. This tutorial addresses this development by providing an overview and in depth treatment of the issues around architecture-centric engineering of software.
The two typical reasons for this move are (1) the architecture allows for a clear break-down in parts whereas a project-centric approach easily leads to a monolithic system and (2) the organization is interested in exploiting the commonalities between its products or systems. Many software organizations are in the process of moving from project-centric to architecture-centric engineering of software. Tutorial 2Īrchitecture-Centric Software Engineering System architects, chief engineers, project managers, and front-line software engineers will each find immediate value in this tutorial. This tutorial is intended for audiences who practice, or wish to practice, component-based software system design and development.
Expert choice 11 tutorial how to#
This tutorial describes a number of proven techniques and much needed guidance on how to build component-based systems in a real working environment. With more and more software systems being developed from commercially available components, it is increasingly critical to recognize the novel challenges and unfamiliar constraints inherent in such design. The theory largely assumes that the design task is to develop specifications for software component in reality, however, most component-based design relies on preexisting components, which have preexisting specifications. There is a growing gap between the theory and practice of component-based software design. Robert Seacord, Software Engineering Institute Scott Hissam, Software Engineering Institute International Conference on Software Engineeringīuilding Systems from Commercial Components
0 kommentar(er)
