bluuebunny/crossref_metadata_2025_split huggingface dataset:
Integrative Systems Approach to Cost Deployment
Authors: Jeyaratnam Canestus , Doukas Louis , Pollock Graham 
Published: November 2014

AbstractThe central theme to this paper is to provide the research outcome on the application of a software model developed for effective transfer of user requirements into product design features including cost analysis, with built‐in scientific decision making support tool. In the extremely competitive global environment, there is a need for integrating cost evaluation and deployment into the design process in a systematic way for up front identification of cost while maintaining a balance of quality and performance requirements. The developed model is Excel® based and tested with actual industry based case studies as applied to Australian manufacturing and industry. The proposed model will establish measures of World Best Practice with minimum complexity to improve product design and project management.
British Army Equipment Support ‐ How Does It Measure Up To Systems Engineering?
Authors: Wright D M H 
Published: November 2014

AbstractThis paper sets out the full range of activities involved in the British Army's business of supporting our extensive range of complex equipment. These activities are then set against the requirements of total systems engineering, that is the engineering and optimisation of both product and process. A number of shortfalls are identified, principally that there is little attempt to use through‐life systems engineering to achieve optimisation. A comparison is then made between Defence procurement and the operation of the normal commercial market. The demands of equipment support in this commercial environment are also addressed. A number of recommendations for improvement are made, principally the adoption of a more commercial approach to equipment procurement and support.
The CMMI Project
Authors: Ferguson Jack R. 
Published: November 2014

ABSTRACTThe CMMI ProjectThe CMMI project is a collaborative effort sponsored by the Office of the Secretary of Defense/Acquisition and Technology (OSD/A&T) Systems Engineering with participation by U.S. government, industry, and the Software Engineering Institute (SEI). The project's objective is to develop a capability maturity model integrated product suite that provides industry and government with a set of integrated products to support process and product improvement.This project was designed to preserve government and industry's investment in process improvement and to enhance the use of multiple models. The project's outputs include integrated model(s), assessment method(s), and training materials.The CMMI project's objective is to improve the usability of the maturity modeling technology in a wider set of disciplines than simply software. The concept calls for use of common terminology, common components and rules for constructing models, to reduce the training and process improvement effort needed by users of multiple disciplines. In the initial phase, the scope of the CMMI project is restricted to the most needed disciplines: software engineering, systems engineering and Integrated Product and Process Development (IPPD). The initial set of models to be produced include staged and continuous representations for:
Software Engineering
Systems Engineering
Software and Systems Engineering
Software and Systems Engineering with IPPD.
The CMMI Product Suite was designed with the capability to expand in both disciplines and life cycle coverage. While the schedule for these expansions has not yet been decided, other disciplines (such as security systems engineering) are possible. Expansion decisions will be made based upon the success of the initial stage, user community needs and support, and availability of participants for the Product Development Team (PDT).® Capability Maturity Model and CMM are registered in the U.S. Patent and Trademark Office
ATM or Gigabit Ethernet…Which One Will Be The One Stop Solution?
Authors: Smith Reggie 
Published: November 2014

ABSTRACTThis trade study will examine both ATM (Asynchronous Transfer Method) and Gigabit Ethernet. I will look at these technologies to serve as the backbone for a network, plus service down to the desktop. I will examine cost, design, performance and future trends. These technologies will be compared in a same case scenario with both networks passing voice, video and data for a distributive network nationally. This comparison is also considering what the end‐users wish to increasingly use such as the following: scientific modeling, publications, medical data transfers, inter/intranets, data warehousing, network backups, interactive media applications, increased network reliability, low cost, compatibility, etc.I chose this trade study subject comparison because “most organizations competing in the global marketplace increasingly turn to information management technology to gain a competitive advantage” (FORE, 1996). “These new organizations are driven by information and powered by new enablers such as distance learning, collaborative workgroups, telecommuting, videoconferencing, and multimedia front ends to existing databases. Today's conventional LAN (Local Area Network) technologies (e.g., Ethernet, Token Ring, and FDDI) and components (e.g., hubs, bridges, and routers) were not designed to support such demanding requirements” (FORE, 1996).This explosive demand has brought about ATM and Gigabit Ethernet. I believe that ATM will become a natural backbone medium with Gigabit Ethernet service to the desktop. The future looks like a mixed environment with not just one medium providing service.
Managing the right thing: Risk Management
Authors: Langenberg Ilse , de Wit Franklin C.A. 
Published: November 2014

