[pratima]

The system development methodology supports an integrated set of principles, procedures, practices, technical standards, and supporting tools that the USPTO has adapted for use in developing, modifying, and managing AISs or infrastructure systems.



USPTO’s methodology is described in a series of technical standards and guidelines publications. These technical publications describe methods and procedures as well as documentation requirements (format and content) associated with developing an AIS or infrastructure system within the USPTO information technology infrastructure. The methodology defines the activities that are needed to build a system, the interfaces among those activities, and the products created as a result of those activities. Much of the AIS or infrastructure system analysis and design-level documentation will be captured and maintained in the Computer Aided Software Engineering (CASE) tool repository, and reused where practicable.

System Development Methodology Criteria



In order for the USPTO to build upon business process reengineering activities, share data and processes, and develop and maintain responsive automated information systems on time and within budget, a rigorous and proven system development methodology is needed that:



a. Supports an integrated set of formal techniques for the planning, analysis, design, and development of automated information systems on an enterprise-wide basis rather than on a project-wide basis.

b. Is business-driven and firmly anchored in the strategic planning of the business enterprise.

c. Supports business process reengineering and provides for storage of planning information relative to the business enterprise such as data and process models, critical success factors, process improvement, best practices, and business functions, goals, and objectives.



a. Is supported by a set of commercially available automated tools that facilitate applying the methodology and provide for a rigorous enforcement of the methodology's techniques and standards.

b. Is a data-centered design approach and provides techniques for formal data modeling and data administration.

c. Imposes a rigorous discipline that enforces a good structuring of data and application program code.

d. Supports techniques to identify processes and process improvements that are used many times in the enterprise so that designs and program code can be reused.

e. Emphasizes top management involvement to provide strategic direction and active program sponsor/customer participation throughout the life cycle.

for more information visit:
http://www.onestopsap.com/
or
http://forum.onestopsap.com/forum_posts.asp?TID=202