|
|
| home about us free pdf software downloads links privacy site map copyright policy |
|
|
Many avionics systems have been successfully developed using custom hardware and software.. Common processing subsystems: These should allow multiple applications to share and reuse the same computing resources. This results in a reduced number of subsystems that need to be deployed and more efficient use of system resources, leaving space for future expansion. Software abstraction: This should isolate the application not only from the underlying bus architecture, but also from the underlying hardware architecture. This enhances portability of applications between different platforms and also enables the introduction of new hardware to replace obsolete architectures. Cost of change: An IMA architecture should reduce the cost of change: It facilitates reuse and lowers retest costs, because it simplifies the impact analysis by decoupling the constituent pieces of the platform of multiple applications executing on the same processor. These and other IMA standards place new demands on the software architecture, especially the RTOS implementation provided by the COTS supplier. Smiths Aerospace Boeing 7E7 Dreamliner Common Core System; www.windriver.com: Customers / Customer Success EADS / CASA; www.windriver.com: Customers / Customer Success ARINC Specification 653-1, “Avionics Application Software Standard Interface.” Third IEEE International High-Assurance Systems Engineering Symposium, 1998. http://doi.ieeecomputersociety.org/10.1109/HASE.1998.731596 P. Parkinson & F. Gasperoni, “High Integrity Systems Development for Integrated Modular Avionics Using VxWorks and GNAT.” 7th International Conference on Reliable ... Total global demand for software will grow by an order of magnitude over the next decade, driven by new forces in the global economy like the growing role of software in social infrastructure, by new application types like business integration and medical informatics, and by new platform technologies like web services, Without comparable increases in productivity, total software development capacity seems destined to fall far short of total demand by the end of the decade.http://www.softwarefactories.com/ScreenShots/MS-WP-04.pdf. Instead, software development methods and practices will have to change dramatically to make developers much more productive. What will industrialization look like in the software industry? We cannot know with certainty until it happens, of course, but we can make educated guesses based on the way the software industry has evolved, and on what industrialization looks like in other industries. The next step is to move from documentation to automation, using languages, frameworks and tools to automate more of the software life cycle. Automating Software Development Can we automate software development? A software factory contains three key ideas: a software factory schema, a software factory template and an extensible development environment: Think of the software factory schema as a recipe. When configured with the software factory template, VSTS becomes a software factory for the product family. We might use this software factory schema to configure VSTS to become a software factory to build members of this family. We would use the extensibility features of VSTS to host a software factory template based on this software factory schema. Included in the ... Abstract: This report presents a perspective on software reuse in the context of "ideal" software development capabilities.http://www.sei.cmu.edu/pub/documents/88.reports/pdf/tr22.88.pdf. Software reuse is viewed as a means of achieving—or at least approximating—the ideal capabilities. A generic appli-cation and development model is proposed for unifying various types of software reuse. The approach presented in this report is intended to lead to a reuse strategy and methodology for software development. This report focuses on an approach to software reuse which can be expanded to a reuse strategy for software development. Software engineering attempts to reduce the search aspects of the process by formulating methodologies which specify the type of the interme-diate artifacts and guide the application of operators. Using this approach, software reuse can be precisely formulated as analogical development, where a previous development from similar requirements is transformed to a new devel-opment satisfying new constraints. In the next section, they are recast as software development scenarios so that they can become the basis for a reuse strategy. The three scenarios include a variety of software development approaches that can be ap-plied to software reuse. For example, a particular VCR can be characterized by a set of VCR features; an automobile can be characterized by a set of automobile features; or a software switch can be characterized by a set of switching features. In this scenario, there exists a software product with a large set of features from which the desired product is de-rived, and an impact analysis maps the desired features to the existing system. Thirdly, reuse of ... What if your software was tested and working before you received first silicon samples? Converges the hardware needed to drive call-processing and applications-processing technologies with a shared memory system Separates the communications software from the application processing to provide a simplified development environment Dramatically reduces power consumption by utilizing hardware acceleration and memory Designers are faced with serious project delays if they wait for first silicon to begin software development and testing.http://www.freescale.com/files/wireless_comm/doc/brochure/MXCSWDEVWP.pdf. Software teams can port an operating system, develop device drivers and complete most of the software stack months before the silicon exists. Parallel hardware/software development—The resulting platforms are capable of executing application software on top of the virtual hardware at speeds of several tens of millions of cycles per second. Increased software development productivity—A virtual platform increases software developers' ability to observe and control target hardware, not limiting that ability to available pins or the JTAG interface on the physical prototype. This capability is especially useful when designing complex software components like device drivers that touch the hardware-software boundary. By using a virtual platform, you can automate tests of your software using either built-in or desktop testing tools and create regressions to assure that changes do not diminish software functionality. By aligning internal software-development phases with MXC platform deliveries, software development started as early as six weeks after platform development began. In ... Rational Software Over the past two decades, the software industry has moved unrelentingly toward new methods for managing the ever-increasing complexity of software projects.http://www.ibm.com/developerworks/rational/library/content/RationalEdge/apr01/ImprovingSoftwareDevelopmentEconomicsPartIApr01.pdf. While software technologies, processes, and methods have advanced rapidly, software engineering remains a people-intensive process. For more than twenty years, Rational has been working with the world's largest software development organizations across the entire spectrum of software domains. Today, we employ more than 1,000 software engineering professionals who work onsite with organizations that depend on software. We have diagnosed the symptoms of many successful and unsuccessful projects, identified root causes of recurring problems, and packaged patterns of software project success into a set of best practices captured in the Rational Unified Process. Rational is also a large-scale software development organization, with more than 750 software developers. One of our primary goals is to apply what we have learned in order to enable software development organizations to make substantial improvements in their software project economics and organizational capabilities. A Simplified Model of Software Economics There are several software cost models in use today. The latest version, COCOMO II, is the result of a collaborative effort led by the University of Southern California (USC) Center for Software Engineering, with the financial and technical support of numerous industry affiliates. To develop a software cost and schedule estimation model for the lifecycle practices of the post-2000 era 2. This level of unpredictability in the outcome ... The combination of ever-growing complexity and increasing software content of embedded systems and Systems-on-Chip (SoCs) demand software development and integra-tion earlier in the design cycle to reduce product risk and time-to-market (TTM).http://www.virtio.com/newsroom/articles/EDNSystemDesignSeries.pdf. The rapid progress in automat-ed hardware synthesis, and the adoption of intellectual property (IP) re-use and platform-based solutions continue to shrink the hardware design cycle—causing software development to become the design bottleneck. To increase the success of embedded systems, new ap-proaches focusing on the software development side of embedded system designs are essential. Virtual Prototyping is a key approach enabling embedded software developers to start development earlier in the system design cycle by cutting the dependency on the physical system hardware. A major impediment to starting software development is the unavailability or late availability of the target hardware, whether it be a development board or SoC silicon prototype. integrated development environ-ment (IDE) provides support for application software development, but without a hardware prototype in place, falls short of helping the designer with the task of develop-ing software components that have to be tightly coupled with the underlining hardware, such as hardware abstract layers (HAL), Virtual prototyping as a software IDE extension A different approach for software development is possible because software models require less hard-ware details in order to accurately execute. Software development needs to occur as close as possible to the beginning of the design cycle which is in-line ... Periodically, the development staff is pulled off the project in order to help perform the tasks by hand, which makes them fall even further behind on the software.http://www.satisfice.com/articles/test_automation_snake_oil.pdf. Seasoned software engineers know that, and approach each new project with a wary eye and skeptical mind. In the nine years I spent managing test teams and working with test automation (at some of the hippest and richest companies in the software business, mind you), the most important insight I gained was that test software projects are as susceptible to failure as any other software project. For GUI software, it is very hard to automatically notice all categories of significant problems while ignoring the insignificant problems. The problem of automatability is compounded by the high degree of uncertainty and change in a typical innovative software project. In market-driven software projects it's common to use an incremental development approach, which pretty much guarantees that the product will change, in fundamental ways, until quite late in the project. Is the behavior of the software under test the same with automation as without? Common culprits are changes to the software being tested, memory problems, file system problems, network glitches, and bugs in the test tool itself. Besides, there are so many particulars and hidden factors involved in a genuine comparison that the best way to evaluate the issue is in the context of a series of real software projects. Most groups I've worked in that tested GUI software tried at one point or another to make all testers do part-time automation, and every group eventually abandoned that idea in favor ... The protocol stack will be re-configurable for different partitions between the Bluetooth A simple, PC based host application BlueChat allowing the transfer of text and files and the establishment/teardown of an audio connection.http://www.btdesigner.com/pdfs/casira.pdf. written as a Windows DLL. Flash memory programming utility to allow future releases of the Bluetooth stack firmware to be downloaded from a PC to the BlueCore The system hardware consists of two units each containing: A module including the BlueCore Bluetooth IC, flash memory (for the host controller protocol stack firmware), crystal reference and antenna. A motherboard containing host I/O and man/machine interface elements including RS232 and USB drivers & external connector, audio codec, external audio socket for a headset and internal connectors for audio PCM stream & synchronous serial interfaces. The lid of the case is removable to allow access to the PCM and synchronous serial interfaces for embedded software development (for the embedded s/w development toolkit, available later). However, Casira users can also buy extra modules - supplied as bare PCBs, without software - for cost-effective construction of piconets, and simpler connection to host equipment (the bare PCB can easily be mounted as a daughterboard for example). From September 2000, CSR can support directly customers who wish to write their own software applications running directly on the BlueCore chips. These software tools will be offered as a software upgrade to existing customers of the CASIRA The software environment will allow customers to create on-chip program in user space whilst maintaining the integrity ... an innovative way of developing embedded software, compatible with the tools a developer is familiar with, and effective as a target in an iterative “edit-compile-debug” development cycle.http://www.synopsys.com/products/designware/pdfs/vp_improving_software_development.pdf. Today's embedded systems need to verify that that the combination of hardware and software matches the expected functionality and per-formance. Performing this task requires control and observation of the hardware, with aware-ness of the software execution. Another major impediment to starting software development and hardware/software integration is the late availability of the target hardware. Today's SoC hardware/software co-design and co-verification approaches are geared towards the silicon development. hardware development to evaluate small amounts of software interacting with the hard-ware, the detailed HDL models limit the per-formance, typically limited to ~50,000 instructions per second. The software design process includes many stages, including specifications, coding and integration. Developers need to embrace newer, more-so-phisticated software development tools, simu-lation modeling being one of them. With virtu-al prototyping, Virtio offers a technology which delivers a software-based approach for develop-ing embedded software long before any hard-Components of virtual proto-typing technology ware is available, and thus increases hardware availability and accessibility. This technology enables the creation of a software-based embedded platform that can fully mirror the functionality of a target SoC or board. Essential for software developers to adapt sim-ulation technology is the abstraction level of the ... 28 years of high reliability software project management, development, quality assurance, and regulatory affairs Software & Quality Systems regulatory crisis management, and FDA negotiation Software validation for medical device, blood establishment, pharmaceutical, & medical gas manufacturers including Part 11 compliance Experience with software based devices including implantable defibrillators, IVDs, PACS, bedside monitors, blood bank systems, clinical information systems, infusion pumps, hemodialysis monitors, insufflators, surgical devices, MRIs, home use devices, CADx, and others.http://www.softwarecpr.com/DOCS/AKqualificationssheets.pdf. 510(k), IDE, and PMA software submissions for all classes of devices Constructed FDA and ISO 9001 compliant qual-ity systems. Software hazard analysis and risk management including conformance to standards Software technical reviews, process measure-ment, and process improvement Implementation of effective, compliant quality systems, design control, and software development standards, for large and small companies and groups Software project management and facilitation. Key contributor to development of the AAMI Formerly International Director of Software & U.S. Reviewer for the AAMI/FDA Production Software Validation-working group. Represented the Medical Device Manufacturer’s Association on the executive board of the AAMI/ FDA Medical Device Software Standard Commit-tee for development of SW68 Medical device soft-ware — Software life cycle processes Developer and Lead Instructor of the AAMI/FDA Software Validation and Part 11 Course Regulation and Design Control courses Author of the Software Validation chapter in the 1997 AAMI ... The purpose of this document is to put forth guidelines for implementing software peer reviews within the Office of Hydrologic Development (OHD) at the National Weather Service.http://www.nws.noaa.gov/oh/hrl/developers_docs/Software_Peer_Review_Guidelines.pdf. Peer reviews will be conducted as part of the software validation process and will be performed during the Hydrologic Operations and Service Improvement Process (HOSIP) Stage 4 (Operational Development) as well during software maintenance. It is highly recommended prototyping software undergo peer reviews as well, though they may not need to follow the guidelines discussed in section 4.0. From a software development perspective, the product being assessed is source code. In the software world, the term peer review is often used interchangeably with the term code walkthrough. A code walkthrough is the act of tracing the logic and validating the assumptions of a software module using test cases. Performing software peer reviews has the following advantages: Most important, they promote software that is easy to read and maintain They serve as a mechanism for enforcing the OHD General Programming Standards. They are or will be required by our software delivery customers, that is, AWIPS and NEXRAD Standards apply to all types of software tasks, small and large. The peer review is the mechanism which ensures that software developers are following these standards and guidelines when writing programs. 4.1 Scope of Software Development Tasks It is difficult to develop a metric which precisely defines the scope of a software project and how detailed of a peer review is required. For the purposes of this document, software tasks have been divided ... Many software systems currently being deployed in both military and industrial domains serve their users through a large number of concurrent processes.http://www.serc.net/report/tr82f.pdf. But a software system cannot evolve without an understanding of its design, and such understanding is easily lost when the developers disperse. This paper presents a relatively simple method for using traces of inter-process messages to recover functional software design threads from a large, multi-process system. The method seems to be effective in providing useful insights even to Software Engineers who are relatively familiar with the system. The large multi-process software systems often found in major aerospace systems are very costly to develop and so must be designed for long useful lives. From a Software Engineering point of view, JSTARS is an interesting example of the complexities of modern military software. A software thread typically starts with a discrete event or operator input and ends with another discrete event or with operator output. The thread gives a visual representation of a functionality and helps to identify major software components. While not all JSTARS software was designed using threads, they were often used to allocate resources to meet timing constraints and served a communications function since the thread may span units developed by different teams. All message traffic could be logged, and software was available to extract and format information from this log. Could key processes and messages involved in a design thread be identified by applying Software Reconnaissance to the message log generated when that thread was exercised? The ... For the purposes of the Software Design and Development Stage 6 Syllabus, software design and development refers to the creativity, knowledge, values and communication skills required to develop computer programs.http://www.boardofstudies.nsw.edu.au/syllabus_hsc/pdf_doc/softwaredesign_syl.pdf. An understanding of these and the situations in which they are applied is essential in software development. So too is an understanding of how hardware and software are interrelated and need each other to function. The focus of this subject is the development of computer-based solutions that require the design of computer software. Students interested in the fields of software development and computer science will find this subject of value. The subject is not only for those who seek further study or careers in this field, but also for those who wish to understand the underlying principles of software design and development. Students with software development skills wishing to acquire team and communication skills will find this subject useful. Study of this subject will enable students to take part in debates on software development in society. Planning and organising activities and working with others and in teams are integral to the development of software and are addressed in Preliminary and HSC courses, mainly through the development of software solutions using effective project management techniques. Hardware and software are two different but dependent components of a computer system — they cannot be used in isolation. The approach used for a given software solution will reflect the level of ability of those developing the software, its purpose and its users. P5.2 uses and develops documentation ... Quality requirements, captured in general as nonfunctional requirements in the early steps of software development, influence greatly the software system’s architecture.http://www.jot.fm/issues/issue_2002_09/article4.pdf. An important aspect of architectural design is that, on one hand quality requirements influence greatly the software architecture. Software architecture design should not be considered as an independent activity, but a step further in the development and evolutionary process of software products. The Test Model is used to evaluate the architecture, but how to design the part of the Test model corresponding to check the architectural behavior against the established quality goals is left to the software engineer team customizing the UP. This design is again evaluated and the same process is repeated, if necessary, until all quality requirements are fulfilled or until the software engineer decides that there is no feasible solution. In this case the software architect needs to renegotiate the requirements with the customer. It provides a way to evaluate software architecture’s fitness with respect to multiple competing quality attributes. In our case, this aspect is crucial, because we want to define a quality design process to build a solid baseline for the software architecture. SQUID supports the activities for quality specification, planning, control and evaluation and the modeling the software measurement that support these activities. Definition of the objects of the development process According to the SQUID approach, in order to define the conceptual model of software quality, customized to the development process, the development objects have to de ... | |