AbstractThe product range of Hollandse Signaalapparaten consists of high‐tech military and civil products. These projects are characterized by uncertainty, which can cause financial, schedule, and performance problems. In order to keep control over the development and delivery of the projects, these problems must be tackled as early on in the project as possible. The method which enables to do so is called risk management.Risks are uncertainties that can occur during the execution in every phase of a project and that have a significant negative impact on the performance, schedule or cost of the project. Risk management can be defined as the identification, assessment and mitigation of risks in order to develop and deliver, on schedule and within cost, a system that meets the performance requirements.The risk management process consists of the following steps:
Identify Risks
Quantify & Prioritize Risks
Plan Risk Mitigation
Implement Risk Mitigation
Track & Report Risks
Between the distinguished steps important iterations take place and the steps should be carried out several times during each project.Risk management is an important, if not the most important, aspect of managing projects. Or as Rear Admiral Bill Carlson, United states Navy once said: “If you are not managing risk, you are managing the wrong thing.”
Experiencing Requirements Engineering for a small system
Authors: Rouge A. , Callet S. , Moinon C. , Ermine F. , Moulis G 
Published: November 2014

AbstractFor software, there exists a community that can provide awareness and elements to justify the adoption of good engineering practices. For systems engineering, all this work is still to be done. This paper provides a modest contribution to such an endeavor, and more precisely in the area of requirements engineering for small systems.The targeted goals for this article are:
Is model‐driven requirements engineering, as practiced for large systems, relevant to develop small systems ?
In which way can requirements engineering return on investment be demonstrated ?
Are many of the assumptions made against documentation and model‐based requirements engineering valid ?
These issues are investigated in the context of the FRUITS experiment that aimed at comparing documentation‐driven and model‐driven requirements engineering.This experiment was carried out in 1998 by the systems department of MTI (Matra Transport International), a railway system provider. And Objectif Technologie provided some support to carry it out.
Providing Pragmatic Advice On How Good Your Requirements Are ‐ The Precept “Requirements Counsellor” Utility
Authors: James Laurence 
Published: November 2014

AbstractOne of the main goals of the Precept venture as defined in (Precept 97) was to “significantly improve the requirements elicitation process”. There are many ways in which this could have been accomplished ranging from the development of new elicitation methods to the development of new intelligent elicitation utilities. This article discusses the latter approach and focuses on a specific Precept utility termed the “Requirements Counsellor” which is designed to provide feedback on the perceived “goodness” of a set of requirements.
Requirements Management for True System Reusability
Authors: Jorgensen Raymond 
Published: November 2014

AbstractThis paper examines capabilities that are required to maintain a reusable development environment for products that are shared across many unique customer needs. Uniqueness within a product offering is driven by special needs or circumstances of the customer, which is translated by a project team into real system requirements. This uniqueness, though, must be managed in light of the product offering that is being built and maintained within a business climate. Diversity of customer needs is a significant cost driver that should be managed to preserve the integrity of the product offering as well as to keep costs under control. By appropriately managing requirements within the project and product development environments, a single, reusable product definition can be preserved that is both tailorable for each customer as well affordable for future customers.
Lessons Learned in Reengineering a Legacy System
Authors: Wimmergren Alan 
Published: November 2014

AbstractThis paper describes Experian's efforts to reduce schedule risk and to improve system quality by instituting a formal testing methodology, both for building a large replacement system and for long term ongoing evolution of that system. Successful testing depends, among other things, on thorough and relatively stable requirements. The paper also describes a weakness of using prototypes to refine requirements and describes how the company instead uses a multiple release software life cycle in order to define requirements incrementally.
Using Web‐Based Tools for Providing Program Management Information
Authors: Manuel Gregory C. , Sunday David A. 
Published: November 2014

ABSTRACTThis paper discusses the development and use of web‐based tools to communicate real‐time, critical Program‐level information throughout an enterprise network of several hundred managers, engineers, and other professionals. The design and development of tools will be briefly described, as well as the integration and current application of the tools. Finally, a vision for planned future enhancements will be discussedThe Internet has increasingly become the route of choice on the information highway. For the few reading this who are not aware of the Internet (where have you been for the past ten years?!?!), it is a system by which computers are electronically linked. The Internet is used to transmit information among widely‐dispursed, even worldwide, computers without regard to platform type. An Intranet is a ‘subset’ of the internet when restricted to operations within a company or enterprise network. The environment described within this paper is that of an Intranet.At the Aircraft Combat Systems Business of the Integrated Systems and Aerostructures Sector of Northrop Grumman, the development and use of intranets has been expanding dramatically. The number of websites and pages has proliferated with no signs of slowing in the near future.There have been debates and discussions in this forum and others regarding the inclusion of Program Management (or Program Management tools) in the broad discipline of Systems Engineering. Within our enterprise element, however, this discussion has been tabled (for now, at least). The SE organization resides within the Program Management organization, and advancement of tools development for SE and for Program Management is being directed, deployed and managed by that organization.
Cross‐Tool Database Connectivity (XDBC): A“Rosetta Stone” for Engineering Methods
Authors: Rhodes Robert R. 
Published: November 2014

