Principles of the USoft Approach |
|
|
|
The USoft Approach has four basic principles of delivering business software: •Deliver business conduct. In the USoft Approach, you define and model business reality or business conduct. This contrasts with approaches where you (only) specify what are the desired characteristics of a physical software project, or what are the various steps to be carried out in a project plan. •Deliver in short cycles. In the USoft Approach, you deliver work continuously in short, subsequent cycles. While some are busy defining or delivering one batch of specifications and implementations, others are already busy planning the next phase of work. •Deliver specifications and implementations in parallel. In the USoft Approach, specifications are regarded as an end product in their own right. While they describe or imply target implementations, their role has not ended when these implementations are delivered. •Deliver a central repository with distinct application tiers. In the USoft Approach, deliverables are not just file structures containing software code. You deliver a central repository from which all manner of software components within and outside the physical repository are referenced. This repository has distinct application tiers. Click on a subject to continue: Advantages of the USoft Approach Deliver specifications and implementations in parallel Deliver a central repository with distinct application tiers |
|