Planning Frameworks

Business Goals in Software Acquisition
A business goal is an expression of some organizational objective — sometimes referred to as a business driver — not specific to the solution, but focused on what the organization should do or how it should behave.

Capabilities Architecture
Focusing first on a view of "how" work is performed makes assumptions about "what" is performed. Solutions are then limited to improving the mechanics — not challenging the fundamental premise of the work.

Capability Feasibility Assessment
Starts with the purpose, audience, drivers, and motivations of the assessment and then validates the opportunities and efficiencies enabled.

Critical Success Factors
Critical success factors include issues vital to an organization's current operating activities and to its future success.


Identifying the Quality Attributes of Software and Systems Acquisition Strategies
Acquisition quality attributes are properties of an acquisition approach. An acquisition quality attribute is a measure or testable property of an acquisition’s strategy that is used to indicate how well the acquisition satisfies the needs of its stakeholders. 

Platform Independence and Vendor Neutrality
People who buy vendor-locked-in products are buying trains on tracks while thinking they’re buying cars.

Software and Systems Quality Attributes
Quality attributes are a measurable or testable property of a system that is used to indicate how well the system satisfies the needs of its stakeholders.

Solid-State Financial Management Systems
Solid-state means ordinary power users can employ low-cost extensions to enterprise capabilities that are permanently enabled and unaffected by changes to parent applications running in the cloud.

A strategic information system is a computer system that implements business strategies. They are an integral and necessary part of the strategic component of a business, and they affect profitability and growth.

Technological Soft Goals
Broadly, functional requirements define what a system is supposed to do. Non-functional requirements define how a system is supposed to be. Functional requirements are usually in the form of "system shall do requirement." In contrast, non-functional requirements (technological soft goals) are in the form of "system shall be requirement," an overall property of the system as a whole or of a particular aspect and not a specific function.

Technology & Technology Transfer
Technology may be broadly defined as the knowledge, skills, methods, and techniques used to accomplish specific practical tasks. Thus, technology is more than just methods and materials; in the broader context it also includes the people, policies, and procedures which ensure its application.