AbstractSoftware Engineers who work with multiple modeling tools (such as engineers who use legacy methods to specify requirements for object‐oriented development teams) have sundry and unique needs. An XDBC (Cross Database Connectivity) model to address these needs has been implemented. This XDBC model generalizes tool and method specific artifacts so that remote access to previously isolated tool repository data and cross‐tool translation becomes possible.
Requirements management as a matter of communication
Authors: Ogren Ingmar 
Published: November 2014

AbstractRequirements work all started as a dialogue between a vendor and an end user. Nowadays this dialogue has been complicated through introduction of marketing and acquisition personnel. This has led to introduction of requirements specifications, but the need for a basic dialogue is still there since a specification cannot capture the increase of knowledge that will always take place during development.An efficient dialogue must not only include requirements, but also stated missions, problem management and understandable formalism for the system's structure and behavior.Further study of the dialogue shows that requirements management must be managed as a process in parallel with processes for development and verification.
A Human Factors Integration Capability Maturity Model
Authors: Sherwood‐Jones Brian , Earthy Jonathan , Bowler Yvonne , Taylor Robert , Forster Melanie 
Published: November 2014

AbstractVendor capability assessment is a vital risk‐reduction component of pre‐contract award on major projects, and process improvement has become recognised as an important development in improving productivity and quality. This has become established for Software Capability Evaluation, using Capability Maturity Models. Similar approaches have been developed for systems engineering and are starting to see application.The integration of human factors into systems development is now seen as essential for reasons of manning, safety and operability. The Human Factors discipline has matured and there are now stable standards, and a consensus over the processes involved appears to have developed. However, the means of ensuring Integration into system development are less well evolved.A capability assessment scheme for human factors would extend existing software and system engineering capability evaluations to give assurance that complex systems, such as command centres, will be operable on delivery. This would be particularly valuable because human adaptability and variability pose difficulty for reliance on hard requirements. Traditional specification and test against pre‐defined acceptance criteria is inadequate to assure operability in complex systems. Contractors and/or partners in the development need to provide assurance of their ability to do human factors work within this dynamic project environment and deliver sub‐systems which integrate into the worksystem.This paper summarises the state of the art in Human Factors process models and capability evaluation, sets out the requirements for successful HFI capability evaluation, and discusses a proposed implementation strategy.The presentation will review the requirements for such a scheme and present the development and implementation strategy for a general‐purpose Human Factors Integration Capability Maturity Model.
Engineering in Integrated Project Teams
Authors: Dawson A. J. 
Published: November 2014

AbstractDevelopment teams consisting of user and contractor personnel are becoming recognised as the best way to deliver systems which are focused on the needs of the user. Whilst there are obvious project management and contractual issues, there are also impacts on the engineering process. This paper describes those issues and the lessons learnt from a real project In summary one needs to build on the different skills users and engineers possess, to have a defined engineering process with clearly defined roles, to have a subset of engineering data specially tailored to be understandable to the users and a managed mechanism for assessing and prioritising user comments. These lessons can be applied to a wide range of project types where a mixture of non‐engineers and engineers have to work together.
Using RDD‐1001 to Develop Technical Baseline at the Idaho National Engineering and Environmental Laboratory
Authors: Gibson Patrick L. 
Published: November 2014

ABSTRACTRDD‐100 was used to develop the technical baseline for infrastructure operations at the Idaho National Engineering and Environmental Laboratory (INEEL). Systems engineers in the Environmental Management Integration (EMI) office of Lockheed Martin Idaho Technologies Company (LMITCO), working with functional managers in the infrastructure organizations, developed the technical baseline. Key elements were entered into the RDD‐100 systems engineering tool to provide an easily maintained, dynamic baseline database. The baseline is placed under configuration control and will serve as the foundation for change control and work scope evaluations.
Effect of microseparation on contact mechanics in metal‐on‐metal hip replacements—A finite element analysis
Authors: Liu Feng , Williams Sophie , Fisher John 
Published: November 2014

