Adaptable Process Model Product Description
		A software process model that can be adapted to your organization's specific project needs. The APM is intended as a basis from which a customized software process can be developed. IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.		Just Released! Another novel by Roger Pressman!
				Available in trade paperback and e-book editions. For more information, click here.
	Adaptable Process Model - Product Description The intent of RSP&A's Adaptable Process Model (APM) is to provide you with a software process that you can customize and adapt to local needs. The APM includes a detailed process flow implemented as a hypertext document, descriptions of many key software engineering tasks, document templates, and checklists. Acquiring the APM can significantly reduce the time required to develop your company's software process description. Because the complete APM is provided in hypertext format within the RSP&A Web site, you and your colleagues review the complete generic process. If you think it has merit for your organization, the complete hypertext version can be acquired for an extremely reasonable price. You can then build a local website for Internet or intranet application, while at the same time making the adaptations necessary to mold the APM to local requirements. In most cases, large portions of the APM can be used as is, but in every case, you have the capability to modify terminology and process content to meet your needs and better reflect your local information technologies or engineering environment. Complete information on APM licensing and pricing is available at this Web site. If you have additional questions, please contact us. How to Use the Adaptable Process Model (1) First, we'd like to know who you are. Please send us an email to register with your name, organization and e-mail address. We respect your privacy and will not share this information with any third party. Please Register now. (2) Now you're ready to examine the APM. Begin by reading about the APM. Introduction to APM If you need information about APM's traceability to the SEI CMM and ISO-9000, examine: SEI Capability Maturity Model Compliance Issues ISO-9000 Compliance Issues The APM can be adapted to your project environment. To do this, perform the following steps: Selecting the task set for your project Establishing the degree of rigor Characterizing your project Interpreting the TSS value Selecting the task set Now you're ready to examine the APM process flow. Follow the process flow to the level of detail that is appropriate for your needs. A description of many software engineering tasks -- including intent, mechanics, SQA points, do's and don'ts, and helpful hints -- is contained at the botton level of detail. The APM process flow suggests the development of a number of software engineering work products. These are often organized as a set of documents and reports. The following document templates are available as part of the APM: System Specification Software Project Plan SQA Plan Technical review summary report SCM Plan Software change request Software change report Engineering change order Software Requirements Specification Software Design Specification Test Specification Developing (and later reviewing) software engineering work products demands attention to many details. The following software engineering checklists may be useful whenever you have to develop or review these softare engineering work products: CHECKLISTS FOR MANAGERS The following checklists are provided to assist managers in assessing the quality of various work products produced early in the software process. It should be noted that these checklists are not intended to be comprehensive in nature. Rather, they provide a starting point from which an assessment of quality can be made. Assessing the Project pLan Assessing Cost Estimates and Schedule Conducting Feasibility Analysis Airlie Project QuickLook (best practices that should exist for all projects) Assessing Team Structure and Resources Conducting Risk Analysis Software Quality Assurance Checklist ISO-9001 Checklist Software Configuration Management Checklist Assessing the Likelihood of Reengineering CHECKLISTS FOR PRACTITIONERS The following checklists are provided to assist software engineers (and those with technical interest) in developing and reviewing work products produced as part of the software process. It should be noted that these checklists are not intended to be comprehensive in nature. Rather, they provide a starting point from which an assessment of quality can be made. System Level Requirements Validation Preparing for Software Requirements Elicitation Conducting and Reviewing the Analysis Model Software Requirements Specification Checklist Conducting and Reviewing the Software Design Model General Issues Data design Architectural design User interface design Component-level design Conducting Unit Tests Conducting Integration Tests Conducting Validation Tests Testing GUIs Reviewing OOA and OOD Models Conducting Object-Oriented Testing Component-Based Software Engineering Assessing Quality Of Web Applications (WebApps)