Collecting requirements and strategic analysisThe prerequisite of inception of a software development project is the preparation of vision and conceptual architecture documents of the system. The vision document of a system is in essence an business agreement between different stakeholders of the system, containing answers to questions like "what is the purpose of the system"?, "why we need a system?", "which problems it is meant to solve?" and "what is life like after the system is put into production?". The conceptual architecture document describes how to meet the requirements set by the vision.
The main components of a vision document are descriptions of business reasons, scope, main requirements (functional and non-functional) and risks. - The conceptual architecture document includes in brief the model of the system, decomposition of modules, reference architecture (what we have now and how to utilize that), objects, development patterns and constraints.
- Vision and conceptual architecture documents are part of strategic analysis accompanied by business analysis.
- Collecting requirements is usually followed by planning resources and duration of the project and is finalized by invitation to tender.
ASA has the specific expertise to help contracting entities to prepare all these required documents to maximize the probability of success of the project in both local and international project environments. ASA helps to collect requirements from inside of the organization, harmonize and prioritize the requirements, prepare all the necessary documents, organize the invitation for tenders, help to negotiate development agreements with tenderers, consult the preparation of development agreements (both in juridical and contents wise) and support the development with other services in later stages.
|