AbstractSome early failures of metal‐on‐metal (MoM) hip replacements associated with elevated wear have caused concerns for the use of this bearing combination. Simulator studies have shown that microseparation and its associated rim contact and edge loading may produce the most severe wear in MoM bearings. It is generally recognized that this high wear can be attributed to the high contact stress of the head on the rim of the cup. In this study, an improved finite element contact model that incorporates an elastic‐perfectly plastic material property for cobalt‐chrome alloy of the metal bearing was developed in an attempt to provide an accurate prediction of the stress and strain for the rim contact. The effects of the microseparation displacement (0.1−2 mm), cup inclination angle (25−65°) and cup rim radius (0.5−4 mm) on the contact stress/strain were investigated. The results show that a translational displacement >0.1 mm under a load >0.5 kN can produce a highly concentrated contact stress at the surface of the cup rim which can lead to plastic deformation. This study also suggests that the magnitude of translational displacement was the major factor that determined the severity of the contact conditions and level of stress and strain under microseparation conditions. Future studies will address the effect of surgical translational and rotational malposition and component design on the magnitude of microseparation, contact stress and strain and severity of wear. © 2014 The Authors. Journal of Biomedical Materials Research Part B: Applied Biomaterials Published by Wiley Periodicals, Inc. J Biomed Mater Res Part B: Appl Biomater, 103B: 1312–1319, 2015.
TNFα Shedding in Mechanically Stressed Cardiomyocytes is Mediated by Src Activation of TACE
Authors: Niu Airu , Wang Bin , Li Yi‐Ping 
Published: November 2014

ABSTRACTSynthesized by the heart under hemodynamic overloading (mechanical stress), TNFα exerts complex effects on the heart —beneficial as a membrane protein and detrimental as a secreted protein, which presents a dilemma in the treatment of congestive heart failure. We postulate that by selectively blocking mechanical stress‐induced cardiomyocyte secretion of TNFα, a function of TNFα converting enzyme (TACE), the detrimental effect of TNFα can be mitigated. However, the mechanism through which mechanical stress activates TACE in cardiomyocytes is unknown. Here, we report a molecular mechanism that mediates TACE activation in mechanically stressed cardiomyocytes. We found that the non‐receptor tyrosine kinase Src mediates TACE activation in mechanically stretched rat cardiomyocytes by phosphorylating the Tyr‐702 residue within the intracellular tail of TACE. The rapid activation of Src in mechanically stretched cardiomyocytes is followed by TACE phosphorylation on Tyr‐702, leading to activation of p38 MAPK, a kinase that is an effector of TNFα receptor activation. Pharmacological inhibition or silencing of Src attenuated stretch‐induced TACE phosphorylation on Tyr‐702 and p38 activation. Overexpression of a TACE mutant in which Tyr‐702 was replaced by alanine (TACE‐Y702A) attenuated stretch‐induced TNFα release from cardiomyocytes as well as activation of p38. These data suggests that Src mediates TACE activation in mechanically stressed cardiomyocytes and this mechanism could be exploited for specific blockade of TNFα secretion and its detrimental effects in congestive heart failure. J. Cell. Biochem. 116: 559–565, 2015. © 2014 Wiley Periodicals, Inc.
The Hepatic Transcriptome of Young Suckling and Aging Intrauterine Growth Restricted Male Rats
Authors: Freije William A. , Thamotharan Shanthie , Lee Regina , Shin Bo‐Chul , Devaskar Sherin U. 
Published: November 2014

ABSTRACTIntrauterine growth restriction leads to the development of adult onset obesity/metabolic syndrome, diabetes mellitus, cardiovascular disease, hypertension, stroke, dyslipidemia, and non‐alcoholic fatty liver disease/steatohepatitis. Continued postnatal growth restriction has been shown to ameliorate many of these sequelae. To further our understanding of the mechanism of how intrauterine and early postnatal growth affects adult health we have employed Affymetrix microarray‐based expression profiling to characterize hepatic gene expression of male offspring in a rat model of maternal nutrient restriction in early and late life. At day 21 of life (p21) combined intrauterine and postnatal calorie restriction treatment led to expression changes in circadian, metabolic, and insulin‐like growth factor genes as part of a larger transcriptional response that encompasses 144 genes. Independent and controlled experiments at p21 confirm the early life circadian, metabolic, and growth factor perturbations. In contrast to the p21 transcriptional response, at day 450 of life (d450) only seven genes, largely uncharacterized, were differentially expressed. This lack of a transcriptional response identifies non‐transcriptional mechanisms mediating the adult sequelae of intrauterine growth restriction. Independent experiments at d450 identify a circadian defect as well as validate expression changes to four of the genes identified by the microarray screen which have a novel association with growth restriction. Emerging from this rich dataset is a portrait of how the liver responds to growth restriction through circadian dysregulation, energy/substrate management, and growth factor modulation. J. Cell. Biochem. 9999: 1–15, 2015. © 2014 Wiley Periodicals, Inc. J. Cell. Biochem. 116: 566–579, 2015. © 2014 Wiley Periodicals, Inc.