Listing 1 - 10 of 240 | << page >> |
Sort by
|
Choose an application
Papers from the October 1995 conference look at subjects such as object-oriented techniques; tools and environments; maintenance of user interfaces; reverse engineering; reuse; maintenance management; reengineering techniques; testing; quality; and maintenance process issues from the perspective of software systems as business assets. Topics include the effects of inheritance and architecture on the maintainability of object-oriented systems; domain-retargetable reverse engineering; user-interface migration from BASIC to Visual C++; correcting for unreliable regression integration testing; and using views to maintain Petri-net-based process models. No index. Annotation copyright by Book News, Inc., Portland, OR.
Choose an application
Papers from the October 1995 conference look at subjects such as object-oriented techniques; tools and environments; maintenance of user interfaces; reverse engineering; reuse; maintenance management; reengineering techniques; testing; quality; and maintenance process issues from the perspective of software systems as business assets. Topics include the effects of inheritance and architecture on the maintainability of object-oriented systems; domain-retargetable reverse engineering; user-interface migration from BASIC to Visual C++; correcting for unreliable regression integration testing; and using views to maintain Petri-net-based process models. No index. Annotation copyright by Book News, Inc., Portland, OR.
Choose an application
The minimum required contents of a Software Configuration Management (SCM) Plan are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.
Choose an application
The only authoritative reference to provide a management perspective of software maintenanceSoftware maintenance accounts for 60-90% of software life-cycle costs, and unfortunately, very little attention is given to software maintenance education, training, and research. Now, two experts in the field explain how understanding software maintenance, implementing best practices, and improving its processes can help software managers to dramatically cut costs.Software Maintenance Management explores the domain of software maintenance management and provides road maps for improving software maintenance organizations. It describes full maintenance maturity models organized by levels 1, 2, and 3, which allow for benchmarking and continuous improvement paths. Goals for each key practice area are also provided, and the model presented is fully aligned with the architecture and framework of software development maturity models of CMMI and ISO 15504.Complete with case studies, figures, tables, and graphs, Software Maintenance Management fills the need for a comprehensive and authoritative reference on the subject for maintenance managers, software managers, systems analysts, quality managers, and quality analysts. It alsoserves as a valuable textbook for advanced undergraduate and graduate courses in softwareengineering, software maintenance, software process improvement, and software benchmarking.
Choose an application
Choose an application
Replaced by ISO/IEC 14764: 2006. The process for managing and executing software maintenance activities is described.
Choose an application
Choose an application
Choose an application
Promoting and facilitating interoperability between components of automatic test systems where test results need to be shared is addressed in this standard. The standard thus facilitates the capture of test results data in storage devices and databases, facilitating online and offline analysis. The test results schema becomes a class of information that can be used within the SIMICA family of standards. The exchange format is expressed in both the OWL and XML formats.
Choose an application
Promoting and facilitating interoperability between components of automatic test systems where test results and/or maintenance actions need to be shared is addressed in this standard. The standard defines the common elements between both test results data and maintenance action data. The common schema becomes a class of information that shall be used within the SIMICA family of standards.
Listing 1 - 10 of 240 | << page >> |
Sort by
|